> 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/frequently-asked-questions-faqs.md).

# Frequently Asked Questions (FAQs)

<details>

<summary><strong>Q: Are changes I make instantly reflected in the legacy platform? Are they connected?</strong></summary>

A: Yes! The New UI and legacy UI use the same APIs for campaign management and wallet management. Every change you make in the New UI will be reflected in the legacy UI.

{% hint style="info" %}
If you are working between the UIs, refresh the tab when you switch between them. Both UIs fetch new campaigns on refresh, which ensures your changes are synchronized effectively.
{% endhint %}

</details>

<details>

<summary><strong>Q: Why can I see minor reporting variances between the New UI and the legacy UI?</strong></summary>

A: You shouldn't see variances between the key legacy and new UI reports.

We recommend reading [Understanding reporting data delays and time zones in the new interface](/retail-media-interface/advertiser-reporting/understanding-reporting-data-delays-and-time-zones-in-the-new-interface.md) to familiarize yourself with the New UI.

</details>

<details>

<summary><strong>Q: Why are certain features only shown on certain retailers?</strong></summary>

A: Much like the legacy platform, certain features may be enabled based on a retailer's integration or regional or language availability. If you would like to see a specific feature enabled for a retailer, we recommend raising it with your retailer.

</details>


---

# 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/frequently-asked-questions-faqs.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.