> 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/navigating-the-on-site-campaign-manager.md).

# Navigating the on-site campaign manager

Campaign management has been streamlined in the new interface, with key functions enhanced for improved usability. Here's what's new:

* All campaigns across all statuses for your selected ad type are now shown. Use the **Campaign Status** filter to narrow your view.
  * Use additional filters like **Campaign Name**, **Wallet**, and **Status** under **More Filters** to refine your results.
* See live performance metrics directly in the table, including **Impressions**, **Clicks**, **ROAS**, **CTR**, and **CPC** (last 24 hours).
* Select multiple campaigns to perform **bulk actions,** including **bulk pause/activate, change end dates, set dayparting, and remove keywords/products.**.
* Click a campaign row to open the **quick view** for fast edits.
* Click a campaign name to open its **report page**.
* Click the **vertical ellipsis** on a campaign row to **edit**, **duplicate**, **pause**, or **archive** the campaign.

Take a guided tour below to see everything that's new in the campaign manager.

{% embed url="<https://epsilon.storylane.io/share/wvtgembldx8o>" fullWidth="true" %}

Want to make a quick edit? Take a look at [Broken mention](broken://pages/j5zjzX3nYb8hKpcJZctI)


---

# 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/campaign-management/navigating-the-on-site-campaign-manager.md?ask=<question>&goal=<user_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.
