Reply measurement · Practical guide

Sent versus delivered denominators: label what your reply rate means

State exactly what belongs in the denominator. A sent-based rate and a delivery-adjusted rate can both be arithmetically correct while answering different questions.

Reviewed · Examples are illustrative

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

Define the decision

Sent usually refers to an application or provider acceptance event, while delivered can mean different things across systems. Some reports approximate delivery as sent minus recorded bounces. That approximation should be labeled; it is not evidence of inbox placement or human visibility.

Work through the procedure

  1. Document the source system's definition of sent and delivered before copying its numbers.
  2. Choose a numerator with the same unit, such as replied messages for a message denominator.
  3. If subtracting bounces, label the result as non-bounced or estimated delivered rather than claiming confirmed inbox delivery.
  4. Show raw counts beside the rate and retain the observation cutoff because late failures or replies can change the result.

Worked example

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

Message-level example
Sent messages: 100
Recorded bounced messages: 10
Replied messages: 9
Reply/sent = 9%
Reply/non-bounced = 9/90 = 10%
Neither denominator proves inbox placement.

Read the result

The difference comes from the denominator, not from additional replies. Comparing 9% in one report with 10% in another as if performance improved would be misleading. Reconcile definitions before interpreting trends, and avoid switching denominators because one produces a more attractive percentage.

Check before moving on

  1. Do not mix unique responding people with all sequence messages without explaining the mixed-unit metric.
  2. Check whether failures arriving later revise the denominator.
  3. Keep provider acceptance distinct from recipient reading.

Limits and next action

Zintara's current overview uses sent-message cohorts including sent, delivered and bounced statuses for its rate calculations. This worksheet explains alternative definitions rather than changing that implementation. Verify the metric source before comparing it with another platform.

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