> 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.md).

# Banner ads (static)

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

Banner ads require a simple **`bannerSlotId`** array sent to Epsilon Retail Media in addition to the context of the page. By receiving the context of the page, Epsilon Retail Media ensures relevant banners are shown to your customers.

{% hint style="success" %}
If you are successfully syncing data, you are ready to request banner ads.
{% endhint %}

## Supported placement types

Through Epsilon Retail Media's placement capability, we're able to support more placements than outlined in this documentation. The below can be used as thought starters.

### Search

Use search placements to show ads where your customers have entered a keyword search on your site. A simple example of this is asking Epsilon Retail Media for ads on "chocolate".

<figure><img src="/files/dukOiW2ZMMLTibhHEdlf" alt="Search Banner.jpg" width="100%"><figcaption></figcaption></figure>

### Category

Use category placements for your category aisles. Send Epsilon Retail Media a simple context of `productFilters` of your taxonomy such as "Category:Cupboard/Snacks"

<figure><img src="/files/2Z8dgfZqbgka1gOsvupA" alt="Category Banner.jpg" width="100%"><figcaption></figcaption></figure>

### Broad match (home page, specials, checkout, etc)

Broad match placements can be used for any other placement such as home pages, specials, checkout, etc.

#### Home page

Your home page can be a simple request of only the placement identifier and any relevant `productFilters` in your request.

<figure><img src="/files/1ZWMtwsRWuaeKiMHnb21" alt="Homepage Banner.png" width="100%"><figcaption></figcaption></figure>

#### Specials/sale

If you are synchronising in the product catalog which products are on sale via a consistent filter value, you are able to send any relevant `productFilters` in your request to filter ads accordingly to the placement's business rule such as "type:On-Special","type:New", etc.

<figure><img src="/files/iuJ95OA4MMlglSYQnxum" alt="Sale Banner.jpg" width="100%"><figcaption></figcaption></figure>

#### Checkout

Your home page can be a simple request of only the placement identifier and any relevant `productFilters` in your request.

<figure><img src="/files/BwUm705K5mXRWFspK7TL" alt="Checkout Banner.jpg" 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.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.