Best for
- Lean marketing teams launching campaigns across multiple channels
- Marketing ops teams tired of broken UTMs, forms, and routing errors
- Demand gen teams that need a repeatable pre-launch QA process
Create a launch checklist that catches broken forms, missing UTMs, bad routing, wrong links, and unapproved copy before a campaign goes live.
Build a campaign launch QA system with channel checks, tracking validation, CRM routing tests, approval gates, and a reusable launch checklist.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
6 tools used across the workflow.
Access
The complete workflow is available from the first step through the final result.
Why this works
Most campaign mistakes are not strategic. They are operational: bad links, missing tracking, broken forms, wrong audiences, or unclear approvals. This workflow turns campaign QA into a repeatable system so launches become less dependent on memory and last-minute heroics.
Expected results
Launch readiness
One complete QA checklist
Every asset, form, link, routing path, and reporting dependency has an owner and expected result.
Error reduction
Fewer broken launches
The workflow catches common issues such as wrong UTMs, broken forms, bad routing, and missing conversion events before launch.
Time saved
3-6 hours per campaign
Reusable QA structure reduces repeated manual coordination and last-minute launch checks.
Post-launch confidence
24-hour monitoring plan
The campaign is checked after real traffic begins instead of assuming pre-launch tests caught everything.
Step-by-step workflow
This workflow is fully available. Follow the steps below to build the system from start to finish.
45 min
45 min
List every campaign asset and dependency: landing pages, ads, emails, forms, thank-you pages, CTAs, UTMs, audiences, suppression lists, CRM workflows, sales alerts, and reporting views. Put each item into Asana with owner, due date, status, and QA requirement.
A complete campaign launch inventory with owners and QA fields.
The launch inventory should include hidden dependencies like suppression lists and sales notifications, not just visible assets.
30 min
30 min
Use Claude to convert the inventory into a checklist by channel and system. Include checks for copy approval, page rendering, mobile layout, form submission, CRM field mapping, lead routing, UTM consistency, conversion event firing, thank-you page behavior, and reporting ownership.
A campaign-specific QA checklist tailored to the actual launch assets.
Generic QA checklists get ignored. The checklist should name the exact page, form, campaign, ad set, workflow, and report being checked.
Create a campaign launch QA checklist from this campaign inventory.
Campaign summary:
{{campaign_summary}}
Asset inventory:
{{asset_inventory}}
Systems involved:
{{systems_involved}}
Output checklist sections for:
1. Landing pages
2. Forms and conversion paths
3. UTMs and links
4. CRM fields and routing
5. Email or ad assets
6. Audience and suppression lists
7. Analytics and conversion events
8. Sales alerts
9. Approval gates
10. Final launch decision
For each check, include owner, expected result, and failure condition.30-60 min
30-60 min
Check every ad, email, social post, and CTA link. Confirm UTM source, medium, campaign, content, and term values match the naming convention. Click through each URL and make sure it lands on the right page without redirects that strip tracking.
A validated link and UTM table with errors fixed before launch.
Test links in the actual final asset, not only in the planning sheet. Copy-paste mistakes often happen after the tracking spreadsheet is correct.
45-60 min
45-60 min
Open every landing page on desktop and mobile. Submit test leads using realistic email addresses. Confirm the form works, hidden fields populate, thank-you page loads, confirmation email sends if applicable, and the conversion event appears in GA4.
Verified landing pages, forms, thank-you paths, and conversion events.
Use a test email pattern that is easy to filter out later. Otherwise QA leads pollute campaign reporting.
45 min
45 min
Submit test leads for each major routing path: ICP fit, non-ICP, existing customer, partner, target account, and employee/test lead. Confirm HubSpot workflows assign the right owner, set lifecycle stage correctly, apply campaign membership, and send Slack or email alerts where expected.
Validated CRM routing and sales notification paths.
Routing QA is where revenue leaks happen. A perfect landing page is useless if qualified leads sit unassigned.
20 min
20 min
Paste the launch inventory, QA results, and open issues into Claude. Ask it to identify unresolved launch risks, missing owners, tracking gaps, and issues that should block launch. Use the output as the agenda for the final approval meeting.
A pre-launch risk report with launch blockers and nice-to-fix items separated.
Separate blockers from imperfections. Not every issue should delay launch, but every issue should have an owner.
30 min launch + 24 hour monitoring
30 min launch + 24 hour monitoring
Once blockers are cleared, record final approval in Asana and announce launch in Slack. After launch, check page traffic, form submissions, CRM routing, ad delivery, email sends, conversion events, and sales alerts during the first 24 hours. Log anything that needs a fix.
A launched campaign with first-day monitoring and issue log completed.
The first 24 hours are part of QA. Many problems only appear after real traffic starts hitting the system.
Review this campaign QA status and identify launch risks.
Campaign summary:
{{campaign_summary}}
QA checklist status:
{{qa_status}}
Known issues:
{{known_issues}}
Output:
1. Launch blockers
2. High-priority risks
3. Nice-to-fix issues
4. Missing owners
5. Tracking/reporting concerns
6. Recommended launch decision
7. Follow-up checklist for 24 hours after launch
Be strict but practical.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
Create a UTM and attribution hygiene audit with naming fixes, campaign mapping, reporting gaps, and a governance checklist.
Create a website conversion friction audit with evidence clips, root causes, prioritized fixes, and an experiment backlog.
Build a brand voice QA system with voice rules, banned phrase checks, review prompts, scoring, and an approval workflow for AI-generated GTM content.