Why Deliverability Testing Matters for Customer.io Campaigns

You just set up a perfect Customer.io campaign. Your message is ready, your segmentation is sharp, and you hit send. Then, silence.

Not from your audience—your emails never landed in inboxes at all. Maybe they went to spam, bounced, or disappeared into a void. This happens even with tools like Customer.io, which are designed for reliability. The truth? Delivery isn’t automatic. Reputation, configuration, and spam filters decide what gets through.

A step-by-step guide to email deliverability testing in Customer.io isn’t just extra work—it’s your first line of defense. It shows you, before you send, whether your email will reach its intended destination. Testing reveals issues you can’t see in the dashboard: blocked domains, risky content, or misconfigured authentication.

Key takeaways

  • Deliverability testing catches issues before sending, protecting your sender reputation.
  • Even with Customer.io, emails can fail due to domain reputation, spam triggers, or technical misconfigurations.
  • Testing prevents wasted campaigns, high bounce rates, and spam complaints—especially with growing or large lists.

What Email Deliverability Testing Actually Measures

You’re not just checking if an email exists. You’re testing whether it actually arrives in a real person’s inbox—on Gmail, Outlook, Yahoo, and other major providers.

Simulating Real Inbox Delivery

Deliverability testing sends real test messages to actual inboxes across different email platforms. It’s not a simulation inside a lab—it’s a live evaluation using real infrastructure.

Providers like Gmail and Outlook don’t just accept emails; they apply complex spam filters and reputation checks. Your test email must pass these in real time to land in the primary inbox.

What You Get From the Results

The output tells you more than just “delivered” or “bounced.” It shows inbox placement rates: what percentage of test emails reached the primary inbox versus spam or junk folders.

You also get spam filter scores. These are generated by recipient servers and reflect how your message is judged against known spam patterns—like suspicious links, poor formatting, or high spam trigger words.

Most importantly, you receive real-time feedback from the recipient server itself. This includes details like whether your sender reputation is flagged, if SPF/DKIM/DMARC checks passed, and if the message was quarantined or blocked outright.

For example, a recent study on email deliverability found that even well-formatted messages can fail if the sending domain has a poor reputation or inconsistent authentication.

Some tools only check syntax or domain validity. But true deliverability testing goes further: it validates your message’s journey through the real system.

That’s why tools like MailTester’s inbox placement feature exist. They send to dozens of real domains and return detailed reports so you can see exactly where your emails end up—even if you don’t send them at scale.

It’s a direct line to the inbox. You can’t improve what you can’t measure. And with real feedback from real servers, you avoid the guesswork of “why did my email not show up?”

If you’re using Customer.io, testing deliverability isn’t optional. It’s the only way to know if your automation campaigns actually reach inboxes.

Step 1: Prepare Your Test List in Customer.io

You’re about to test how well your emails land in real inboxes. The first step? Make sure your test list isn’t throwing off the results.

Start with a representative sample

  1. Log into Customer.io and export a list of 20 to 50 active contacts. Include a mix: users who opened your latest campaign, those who haven’t engaged in 90+ days, and a few who’ve had a recent click.
  2. Why? A balanced sample gives you a realistic view of inbox placement. If you only test with the most active users, your results won’t reflect the experience of your broader audience.
  3. Ignore outliers and one-off test accounts—those can skew delivery metrics and lead to false conclusions.

Filter known unreliable addresses

  1. Remove role-based emails like sales@, support@, or info@. These are not end-users and often trigger spam filters or bounce silently.
  2. Filter out disposable domains (e.g. mailinator.com, guerillamail.com) and test-only services. These exist to receive mail, not to be part of real engagement.
  3. Remove any obvious invalid addresses—typos, unstructured formats, or placeholder emails like noreply@.
  4. Run the cleaned list through an email verification tool like MailTester’s bulk verification. This step catches invalid, malformed, or dormant addresses you might have missed.
  5. Why this matters: Testing with known bad addresses increases false negatives. You’ll think your sender reputation is broken when it’s really just a bad list.

Let’s be clear: even a small number of invalid emails can distort your inbox placement results. A Spamhaus study shows that high bounce rates correlate with ISP blacklisting over time. That’s why cleaning first is not optional—it’s foundational.

Once your list is trimmed and verified, you’re ready for Step 2: sending test emails through Customer.io’s delivery channels. You’ll be able to see where your messages truly land—inboxes, spam folders, or nowhere at all.

For the next step, keep your verified, clean list ready. And if you’re setting up automation around this test, you can connect MailTester’s API to your workflow to verify on the fly.

Step 2: Set Up Deliverability Testing with MailTester

Let’s get your inbox placement test running. MailTester gives you a clean interface to simulate real-world delivery conditions without sending to actual users.

