Per-platform HTML5 ad verdict
Check one HTML5 ad against Google Ads, DV360, CM360 and CM360 Studio at once
Each platform rejects different things. The Ad-Preflight desktop app checks a creative against every platform's own rules and shows a verdict per platform, so you know where it will upload before you send it.
The short version
The same ZIP uploads to DV360 and is rejected by Google Ads: 640 KB is over its 600 KB limit. Or it passes CM360 but uses the Studio Enabler, which Google Ads refuses. A single pass/fail cannot say where a creative is ready.
A verdict for each platform
Before the check, tick the platforms the creative is going to. All four are ticked by default. The result shows a stamp per platform - cleared, hold or grounded - and the overall verdict comes from the ticked ones: ready for some and not others is a hold that names the platform and the reason, for example "Ready for DV360 and CM360. Not Google Ads: 970×250 is 640 KB, over its 600 KB limit."
Problems every platform shares, such as a JavaScript error, a blank render or a forbidden file, still ground the ad everywhere. Untick a platform you are not uploading to and it stays in the box as information, without moving the verdict.
What each platform checks
- •Google Ads: 600 KB ZIP, at most 40 files, its file types, the ad.size meta, a complete HTML document, straight quotes, every referenced file inside the ZIP, allowed external resources, one exit, no custom click area, no Studio Enabler.
- •DV360: at most 100 files, its file types and name lengths, no nested ZIP, no unreferenced files, no web storage, a clickTag or exit that is spelled, bound and readable, HTTPS assets, ad.size matching the size.
- •CM360: 9.5 MB ZIP, at most 100 files, its file types, no % in file names, no web storage, a complete HTML document, a clickTag the click actually uses, no hard-coded landing page.
- •CM360 Studio: the Enabler is loaded and waited for, Enabler exits instead of <a> links, exit and event limits, one HTML file, Studio's file types. It judges only creatives built on the Enabler.
What Ad-Preflight checks
- ✓Platform-specific weight and file-count limits
- ✓Allowed file types per platform
- ✓clickTag, exit and Enabler rules per platform
- ✓Per-platform verdict with the reason, per size, across a whole campaign
What it cannot guarantee
- !Rules follow each platform's published specs and can change; they are reviewed against the official documentation
- !It cannot reproduce account, policy or manual review decisions
- !Ad tags are checked once for every platform, not per platform
Run it in the desktop app
Designers and AdOps can drop a campaign folder or paste an ad tag into the desktop app and follow the visual report.
- 1.Drop the creative or campaign folder (or a ZIP) into the desktop app.
- 2.Tick the platforms it is going to.
- 3.Read the verdict box: each platform's stamp and the reason behind it.
- 4.Fix what blocks the platforms you need, then package the upload-ready ZIPs.