Frequency measurement in India CTV determines how many times the same household or device has been exposed to a campaign. Getting frequency right — neither too low (insufficient impact) nor too high (wasted spend and viewer irritation) — is one of the most direct optimisation levers available in programmatic CTV. But frequency measurement in India has real constraints that must be understood before acting on the numbers in campaign reports.
What frequency reports actually measure in India CTV
A frequency report from a DSP shows the average number of impressions served per unique device ID. If a campaign served 10 million impressions to 2 million unique device IDs, average frequency is 5. But this number has important caveats:
Device-level, not household-level: Frequency is counted per device ID. If the same household has two CTV devices (a smart TV and a streaming stick), and each receives impressions, the household frequency is the sum of both — but the DSP reports them as two separate device IDs with frequency of their own. Household-level frequency is higher than device-level frequency when multi-device households are in the campaign.
Device IDs without impressions are invisible: Impressions served to device IDs without a valid ID (approximately 30–40% of India CTV impressions) are not included in the frequency distribution. The average frequency shown is only for the tracked fraction of inventory.
Single-publisher view: DSP frequency reports only include impressions within the DSP's visibility. A household that received 3 impressions via DV360 and 4 impressions via a direct JioHotstar campaign appears as frequency 3 in the DV360 report — the DV360 system has no visibility into the JioHotstar direct impressions.
Optimal frequency ranges for India CTV
| Campaign objective | Recommended frequency (per device per week) | Notes |
|---|---|---|
| Brand awareness (new campaign) | 3–5 | Sufficient for recognition; minimises irritation |
| Brand awareness (sustain) | 2–3 | Maintenance level after initial exposure |
| Product launch / key message | 5–7 | Higher frequency justified for short-burst launches |
| Performance / app install | 1–3 | Lower frequency; performance decision happens once |
| Live event / sports sponsorship | No cap needed during event; cap post-event | Event frequency is natural; post-event cap at 3–5/week |
Diagnosing frequency problems in India CTV campaigns
Over-frequency (high average frequency with low unique reach): Occurs when the addressable inventory pool is too small relative to the budget. The campaign keeps serving the same device IDs because there are not enough new unique devices to reach. Fix: expand geographic targeting, add publishers, reduce daily CPM bids to slow pacing and extend reach duration.
Under-frequency (high unique reach but low completion rates): Indicates the campaign is buying too broadly, serving single impressions across many devices without building cumulative message impact. Fix: reduce unique reach targets or introduce frequency floors (minimum 2 impressions per device before moving to new devices).
Cross-publisher frequency management in India
True cross-publisher frequency management in India CTV requires a unified identity layer across all publishers — which does not currently exist. The practical workaround: manage frequency within each publisher independently (3–5 impressions per device per week per publisher), and assume 20–30% of households are reached by multiple publishers, receiving combined frequency above the per-publisher cap. For campaigns with strict frequency requirements, reduce individual publisher caps to account for multi-publisher overlap.