Brand safety and fraud in CTV: how the trust layer works
CTV commands premium prices because buyers trust the screen is safe and the audience is real. That trust is enforced, not assumed — through verification files, supply-chain records and anti-fraud measurement. This guide explains the whole layer and what publishers must do to stay on the right side of it.
Brand safety on TV is two questions
On the open web, brand safety mostly means keeping ads away from harmful content. CTV adds a harder supply question: did this ad really run in the app it claims, on a real television, in front of a human? Brand buyers pay CTV prices only when all three are verifiable — safe content, real device, real viewer.
Your content ratings, genre metadata and channel descriptions answer the first. The technical files and measurement discipline below answer the other two — and they are where most publishers either win or lose premium demand.
The verification files: ads.txt and app-ads.txt
ads.txt is a plain-text file on your web domain listing who is authorized to sell your inventory. app-ads.txt is the same file referenced from your app store listing, extending the standard to apps — essential in CTV, where inventory lives in apps rather than websites. Each line declares an ad system, your account ID and the relationship: DIRECT or RESELLER.
Publishing and maintaining these files is the single highest-leverage trust action a CTV publisher can take. Buying systems check them automatically and drop unauthorized supply — so a missing or stale file is not a compliance detail, it is a revenue leak.
sellers.json and the SupplyChain object
sellers.json is the mirror published by ad systems: it discloses who the sellers in a transaction are. Together with the SupplyChain object in each bid request — the list of every intermediary that touched the impression — it lets a buyer trace every hop between their money and your screen.
You do not host sellers.json yourself, but verify that your monetization partners publish it correctly and list your account accurately. Opaque chains are increasingly blocked by demand-side filters, and 'I did not know' does not restore the demand.
What CTV fraud actually looks like
CTV fraud is mostly misrepresentation. Device spoofing — cheap mobile or server traffic claiming to be a smart TV — is the classic scheme, because CTV prices make the lie profitable. App spoofing makes one app impersonate a premium one. Server farms manufacture fake streams with fabricated measurement. The common thread: fraud severs the link between a claimed impression and a human watching a real television.
Even honest publishers are targets: fraudsters can forge your app's identity and sell fake inventory in your name. A current app-ads.txt and an accurate store listing are your defense — the fake supply fails verification, yours passes.
How verification vendors work
Brand campaigns on CTV routinely require independent measurement. Verification vendors confirm viewability, completion, fraud-free delivery and brand-safe context. Their measurement works through standards like OMID inside the player, or through server-side signals for SSAI streams.
Publishers cannot opt out of this — but can make it easy. Correct VAST event firing, accurate device and app identifiers on every ad request, and stable SSAI measurement all translate directly into eligibility for brand budgets. Verifiable inventory sells; unverifiable inventory gets filtered before price is ever discussed.
The SSAI double edge
Server-side ad insertion hides ad calls from the device, which blocks some client-side abuse — but creates room for server-side fabrication, since the ad decision and much of the measurement happen off the device. This is why buyers scrutinize SSAI measurement hardest, and why reputable setups include client-side confirmation beacons even when the stream is stitched server-side.
If you run FAST or live content, assume your measurement will be probed for exactly this weakness, and build it to survive the probe.
The controls publishers can offer buyers
Beyond the files, you can offer brand-safety controls that make more campaigns eligible to buy you: genre and content-rating metadata per channel or show, category exclusions, and accurate app identity on every request. These controls do not just make inventory safer — they expand the demand pool that is allowed to bid.
Think of the trust layer as product packaging. Two identical audiences sell at different prices depending on how verifiable the packaging makes them.
Quality is a standing condition
Passing one review is not the end. Serious partners score sources continuously — audience patterns, GEO consistency, device distribution, measurement completeness — and buyers re-verify on every bid. The publishers who keep premium rates treat verification files, measurement hygiene and traffic quality as weekly maintenance, not launch tasks.
On our side, sources are reviewed before demand is connected and monitored after. If you want your setup assessed, register as a publisher — the inventory review comes before any commercial terms, which are agreed individually and confirmed in writing.