> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/integration/data-api/audience-targeting-new/option-1-curated-unified-audiences.md).

# Option 1: Curated Unified Audiences

### Overview

Unified audiences enable consistent targeting across both onsite and offsite marketing channels. For retailers with existing Epsilon offsite integration, no additional setup is required. This approach utilizes Epsilon's curated audience segments, which are periodically synchronized between onsite and offsite systems to support unified campaign activation.

### Integration Requirements

* Offsite integration must be complete and must include customer ID across all relevant data integration points.

{% hint style="info" %}
A complete on and offsite integration is all that's required.
{% endhint %}

### How It Works

Customer IDs included in ad requests are matched to audience segments and associated campaigns. Audience segments created for offsite campaigns are periodically synchronized with the onsite system, enabling consistent targeting across channels.

<figure><img src="/files/CnPGKTYr42x0KvX6Wtjk" alt="" width="100%"><figcaption></figcaption></figure>

### Integration Examples

**Ad Request Example**: Ad request containing customer ID:

```http
POST $BASE_URL/v1/ads/generate HTTP/1.1
accept: application/json
content-type: application/json
Authorization: Basic <API_KEY>
{
    "customerId": "wertg5432a",
    "sessionId": "ec9-4e07-881d-3e9",
    "dtmCookieId": "AAAF8xLBTA968AB6TOthAAAAAAE",
    "placement": "search",
    "catalogId": "628dbe95-2ec9-4e07-881d-3e9f92ab2e0b",
    "searchTerm": "chocolate",
    "options": {
        "filterMode": "AndOr"
    },
    "maxNumberOfAds": 3
}
```

{% hint style="info" %}
As an offsite integrated customer, we have all we need.
{% endhint %}


---

# 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://help.citrusad.com/retail-media-interface/integration/data-api/audience-targeting-new/option-1-curated-unified-audiences.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.