- Delivery rate, defined
- Delivery rate is the share of your messages that a receiving server accepted, calculated as messages sent minus bounces, divided by messages sent.
The arithmetic is direct. Send 10,000, take 180 bounces, and 98.2% were delivered. Every sending platform reports it because it is the one number they can compute with certainty.
It answers a narrow question: did the receiving server take the message. It cannot answer the question people use it for, which is whether anyone saw it.
That gap is why a list that has been verified but never engaged can show 99% delivery and produce nothing. The mail arrived and sat in a folder no one opens.
Watch it as a list-health indicator, not a marketing one. A sudden drop from 98% to 91% means a chunk of your data aged out, or an import brought in something unvetted.
How ZapBounce reports it
Delivery rate is measured by your sending platform after a campaign, so it is not ours to report. What we can do is predict the bounce half of it before you send, which is the difference between finding out now and finding out from the receiving server.
One healthy average hiding one sick segment
Suppose you send to 25,000 addresses and 480 bounce, for a delivery rate of 98.1%. That clears the usual bar, and most people stop reading there. Split the same send by recipient domain and the picture changes.
The 14,000 Gmail addresses bounced at 0.4%. Two thousand Yahoo addresses bounced at 1%. The 9,000 addresses at company domains bounced at 4.5%, which is about 405 of your 480 failures. Your consumer data is fine, while the B2B segment is decaying, and the blended number was hiding it.
Every rate has a denominator, and the choice of denominator decides what the rate can show you. A delivery rate over the whole list is dominated by whichever segment is biggest. The one measured per segment is the one that points to which part of the list needs cleaning.
Why the number keeps moving for three days
The figure on your dashboard an hour after sending isn't final. Some messages are still in the retry queue after a temporary refusal, and they're usually counted as neither delivered nor bounced yet. If they fail for good on Thursday, Monday's delivery rate gets revised down.
Then there are bounces that arrive after acceptance. Servers on accept-all domains, and providers that say yes to every recipient during the handshake, take the message with a 250 and only later discover there's no such mailbox. They send a bounce message back to your return path, and your platform has to match it to the original send.
So read delivery rate at 72 hours, not at one. If you compare campaigns, compare them at the same age. When the late bounces concentrate on a few domains, note which ones. Verification can't resolve mailboxes on those domains ahead of time, so your own bounce history is the only reliable record of which of them are dead.
Delivery rate: common questions
What delivery rate should I expect?
Above 98% on a maintained list. Under 95% means the data has decayed or the source was never clean.
Is delivery rate the same as inbox placement?
No. Delivery counts acceptance by the server. Placement asks which folder it landed in, and the spam folder counts as delivered.
Why is my delivery rate high but engagement zero?
Almost always spam placement. The mail is being accepted and filtered, which is invisible in this metric by construction.