Best for
- Teams reporting email performance to executives
- Marketers who need to move beyond open-rate summaries
- Organizations comparing campaigns sent to different segments
Separate delivery, engagement, click behavior, audience quality, segment context, unsubscribe risk, and downstream evidence so stakeholders see what a campaign proved and what it did not.
An evidence-linked Mailchimp performance brief, caveat register, and prioritized follow-up actions.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
2 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Email reporting becomes misleading when delivery, opens, clicks, conversions, audience composition, and privacy-related measurement limits are collapsed into one success claim. Mailchimp provides campaign, audience, segment, link, bounce, unsubscribe, and automation context that can be reviewed against the original objective. Claude can distinguish observed evidence from interpretation and explicitly flag where downstream proof is absent. The brief therefore supports decisions without pretending that an open or click automatically created pipeline.
Expected results
Records or configurations reviewed
100% of the approved in-scope population
The run reconciles every eligible record or configuration item to the signed source manifest rather than relying on an informal sample.
Evidence validation
Stratified QA before action
Every major finding class and high-impact segment is checked against source records before operational changes are approved.
Decision output
One owner-ready action register
Findings are converted into deduplicated actions with evidence, confidence, owners, approvers, deadlines, and rollback requirements.
Operational reuse
Versioned recurring runbook and Claude Skill
The same inputs, rules, prompts, schemas, validation gates, and metrics can be rerun while preserving a visible change history.
Step-by-step workflow
The first 2 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
30-60 min
30-60 min
State whether the brief should decide message retention, segment changes, CTA changes, offer changes, or a follow-up test. Name the primary business outcome. Work from Mailchimp using campaign ID, campaign type, send date, audience as the minimum evidence set. Complete this work in Mailchimp or the controlled working file; no Claude prompt is needed for this step. Save the finished artifact in the campaign reality brief with the run date, owner, evidence reference, confidence, and approval status. Treat Apple Mail Privacy Protection as a separate exception class and do not count it as failure unless the policy says so.
Define the campaign decision completed as a dated section of the campaign reality brief, with campaign ID, click rate, evidence links, owner, and approval status for retain the winning message.
Do not let campaign ID stand in for campaign type; that shortcut creates false positives in campaign performance reality brief. Document the result in the same run folder so the next cycle can compare like with like. Apply it specifically during “Define the campaign decision.”
30-60 min
30-60 min
Pull delivered, unique clicks, click map, unsubscribes, bounces, orders, revenue, segment, audience growth, subject line, send time, device, and comparison-campaign data. Capture send date, audience, segment, delivered in a dated working table before interpreting the result. Complete this work in Mailchimp or the controlled working file; no Claude prompt is needed for this step. Save the finished artifact in the campaign reality brief with the run date, owner, evidence reference, confidence, and approval status. Quality-check the result against clicks are separated by destination and CTA, then route any contradiction to the named data owner.
Export campaign and audience evidence completed as a dated section of the campaign reality brief, with campaign type, click-to-open rate, evidence links, owner, and approval status for retire weak CTAs.
Keep test sends visible as its own class because merging it into the main failure rate will distort the decision. Document the result in the same run folder so the next cycle can compare like with like. Apply it specifically during “Export campaign and audience evidence.”
Pro workflow preview
Previewing 2 of 12 steps
Get the remaining 10 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
A test-ready Mailchimp experiment plan with frozen cohorts, decision rules, QA checks, and a learning backlog.
An executive-ready campaign summary that explains what happened, why it matters, and what the team should do next.
Create a post-campaign rescue system with behavior-based segments, smart follow-up copy, and a review process before re-engagement.