Campaign Probe
Campaign Probe is built for the moment when a campaign leaves staging and starts behaving like a real send. It gives teams a controlled way to capture campaign output, inspect what arrived, and review quality before problems spread across a full audience.
When to use Campaign Probe
Use it when you need to:
- review live campaign output from your ESP or application
- verify that the correct subject lines, senders, and variants are going out
- capture samples from an active send for QA or marketing sign-off
- keep ongoing visibility into campaign quality after launch
What makes it different from deliverability tests
- Deliverability tests answer "did the selected cohort receive what we expected?"
- Campaign Probe answers "what is actually being delivered right now, and does it look correct?"
Teams often use both together during major launches.
Typical operating model
- Set up the capture addresses or monitoring path for the campaign.
- Start the send from your ESP or application.
- Review the captured output for sender, subject, content, and variant quality.
- Escalate issues before widening the audience or approving the next campaign stage.
Best paired workflows
- Email audit for link, image, and content checks
- Device previews for cross-client rendering review
- Domain Monitor for sender-domain posture
- Deliverability tests for cohort-level pass/fail validation
Good use cases
- canary launches
- release-day campaign QA
- lifecycle journey reviews
- high-risk transactional message changes