Bid Stack 101
167 subscribers
5 photos
Header bidding explained without the AdTech jargon: what Prebid, wrappers, timeouts and floors actually do, one bite-sized lesson at a time, so non-ad-ops site owners can finally get it.
Download Telegram
Channel created
Channel photo updated
The wrapper: the referee of your auction

A "wrapper" is a small piece of code that runs the header bidding auction. It's the referee — it invites the bidders, starts the clock, and collects the bids.

Why it matters: without a wrapper, each ad partner would load their own script in its own way, slowing your page and creating chaos. The wrapper makes them all play by one set of rules.

Tiny example: the wrapper says "Everyone, bids in within 1 second — go." Partners reply, the wrapper picks the highest, and sends it to your ad server.

One thing to try: ask whose wrapper you run. Most independent sites use Prebid, a free open-source one.

In plain English: the wrapper is the referee that runs the auction fairly and on time.
Loading ads only when they're about to be seen pays better

Lazy loading means an ad only runs its auction as the reader scrolls near it, not all at once on page load.

Why it matters: buyers pay more for ads people actually see ("viewability"). An ad that loads at the bottom but is never scrolled to is a wasted, cheap impression that drags your whole average down.

Tiny example: load all 6 ads at once, only 2 get seen. Buyers see your low view rate and bid less on everything.

One thing to try: set lazy loading to trigger about 200 pixels before a slot enters the screen. Close enough to fill in time, not so early it loads unseen ads.

In plain English: ask for the auction right before the reader arrives, not before they've scrolled.
Myth: copy a successful site's config and you'll earn like them

The shortcut: find a big publisher's setup, copy their partners and timeout, done.

Why it fails: their numbers fit their audience. A site with mostly US desktop visitors can run a short timeout and premium partners. If your visitors are mobile and global, those same settings might starve your auction of bids.

Tiny example: their 1200ms timeout works on fast US connections but cuts off bids from your slower mobile readers in other regions.

One thing to try: copy their structure (how things are organized) as a starting point, then test every number against your own traffic.

In plain English: borrow the skeleton, never the exact numbers.


Хочешь больше cmo appointments? @cmo_week_aff
The old way (waterfall) quietly underpaid you

Before header bidding, sites used a "waterfall" — ad partners were asked to buy your ad space one at a time, in a fixed line.

Why that hurts:
— The first partner in line got first dibs, even if a partner further down would have paid more.
— Partners were ranked by their average past price, not what they'd actually pay right now.

Tiny example: Partner A usually pays $2, so they go first. But today Partner C would have paid $5 — they never got asked.

One thing to try: ask your ad setup whether you're still on a waterfall. If yes, that's the upgrade conversation to have.

In plain English: a waterfall asks buyers in order; header bidding asks them all at once, so the real top bidder wins.
What header bidding actually is

Header bidding is an auction for your ad space that happens the instant your page starts loading — usually finished in under 300 milliseconds (less than half a second).

Why it matters: instead of one ad buyer getting first pick, many buyers bid at the same time. More bidders competing means a higher winning price for you.

Tiny example: five ad partners each say what they'll pay — $1.40, $2.10, $0.90, $3.05, $1.80. The $3.05 bid wins and that ad shows. You earned $3.05 instead of whoever happened to be "first in line."

One thing to try: open any big news site, watch an ad load, and picture that silent auction firing.

In plain English: it's a 200-millisecond auction held the moment your page loads.