Header bidding — running simultaneous auctions across multiple demand sources before the ad server decides which ad to serve — works differently on CTV than on the web. Display header bidding runs JavaScript in the browser before the page loads, collecting bids from multiple SSPs in parallel. CTV apps are not web browsers and cannot run JavaScript auction wrappers. CTV header bidding is therefore entirely server-side: the publisher's SSP or ad decisioning server orchestrates simultaneous bid requests to multiple demand sources, aggregates the responses, and selects the winning bid — all without any client-side JavaScript. The yield management benefit is the same; the implementation is fundamentally different.
Why CTV header bidding is server-side
Display header bidding works because browsers can execute the Prebid.js wrapper — a JavaScript file that manages simultaneous SSP calls before the page's ad server call. Native CTV apps (Android TV, Apple TV, Samsung Tizen, LG webOS) have no equivalent execution environment for third-party JavaScript in their video player context.
This is not a limitation that can be engineered around by the publisher without replacing their entire ad tech stack. A CTV app can integrate an SDK from a single SSP; it cannot run an arbitrary JavaScript wrapper. The server-side prebid model solves this by moving the auction orchestration off the device and onto the publisher's or SSP's infrastructure.
How CTV server-side prebid works
The server-side prebid sequence:
- CTV app sends ad request to publisher's ad server: When an ad break approaches, the CTV app sends an ad request to the publisher's ad decisioning layer (often SpringServe, FreeWheel, or a custom ad server).
- Ad server triggers server-side auction: The ad server makes simultaneous bid requests to multiple SSPs (Magnite, PubMatic, Index Exchange) via their server-to-server APIs. Each SSP runs its own downstream auction with connected DSPs.
- SSPs return bids: Each SSP responds with its highest bid within the timeout window (typically 200–300ms for CTV server-side).
- Ad server runs unified auction: The publisher's ad server compares all SSP bids, direct IO deals, and guaranteed campaigns in a single unified auction. The highest net revenue option wins.
- Winning creative delivered: The ad server returns the winning VAST tag to the CTV app. If SSAI is used, the SSAI system fetches and stitches the creative into the content stream.
Unified auction vs waterfall in CTV
Before server-side prebid, publishers managed demand through a waterfall — a sequential priority list where demand sources were called one at a time (direct IO first, then preferred programmatic, then open auction). Waterfalls are still common in India CTV because they are simpler to implement. Their disadvantage: lower-priority demand sources never compete against higher-priority ones, even if a lower-priority DSP would pay more for a specific impression.
Unified auctions (server-side prebid) let all demand sources compete simultaneously for every impression. For publishers, this improves yield — every impression goes to the highest bidder across all demand sources. For buyers, it means open auction bids can win against PMP floors if the bid is high enough, and DV360 or TTD's bids are always evaluated against the full demand pool.
In India CTV: JioHotstar and SonyLIV run unified auctions via Magnite. Smaller FAST publishers often still use waterfalls, particularly those relying on Zee Media's ad stack or custom integrations. Buyers should ask publishers directly how they structure their demand stack — it affects which deal type offers the best pricing efficiency.
Header bidding for India CTV publishers
For India CTV publishers considering server-side prebid adoption:
- SpringServe is the most common ad server for CTV prebid in India. JioHotstar and several mid-tier publishers use SpringServe as their video ad server, with Magnite and PubMatic connected as SSP demand sources. SpringServe's unified auction capability handles the prebid orchestration.
- Prebid Server (open source) is viable for technically capable teams. Publishers willing to operate their own infrastructure can deploy Prebid Server (the server-side counterpart to Prebid.js) to orchestrate CTV auctions. Requires engineering investment; not appropriate for publishers without an ad tech team.
- Expect 15–25% yield lift vs waterfall. Industry benchmarks for server-side prebid adoption in video/CTV show 15–25% revenue improvement over pure waterfall. The lift is lower when the publisher already has strong direct sell-through (60%+) because direct IO fills most inventory before programmatic competes.
- SSP consolidation matters: Running 5+ SSPs in a server-side prebid setup adds latency as the ad server waits for all responses. Most India CTV publishers run 2–3 primary SSPs (Magnite, PubMatic, one more) with a timeout that balances bid depth against delivery latency.