CTV device IDs are the primary signal for frequency capping, audience targeting, and attribution on connected TV screens. Unlike mobile where nearly every ad request carries a GAID or IDFA, CTV has lower device ID availability — roughly 60–75% of India CTV ad requests carry a usable IFA. The rest fall back to IP-based household signals. Understanding why, and what each ID type enables, is foundational for anyone configuring CTV campaigns or troubleshooting frequency cap failures.
Device IDs on CTV: the basics
A device ID on CTV is a persistent, resettable identifier tied to the TV device or operating system — not to an individual user account. It is called an IFA (Identifier For Advertisers) in OpenRTB. The IFA travels in the device.ifa field of every OpenRTB bid request and is used by DSPs for:
- Frequency capping — Limiting how many times a household sees a specific ad
- Audience matching — Matching the device to an audience segment in the DSP's data graph
- Attribution — Linking a CTV ad exposure to a subsequent conversion on the same household's devices
- Cross-publisher deduplication — Identifying that two impressions (JioHotstar + SonyLIV) were served to the same household
GAID on Android TV
Android TV — the OS powering most India smart TVs from Sony, TCL, Hisense, Philips, and many brands sold on Flipkart and Amazon — uses the GAID (Google Advertising ID) as its IFA. This is the same GAID framework used on Android mobile, but tied to the TV device rather than a phone.
GAID on Android TV characteristics:
- Persistent until the user resets it in Android TV settings (Settings → About → Ads → Reset Advertising ID). Most users never do this.
- Can be opted out — the user can enable "Opt out of Ads Personalisation" in the same settings menu. An opted-out GAID still passes in the bid request but is flagged as
lmt: 1(Limit Ad Tracking) in OpenRTB. DSPs respect this flag and serve contextual-only ads. - Shared across all users of the TV device — it is a household identifier, not a personal one. Everyone who watches the same Android TV shares the same GAID.
Android TV accounts for approximately 70–75% of India CTV device inventory. GAID availability on Android TV is high (~85–90% of requests when the user has a Google account linked to the device).
IFA types across CTV platforms
| Platform | IFA type | OpenRTB ifa_type | India prevalence |
|---|---|---|---|
| Android TV (Sony, TCL, Hisense etc.) | GAID | gaid | ~70–75% of India CTV devices |
| Google TV (Chromecast, newer Android TV) | GAID | gaid | Growing; part of Android TV ecosystem |
| Amazon Fire TV Stick | AFAI (Amazon Fire TV Advertising ID) | afai | ~10–15% of India CTV devices |
| Samsung Tizen (Smart TV OS) | TIFA (Tizen IFA) | tifa | ~5–8% |
| LG webOS | LGUDID (LG User Device ID) | lgudid | ~3–5% |
| Apple TV (tvOS) | IDFA | idfa | <2% in India |
DSPs handle each IFA type differently. DV360 is optimised for GAID (Google's own ecosystem). TTD supports all major IFA types via its identity graph. For cross-platform frequency capping, the DSP must recognise and deduplicate across GAID, AFAI, and TIFA — which requires the DSP's identity graph to have crosswalk mappings between ID types. This is available in TTD and DV360 for the major India platforms but is imperfect for household-level deduplication across Android TV and Fire TV simultaneously.
Why device ID availability is lower on CTV
Compared to mobile (~95% GAID availability on Android), India CTV has lower IFA availability (~60–75%). Reasons:
- No mandatory Google account sign-in: An Android TV can be used without signing in to a Google account. Without a Google account, GAID generation requires the user to sign in or set up Google Play. Many budget Android TV users skip this step.
- Shared Google accounts: A family may set up the Android TV with a Google account, then reset or remove it. The GAID becomes unavailable until the account is re-linked.
- Older firmware: Older Android TV devices (Android TV 7 or earlier) may have buggy GAID generation. Budget smart TVs sold in India at ₹8,000–12,000 often run older firmware versions.
- Sideloaded apps: Some India users sideload OTT apps outside the Google Play Store. Sideloaded apps on Android TV may not access GAID through the standard API.
- LMT (Limit Ad Tracking) flags: A small but growing proportion of India CTV users have opted out. These impressions carry a GAID but it is flagged as LMT — effectively not targetable for personalised ads.
IP address as the fallback signal
When a CTV bid request arrives without a usable IFA, the DSP falls back to the IP address for frequency capping and household identification. IP-based household matching is less precise:
- Works well for fixed broadband (JioFiber, Airtel fiber) where the IP is stable per household
- Fails for mobile hotspot connections (dynamic carrier IPs, shared across users)
- Unreliable in dense urban areas where building-level shared IPs are common
IP-based frequency capping is applied at the IP level, not the device level. If a household has a stable IP and one CTV device, IP-based capping is functionally equivalent to device-level capping. If a household has a dynamic IP, the same device may be counted as a new household after each IP rotation — blowing through frequency caps.
Frequency capping with device IDs
Device ID-based frequency capping on CTV is household-level, not person-level. A household of 4 with one Android TV device all share the same GAID. A frequency cap of 3 per device = 3 ad exposures to all 4 household members combined — not 3 per person.
Implications for India CTV planning:
- Set frequency caps lower than on mobile to account for household co-viewing. A cap of 3 per device on a 3-person co-viewing household = 9 total person-exposures.
- For reach-maximisation campaigns, IFA-based frequency capping on CTV is more reliable than on mobile (where users switch between apps and devices). A CTV household tends to stay on the same device and same app — frequency capping works as designed.
- Cross-publisher frequency capping (limiting total exposure across JioHotstar + SonyLIV) requires both publishers to pass the same IFA type to a DSP with cross-publisher graph capability. In practice, this works via DV360 (JioHotstar + YouTube CTV) or TTD (SonyLIV + Zee5), but not seamlessly across both ecosystems simultaneously.
India-specific device ID context
India's smart TV market is price-sensitive and Android TV-dominated. The implication: GAID is the dominant IFA for India CTV, making DV360's GAID-native ecosystem well-suited for India CTV frequency management and audience matching. TTD's cross-platform graph adds value for brands buying across SonyLIV and Zee5, which are not in the Google ecosystem.
The DPDPA (India's Digital Personal Data Protection Act, 2023) treats advertising identifiers — including GAID on CTV — as personal data when used for targeting. Publishers passing GAID in bid requests need a valid consent basis. As of 2026, India CTV publishers are navigating compliance implementation, and consent management for CTV device IDs remains an evolving area. See the DPDPA and CTV advertising article for the current compliance framework.