> 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/product-ads.md).

# Product ads

<figure><img src="/files/fX1ldsTf0LEV9AoDbB28" alt="Product Ad.png" width="100%"><figcaption></figcaption></figure>

Product ads are typically the easiest to integrate and request for retailers due to the ease of integration. This guide's information assumes you have already created your catalog and products, and that you’re sending customer and order data to Epsilon Retail Media.

{% hint style="success" %}
If you are successfully syncing data, you are ready to request product 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 "tops".

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

### Category

You should use category placements for your category aisles by sending Epsilon Retail Media a simple context of `productFilters` of your taxonomy such as "Category:Cupboard/Snacks"

<figure><img src="/files/iZ2Rj012jTWo5rwsfdXv" alt="Category.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/oiRqtU5NVHxmbKoZ0cX8" alt="Homepage.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/ga0rxwP7dleFI0TS13d8" alt="Sale.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/odjJVhfpvHB9eVSX5QUP" alt="Checkout.jpg" width="100%"><figcaption></figcaption></figure>

## Multiple placements in a page

If you're looking to get the most out of your ecommerce site, you're able to make multiple unique requests on the same page. In Epsilon Retail Media you're able to split these out by your requirements such as "Search In Grid" and "Search Below Grid".

<figure><img src="/files/Qz8nKAtWJVmy1HDOhYLo" alt="Multi Placement Page.jpg" width="100%"><figcaption></figcaption></figure>

This empowers you to gain additional revenue per page view by increasing ad saturation per page, as well as the ability to have different targeting strategies per placement. You are able to have strict search term matching on your "In Grid" placement, and a looser, category ID based matching on your "Below Grid" placement.


---

# 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/product-ads.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.