Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

ads.txt

A file on a publisher's site listing the companies authorised to sell its ad inventory.
Authorized Digital SellersAd TechtechnologyUpdated

Definition

ads.txt is an IAB Tech Lab standard. A publisher creates a text file named ads.txt at the root of its domain, and each line names one authorised seller with three pieces of information:

  • The advertising system, identified by its domain, usually an exchange or supply-side platform (SSP).
  • The publisher's account ID on that system, the identifier that system will put in its bid requests.
  • The relationship, either DIRECT, meaning the publisher controls that account, or RESELLER, meaning a third party has been authorised to resell the inventory.

Because the file sits on the publisher's own domain, only someone who controls the site can change it. That is what gives it authority: a fraudster can fake a bid request but cannot edit a well-known publisher's website.

In practice

A demand-side platform (DSP) reads ads.txt files and compares each bid request against them. If a request claims to be from a given domain but arrives through an exchange and account ID that the domain's file does not list, the request is treated as unauthorised. Buyers can then choose how strict to be. The DV360 inventory and deals guide describes authorised seller targeting with options ranging from direct sellers only to including publishers that have no file, each with its own trade-off in reach.

Checking ads.txt is one of the pre-bid controls in the brand safety and viewability guide, where it sits beside inventory lists, content categories and verification. It is also one of three transparency standards the programmatic ecosystem guide uses to read a supply chain and its fees, and the programmatic fundamentals section introduces all three together.

app-ads.txt and sellers.json

app-ads.txt applies the same idea to apps, so buyers can check app inventory against the developer's own declaration of who may sell it.

sellers.json works from the other end. Each exchange or SSP publishes a file declaring who is behind each seller ID it uses: the publisher itself, or an intermediary. Read together, ads.txt says who the publisher has authorised, and sellers.json says who those sellers actually are. A third standard, the SupplyChain object carried in the bid request, records each hop an impression took; the real-time bidding guide shows where it sits in the request.

What ads.txt does not prove

An authorised path is not a quality guarantee. ads.txt confirms that a seller may sell a domain's inventory. It does not confirm that the impression will be seen, that the visitor is human, that the page is suitable for the brand, or that the price is fair. Invalid traffic (IVT) can arrive through authorised sellers, a publisher can authorise resellers it does not monitor closely, and a site that exists only to sell ads can publish a perfectly valid file. Those questions belong to Brand Safety controls, viewability measurement and independent checking, which the media auditing and verification guide covers.

Illustrative example — not a real result

A mortgage broker restricts its supply paths

Coinwold Mortgage Advisers buys open-exchange display for £12,000 a month. A placement report shows 310,000 impressions labelled as a national news site, bought through an exchange whose account ID is not in that news site's ads.txt file. The broker switches its line items to authorised direct and reseller paths only. The mislabelled impressions disappear, total impressions fall by 9% and CPM rises from £3.10 to £3.40. Its verification vendor's invalid traffic rate falls from 6.8% to 2.1%, and cost per mortgage enquiry from display drops from £96 to £81, because less of the budget was buying impressions no person saw.

An SSP appears in ads.txt as the advertising system and publishes the matching sellers.json file. A DSP is the platform that checks bids against both. IVT is the wider fraud problem that ads.txt narrows only at the domain level, and Brand Safety covers the content questions it does not touch.

Common confusions

  • Authorised means safe. It means permitted to sell; quality, content and fraud need other controls.
  • ads.txt blocks bots. It stops domain misrepresentation, not non-human traffic on a real domain.
  • Reseller lines are suspect. Many are legitimate; the issue is resellers the publisher does not monitor.
  • ads.txt and sellers.json are alternatives. One is published by the publisher, the other by the seller, and they are read together.
  • No file means no risk. A site without ads.txt cannot be checked at all, which is why buyers decide whether to include such publishers.

More terms to look up

Where this term is used

Related