> 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/order-data-1.md).
# Order data
Epsilon Retail Media requires order data to generate relevant ads. Syncing orders is also highly valuable for advertiser and retailer dashboards within the Epsilon Retail Media portal, as orders are used in sales, conversion, sale value and ROAS calculations. This data is extremely useful for advertising teams, as they can analyse investment effectiveness, and contribute additional spend in response.
Campaign screen image
## Syncing order data
Synchronising order data involves the retailer sending a customer's **`sessionId`** in the ad request, then in the order data sync with Epsilon Retail Media. With this information, Epsilon Retail Media is able to review the `adId`s provided for the `sessionId`'s ad requests and attribute accordingly within the configured attribution window.
If desired, the `sessionId` can be substituted with a long-term hashed customer identifier to attribute across sessions. To learn more, please speak to your Technical Account Manager.
#### Integration requirements
With this integration, you are required to send Epsilon Retail Media the customer's unique session identifier in the ad request and order confirmation, like the example below:
```json
{
"orders": [
{
"customerId": "npc-s243-ir",
"catalogId": "6adb93d0-7he4-4d4e-9b47-e5d3714c976a",
"sessionId": "5cat7-9964-4f",
"orderDate": "2021-12-02T15:00:00Z",
"id": "3h30e938-c158-4d78-a0af-b48bbwfrcss4",
"orderItems": [
{
"gtin": "9891998566P",
"quantity": 3,
"regularUnitPrice": "1.00",
"totalOrderItemPriceAfterDiscounts": "3.00"
}
]
}
]
}
```
{% hint style="info" %}
This `sessionId` must be the same as what is provided in the ad request sent to Epsilon Retail Media.
{% 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/data-api/order-data-1.md?ask=&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.
