Concept
Delivery dashboard
See how fast your email reaches each inbox provider, how often it's delivered on the first attempt or deferred, where the time goes and which SMTP replies are behind deferrals and bounces.
Email APIDelivery shows how fast your email reaches each inbox provider, from the moment Emailit receives it to the receiving server’s reply, and what slows it down. It’s available on Pay as you goProBusinessCustom. To follow a single email the same way, open its delivery timeline.
On Pay as you go, the page shows a preview with sample data and an Upgrade button.
Filters
The date range at the top works like the one in Analytics, with the same presets, time zones and retention. See Analytics. Below it:
- Sending domain and API key narrow the page to one domain or one key.
- Inbox provider shows All providers or one provider. Selecting a row in the Inbox providers table does the same; select it again to clear it.
The page counts outgoing emails with delivery attempts in the range. Emails sent before the delivery timeline was introduced have no timing data and aren’t counted.
Headline numbers
Four cards sit at the top. Each shows the change from the previous period of the same length, in green when it’s an improvement and in red when it isn’t.
| Card | What it measures |
|---|---|
| Median time to deliver | Half of the delivered emails took less than this. Time to deliver runs from when Emailit received the email, or its scheduled time, to the receiving server accepting it. Time in the queue and between retries counts. |
| 95th percentile | 95% of the delivered emails took less than this. A slow 95th percentile usually means deferrals and retries. |
| Delivered on first attempt | The share of delivered emails that the receiving server accepted on the first SMTP attempt. The card also shows how many emails were delivered, out of how many. |
| Deferred at least once | The share of emails that got at least one temporary (4xx) reply. |
Time to deliver and distribution
Time to deliver charts the median (p50) and the 95th percentile (p95) over time. The scale is logarithmic, so a median of a second and a tail of several minutes fit on one chart. Periods with no deliveries are left empty.
Distribution counts delivered emails by how long they took: under 1 second, 1 to 5 seconds, 5 to 30 seconds, 30 seconds to 2 minutes, 2 to 10 minutes, 10 minutes to 1 hour, 1 to 6 hours, and over 6 hours.
Inbox providers
The table has one row per provider, busiest first, with Other last. Sort it by any column:
| Column | Shows |
|---|---|
| Emails | Emails to that provider in the range. |
| Delivered | The share of them that were delivered. |
| First attempt | The share of delivered emails accepted on the first attempt. |
| Deferred | The share of emails deferred at least once. |
| Bounced | Emails that bounced without being delivered. |
| p50, p95 | Median and 95th percentile time to deliver. |
| Avg. attempts | Average number of SMTP attempts per delivered email. |
| TLS | The share of connections to the provider that used TLS. |
Providers are recognized by the receiving mail server (the MX host), not by the recipient’s domain, so company domains on Google Workspace count as Google and those on Microsoft 365 as Microsoft. When the mail server isn’t known yet, the recipient’s domain decides. The providers are Google, Microsoft, Yahoo / AOL, Apple iCloud, Seznam, Centrum, GMX / Web.de, Yandex, Mail.ru, Zoho, Mimecast, Proofpoint, Barracuda and Other.
The Delivery by provider chart in Advanced analytics goes by the recipient’s domain only, so its numbers can differ from this table.
Where the time goes
For up to eight providers, a bar splits a typical delivery attempt into phases, using the median of each phase. All bars share one scale, so you can compare providers:
| Phase | What it covers |
|---|---|
| Queue | Waiting in the send queue after the email became due: when it was accepted, at its scheduled time or at its retry time. |
| Processing | Work before connecting: loading the message, rewriting tracked links, DKIM signing, spam checks and choosing a sending IP. |
| DNS | Looking up the mail servers of the recipient’s domain. |
| Connect + TLS | Opening the connection to the receiving server and starting TLS. |
| SMTP | The SMTP conversation, up to the server’s reply. |
Top deferral and bounce responses
The last table lists the most frequent replies behind deferrals and bounces, up to 15 rows. Each row shows the Provider, the Status (Deferred or Bounced), the SMTP code with its enhanced status code, for example 421 4.7.0, a sample Response, the Count and when it was Last seen.
Use it to see why a provider slows you down or turns mail away. A provider that defers with “try again later” is usually throttling you; see Warm-up and SMTP reply codes.
How it differs from Advanced analytics
The Time to inbox chart on the Advanced tab measures only the successful SMTP attempt. The Delivery dashboard measures the whole way, including the queue, processing and the wait between retries, which is what the recipient experiences.