Automate campaign launch QA across ads, landing pages, CRM, and tracking

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.

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.

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.

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.

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.

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.

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.

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.

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.