> 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/integration-architecture.md).

# Integration Architecture

## Integration Components

**Required Components**

1. API Client – Fetches brand page content.
2. Content Renderer – Displays modules on your site. Handles modules and fields that may be missing or empty without throwing; falls back or hides UI blocks when optional creative data is absent.
3. Tracking Handler – Fires C2S and/or S2S tracking events. Page-level impression, click, and add-to-cart events use `trackingTemplates` together with the corresponding `trackers.<slot>.params` values. Video tracking events for `VIDEO_TILE` and `BACKGROUND_VIDEO` modules are returned as fully composed beacon URLs on the module and must not be generated from `trackingTemplates`. The request fields `trackingMode` and `clickTrackingMode` determine which tracking templates and tracker types are included in the response.
4. Reverse Proxy – Routes **browser (C2S)** tracking through your domain. A reverse proxy is required for C2S tracking, even when `trackingBaseUrl` is used and client URLs are returned as fully qualified URLs, because the requests still route through your proxy.

This section describes the high‑level runtime sequence for serving and tracking.

## Integration Flow

**Tracking Options (Choose One)**

| Method                     | When to Use                                                                                                                                                                                       |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **(Client-to-Server) C2S** | Standard web implementation: browser‑based impression pixels plus click redirects or event beacons (clicks and add-to-cart). This approach is strongly recommended by Epsilon for most retailers. |
| **(Server-to-Server) S2S** | Use when your architecture requires server‑side event firing, client‑side pixels are unreliable, or you want server‑side confirmation in addition to C2S.                                         |

{% hint style="info" %}
A reverse proxy is **required** for **C2S (browser)** tracking. Pass `trackingMode` and `clickTrackingMode` in the ad-serving request to receive only the tracking templates applicable to your implementation (see **Ad Serving API**).

**S2S** tracking requests must be sent **directly** to the Epsilon tracking host using URLs composed from `trackingTemplates.server` and the corresponding `trackers.<slot>.params` values. Do **not** route S2S requests through your reverse proxy or modify the host or path returned in the tracking template.

The `trackingBaseUrl` field applies only to C2S tracking URLs and does not modify or rewrite S2S tracking URLs.
{% endhint %}

<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/integration-architecture.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.
