> 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/partner/campaign-management-api/bannerxcontentstandard.md).

# Content standard

Content standards are guidelines and technical parameters that dictate how a banner or banner X ad should be displayed within a designated space on a website or digital platform. These standards may include:

* **Dimensions and size**: Specifications on the exact width and height of the banner.
* **File format**: Accepted image or video file formats, such as JPEG, JPG, PNG, SVG, or GIF.
* **File size limit**: Maximum allowable file size to ensure quick loading times and optimal performance on the webpage.
* **Resolution and quality**: Minimum resolution requirements to ensure the banner looks crisp and professional.
* **Positioning and alignment**: Guidelines on how the banner should be aligned within the available space.
* **Content restrictions**: Rules on what content can or cannot be included within the banner (e.g., no offensive content, inclusion of mandatory legal disclaimers).
* **Interactivity**: Specifications for interactive elements, such as clickable areas, animations, or user-triggered events, if applicable.

Familiarize yourself with the retailer’s content standards guidelines to start your campaign. These guidelines include example URLs, page positioning, and specific artwork content restrictions. Consult your Customer Integration Engineer (CIE) for detailed information about available banner slots and their specifications. Here is an example:

<figure><img src="https://110176934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyPijakfWdNW5OjxjMGoY%2Fuploads%2Fgit-blob-403fef0456c33f3ea159f3db199cec161f5f7ab0%2FScreenshot_2025-02-06_141125.png?alt=media" alt="" width="100%"><figcaption></figcaption></figure>


---

# 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/partner/campaign-management-api/bannerxcontentstandard.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.