Most India CTV advertising discussions centre on Google Ad Manager (which JioHotstar uses) because JioHotstar dominates the market. But SonyLIV's programmatic infrastructure runs on SpringServe, and international publishers and some mid-tier Indian platforms use FreeWheel. Understanding these ad servers matters when a buyer wants to access inventory outside the JioHotstar-DV360 axis, or when troubleshooting delivery issues that trace back to ad server configuration.
What a CTV ad server does
An ad server is the publisher's decision engine for ad delivery. When a viewer starts a content stream and an ad break is triggered, the ad server receives the ad request, evaluates available demand sources (direct deals, PMP deals, programmatic auction), selects the winning ad, and instructs the SSAI system to stitch it into the content stream. The ad server controls:
- Waterfall order: which demand sources are called first, in what priority sequence
- Floor prices: minimum CPMs per inventory tier or deal type
- Frequency capping: how many times the same ad is served to the same device
- Brand safety and competitive exclusions: preventing advertiser conflicts or unsafe adjacencies
- VAST tag management: receiving and processing creatives from buyers
- Reporting: impression, completion, and error logging
For CTV specifically, ad servers must handle server-side ad insertion (SSAI) rather than client-side JavaScript — the ad stitching happens at the video stream level, not in the viewer's browser. This is why general-purpose web ad servers (older versions of DFP, some DoubleClick products) needed CTV-specific upgrades, and why specialised CTV ad servers gained market share.
SpringServe
SpringServe is a CTV-first ad server built specifically for streaming and OTT environments. It was acquired by Magnite in 2021, making SpringServe the ad server component of Magnite's sell-side stack for CTV publishers. The combination of SpringServe (ad decisioning) and Magnite (SSP/auction) gives publishers a vertically integrated CTV monetisation stack.
Key SpringServe capabilities relevant to India CTV:
- Unified auction: SpringServe runs a unified first-price auction across all demand sources simultaneously, rather than a sequential waterfall. This maximises yield by letting programmatic compete directly with direct deals at the impression level.
- SSAI integration: Native integration with server-side ad insertion, enabling seamless ad stitching without client-side execution. Reduces ad errors on CTV devices that don't support JavaScript.
- Deal management: Full deal ID management for PMP and preferred deals, with per-deal reporting and performance tracking.
- Competitive exclusions: Category-level competitive separation — prevents competing brands from appearing in the same ad pod or within a defined time window.
India CTV use: SonyLIV uses SpringServe as its primary CTV ad server, with Magnite as its SSP. Programmatic buyers accessing SonyLIV inventory through The Trade Desk or DV360 transact via Magnite's SSP, which feeds through SpringServe for ad decisioning. Direct IO deals with SonyLIV's sales team are also managed through SpringServe for delivery and reporting.
FreeWheel
FreeWheel (a Comcast company) is the dominant ad server for broadcast and cable TV networks in the US and is widely used by premium video publishers globally. FreeWheel's strength is its deep integration with traditional TV ad workflows — guaranteed deals, upfront commitments, competitive separation, and broadcast-grade ad decisioning — which makes it attractive to publishers whose inventory originated as linear TV and migrated to streaming.
FreeWheel capabilities relevant to CTV:
- TV-first deal structures: FreeWheel natively supports upfront/scatter deal models and guaranteed delivery commitments that align with how TV inventory has historically been sold
- MRM (Media Rights Management): Complex rights and exclusivity management for sports content — which league or brand has exclusivity in which region for which content type
- Cross-screen: Unified ad decisioning across linear TV, OTT, and digital, enabling publishers that span both to manage a single ad log across screens
- Programmatic integration: Connects to SSPs (including Magnite and PubMatic) for programmatic demand alongside direct-sold deals
India CTV use: FreeWheel has limited direct deployment among India's domestic OTT publishers. Its primary India relevance is through international content providers who use FreeWheel globally and whose content appears on India platforms. Some media conglomerates with global operations (Sony Pictures Networks, historically) have used FreeWheel components for their linear-to-digital ad workflows.
vs Google Ad Manager for CTV
Google Ad Manager (GAM) is the dominant CTV ad server globally and in India through JioHotstar. GAM's advantage over SpringServe and FreeWheel for India CTV publishers is its deep integration with Google's demand ecosystem — DV360, Google Ads, YouTube — which provides access to the largest pool of programmatic demand.
| Feature | Google Ad Manager | SpringServe | FreeWheel |
|---|---|---|---|
| Primary strength | Google demand ecosystem access | CTV-native unified auction | TV-first deal structures |
| SSAI | Google DAI | Native SpringServe SSAI | FreeWheel SSAI |
| Programmatic | Via DV360/Google Ads primarily | Via Magnite SSP and open market | Via connected SSPs |
| India CTV publisher | JioHotstar | SonyLIV | Limited India deployment |
| Buyer access DSP | DV360 (primary) | TTD, DV360 via Magnite | Via connected DSPs |
India publisher ad server stack
The India CTV sell-side ad server landscape by publisher:
- JioHotstar: Google Ad Manager + Google DAI (SSAI). Programmatic demand via DV360 (primary) and select SSP connections. Direct IO via JioHotstar sales team managed in GAM.
- SonyLIV: SpringServe (ad server) + Magnite (SSP). Programmatic via TTD and DV360 through Magnite. Direct IO via SonyLIV sales team managed in SpringServe.
- Zee5: PubMatic (SSP with ad server functionality for programmatic). Direct IO via Zee5 sales team. PubMatic acts as both SSP and programmatic ad server for Zee5's digital inventory.
- MX Player / OP (now owned by Times Internet): Uses a combination of GAM and SSP connections for programmatic CTV inventory.
- Samsung TV Plus India: Uses Samsung Ads' own ad server for its FAST channel inventory, with DV360 and TTD access via Samsung Ads' programmatic marketplace.
What buyers need to know
The ad server stack matters to buyers in three practical ways:
- DSP access path: Knowing which ad server a publisher uses tells you which DSP gives you the best access. JioHotstar = DV360 is the primary route. SonyLIV = TTD or DV360 via Magnite. Zee5 = TTD or DV360 via PubMatic. Using the wrong DSP for a publisher can result in lower priority or limited inventory access.
- VAST error diagnosis: VAST errors in CTV are often ad server-specific. A VAST 403 error on SonyLIV inventory traces to SpringServe's validation; a VAST 201 error on JioHotstar traces to Google DAI. The error code's meaning and the fix differ by ad server — knowing which system generated the error is the first step in diagnosis.
- Deal ID setup: PMP Deal IDs are configured in the publisher's ad server. A Deal ID for SonyLIV inventory is set up in SpringServe and activated in Magnite; a Deal ID for JioHotstar is configured in GAM. The setup process, testing methodology, and troubleshooting path differ by ad server.
Related articles
- Google Ad Manager for CTV publishers
- SSPs in India CTV: Magnite, PubMatic, and their roles
- Magnite and PubMatic in India CTV
- Server-side ad insertion (SSAI) for CTV
- Setting up Deal IDs for CTV campaigns
For related FAQs, see Which SSPs operate in India CTV? and What is SSAI in CTV?