How to Track Your Email Bounce Rate Day by Day (and Find the Day It Went Up)

To track your bounce rate day by day, put the date, the emails sent and the bounces for each sending day in three columns, then work out bounces divided by sent for each day and for a rolling window. The daily number tells you which day looked bad. The rolling number tells you whether the problem is a one-day blip or a trend. This post is the method, the traps in the arithmetic, and what to do once you know which day it was.

Track your daily bounce rate →

Why one bounce rate is not enough

Most sequencers show a bounce rate for a campaign or for the last 30 days. That single number is useful for a quick look, but it hides the thing you usually need to know: when did it change?

Suppose a campaign has been running for three weeks and the overall bounce rate looks higher than you expected. The overall number cannot tell you whether the whole campaign was a little high, or whether it was fine until a new batch of leads was added on one particular day. Those two cases have different fixes. In the first, the list source is the problem. In the second, one batch is the problem and the rest of the list is fine.

A daily table separates them. It shows the day the line moved, and that gives you a date to hold up against everything else you changed: the new list, a new source, a new inbox, a resumed campaign, or a template that now links somewhere new.

If you have not worked out a bounce rate before, start with our post on how to calculate your email bounce rate, which covers what counts as a bounce and what the denominator should be.

What you need: three columns

You need one line per sending day:

1. Date. The day the emails were sent.
2. Sent. How many emails went out that day.
3. Bounced. How many bounced.

Most sequencers and email platforms can show sends and bounces per day or per campaign in their reports. Copy those numbers into a sheet. If your tool only gives you a total per campaign, export the campaign's activity log and count by date.

Two practical points:

• Use whole numbers with no thousands separators. A number such as 1,200 contains a comma, and a comma splits a pasted line into extra columns. Write 1200.
• Lines for the same date are added together. If you paste two campaigns that both sent on the 4th, the tracker treats the 4th as one day with both campaigns' numbers. To compare campaigns, run each one separately.

The daily rate

For each day, divide bounces by sent.

As an illustration with made-up numbers: if you sent 200 emails on a Tuesday and 6 bounced, that day's rate is 6 divided by 200, which is 3 percent. If you sent 40 emails on the Wednesday and 2 bounced, that day's rate is 5 percent.

Look at that example for a moment. The Wednesday rate is higher, but it rests on two bounces. A single address more or less changes the day by 2.5 points. Daily rates on small days are noisy, so never decide on one of them alone.

The rolling rate

A rolling rate fixes that. Pick a window in calendar days, for example 7, and for each date add up the bounces over the window ending on that date, add up the sends over the same window, and divide one by the other.

With the made-up numbers above, a window that held only those two days would have 8 bounces over 240 sends, or about 3.3 percent. The quiet Wednesday barely moves it, which is the right behaviour: 40 emails should not outweigh 200.

The method matters. Do not average the daily percentages. Averaging a 3 percent day and a 5 percent day gives 4 percent, which treats a 40-email day as equal to a 200-email day. Dividing sums weights each day by how much was sent.

Dates missing from your data count as days with nothing sent. They add nothing to either number, and the tracker tells you how many dates it found missing so you can check whether you left a day out by mistake.

Set your own line

A line is the rate above which you want to stop and look. You set it. Different platforms publish different limits, and they are not the same; our post on bounce rate thresholds by platform links each to its source, and the bounce rate calculator compares a rate with them.

A reasonable approach is to set your own line a little tighter than the platform you send from, so you get warning before you reach theirs. The tracker marks every day, and every rolling window, that is over the line you typed. The 2 percent it starts with is an example only.

Read the output: three things to look for

The worst day. Find the date with the highest rate and check how many emails it rests on. A bad day with several hundred sends is a real event. A bad day with five sends is noise.

The first day the rolling rate crossed your line. This is usually more useful than the worst day. It marks when the trend started, and the day before it is often the day something changed.

How the rolling rate behaves afterwards. If it falls back below the line within a few days, the event was short. If it stays above, whatever changed is still in your sends.

What to do on the day it went over

Once you have a date, ask what was different that day. The usual suspects:

• A new list or a new source. Bounces come from the addresses you send to. If a new batch was loaded that day, it is the first suspect. The bounce rate by source tool compares sources side by side.
• An old list that was resumed. Addresses go stale. A list that sat for months before sending is older data than one exported last week. Our post on how often to verify an email list covers the timing.
• A new sending inbox or domain. A fresh inbox may behave differently from an established one. Compare the bounce messages, not only the rates.
• A change in the message. Bounces are a list problem, but a template change can affect other signals such as replies and spam complaints, which this table does not measure.

Then read the actual bounce messages for that day. A permanent failure is reported with a 5.x.x enhanced status code, and the text usually says what kind of failure it was, for example that the mailbox does not exist. The bounce message analyzer reads pasted messages and groups them. Mailbox-does-not-exist bounces point at the list. Messages about the sending server point somewhere else.

How many clean sends would bring the rate back down?

Because a rolling rate is a fraction, adding sends that do not bounce makes it smaller. The tracker shows that arithmetic for the latest window: the number of sends that would put the bounces at exactly your line if nothing else bounced.

Treat that figure carefully. It is arithmetic, not advice. It does not say that sending that volume is wise, and it assumes none of the new sends bounce, which is only true if the new list is clean. If you meet the line by sending more to a list that is just as bad, you will be back over it. The better move is to pause, clean the list, and follow the steps in what to do after a high bounce rate. The sending recovery planner helps you pace the restart.

Verify before the next send

The bounces on any given day start with the addresses on the list. A table can show you the day it went wrong, but it cannot stop the next one. Before you load the next list, run it through email verification so addresses that do not exist are removed before they reach a sending inbox.

Upload the list at /verify and remove the invalid ones. SimpleVerifier Pro is $39 a month, with the first 100,000 checks a month at full speed, then slower, never cut off. Verification reduces bounces from dead addresses; it does not change spam-folder placement or reply rates, and a table of bounces does not measure those either.

Limits of a daily table

• It uses only the numbers you paste. It does not read any account.
• A bounce rate says nothing about whether your emails landed in the inbox or the spam folder.
• Late bounces are counted on the day your report shows them, not the day of sending.
• Your line is a rule you chose. Meeting it is not the same as meeting a platform's limit.

A simple routine

1. Once a week, copy the last 14 to 30 days of date, sent and bounced into the tracker.
2. Keep the same rolling window and the same line each time, so weeks are comparable.
3. When a day or a window is marked, look at what changed that day before looking at anything else.
4. Verify the next list before it goes out, and keep the table so you can show what each fix did.

That is all the method is: three columns, one division, one rolling window, and a habit of asking what changed on the day the line moved.