> 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/order-data-1.md).

# Order data

{% 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/order-data-1) in the new Integration APIs space of our documentation.
{% endhint %}

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.

<figure><img src="https://3425731255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBL8KNnR5myWfc4R7Zbbq%2Fuploads%2Fgit-blob-feed98417f746f7a2782c95dd0a19d40ee906e4c%2FReporting.png?alt=media" alt="Reporting.png" width="100%"><figcaption><p>Campaign screen image</p></figcaption></figure>

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

<figure><img src="https://3425731255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBL8KNnR5myWfc4R7Zbbq%2Fuploads%2Fgit-blob-5823a030d36bc37aeaaef37ffda7ad867c3daad7%2FGroup_95.png?alt=media" alt="Group 95.png" width="100%"><figcaption></figcaption></figure>

#### 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 %}