Before Stride creates Adobe Target audiences from your Tealium AudienceStream audiences, set the rule that decides how they are named and how they match visitors.
Note
You need a Tealium API key integration and an Adobe IO integration with Adobe Target. Stride uses your default integration of each kind.
Who can do this
Only Owners and Admins can save config rules and add audiences to Adobe Target.
Tealium Audience Stream #
Go to Audiences → Tealium Audience Stream. The page lists the audiences in your default Tealium AudienceStream profile.

For each AudienceStream audience, the table shows its ID and Name and, once it has been sent to Target, the Adobe Target audience ID, name and workspace, and when and by whom it was last modified. Search by audience name with Search By Name. If there are no audiences to show, the page says “No Tealium Audience Stream found.”
Adobe Target audience config rules #
- Click AT Audience Config rules.

- Fill in the three fields:
| Field | Meaning |
|---|---|
| Mbox Param name | The mbox parameter Tealium sends to Target with the visitor’s audiences, for example at_param. |
| Naming convention | How Stride names each Adobe Target audience. You can use {{AS_AUDIENCE_ID_NUMERIC}} (the AudienceStream audience’s numeric ID), {{AS_AUDIENCE_ID_FULL}} (its full ID) and {{AS_AUDIENCE_NAME}} (its name). For example, AT_{{AS_AUDIENCE_ID_NUMERIC}} gives names like AT_123. |
| Comparison rule | How the Target audience compares the mbox parameter with the audience’s numeric ID: Equals, Equals Ignore Case, Contains or Contains ignore case. |
- Click Submit.
If no rule exists yet, Stride shows “You have no Adobe Target Audience config rule, please add new” when you try to add audiences. When you send audiences, Stride uses the first rule.
Then send audiences to Adobe Target, by hand or on a schedule.