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

# Create Ads

Create ads in the Ads library and add them to your campaigns.

An ad can be created in the Ads library or from a campaign page. The same ad can be added to several campaigns. Ads can't be edited once created.

## Create an ad

* In the left menu, open **User Acquisition → Ads** to open the Ads library.
* Click **New ad** in the top right.

You can also create an ad from a campaign. See [Add an ad to a campaign](#add-an-ad-to-a-campaign).

### Name

Give your ad a clear and descriptive name.

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

### Apps

Select one or several apps the ad will promote, for example the iOS and Android versions of your game.

### Format

Select the ad format from the dropdown list.

* Playable
* Video + Playable

### Assets

Once the format is selected, the **Assets** section appears.

* For **Playable**, select an HTML file.
* For **Video + Playable**, select a video and an HTML file.

The asset picker only lists assets of the selected type that are available on all the selected apps.

{% hint style="info" %}
All selected assets must already be uploaded and activated in the [Assets library](https://docs.helix.voodoo.io/user-acquisition/upload-creative-assets.md). To use an asset on several apps, link it to all of them.
{% endhint %}

### Save

Click **Save** to create the ad. It appears in the Ads library, not linked to any campaign yet.

## Add an ad to a campaign

* In the left menu, open **Campaigns**, then select a campaign.
* On the **Ads** tab, click **New ad**. The Ads library opens.
* Pick an existing ad, or click **Create ad** if none fits.

An ad can only be added to a campaign if all its assets are available on the app the campaign promotes.

When you create an ad from a campaign, a QR code is displayed after saving. Scan it with the [Helix Test App](https://docs.helix.voodoo.io/user-acquisition/create-ads/test-your-ads.md) to check that the ad renders and behaves as expected, then click **Done**.

## Remove an ad from a campaign

Use the three-dot menu next to an ad on the campaign's **Ads** tab and click **Remove from campaign**. To remove several ads at once, select them, then click **Remove from campaign** in the selection bar.

A removed ad stops on that campaign only: it keeps running on its other campaigns, stays in the Ads library, and the campaign keeps its reporting. On the campaign's **Ads** tab, it shows a **Removed** tag.

To put it back, use **Add to campaign** on that ad.

{% hint style="warning" %}
Don't archive an ad to stop it on a campaign. Use **Remove from campaign** instead. Archiving is final and stops the ad everywhere. See [Ads Library](https://docs.helix.voodoo.io/user-acquisition/create-ads/ads-library.md).
{% endhint %}

## Pause or start ads

Use the three-dot menu next to an ad, or the ad's details panel, to **Pause** or **Start** it. Only active ads are eligible to serve traffic.

{% hint style="warning" %}
An ad has one status across every campaign it runs on. Pausing it stops it on all of them. Helix lists those campaigns before applying the change.
{% endhint %}


---

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