Header bidding trafficking FAQ
In Ad Manager, header bidding trafficking is a feature that enables publishers to integrate their header bidding demand.
Frequently asked questions
Here are some answers to questions you may have about header bidding trafficking and how it works:
Currently, Ad Manager 360 supports the Prebid wrapper for header bidding trafficking. While header bidding allows for a lot of customization, the Prebid implementation must be "standard" enough such that the Google Publisher Tag (GPT) is able to integrate with it. Web inventory and the Banner ad format are currently supported. Learn more about the requirements for header bidding trafficking.
The majority of Prebid implementations are supported, but some customizations that change the way that Prebid works may prevent Ad Manager 360 from collecting bids to compete in ad serving. Note that failure to fetch data will prevent the bidder from competing, causing ad requests to fall back to status quo Price Priority line items targeted for header bidding.
To use header bidding trafficking, the Prebid implementation must meet the following requirements:
- GPT can find the Prebid global object.
- The global object has a getEvents() function that works properly.
- For each slot using header bidding in yield groups, the Prebid AdUnit is set to a GPT slot's ad unit path or element ID.
pbjs.renderAd().