Viewability in CTV means something structurally different from viewability in display or mobile. The MRC display standard — 50% of pixels in view for 1 continuous second — was built for a browser-based world where ads compete with page content for screen real estate. On CTV, the ad occupies the full screen during a forced break in content. Applying the display standard results in near-100% viewability rates that communicate nothing useful. The relevant question for CTV is not whether the ad was on screen, but whether a human was present to see it.
The MRC CTV viewability standard
The Media Rating Council (MRC) released CTV-specific viewability guidance in 2020. The standard: a CTV video ad impression is viewable if it meets all of the following:
- 100% of the ad pixels are within the display area (full screen — by definition true on CTV)
- The audio is on (not muted) or the ad is delivered in a context where audio is the primary engagement signal
- The video player is in focus (the app is active, not backgrounded)
In practice, this standard is difficult to measure on CTV because native TV apps do not expose browser-level pixel measurement. Verification vendors (IAS, DoubleVerify) measure CTV viewability through SDK integrations with publisher apps or through SSAI-layer beaconing — which requires the publisher to have integrated the measurement vendor's SDK. Publishers without SDK integration cannot provide third-party verified viewability data.
Audibility: the overlooked CTV viewability dimension
CTV viewing is almost always sound-on. Unlike mobile video (where 70%+ of consumption is muted), TV screens default to audio-on and CTV inherits that behaviour. This makes audibility a stronger proxy for ad exposure on CTV than pixel coverage.
Some India CTV publishers — particularly JioHotstar on mobile CTV (Chromecast, mobile-to-TV casting) — have inventory where the viewing environment is less predictable. For these placements, confirming audio-on rate alongside VCR is worth the additional reporting request.
Invalid traffic and bot detection on CTV
CTV has a specific IVT problem that display does not: app spoofing. Fraudulent apps can misrepresent their identity in bid requests, making low-quality or non-existent inventory appear as premium CTV publisher inventory. A DSP buying open auction CTV without app-list filtering may deliver impressions to spoofed apps that register as completions but have no human viewers.
IAS and DoubleVerify both offer CTV IVT detection through pre-bid targeting and post-bid verification. GroupM's Xaxis requires DV or IAS verification on all programmatic buys; brands buying direct should require the same. For India CTV specifically, app-list targeting in DV360 (restricting to a verified list of India CTV app IDs) is the most practical fraud mitigation for buyers without full verification vendor integration.
What India buyers should actually measure
Given the measurement limitations in India CTV, a practical viewability framework:
- VCR as primary: Non-skippable CTV with 90%+ VCR is a stronger quality signal than viewability percentage, which is either near-100% (meaningless) or unmeasurable without SDK integration.
- IVT rate from DV/IAS: If buying programmatically through DV360, IAS or DV post-bid reporting flags IVT at the impression level. Target IVT below 3%.
- App-list filtering: Restrict open auction buys to a verified app ID list. DV360 supports this via the inventory source targeting. Reduces fraud exposure significantly without requiring full verification SDK integration.
- Publisher SDK verification for direct deals: For Rs 25 lakh+ direct or PMP deals, require the publisher to have IAS or DV SDK integrated. Most premium India publishers (JioHotstar, SonyLIV) do.