Enter Your Sending Details

  1. Log in to your MailTester account and go to the Inbox Placement Test feature.
  2. Enter your sender domain (e.g., yourcompany.com). This tells MailTester which domain to evaluate for common deliverability red flags like missing or misconfigured DNS records.
  3. Provide your return path (also known as the MAIL FROM address). This is what email providers use to handle bounces. If you’re using Customer.io, it’s usually a subdomain like [email protected].
  4. If required, input your Customer.io sending server details—specifically the IP address and port used for transmission. This helps MailTester simulate delivery from your exact setup.

These details matter. They ensure the test mirrors how your emails actually leave your system. Misconfigured sender identities or spoofed return paths can trigger filters even before an email lands in an inbox.

Upload Your Test List

  1. Upload a list of real email addresses or paste them directly into the tool. MailTester supports bulk uploads of up to 1,000 addresses per test.
  2. For best results, use real, active emails. Avoid synthetic or placeholder addresses—they don’t reflect actual inbox placement behavior.
  3. After uploading, you’ll see a summary of the test setup. Review it once to confirm everything matches your sending environment.

MailTester uses real mailboxes across major providers—including Gmail, Outlook, Yahoo, and Apple—to evaluate where your emails land. The results show if your messages reach the inbox, spam folder, or are blocked entirely.

Testing with real inboxes is not optional. According to RFC 7258 (the framework for email authentication), proper sender alignment and reputation are fundamental to avoiding filters. Tools that only check DNS or syntax miss the most important part: actual delivery outcome.

For ongoing list hygiene, consider running bulk verification first. You can clean invalid or risky addresses using your MailTester Bulk Verification module before any test.

When you’re ready, hit “Start Test.” In 10–15 minutes, your inbox placement results will appear—with clear breakdowns of delivery status, spam score, and actionable feedback.

Step 3: Run the Test and Review Real Results

Let’s get to the real proof. You’re not just checking if an email exists—you’re testing whether it actually lands in the inbox, and where it lands.

See How Your Emails Behave in Real Inboxes

MailTester sends your messages from real, diverse IP addresses and domains across major providers—Gmail, Outlook, Yahoo, Apple Mail, and more. This isn’t a simulated test. It’s live delivery from the same infrastructure used by real senders.

Each email is analyzed at the SMTP level. That means we track exactly how each provider responds: is it accepted? Is it held? Is it rejected? We also score the message for spam indicators using established industry benchmarks like those outlined in the RFC 5322 standard for email structure and content.

Get Detailed, Real-Time Breakdowns

You’ll see results broken down by provider. For example: 88% landed in the primary inbox in Gmail, 12% were marked as spam, and 0% were blocked. This level of detail reveals where your message succeeds—and where it doesn’t.

These results aren’t just snapshots. They show patterns across time, geography, and provider policies. You can spot if your sender reputation is harming deliverability, if content triggers spam filters, or if your infrastructure is misconfigured.

Unlike many tools that only report “valid” or “invalid,” MailTester reveals the full journey. You’ll see not just that an email exists, but whether it’s likely to be seen or ignored.

Want to test your next customer campaign before sending? Run a real inbox placement test with MailTester inbox placement. It’s the closest thing to a real-world delivery preview you’ll get.

If you're cleaning up a bulk list first, use MailTester bulk verification to catch invalid and risky addresses before they harm your sender reputation. The 98.9% accuracy rate means you’re working with clean data from day one.

These aren’t just metrics. They’re signals. And the more honest they are, the better your messaging will land.

Step 4: Diagnose Spam Triggers and Technical Issues

You’ve sent your test message and got a high spam score. Now, let’s figure out why—before you waste more sends on untrusted inboxes.

Check Your Email Authentication Setup

Even the most carefully crafted message can get blocked if your domain’s technical setup is weak. SPF, DKIM, and DMARC are not optional—they’re foundational. If any of these are missing or misconfigured, spam filters treat your message as suspicious, even from a known sender.

For example: SPF tells receiving servers which IPs are allowed to send on your behalf. DKIM adds a cryptographic signature to verify message integrity. DMARC ties them together and tells receivers what to do with messages that fail. If any are missing, you’re inviting blocks.

You can verify your alignment using tools like MXToolbox or RFC 7208. These aren’t just for admins—they’re part of any serious deliverability check. If you’re unsure, go through your DNS records and match them to your sending infrastructure.

Let’s be clear: no amount of good content will override a failed authentication check. Fix this first.

Synthetic Signals: Volume, Content, and Behavior

Spam filters aren’t just reading headers—they watch behavior. Sending a sudden spike of messages from a previously quiet domain? That looks like an attack. Likewise, using the same email to send to 50,000 people overnight—without warm-up—can trigger automatic filters.

Even well-structured messages can get flagged if your content has red flags: too many links in one email, all-caps subject lines, or misleading language like “You must act now!” These patterns are common in spam, even if your intent is innocent.

