Publisher Demand Integration
Header Bidding support (Body Bidding)
There are two options to plug in publisher’s header bidding setup into Browsi:
- Using the publisher’s existing setup (classic Header Bidding with Browsi see documentation here)
- Enable Browsi to run the header bidding setup by itself (Body Bidding).
What is Browsi’s “Body Bidding”?
Browsi’s supply dynamic creation enabling publishers to run bidding auctions in their pages <body>, instead of the <head>. This approach not only enables faster loading of the page, but also provides higher flexibility for demand setup.
How it works
- Publisher provides Browsi with the relevant header bidding tags they wish to run. Browsi team will plug them into the engine.
- Loaded later in the page, Browsi’s engine will dynamically discover, create and optimize ad supply on each page.
- Once each placement is created, Browsi will initiate, in the <body>, a different auction per each and every placement.
- The winning bid/impression will be embedded into the Browsi placement.
- (Optional) if using DFP, Browsi can insert the winning bid into it for Dynamic Allocation.
- No more holding content hostage – unlike traditional header bidding, Browsi enables dynamic placements that allow content, images widgets, and other content elements to load quicker and in parallel to ad supply.
- Run asynchronously – the auction is initiated in parallel for different placements on the page.
- Reduced latency – the entire auction flow runs in the <body> only after discovering a relevant, acceptable placement. It streamlines the loading of the page and reduces redundant calls to nonrelevant placements.
- Add more demand partners – removing the process to the <body> enables better, higher flexibility around the number of demand sources the bidding process can use.