1:03Ep 4: ads.txt and sellers.json, the guest list buyers check
A buyer was offered your site's ad space. By a stranger.
Lesson notes
A buyer was offered your site’s ad space. By a stranger.
Ads.txt lists who may sell your ads. Sellers.json names them.
A bid request from ssp.example says site news.example, seller account four five two one. Check one. Does news.example/ads.txt list that account, marked direct? Yes. Check two. In ssp.example/sellers.json, account four five two one is News Example Media, type publisher. Both match, so the buyer bids. Now the stranger. Same site name, account nine nine nine nine. It’s not in your ads.txt, so it’s unauthorized. Google’s Display and Video three sixty skips unauthorized sellers by default.
Open your ads.txt. Pick one line, and find that account in that SSP’s sellers.json.
Next, client side versus server side header bidding.
Go deeper · 6 min readWhat is Ads.txt? Everything You Need to KnowUp next in this series
0:57Ep 5: Client-side vs server-side header biddingEp 5: Client-side vs server-side header bidding
0:58Ep 6: Curate vs PMPsEp 6: Curate vs PMPs
0:38Ep 7: Higher CPM, lower revenueEp 7: Higher CPM, lower revenue
1:03Ep 8: Price floors, the number that can raise or sink revenueEp 8: Price floors, the number that can raise or sink revenue
1:01Ep 9: More bidders, more revenue? Not past a pointEp 9: More bidders, more revenue? Not past a point
0:54Ep 10: Header bidding timeoutsEp 10: Header bidding timeouts
1:03Ep 1: One ad, 100 millisecondsEp 1: One ad, 100 milliseconds
1:00Ep 2: Waterfall vs header biddingEp 2: Waterfall vs header bidding
0:42Ep 3: Supply path — count your hopsEp 3: Supply path — count your hops