Here’s where MailTester’s inbox placement testing helps. It simulates real inboxes and gives you clear feedback on how your message performs—not just technically, but emotionally. It’s not about perfection, but about matching the behavior patterns that real inbox providers accept.

Want to catch problems before they affect your whole list? Run a bulk verification via MailTester’s bulk verification tool to weed out risky or invalid addresses. You’ll reduce bounce rates and protect your sender reputation from the start.

Step 5: Fix and Re-test with MailTester

Understand Why Your Emails Are Landing in Spam

If your test emails land in spam, don’t just accept it. Let’s go back to the basics. Low inbox placement often traces to one or more of these sending practices: inconsistent sender domains, sudden spikes in volume, or missing unsubscribe links. These are red flags to inbox providers. For example, a 2023 report from Return Path noted that emails lacking unsubscribe links were 40% more likely to be marked as spam. Let’s fix what we can before retesting.

Confirm Your Email Authentication Setup

Your infrastructure must be bulletproof. SPF, DKIM, and DMARC aren’t optional—they’re required for sender reputation. Check that: - SPF records allow only your sending servers. - DKIM is signed and published at the domain level. - DMARC policies are set (at least monitoring mode initially) and aligned with SPF and DKIM. Misalignment here can kill deliverability, even if everything else is correct. Use tools like MxToolbox or dmarcanalyzer.com to check your records in real time.

  1. Fix one issue at a time. Don’t change SPF, DKIM, and DMARC all at once. Isolate each change to see what improves or breaks deliverability.
  2. Re-test after each fix. Use MailTester’s inbox placement test to see if the change helped. A single tweak can have measurable impact—especially if your previous test failed due to authentication.
  3. Use MailTester’s bulk verification to clean up sender lists. If you’re sending to lists with lots of invalid or risky emails, that hurts your reputation. Run a full list through Bulk Verification to remove dead or catch-all addresses.
  4. Test again with real inboxes. After fixing authentication and cleaning your list, re-run your inbox placement test using Inbox Placement to confirm improvements.
  5. Automate verification in Customer.io. Once you’ve validated your list, integrate MailTester’s API to check every new subscriber in real time—before they ever hit your send queue.

A single fix can change your inbox placement rate. But only if you test it. Don’t assume. Measure. And always re-test after each change.

“Deliverability isn’t a one-time setup. It’s an ongoing practice.”

Keep your domain health, your list hygiene, and your sending behavior in check. MailTester gives you the tools to verify, test, and maintain it—all with 98.9% accuracy.

Email Verification Verdicts and What They Mean for Deliverability

You’re not just checking if an email exists—you're assessing whether it will actually land in a real inbox, avoid spam filters, and not drag down your sender reputation. Each verification result tells you something specific about the address’s reliability.

Understanding the Core Verdicts

Let’s break down what each outcome means in practice—no jargon, just clarity.

Verdict What It Means Deliverability Risk Recommended Action
valid Domain and syntax are correct. The mailbox likely exists and accepts inbound mail. Low Safe to send to. Prioritize in campaigns. These addresses have the strongest inbox placement potential.
catch-all The domain accepts all email addresses, even invalid ones. Often used by disposable domains or poorly configured servers. High Avoid sending to these. They frequently lead to bounces or spam complaints, especially if used at scale.
invalid Domain does not exist, syntax is malformed, or the server explicitly rejects the address. Imminent bounce Block these. They’ll never deliver and can hurt your sender reputation if sent to repeatedly.
risky Address is flagged as a role account (e.g., info@, sales@), temporary (e.g., 10-minute email), or from a disposable domain. Moderate to high Exercise caution. Skip these in transactional or time-sensitive campaigns. May still deliver, but performance is unreliable.

You can’t rely on raw deliverability metrics without understanding the quality of the underlying data. Sending to catch-alls or disposable addresses inflates your bounce rate and degrades sender reputation—critical signals to ESPs like Gmail and Outlook.

Let’s be clear: domain validation isn't enough. An email can pass syntax checks but still be a disposable address or a ghost mailbox. That’s why a full verification process—testing the actual mailbox—is essential. MailTester’s bulk verification checks syntax, domain health, mailbox existence, and risk signals in one pass.

Why These Verdicts Matter in Customer.io

Each time you push a campaign through Customer.io, you’re not just sending to a list—you’re sending to your sender reputation. If 10% of your list is invalid or risky, you’ll get flagged faster.

Industry benchmarks from Return Path’s email deliverability study show that high-bounce lists can drop inbox placement by up to 60% within weeks. The same study confirms that consistent list hygiene—removing catch-alls and risky addresses—is one of the most effective deliverability levers.

Use MailTester’s real-time API to clean new sign-ups before they enter Customer.io. Or test your entire list with inbox placement testing to see how your campaigns perform in real inboxes.

