> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/integrations/pull-integrations/adobe-audience-manager.md).

# 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.

{% hint style="info" %}
Unlike a classic daily-export integration, the Adobe pull integration combines a **periodic audience list refresh** (at tag compilation) with **real-time, per-session matching** via a cookie. See How it works below. 
{% endhint %}

### 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).

{% hint style="info" %}
 Exact steps and menu labels may vary depending on your Adobe contract and console version check with your Adobe admin or the Adobe documentation for the current path to generate credentials.
{% endhint %}

General steps:

1. Access your Adobe Developer Console / Audience Manager admin settings.
2. Create (or request) API credentials scoped to Audience Manager.
3. 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:

1. Access **Integrations > Integration Hub > Pull**.
2. Search for and select **Adobe** 
3. Click **Setup connector**.
4. Give a name to your connector so you can easily retrieve it.
5. Enter your Adobe API credentials + User credentials
6. 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_ABTASTY` cookie with the relevant segment ID/Name for the current visitor.

Without this step, the tag has no cookie value to match agains`segment_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](/assets-library/creating-and-managing-segments.md) under `3rd Party Audiences>Adobe`

{% hint style="info" %}
For an audience to be available in the segment builder, at least one user must have matched that audience via the cookie mechanism above. Empty audiences will not be displayed. 
{% endhint %}

### Technical Specifications

| Element                           | Detail                                                              |
| --------------------------------- | ------------------------------------------------------------------- |
| 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                                                  |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.abtasty.com/integrations/pull-integrations/adobe-audience-manager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.