For teams sending with SendPulse SMTP or Email Service
SendPulse reports delivery through SMTP webhooks for transactional mail and Email Service webhooks for campaigns. Tatami accepts both feeds as JSON arrays and keeps SMTP response codes, bounce classifications, and campaign identifiers with each outcome so your team can investigate why a recipient bounced or a campaign was delayed.
Keep sending with SendPulse. Use Tatami to investigate delivery problems, monitor sender reputation, and give your team a shared view of what needs attention.
Built by the team at Bento to monitor our own email traffic.
A delivery rate is a starting point. Look at the events behind it to understand which recipients, sending domains, or parts of your email program need attention.
01
SendPulse emits hard_bounces and soft_bounces as distinct events. Tatami records permanent failures as bounced outcomes and temporary mailbox or quota problems as deferred, with the SMTP response text when SendPulse supplies it.
02
SMTP events include smtp_server_response, response code, and subcode. Inspect those fields alongside the recipient domain when deciding whether a failure is an invalid address or a policy rejection.
03
Campaign webhooks identify traffic with task_id. Tatami stores that value as campaign context so a bounce can be traced back to the SendPulse mailing that produced it.
Follow delivery and bounce trends over time. Break down incoming events by receiving email provider to narrow your investigation.
Use AI-assisted reports to explain the response codes supplied by SendPulse and identify patterns worth investigating.
Add your sending IPs and domains to reputation monitoring. Review blocklist findings alongside delivery issues.
Set alert rules and send notifications to Slack, Discord, or email so someone can act when your thresholds are crossed.
Need to keep customers or colleagues updated? Share a filtered delivery report.
Add a SendPulse source to your Tatami project and copy its webhook URL. Name the source for the SMTP account or Email Service workspace you are connecting.
In SendPulse Account Settings, open the API tab and create a webhook using the Tatami URL. Enable delivered, not delivered, hard bounce, soft bounce, spam, and unsubscribe events. Email Service requires a webhook per event type; SMTP lets you select several events on one webhook.
Send a test message through SendPulse SMTP or a campaign and confirm a delivery or bounce event appears in Tatami. SendPulse batches events, so allow up to a minute for the first payload to arrive.
Read the official SendPulse webhook documentation
Explore Tatami onboarding for help connecting your sending setup.
Use SMTP webhooks for transactional mail and Email Service webhooks for campaigns. Both POST a JSON array to the same Tatami URL. SMTP events include recipient, message_id, and SMTP response fields. Email Service events use email and task_id. Create one Tatami source per SendPulse product if you want those streams separated.
Soft bounces become deferred outcomes. Hard bounces and undelivered events become bounced outcomes. Tatami skips opened, clicked, new subscriber, list deletion, and campaign status-update events so the monitoring view stays focused on delivery results.
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.
Keep your ESP. Get more visibility.
Tell us about your sending volume and the delivery problems you want to understand. We’ll help you connect SendPulse and get your first events into Tatami.
Sending through more than one provider? Explore the integration for each service.
Tatami is a modern email deliverability and monitoring platform, built for teams who care about reliable, transparent, and actionable email infrastructure.
100% independent, bootstrapped, and focused on customer trust.