Email deliverability rate
Email deliverability rate is the share of sent emails that were accepted by receiving servers — delivered divided by sent, the inverse of the bounce rate. But 'delivered' only means not bounced; it does not say whether mail reached the inbox or the spam folder. True inbox placement depends on authentication (SPF, DKIM, DMARC), sender reputation, and engagement, which is why deliverability is read with placement and complaint signals.
What this means
Deliverability rate = delivered ÷ sent, as a percentage — the inverse of the hard-and-soft bounce rate. 'Delivered' means the receiving server accepted the message. Crucially it does not distinguish inbox from spam folder, so a perfect deliverability rate can still mean poor inbox placement.
What actually drives placement
Where accepted mail lands depends on sender authentication and reputation. SPF, DKIM, and DMARC let receivers verify the sender; consistent low complaints and real engagement build reputation. Bulk-sender requirements from major providers make authentication and low spam-complaint rates effectively mandatory for reaching the inbox.
- Deliverability = delivered ÷ sent (inverse of bounce)
- Delivered ≠ inboxed — spam folder still counts as delivered
- SPF, DKIM, DMARC and reputation drive placement
Why it misleads
Because deliverability only measures acceptance, it overstates success: messages silently filtered to spam still count as delivered. Read it with seed-list or panel-based inbox-placement signals and the spam-complaint rate, rather than treating 'delivered' as 'seen'.
How it appears in analytics and logs
A high deliverability rate only confirms mail was not bounced — it can still be landing in spam; falling deliverability points at list quality, authentication, or reputation problems.
Diagnostic use case
Use deliverability rate as a first check that mail is accepted, then look past it to inbox placement, authentication, and complaint signals that determine whether messages are actually seen.
What WebmasterID can help detect
WebmasterID measures first-party engagement of recipients who reach your site, an outcome signal that complements deliverability without inspecting mailbox contents.
Common mistakes
- Reading 'delivered' as 'reached the inbox'.
- Sending without SPF, DKIM, and DMARC authentication.
- Ignoring complaint rate when deliverability looks fine.
Privacy and accuracy notes
Deliverability is computed from aggregate send and acceptance counts, not message content inspection. This page is educational, not legal advice.
Related pages
- Spam complaint rate
Spam complaint rate is the number of recipients who marked a message as spam divided by emails delivered, as a percentage. Mailbox providers report it through feedback loops, and it is one of the most damaging signals a sender can accumulate. Major providers' bulk-sender requirements set a complaint-rate threshold senders must stay under, making it a compliance metric, not just an engagement one.
- Email open rate
Email open rate is the number of opens divided by the number of emails delivered, as a percentage. It is measured by a tiny tracking pixel that loads when the message is viewed. Since Apple's Mail Privacy Protection began pre-fetching images regardless of whether a person opened the email, pixel-based opens are inflated and unreliable, so open rate is now read as a soft signal rather than a precise engagement measure.
- Email unsubscribe rate
Email unsubscribe rate is the number of recipients who opted out divided by the number of emails delivered for a send, as a percentage. It signals when content, frequency, or relevance is pushing people to leave the list. Bulk-sender requirements now mandate a working one-click unsubscribe, so a clear opt-out path is expected — and a very low rate can hide people who instead mark mail as spam.
- Website observability
On-site outcomes of email arrivals.
Sources and verification notes
- Google — Email sender guidelines (authentication)
- RFC 7489 — Domain-based Message Authentication (DMARC)
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.