> 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/viewing-the-campaign-report-page.md).

# Viewing the campaign report page

The campaign-level report provides key performance metrics for a single campaign. You can access it by clicking a campaign's name on either the Campaign Manager or the performance page.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FoAzfS4HeVVn0IgJQMncl%2FCleanShot%202025-09-23%20at%2010.58.36.png?alt=media&amp;token=c64ef3cb-950d-4aad-b5c0-9149f0c9df5c" alt=""><figcaption></figcaption></figure>

#### **How to View the Campaign Level Report:**

1. Navigate to the campaign management dashboard.
2. Filter to the campaign you want to view.
3. Click the campaign name.

It's that easy! Learn everything about the campaign report page in the clickable guided tour below:

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

Want to view more guided tours? Check out the [**Demo Hub**](https://epsilon.storylane.io/hub/demo-hub)**.**


---

# 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/viewing-the-campaign-report-page.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.
