Frequency capping is the mechanism that limits how many times a single viewer (or household) sees the same ad within a defined time period. In display advertising, frequency caps are enforced via cookies — a straightforward, reliable mechanism. In CTV, there are no cookies, multiple viewers share a single device, and inventory is spread across multiple publishers and DSPs that do not share impression data. The result: frequency control in CTV is genuinely difficult, frequently misconfigured, and one of the leading causes of viewer fatigue complaints in India CTV campaigns.
Why frequency matters in CTV
CTV ads are non-skippable and played at high volume in an immersive environment. A viewer who sees the same 30-second ad four times in a single evening will develop negative brand sentiment — the opposite of the campaign's intent. This is not a hypothetical: frequency overexposure is consistently cited in post-campaign research as the top negative viewer experience driver in India CTV.
The risk is amplified in India because: CTV reach is concentrated (a relatively small number of publishers hold the majority of CTV viewing), households watch together (so impressions accumulate at the device level faster than they would for individual viewers), and campaign budgets are sometimes concentrated in short flights that push delivery pace to meet spend goals.
Industry research suggests the effective frequency range for CTV brand campaigns is 3–5 exposures per week per household. Above 7–8 exposures per week, recall does not improve and brand sentiment can decline.
How CTV frequency capping works
CTV frequency capping uses device identifiers rather than cookies:
- Device IFA (Identifier for Advertisers): The primary frequency signal. Each CTV device (Android TV, Fire TV, smart TV with AIFA) has an advertising ID that is persistent until the user resets it. The DSP tracks impressions delivered to each IFA and stops bidding when the cap is reached within the specified window (e.g. 3 per day, 10 per week).
- IP address: A secondary signal used when IFA is not available (e.g. some Samsung/LG smart TV environments, or when the user has opted out of ad tracking). IP-based frequency capping is household-level, not device-level, but provides a fallback when IFA is absent.
- Publisher-side capping: Some publishers enforce frequency caps at the ad server level (Google Ad Manager for JioHotstar, Magnite for SonyLIV) independently of the DSP. Publisher-side caps are most reliable for within-publisher frequency control.
Why CTV frequency is harder than display
Several structural factors make CTV frequency control imprecise compared to display:
- No cross-publisher frequency sync: If a brand is buying on JioHotstar (via DV360/AdX) and SonyLIV (via Magnite/TTD) simultaneously, there is no shared frequency counter between the two supply paths. A household can receive 3 impressions from JioHotstar and 3 from SonyLIV on the same day and both DSPs will report they respected a 3/day cap — but the household saw 6 impressions. Cross-publisher frequency management requires a household graph or identity solution, which is nascent in India.
- IFA opt-out: Viewers who reset their advertising ID or opt out of ad tracking are effectively anonymous. The DSP treats each impression as a new device, making frequency caps unenforceable for opted-out devices. India CTV IFA opt-out rates are lower than mobile (most viewers do not adjust this setting) but not zero.
- Household vs individual: One IFA represents one device shared by multiple viewers. A household frequency cap of 5/week might represent 5 impressions to a single heavy viewer, or 1 impression each to 5 different family members. DSPs have no way to distinguish these scenarios.
- SSAI-side delivery: For SSAI publishers, frequency counting may occur on the server rather than the device, and the SSP's frequency data is not always available to the buying DSP in real time. This creates lag in frequency enforcement — the cap may be exceeded before the SSP's data propagates to the DSP's bid suppression logic.
Frequency capping in India CTV
Practical guidance for India CTV frequency management:
- Set DSP-level caps conservatively: Given the cross-publisher leakage described above, set individual publisher/DSP frequency caps lower than your total campaign target. If your goal is 5 impressions per household per week across all publishers, set each DSP to 3/week rather than 5 — the cumulative total will naturally run higher.
- Use daypart caps alongside weekly caps: Setting both a daily cap (e.g. 2/day) and a weekly cap (e.g. 5/week) prevents a single heavy-viewing evening from exhausting the week's frequency budget in one session.
- Monitor completion rate as a frequency proxy: A campaign with rising VAST 402 errors or declining VCR over time often signals frequency fatigue — viewers who have seen the ad many times are exiting the app rather than watching it again. This is not a perfect proxy but it is a detectable signal in DSP reporting.
- Negotiate publisher-side frequency caps for PMP deals: When activating a PMP deal with JioHotstar or SonyLIV, ask the publisher to apply a server-side frequency cap as part of the deal parameters. This is the most reliable frequency control available for within-publisher buying and is available on request for most large campaigns.