Four categories of email monitoring tool, and what each one actually catches
"Email monitoring" can mean four different things depending on who you ask. The categories overlap in marketing language and barely overlap in what they detect. This page lays out the differences with concrete examples.
The four categories
Where each tool focuses, and where it goes blind
Native ESP analytics
The reporting built into your sending platform. Tracks queued, dispatched, delivered, opened, clicked. Great for campaign performance. Blind to whether the receiving inbox actually saw the email, or whether the trigger fired in the first place.
Deliverability monitoring
Inbox placement testing across mailbox providers. Tracks whether your sending domain and IP reputation get you to inbox, promotions or spam. Great for outreach and infrastructure work. Blind to whether a specific configured flow is firing for your actual customers.
Inbox-side monitoring
Watches the inbox for the specific messages your sending platform claims it sent. Tracks per-flow arrival, timing, and content. Great for catching sends that didn't go out and timing drift. Not designed for inbox placement testing.
DIY scripts
A team-built monitor that polls a mailbox and pages someone when an expected email does not arrive. Cheap to build for one or two flows. Becomes a maintenance burden at thirty flows.
Side by side
What each tool catches
| Failure | Native ESP | Deliverability | Inbox-side | DIY script |
|---|---|---|---|---|
| Trigger silently stops firing | No | No | Yes | Yes |
| Email reported delivered but lands in spam | No | Yes | Partial | No |
| Suppression rule overreach | No | No | Yes | Yes |
| Time delay misconfigured, sends arrive late | No | No | Yes | Yes |
| Merge tag breaks rendering | No | No | Yes | Partial |
| Sending domain reputation drops | Partial | Yes | Partial | No |
| API integration loses scope | No | No | Yes | Yes |
When to combine them
These tools are complements, not substitutes
A mature email program runs three of the four. The native ESP analytics tell you how campaigns performed. A deliverability tool tells you whether your sending domain is healthy. A inbox-side monitor tells you whether the flows you care about actually fired and arrived. The DIY script is the one that gets dropped first, because the maintenance cost grows with the flow count and the build cost grows with the alerting requirements.
Where Telltide fits
A inbox-side monitor for any sending platform
Telltide is the inbox-side category. It runs alongside whatever you already use for sending. The setup looks the same regardless of platform: Klaviyo, Salesforce Marketing Cloud, HubSpot, Sendgrid, Workflow Monitoring, Automation Monitoring, Email Suppression, Webhook Trigger, How To Audit Lifecycle Journey, Receive Side Monitoring, or anywhere else. One monitor per flow, an arrival window, and an alert channel. The concepts behind it are covered in the silent send and triggered flow definitions.
FAQ
Common questions
Don't ESPs already monitor email delivery?
Sending platforms monitor what their own infrastructure does: queued, dispatched, delivered to a receiving server. They cannot confirm what arrived in a real inbox, when it arrived, or whether it rendered correctly. That is the inbox-side gap.
What's the difference between deliverability and monitoring?
Deliverability tools focus on inbox placement: are your messages landing in inbox, promotions or spam, and what percentage of seed lists are receiving them. Inbox-side monitoring focuses on whether specific configured flows actually fire and arrive on time. Different problems, different tools.
Can I just write a script to monitor this myself?
Yes, and many teams do. The build cost is low. The maintenance cost is high once you need per-flow alerting, baseline learning, multi-channel alerting and drift detection across thirty flows.
From the blog
Where each category breaks
- CRM journey observability: where deliverability tools, ESP dashboards and inbox-side monitoring each fit in the stack.
- The supervision gap in agentic CRM: the category that none of the existing tools cover.
Try inbox-side monitoring
One monitor free. Paid plans from $49 USD per month. Set up takes about two minutes.