UTM QA Checklist
Use this page as the last human review before a tracked link goes live. Confirm naming, redirect survival, ownership, logging, and GA4 proof after the automated checks are done.
The UTM QA Checker validates structure. This checklist validates readiness. Run it after links are named and built, before ads, emails, creator placements, or redirects go live. Use it with the UTM Builder, Bulk UTMs, Redirect Checker, and your campaign tracking sheet.
Use the checklist after automation is finished and before the campaign reaches live traffic.
Ownership, redirect proof, logging discipline, and approval evidence still need human review.
If any red-flag item fails, stop the launch and fix the link before traffic starts.
Run the human release gate
Check every section below before a tracked link reaches live traffic. The progress panel updates as you tick off each item, so the whole team can see whether the launch is ready, drifting, or blocked.
1. Naming and contract
0/4Do not start with guesswork. The link should already match the approved taxonomy, naming pattern, and campaign plan.
2. URL and destination integrity
0/4The finished URL should still respect the live destination, preserve existing parameters, and land where the team expects.
3. Approval and evidence
0/4Every publishable link needs a traceable owner, a reviewer, and evidence that the release was approved on purpose.
4. Publish and post-launch proof
0/4The final check is whether the launch can be monitored after it goes live and whether the first proof steps are already planned.
Automatic fail conditions
These are the fastest ways to stop a launch without debate. If any of these are true, the link is not ready.
Wrong or incomplete tracking contract
Required UTMs are missing, naming rules changed mid-build, or the values do not match the approved taxonomy.
Route proof is missing
The team has not tested the redirect path, or the destination behaves differently once the public route is clicked.
No publish evidence
The final link is not logged, the owner is unclear, or there is no explicit approval evidence for the live route.
Use the checker for structure
Run the finished URL through the UTM QA Checker before you use this manual release gate.
Use redirect testing for route truth
Use the Redirect Checker when shorteners, affiliate redirects, or click trackers sit in the path.
Use the campaign sheet as proof
Log the exact publishable URL in the campaign tracking spreadsheet before the launch happens.
Use the right next step after the checklist
The checklist should route the team into the next control, not become the last page anyone looks at.
Run the automated check
Use the QA Checker when the structure itself needs validation before a human signs off.
Open QA Checker →Validate the public path
Use the Redirect Checker when the route has to survive shorteners, click trackers, partner redirects, or affiliate hops.
Open Redirect Checker →Keep launch evidence visible
Use the campaign tracking spreadsheet or automation workflow to preserve exactly what went live.
Open campaign sheet →FAQ
Short answers for the common launch-governance questions around this checklist.
What is the difference between the UTM QA Checker and the UTM QA Checklist?
The checker is the automated validation layer. The checklist is the human release gate that confirms ownership, redirect survival, approval evidence, logging, and launch readiness.
When should teams use this checklist?
Use it after links have been named and built, but before the campaign goes live. It is the final release gate before publish.
What should fail a link immediately?
Missing required UTMs, wrong destination, broken redirect path, unapproved naming, missing owner, or a live link that has not been logged should block publication immediately.
Does this replace redirect testing?
No. The checklist confirms that redirect testing happened, but the Redirect Checker is still the right tool to trace the route and confirm parameter survival.