Third-party ad verification for CTV in India: IAS and DoubleVerify

Integral Ad Science (IAS) and DoubleVerify (DV) are the two dominant third-party ad verification vendors operating in India CTV. They provide independent measurement of three things publishers cannot credibly self-report: viewability (was the ad actually delivered to an active screen?), brand safety (did the ad appear adjacent to inappropriate content?), and invalid traffic (was the impression served to a real person?). In a market without a unified audience currency, third-party verification is the closest India CTV has to independent delivery auditing.

What third-party verification covers

Viewability: For CTV, viewability is defined differently from display or mobile video. The MRC (Media Rating Council) CTV viewability standard considers a CTV ad impression viewable if it is delivered to an active (non-sleeping) connected TV screen. Unlike web display ads, CTV video ads are full-screen by nature — the traditional "50% of pixels in view for 2 seconds" standard doesn't apply. Instead, CTV viewability measurement focuses on confirming the TV was actively displaying the ad rather than on standby, screen-off, or in a background app state.

Invalid traffic (IVT): CTV IVT includes sophisticated invalid traffic (SIVT) — bot traffic, device ID spoofing, app bundle spoofing — and general invalid traffic (GIVT) — known data centre traffic, known invalid user agents. App bundle spoofing is the dominant IVT vector in India CTV: a fraudster sends bid requests claiming to be JioHotstar (app.bundle = com.jiohotstar) to capture premium CPMs without any real JioHotstar inventory. Third-party verification cross-references declared app bundle against app-ads.txt compliance and known fraud signatures to flag these impressions.

Brand safety: CTV brand safety measures whether the ad appeared adjacent to content that could harm the advertiser's brand — violence, controversial news, adult content. On CTV, this is done at the title/channel level rather than the keyword level used in display. IAS and DV maintain content classification databases covering Indian OTT publishers.

IAS for India CTV

IAS has direct integration with major India CTV publishers and DSPs. For DV360 campaigns, IAS verification is available as a third-party measurement tag integrated at the campaign level. For TTD campaigns, IAS integrates via the Unified ID and deals with Magnite and PubMatic to provide server-to-server measurement on SonyLIV and Zee5 inventory.

IAS CTV products for India:

IAS Total Visibility: Viewability measurement specifically calibrated for CTV environments, accounting for device type and delivery context
IAS Brand Safety: Category-level content classification for India OTT publishers; Hindi-language and regional-language content classification available
IAS Invalid Traffic: GIVT and SIVT detection including app spoofing detection cross-referenced against app-ads.txt
IAS Context Control: Pre-bid brand safety targeting that filters inventory before bidding — prevents the ad from being served to unsafe content rather than just reporting post-serve

DoubleVerify for India CTV

DoubleVerify operates similarly to IAS with direct integrations into DV360 and TTD. DV has been more aggressive in India CTV publisher integrations and as of 2026 has direct server-side integrations with JioHotstar's ad serving infrastructure, providing more comprehensive measurement coverage on that publisher than IAS offers.

DV CTV products for India:

DV Authentic Impressions: Combines viewability, IVT, and brand safety into a single "authentic impression" metric — the fraction of impressions that were viewable, fraud-free, and brand-safe simultaneously
DV Fraud Lab: Fraud detection infrastructure including CTV-specific app spoofing and sophisticated IVT detection
DV Attention: Beyond viewability — measures engagement signals (audio on, screen size, etc.) for CTV environments
DV Pre-bid Segments: Available in DV360 and TTD, allow buyers to exclude low-quality inventory before bidding

How to integrate with DV360 and TTD

DV360: IAS and DV both integrate as third-party measurement vendors in DV360's measurement settings. Once a DV360 advertiser account is linked to the verification vendor, measurement tags are automatically applied to eligible impressions — no manual tag implementation per campaign required. Setup requires a contract with the verification vendor and account linking through DV360's partner management interface.

The Trade Desk: IAS and DV integrate into TTD via the platform's third-party data/measurement marketplace. Activation is done at the advertiser or campaign level in TTD's UI. For India CTV specifically, the coverage of server-side measurement (which doesn't require a JavaScript tag and works on CTV) depends on which publishers have a direct integration with the verification vendor.

Server-side vs tag-based measurement: Standard JavaScript ad verification tags don't work on CTV — there is no browser to execute JavaScript. All CTV verification is server-side: the verification vendor receives impression-level data via a server-to-server integration with the publisher's ad server, or via the DSP's data feed. Coverage depends on which publishers the vendor has server-side integrations with. For India CTV, JioHotstar (via Google Ad Manager) and Zee5 (via PubMatic) have the broadest third-party verification coverage.

CTV-specific limitations

Not all publishers integrated: Smaller India FAST channel operators and regional OTT platforms may not have server-side integrations with IAS or DV. Verification coverage is concentrated on the three major publishers.
No content-level classification on all inventory: Brand safety classification works at the channel or content category level for most India CTV inventory — title-level classification is available only where publishers share content metadata with verification vendors.
Impression discrepancy: Third-party verified impression counts typically run 2–8% below publisher-reported impressions due to methodology differences. This is normal and should be agreed upon with the publisher in the IO terms before campaign launch.
Regional language classification gaps: IVT and brand safety classification for Tamil, Telugu, Kannada, and Bengali content is less comprehensive than for Hindi content. Buyers targeting regional language CTV inventory should acknowledge this gap in their verification setup.

India CTV verification benchmarks

Directional benchmarks from verification vendor reports and market observation (these vary by publisher and inventory type):

Viewability rate: 90–97% for premium India CTV inventory (JioHotstar, SonyLIV scripted content). CTV is structurally higher viewability than display or mobile web due to the full-screen format.
Invalid traffic rate: 1–4% for direct publisher deals and PMP buys from major publishers. Open auction inventory from unknown or unverified publishers can run 8–20%+ IVT.
Brand safety rate: 95–99% for curated publisher lists. Open auction buying without brand safety filters can produce brand safety incidents on news or user-generated content.

If your DV360 or TTD campaign shows IVT rates above 5% on what should be premium inventory, investigate whether app bundle spoofing is occurring — cross-reference DSP delivery report publisher data against app-ads.txt compliance for the publishers listed.

When to require third-party verification

Any India CTV campaign with spend above ₹20L: the cost of verification (typically $0.10–0.25 CPM added to media cost) is proportionate at this scale
Any open auction or PMP buy where the buyer cannot verify publisher identity via direct deal: IVT risk is highest here
Brand-sensitive categories (financial services, pharma, FMCG): brand safety classification and pre-bid filtering is standard practice
Any campaign where post-buy reporting will be shared with a client who expects independent delivery verification: third-party verification is the credibility layer between DSP delivery reports and client-facing reconciliation

For related FAQs, see Do I need IAS or DoubleVerify for India CTV campaigns?