Email glossary · Practical guide

Email delivery rate: define accepted, bounced and unknown outcomes

Delivery rate needs an explicit operational definition. A common non-bounce calculation describes observed failures against a send cohort, not confirmed inbox placement for every message.

Reviewed · Examples are illustrative

Who this helps: Readers checking a term before making an outreach or mailbox decision.

Meaning and common confusion

Choose a fixed message cohort and observation cutoff. Distinguish rejected submissions, accepted messages, later bounces and uncertain attempts. If a dashboard calls the remainder delivered, explain that definition rather than letting readers infer a verified recipient action.

Worked example

This is a synthetic illustration, not a customer result or a live configuration to copy.

Accepted cohort: 200 messages
Observed bounces by cutoff: 10
Non-bounced remainder: 190 / 200 = 95%
This is a defined non-bounce rate, not a verified 95% inbox-placement rate.

Checks to make

  1. Keep message counts separate from unique people.
  2. Record delayed bounce revisions.
  3. Do not silently classify uncertain attempts as successful delivery.

Next step and limits

Use the sent-versus-delivered denominator guide when reports disagree. The correct formula depends on the chosen cohort and statuses. Zintara's sent records and provider evidence should be reconciled before making a delivery claim.

Source: Zintara product context for this operational definition

Source references

Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.

Related guides

Explore the Zintara workflow