> 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/campaign-management/campaign-change-history.md).
# Campaign change history
See who changed a campaign, when they changed it, and what was updated — all from a single tab on the campaign details page.
***
### How to access change history
The campaign history tab is a tab available on the onsite campaign details page. You can access it by **clicking a campaign name**, and then navigating to the tab.
You can access the page from:
* The onsite campaign manager as a retailer or supplier
* The onsite performance dashboard as a retailer or supplier
* The bulk edit tool (SPA campaigns only)
* The retailer review page
Once you navigate to the onsite campaign details page, you have to click the change history tab.
You need **Campaign** edit permission to view change history.
{% hint style="info" %}
Don't see the tab? You may not have the right permission. Retailer users who are not on the primary retailer team will not see this tab.
{% endhint %}
***
### Review changes in the table
The change history table lists every recorded update to the campaign, newest first.
| Column | What it shows |
| ------------------ | ------------------------------------------------------- |
| **Date / time** | When the change occurred (in your retailer's time-zone) |
| **User** | Who made the change |
| **Action type** | What kind of update it was (see below) |
| **Change summary** | A brief description of what changed |
#### Action types
| Action type | Meaning |
| ------------- | --------------------------------------- |
| **Created** | The campaign was first created |
| **Draft** | A draft version was saved |
| **Submitted** | The campaign was submitted for approval |
| **Approved** | A retailer approved the campaign |
| **Rejected** | A retailer rejected the campaign |
| **Activated** | The campaign was turned on |
| **Paused** | The campaign was paused |
| **Archived** | The campaign was archived |
| **Edited** | Campaign settings were updated |
{% hint style="info" %}
If you are a supplier, approve and reject actions may show **Retailer team** instead of an individual name.
{% endhint %}
***
### Types of changes we track
Change history records both **status changes** (like approvals and pauses) and **setting changes** (like dates, products, or targeting). Every recorded update appears in the table's **Change summary** column. Some changes also include field-level **before** and **after** values in the detail drawer.
#### Status and workflow changes
These appear as action types in the table. When a status change also updated campaign settings at the same time, the summary includes both (for example, **Approved** plus the fields that changed).
| What changed | How it appears |
| ---------------------------------------- | ------------------------------------------ |
| Campaign created or submitted | **Created** or **Submitted** |
| Draft saved | **Draft** |
| Retailer approved or rejected | **Approved** or **Rejected** |
| Campaign turned on, paused, or archived | **Activated**, **Paused**, or **Archived** |
| Settings updated without a status change | **Edited** |
Rejection reasons are shown in the detail drawer when a campaign is rejected.
#### Campaign settings in the change summary
The table summarizes changes across these campaign areas. Wording varies by change type — for example, "Products updated" or "3 products added."
| Area | Settings tracked in the summary |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Campaign setup** | Name, start date, end date, wallet |
| **Products** | Products, product groups, catalogs |
| **Targeting** | Placement, keywords, negative keywords, audience segments, categories, cross-sell and upsell targeting, product attributes, custom questions |
| **Strategy** | Bidding strategy, custom fields, fixed costs |
| **Creative** | Banner setup, BannerX setup |
| **Brand page** | Brand page configuration |
#### Field-level details in the drawer
When you open **Change details**, before and after values are available today for:
| Area | Fields with before / after values |
| ------------------ | ---------------------------------- |
| **Campaign setup** | Name, start date, end date, wallet |
| **Products** | Products, product groups, catalogs |
For other areas listed above, the table still notes that something changed, but the drawer shows a message that detailed before/after values for that area are not yet available. Any supported fields from the same change are still shown.
{% hint style="info" %}
**COMING SOON**
Field level support is expanding over time. If you see a note that an area is not yet supported, check back after future releases.
{% endhint %}
***
### Filter and customize the table
Use the filter bar above the table to narrow what you see:
1. **Action type** — Show only certain types of changes (for example, **Edited** or **Approved**).
2. **User** — Show changes made by a specific person.
3. **Date range** — Limit results to a calendar date range.
You can also customize which columns appear using **Customize history table**.
***
### View change details
Click a row to open the **Change details** drawer on the right. The drawer shows:
* When the change happened and who made it
* A **Rejection reason** (when a campaign was rejected)
* Field-level **before** and **after** values for supported campaign areas
Click the same row again, or close the drawer, to return to the full table.
{% hint style="info" %}
Detail views are not yet available for every type of campaign change. If part of a change is unsupported, the drawer shows a note and still displays any supported fields.
{% endhint %}
***
### Tips for success
* **Start with filters** — Use action type and date range to find approval events or recent edits quickly.
* **Check rejections in the drawer** — Rejected campaigns include the retailer's reason directly in the detail view.
* **Use sort columns** — Click column headers to sort the table (for example, by user or action type).
* **Refresh after edits** — If you just saved a change elsewhere and don't see it yet, reload the page or revisit the tab.
***
### Troubleshooting & support
| Issue | What to try |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Change history tab is missing** | Confirm you have campaign edit permission. |
| **No rows appear** | The campaign may not have any recorded changes yet, or your filters may be too narrow. Reset filters and try again. |
| **User shows as Unknown** | The person who made the change may no longer be on the team, or their account could not be matched. |
| **Drawer won't open for a row** | Some rows (for example, status-only updates with no field details) don't have expandable details. |
| **Recent edit not listed** | Reload the page. If it still doesn't appear, contact support — the change may still be processing. |
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/campaign-management/campaign-change-history.md?ask=&goal=
```
`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.
