> 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/references/banner-ad-static-reference.md).
# Banner ad (static) reference
The below outlines the properties possible in a standard request as outlined in [Requesting banner ads](/retail-media-interface/integration/generating-ads/banner-ads-static/requesting-banner-ads.md) for your request, and the response if you receive an ad.
{% hint style="info" %}
Banner ads are requested on the same `/generate` endpoint as product ads. A single request can be used to retrieve both ad types.
{% endhint %}
## Requested items
| String | Description | Required/optional |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| `bannerSlots` | An array of banner slots that you wish to receive banner ads for. By specifying a maxNumberOfAds for the banner slots, you can retrieve more than one banner for the slot. Such a use case would be for carousel placements. | Required |
| `bannerSlotIds` | An array of banner slots that you wish to receive banner ads for | Required, superseded by bannerSlots |
| `catalogId` | Your product catalog identifier for your website. | Required |
| `contentStandardId` | The content standard identifier for your website. | Required |
| `customerId` | The unique identifier for the customer being served ads. | Optional |
| `filterMode` | Optional way of defining the structure of your request. See [Ad generation filtering](/retail-media-interface/integration/data-api/api-overview/ad-generation-filtering-1.md) for more information. | Optional, preferred |
| `maxNumberOfAds` | The maximum number of product ads you would like returned up to 15. | Required, enables product ads to be served in the same request. If no product ads are wanted, set to `0` |
| `options` | Optional way of defining the structure of your request. See Ad generation filtering for more information.
This is also the object where you can request advertiser information in order to comply with local advertising legislation like Europe’s Digital Services Act .
| Optional, preferred |
| `placement` | The unique placement you are requesting ads for. | Required |
| `productFilters` | Any product filters relevant to your request. Such as a category, location, or size. | Required |
| `sessionId` | The unique identifier of the customer's session. Used for attribution in standard integrations. Review Integration workflow options for more information. | Required in standard integrations |
| `dtmCookieId` | Cookies created and stored by the website, used for tracking user behavior on the same domain. | Optional |
| `audience` | Specifies specific audience segments that the shopper belongs to. Only relevant is using [Audience Targeting Option 3](/retail-media-interface/integration/data-api/audience-targeting-new/integration-option-3-sync-audiences-only.md) | Optional |
## Returned items
| String | Description | Example value |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `banners.altText` | Alternative text for the hero image in the rare event it doesn't display. | `Advertisement for <BRAND>. Art of the Burger. Create your delicious masterpiece. Shop Now.` |
| `banners.contentStandardId` | The content standard identifier for your website. | \`4ffb80ba-b9a9-4567-8069-79b2eca93473 |
| `banners.expiry` | The expiry of the ad. This is the latest point in which a click can be reported to Epsilon Retail Media | `2021-06-01T23:48:16.573967987Z` |
| `banners.id` | The unique id of the ad.
This is unique to each request made to Epsilon Retail Media and cannot be cached.
| `banner_j2vfi9pN2BiQZk4X9sC55PgNu5k3ODIzOTlfMDAwODc2ODQwMDEwNzM=` |
| `banners.imageUrl` | The image link of the banner. | `[]\() |
| `banners.gtins` | An array of up to 20 product codes selected from the campaign's advertised products. | `[
"7714107",
"7163379",
"7733636",
"7733657",
"7733628"
],` |
| `banners.linkUrl` | The url forwarded from the banner when the customer clicks the banner. | ` |
| `banners.slotId` | The id of the specific slot for the banner you have requested. | `Category_Top` |
| `banners.tags` | This field returns any third party tags entered by the advertiser in their campaign. | `{
"dv": "<script src=\"" type=\"text/javascript\"></script>"
}` |
| `banners.text` | Used in bespoke integrations as an additional text field. | |
| `banners.position` | The ad's position in the Epsilon Retail Media response. You should honour this position in the event fixed tenancy campaigns are utilised. | 1 |
| `banners.sellerId` | The unique Id of the seller. Will only populate if a sellerId is set on a team. sellerIds are typically used when onboarding marketplace sellers. | `73nns-32sxr-32ss` Custom per integration |
| `banners.metadata` | Object containing the advertiser info required to help advertisers comply with local advertising legislation such as the Digital Services Act in Europe.
advertiser is carried from the Company name in the supplier team.
onBehalfOf is carried from the Ad financer in the supplier team.
| `"metadata": {
"advertiserInfo": {
"advertiser": "Bob's advertising agency",
"onBehalfOf": "Brand company inc"
}
...` |
| `metadata.warnings` | Object containing warning information about the ad request. Currently only warns if the maximum number of segments is exceeded. | `"metadata": {
"warnings": [
"Audience Segment IDs exceeded the limit of 100 and were truncated"
]
}` |
---
# 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/references/banner-ad-static-reference.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.