Audience & Data · First-Party Data

First-party data strategy for CTV advertising in India

Updated May 2026

First-party data is the most reliable targeting input for India CTV campaigns. Third-party data has low match rates on CTV device IDs. BARC does not cover streaming. Publisher MAU numbers are aggregated and cross-device. But a brand's own CRM data — customers, app users, purchasers — can be onboarded directly to a DSP and used to target or suppress specific audiences on India CTV. Building a first-party data strategy for CTV requires different data collection practices than for mobile or display.

Why first-party data matters for India CTV

The India CTV targeting landscape has three structural gaps that first-party data helps address:

  1. No independent audience currency: Without BARC covering streaming, advertisers rely on publisher-reported demographics. First-party data lets brands define their own audience, not accept the publisher's segment definition.
  2. Low third-party data match rates: External segments typically match 20–40% of India CTV impressions. First-party data — when properly onboarded — can achieve 30–60% match rates to CTV device IDs through GAIDs.
  3. DPDPA compliance pressure: India's Digital Personal Data Protection Act (2023) is tightening third-party data collection. Brands that have built first-party consent pipelines are better positioned as third-party data availability shrinks.

What first-party data to collect for CTV activation

The most actionable first-party data for CTV targeting:

  • Hashed email addresses: Collected via app registration, website login, loyalty programmes, purchase confirmation. This is the most universal identifier for DSP data onboarding.
  • Mobile phone numbers: Collected via OTP-based login (standard in India). Phone numbers can be hashed and matched against DSP identity graphs. In India, mobile numbers are more consistently linked to individual identity than email due to real-name SIM registration requirements.
  • App GAIDs (Android Advertising IDs): If the brand has a mobile app with >500K+ users, the app's GAID collection (with consent) directly matches to Android TV GAIDs in the same household graph. This is the most direct CTV targeting path.
  • Purchase behaviour segments: Segmenting CRM data by recency, frequency, and category (e.g., "purchased in last 90 days," "lapsed buyers," "high-value customers") enables campaign-level targeting and suppression strategies.

What doesn't work well for CTV onboarding: cookie-based segments from web analytics (cookies don't exist on CTV), device fingerprint data (not cross-device reliable), and third-party appended data that can't be re-consented under DPDPA.

Onboarding first-party data to a CTV DSP

The onboarding path for DV360 and The Trade Desk is similar:

  1. Export CRM identifiers: Extract hashed emails and/or phone numbers from CRM. Hash using SHA-256 (lowercase normalised). Most DSPs require SHA-256 hashing.
  2. Upload to DSP audience manager: DV360: Customer Match audience (Audience Manager → New audience → Customer Match). TTD: First-party data onboarding via UID2 (The Trade Desk's identity solution).
  3. Wait for match processing: DSPs typically take 24–48 hours to match uploaded identifiers against their identity graphs. Match rates are shown in the audience management dashboard.
  4. Apply to CTV line item: Set the custom audience as a targeting criterion on the CTV line item. Optionally layer with geo or content targeting.

Expected India CTV match rates from first-party data: hashed email → GAID: 25–45%; hashed phone → GAID: 30–55% (higher due to real-name mobile registration). GAID → Android TV GAID (household linkage): additional 20–35% step-down.

First-party data use cases for India CTV

  • Customer suppression: Exclude current active customers from a new-customer acquisition CTV campaign. Reduces wasted spend and improves incremental reach measurement.
  • Lapsed customer re-engagement: Target customers who purchased 3–12 months ago but haven't returned. CTV's high-attention environment is well-suited for brand reminders vs mobile's higher-intent but lower-attention format.
  • High-value customer lookalike: Upload top 10–20% of customers by spend; use DSP lookalike modelling to find similar audiences on CTV inventory. The base audience quality determines lookalike quality.
  • Sequential messaging: Identify CTV viewers who were exposed to an upper-funnel brand ad in the first 2 weeks, then serve a lower-funnel product-specific CTV ad in week 3–4. First-party data enables the segment definition for sequential targeting.

DPDPA compliance for first-party data

India's Digital Personal Data Protection Act (2023) requires that personal data — including names, emails, and phone numbers — is processed only with the data principal's (user's) consent or under a specified lawful basis. For advertising activation:

  • CRM data collected for one purpose (e.g., "to process your order") should not be reused for advertising targeting without separate consent or a compatible purpose assessment
  • Hashing data before upload does not remove the legal obligation — if the data was collected from Indian citizens, DPDPA applies
  • Consent language in app registration, loyalty programmes, and purchase flows should explicitly cover use for advertising personalisation

Brands that invest in proper consent architecture for their India user base now will have the most durable and legally defensible first-party data asset for CTV targeting as DPDPA enforcement matures.