Is it a wrapper? Is it a container? Or is it a framework? The answer is all of the above. In our last post, we covered what header bidding is along with its benefits and drawbacks. Today, we’ll break down what a header bidding wrapper is and how they fit into the process. So let’s kick off the conversation with a definition:
What is a header bidding wrapper?
A wrapper, also referred to as a container or a framework, is a technology used to manage all the header bidding partners a media owner wants to utilize. This technology organizes buyers and sets rules for the programmatic auction. This minimizes the added code and complexity introduced with each new header bidding partner. Header bidding wrappers are necessary for media owners wanting to maximize the number of demand sources competing for an impression opportunity. Using a wrapper ensures that all partners have their bid requests triggered at the same time. Additionally, wrappers include a universal timeout setting to manage how long the browser waits for bidders to respond.
- Page loads, player loads, the header bidding wrapper code loads with each header bidding partners’(HBPs) code and fires the opportunity to all HBPs’ servers.
- HBPs respond with their respective bids.
- The wrapper then takes those responses and mediates the results to DoubleClick for Publishers (DFP).
- HBC code on page modifies the Master Video Tag (MVT) with Key Value Pairs (KVPs) that instruct DFP on which line item to trigger.
- DFP sends the corresponding line item to the player, which plays the ad.
While a wrapper isn’t essential to implement header bidding, it is beneficial when working with multiple partners and provides a simplified way of sending information back to DFP. At SpotX, we already have the ability to compete an infinite list of demand partners at the same time server-side with our parallel ad decisioning, removing the need for a wrapper. This introduces a number of important efficiencies that client-side header bidding alone cannot.
However, media owners often have contractual or financial reasons to maintain client-side header bidding partnerships. That’s why SpotX has built out the technology to accept bids from multiple header bidding partners on the page and inject them into our server-side auction, removing any unnecessary processes. SpotX can integrate with your stack of client-side header bidder solutions, along with all of our existing demand sources and provide fine-grained campaign and timing controls for each demand partner.
To learn more about header bidding, check out Debunking the video header bidding hype, a publisher’s guide on Digiday by our very own Senior Director of Product Management, Kevin Hunt. And stay tuned for the upcoming weeks as we’ll cover:
- What is Header Bidding?
- How Header Bidding Works in Video vs. Display
- Client vs. Server Side Header Bidding
- SpotX Launches New Tools to Integrate Third-Party & Proprietary Header Bidding Solutions
- Compete Demand Holistically with SpotX
- Everything you need to know about video header bidding
This article was written by Lexie Pike, product marketing coordinator at SpotX.