> 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/integration/brand-pages/brand-page-retailer-integration-guide/prerequisites.md).

# Prerequisites

Before beginning the Brand Pages integration, ensure the following requirements are in place:

## Required Setup

* Existing Epsilon RMN Platform Access: You must have an active Epsilon RMN account with platform access.
* Catalog ID: Identifier for the retailer’s existing product catalog, provided by Epsilon as part of the RMN onboarding process and reused for Brand Pages.
* URL Configuration: The full brand page base URL is configured during onboarding and stored in the Retailer Style Guide (e.g., `https://retailer.com/brands/`).
* Reverse Proxy Infrastructure: Capability to set up reverse proxy for seamless integration, including the Epsilon-assigned tracking hostname (`https://[region]-tracking.rmn.dotomi.com/`) for routing browser tracking requests.
* HTTPS/TLS 1.2+ Support: Required for secure communication and tracking.
* Style Guide Information: Brand colors, fonts, and styling requirements collected during onboarding.
* Template Creation: Completed during onboarding process with Epsilon team.

## Before You Start Checklist

* [ ] Epsilon RMN platform access confirmed.
* [ ] Catalog ID received from Epsilon.
* [ ] Brand page URL structure agreed upon.
* [ ] Reverse proxy capability verified.
* [ ] HTTPS/TLS 1.2+ infrastructure in place.
* [ ] Tracking hostname received from Epsilon.
* [ ] Style guide information provided to Epsilon.
* [ ] Brand page templates created and approved.

<br>


---

# 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/integration/brand-pages/brand-page-retailer-integration-guide/prerequisites.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.
