> 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/campaign-creation-and-editing/targeting.md).

# Targeting

The targeting stage is where you select specific targeting configurations, including your campaign's placement. The new platform has streamlined targeting into a single stage and automatically adjusts settings based on your selected placement and the targeting enabled by your retailer.

## Steps to configure

{% stepper %}
{% step %}

### **Select placement**

* The wizard will update based on what you choose and the features available for your retailer
* When setting up a campaign across multiple retailer catalogs, you’ll only see the placements that are shared by each of those retailers.
* Cannot be changed once your campaign is launched.
  {% endstep %}

{% step %}

### **Configure placement specific targeting.**

* Broad targeted placements such as the homepage or checkout page won't show specific targeting criteria. You can move forward after picking your placement.
* Some category placements may allow category targeting subject to retailer activation.
* Keyword placements will show keyword targeting with a new and improved UI.
* Some retailers might show specific **location or audience targeting** based on your chosen placement, depending on how they’re set up.
  {% endstep %}
  {% endstepper %}

{% hint style="warning" %}
The targeting stage is key to your campaign's success. We recommend clicking through the guided tour below, which covers each targeting configuration in detail.
{% endhint %}

{% embed url="<https://epsilon.storylane.io/share/8cctt6oga09v>?" fullWidth="true" %}

Click the **Targeting Stage Tours** button in the bottom left to select the specific targeting criteria available on your campaign.

Take the full wizard tour by following the prompts, or check out the [**Demo Hub**](https://epsilon.storylane.io/hub/demo-hub)**.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.citrusad.com/retail-media-interface/campaign-creation-and-editing/targeting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
