> 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/brand-page-creation-and-editing/managing-brand-pages.md).
# Managing Brand Pages
Once a Brand Page has been created and submitted, it goes through an approval process before going live on the retailer's website. This section covers the approval workflow, scheduling, and how to manage pages after they're published.
### The approval and review process
Brand Pages follow a review workflow to ensure content quality before going live. Your retailer will review your Brand Page and either approve it - where it can then go live, or reject it and submit a rejection reason.
#### Status lifecycle
You can see your Brand Page's status directly in the Brand Page Campaign Manager:
| Status | What it means |
| ------------- | ------------------------------------------------------------------------------------------------ |
| **Draft** | The page is being created or edited. It is not visible to shoppers. |
| **Submitted** | The page has been submitted for review and is awaiting approval. |
| **Approved** | The page has passed review and will go live according to its scheduled dates. |
| **Rejected** | The page did not pass review. Feedback is provided so you can make corrections and resubmit. |
| **Live** | The page is active and visible to shoppers on the retailer's website. |
| **Inactive** | The page has been paused or its scheduled dates have ended. It is no longer visible to shoppers. |
| **Archived** | The page has been archived and is no longer active. |
#### What happens during review
When a Brand Page is submitted, it enters the review queue. Reviewers check the page content, product selections, and overall quality. If the page meets the requirements, it is approved. If changes are needed, the page is rejected with feedback explaining what to correct.
{% hint style="info" %}
**Tip:** Review timelines may vary. If your page is time-sensitive, submit it well in advance of your planned launch date.
{% endhint %}
#### Resubmitting a rejected page
1. Open the rejected Brand Page.
2. Review the rejection feedback.
3. Make the requested changes.
4. Submit the page again for review.
### Scheduling
Each Brand Page has scheduling controls that determine when it is visible to shoppers.
* **Start date** — The date and time the Brand Page becomes visible to shoppers (once approved).
* **End date** — The date and time the Brand Page stops being visible.
* **Always-on** — If enabled, the page runs indefinitely with no end date.
{% hint style="warning" %}
**Warning:** A Brand Page will not go live until it has been both **approved** and its **start date** has been reached. If the start date has already passed when the page is approved, it will go live immediately.
{% endhint %}
### What happens when a page is live
When a Brand Page is live:
* **Shoppers can visit the page** at its URL on the retailer's website.
* **Content is served dynamically** — the page content and product details are resolved each time a shopper loads the page, so product information stays current with the catalogue.
* **Performance is tracked** — impressions, clicks, and other interactions are recorded and available in the Brand Page Performance tab.
### Making changes to a live page
You can edit a Brand Page after it has been published. Depending on the change, the updated page may need to go through the review process again before the changes go live.
Begin editing the campaign by clicking the chevron, then clicking **Edit.**
{% hint style="warning" %}
**Warning:** Significant content changes (such as swapping products or changing the theme) typically require re-approval. Minor metadata updates may not.
{% endhint %}
### Pausing or archiving a Brand Page
* **Pause** — Set the page to **Inactive** to temporarily remove it from the live site. The page content is preserved and can be reactivated later.
* **Archive** — Archive a Brand Page when it is no longer needed. Archived pages are removed from the active list but remain accessible for reference.
---
# 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/brand-page-creation-and-editing/managing-brand-pages.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.
