Hi all,
I pulled together some thoughts for the upcoming meeting on how to incorporate header bidding into OpenRTB.
Looking forward to discussing.
-Tony
OpenRTB 2.5 Header Bidding Proposal
Bid Request
As a publisher, I want to be able to maximize the yield from my header bidding implementation. By signalling OpenRTB buyers that a bid request originated from a header bidding implementation, I can ensure that buyers have the best available information in order to appropriately value the ad opportunity.
Option #1 - Minimal Solution - Update Impression Object
Add a field, imp.hb, integer, 0=non-header, 1=header, where the omission of the field presumes non-header.
Option #2 - Header Object
Create a Header Object as part of the bid request object. If the Header Object is present, then the bid request originated from a header auction.
header.type, integer, required, 0=unknown, 1=client-side, 2=server-side
header.mediation, integer, recommended/required?, enumerated list of mediation methods 1=container, 2=ad server, 3=other, etc.
header.adserver, string, optional, name of ad server platform
header.container, string, optional, name of container technology
header.timeout, integer, optional, timeout setting for header auction
Note: The format object introduced in 2.4 solves for one of the more frequent scenarios in header bidding - soliciting multiple bids for multiple sizes for the same impression.
Bid Response
As a buyer, I want to ensure that I see only the bid requests necessary to meet my campaign goals. Header auction technology may result in superfluous bid requests. By signaling the seller with appropriate codes, I can coordinate an appropriate volume of bid requests.
Option #1 - Update NBR Codes
9 - Daily Reader Cap Met
10 - Daily Domain Cap Met--
You received this message because you are subscribed to the Google Groups "openrtb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrtb-dev...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
header.type, integer, required, 0=unknown, 1=client-side, 2=server-side
How does "header.type" make sense?
What type of header bid takes place on the server side?
Header bidding generally refers to an auction in the HTML <head> tag via script, meaning in an HTTP response for a web page to a client.
header.mediation, integer, recommended/required?
What is the mediation referring to exactly? Does this refer to an embedded ad tag in an OpenRTB response to the header (waterfall)? Why would this be in the protocol?
header.timeout, integer, optional, timeout setting for header auction
This one sort of makes sense since the publisher often times sets the auction timeout.
Are these parameters from typical header bidding such as Prebid.js, or are they from Sovrn's HeaderSuite.com proprietary implementation?
- Chris