> 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/monetization/configure-ad-units.md).

# Configure Ad Units

Create ad units for your app’s Interstitial and Rewarded placements.

An **ad unit** represents a specific placement in your app where ads can be shown to users. It defines the ad format and acts as the connection point between your app, the mediation platform if you use one, and demand sources.

Create an ad unit for each placement you want to monetize. Before you begin, [add your application](https://docs.helix.voodoo.io/monetization/add-your-application.md).

{% stepper %}
{% step %}
In Helix, navigate to **Ad Units** and click **New ad unit**.
{% endstep %}

{% step %}
Enter an optional **Name** for internal reference. Use a placement-focused name, such as <mark style="color:red;">`My App iOS Interstitial`</mark>.
{% endstep %}

{% step %}
Select the **Application**. Verify that its platform is correct: **iOS** or **Android**.
{% endstep %}

{% step %}
Choose the **Ad Format**:

* **Interstitial** displays a full-screen ad at a natural transition.
* **Rewarded** offers an in-app reward after an ad interaction.
  {% endstep %}

{% step %}
Click **Save** to create the ad unit.
{% endstep %}

{% step %}
Copy the system-generated **Ad Unit ID**. Use the matching ID when configuring Helix on your mediation platform.
{% endstep %}
{% endstepper %}


---

# 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/monetization/configure-ad-units.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.
