Keep sending with Customer.io. Tatami reads its delivery events and shows you what bounced, what got blocked, and what to fix next.
No DNS changes. No rerouting mail. See the Customer.io setup.
Customer.io
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/customer_io/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through Customer.io. Tatami only reads the events it reports.
A lifecycle journey can be configured correctly while individual emails still bounce, fail, or get dropped. Tatami connects to Customer.io Reporting Webhooks to bring those delivery outcomes into one monitoring view. Keep campaign, broadcast, action, and delivery identifiers available when investigating which message in a customer journey needs attention.
Inspect campaign, broadcast, newsletter, and action identifiers supplied with Customer.io events. Connect a delivery problem to the relevant message in an onboarding or retention journey.
Review each outcome with its failure message or reason where available. Give your team evidence to distinguish recipient problems from issues reported before delivery completed.
Bring email spam reports and unsubscribe events into the same investigation as delivery outcomes. Use the supplied campaign context when reviewing the audience and message that prompted a response.
Tatami explains each bounce, watches your IPs and domains, and tells your team when something breaks.
1,240 Outlook bounces since 9:00, all from 198.51.100.24.
Microsoft is blocking that IP. Gmail and Yahoo look normal.
Also works in Claude Code and Codex through mcp.tatamimonitor.com.
Google, Yahoo, and Microsoft signals for every IP and domain.
Outlook is bouncing mail from 198.51.100.24 with 550 5.7.1 S3150.
Also sent to
Discord
Email
Rules on bounces, blocklists, volume, and throttling.
One filtered link per customer.
Point the Customer.io webhook at Tatami. Your mail keeps sending the same way.
Create a Customer.io source in Tatami and copy its webhook URL. Name the source for the Customer.io workspace whose lifecycle email you want to monitor.
In Customer.io Integrations, add a Reporting Webhook using the Tatami URL. Select email delivered, bounced, dropped, failed, spammed, and unsubscribed events, then save and enable the webhook.
Use Customer.io's Send Test action, then send an email through a journey. Confirm the delivery outcome and campaign or action identifiers appear in Tatami.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
Use Reporting Webhooks for this connection. They report message outcomes such as delivery, bounce, drop, failure, and spam complaints. A webhook action inside a journey serves a different purpose and does not automatically supply the reporting event feed.
No. Tatami's delivery monitoring does not require email body content. Leave that option off for this setup. Tatami uses the reporting event's delivery identifiers, campaign context, and failure details, and skips sent, opened, and clicked events.
No. A delivery event means the receiving mail server accepted the message. It does not confirm whether it reached the inbox or spam folder. Tatami monitors the delivery events you send, bounce reasons, and sender reputation to help you investigate deliverability issues; it does not measure inbox placement.
Providers are unlimited on every plan. Connect the rest of your email stack the same way.
PostShiba deliverability tool
Amazon SES deliverability tool
Smartico deliverability tool
Bento deliverability tool
$10 per million emails. First 100 IPs free. See pricing
Connect the webhook and watch your first Customer.io events arrive in minutes.