Ads.txt & App-Ads.txt: A Guide
Ads.txt and App-Ads.txt are essential tools in the digital advertising ecosystem designed to improve transparency and reduce ad fraud. They allow publishers to declare which companies are authorized to sell their digital advertising inventory, helping prevent counterfeit traffic and unauthorized sales.
By clearly listing approved sellers of ad inventory, these files give advertisers and buyers a reliable way to verify legitimate supply sources. This strengthens trust across the advertising ecosystem and ensures more secure transactions between publishers and demand-side platforms.
This guide provides a practical overview of Ads.txt and App-Ads.txt, including their structure, importance, and implementation.
Key Takeaways
- Ads txt and App-Ads.txt improve transparency in the programmatic advertising ecosystem by allowing publishers and app developers to define authorized sellers of their inventory.
- These files help reduce fraud risks such as domain spoofing, unauthorized reselling, and counterfeit inventory.
- Regular updates and correct implementation are essential for maintaining accurate records, improving buyer trust, and supporting more reliable monetization.
What is Ads.txt (Authorized Digital Sellers)?
Ads.txt stands for Authorized Digital Sellers. It is an initiative developed by the IAB Tech Lab that allows website publishers to publicly declare which companies are authorized to sell their digital advertising inventory.
By creating an Ads.txt file, publishers maintain better control over their ad inventory and help prevent unauthorized or counterfeit sales.
The file is a simple, machine-readable text file that ad platforms and buyers can scan to verify approved seller relationships for a domain. If a website works with multiple advertising partners, those partners are listed in the txt file so buyers can confirm they are purchasing legitimate inventory.
Although optional, Ads.txt has become a widely adopted standard in the programmatic ecosystem because it improves transparency, reduces fraud risk, and strengthens trust between publishers, advertisers, and ad technology platforms.
Why Ads.txt Matters for Publishers and Advertisers
Ads.txt helps reduce domain spoofing, unauthorized reselling, and counterfeit inventory in programmatic auctions. Buyers can check a publisher’s Ads.txt file and avoid bidding when seller information does not match authorized listings, helping protect advertising budgets from invalid traffic and misrepresented inventory.
For publishers, Ads.txt strengthens relationships with premium ad networks and programmatic buyers by improving transparency across the inventory supply chain. It also helps prevent unauthorized resale or arbitrage, where third parties attempt to sell inventory without publisher approval, giving publishers control over how their advertising inventory is represented and sold.
For advertisers, Ads.txt increases confidence that impressions are being purchased from legitimate and verified sellers, supporting safer transactions and more reliable digital advertising outcomes.
Structure of an Ads.txt File
An Ads.txt file is a simple, standardized text file that lists the authorized digital advertising sellers for a website. It is designed to be machine-readable for advertising systems while remaining easy for publishers to create and maintain.
Each line in the file represents a separate advertising relationship and follows a defined format set by the industry standard. This structure allows ad exchanges, SSPs, and demand-side platforms to quickly verify whether a seller is authorized to represent a publisher’s inventory.
Because of its consistent format, Ads.txt files can be automatically crawled and validated during real-time bidding, helping ensure that only approved inventory is included in programmatic advertising transactions.
Core Fields in Ads.txt Records
An Ads.txt file is made up of structured lines, and each line contains specific fields that define who is authorized to sell a publisher’s advertising inventory. Understanding these fields is essential for correctly creating and maintaining an Ads.txt file.
Ad system domain
This refers to the canonical domain of the advertising exchange or supply-side platform (SSP) that is authorized to sell a publisher’s inventory.
Publisher account ID
This is the unique identifier assigned to the publisher within a specific advertising platform. It ensures that ad inventory is correctly matched to the publisher’s account in the Ads.txt file.
Relationship type
This field defines the type of relationship between the publisher and the seller. “DIRECT” indicates a direct relationship with the publisher, while “RESELLER” indicates that the inventory is being sold through an authorized third party.
Certification authority ID
This optional field provides an additional layer of verification and is used by some certification authorities to support supply chain transparency and validation.
Common implementation errors include incorrect formatting, missing or extra commas, outdated publisher IDs, and failure to update entries when partnerships change. Keeping the file accurate and up to date is essential for maintaining Ads.txt effectiveness.
How to Create and Publish an Ads.txt File
Open a text editor and create a plain text file named “ads.txt”. Add the record strings provided by each approved ad network or advertising partner. Each partner has a specific record format that must be included accurately in the file.
Once completed, upload the file to the root domain directory of your website, typically accessible at yourdomain.com/ads.txt. This ensures the file is publicly available and can be crawled by advertising platforms.
After publishing, verify that the Ads.txt file is live by visiting the URL and confirming that the correct entries are displayed. It is also important to ensure the server returns a successful HTTP 200 status so that buyers and platforms can properly access and validate the file.
Managing Multiple Domains, Subdomains, and Large Publisher Setups
Large publishers, ad networks, and organizations managing multiple websites require strong governance when implementing Ads.txt. Each domain serving ad inventory should maintain its own Ads.txt file at the root level.
In some cases, subdomains may inherit the main domain’s Ads.txt file, while in other setups, depending on technical configuration and the Public Suffix List, they may require separate files.
To maintain consistency and control, publishers often maintain a centralized internal record of all authorized sellers. This typically includes seller names, authorization status, relationship type (DIRECT or RESELLER), and approved domains. A structured system like this helps reduce errors across multiple properties and ensures accurate Ads.txt management at scale.
App-Ads.txt for Mobile Apps
App-Ads.txt is an extension of the Ads.txt standard designed specifically for mobile applications. It allows app developers to publicly declare which advertising platforms and partners are authorized to sell their in-app advertising inventory.
Instead of being stored within the app itself, the App-Ads.txt file is hosted on the developer’s website and linked through the app store listing. Advertising platforms then crawl this file to verify authorized seller relationships before participating in ad auctions.
By clearly defining approved partners, App-Ads.txt improves transparency in mobile advertising, protects app revenue, and reduces the risk of unauthorized inventory sales.
How App-Ads.txt Works in Practice
A crawler first checks the app store listing to identify the developer’s official website, then accesses the App-Ads.txt file hosted on that domain (for example: dev-example.com/app-ads.txt).
It then compares the authorized sellers listed in the file with those appearing in incoming bid requests for in-app advertising. If a mismatch is detected, unauthorized sellers can be excluded from the auction process.
Implementing App-Ads.txt strengthens trust in the mobile advertising ecosystem by ensuring that only verified and approved sellers can monetize in-app inventory, reducing fraud and improving overall transparency.
Benefits of App-Ads.txt for App Developers
For mobile app developers, including those building gaming apps, streaming platforms, and Connected TV applications, App-Ads.txt helps buyers identify authorized digital sellers for each app. This increases transparency in the advertising supply chain, enabling advertisers to purchase inventory with greater confidence while reducing risks such as cloned apps, spoofed inventory, and unauthorized reselling of ad impressions.
For example, a mobile game that serves rewarded video ads can ensure its inventory is monetized only through approved advertising partners. This helps maintain control over ad placements, protects revenue streams, and supports long-term revenue growth while ensuring advertisers are buying through legitimate channels.
Implementing App-Ads.txt Step by Step
- Confirm that your app is linked to a stable and verified developer website domain.
- Create an App-Ads.txt file using the official IAB format and include the correct seller IDs provided by your advertising partners.
- Upload the file to the root directory of your developer website, so it is publicly accessible.
- Ensure the correct website URL is listed in your app store profile (Google Play Console or App Store Connect) so crawlers can locate the file.
- Allow time for advertising platforms to crawl and process the file, which may take from a few hours to several days.
- Regularly update and synchronize records whenever changes occur, such as new partners, account updates, rebrands, or acquisitions.
Ongoing Maintenance and Best Practices for Ads.txt and App-Ads.txt
Ads.txt and App-Ads.txt require ongoing maintenance rather than a one-time setup. It is recommended to audit the files every 30 to 90 days, remove outdated sellers, and document why each partner is included.
Before publishing updates, always validate the syntax to ensure there are no formatting errors, as even a single malformed line can impact ad demand.
Common Mistakes and Troubleshooting Tips
Most implementation issues come from simple errors such as incorrect domains, mismatched publisher IDs, inaccessible files, or misconfigured app store URLs.
To troubleshoot effectively:
- Check platform alerts from ad networks or SSPs
- Open the Ads.txt or App-Ads.txt URL directly in a browser
- Scan for formatting errors or malformed lines
- Maintain a changelog to track updates and enable quick rollbacks if needed
