Keep sending with Smartico. 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 Smartico setup.
Smartico
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/smartico/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through Smartico. Tatami only reads the events it reports.
Smartico journeys can send across several channels and brands. For email deliverability monitoring, Tatami needs the email delivery-status callbacks that follow those sends. Bring delivered, bounced, failed, and complained events into Tatami with campaign and brand identifiers so your team can investigate the right customer communication.
Connect callbacks for delivered, bounced, failed, and complained statuses. A reverse-integration notification that only reports a send cannot establish how delivery ended.
Include brand, campaign_id, campaign_name, and email_uid in callback data. Tatami retains this context so an investigation can focus on the relevant brand and journey message.
Tatami maps soft_bounce to deferred and rejected to bounced. Review those outcomes with reason or error fields supplied by your Smartico callback configuration.
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 Smartico webhook at Tatami. Your mail keeps sending the same way.
Add a Smartico source to your Tatami project and copy the webhook URL. Choose a source name that identifies the account or brand group you are monitoring.
Configure email delivery-status callbacks or appropriate journey WebHook activities to POST JSON to Tatami. Include status, email, email_uid, timestamp, campaign, brand, and reason; coordinate reverse integration with your Smartico success manager if needed.
Test a delivered or bounced email callback and inspect it in Tatami. Verify that outcomes arrive after sends and that campaign and brand values identify the intended traffic.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
No. A send-only notification becomes a processed event, which Tatami skips. Configure delivery-status callbacks or additional WebHook activities for delivered, bounced, failed, complained, and unsubscribed outcomes. Available status data depends on your Smartico and email gateway setup.
This integration monitors email. Tatami ignores callbacks explicitly marked as other channels. Include channel set to email in your payload and supply brand and campaign identifiers to keep the relevant email traffic in context.
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
Customer.io deliverability tool
Bento deliverability tool
$10 per million emails. First 100 IPs free. See pricing
Connect the webhook and watch your first Smartico events arrive in minutes.