Reply measurement · Practical guide

Cold email bounce rate calculation: reconcile failures with the send cohort

Divide the defined bounced-message count by the matching sent-message cohort and show both counts. Keep the diagnostic categories available because the same rate can arise from different causes.

Reviewed · Examples are illustrative

Who this helps: Campaign owners and analysts reconciling outreach performance.

Define the decision

A bounce rate compresses delivery failures into one percentage. It does not tell you whether the issue is address quality, authentication or a temporary provider condition. Use it as a signal to inspect evidence, not as a complete diagnosis or a universal safety certificate.

Work through the procedure

  1. Define the sent cohort by date, workspace and campaign scope. Record the observation cutoff.
  2. Count bounced messages associated with that cohort using a consistent status definition.
  3. Calculate the percentage and show the numerator and denominator beside it.
  4. Inspect the failure reasons and affected senders before deciding whether to repair data, connection settings or the campaign plan.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Cohort: 250 sent messages
Recorded bounced messages by cutoff: 5
Bounce rate = 5/250 × 100 = 2%
Diagnostic review: separate the five reasons
Do not infer that all five addresses are invalid from the percentage alone.

Read the result

The arithmetic is simple; attribution is the harder part. A later bounce can revise the cohort's rate, and a repeated sender-side error may explain several failures together. A rate of 2% in this synthetic example is not a recommended threshold or a claim that sending is safe to expand.

Check before moving on

  1. Keep zero-denominator cases undefined rather than dividing by zero.
  2. Compare equal observation windows when comparing cohorts.
  3. Do not count failed connection tests as prospect bounces unless the metric explicitly includes them.

Limits and next action

Zintara's overview calculates bounced messages over its sent-message cohort. This guide does not redefine provider status codes or prescribe a universal retry policy. Read the original diagnostics and preserve suppression when a recipient should remain excluded.

Source: Zintara product context; calculations are defined in this guide

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