> 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/advanced-configurations/app-ads.txt.md).

# app-ads.txt

As an extension of its [Authorized Digital Sellers (`ads.txt`)](https://iabtechlab.com/wp-content/uploads/2022/04/Ads.txt-1.1.pdf) specification, the Interactive Advertising Bureau (IAB) provides the [Authorized Sellers for Apps (`app-ads.txt`)](https://iabtechlab.com/wp-content/uploads/2019/03/app-ads.txt-v1.0-final-.pdf) specification that defines how app publishers should list their authorized monetization partners. Using this file, buyers can confidently identify authorized sellers and prevent app domain spoofing and unauthorized selling of in-app inventory.

To implement `app-ads.txt` for fraud prevention, complete the following tasks:

* Add DT to your `app-ads.txt` file. This authorizes DT as a direct seller. For more information, see [Adding DT to Your app-ads.txt File](#adddt).
* Add the `app-ads.txt` file to the root of your developer or marketing website. For more information, see [Place Your app-ads.txt File](#txtlocation).
* Add your website URL to your app store listing. Buyers only search the listed sites for `app-ads.txt` files. For more information, see [Adding a Developer Website](#addurl).

## Adding DT to Your app-ads.txt File <a href="#adddt" id="adddt"></a>

To list DT in your app-ads.txt file:

1. Create your `app-ads.txt` file according to the IAB specification for [`ads.txt`](https://iabtechlab.com/wp-content/uploads/2022/04/Ads.txt-1.1.pdf).
2. Add DT as a direct seller in your `app-ads.txt` file by copying the following record into your `app-ads.txt` file and entering your DT Publisher ID where indicated.\
   For more information, see [Locating Your DT Publisher ID](#dtid).

```
fyber.com,YOUR_DT_PUBLISHER_ID,DIRECT,1ad675c9de6b5176
```

3. Add official DT resellers in your `app-ads.txt` file. For a complete list of official resellers, see [app-ads.txt Contents](#section-listing-indirect-authorized-sellers).

### Locating Your DT Publisher ID <a href="#dtid" id="dtid"></a>

To locate your DT Publisher ID:

1. Log in to the [DT Console ](https://console.fyber.com/login)and click your user name at the top-left of the screen.
2. Select **User Profile**.

<div align="left" data-with-frame="true"><img src="/files/pdIKrNcCASlKYKRqyw21" alt="" width="228"></div>

3. From the **Basic Reporting API - Credentials** section, copy your **Publisher ID**.

<div align="left" data-with-frame="true"><img src="/files/f7xXQOmKADdnSOdJvSIK" alt=""></div>

### app-ads.txt Contents <a href="#section-listing-indirect-authorized-sellers" id="section-listing-indirect-authorized-sellers"></a>

The `app-ads.txt` file contains entries for DT and our official resellers.

Copy the contents into your `app-ads.txt` file and enter your DT Publisher ID where indicated.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Click to Open DT's app-ads.txt File</td><td><a href="/files/FkHIpk9wbheDS65vGj3f">/files/FkHIpk9wbheDS65vGj3f</a></td><td><a href="https://www.digitalturbine.com/dt-app-ads.txt">https://www.digitalturbine.com/dt-app-ads.txt</a></td></tr></tbody></table>

{% hint style="danger" %}
Beware of unknown companies reaching out directly and requesting to be added to your `app-ads.txt` file. This may be fraud. DT strongly advises that you only list your direct partners and their official resellers.

If you suspect a company is fraudulently contacting you, contact your DT Representative.
{% endhint %}

## Place Your app-ads.txt File <a href="#txtlocation" id="txtlocation"></a>

When placing your `app-ads.txt` file on your domain, ensure that the location meets the following criteria:

* Either the root of your domain (`fungames.com/app-ads.txt`) or no more than one subdomain below the root (`my.fungames.com/app-ads.txt`).
* If you place the file in a subdomain, do not place it in either the `www.` or `m.` subdomains.

## Adding a Developer Website <a href="#addurl" id="addurl"></a>

List your developer website URL in all app stores where you offer your app so that advertising platforms can locate your `app-ads.txt` file. The following sections provide guidance in entering a website URL for your app listing.

### Apple App Store <a href="#h_01k5hb3zmd0ffz3zvx3k9m3fn1" id="h_01k5hb3zmd0ffz3zvx3k9m3fn1"></a>

The App Store provides your Developer URL as part of the app listing.

<div align="left" data-with-frame="true"><img src="/files/J3k83PtOrYAgEMrvb2Ai" alt=""></div>

To update or add a developer website to your App Store listing:

1. Log in to [App Store Connect](https://appstoreconnect.apple.com/login) and locate your app and version.
2. In the **Marketing URL** field, enter the URL for the domain where you placed your `app-ads.txt` file.

<div align="left" data-with-frame="true"><img src="/files/HxXe9AInhNiermueVXVJ" alt=""></div>

### Google Play <a href="#h_01k5hb3zmdvb6aj31cskxy6xj3" id="h_01k5hb3zmdvb6aj31cskxy6xj3"></a>

The Google Play Store lists your developer URL in the **App Support** section of your app store listing.

<div align="left" data-with-frame="true"><img src="/files/c8y0s9j5PtQ2IvzPyD0U" alt=""></div>

To specify your developer website for Google Play:

1. Log in to the [Google Play Console](https://play.google.com/console) and go to **Store presence→Store settings**.

<div align="left" data-with-frame="true"><img src="/files/NaOo1zCYa6YV7HPRW5za" alt=""></div>

2. Click **Edit** and enter the URL for the domain where you placed your `app-ads.txt` file.

<div align="left" data-with-frame="true"><img src="/files/KDeYao5hYs9E4P69n6c6" alt=""></div>


---

# 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://docs.digitalturbine.com/dt-exchange/getting-started-with-dt-exchange/advanced-configurations/app-ads.txt.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.