ads.txt-for-apps | Ads.txt for Apps
App-ads.txt is a simple solution that gives you complete control of your inventory. By creating a depository of authorized sellers, you can let your buyers identify the programmatic firms that have legitimate access to the inventory.
App-ads.txt will be a text file on the app publisher’s website that declares who is authorized to sell the publisher’s inventory.
How to implement
Perform these steps to implement
Step 1: Provide developer website URL in the app store
Publishing a website and providing its URL is mandatory for the app’s ad inventory to participate in the authorized seller scheme.
Step 2: Create the
Create a .txt file and name it
Step 3: Add Entry
Add an entry in the
app-ads.txt concatenating the following information. Contact your partner manager for assistance.
|IAB Field Name||Description||Example||Requirement Status|
|Domain Name of the Advertising System||The domain name of the system to which bidders connect.||inmobi.com||Mandatory|
|Seller Account ID||Please reach out to your InMobi partner manager for the Seller Account ID and TAG ID that needs to go with the InMobi entry. Do not use the Publisher GUID on the portal [Format: inmobi.com, seller account ID, relationship, InMobi TAG ID].||74dcd2c4fa2d401cb74bbb9c124a268c||Mandatory|
|Type of Account/Relationship||
The type of account is, either:
|Certification Authority ID||
An ID that uniquely identifies the system in Field 1 within a certification authority.
Note: The TAG ID for all InMobi lines in the ads.txt file is 83e75a7ae333ca9d.
|83e75a7ae333ca9d||Optional, but highly recommended|
Step 4: Post
app-ads.txt file to the root directory of your domain server for the appropriate website. The file can be accessible via HTTP or HTTPS but must be located under a standard relative path: "app-ads.txt". The HTTP request header must contain "Content-Type: text/plain".
Ads.txt checklist for apps
Please go through this to mitigate mistakes in implementation:
- List your developer URL on all app stores distributing the app. For example: https://www.example.com where "example" is the host name.
- Ensure you implement
app-ads.txton the same developer URL (https://www.example.com) that is listed on the app store.
- If you have multiple developer URLs across apps, ensure
app-ads.txtis implemented on all developer URLs and all your apps list the same developer URL on the app store.
- Ensure the app-ads.txt file is implemented in the root domain as shown below:
Please also refer the IAB specifications to know more about this.
- Be wary of mistakes in naming the .txt file. The file must be named
- Ensure the format of the file is
.txt. Buyers won’t be equipped to read data from any other format.
- Please reach out to your InMobi partner manager for the Seller Account ID and TAG ID that needs to go with the InMobi entry. Do not use the Publisher GUID on the portal [Format: inmobi.com, seller account ID, relationship, InMobi TAG ID].
- To mitigate any revenue loss, make sure you make entries for all InMobi Exchange partners as well. Please reach out to your InMobi partner manager for this information.
Generating app-ads.txt string on InMobi’s user interface
To ease implementation, we have introduced an
app-ads.txt file generator on the InMobi user interface that will automatically build the strings you need to add to your
app-ads.txt file in order to declare InMobi and its exchange partners as authorized sellers.
Step 1: Log into your InMobi Account > Account > Account Settings
Step 2: In Account Settings page, click
Step 3: In Ads.txt page, click
Generate Ads.txt Entries button
Following this, the UI will download a .txt file with the necessary strings. The four essential fields - inmobi.com, inventory source id, relationship, and tag ID - will be stitched together, ready to be added to the .txt file that you maintain. Please note that these ONLY include entries for InMobi accounts and Exchange partners.