> For the complete documentation index, see [llms.txt](https://docs.helix.voodoo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helix.voodoo.io/user-acquisition/create-campaigns.md).

# Create Campaigns

You’re just a few steps away from launching your campaign on Helix. Creating a campaign lets you define how, where, and to whom your ads are delivered so the system can start optimizing toward your goals.

To get started:

* Go to **User Acquisition → Campaigns**.
* Click **New campaign**.

## General settings

### Campaign name

Give your campaign a clear and descriptive name.

A commonly used naming convention is:

<mark style="color:red;">`[App]_[Platform]_[Objective]_[Geo]_[Optimization]_[Date or Version]`</mark>

**Example:** <mark style="color:red;">`MobControl_iOS_ROAS_Tier1_D7_2024Q1`</mark>

This structure helps teams quickly identify the campaign’s purpose, target, and optimization logic when managing or analyzing multiple campaigns.

### App

Select the platform and application you want to promote from the list.

This list is populated from the **Applications** you previously added to Helix. Search for an app by any part of its name.

{% hint style="warning" %}
If the selected app's MMP signals are partial or missing, a warning under the app field lists the missing signals. You can still save the campaign, but it may not be attributed and optimized correctly. See [Check MMP Signals](https://docs.helix.voodoo.io/user-acquisition/integrate-your-mmp/check-mmp-signals.md).
{% endhint %}

## Strategy

### User acquisition

Use this strategy to acquire new users.

Currently, **ROAS** campaigns are supported on Helix.

Select **ROAS** as the **Optimization Goal**.

Choose the **ROAS Period** you want to optimize for:

* **D0**: Optimizes toward revenue generated on the install day.
* **D7**: Optimizes toward revenue generated within the first 7 days after install.

The ROAS period defines the time window the system uses to evaluate user value and optimize delivery. Shorter periods (D0) favor faster feedback and scale, while longer periods (D7) favor higher-quality users with stronger long-term value signals.

### Reengagement

Use this strategy to reengage existing users.

Reengagement campaigns require a predefined audience.

Create your audience on the **Audiences** page, then select it in the campaign's [Targeting](#audience) section. See [Audience Management](https://docs.helix.voodoo.io/user-acquisition/audience-management.md).

## Countries and budget

You can create **groups of countries**, each with its own daily budget.

* Click the default group name (**Unnamed 1**) to rename your group.
* Set a **Daily budget** for the group.
* Click **Add country** to include countries in the group.
* For each country, set a **% ROAS goal**.

The ROAS goal defined at the country level guides bidding and traffic allocation:

* Countries with higher ROAS targets will receive more conservative bidding, prioritizing efficiency.
* Countries with lower ROAS targets allow more aggressive bidding, prioritizing scale.
* This enables the campaign to balance volume and efficiency based on country-level performance expectations.

You can use the **three-dot menu** next to a country to copy its ROAS value to other countries.

To target additional country sets with different budgets or ROAS goals, click **New group** and repeat the process.

## Targeting

### Placements

Select where your ads can appear:

* Interstitial (INT)
* Rewarded Video (RV)

### Device

Select supported device types:

* Phone
* Tablet

### Minimum OS version

Set a minimum OS version to restrict delivery to supported devices only.

### Audience

Link audiences to include or exclude specific lists of users by their device IDs. Search for each audience by name, select it from the list, and choose whether to include or exclude it. You can mix included and excluded audiences in the same campaign. Audiences are created and managed on the **Audiences** page. To create one, see [Audience Management](https://docs.helix.voodoo.io/user-acquisition/audience-management.md).

## Save the campaign

After saving, your campaign is created and you land on its **Ads** tab, where you add ads from the Ads library or create new ones. See [Add an ad to a campaign](https://docs.helix.voodoo.io/user-acquisition/create-ads.md#add-an-ad-to-a-campaign).

## Review large changes

When you edit a campaign, from the campaign form or from the campaign's **Countries** tab, a **Review before saving** dialog lists the changes that deserve a second look:

* A country's ROAS target moved by more than 10 points.
* The total daily budget moved by more than 50%.

The confirmation shows the before and after values for each change. Click **Save anyway** to apply them, or **Cancel** to go back. Nothing is blocked.

This confirmation doesn't appear when you create or duplicate a campaign.


---

# 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://docs.helix.voodoo.io/user-acquisition/create-campaigns.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.
