> 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/retailer-reporting/history-reporting.md).

# History reporting

View delivery history and performance metrics for campaigns across your retail media network.

***

### How to access the History Report

Navigate to **Reports → History** in the left sidebar.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FTxvJbhlNhRjCztGzJM0P%2FCleanShot%202026-03-23%20at%2015.57.571.png?alt=media&amp;token=f57ae462-c732-44d2-89ac-311762b02566" alt=""><figcaption></figcaption></figure>

## Viewing supplier campaign history

The History Report lets you view performance data for all suppliers within your network. Use the filters to customize your view:

* **Select a catalog:** Choose the catalog to view campaign data for
* **Select supplier team(s):** Choose which supplier team(s) to view data for
* **Search by campaign name:** Enter text to filter results to a specific campaign
* **Choose a campaign type:** Filter by Product Ad, Banner, or Banner X.
* **Set your date range:** Select start and end dates for the report
* **Group by time period:0**
  * **Day**
  * **Week**&#x20;
  * **Month**&#x20;
  * **Hour** (Available for date ranges of 7 days or less)
* **Filter by wallet**: Narrow results to campaigns using a specific wallet

### Understanding the report data

To understand all KPIs, we recommend to view the [Reporting reference](/retail-media-interface/advertiser-reporting/reporting-reference.md).

### Exporting your data

To download your history data as a CSV file:

1. Configure your filters to show the data you want
2. Click the **Export** button in the top-right of the table section
3. Your browser will download a CSV file with all visible data

{% hint style="warning" %}
Large exports may take a moment to generate. The button will show a loading indicator while processing.
{% endhint %}

***

### Tips for success

* **Monitor supplier performance** — Use the team filter to review individual supplier trends over time
* **Compare suppliers** — Run reports for different suppliers to identify top performers
* **Use date grouping strategically** — Daily data is best for recent analysis; weekly or monthly grouping works better for longer-term trends
* **Export for deeper analysis** — Download data to spreadsheets for custom reporting and comparisons

***

### Troubleshooting & support

| Issue                                      | Resolution                                                    |
| ------------------------------------------ | ------------------------------------------------------------- |
| "History reports aren't available" message | Contact your Epsilon representative to enable this feature    |
| Team filter not showing                    | Ensure you're logged in as a retailer team user               |
| No suppliers in team dropdown              | Verify suppliers exist in your network                        |
| No data for selected supplier              | Confirm the supplier has campaigns in the selected date range |

For help, contact your Epsilon Retail Media representative or use the Support tab within the platform.


---

# 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/retailer-reporting/history-reporting.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.