First-party data activation for CTV retargeting means taking audiences you already own — your CRM database, website visitors, app users, past purchasers — and reaching them on Connected TV screens. In India, this translates to matching your customer records against JioHotstar, SonyLIV, and Zee5 logged-in user graphs, then serving CTV ads to households where a match is found. Done correctly, it delivers CPMs of ₹180–400 against audiences with demonstrated purchase intent rather than modelled demographic proxies.
What first-party data activation means for CTV
CTV retargeting is structurally different from browser retargeting. There are no cookies on a TV screen. The matching mechanism is identity-based: your customer's email or phone number is hashed, uploaded to a DSP or publisher data platform, and matched against the platform's logged-in user graph. When a match is found, that household's CTV devices become targetable.
The typical first-party data sources used for CTV activation in India:
- CRM email/phone lists — existing customers, lapsed buyers, loyalty programme members
- Website pixel audiences — product page visitors, cart abandoners, checkout starters who did not convert
- App event audiences — app installers who did not purchase, high-engagement users, churned subscribers
- CDP-built segments — behavioural segments combining online and offline signals (e.g., high-LTV customers, category intenders)
- Offline transaction data — POS purchase history, store visitors matched via loyalty card email
CTV retargeting is most effective for mid-funnel to lower-funnel goals: re-engaging lapsed users, accelerating consideration for high-intent prospects, cross-selling to existing customers. It is less suited to pure reach or awareness, where contextual or demographic targeting is more efficient.
From CRM data to CTV audience segment
The standard workflow for CRM-to-CTV activation:
- Export and hash — Export customer email and phone records from your CRM. Apply SHA-256 hashing before upload. Never send plaintext PII to a DSP or data platform.
- Upload to DSP customer match — DV360 uses Customer Match (same mechanism as Google Ads); TTD uses UID2.0 or its own match API. Upload the hashed list as a first-party audience segment.
- Match rate realisation — The DSP matches your list against its identity graph. In India, match rates on DV360/JioHotstar are typically 30–50% for email lists (lower for phone-only lists). TTD against SonyLIV/Zee5 is typically 20–40%.
- Segment becomes targetable — Matched users are added to a CTV-targetable segment. You select this segment in campaign setup alongside CTV inventory targeting.
- Layer suppression if needed — You can suppress existing customers from an acquisition campaign, or suppress recent converters from a retargeting campaign, using the same mechanism.
Match rate is the key variable. A 100,000-record CRM list at 35% match rate yields ~35,000 matched households — at 2+ people per household, meaningful CTV reach. Lists below 10,000 records are too small: the matched segment will underdeliver or not reach statistical significance for measurement.
CDP to CTV activation workflow
A Customer Data Platform allows you to build behavioural segments from combined data sources before activation. CDPs commonly used by India advertisers include Segment (Twilio), mParticle, Clevertap, and WebEngage. The activation path to CTV:
- Segment → DV360: Twilio Segment has a native Google Ads / DV360 destination. Audiences built in Segment sync directly to DV360 as Customer Match segments and are available for CTV targeting within 24–48 hours.
- Segment → TTD: Via the TTD integration in Segment's destination catalogue. Segments sync to TTD's first-party data library.
- Clevertap / WebEngage → programmatic: These India-native CDPs typically export via CSV or webhook. Export the audience, hash, and upload manually to DV360 or TTD. Native programmatic integrations are less mature than Segment/mParticle.
CDP activation adds value over raw CRM export when you need dynamic audiences — segments that update in real time as users enter or exit qualification criteria (e.g., "added to cart in last 7 days"). Static CRM exports go stale within weeks.
Website visitor retargeting on CTV
Website pixel audiences can be activated on CTV through IP-based household matching rather than cookie-based matching. The mechanism:
- A visitor lands on your website. The browser pixel fires and records the visitor's IP address alongside the page event.
- The DSP (DV360 or TTD) maintains a real-time IP-to-household mapping. The visitor's IP is matched to a household profile.
- CTV devices in that household become retargetable for a defined window (typically 7–30 days).
This is the IP-based pixel attribution mechanism described in detail in the pixel attribution for CTV in India article. For retargeting purposes, the same limitations apply: mobile hotspot IPs do not reliably link to a home CTV screen, dynamic IP rotation in dense urban areas reduces match accuracy, and shared IPs in offices or co-working spaces create false positives.
For India CTV retargeting, IP-based website visitor audiences work best when the website traffic is predominantly home broadband (walled neighbourhoods, tier-1 city users on JioFiber or Airtel fiber). Mobile-heavy traffic — the majority of India web traffic — has a much lower CTV household match rate.
Activation via DV360 and TTD
DV360 + JioHotstar is the most mature first-party data activation path in India CTV. JioHotstar uses Google Ad Manager with DV360 as the primary programmatic demand channel. DV360 Customer Match segments can be layered onto JioHotstar CTV inventory in a Display & Video 360 Insertion Order targeting configuration. Match rates are higher here because the Google identity graph (Gmail, Google accounts) has strong overlap with JioHotstar's logged-in user base (Reliance account / JioID login).
TTD + SonyLIV / Zee5 is the alternative path for non-JioHotstar inventory. TTD's UID2.0 framework allows hashed email-based audience activation across participating publishers. SonyLIV and Zee5 both work with TTD. Upload your hashed email list to TTD's audience library, create a first-party data segment, and layer it onto CTV targeting in campaign setup.
Neither path gives you cross-publisher deduplication. If you run DV360 for JioHotstar and TTD for SonyLIV/Zee5 simultaneously, the same customer household may be reached on both platforms with no coordination. Budget accordingly — treat them as separate reach pools unless you have a frequency cap mechanism in place.
India-specific challenges
Phone-number-dominant CRM records. Most India CRM databases have phone numbers, not email addresses. Phone-to-CTV match rates are lower than email on DV360 because Google's identity graph is email-anchored. TTD's UID2.0 also works from email. The workaround: enrich your CRM with email via login flows, loyalty programme enrolment, or payment-linked email capture at checkout.
Language mismatch in segmentation. India CDPs often store user language preference as a segment attribute, but CTV DSPs do not expose language as a first-party audience filter. You need to build language-based intent audiences upstream (e.g., segment users who engaged with Hindi content separately from Tamil content) and activate them as separate audience uploads.
DPDPA compliance. Under India's Digital Personal Data Protection Act (2023), you must have a valid consent basis before uploading customer PII (even hashed) to a third-party DSP or data platform. This means your consent capture at registration or purchase must include consent for use of personal data for advertising purposes. See the DPDPA and CTV advertising article for the full compliance framework.
Audience size minimums. DV360 and TTD enforce minimum audience sizes (typically 1,000 matched users) before a segment is eligible for CTV targeting. A small brand with a 5,000-person CRM at 30% match rate hits 1,500 matched users — viable, but barely. Audiences below minimum threshold are suppressed for delivery.
Measuring retargeting effectiveness
Retargeting effectiveness for CTV is measured differently from browser retargeting. There is no click-through rate. The primary metrics:
- Incremental site visit rate — Did exposed households visit your website at higher rates than unexposed households? Measured via geo holdout or DSP-native lift study.
- View-through conversion rate — Did exposed households complete a tracked conversion (app install, purchase, form fill) within the attribution window? Reported by the DSP but subject to all the correlation limitations in the pixel attribution article.
- Brand lift (for consideration) — Did exposed users show higher purchase intent or category consideration in a survey? Requires a minimum impression threshold (~₹25–50L spend) to reach statistical significance. See brand lift measurement for India CTV.
- CRM segment re-engagement rate — Did lapsed customers in the retargeted segment reactivate (purchase, renew, visit store) at higher rates than a holdout? This requires you to split your CRM segment before upload: 70% activated, 30% held out as control.
The most defensible measurement approach for India CTV retargeting: run a randomised holdout on your CRM segment before activation, measure post-campaign conversion rates in both groups, and compute incremental lift. This requires discipline at the audience upload stage but produces meaningful ROI evidence rather than correlation-heavy view-through attribution.
India first-party data activation benchmarks
| Metric | Typical range | Note |
|---|---|---|
| CRM match rate (DV360/JioHotstar) | 30–50% | Email-anchored lists; lower for phone-only |
| CRM match rate (TTD/SonyLIV/Zee5) | 20–40% | UID2.0 email-based; smaller India footprint |
| Website visitor CTV match rate | 10–25% | IP-based; mobile-heavy traffic reduces rate |
| Retargeting CPM premium vs open auction | 30–60% | Offset by higher conversion rates |
| Minimum list size for viable delivery | 5,000+ records | To clear DSP minimum matched threshold |