HTML5 clickTag and exit validation
HTML5 clickTag validator for ad creatives before upload
Find missing or malformed click handlers before AdOps uploads an HTML5 banner. Ad-Preflight checks clickTag implementations and supported exit patterns, then can repair safe common cases.
The short version
The ad displays correctly, but the platform reports that it has no valid clickthrough or the click does not lead to the advertiser landing page.
Check your creative now: ZIP, folder or ad tag
Your browser reads the ZIP or folder - no upload, no account. A result tells you what failed, which of those the free app repairs for you, and what to do with the rest.
LOCALYour browser reads the file. Nothing is uploaded.
Preflight check
Drop a creative ZIP or folder here
One creative at a time. The verdict appears right here.
Video asset check
Drop your video exports here
MP4, MOV, WebM or an animated GIF. One file or the whole set of cuts, up to 12 at once, each judged against the rules Meta, TikTok, YouTube, LinkedIn, Pinterest, Snapchat, DV360, CM360 and Ad Manager publish.
The example is a six-second 1080×1920 MP4 from this site, put through the same checker as your own file - not a canned result.
- Running calls the ad server, the same request a real impression makes. It may count one.
- An empty slot can be targeting (domain, region, frequency cap), not a broken tag.
What Ad-Preflight checks
- ✓Presence of clickTag variables and click handlers
- ✓Supported Sizmek Enabler and Adform Exit API patterns
- ✓Click target wiring and common malformed references
- ✓Runtime click behavior when Deep Audit is enabled
What it cannot guarantee
- !It cannot verify the final URL after platform macro substitution
- !It cannot certify that the landing page is crawlable, available worldwide, or policy-compliant
- !Campaign Manager 360 rich-media creatives may require Studio Enabler exits rather than clickTag
Run it in the desktop app or CLI
Designers and AdOps can drop a campaign folder into the desktop app and follow the visual report. If you work in a terminal or CI pipeline, the same checks are available through the CLI.
- 1.Run the validator against every size in the campaign folder.
- 2.Inspect the finding and the exact handler pattern in the report.
- 3.Use --fix only when the repair is marked safe, then test the click in preview.
- 4.Keep the original backup and upload the generated package.
CLI equivalent
npx @ad-preflight/cli package ./my-ad --fixStill rejected? Send it to us
Send the rejection message and your free check result, and within 3 working days you get a written answer: what failed, on which platform, and the fix. No files, no call, no sign-up.
Send it to usPlatform reference: Google: guidelines for HTML5 display creatives