In this guide
Creative QA means checking an ad and the experience it creates before it runs. Review the asset, its message, the actual click path, and the landing page. The approved dimensions are one check among several.
“Creative” is the ad asset: a banner, video, audio file, or another advertising message. “QA” is quality assurance. The aim is to catch faults that would change what the advertiser promised or what a visitor experiences.
Start with the approved requirements
Keep the placement specification and approved brief beside the asset. Confirm the dimensions or aspect ratio, format, file size limit, animation or duration rules, and any required controls. Requirements differ by format and receiving environment; use the current specification for the actual placement.
Open every file. Similar filenames can contain different offers or versions. For audio and video, review the whole asset, including the closing frame or spoken offer.
Work through an example
Imagine a banner advertising a 20% discount through October 31. It has the correct dimensions, but its click redirects to a page showing a 10% offer that expired in September. This is an illustrative QA failure.
| Check | Observed result | Decision |
|---|---|---|
| Dimensions and format | Match the placement specification. | Pass this check. |
| Ad message | Shows the approved 20% offer and October 31 end date. | Pass this check. |
| Destination | Redirects to an expired 10% offer. | Block launch until the destination or approved offer is corrected. |
| Mobile page | Requires another test after the destination changes. | Keep open; do not inherit the earlier result. |
The asset passing one check does not make the full experience ready. Test the replacement and record which version passed.
Check the full experience
- Message: brand, offer, dates, currency, language, and required disclosures match the approval.
- Display: text is readable; the asset is not clipped, distorted, or obscuring page controls.
- Motion and sound: animation, duration, playback, and audio behavior meet the placement requirements.
- Click: the actual ad interaction works, including any permitted test tracking.
- Destination: redirects finish at the approved page and required parameters remain intact.
- Page content: the landing page matches the ad's offer and call to action.
- Device and context: the experience works in the desktop and mobile environments in scope.
- Consent and regional steps: any applicable choices or redirects have been considered in the test.
Use the approved testing process. Avoid generating invalid interactions with live paid ads. A preview can differ from a live environment, so record what it does and does not cover.
Keep a QA record
Record the campaign and placement IDs, asset version, destination, test date, browser or device, result, and reviewer. Attach enough evidence for another person to reproduce a failure. Remove private data before sharing it outside the team.
Instead of “link broken,” write: “On the mobile preview, tapping the banner opens the September offer page after two redirects. Expected: the approved October offer page.” That describes an observable problem and the expected result.
Recheck changes after approval
A new file, destination, offer, or tracking path can invalidate earlier checks. Review the affected parts again and record the change. Plan a post-launch check for conditions the preview could not reproduce.
Use the campaign launch checklist to connect the asset approval with targeting, budget, measurement, and the final launch decision.
Put this guide to work
Bulk creative asset checker →HTML5 banner checker →AdOpsNow Editorial
Examples use illustrative data. See our editorial standards or report a correction.