Learn
How in-app supply is declared and checked
Short, specific guides for ad-ops, monetization and programmatic teams. Each one is based on the IAB Tech Lab specifications and says where the files stop being able to tell you anything.
Basics
What is app-ads.txt? The file, the format and where it goes
The file every monetized app needs: what it declares, the four fields, the variables and exactly where verifiers look for it.
7 min read
app-ads.txt vs ads.txt: what differs and what does not
Same syntax, different discovery. Where each file lives, what each covers, and when you need both.
4 min read
sellers.json explained: fields, seller types and how to read one
The network's side of the declaration: every field, the three seller types, confidential entries and how lines are matched.
6 min read
DIRECT vs RESELLER in app-ads.txt
Which one to write, how buyers check it against sellers.json, and the mismatches that cost publishers bids.
5 min read
Publishers
OWNERDOMAIN and MANAGERDOMAIN in app-ads.txt
The ads.txt 1.1 variables that say who owns an app and who monetizes it, and how they tie to sellers.json.
5 min read
Common app-ads.txt errors and how to fix them
File not found, wrong host, stale seller IDs, relationship mismatches: what each error means and the fix.
7 min read
app-ads.txt for CTV apps
How CTV stores link to app-ads.txt, and how INVENTORYPARTNERDOMAIN handles shared inventory.
4 min read
Buyers
The SupplyChain object (schain) explained
The per-request record of who sold an impression: nodes, complete, hp, and how it is validated.
6 min read
How buyers verify mobile app supply
From store listing to schain: the checks a DSP runs on an in-app request, and what each can and cannot prove.
6 min read
How to read a supply path
Walk a declared path hop by hop through app-ads.txt and sellers.json, and know which signals matter.
6 min read