BeeBid
Hybrid Header Bidding Wrapper
Make every impression fight for its price.
BeeBid runs a real-time auction across every demand partner you have — in parallel, before your ad server ever gets involved. Google stops being the only buyer at the table and starts having to outbid the street price for your inventory.
Auction · in-content 300×250
cricketblog.example · 🇮🇳 Delhi · mobile
Bids received · parallel
Winner
₹92 CPM
AdX outbid the ₹84 header bid to win. Either way the impression cleared above the street price.
- Header bid → GAM
- ₹84
- AdX response
- ₹92
- Timeouts
- 0 / 6
- Without competition
- ₹71
The problem
What this is costing you right now
AdSense-only means one buyer sets the price
With a single demand source there is no auction — there is a quote.
Waterfalls sell premium impressions to the first bidder, not the highest
A traditional waterfall calls networks in a fixed order and stops at the first one that fills.
Heavy wrappers kill page speed and Core Web Vitals
Most publishers who try header bidding bolt on a full Prebid build with forty adapters, blow their LCP budget, and watch search traffic fall further than ad revenue rose.
How it works
What BeeBid actually does
No black box. Here is the whole mechanism, step by step.
BeeBid — how it works
-
1
Parallel auction to every demand partner
The moment the page starts loading, BeeBid asks all your demand partners for a bid at the same time — not one after another. The whole auction is time-boxed, defaulting to 400ms client-side, so a slow bidder can never hold up the page.
-
2
The winning bid enters Google Ad Manager as a line item
The highest header bid is passed into GAM as a price the ad server can see. This is the step that changes the economics: your open-market demand is no longer invisible to Google.
-
3
AdX has to beat the street price
Google now competes against a real number rather than an empty room. It either outbids the header bid — and you earn more from AdX — or it loses, and you earn more from the header bidder. Both outcomes pay you more than having no competition.
-
4
The winner renders
The creative is served through your existing ad server. Nothing about your GAM setup, your AdSense account or your ad units has to be replaced — BeeBid adds competition to what you already run.
-
5
Every bid is logged
Win or lose, each bid is streamed to the BeeOS data pipeline: bidder, price, latency, timeout, win/loss. That log is what BeeFloor learns your price floors from and what BeeFresh uses to decide when a refresh is still worth serving.
- Parallel auction all partners at once
- Under 400ms configurable 200–1000ms
- Bid-level logs every bid, win or lose
- TCF v2.2 ready consent passed through
In context
Where BeeBid sits on your page
BeeBid runs the auction for every ad slot on the page — leaderboard, in-content and sidebar. One is highlighted here for clarity.
Your existing Google Ad Manager setup keeps serving. BeeBid adds the competition it has to beat.
Specifications
Full technical specification
Publishers compare specifications, not adjectives. Everything is here, including what depends on partners we do not control.
Auction architecture
| Wrapper base | Prebid.js (latest stable), custom modular build — only the adapters you actually use are compiled into the bundle we ship to the browser. No dead code for demand you do not have. |
|---|---|
| Architecture | Hybrid. Client-side bidding for premium CPMs where buyer match rates matter, plus Prebid Server (server-side) for fill and speed. Per-slot routing rules decide which path each ad unit takes. |
| Auction timeout |
Configurable 200–1000ms. Defaults: 400ms client-side, 200ms server-side — chosen for Indian mobile network latency, where anything under ~300ms starts costing real fill from slower bidders.
|
Demand & identity
| Demand adapters at launch | Amazon APS/TAM, PubMatic, Magnite, Index Exchange, Sharethrough, Sovrn, Criteo, plus AdSense/AdX backfill through Google Ad Manager. Partner-dependent — individual SSP seats are subject to that SSP's own approval process and timelines. |
|---|---|
| Bid caching & refresh-aware auctions | Supported. Refresh requests are tagged as refresh inventory so buyers can price them for what they are — see BeeFresh gate 6. |
| Identity modules | SharedID, UID2-ready, hashed-email support. Privacy-safe by construction: identifiers are hashed before they leave the page. |
| Consent & privacy | IAB TCF v2.2 / GDPR compatible, and works with Google consent mode. Consent signals are passed through to every bidder rather than being assumed. |
Delivery & reporting
| Google Ad Manager integration |
Automated line-item generator with price granularity presets — dense granularity across a ₹0–₹500 CPM range. Generating hundreds of line items by hand is where most in-house header bidding projects quietly die.
|
|---|---|
| Deployment |
A single async tag. Target core size under 35KB gzipped, zero render-blocking requests. Nothing in the critical rendering path.
|
| Reporting | Bid-level log — bidder, bid price, win/loss, timeout rate, latency — streamed to the BeeOS dashboard. You can see which SSP is wasting your auction time and which one is quietly paying your bills. |
Some capabilities depend on third-party approvals and platform policies that are not ours to promise. Where that is the case, the spec above says so explicitly.
Expected impact
What the industry reports
Every number below is an industry benchmark published by a third party. BeeOS has not shipped, so none of these are results we have produced.
Expected RPM uplift once every impression has real competition benchmark 1
The top of the range is for publishers starting from a single demand source. Already running three SSPs? Expect the low end.
Without BeeOS
- Buyers per impression
- 1
- Price discovery
- None — a quote
- What AdX must beat
- Nothing
- Bid-level visibility
- None
With BeeOS
- Buyers per impression
- 6–7
- Price discovery
- Real-time auction
- What AdX must beat
- The street price
- Bid-level visibility
- Every bid logged
Expected difference
+15–30% RPM benchmark 1
The "without" column is the AdSense-only starting point most Indian publishers are actually in.
+15–30%
Typical RPM uplift after adding real competition benchmark 1
Publishers moving from a single demand source to Amazon plus three SSPs.
~18%
Hybrid client+server vs client-only architectures benchmark 2
Server-side adds fill from bidders the browser cannot reach in time.
<400ms
Default auction budget
Configurable per site. A bidder that misses the window is simply not counted.
Being straight with you: How much you gain depends almost entirely on where you are starting from. An AdSense-only publisher has the most to gain because they currently have no auction at all. A publisher already running three SSPs will see a smaller, narrower improvement — mostly from better timeout handling and floor coordination rather than from new demand.
Works with
Fits into the stack you already run
Platforms BeeOS integrates with — not customers, partners or endorsements.
- Google AdSense
- Google Ad Manager
- AdX (via partner)
- Prebid.js
- Amazon APS
- PubMatic
- Magnite
- Index Exchange
- Sharethrough
- Sovrn
Glyphs are generic shapes, not brand logos — these are platforms we integrate with, not endorsers.
Questions
BeeBid — frequently asked
Module 1 · Yield Engine
The rest of the module
Squeeze every rupee out of the ad requests you already serve — competition, pricing, repetition, placement and speed.
BeeFloor
Dynamic Price Floor Engine
Never sell a ₹100 impression for ₹21 again.
BeeFresh
Smart Ad Refresh (Engagement-Gated)
One visit. Multiple honest impressions.
BeeLab
Ad Layout A/B Testing Engine
Stop guessing where ads earn. Measure it.
BeeVitals
Viewability, Speed & Core Web Vitals Optimizer
Fast pages. Visible ads. Premium bids.
Be first in line for BeeBid
BeeBid is under active development. Early-access publishers get priority onboarding, founder-level support on WhatsApp, and locked-in launch pricing.
No spam — we write only when something real ships.