CTV devices use advertising identifiers — resettable, privacy-preserving IDs — to enable audience targeting without requiring logged-in identity. In India's programmatic CTV ecosystem, device IDs are the primary signal for open-market buying when platforms do not pass logged-in user IDs to the DSP. Understanding how these IDs work, where they break, and what they cannot do is foundational to building CTV targeting strategy.
The major device identifiers on India CTV
Samsung TIFA (Tizen Identifier for Advertising)
Samsung is the largest smart TV manufacturer in India by revenue. Samsung smart TVs running Tizen OS generate a TIFA — a device-level advertising identifier similar to mobile's GAID (Google Advertising ID). TIFA is:
- Persistent until the user resets it in TV settings (Settings → Privacy → Reset Advertising ID)
- Accessible to apps running on the TV and to Samsung Ads (Samsung's advertising platform)
- Used for frequency capping, audience targeting, and attribution within Samsung's ad ecosystem
- Available to advertisers buying through Samsung Ads directly or through DSPs integrated with Samsung's supply
Fire TV Advertising ID
Amazon's Fire TV Stick is one of India's most popular streaming devices. The Fire TV advertising ID functions similarly to TIFA — resettable, device-level, available to apps and to Amazon's DSP (Amazon DSP / Amazon Ads). Fire TV IDs are particularly valuable because Amazon can correlate them with Amazon.in shopping behaviour, Prime membership, and delivery address data.
LG Advertising ID
LG TVs running webOS have their own advertising identifier, accessible through LG Ad Solutions. Less commonly integrated into India's programmatic ecosystem than Samsung or Fire TV, but available for direct buys through LG's ad platform.
Android TV / Google TV Advertising ID
Devices running Android TV or Google TV (many mid-range and budget smart TVs, plus Chromecast with Google TV) use the Android advertising ID — the same GAID used on mobile. This is the most familiar ID for programmatic buyers and is accessible through DV360, The Trade Desk, and other DSPs with Android TV inventory.
How device IDs flow through the programmatic stack
When a CTV device loads an app and an ad request is made:
- The app sends an ad request to the SSP (supply-side platform) or ad server, including the device's advertising ID
- The SSP sends a bid request to connected DSPs, including the device ID and available targeting signals (content, geo, device type)
- The DSP matches the device ID against its audience segments or frequency caps
- If the device ID matches a target audience segment or has not exceeded the frequency cap, a bid is placed
- The winning bid's creative is served to the device
This flow works when the device ID is present in the bid request. In practice, ID availability varies: some apps do not pass device IDs (particularly if the user has opted out), some integrations drop the ID in transit, and some publishers strip IDs for privacy reasons.
Limitations of device IDs for CTV in India
- Household-level, not individual-level: A device ID represents a TV set, not a person. In co-viewing households, the same ID covers 3–5 people. Frequency caps applied to device IDs over-expose households.
- Opt-out: Users can reset or opt out of device advertising IDs. Reset rates are low in India (TV privacy settings are obscure to most users) but growing as awareness increases.
- No cross-device linkage without additional data: A Samsung TIFA and a mobile GAID in the same household are not automatically linked. Cross-device identity requires an additional identity layer (IP matching, logged-in account).
- Walled gardens do not share IDs: JioHotstar's logged-in user data does not pass to the open programmatic ecosystem. When you buy JioHotstar inventory through a DSP, you may get an IP address or limited contextual signals — not the full subscriber profile JioHotstar holds.
- Signal loss is increasing: Privacy regulation and platform policy changes (paralleling mobile's IDFA deprecation trajectory) are reducing device ID availability over time. India's DPDPA will likely accelerate this.
What this means for India CTV buyers
- Device ID-based targeting works best for frequency capping and broad demographic/contextual targeting — not for precise individual-level audience cuts
- For precise audience targeting, prefer logged-in platforms (JioHotstar, YouTube, Amazon) bought through their native tools where the full first-party identity is available
- Do not assume device ID match rates of 90%+ — plan for 60–80% ID availability in programmatic CTV buys in India
- Build contingency for IP-based fallback targeting for impressions where device IDs are not available