What is Header Bidding?
Also known as: Prebid, Server-side header bidding
Quick definition
Header bidding is a technique where a publisher offers each impression to multiple SSPs and exchanges simultaneously before calling its ad server, so demand competes on price at once instead of in a sequential waterfall.
How it works
- Page or app loads a wrapper (e.g. Prebid.js or an SDK)
- Wrapper requests bids from several demand partners in parallel
- Bids are passed as key-values to the publisher ad server
- Ad server compares header bids with direct deals and picks the winner
Key points
- Client-side
- Auction runs in the browser; transparent but adds page latency and limits partner count.
- Server-side
- Auction runs on a server (e.g. Prebid Server); scales to more partners but reduces cookie match rates.
Benefits
- Higher yield through simultaneous competition
- Less dependence on a single ad server's exchange
Trade-offs
- Latency and complexity
- Duplicate bid requests inflate infrastructure cost
FAQ
How is header bidding different from a waterfall?
A waterfall calls partners one after another by historical priority; header bidding asks them at the same time and lets the best real-time price win.
Explore on AdTech Radar
Official sources
Last reviewed 2026-10-27. Explanations are written by AdTech Radar; consult the official specification for implementation.