What Is Header Bidding in Programmatic Advertising?

The problem it replaced

Before header bidding, publishers sold unsold inventory through a waterfall: the ad server offered an impression to one demand partner, and only if that partner passed did it move to the next, in a fixed order set in advance. The partner at the top of the list always got first look, whether or not it actually valued the impression the most. A demand partner willing to pay the most could sit fourth in line and never see the request at all, because the ad above it in the waterfall claimed the impression at a lower price it was willing to accept.

Header bidding fixes the order problem by removing the order. A small script runs in the page's header, before the ad server is called, and sends the same bid request to every connected demand source simultaneously. AdExchanger's 2015 piece describing "the rise of header bidding and the end of the publisher waterfall" is generally credited with naming the shift, and Prebid.js — the open-source wrapper published the same year — became the standard way publishers implement it without building the auction logic themselves.

How one auction actually runs

Here is what happens in the roughly 200–600 milliseconds most publishers allow before the page moves on without waiting further:

• The header script fires a bid request to every connected demand-side platform at once, carrying the ad slot, page context, and whatever the publisher knows about the visitor.
• Each DSP has until the timeout to respond. Say the publisher's floor is $2.00 CPM and five demand partners answer: $2.10, $2.65, $3.40, $1.90, and $2.20. The $1.90 bid is below floor and is excluded automatically.
• The wrapper passes the remaining bids into the ad server's decision alongside any direct-sold campaigns and line items already booked.
• The $3.40 bid wins the auction. The page renders that creative, and the whole sequence — request, four live responses, decision — finishes inside the timeout window, not after it.

The publisher nets more from that impression than a waterfall would have produced, because the second- and third-highest bidders were never given the chance to make the sale before the highest one even got asked.

Client-side vs. server-side, and why the choice matters

The original implementation ran entirely in the visitor's browser: the wrapper script loaded, contacted every demand partner directly, and only then called the ad server. That is client-side header bidding, and it is the version most responsible for header bidding's reputation for slowing pages down — every added demand partner is another network round trip the browser has to complete before the timeout closes.

Server-side header bidding moves the fan-out to a server the publisher controls: the browser makes one request, the server queries every demand partner in parallel, and only the winning bid comes back down to the page. It reduces the browser-side load, but it is not free of latency either — the request still has to reach the server, query several partners, and return, and it can lose some of the signal (like precise device data) that client-side bidding passes along directly. Neither one is simply "the fast one"; the trade-off is signal richness against round-trip time, and most large publishers now run a mix of both.

Where Amazon DSP actually fits — and where it doesn't

Amazon does not run header bidding as a publisher does. It participates in it, on the demand side, in two ways. Amazon Publisher Services (APS) gives publishers a header-bidding demand connection — Transparent Ad Marketplace (TAM) for publishers with their own established SSP relationships, and Unified Ad Marketplace (UAM) for publishers who want Amazon to manage those connections for them. Separately, Amazon DSP — the Demand-Side Platform, not the Delivery Service Partner courier franchise that shares the initials — is one of the demand partners a header-bidding wrapper can call, bidding for impressions on third-party sites the same way any other DSP does.

That second role is bigger than most explainers make it sound. In a single 31-day pull across 27 advertisers in our own managed Amazon DSP book, delivery landed on 134 distinct named supply sources — not the two or three placements most "Amazon DSP" articles describe. A meaningful share of that inventory arrives through exactly this kind of unified, header-bidding-style auction, run by a publisher's own ad stack, with Amazon DSP as one bidder among several competing for the same slot.

The mistake publishers make, and what to check when it isn't paying off

We buy media into these auctions as a demand-side participant; we don't run a publisher's ad stack, so this is the mistake we watch other buyers and publishers make rather than one we've made ourselves. The most common one is adding demand partners past the point of diminishing returns — every additional wrapper connection adds latency, and past roughly six to eight well-chosen partners, the extra competition rarely lifts the winning bid enough to offset the slower page and the viewability loss that comes with it.

If header bidding revenue looks flat or a specific demand partner's fill rate is low, work through the causes in this order: check the timeout first — a window set too short cuts off slower-but-higher bidders before they can respond; check the floor price second — a floor set above what the market will actually pay filters out real bids, not just weak ones; and check partner overlap third — several SSPs often resell access to the same underlying demand, so two "different" bidders may be quietly bidding against the same advertiser twice, inflating the perceived competition without adding real revenue.

Where Dr. DSP fits

Dr. DSP is Amazon DSP run as a managed product by Full Circle, which has managed more than $500M in revenue across 100+ brands. On the buy side, header bidding is one of the mechanisms that decides which of the 134 supply sources an impression actually reaches — evidence that a DSP bid without knowing which auction type won it is buying an average of things that behave nothing alike. A reader who never buys anything from us should still leave this page knowing that the words "header bidding" describe a publisher-side auction technique, not an Amazon-specific concept, and that Amazon DSP shows up in it only as one bidder among many.