Header Bidding Explained
Header bidding is one of the most significant structural shifts in programmatic advertising over the past decade. It changed the rules of how ad inventory is auctioned, and who benefits most from the process.
The problem header bidding solved
To understand header bidding, it helps to understand what came before it: the waterfall.
In a waterfall setup, a publisher’s ad server would offer inventory to demand sources one at a time, in a ranked order. The top-ranked network got first right of refusal at a preset price. If it passed, the impression moved to the next partner, and so on. This meant that a high-value buyer sitting lower in the waterfall might never get the chance to bid on an impression, even if they would have paid more than the winning price.
The result: publishers often left money on the table, and buyers with genuine demand were locked out.
What is header bidding?
Header bidding (also called pre-bid or advance bidding) is a technique that allows multiple demand sources (DSPs, ad networks, and direct buyers) to bid on a publisher’s inventory simultaneously, before the publisher’s own ad server makes its final decision.
In a typical setup:
- A user’s browser loads a publisher’s page.
- JavaScript code in the page header sends a bid request to multiple demand partners at the same time.
- All partners respond with their bids within a defined timeout (typically a few hundred milliseconds).
- The highest bid is passed to the publisher’s ad server, which compares it against direct-sold campaigns.
- The overall winner’s creative is rendered.
Because all demand sources compete at once, publishers get a true, competitive price for every impression rather than a first-come-first-served result.
Server-side vs. client-side header bidding
The original implementation runs in the user’s browser (client-side). While effective, it adds latency and can slow page load times when many demand partners are involved.
Server-side header bidding moves the auction logic to a server. The browser makes a single call to a header bidding server, which then fans out to multiple demand partners simultaneously. This reduces browser load and allows more partners to participate without meaningfully impacting page performance.
Both approaches are widely used, and many publishers run a hybrid model.
Open Bidding and unified auctions
Google’s Open Bidding (formerly Exchange Bidding) is a server-side alternative that runs within Google Ad Manager. It allows third-party exchanges and SSPs to bid alongside Google’s own demand in a unified auction. Other major SSPs offer comparable unified auction products.
These unified auction approaches consolidate much of the complexity that publishers previously had to manage across multiple header bidding wrappers.
Benefits for publishers
- Higher CPMs through genuine competition across all demand sources
- Reduced dependency on any single network or exchange
- Better fill rates for premium inventory
- More transparency into what buyers are willing to pay
Benefits for buyers
- Equal access to inventory regardless of where they sit in an old waterfall hierarchy
- More auction opportunities for high-value impressions
- Cleaner pricing signals from competitive auctions
Trade-offs and criticisms
Header bidding is not without drawbacks. Client-side implementations can slow page load, which has implications for user experience and SEO. Managing multiple demand partner integrations adds operational complexity for publishers. There are also ongoing discussions in the industry about auction mechanics, bid shading, and whether header bidding has fully delivered on its transparency promise.
How Arago helps
As a DSP built for local retail, Arago connects to publishers and inventory sources through modern programmatic infrastructure, including header bidding and unified auction environments, so that local advertisers can compete fairly for premium digital placements at efficient prices.