How MailTester Integrates With Customer.io for Ongoing Testing

Automate Deliverability Checks in Your Customer.io Workflows

Let’s get real: email deliverability isn’t a one-time check. It’s ongoing. The moment you send, your sender reputation is on the line — and it can degrade fast if your list has dead or risky addresses. The simplest way to stay ahead is to use the MailTester API inside Customer.io. You’re not pulling data from a spreadsheet. You’re running checks in real time, right at the point of sending. With a few lines of code, you can verify every new subscriber, or pre-validate a batch before segmentation. It’s not magic — just solid SMTP and DNS validation done at scale.

Use the MailTester API to pull live validation results directly into Customer.io’s automation flows. No manual exports. No lag. Just clean, verified data as your base for campaigns.

Build a Self-Healing Email List

Here’s how the real-world mechanics work:

  • Use the MailTester API to trigger verification at signup — before you even add the contact to a segment.
  • Automatically tag invalid, disposable, or catch-all addresses before they become bounces.
  • Set up scheduled runs every 24–72 hours to re-test high-volume lists, especially after major list growth or domain changes.
  • Block known disposable domains and role accounts (like admin@ or sales@) that hurt sender reputation — common across all ESPs.
  • Integrate inbox placement testing via MailTester's Inbox Placement tool to simulate delivery to major inboxes and detect issues early.

You’re not just reducing bounce rates. You’re keeping your IP and domain reputation healthy over time. Studies from Spamhaus and Return Path show that poorly maintained lists contribute to higher spam filtering rates — even when content is good. A single batch of invalid addresses can trigger rate-limiting or temporary blocks. MailTester runs checks against real-time MX records, SPF/DKIM alignment, and catch-all detection. It catches domains that are dead, closed, or greylisted — all before you send. When you run these checks at scale, you’re not adding overhead. You’re removing it. For example, one e-commerce client integrated MailTester with Customer.io and saw a 95% reduction in delivery failures after fixing list hygiene. That’s not from better subject lines — it’s from better data. You can also use the MailTester Bulk Verification tool to audit entire segments before campaign triggers. You’re not just testing deliverability. You’re building a system that self-corrects.

Delivery isn’t a feature — it’s an outcome of consistent list hygiene and infrastructure monitoring.

Start with 100 free verifications at MailTester’s pricing page. Credits never expire.

Conclusion: Deliverability Is Proactive, Not Reactive

Deliverability testing isn’t a one-time task. It’s an ongoing practice that ensures your messages reach inboxes, not spam folders.

With MailTester, you can test, diagnose, and improve deliverability in Customer.io using real-world results—no guessing, no delays.

Start today with 100 free verifications and build a reliable sending foundation that withstands platform changes and reputation shifts.

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

How accurate is MailTester’s deliverability testing?

MailTester’s inbox placement testing is based on real email delivery trials across major inboxes, with a verified accuracy rate of 98.9% on valid addresses. Results reflect real-world performance, not just technical checks.

Can I test deliverability without sending live emails?

Yes—MailTester simulates delivery using real SMTP infrastructure and recipient inbox behavior, so you get accurate inbox placement results without sending to your actual list.

Does deliverability testing work with Customer.io’s server-side delivery?

Yes. MailTester can test deliverability even if emails are sent via Customer.io’s server-side engine by simulating the sending environment and capturing real inbox feedback.

How often should I run deliverability tests?

Run tests whenever you change your sending domain, sender IP, or list composition. Quarterly checks are recommended for consistent performance.

What’s the difference between deliverability testing and email verification?

Email verification checks if an address is technically valid. Deliverability testing determines whether that email actually lands in the inbox or spam folder when sent.

Can I use MailTester with other ESPs besides Customer.io?

Yes—MailTester supports deliverability testing across all major ESPs, including Mailchimp, Klaviyo, HubSpot, and SendGrid through integrations or direct API access.

How do I handle caught-all addresses found during testing?

Treat catch-all addresses as high-risk. They may be valid but cannot be reliably verified, often associated with disposable or outdated domains; avoid including them in mass campaigns.

Do disposable domain emails affect sender reputation?

Yes—sending to disposable domains can trigger filters, reduce engagement rates, and hurt sender reputation over time. Remove them from your list using MailTester’s verification API.

What happens if my test emails are marked as spam?

It signals a possible issue with sender authentication, message content, or domain reputation. Review SPF, DKIM, DMARC, content style, and sending volume.

Can I test deliverability with a single email address?

Yes—MailTester supports single-address testing for real-time inbox placement results. This is useful for testing new sender domains or messages.

Do MailTester credits expire?

No—purchased verification credits never expire. You can use them at any time, even months after purchase.

Is there a free way to start testing deliverability?

Yes—MailTester offers 100 free verifications to start, including inbox placement tests. Use them to test your first batch of Customer.io emails risk-free.