> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-exchange/getting-started-with-dt-exchange/setting-up-your-app-in-the-dt-console.md).

# Setting Up Your App in the DT Console

To set up apps and offer placements on the DT Exchange, you must have access to the DT self-service web dashboard, [DT Console](https://console.fyber.com/). Signing in to the DT Console requires a DT Publisher account.

For more information, see articles on [Signing Up for DT Console](/dt-console/authorization/signing-up-for-dt-console.md) and [Signing In to the DT Console](/dt-console/authorization/signing-in-to-the-dt-console.md).

Once you have the credentials and your account has been confirmed, configure your app:

* [Step 1: Add your app](#addapp).
* [Step 2: Add placements to your app](#addplacements).

## Step 1: Add Your App <a href="#addapp" id="addapp"></a>

The DT Console allows you to add your app whether or not it is published in an app store. When you add your app, you can either add placements at the same time or add your placements after adding your app.

To add your app using the DT Console:

1. In the [DT Console](https://console.fyber.com/), go to **Monetization → App Management**, and click **Add App**.
2. Enter details about your app.\
   For more information, see our [Adding an App](/dt-console/app-management/adding-a-new-app/adding-an-app.md) article.
3. Enter placements for your app as described in [Working with Placements When Adding an App](/dt-console/app-management/adding-a-new-app/working-with-placements-when-adding-an-app.md), or skip this step now and add them later.
4. Click **Add app**.

## Step 2: Add Placements to Your App <a href="#addplacements" id="addplacements"></a>

You can add multiple placements to one app, and you must add at least one placement to monetize your app. For each placement, you can define a specific ad format, configuration, and delivery rules to maximize performance.

To add a placement to your app:

1. In the [DT Console](https://console.fyber.com/), go to **Monetization → App Management**, and click your app.
2. On the **Placements** tab, click **Add placement**.
3. Enter basic placement details (ad type, floor price, and name), and click **Add** at the end of the new placement row.\
   For more information, see [Setting Up Placements](/dt-console/app-management/setting-up-an-existing-app/setting-up-placements.md).
4. To configure additional placement settings (targeting, refresh rate, capping, pacing, etc.), click the newly added placement, enter the desired settings, and click **Save**.


---

# 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.digitalturbine.com/dt-exchange/getting-started-with-dt-exchange/setting-up-your-app-in-the-dt-console.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.