Adobe Audience Manager
Adobe Audience Manager & AB Tasty
Adobe Audience Manager (AAM) is Adobe's audience data management platform (DMP) that lets you build audience segments based on behavioral, demographic, or first/third-party data.
The Adobe integration allows you to import your AAM segments into AB Tasty, so you can target them through AB Tasty campaigns.
A segment in AAM is any subset of users based on a particular criterion defined by you. For further information on how to use segments, please refer to the Adobe Audience Manager documentation.
How it works
1. Audience list refresh (compile-time) Every time the AB Tasty tag is refreshed or recompiled, AB Tasty calls the Adobe API to retrieve the list of available audiences (ID / Name) and stores it in local storage as segment_list.
2. Client-side setup (per session) The client is responsible for:
setting up authentication with Adobe,
appending a cookie named
AAM_ABTASTY, containing the ID/Name of the segment(s) the current visitor belongs to.
3. Matching (per session) When the AB Tasty tag executes for a given user session, it reads the AAM_ABTASTY cookie and compares its value against the segment_list stored locally.
4. Activation If a match is found, AB Tasty sends a "segment" hit to the collection layer. The corresponding audience becomes available for targeting in AB Tasty.
Adobe (AAM)AB Tasty TagClientAdobe (AAM)AB Tasty TagClientOn tag compile / refreshOn each user sessionalt[Match found][No match]API call - get available audiencesAudience list (ID/Name)Store as segment_list (local storage)AAM_ABTASTY cookie (via client-side auth)Compare cookie value vs segment_listSend "segment" hit to collectionAudience available for targetingNothing happens
{% hint style="warning" %} segment_list is only refreshed when the tag is recompiled — not continuously. If a new audience is created in Adobe, it will not be usable in AB Tasty until the next tag recompilation. The cookie-matching step itself, however, runs on every session. {% endhint %}
Integration
Get Adobe API credentials
The Adobe pull integration uses the Adobe API to retrieve the list of available audiences. To use it, you'll need valid API credentials from your Adobe Audience Manager / Adobe Experience Platform account (typically generated via the Adobe Developer Console).
General steps:
Access your Adobe Developer Console / Audience Manager admin settings.
Create (or request) API credentials scoped to Audience Manager.
Copy the credential values (client ID / secret, or API key depending on your setup) and store them in your preferred password manager. You may not be able to view them again later.
Enabling the integration on AB Tasty
To enable the integration on AB Tasty (with your Adobe credentials ready), follow the steps below:
Access Integrations > Integration Hub > Pull.
Search for and select Adobe
Click Setup connector.
Give a name to your connector so you can easily retrieve it.
Enter your Adobe API credentials + User credentials
Click Save and create connector.
Your AB Tasty Tag will be refreshed
Client-side setup (required)
Unlike a purely server-to-server pull integration, this connector also requires client-side work:
Implement Adobe authentication on your site/app,
append the
AAM_ABTASTYcookie with the relevant segment ID/Name for the current visitor.
Without this step, the tag has no cookie value to match againssegment_list, and no audience will ever activate, even if the connector is correctly configured.
Configuration
Once the integration is activated and configured, you can retrieve Adobe audiences in the segment builder (available when you create a new segment).
Audiences generated by your integrations can be found in Segment Builder under 3rd Party Audiences>Adobe
Technical Specifications
Pull trigger
Tag refresh / recompilation
Storage
Local storage → segment_list (ID/Name)
Key cookie
AAM_ABTASTY
Activation condition
Match between cookie value and segment_list
On match
"segment" hit sent to collection → audience available for targeting
Client responsibility
Adobe authentication + appending AAM_ABTASTY cookie
Refresh frequency of segment list
Only at tag compile/recompile — not real-time
Matching frequency
Every user session
Last updated
Was this helpful?

