How to send a test email in Mailchimp and preview it like a QA team

A Mailchimp test email lets you review the campaign before your audience receives it. Start with the send steps below, then check the delivered layout, links and any personalized content that changes the message.

Quick answer: how do you send a test email in Mailchimp?

In Mailchimp:

1. Open your campaign draft
2. Use preview mode to inspect merge tags and layout
3. Click Send a test email
4. Send to controlled test inboxes
5. Verify rendering, links, tracking, and spam signals before publish

Mailchimp test email workflow (practical version)

Step 1: Prepare controlled recipients

Do not send tests to personal inboxes only. Use purpose-specific addresses:

• Rendering inboxes (desktop/mobile clients)
• Link-validation inboxes
• Personalization-validation inboxes
• Deliverability-check inboxes

Step 2: Validate merge fields and conditional blocks

Mailchimp's preview and test guidance explains that contact-specific merge tags and dynamic content do not work in ordinary test emails. Use the live merge-tag preview to inspect a representative contact. When that content changes the layout, send a controlled live campaign to a small test segment containing only your review addresses, then inspect the delivered version in MailSlurp.

Before sending, confirm:

• All required merge tags resolve
• Fallback text exists for missing profile fields
• Conditional sections render as expected for key audience segments

Step 3: Send test email from Mailchimp

Trigger a test send and collect message IDs and timestamps for later comparison with event logs.

Step 4: Run the QA checklist

Check	What to verify	Fail condition
Subject and preheader	Correct message intent and length	Truncation or misleading copy
Personalization	Merge tags and conditional blocks	Raw tag output or missing values
Links and CTAs	Destination and tracking parameters	404, wrong UTM, broken deep links
Rendering	Desktop/mobile client behavior	Layout break or unreadable sections
Compliance	Footer, unsubscribe, required disclosures	Missing legal components

Send the same Mailchimp test message to the Mailchimp email preview tool when the final campaign needs Gmail, Outlook, iPhone, Android, desktop, light-mode, and dark-mode evidence before approval.

For the complete screenshot walkthrough, follow how to preview a Mailchimp email across devices.

Step 5: Run pre-send deliverability checks

For high-volume campaigns, add:

• Spam score check
• SPF/DKIM/DMARC validation
• Inbox-placement smoke test

When Mailchimp test emails are not enough

Mailchimp preview and test-send tools help validate campaign assembly. For release workflows, add a MailSlurp inbox and device-preview check when you also need:

• Automated assertions in CI/CD
• Deterministic waits for OTP or transactional triggers
• Multi-step end-to-end tests across app and email events
• Shareable render evidence for Gmail, Outlook, mobile, and dark mode

Choose the check you need

Start with device previews for a campaign's appearance and the email spam checker for content signals. Use inbox placement testing to check where a controlled campaign actually lands; a screenshot or spam score does not establish placement.

If the campaign depends on actions in your application, email integration testing can cover that broader workflow too.

Common Mailchimp test mistakes

• Sending one test and skipping segment variants
• Validating rendering but not link destinations
• Skipping spam checks for promotional sends
• Publishing without storing QA evidence for postmortems

After the last edit, send a fresh version and keep the completed results with your team's approval. The Mailchimp device-preview walkthrough shows the send and review steps with screenshots.