Effective deliverability monitoring is a cadence, not a one-time setup. Check bounce and complaint rates daily, review Google Postmaster Tools and Microsoft SNDS reputation weekly, run seed-list inbox placement tests monthly, and audit authentication quarterly. The goal is to notice the day a metric turns from green to amber, because that is your head start before delivery actually fails. The most dangerous gap is that "delivered" does not mean "inboxed," and only seed testing reveals where your mail truly lands.
Here is the trap that catches most email programs. Your ESP dashboard reports 99% delivered, the number is green, and everyone assumes email is working. Then you run a seed-list test and discover that a third of those delivered messages are sitting in spam folders, invisible to every recipient. The gap between delivered and inboxed is the single most expensive blind spot in email operations, and most teams do not even know it exists.
The fix is not a single tool or a one-time audit. It is a monitoring cadence: a routine of checking the right metrics at the right frequency so problems surface while you still have time to act. This guide lays out exactly what to check daily, weekly, monthly, and quarterly, with the thresholds that should trigger action at each level.
Why Delivered Does Not Mean Inboxed
The foundational concept behind the entire monitoring cadence is the difference between delivery and inbox placement. Your ESP reports a message as delivered when the receiving server accepts it. That acceptance says nothing about where the message landed. The receiving server can accept a message and then route it to the spam folder, to a tabbed category, or to the inbox, and your ESP has no visibility into that final placement.
This is why a 99% delivery rate can coexist with terrible actual performance. Across large-scale seed testing, only around 60% of email reaches a visible inbox location, with a significant share landing in spam and a small fraction vanishing entirely. The delivery rate measures whether the server took the message. Inbox placement measures whether a human will ever see it. Your monitoring cadence exists to track the second number, not just the first.
Daily: The Five-Minute Health Check
Daily monitoring is a fast glance at the leading indicators, the metrics that move first when something goes wrong. This should take a few minutes and is best done at the same time each day so you build a feel for normal.
Bounce Rate
Bounce rate is the fastest leading indicator of a list or reputation problem. A sudden rise means either your list quality degraded (a bad import, a stale segment) or a receiver started rejecting your mail. Check it daily against your active sends.
Threshold: A bounce rate above 2% warrants immediate investigation. Above 5% is a crisis that should pause sending until resolved. Even a jump from your normal baseline (say 0.3% to 1.5%) is worth investigating even though 1.5% is technically acceptable, because the change is the signal.
Complaint Rate
Complaint rate is the metric mailbox providers weight most heavily. A spike means recipients are actively marking your mail as spam, which damages reputation fast. Check it daily from your ESP and feedback loop data.
Threshold: Keep complaint rate below 0.1% as a best-practice target. The hard ceiling for bulk senders at Gmail, Yahoo, and Microsoft is 0.3%, at which point throttling and blocking begin. Any single-day spike toward 0.3% requires immediate action.
The point of the daily check: It is not to admire green numbers. It is to notice the day one of them turns amber. That early warning is your head start, often the difference between a quick fix and a multi-week reputation recovery. A bounce or complaint trend caught on day one is far cheaper to resolve than the same problem discovered three weeks later through falling reply rates.
Weekly: Reputation and Authentication Review
Weekly monitoring goes deeper into the reputation systems that mailbox providers maintain. These do not change minute to minute, so a weekly cadence is appropriate. Pick a consistent day (many teams use Monday) so it becomes routine.
Google Postmaster Tools
Google Postmaster Tools shows your domain and IP reputation as Gmail sees it, your spam complaint rate, and your authentication pass rates. Since most lists are 30 to 50% Gmail, this is the single most important free reputation source for most senders. Review the domain reputation trend, the spam rate dashboard (which includes visual threshold lines at 0.1% and 0.3%), and the authentication pass rates.
What to watch: Any decline in domain reputation from High or Medium toward Low, any spam rate creeping toward the 0.3% line, and any drop in SPF, DKIM, or DMARC pass rates, which would indicate an authentication regression.
Microsoft SNDS
Microsoft Smart Network Data Services provides IP-level reputation data for Outlook and Hotmail. For B2B senders with Outlook-heavy audiences, this is essential. Review your IPs' status, complaint rates, and any spam trap hits flagged by Microsoft.
What to watch: Any IP moving to a yellow or red status, complaint rates rising, and spam trap hits, which indicate list hygiene problems that need immediate attention.
IP Reputation Spot Check
Run a quick Sender Reputation check on your sending IPs and a blacklist check to confirm none of your IPs or domains have been listed. Blocklist appearances can happen suddenly and silently, and a weekly check catches them before they cause sustained damage.
Monthly: Inbox Placement Testing
Monthly monitoring answers the question the daily and weekly checks cannot: where is my mail actually landing? This requires seed-list inbox placement testing, which sends your campaign to a panel of seed addresses across providers and reports exactly where each landed.
Seed List Testing
Run a seed test on your current sending using your real production mail. The test sends to seed addresses covering Gmail, Outlook, Yahoo, and other providers, then reports inbox versus spam versus missing placement for each. This is the only reliable way to know your true inbox placement before your campaign metrics reveal a problem.
Threshold: Confirm inbox placement above 90% across Gmail and Outlook. Flag and diagnose any provider where placement falls below 85%. A provider-specific drop (good at Gmail, bad at Outlook) points to a provider-specific issue like a Microsoft authentication or PTR problem.
List Hygiene Review
Monthly is also the right cadence for a list hygiene pass. Roughly a quarter of B2B contact data decays every year as people change jobs, so a list that was clean in January is measurably dirtier by summer. Re-verify recently added contacts with email verification, and review engagement to identify segments for sunset or re-engagement.
Run a seed test before any major campaign, not just on the monthly schedule. A large send to a poorly-placing inbox is expensive in both lost engagement and reputation damage from the spam-foldering itself. A ten-minute seed test before a big send catches placement problems while you can still fix the content, authentication, or timing rather than discovering the problem from the campaign results.
Quarterly: Full Authentication Audit
Quarterly monitoring is the deep infrastructure audit. Authentication and DNS records can change without your knowledge after hosting provider updates, domain transfers, or platform migrations, and a quarterly audit catches drift before it causes failures.
Authentication Verification
Verify SPF, DKIM, and DMARC are still correctly configured on every sending domain and subdomain. Confirm SPF still resolves within the 10-lookup limit (new includes can push it over), DKIM selectors are still active, and DMARC alignment is still passing for all legitimate sources. Use an SPF checker, DKIM checker, and DMARC checker across every sending identity.
DMARC Report Review
Review a quarter's worth of DMARC aggregate reports to catch any new sending sources that appeared (legitimate systems you forgot about, or spoofing attempts) and confirm alignment held across all of them. This is also the moment to consider tightening DMARC policy if you are still at p=none or p=quarantine and reports show clean alignment.
Automated Alerting: The Layer Above the Cadence
Manual checks are essential for judgment and trend-feel, but they cannot catch a problem that erupts between checks. Automated alerts close that gap. Configure alerts that fire immediately when a metric crosses a threshold, so you are notified the moment something breaks rather than at your next scheduled review.
Recommended alert thresholds:
- Spam complaint rate exceeding 0.1%
- Bounce rate exceeding 2%
- Unsubscribe rate on a single campaign step exceeding 0.5%
- Any blocklist appearance for your sending IPs or domains
- Any drop in authentication pass rate in Postmaster Tools
Alerts and cadence work together: alerts catch sudden breaks, the cadence catches slow drifts that never trip a threshold but degrade you over time. A reputation that erodes from High to Medium over six weeks may never cross an alert line on any single day, but the weekly Postmaster review will catch the trend.
Adjusting the Cadence During a Problem
The cadence above is for steady-state operation. When you are actively dealing with a deliverability problem or warming new infrastructure, compress the schedule. During a new domain or IP warmup, check Postmaster Tools daily for the first two weeks. During an active deliverability incident, check everything immediately before deciding whether to continue or pause sends, and continue daily monitoring until metrics stabilize. During a reputation recovery, monitor daily, because recovery is fragile and you need to catch any setback instantly.
Once metrics stabilize, settle back to the steady-state cadence. The compressed schedule is for periods of elevated risk; the routine cadence is for keeping a healthy program healthy.
Building a Monitoring Dashboard
Pulling these signals into one view makes the cadence sustainable. A practical dashboard combines bounce and complaint data from your ESP, authentication and spam rate from Google Postmaster Tools, IP reputation from Microsoft SNDS, and placement from your seed-test tool. The point is not to admire green numbers but to make the amber moment obvious the instant it happens.
Order the dashboard by leading indicator: bounce and complaint trends first (they move earliest), then reputation, then placement. This ordering means the metrics most likely to give you early warning are the ones you see first, reinforcing the entire purpose of the cadence, which is to catch problems while you still have time to fix them rather than after delivery has already failed.
Frequently Asked Questions
Check bounce and complaint rates daily, review Google Postmaster Tools and Microsoft SNDS reputation weekly, run seed-list inbox placement tests monthly, and audit authentication quarterly. During a new domain warmup or an active deliverability problem, compress the schedule and check the key metrics daily until they stabilize. Automated alerts should run continuously on top of the manual cadence.
Because delivered does not mean inboxed. Your ESP reports a message as delivered when the receiving server accepts it, but the server can then route the message to the spam folder where recipients never see it. A high delivery rate with low engagement usually means your mail is being delivered to spam. Only seed-list inbox placement testing reveals where your mail actually lands.
The core metrics are bounce rate (below 2%), spam complaint rate (below 0.1% target, 0.3% hard ceiling), domain and IP reputation from Postmaster Tools and SNDS, authentication pass rates for SPF, DKIM, and DMARC, and inbox placement from seed testing (above 90%). Bounce and complaint rates are leading indicators that move first; reputation and placement confirm the underlying health.
A seed list test sends your campaign to a panel of seed addresses across Gmail, Outlook, Yahoo, and other providers, then reports exactly where each message landed: inbox, spam, or missing. Run one monthly for routine monitoring and before any major campaign. It is the only reliable way to measure true inbox placement, which your ESP delivery rate cannot tell you.
A bounce rate above 2% warrants immediate investigation, and above 5% is a crisis that should pause sending until resolved. Beyond the absolute thresholds, any sudden jump from your normal baseline is worth investigating even if it stays technically acceptable, because the change itself signals a list or reputation problem developing. Set an automated alert at 2% so you are notified the moment it crosses.