Third-party audience data for CTV targeting in India is thinner than mobile and significantly more fragmented. Unlike mobile where cookie-based and MAID-based data markets are well developed, CTV in India relies on a combination of telco-derived data, panel-based segments, and publisher first-party data licensed to DSPs. For most India CTV campaigns, third-party data provides directional targeting rather than precision reach.
What is third-party data in CTV advertising
Third-party data is audience segment information collected by a party that has no direct relationship with the advertiser or the publisher serving the ad. In digital advertising, this includes data aggregators, data brokers, and data management platforms (DMPs) that collect consumer behaviour signals across properties, bundle them into segments (e.g., "auto intenders," "new parents," "affluent urban"), and make them available to buyers through DSP integrations.
In CTV, these segments are matched to device IDs. When an advertiser activates a third-party segment in a DSP, the DSP bids on impressions where the device ID (GAID, AFAI, or similar) matches the segment. The match rate — how often an impression has a device ID that appears in the segment — determines effective reach.
Third-party data providers in India
The India third-party data ecosystem for CTV is limited relative to the US or UK. Key providers:
- Jio platforms data (via JioAds): JioFiber subscriber data — income proxy, location, broadband usage patterns. Available only for JioHotstar inventory through JioAds direct buying, not through open programmatic DSPs.
- Airtel Ads data: Airtel's telco subscriber segments — location, data usage, postpaid vs prepaid, roaming. Available for Airtel Xstream inventory and select DSP integrations.
- BSNL data: Not practically available for programmatic activation.
- Oracle Advertising (formerly BlueKai): India intent and demographic segments. Available in DV360 and TTD data marketplace. Coverage on CTV is limited — primarily mobile-derived segments matched to GAID where overlap exists.
- Nielsen India segments: Panel-derived demographic and purchase segments. Used primarily in direct IO deals with premium publishers. Not widely available in open programmatic.
- Experian India: Credit bureau-derived segments (income, financial product ownership). Available in select DSPs. Match rate on CTV device IDs is lower than on mobile.
- Lifesight: India-focused data provider offering location and behavioural segments built from mobile signals. Has GAID-based matching that works on Android TV in India. More current than legacy DMP segments for India.
How third-party data reaches a CTV DSP
Third-party data flows into CTV targeting through the DSP data marketplace. The path:
- Data provider collects signals from their sources (telco records, panel, credit, location)
- Signals are tied to device IDs (GAID on Android, IDFA on iOS/tvOS, AFAI on Fire TV)
- Segments are uploaded to or integrated with the DSP's data marketplace
- Buyer selects the segment in the DSP targeting UI — typically under "Audience" or "Third-party data"
- On each impression, the DSP checks whether the device ID matches the segment before bidding
The match rate between a third-party segment and India CTV inventory is typically 20–40% — meaning the segment can only be applied to that fraction of available impressions. This is lower than mobile (60–80% match rates are common) because India CTV device IDs are less consistently passed in bid requests, and third-party segments are primarily built from mobile signals.
Limitations: CTV vs mobile targeting
| Dimension | Mobile (India) | CTV (India) |
|---|---|---|
| Device ID availability | 75–85% of impressions | 50–65% of impressions |
| Third-party segment match rate | 60–80% | 20–40% |
| Data freshness | Days to weeks | Weeks to months |
| Cross-device linkage | Strong (mobile-to-mobile) | Weak (mobile-to-TV) |
| Telco data availability | Broad (Jio, Airtel, Vi) | Limited to Jio/Airtel direct |
| Purchase intent signals | Moderate (app behaviour) | Low (content-based only) |
The core limitation is that CTV device IDs exist in a largely separate identity graph from mobile. A consumer browsing for a car on their phone accumulates intent signals on their GAID (Android) or IDFA (iOS). That GAID may not be linked to their Android TV's GAID unless the household graph explicitly connects them. Most India households are not in any household graph with verified cross-device linkage.
Practical guidance for India CTV campaigns
Given the limitations, India CTV buyers use third-party data in specific ways:
- Use it for exclusion, not only inclusion: Third-party segments can be used to suppress impressions to existing customers or competitive converters. This requires smaller match rates and is less sensitive to data freshness.
- Layer geo + third-party: Combining state-level geo with a broad demographic segment (e.g., SEC A/B in Maharashtra) narrows reach in a way that doesn't require high individual-level match rates.
- Prefer publisher first-party over third-party: JioHotstar's registered user data and SonyLIV's subscriber segments are more reliable for India CTV than external third-party segments. These are available as publisher audience deals, not third-party marketplace purchases.
- Treat third-party as directional: Don't over-optimize toward segment match rate at the expense of reach. On India CTV, restricting to matched impressions only often results in thin delivery and poor pacing.
- Check DPDPA compliance: India's Digital Personal Data Protection Act (2023) affects how third-party data providers can lawfully collect and share Indian consumer data. Verify that any third-party segment used for India CTV was built on lawfully obtained consent.
The most effective India CTV targeting is typically contextual (content genre, language, platform) layered with publisher first-party data — not third-party segments. Third-party data's role is narrower here than on mobile.