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

# Option 1: Curated Unified Audiences

{% hint style="info" %}
Epsilon Retail Media's documentation is now centralized with our knowledgebase!

For up to date guides, please view [this page](https://help.citrusad.com/retail-media-interface/integration/data-api/audience-targeting-new/option-1-curated-unified-audiences) in the new Integration APIs space of our documentation.
{% endhint %}

### 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="https://3425731255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBL8KNnR5myWfc4R7Zbbq%2Fuploads%2Fgit-blob-aec2231f5a7274dd31aaa75d08a4b48970871300%2FScreenshot_2025-10-28_153838.png?alt=media" 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 %}