When to run this checklist
Run it after the campaign is fully built and before it is enabled, with the campaign open in one window and the campaign brief open in another. The brief is the source of truth: every item below is a comparison between what the brief asked for and what the platform shows. If there is no brief, write the objective, audience, budget, dates and KPIA metric tied directly to an objective. on a single page first, because a QA pass without a reference document only checks that the campaign is internally consistent, not that it is right.
Run it again whenever a paused campaign is restarted, a campaign is duplicated for a new market or a new offer, or the budget is increased by a large amount. Duplicated campaigns are a classic source of errors: the copy keeps the old dates, the old destination and the old exclusions, and the person duplicating it is usually in a hurry. A restarted campaign may be pointing at a conversion action that was retired or a page that was redirected while it was off.
Before you start
Have access to the ad account with a role that can see billing, audience and conversion settings, not just the campaign editor. Open the brief and the naming convention document; the Google Ads naming conventions guide describes the pattern most accounts use, and the same idea applies to Meta, where the campaign structure guide explains how campaigns, ad sets and ads should be organised. Have a phone to hand for the landing-page checks, because a page that looks fine on a desktop can be unusable on a small screen, and open the analytics property so that a test click can be traced end to end.
Agree who is doing the QA. The person who built the campaign should run the list once while building; a second person who did not build it should run it again before approval. The second pass is the one that matters. A builder reads what they meant; a reviewer reads what is there.
The checklist
Work through the groups in order. Each item is a single pass-or-fail check; if a check needs a discussion, it is not yet a pass. The first items in each group come from the compact launch list on the resources page; the rest extend it to the areas a quick list leaves out, such as creative specifications, the landing-page journey and who watches delivery on the first day. Ticks are saved in your browser only, so record the sign-off itself in the ticket or the brief; the checklists library explains how the ticks are stored and which list to run after this one.
Setup
Targeting
Tracking
Creative
Landing page
Sign-off
If an item fails
A failed item means the campaign does not launch until it passes, however small the item looks. The question is who fixes it. Setup and targeting failures are fixed in the platform by the builder, and the whole group is re-run afterwards, because changing a bid strategy or an audience can quietly change the optimisation event or the budget pacing alongside it. Exclusions that cannot be built, because the customer list has not been uploaded or has not finished matching, are a reason to delay, not a reason to launch without them: showing an acquisition offer to existing customers is the most common way a CPACost of each conversion. looks good in the platform and bad in the accounts. For a Google display campaign, the display campaign launch tutorial sets the display-specific settings, from optimised targeting and placement exclusions to the frequency cap, before this list is run.
Tracking failures leave this list and go to the tracking verification checklist, which covers the tag manager, analytics, the ad platforms and consent in full. Do not tick a tracking item because a pixel is present on the page; tick it because a test action produced the event with the right value. Missing or inconsistent UTMURL tags identifying traffic source. parameters are fixed against the naming and UTM conventions rather than invented on the spot. Creative failures go back to the writer or designer through the brief's approval chain; editing a headline in the platform to pass QA is how a campaign ends up running copy nobody approved. Landing-page failures are usually outside the ad account entirely, and the landing page checklist is the fuller list for the page itself. A Google Ads ad that fails policy review is handled as the guide to ad policies and disapprovals describes: read the reason, fix the ad or the destination, then resubmit.
A duplicated campaign that nearly launched with last season's settings
A furniture retailer duplicates its autumn sale campaign for a January clearance. The builder changes the creative, the budget and the start date, and marks the campaign ready. The reviewer's QA pass fails three items: the end date is still the previous one from October, so the campaign would have ended before it began; the customer exclusion list points at an audience last refreshed four months earlier, when the customer base was 3,200 people smaller; and the destination URL is the autumn landing page, which now redirects to the homepage. All three are fixed in about twenty minutes. Without the second pass, the campaign would have spent its first day's £450 sending clearance traffic to a homepage with no clearance message on it.
Common mistakes
- Checking the campaign against itself. Without the brief open, QA confirms the campaign is tidy, not that it does what was agreed. Every item is a comparison with a document, not an inspection of a screen.
- Letting the builder be the only reviewer. The person who built it reads their intentions. A second pair of eyes, with no stake in the build, is the cheapest control in the whole process.
- Trusting a duplicated campaign. Copies inherit dates, destinations, exclusions and conversion actions from the original. Treat a duplicate as a new build and run the full list.
- Ticking tracking because the pixel is installed. Installed is not firing, and firing is not firing with the right value and currency. Only a traced test action counts.
- Treating the end date as optional. An open-ended campaign is a budget commitment nobody made. Set the end date even for always-on activity and review it when it arrives.
- Leaving the first day unwatched. Delivery problems, disapprovals and broken pages all show up in the first hours. Name the person who checks, and what they check, before the launch.
