1:05Inside an OpenRTB bid request
Your page asks for an ad. What does the buyer actually see?
Lesson notes
Your page asks for an ad. What does the buyer actually see?
A bid request. In OpenRTB, that’s one JSON message describing one ad opportunity.
Here’s one from news.example. First, imp, the impression. A three hundred by two fifty banner, floor one dollar fifty. Then site, the exact page. Device, the browser and country. User and regs carry the consent strings, what data may be used. Source holds the schain, every seller in the path. In version two point six, that’s a core field. And tmax, one hundred and twenty. Answer within one hundred and twenty milliseconds, or you’re out. The DSP reads it all, and decides whether to bid, and how much.
So, a buyer can only price what you send. Ask your SSP which fields it fills, especially page, consent and schain.
Next: buyers.json and the demand chain.
Go deeper · 4 min readUnderstanding OpenRTB 3.0: The Future of Programmatic AdvertisingUp next in this series
1:01buyers.json and DemandChain: the buyer-side mirrorbuyers.json and DemandChain: the buyer-side mirror
1:05ads.cert: signing the bid requestads.cert: signing the bid request
1:25OpenRTB started with block listsOpenRTB started with block lists
1:18Header bidding, in one storyHeader bidding, in one story
1:24Who actually handled this impression? (schain)Who actually handled this impression? (schain)