CTV brand safety works at the app and inventory level, not the URL level — there are no cookies or JavaScript trackers on smart TV apps. Protection relies on app-ads.txt enforcement, publisher allowlisting, and third-party verification where implemented. In India, verification coverage is partial, making app-level controls the most reliable defence.
How does brand safety work on CTV?
Protection comes from four layers: (1) app-ads.txt enforcement — block inventory from sellers not authorised by the publisher; (2) app allowlisting — only buy from verified India OTT publishers; (3) IVT filtering via IAS or DoubleVerify where publishers have implemented OMID SDK; (4) IAB Content Taxonomy category exclusions where content metadata is populated. The most important control is app-ads.txt enforcement — it eliminates app spoofing, the primary India CTV fraud vector.
What is the main fraud risk on India CTV?
App spoofing — a bad actor declaring their inventory as JioHotstar or Zee5 in the bid request while actually serving ads against low-quality or fraudulent inventory. The defence is app-ads.txt enforcement: enable "authorised sellers only" in DV360 or The Trade Desk. This blocks bids where the selling SSP is not listed in the publisher's app-ads.txt file, eliminating most app spoofing risk.
Do IAS or DoubleVerify cover India CTV?
Partially. IAS and DV cover major India OTT platforms (JioHotstar partially, SonyLIV, Zee5) but not smaller publishers or all open exchange inventory. Where OMID SDK is not implemented by the publisher, IAS/DV cannot measure viewability or IVT independently. Confirm verification vendor support with each publisher before a campaign launches — do not assume coverage is active.
Related questions:
In-depth article: CTV brand safety stack in India