> 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/generating-ads/banner-ads-static/banner-content-standard-1.md).

# Banner content standard

Your content standard is a PDF document that is displayed to your advertisers within the Epsilon Retail Media platform when selecting a banner slot. The purpose of this PDF is to inform your users of any retailer-specific specifications that must be adhered to.

When they reach the content standard stage, the advertiser will select the applicable content standard and has the option to view the PDF. It is rare to need multiple content standard documents.

<figure><img src="/files/iQveWw3PH9dKvsCShggm" alt="Banner Content Standard.png" width="100%"><figcaption></figcaption></figure>

Within this document, you should outline any business and/or rendering-specific rules the advertiser should be made aware of when generating their creative files for upload. Additionally, it is beneficial to display to advertisers the pages on which their ads will render.

<figure><img src="/files/GmL3dTnh0Hz52lGvGpxs" alt="Banner Content Standard Screen.png" 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 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/integration/generating-ads/banner-ads-static/banner-content-standard-1.md?ask=<question>&goal=<endgoal>
```

`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.