Vendor Coverage

CreativeValidator recognizes vendor families and classifies specific tag formats. Recognition, documented macro syntax, automatic repair and observed click behavior are separate capabilities. A vendor name alone does not establish that a tag is repairable or accepted by GAM.

Test a tag now — free

Recognized vendor families and tag formats

This list describes recognition coverage, not 28 independently GAM-tested vendors. Automatic click/cachebuster repair requires an eligible vendor rule and supported tag shape. Some listed vendors are analysis-only. Consent values are preserved for vendor/CMP configuration. Review each report's repair status and execution evidence.

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

Additional detected vendors

These vendor names can be recognized, but the scanner may require manual review or provide no macro repair for a particular tag. This is not a commitment that platform verification is scheduled.

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

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.