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

# Data overview

In order to generate ads, Epsilon Retail Media needs to ingest product, customer, and order data from the retailer’s site. Once the data is populated by the retailer, it is stored, processed, and updated within the Epsilon Retail Media platform.

To automate the process of downloading and updating data, Epsilon Retail Media and the retailer agree on the format and structure of the data, as well as the protocol for communication between the retailer’s site and the Epsilon Retail Media platform.

This section describes the constraints on the feeding in of three types of data: product, customer, and order.

## Syncing options

You may want to sync your data via API or by syncing files, depending on your integration requirements. Epsilon Retail Media supports both types of syncing. For more information, please visit the relevant page below:

* [Catalog & Products](/retail-media-interface/integration/data-api/catalog-products-2.md)
* [Customer data (audience targeting)](/retail-media-interface/integration/data-api/customer-data.md)
* [Order data](/retail-media-interface/integration/data-api/order-data-1.md)

## Sync data via file or API?

The decision on how to sync data is ultimately up to the retailer, as both options have their benefits and drawbacks. Larger retailers often prefer to sync via file as it aligns better with resource capabilities and only requires files to be uploaded on a daily basis.

{% hint style="warning" %}
Epsilon Retail Media recommends syncing data via file, as it’s easier to troubleshoot and resolve. If retailer file issues occur, previous catalog files can be reinstated until the issue is fixed.
{% endhint %}

### Syncing data via API

**Pros:**

* Faster data ingestions and updates
* Self sufficient.

**Cons:**

* Data must be batched
* Higher difficulty in troubleshooting
* Cannot roll back to previous updates.

### Syncing data via File

**Pros:**

* Single file supported per data type supported, as opposed to batching
* Can be synced at preferred timing intervals (daily is recommended)
* Different protocol support (GCS, SFTP, SCP, HTTPS)
* Easier to navigate when troubleshooting
* Can roll back to previous files.

**Cons:**

* Data is updated once ingested
* Delta updates are not supported.

### Syncing data via file protocols

When syncing data via file, additional protocols and practices need to be adhered to.

Please visit the [Syncing data via file protocols](/retail-media-interface/integration/data-api/data-overview-1/syncing-data-via-file-protocols-1.md) page for more information.

{% hint style="info" %}
AWS S3: no longer supported

Unfortunately, Epsilon Retail Media no longer supports synchronising files via AWS. Please contact your Technical Account Manager to discuss if you need assistance using GCS.
{% 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/data-overview-1.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.