Header bidding, sometimes called advanced bidding or pre-bidding, is an advanced programmatic advertising technique that allows publishers to offer their ad inventory to multiple demand sources simultaneously — before the ad server makes its final decision.
It's one of the most impactful revenue optimization strategies available to publishers today, and understanding how it works is essential for anyone serious about maximizing ad revenue.
The Step-by-Step Process
Here's exactly what happens when a user visits a page with header bidding enabled:
- User visits the page — The browser starts loading the page and encounters the header bidding JavaScript wrapper (usually Prebid.js) in the
<head>tag. - Simultaneous bid requests — The wrapper sends bid requests to all configured SSPs (Supply-Side Platforms) at the same time. This happens in milliseconds.
- SSPs respond with bids — Each SSP runs its own auction and returns the highest bid it can offer for that specific impression.
- Bids collected — The header bidding wrapper collects all bids within a set timeout (typically 1-2 seconds).
- Winning bid passed to ad server — The highest bid is passed to the ad server (e.g., Google Ad Manager) as a key-value pair.
- Ad server makes final decision — The ad server compares the header bidding bid against direct deals and other demand sources, then serves the highest-paying ad.
- Ad renders — The winning ad creative is displayed to the user.
⚡ Speed matters: The entire header bidding auction typically completes in under 300 milliseconds — faster than a human blink.
What is Prebid.js?
Prebid.js is the open-source, industry-standard JavaScript library used to implement header bidding. It was created by AppNexus and is now maintained by the Prebid.org community.
Key features of Prebid.js:
- Supports 300+ SSP adapters (bidders)
- Fully transparent and open-source
- Highly configurable — set timeouts, price floors, and more
- Works with all major ad servers including Google Ad Manager
- Free to use — no licensing fees
Key Components of Header Bidding
SSPs (Supply-Side Platforms)
SSPs are the technology platforms that connect publishers to advertisers. In header bidding, each SSP runs its own real-time auction and returns a bid. Common SSPs include Google AdX, AppNexus, Rubicon, OpenX, PubMatic, and Index Exchange.
Price Floors
Publishers can set minimum prices (floors) below which they won't accept bids. This protects inventory value and ensures you never sell impressions below their worth.
Bid Timeout
The maximum time the wrapper waits for SSP responses before proceeding. Typically set between 1,000-2,000 milliseconds. Longer timeouts get more bids but can slow page load.
Key-Value Pairs
The mechanism by which winning header bids are passed to the ad server. The bid price is encoded as a key-value pair (e.g., hb_pb=2.50) that the ad server uses to make its final decision.
Header Bidding Revenue Impact
| Metric | Without Header Bidding | With Header Bidding |
|---|---|---|
| Average eCPM | $1.20 | $1.80 – $2.40 |
| Fill Rate | 70-80% | 85-95% |
| Revenue per 1M impressions | $1,200 | $1,800 – $2,400 |
| Demand sources competing | 1-3 | 10-15+ |
Common Header Bidding Challenges
While header bidding is powerful, it comes with challenges:
- Page latency — More bid requests can slow page load if not properly configured
- Technical complexity — Requires ongoing maintenance and optimization
- Bid duplication — Some SSPs may represent the same demand, leading to duplicate bids
- Cookie syncing — User matching across SSPs can be imperfect
Working with a managed header bidding partner like Pubixa eliminates these challenges — we handle all setup, optimization, and ongoing management.