> 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/references/audience-targeting-reference.md).

# Audience targeting reference

The below outlines the properties required for syncing customer and segment data as part of Customer Data Sync for Audience Targeting. These tables define the structure for Segment Feed and Customer Feed, which ensure accurate mapping of segments to customers for targeted ad delivery.

### Segment Feed (Required when syncing your own segments)

| Field         | Description                                                                       | Required/Optional | Type       | Example                                                                               |
| ------------- | --------------------------------------------------------------------------------- | ----------------- | ---------- | ------------------------------------------------------------------------------------- |
| `segment_id`  | Unique segment ID in your system. Must match customer feed or ad request.         | Required          | Text       | `custom-segment-1`                                                                    |
| `name`        | Name of the feed, shown when selecting segments.                                  | Required          | Text       | `High Spending Shoppers - Cola Co`                                                    |
| `description` | Shown when selecting segments. Recommended to be under 20 words.                  | Required          | Text       | `Shoppers with an average weekly shop in the top 15% that purchase Cola Co products.` |
| `category`    | Optional category tag for future UI filtering.                                    | Optional          | JSON array | `Custom segmentation`                                                                 |
| `team_ids`    | Restricts segment access to specified teams. Other teams can't view or select it. | Optional          | JSON array | `["a5166cf4-87f4-4741-a721-c05ffd9941a5"]`                                            |

{% hint style="info" %}
Are you syncing from multiple segment sources?

Ensure to work with Epsilon as we'll need to confirm the source ID referenced in the ad request if using [audience targeting option 3](/retail-media-interface/integration/data-api/audience-targeting-new/integration-option-3-sync-audiences-only.md)
{% endhint %}

### Customer Feed (Required when syncing your own segments and customers)

| Column              | Required  | Type       | Description                                                                              | Example                     |
| ------------------- | --------- | ---------- | ---------------------------------------------------------------------------------------- | --------------------------- |
| `customer_id`       | Required  | Text       | Identifier of the customer in the retailer's system. Must be consistent with ad request. | `oo32s-a432-dsf4380`        |
| `segments`          | Required  | JSON array | Segment IDs linked to the customer. Must align with the segment feed.                    | `["segment-1","segment-2"]` |
| `source_identifier` | Read-only | Text       | Internal system reference. Cannot be modified by retailers.                              | system-generated            |

{% hint style="info" %}
`source_identifier` is read-only and automatically generated by the system. Do not include or modify this field in your upload file.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.citrusad.com/retail-media-interface/integration/references/audience-targeting-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.