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

# Anuncios de productos

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

Product Ads are usually the easiest for retailers to integrate and request due to their ease of integration. The information in this guide assumes you've already created your catalog and products, and are sending customer and order data to Epsilon Retail Media.

{% hint style="success" %}
If you're syncing data correctly, you're ready to request Product Ads.
{% endhint %}

## Supported Placement Types

Through Epsilon Retail Mediaplacement capability, we can support more placements than are outlined in this documentation. The following can be used as starting ideas.

### Search

Use Search placements to render ads where your customers have entered a keyword search on your site. A simple example of this is asking Epsilon Retail Media for ads about "t-shirts".

<figure><img src="/files/XLUiM653fKGcWVLRX2HU" 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` from your taxonomy, such as "Category:Pantry/Snacks"

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

### Broad Match (Homepage, Deals, Checkout etc)

Broad Match placements can be used for any other placement, such as Homepages, Deals, Checkout etc.

#### Homepage

Your Homepage can be a simple request for just the placement identifier and any `productFilters` in your request.

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

#### Deals/Sales

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

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

#### Checkout

Your Homepage can be a simple request for just the placement identifier and any `productFilters` in your request.

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

## Multiple Placements on One Page

If you want to make the most of your ecommerce site, you can make multiple unique requests on the same page. In Epsilon Retail Media you can split these out based on your requirements, such as "Search In Grid" and "Search Below Grid".

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

This enables you to gain extra revenue per page view by increasing ad saturation per page, as well as the ability to have different targeting strategies per placement. You can have a strict search term match on your "In Grid" placement, and a looser category ID-based match 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/es/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.