India's CTV ecosystem runs on six distinct operating systems — Android TV, Google TV, Amazon Fire OS, Samsung Tizen, LG webOS, and a long tail of proprietary OS on Indian OEM smart TVs. Each has different app stores, device identifier types, VAST implementation quality, and programmatic capabilities. This fragmentation is the defining technical challenge of India CTV advertising. A campaign that works cleanly on JioHotstar's Android TV app may have delivery gaps, tracking failures, or targeting mismatches on a budget Indian smart TV running a proprietary OS.
India CTV device mix and OS distribution
Precise India CTV device OS share figures are not publicly audited, but industry estimates from programmatic data suggest the following distribution for 2025–2026:
| OS / Platform | Estimated India CTV share | Primary devices | Device ID type |
|---|---|---|---|
| Android TV / Google TV | 55–65% | Xiaomi, Sony, TCL smart TVs; Chromecast with Google TV; Mi Box | GAID |
| Amazon Fire OS | 8–12% | Amazon Fire TV Stick, Fire TV Cube | AFAI |
| Samsung Tizen | 8–10% | Samsung Smart TVs | TIFA |
| LG webOS | 4–6% | LG Smart TVs | LGUDID |
| Indian OEM proprietary OS | 10–18% | VU, Thomson, Kodak, Acer TVs; Jio set-top boxes | Variable — often no standard IFA |
| Other (tvOS, Roku, etc.) | <3% | Apple TV, Roku devices | IDFA (ATT-limited) / RIDA |
The key divide is between GAID-based devices (the majority, sharing the same identifier ecosystem as Android mobile) and everything else. The programmatic stack, identity matching, and frequency capping all work most reliably on GAID devices. Non-GAID devices require either a different identifier integration or contextual/IP-based targeting.
Creative compatibility issues across device types
MP4/H.264 at 1080p is the baseline that every CTV device can play. Problems arise when buyers or agencies submit creatives that fall outside this baseline:
HEVC (H.265) rejection on older Android TV devices: H.265 offers better compression at the same quality, but hardware decoding support varies significantly across Android TV generations. Devices from 2017–2020 often lack H.265 hardware decode. A creative encoded in H.265 may play correctly on a 2023 Xiaomi smart TV but drop frames or fail to load on a 2019 budget Android TV device. MP4/H.264 is safe across all device generations.
Audio level compliance: CTV apps on Samsung Tizen and LG webOS are more likely to enforce the -24 LUFS audio normalisation standard than Android TV apps, which vary by publisher implementation. Creatives with audio mastered for broadcast (typically -23 LUFS) are close enough. Creatives from digital campaigns mixed for mobile playback (often -14 to -16 LUFS) will be noticeably louder on Tizen and webOS and risk viewer complaints.
Bitrate limits on Indian OEM smart TVs: Budget Indian smart TVs often have slower internal network stacks and limited memory buffers. A 5 Mbps creative that loads instantly on a Xiaomi or Samsung may buffer on a VU or Thomson smart TV. The 2–3.5 Mbps sweet spot covers the widest device range while maintaining acceptable visual quality at 1080p.
Targeting across fragmented device types
Audience targeting works differently across device OS families because the identifier types do not match:
- GAID (Android TV / Google TV): Matches directly against GAID-based CRM uploads in DV360. Cross-device graphs linking GAID CTV to GAID mobile are robust. Frequency capping is reliable within Android TV inventory.
- AFAI (Fire TV): Amazon DSP reads AFAI natively. DV360 and TTD can use AFAI but cross-device matching to other GAID devices requires probabilistic inference. Fire TV frequency caps and audience segments are separate from Android TV.
- TIFA / LGUDID (Tizen / webOS): Targetable via Samsung Ads and LG Ads directly. In open programmatic via DSPs, TIFA and LGUDID can be used for frequency capping but do not match against GAID audiences. Samsung Ads has a household graph based on Samsung account logins that extends beyond TIFA.
- Indian OEM devices (no standard IFA): These devices represent 10–18% of India CTV inventory and are the most problematic for targeting. Without a consistent IFA, frequency capping relies on IP-based household inference. Audience matching is not possible. The programmatic VAST request may include a temporary session ID or leave the IFA field blank — buyers see these as anonymous impressions.
The practical result: a campaign with 10 million India CTV impressions is targetable via GAID on roughly 60% of those impressions, contextually/IP targetable on another 25–30%, and effectively non-targetable (anonymous device) on 10–15%. This anonymous fraction is not wasted reach — it is still a CTV impression on a living room screen — but it cannot be attributed to an audience segment or matched back to a CRM file.
Measurement fragmentation across device OS
Post-campaign measurement is fragmented in ways that matter for attribution:
View-through attribution: Works on GAID and AFAI devices where the identifier persists and can be matched to a post-view action. Does not work on no-IFA OEM devices — these impressions cannot be linked to subsequent conversion events.
Third-party verification (IAS/DoubleVerify): Verification SDKs are implemented in publisher apps. Android TV apps generally have OMID SDK integration, enabling third-party verification. OEM smart TV apps often do not — IVT verification on Indian OEM TV inventory depends on the publisher having explicitly integrated the measurement SDK on that platform.
VAST error rates by device type: CSAI VAST error rates are higher on older Indian OEM devices due to weaker network stacks and lower-quality VAST parser implementations. Error 301 (timeout) is disproportionately high on OEM inventory compared to mainstream Android TV.
Practical guidance for India CTV buyers
- Ask publishers for a device OS breakdown of their CTV inventory. Before committing budget, understand what share is Android TV, Samsung, and OEM. A publisher with 40% OEM device share will have materially lower targetability and higher VAST error rates than one with 80% Android TV.
- Specify MP4/H.264 at 2–3.5 Mbps for maximum device compatibility. Do not submit H.265 for India CTV without confirming device support with the publisher.
- Do not rely on frequency caps alone for OEM-heavy inventory. If 15% of your impressions are on no-IFA devices, your frequency cap is not enforced on those devices. Plan for over-exposure in OEM-heavy environments by buying fewer total impressions than you would on a clean Android TV environment.
- Segment campaign measurement by device type in reporting. If your DSP allows device OS breakouts, compare completion rates, VAST error rates, and win rates separately for Android TV vs OEM inventory. The difference often explains apparent under-delivery.