> 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/advertiser-reporting/on-site-performance-reporting.md).

# On-site performance reporting

The performance dashboard is the first page you'll see when logging in. Use it to understand your team's overall performance, now improved with enhanced metrics such as **brand halo** and **in-store attribution**.

Learn everything about the performance dashboard in the clickable guided tour below:

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

## Key Information

* Quick-look **KPIs** give you an overview of overall team performance.
* **Filter** by campaign, type, and date. For more insights, click "**More Filters**" to narrow it down by catalog, placement, and wallet.
* The **Performance Over Time** chart clearly displays impressions, clicks, and conversions. Click a metric to show or hide it.
* The **All Campaigns** table shows all your KPIs across campaigns. Scroll to the right to see more. You can also export the data for deeper analysis.
* **Enhanced Metrics** highlight your online brand halo performance and in-store attribution (when available by retailer).
* Click on any campaign name to dive deeper into reports for that specific campaign.


---

# 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/advertiser-reporting/on-site-performance-reporting.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.
