Bounce-rate monitoring

Bounce monitoring works when each rate has a defined place, time window, and response. Calculate the rate consistently, inspect delivery rate alongside it, and break the result out by campaign, domain, and mailbox. That keeps a local failure from disappearing inside an account average. A rising bounce rate can cap downstream metrics, so check deliverability before changing copy.¹ Keep hard and soft bounces separate in the calculation so each failure class remains visible.²

Set the measurement

Use one calculation and the same fields in every view. If a report changes its denominator or bounce categories, you cannot tell whether sending improved.

Bounce rate is bounced messages divided by attempted sends, split into hard and soft bounces.² Total bounce rate is the hard bounce rate plus the soft bounce rate.³ Record attempted sends, total bounces, hard bounces, soft bounces, delivery rate, campaign, domain, mailbox, and send period. Use delivery rate as the main indicator.⁴

Before comparing periods, check:

• Did the report use the same denominator as the previous period?
• Did total bounces move because hard bounces changed, soft bounces changed, or both?
• Is the delivery rate moving with the bounce rate?

Use the rate for comparison only when the periods use the same basis and the failure type is visible.

Read each sending view

An account average can hide a failing campaign or receiving domain. Read the same measure at each operational cut, then use the narrowest cut that explains the change.

Review each campaign immediately after it runs to detect list or setup issues.⁵ Compare the result with other campaigns that used the same mailbox or data source. A campaign spike needs its own diagnosis even when the account average looks stable.

Monitor by domain and over a rolling 30-day period to judge sender stability.⁶ Add the mailbox view because monitoring by domain and mailbox can catch verification problems and sending issues before they spread.⁷ Reports can show the inbox provider or email domain experiencing the bounces.⁸

Look for consistent soft bounces to specific domains. That pattern is a symptom of high bounce rates and gives you a place to start the investigation.⁹ Watch sending activity daily for unusual bounces, spam, or unsubscribes.¹⁰

At these views, check:

• Is the change limited to one campaign, domain, or mailbox?
• Did several mailboxes reach the same domain with the same result?
• Did the pattern begin after a list upload, verification change, or sending change?

These checks should show whether the problem is broad or isolated.

Use delivery rate as an early warning

Use bounce rate to track failure and delivery rate to see whether the sending operation is still reaching recipients. Keep both measures in the same review.

During warm-up, the recommended delivery rate is above 99 percent.¹¹ A delivery rate between 98 and 99 percent is acceptable with closer monitoring.¹² A rate below 98 percent needs prompt investigation.¹³ If the delivery rate does not improve after 3 sends, investigate the cause.¹⁴

Use this check during warm-up and afterward when addressing deliverability problems.¹⁵ Compare the delivery rate by domain and mailbox before deciding that the whole sending operation has failed.

For the delivery-rate review, ask:

• Which domain or mailbox accounts for the delivery-rate drop?
• Is the rate recovering after the last change?
• Has the problem persisted through the next send?

Identify the affected slice and its direction before moving on.

Apply response bands

Use thresholds to trigger action. Set the response before the number appears, so a bad result does not lead to another send while people debate what it means.

Treat 0.5 percent as an urgent list-hygiene signal.¹⁶ Keep bounce rate below 2 percent.¹⁷ Rates above 2 percent are worth investigating.¹⁸ When bounces exceed 3 percent, verify the list, pause sending, and remove inactive addresses.¹⁹

Use the lower threshold to inspect data quality, the middle threshold to start diagnosis, and the highest threshold to stop exposure while you repair the list. Keep the campaign, domain, and mailbox views open while taking action, because the right response may apply to one slice rather than the whole operation.

Before applying a response, check:

• Which records entered the affected send?
• Can the list be reverified before sending resumes?
• Which mailboxes or domains should remain paused?

Resume only after the affected slice has a reason for the failure and a clean next check.

Diagnose the failure class

Once you know where the rate moved, classify the failure before changing the campaign. The classification determines whether you remove records, investigate a temporary condition, or inspect the sending setup.

Bounce rate can help troubleshoot technical setup, mailing-list quality, sender reputation, and email copy.²⁰ Keep hard-bounce activity as close to zero as possible.²¹ Investigate repeated soft-bounce patterns before providers escalate their response.²²

Soft bounces can come from a full inbox, a server error, or a message that exceeds size limits.²³ A spike in one campaign can indicate a failed verification step or stale records. Audit the verification handoff, reverify records, and pause affected mailboxes.²⁴

To classify the issue, check:

• Are hard bounces concentrated in one source or spread across the list?
• Are soft bounces recurring at the same domain?
• Did the issue begin with the records, the sending setup, or the receiving side?

Change the campaign only after the delivery problem has been isolated.

What not to do

• Do not rely on an account-wide average when a domain and mailbox view can expose problems before they spread.⁷
• Do not keep sending after bounces exceed 3 percent while the list remains unverified.¹⁹
• Do not let hard-bounce activity drift away from a near-zero target.²¹
• Do not dismiss repeated soft bounces as harmless without investigating the pattern.²²
• Do not wait for a campaign to become old before reviewing its bounce result.⁵