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.
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
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 --fixPlatform reference: Google: troubleshoot creatives rejected by DV360 or Google Ad Manager