Ad Verification Tags
Know which verification tags are in your ads, and whether they're set to block.
Are blocking tags causing revenue discrepancies?
Ad verification vendors like DoubleVerify and IAS give advertisers the ability to block ad delivery based on keywords, content categories, or brand safety rules. When blocking is enabled, your ad server counts an impression — but the advertiser's system doesn't. You've served the ad, but you won't get paid for it.
Catch blocking before it becomes a billing dispute
Our Ad Verification Tags test detects verification pixels in VAST tags and display creatives, identifies the vendor, and flags whether blocking is enabled. You'll know before launch — not after the campaign ends and the numbers don't match.
What this test detects
The test scans creatives for known ad verification vendors and analyzes their configuration:
- Vendor identification — DoubleVerify, IAS, MOAT, Oracle, and others
- Blocking status — Whether the tag is set to monitor-only or actively block delivery
- Multiple tags — Flags when more than one verification vendor is present
How to evaluate your results
Set your ad specification to match your policies on verification tags:
- Monitoring only — Allow verification tags, but fail if blocking is enabled
- Approved vendors — Only allow verification tags from your approved list
- No verification tags — Flag any third-party verification pixels
- Custom rules — Configure by vendor and blocking status
Why this matters
Based on our platform data, 41% of verification tags have blocking turned on. That's nearly half of all tagged creatives potentially causing discrepancies. Testing before launch gives you leverage to push back — or at least set expectations with the advertiser.