> 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/campaign-set-up.md).

# Campaign set-up

The campaign set-up section is the first stage of the campaign wizard.

## Steps to configure

{% stepper %}
{% step %}

### **Campaign ad type (Product Ad, Banner, BannerX).**

* Only ad types available on your selected retailer are shown. If your retailer only offers one ad type, this is auto-selected and hidden for you.
* You won't be able to change this once the campaign is submitted.
  {% endstep %}

{% step %}

### **Campaign name**

* It can describe the campaign and represent the product(s) or your strategy. You'll see this name in the campaign manager and reporting pages.
* Some retailers may require a specific structure for your campaign name.
  {% endstep %}

{% step %}

### **Campaign start date and end date (or always-on status)**

* Your campaign can be **Always On,** or have a set flight date.
* New campaigns default to Always On, starting the day you create them.

  To set an end date, **deselect Always On** and enter the end date.
  {% endstep %}

{% step %}

### **Select the wallet your campaign will draw funds from**

* Only active wallets are shown.
* For multi-currency retailers, only catalogs matching the wallet's currency will be shown in the next stage.
* When editing campaigns, wallets can only be changed within the same currency.
  {% endstep %}
  {% endstepper %}

Take the guided tour below for a step-by-step walk-through:

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

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 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/campaign-creation-and-editing/campaign-set-up.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.