DV360 HTML5 creative troubleshooting
DV360 HTML5 creative rejected? Find the technical issue before upload
Preflight common Display & Video 360 HTML5 rejection causes locally: size mismatches, broken clickthroughs, missing click handling, unsupported packaging, and oversized browser downloads.
The short version
DV360 reviews an uploaded creative and rejects it after the handoff. Ad-Preflight moves the technical checks earlier, before AdOps has to start the upload–reject–fix loop.
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
- ✓Declared ad.size and creative dimensions
- ✓clickTag, Enabler, and Exit API detection where applicable
- ✓HTTPS references, missing assets, file types, and ZIP structure
- ✓Per-size runtime JavaScript, rendering, network, and download-budget checks with Deep Audit
- ✓DV360 rules in the desktop app, with a verdict next to Google Ads, CM360 and CM360 Studio
What it cannot guarantee
- !It cannot approve the final landing page in every geography or browser
- !It cannot reproduce account, campaign, inventory, or manual policy review decisions
- !Rich-media Enabler behavior needs to match the creative type and trafficking setup
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 standard audit against the creative or campaign folder.
- 2.Use --fix for safe packaging and markup repairs.
- 3.Run Deep Audit when the creative can pass static checks but may fail at runtime.
- 4.Give AdOps the upload-ready ZIP and report together.
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: troubleshoot creatives rejected by DV360 or Google Ad Manager