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