Your dashboard says 99%. Your open rate says otherwise.Your ESP dashboard is glowing. Ninety-nine percent delivered. So why is nobody opening your emails? Because "delivered" and "reached the inbox" are two completely different things, and your dashboard only measures one of them.
⬡ split-compare, LEFT "Delivery: 99%" (green check) vs RIGHT "Inbox placement: 60%?" (question mark)Delivery = accepted. Deliverability = where it lands.Here's the whole thing in one breath. Delivery means the receiving server accepted your message. Deliverability means the message actually reached the inbox, where a human can see it. Accepted is not the same as seen.
⬡ split-compare, LEFT "Delivery, the server said yes" vs RIGHT "Deliverability, inbox vs spam"When you hit send, your server knocks on the recipient's server, say Gmail. Gmail says "sure, I'll take it," and your ESP writes that down as delivered. Done, right? Not quite. After Gmail accepts your message, it runs its filters, checks your reputation, and decides where to put it. Inbox, spam, or straight in the bin. That final decision is deliverability.
⬡ journey-flow, envelope reaches the server node, node lights "accepted", then a fork splits into Inbox / Spam / TrashPicture a big office building. The mail carrier hands your letter to the mailroom at the front desk. That's delivery, the handoff happened. But whether that letter makes it to the right desk, or gets tossed by the mailroom staff, that's a separate step. The carrier finished the job either way. Only one outcome actually gets read.
⬡ journey-flow, letter handed to mailroom desk (delivery), then splits: one path to a desk, one path to the binIf this is clearing things up, hit subscribe. We're answering every email question, one at a time.
⬡ title-card, "Subscribe, one question at a time"99% delivered. 60% in the inbox.Here's where it bites. You can have a ninety-nine percent delivery rate, servers took almost everything, and still only sixty percent inbox placement. The rest slipped into spam or got quietly filtered after being accepted. That's the gap that makes your dashboard look fantastic while your open rates crawl. The dashboard measures delivery. Your readers experience deliverability.
⬡ talking-stat, big "99% delivered", then a second number drops in "60% inbox", the gap highlightedSo what do you actually track? Delivery rate watches bounces, the hard permanent ones like a dead address, and the soft temporary ones like a full mailbox. Your ESP counts those for free, and healthy usually sits around ninety-eight percent or better. Deliverability, inbox placement, watches where accepted mail truly lands. Your ESP does not show you that. You need a separate placement test to see it, and plenty of senders sit lower than they think without ever knowing.
⬡ split-compare, LEFT "Delivery rate: bounces, ESP shows it" vs RIGHT "Inbox placement: where it lands, needs a test"Why is it built this way? Because the spam check happens after the server says yes. The server accepts first, then evaluates second. Saying yes does not promise it'll show your message to the user, it just means it's willing to look at it. Filtering every suspicious message away at the front door would be slow and would wrongly reject a ton of real mail. So the server takes it, then decides.
⬡ journey-flow, two-step node: "1. Accept (fast)" then "2. Evaluate (filter)"Low bounce rate feels good. It isn't the whole story.So here's the one to remember. A great delivery rate feels good, but if a big slice of that mail is landing in spam, you're still not getting read. Track both. If your delivery is fine but your open rates are grim, that's a deliverability problem, not a delivery one, and the fix lives in your reputation, your content, or your authentication.
⬡ split-compare, LEFT "Delivery fine + opens grim" vs RIGHT "= deliverability problem, not delivery"Next up: what your ESP actually means when it stamps an email "delivered." And subscribe if you want the rest of the deliverability playbook.
⬡ end-card, Subscribe + Next: "What is a delivered email?" (002.002.002)Email delivery vs deliverability, explained in under four minutes. Delivery means the receiving server accepted your message. Deliverability means it actually reached the inbox where someone can see it. That's why your ESP dashboard can proudly show 99% delivered while only 60% of your mail lands in the inbox, because the spam-filtering decision happens after the server accepts. We cover what each metric tracks (bounces vs inbox placement), why your ESP shows you one but not the other, and how to tell a delivery problem apart from a deliverability problem.
Chapters:
0:00 The dashboard that lies to you
0:20 Delivery vs deliverability in one line
0:40 What happens when you hit send
1:05 The mailroom picture
1:35 The number that proves it (99% vs 60%)
2:05 What each metric tracks
2:35 Why it's built in two steps
3:00 The takeaway
Concepts in this video:
Email delivery → /emailalmanac/deliverability/overview-and-fundamentals/what-is-email-delivery
Inbox placement → /emailalmanac/deliverability/inbox-placement/how-do-i-test-inbox-placement
Sender reputation → [002.001.003]
Related:
Next: What is a "delivered" email? → [002.002.002]
Deeper: Why can delivery be 99% but inbox placement only 60%? → [002.002.004]
If your delivery looks fine but opens are grim, check your authentication first (SPF, DMARC, blocklist status) with our free tools, or if you're stuck, ask us and we'll walk through it: reviewmyemails.com/sos
Full written guide → reviewmyemails.com/emailalmanac/deliverability/overview-and-fundamentals/what-is-the-difference-between-email-delivery-and-email-deliverability
#email #deliverability #emailmarketing