app-ads.txt for Publishers
Publishers must use the
app-ads.txt file to designate authorized digital sellers of their ad inventory, and DSPs use it to validate that they are buying inventory through an authorized source. Implementation is optional, but we strongly recommend adoption to optimize spend, as many buyers require this level of transparency.
In 2018, the IAB launched
ads.txt, a file enabling web publishers to designate authorized digital sellers of their ad inventory.
app-ads.txt is the mobile in-app equivalent of this specification, which mobile publishers can implement. This text file declares your Authorized Digital Seller (ADS) List to prevent unauthorized sellers from profiting off your inventory or from selling counterfeit inventory.
In the Publisher UI, verify necessary fields. Buyers on MoPub Marketplace require these data signals to be correct in order to bid on your app:
In Account Settings, ensure that the correct Domain is entered for the account. This value must reflect the root location of the site where the
app-ads.txtfile is hosted. Additionally, it should match the domain specified as the developer site when submitting the app to the app store.
Under the Apps tab, click to edit each application, and in the Edit App page, ensure that the correct value is entered in the Store URL (recommended) field.
Provide a developer website in your app store listings. Ensure that the proper developer website URL is accessible in the developer website section of the app store.
app-ads.txtfile in Notepad.
If you have multiple frontend accounts (publisher IDs), make sure that your
app-ads.txtfile reflects this. Create a row for each publisher ID in the
Include the following data:
Ad Source Domain: For MoPub, this value is
Publisher ID: Refer to these instructions to find your Publisher ID.
Type of Relationship: All of MoPub’s publisher relationships are direct, so the value for MoPub is always designated as
Ad Source ID: This is the ad source’s TAG ID. For MoPub, the value is
The following is an example of the MoPub entry in a publisher’s
app-ads.txtfile. The four parameters are separated by commas, with a separate line for each authorized partner:
mopub.com, [pub id], DIRECT, 74b46c0ea83967ca
app-ads.txtfile in the root of the app developer’s developer website; for example,
Validate that the file is taking effect. While we do not currently offer a validator tool for
app-ads.txt, you can verify that it is correctly implemented by appending “
/app-ads.txt” to your main domain (as in,
Although implementing this spec is optional, we encourage all publishers and DSPs to adopt
app-ads.txt as a best practice to help further our industry’s overall transparency and trust. For more information, refer to the IAB Tech Lab’s specification in its entirety on its website.
Integrate with Rubicon
Additionally, MoPub has an integration with Rubicon’s trusted exchange. With this integration, you immediately gain access to a larger number of DSPs through the MoPub Marketplace, with additional brand-focused spending at high CPM. To access this high-value demand, include the following entry in your
rubiconproject.com, 21648, RESELLER, 0bfd66d529a55807
MoPub’s Tag ID
If you are implementing
app-ads.txt MoPub’s Tag ID is
How can we make this article better for you?
Last updated March 30, 2021
TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.
© 2021 MoPub (a division of Twitter, Inc.)