How app-ads.txt works

app-ads.txt connects three public places: your app’s store listing, your developer website and the bid request. A buyer checks that all three agree before spending money on your impression.

The idea in one sentence

Only the owner of an app controls the developer website shown in its store listing — so a list of authorized sellers published there can’t be faked by a third party.

Step by step

  1. The developer puts the website address in the app’s Google Play and App Store listing.
  2. At the root of that website the developer publishes app-ads.txt — one line for each ad network or SSP account allowed to sell the app’s ad space.
  3. Ad networks and buyers read the file regularly (usually once a day) and cache it.
  4. A bid request arrives: it names the app and the seller — the ad system and the account ID.
  5. The buyer looks for a line with that ad system and account in the app’s file. A match → the seller is authorized; no match → the request is skipped or bid lower.

What a line contains

google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0

Where it can break

Check your app-ads.txt free

FAQ

How often do buyers read app-ads.txt?

Most ad systems re-crawl it about once a day, so changes take effect within a day or two.

Does app-ads.txt work for CTV and OTT apps?

Yes. The same standard covers mobile, CTV and OTT apps — the file lives on the developer website of the app’s store listing.

Related guides

All app-ads.txt guides

More