Verified Vendor Coverage

CreativeValidator auto-detects ad-server and verification vendors in third-party tags and inserts the macros each vendor needs. Every rule below marked verified has been tested against real Google Ad Manager trafficking behavior — and we publish what's still in verification, so you always know how much to trust a result.

Test a tag now — free

GAM-verified vendors (28)

Macro insertion rules for these vendors are verified against Google Ad Manager. Tags from these platforms get click-tracker, cachebuster, and consent macros inserted exactly as GAM would expect them.

DCM / CM360 INS
DCM IMG redirect
DCM Legacy
Flashtalking
IAS
DoubleVerify
Sizmek
AdForm
BannerFlow
Innovid
Xandr
Criteo
DV360
Taboola
Amazon DSP
EyeReturn
Weborama
BridgeTrack
Yahoo ADTECH
Conversant / Mediaplex
Nielsen
C3 Metrics
Dynata
SpringServe
AdButler
Salesforce / Krux
Google AdService
Google PubAds

Detected, verification in progress

These vendors are recognized by the scanner (their pixels and cachebusters are detected and classified), but their macro-insertion rules haven't completed GAM verification yet. Scans still work — auto-insertion is simply conservative for them.

Vendor Domain Status
Arrivalist dc.arrivalist.com In verification
Foursquare / Placed p.placed.com In verification
Datafy imp.datafyhq.com In verification
Libro libro.io In verification
DISQO track.activemetering.com In verification
SpongeCell spongecell.com In verification
Airtory studio.airtory.com In verification
Smart Adserver / Equativ smartadserver.com In verification
Bound / GetSmartContent s.getsmartcontent.com In verification
Impact imp.pxf.io In verification
Casale / Index Exchange casalemedia.com In verification

Known scanner limitations

A validator you can trust tells you what it can't see. Current limitations, updated as they're closed:

Deep redirect chains

Click-through chains are followed and validated, but very complex DCM click → multi-hop 302 → landing scenarios may not have every intermediate hop enumerated in the report.

1×1 tracking pixels under strict blocking

Tracking pixels are detected and classified, but when a pixel is policy-blocked during the sandboxed run, its downstream behavior can't be fully analyzed.

Deeply nested iframe / postMessage creatives

Multi-layer tags that require publisher-side bootstrapping may not fully execute in the sandbox; the report flags low scanner confidence when this happens.

Flashtalking INS placeholders

FT INS tags render as a placeholder without the publisher-side FT library; macro and network analysis still run, but visual verification shows a blank creative.