OpenAdLibraryOpenAdLibrary
Definition

ads.txt

ads.txt is a public file publishers host to declare exactly which companies are authorized to sell their ad inventory.

ads.txt — ad-tech glossary illustration

ads.txt (Authorized Digital Sellers) is a public text file that a publisher hosts at the root of its domain (for example, example.com/ads.txt) to declare which companies are authorized to sell its ad inventory. Introduced by the IAB Tech Lab in 2017 (see its ads.txt specification, version 1.1 from 2022), it is a simple, machine-readable allowlist designed to make it harder to sell counterfeit or misrepresented inventory in programmatic advertising.

How it works#

Each line names one authorized seller account in up to four comma-separated fields: the canonical domain of the advertising system, the seller account ID within that system, the relationship type (DIRECT if the publisher controls the account itself, RESELLER if it has authorized another entity to control the account and resell its ad space), and an optional certification authority ID, such as a TAG ID. The specification says advertising systems should retrieve a site's declarations before buying or selling advertising that claims to be on that site, so buyers, Demand-Side Platforms and exchanges can check that the seller offering an impression is on the list and decline it if it is not. A site with no ads.txt file (HTTP 404) has declared nothing, and the specification lets a system assume that no advertising system is unauthorized.

Why it matters#

ads.txt addresses one form of fraud: inventory offered under a misrepresented label, where the domain of a page or the ID of an app is falsified to look like a site or app the seller is not authorized to sell (domain spoofing). Publishing the list gives buyers a record to check a seller against, which IAB Tech Lab says makes it harder for bad actors to profit from selling counterfeit inventory. It does not stop fraud by itself: it lists who the publisher authorizes, so it says nothing about whether the traffic is human or the content is suitable, and it does not reveal who stands behind each listed account. sellers.json is the advertising-system counterpart: exchanges, SSPs and other advertising systems publish it to declare the sellers and intermediaries they represent, so a buyer can cross-check an ads.txt line against it and against the SupplyChain Object (schain) in a bid request. Each file is its publisher's own declaration and can be incomplete or out of date, and the SupplyChain specification notes that ads.txt does not attempt to reveal or authorize every party that transacts an impression, so the cross-check supports a review of the ad supply chain but is not proof. For app inventory, the equivalent file is app-ads.txt.

Related terms: sellers.json, SupplyChain Object (schain), and Ad Supply Chain.

The OpenAdLibrary Team
Written byThe OpenAdLibrary Team
Ad intelligence & native advertising research

We build OpenAdLibrary, the open ad-transparency platform. Every day our systems capture live native ads across Taboola, Outbrain, MGID, Revcontent, Teads, Yahoo and MSN, identify the real advertiser behind each one, and follow the click to its landing page. These guides distill what we see in that data so you can research the market faster.