Campaign probe

Campaign probe is for teams that send recurring lifecycle, marketing, or operational emails and need a stable destination to inspect what actually arrived. It helps catch broken links, missing assets, unexpected copy drift, and template regressions before those issues spread across production sends.

Use it when campaign quality needs to be checked continuously instead of only during launch week. The page stays focused on the shortest path: understand the workflow, open the docs if you need implementation details, or start with a free account and wire the probe into your sending stack.

Quick answer

MailSlurp campaign probes give each campaign, newsletter, lifecycle stream, or transactional communication a controlled inbox destination. Send, CC, or BCC the probe address and MailSlurp can inspect the received message for broken links, missing assets, HTML issues, compatibility warnings, sender-readiness signals, and quality drift.

Use campaign probes before and after launch when teams need repeatable evidence instead of a manual screenshot review.

Campaign QA workflow

1. Create a probe inbox for the campaign, newsletter, or recurring lifecycle stream.
2. Send the final email to the probe address from the same path customers will receive.
3. Check links, images, tracking URLs, HTML structure, and preview behavior.
4. Confirm sender readiness with SPF, DKIM, DMARC, MX, and inbox placement checks.
5. Validate unsubscribe and compliance headers for bulk or newsletter sends.
6. Route failures into webhooks, queues, or dashboards owned by the right team.
7. Compare later runs against the healthy baseline to catch drift.

Bulk sender and newsletter readiness

Use MailSlurp probes with authentication and header checks when a send includes newsletters, product announcements, lifecycle campaigns, or other bulk sender patterns.

Before approval, confirm:

• SPF, DKIM, and DMARC are passing for the sender domain
• unsubscribe links and headers are present where required
• Outlook, mobile, and dark-mode previews look acceptable
• mailto links, tracked links, and redirect chains work
• campaign assets are reachable from the received email
• inbox placement and spam checks do not show a release-blocking regression

Troubleshooting campaign probe failures

If a probe fails, start with the evidence MailSlurp captured:

• broken link or redirect: fix the final URL and rerun the probe
• missing image: check asset hosting, permissions, and URL rewriting
• rendering issue: run device previews and compatibility checks
• auth issue: check SPF, DKIM, DMARC, and headers
• placement issue: run inbox placement and spam checks before approving the send

FAQ

Is a campaign probe only for marketing email?

No. Use probes for newsletters, lifecycle sends, transactional announcements, onboarding drips, billing notices, and operational communications where message quality needs standing visibility.

Does a campaign probe replace inbox placement testing?

No. A probe inspects the message received by the probe inbox. Use inbox placement tests when you need provider-specific inbox, spam, or tab placement evidence.

Can campaign probes route failures automatically?

Yes. Pair probe results with MailSlurp webhooks so failed links, missing assets, and quality regressions can reach the team that owns the fix.