--- title: "Email Deliverability Monitoring: A Daily Playbook" description: "Email deliverability monitoring catches problems before they kill your domain. The daily and weekly metrics, thresholds, and responses for cold senders." date: "2026-06-14" tags: "email-deliverability, cold-email, monitoring, sender-reputation, outbound-sales" readTime: "12 min read" author: "FirstSales Team" slug: "email-deliverability-monitoring" canonical: "https://firstsales.io/blog/email-deliverability-monitoring/" --- **TL;DR:** Email deliverability monitoring is the routine of watching a small set of leading indicators - bounce rate, spam complaint rate, inbox placement, and domain reputation - so you catch reputation damage while it is still fixable. The biggest mistake is reacting to the lagging signal (replies dropping) instead of the leading ones. This playbook gives you the metrics to watch, the tools to watch them with (Google Postmaster Tools, seed tests, your sending platform), the thresholds that should trigger action, and a daily-weekly-monthly cadence that keeps a domain healthy. ## Table of Contents - [Why deliverability fails slowly, then all at once](#why-deliverability-fails-slowly-then-all-at-once) - [The metrics that actually predict trouble](#the-metrics-that-actually-predict-trouble) - [Google Postmaster Tools: your single best free signal](#google-postmaster-tools-your-single-best-free-signal) - [Seed testing for inbox placement](#seed-testing-for-inbox-placement) - [The early-warning thresholds that should trigger action](#the-early-warning-thresholds-that-should-trigger-action) - [Your daily, weekly, and monthly monitoring cadence](#your-daily-weekly-and-monthly-monitoring-cadence) - [What to do when a number moves](#what-to-do-when-a-number-moves) - [Turning monitoring into alerts instead of chores](#turning-monitoring-into-alerts-instead-of-chores) - [Monitoring across multiple domains and mailboxes](#monitoring-across-multiple-domains-and-mailboxes) - [FAQs](#faqs) - [Conclusion](#conclusion) --- ## Why deliverability fails slowly, then all at once The thing nobody tells you about deliverability is the timing. It does not break the day you do something wrong. It breaks a week or two later, and by then the cause is buried under a pile of normal-looking sends. Here is the typical sequence. On Monday you load a list with a bad segment in it. The bounces and a couple of complaints register, but your replies that week look fine because the damage is just starting. Your domain reputation ticks down quietly. The next week, placement slips - some of your mail starts landing in spam instead of the inbox. Replies fall, but you blame the copy or a slow week. By the third week, placement has cratered, replies have dried up, and now you finally go looking for the cause. The trail is cold. The list you loaded two weeks ago does not look obviously guilty anymore. This lag is why monitoring matters and why most teams do it wrong. They watch the lagging indicator - replies and meetings booked - because that is the number tied to revenue. But by the time replies drop, the damage is already done and partly irreversible, since damaged domains recover slowly if at all. Watching replies to manage deliverability is like watching your bank balance to manage spending: it tells you about decisions you already made. Real monitoring watches the leading indicators - the numbers that move before replies do. Bounce rate spikes the day you send to a dirty list. Complaint rate rises the day your targeting goes wrong. Domain reputation in Postmaster Tools dips before placement collapses. These are the signals that give you a window to act while the problem is still cheap to fix. The entire discipline of [email deliverability](/blog/email-deliverability/) monitoring is about watching causes instead of consequences. ## The metrics that actually predict trouble There are a lot of numbers you could track. Only a handful actually predict deliverability trouble early. Here are the ones worth watching, roughly in order of how early they warn you. **Bounce rate.** The fastest-moving leading indicator. Bounces spike the moment you send to invalid addresses, often before any reputation damage shows up elsewhere. A sudden bounce climb is your earliest signal that a bad list segment got loaded. Watch it per campaign and per sending identity. The thresholds and the hard-vs-soft distinction are covered in detail in the [cold email bounce rate](/blog/cold-email-bounce-rate/) breakdown. **Spam complaint rate.** The most dangerous number. When recipients hit "report spam," it is the strongest negative signal you can earn, and providers enforce a hard ceiling around it. It moves a bit slower than bounce rate but does more damage faster once it climbs. The exact ceiling and how to stay under it is the subject of the [spam complaint rate threshold](/blog/spam-complaint-rate-threshold/) guide. **Inbox placement rate.** Where your delivered mail actually lands - inbox versus spam versus a tab. This is partly a lagging signal, since by the time placement drops, reputation has already shifted. But it is the most direct measure of whether your mail is reaching humans, and tracking it weekly via seed tests shows a degrading trend before replies disappear. It pairs directly with the leading metrics, which is why it sits at the heart of tracking your [inbox placement rate](/blog/inbox-placement-rate/). **Domain and IP reputation.** Mailbox providers maintain a reputation score for your sending domain. Google Postmaster Tools exposes a version of this for Gmail. When reputation drops from High to Medium to Low, placement follows. This is one of the best leading signals you can get because providers compute it from behavior you cannot see directly. **Authentication pass rates.** SPF, DKIM, and DMARC alignment. If these start failing - because of a DNS change, a new tool, or a misconfiguration - your mail gets filtered or rejected fast. Monitoring authentication catches silent breakages that would otherwise tank placement overnight. **Engagement signals.** Open and reply rates are noisy, especially with privacy-driven open inflation, but a sustained drop in genuine engagement still tells you something. Treat them as soft, corroborating signals rather than primary instruments. The skill is not tracking all of these obsessively. It is knowing which ones lead and which ones lag, and weighting your attention toward the leading signals - bounce, complaint, and reputation - so you act before placement and replies fall. A useful mental model is to picture these metrics on a timeline of cause and effect. At the front of the chain is your behavior - what list you loaded, how much you sent, how relevant it was. The first metric to react is bounce rate, within the same send. Complaint rate follows over the next day or two as recipients see and react to your mail. Domain reputation shifts a few days behind that, as the provider digests the bounce and complaint signals. Inbox placement moves behind reputation. And reply rate - the number you actually care about - sits at the very end of the chain, moving last. The further down the chain a metric is, the more it tells you about damage already done and the less time it leaves you to act. This is the entire argument for watching the front of the chain: bounce and complaint rate are not just "more metrics," they are the metrics that give you a head start. By the time the back of the chain moves, your options have narrowed to damage control. ## Google Postmaster Tools: your single best free signal If you send any meaningful volume to Gmail addresses, Google Postmaster Tools is the most valuable free monitoring resource you have, and a surprising number of cold senders never set it up. Postmaster Tools requires you to authenticate your sending domain with Google, then it shows you data Google collects about your mail to Gmail users. The views that matter for monitoring: **Domain reputation.** Google rates your domain Bad, Low, Medium, or High. This is a direct window into how Gmail sees you. High means your mail reliably reaches inboxes. Anything below High is a warning, and a drop from High to Medium is an early signal to slow down and investigate before placement craters. **Spam rate.** Google shows the percentage of your mail that recipients marked as spam. This is the number tied to the 0.3% hard ceiling. Seeing it climb here, before it crosses the line, is exactly the early warning you want. **IP reputation.** If you send from dedicated IPs, you can see how Google rates them. Useful for isolating whether a problem is domain-level or IP-level. **Authentication results.** Postmaster shows SPF, DKIM, and DMARC pass rates for your mail. A sudden drop flags a configuration break you might otherwise miss. The limitations are worth knowing. Postmaster Tools only covers Gmail, so it tells you nothing about Outlook, Yahoo, or corporate filters. It needs a minimum volume to display data, so very low-volume senders may see gaps. And it reports with a delay of a day or two, so it is an early-warning system, not a real-time alarm. Even with those caveats, it is the closest thing to seeing your own reputation through the provider's eyes, and it is free. Set it up before you do anything else in monitoring. For the providers Postmaster does not cover, Microsoft offers its own programs (SNDS and the Smart Network Data Services / JMRP feedback loop) for Outlook and Hotmail senders, and several providers offer feedback loops that report complaints back to you. Wiring these up where available extends your visibility beyond Gmail. One habit that separates serious senders from casual ones: check Postmaster on a fixed day, not just when something feels wrong. The whole value of the tool is early warning, and early warning only works if you look before the problem is obvious. A sender who checks Postmaster every Monday catches a High-to-Medium reputation slip while it is still a slip. A sender who only opens Postmaster after replies dry up is reading the obituary, not the warning. The data is there either way; the difference is whether you looked in time to use it. Make the weekly Postmaster review a fixed appointment, the same way you would a standup or a pipeline review, and it stops being a thing you do in a panic and becomes a thing that prevents panics. It is also worth understanding what Postmaster's reputation rating is actually built from, because it demystifies the number. Google computes it from the aggregate behavior of your mail to Gmail users - spam complaints, the ratio of mail that gets engaged with versus ignored, authentication results, and how your sending compares to known-good and known-bad patterns. You cannot see the exact formula, but the inputs are the same behaviors you control everywhere else: send wanted mail to real addresses with proper authentication and the rating stays High; send unwanted mail to dirty lists and it falls. The reputation rating is essentially Google summarizing, in one word, everything the other metrics measure in detail - which is why a drop in it is such a strong consolidated warning. ## Seed testing for inbox placement Postmaster tells you about reputation and spam rate, but it does not directly tell you where your mail lands across providers. For that, you run seed tests, and they belong in your regular monitoring routine, not just your initial setup. A seed test means including a set of addresses you control - spread across Gmail, Outlook, Yahoo, corporate domains, the same mix as your real prospects - in your campaign, then checking each one to see whether the message hit the inbox, the spam folder, or a tab. Because you control the seeds, you see actual folder placement instead of guessing from opens. For monitoring purposes, the key is consistency: - **Run a seed test on a fixed schedule.** Weekly at minimum, tied to a real campaign so the filters react to your actual content and sending pattern. A monthly snapshot is too coarse to catch a degrading trend in time. - **Record placement per provider, not just blended.** Your Gmail placement might be fine while Outlook quietly fails. The blended number hides the failing segment. Provider-level data tells you where to act. - **Track the trend, not the absolute.** Seed accounts are not perfectly calibrated to real human inboxes, so the exact percentage is less trustworthy than the direction it moves over weeks. A steady decline from 88% to 80% to 72% is a clear, actionable signal even if the absolute numbers are slightly off. Seed testing is the only practical way to monitor placement across the providers Postmaster Tools does not cover. Combined with Postmaster for Gmail reputation, it gives you a reasonably complete picture: reputation and spam rate from the provider directly, plus placement across the whole provider spread from your own seeds. ## The early-warning thresholds that should trigger action Monitoring is only useful if a number crossing a line actually changes your behavior. Watching metrics drift without pre-set thresholds is just anxiety with extra steps. Here are defensible early-warning lines for a cold outbound program. Decide yours in advance, write them down, and react when they trip. | Metric | Healthy | Warning - investigate | Critical - stop and fix | |---|---|---|---| | Bounce rate | Under 2% | 2 to 5% | Over 5% | | Spam complaint rate | Under 0.1% | 0.1 to 0.3% | Over 0.3% | | Inbox placement (blended) | 85%+ | 70 to 85% | Under 70% | | Gmail domain reputation | High | Medium | Low or Bad | | Authentication pass rate | ~100% | Any sustained dip | Frequent failures | A few notes on reading this table. The "warning" column is where monitoring earns its keep - it is the window where you can still fix things cheaply. The "critical" column means damage is underway and you should stop adding volume immediately. The spam complaint thresholds (0.1% target, 0.3% hard ceiling) are the published Google and Yahoo numbers, not arbitrary - crossing 0.3% triggers active blocking. The bounce thresholds align with where providers start treating your list as low quality. The single most important discipline here is pre-deciding the thresholds. When a number is sliding, it is human nature to rationalize - "it's just a slow week," "it'll bounce back." A threshold you committed to in advance overrides that rationalization and forces the action while the problem is still small. Teams that hold deliverability over the long run are the ones who treat these lines as non-negotiable triggers, not suggestions. ## Your daily, weekly, and monthly monitoring cadence Monitoring works when it is a routine, not a panic response. Here is a cadence that covers the bases without consuming your day. **Daily (5 minutes).** - Glance at bounce rate on the previous day's sends. A spike is your earliest warning and the cheapest to act on. - Check for any send failures or authentication errors flagged by your platform. - If you are sending high volume, a quick look at complaint rate. At lower volume, this can be weekly. The daily check is fast and exists to catch the fast-moving signals - bounces and outright failures - the day they happen, before they compound. **Weekly (20 to 30 minutes).** - Run your seed test and record inbox placement per provider. Compare to last week's. Watch the trend. - Review Google Postmaster Tools: domain reputation, spam rate, authentication results. - Review complaint rate for the week and compare to your threshold. - Look at engagement trends as a soft corroborating signal. The weekly review is where you catch the slower-moving reputation and placement trends, the ones that lag a week behind their causes. **Monthly (an hour).** - Audit list hygiene: re-verify aging lists, review your data sources for quality. - Review per-domain and per-mailbox performance if you send from multiple identities. Retire or rehabilitate any that are dragging. - Confirm SPF, DKIM, and DMARC are still correctly configured and aligned. - Step back and look at the month's trend across all metrics. Are you slowly improving, holding, or quietly degrading? The monthly review is the strategic one - it catches slow drifts that daily and weekly checks normalize, and it forces the list-hygiene work that prevents next month's problems. The slow-drift problem is sneaky precisely because each daily and weekly check sees a number that looks normal relative to yesterday. Placement at 82% feels fine when last week was 84%, which felt fine when the week before was 86%. No single check trips an alarm, but the month-over-month view shows an unmistakable decline that the day-to-day comparisons hid. Stepping back to the monthly horizon is the only way to see a trend that moves slower than your checking interval - and slow declines are often the most dangerous, because nothing ever feels urgent enough to act on until the cumulative drop is severe. This cadence is the operational backbone. The daily catches the fast signals, the weekly catches the reputation trends, and the monthly catches the slow drift and does the preventive maintenance. Skipping any layer leaves a class of problems undetected until it is expensive. ## What to do when a number moves Detection is half the job. The other half is knowing what each moving number means and responding correctly. A wrong response can make things worse - the classic example being more retries on a deferring server, which increases load and deepens the problem. **Bounce rate spikes.** Almost always a dirty list segment. Identify which campaign or which newly loaded batch caused it, pull that segment, and verify it before any further sends. Do not keep sending to a list that is bouncing - each additional bounce compounds the reputation hit. **Complaint rate rises.** A targeting or relevance problem. People are getting mail they did not want or expect. Tighten your targeting, review whether the list is genuinely a fit, and check that your content is not misleading recipients into expecting something different. Pull the most recent segment if the rise coincides with it. **Inbox placement drops.** Work backward to the cause. Check bounce and complaint rate first - placement drops are usually downstream of those. Confirm authentication is intact. If a specific provider dropped (often Outlook or corporate), the issue may be infrastructure reputation with that provider specifically. Slow volume while you diagnose. **Domain reputation falls in Postmaster.** Treat a High-to-Medium drop as a serious early warning. Reduce volume, double down on sending only to engaged, verified contacts, and remove anything questionable from your sends. Reputation recovers through a stretch of clean, well-received sending, not through pushing harder. This warning matters even more now that providers have shifted toward permanent rejection rather than gentle throttling - the trend behind [Gmail's move to permanent rejection in 2026](/blog/gmail-permanent-rejection-2026/) means the recovery window is shorter and the penalty for ignoring a reputation drop is steeper than it used to be. A reputation slip you would have shrugged off two years ago is now a same-week priority. **Authentication starts failing.** Stop and fix immediately. Check for recent DNS changes, a new sending tool that needs its own DKIM record, or an expired key. Authentication failures filter or reject mail fast, so this is a same-day fix, not a monitor-and-watch situation. The universal rule when a leading metric moves the wrong way: reduce volume first, diagnose second, resume third. Pushing more mail through a degrading reputation is the single most common way teams turn a recoverable wobble into a dead domain. Monitoring buys you a window to act calmly - use it to slow down, not speed up. ## Turning monitoring into alerts instead of chores A monitoring routine that depends on a human remembering to check dashboards will fail eventually. Someone goes on vacation, gets busy, or just gets complacent during a stretch of good numbers, and that is exactly when a problem slips through. The teams that hold deliverability over the long run convert as much of their monitoring as possible from a chore you remember to do into an alert that finds you. The principle is to set the thresholds you already decided on as automated triggers, so the system tells you when a number crosses a line instead of waiting for you to notice. Most sending platforms and several deliverability tools support some version of this. The alerts worth wiring up, in rough priority order: **Bounce rate alert.** The highest-value automated alert, because bounce rate is your fastest leading indicator and a spike demands immediate action. Set an alert to fire the moment any campaign or sending identity crosses your warning threshold (around 2%). This is the alert that catches a bad list batch after one send instead of after five. **Complaint rate alert.** Set this to fire as you approach the 0.3% ceiling, not after you cross it. By the time you are over the line, blocking has begun. An alert at 0.15% to 0.2% gives you the window to pull the offending segment before enforcement kicks in. **Reputation change alert.** If your tooling can read Postmaster reputation, alert on any drop from High. Even without automation, a calendar reminder to check Postmaster on a fixed day each week is better than "when I remember." **Authentication failure alert.** Authentication breaks silently and does damage fast, so an alert on any sustained dip in SPF/DKIM/DMARC pass rates catches a configuration break the same day rather than weeks later when you finally notice placement cratered. **Send-failure and volume-anomaly alerts.** Alerts on outright send failures, and on volume spikes that exceed your normal pattern, catch both technical breakages and accidental over-sending before they compound. The goal is not to automate away judgment - you still diagnose and respond as a human. The goal is to automate the detection, so the window between a problem starting and you knowing about it shrinks from days (the gap until your next manual check) to minutes. That window is everything in deliverability, because the cost of damage scales with how long it goes unnoticed. A bounce spike caught in an hour costs you a paused campaign; the same spike caught in a week costs you a domain. A practical way to start: take the threshold table from earlier, and for each row, ask "can I make crossing this line trigger a notification?" Wire up the ones you can, automate the detection, and reserve your manual reviews for the deeper trend analysis - placement patterns, per-provider drifts, monthly hygiene - that genuinely needs a human looking at it. Let the machine watch the lines; you watch the story. ## Monitoring across multiple domains and mailboxes Many cold outbound programs send from several domains and many mailboxes to spread volume. This is sensible, but it multiplies what you have to monitor, and a blended view across all of them hides problems. The core principle: monitor per sending identity, not just in aggregate. One bad domain can quietly drag your blended average while your good domains look fine, and you would never know which one to fix from the aggregate number alone. Practically, this means: - **Track bounce, complaint, and placement per domain and per mailbox.** When something moves, you want to immediately know which identity is responsible. An aggregate spike tells you there is a problem; a per-identity view tells you where. - **Set up Postmaster Tools for each domain.** Each sending domain has its own Gmail reputation. Monitor them separately. - **Quarantine and rehabilitate, do not just abandon.** When one domain's reputation drops, pull it from active sending, diagnose what hit it, and run it through a recovery period of low-volume engaged sending before returning it to load. A domain is an asset worth rehabilitating, not disposable. - **Watch for correlated failures.** If several domains degrade at once, the cause is probably shared - a common list source, a common content pattern, or a shared infrastructure issue. Correlated drops point to a systemic cause rather than an isolated bad domain. The more sending identities you run, the more monitoring discipline you need, because the surface area for silent failure grows with every domain and mailbox. The teams that scale volume without scaling disasters are the ones whose monitoring scales with their infrastructure - per-identity visibility, per-domain reputation, and a routine that does not let any single sender degrade unwatched. ## FAQs ### What is email deliverability monitoring? Email deliverability monitoring is the ongoing routine of watching key sending metrics - bounce rate, spam complaint rate, inbox placement, and domain reputation - so you catch reputation problems while they are still fixable. The goal is to track leading indicators that move before replies drop, rather than reacting to the lagging signal of falling reply rates after the damage is done. ### What tools do I need to monitor email deliverability? The core free tool is Google Postmaster Tools, which shows your Gmail domain reputation, spam rate, and authentication results. Microsoft offers SNDS and JMRP for Outlook. Beyond those, seed-list testing measures inbox placement across all providers, and your sending platform reports bounce and complaint rates. Together these cover reputation, placement, and the leading bounce and complaint signals. ### How often should I check my deliverability metrics? Use a layered cadence. Daily, glance at bounce rate and send failures (about five minutes). Weekly, run a seed test, review Postmaster Tools, and check complaint rate (20 to 30 minutes). Monthly, audit list hygiene, review per-domain performance, and look at the overall trend. The daily catches fast signals, the weekly catches reputation trends, and the monthly catches slow drift. ### What deliverability metric warns me earliest about problems? Bounce rate is the fastest-moving leading indicator - it spikes the moment you send to invalid addresses, often before any other damage shows up. Spam complaint rate and domain reputation move a bit slower but do more damage once they climb. Inbox placement and reply rate are lagging signals, so by the time they drop, the cause is usually already weeks old. ### What should I do when my domain reputation drops? Treat a drop from High to Medium in Postmaster Tools as a serious early warning. Reduce sending volume immediately, send only to engaged and verified contacts, and remove anything questionable from your campaigns. Reputation recovers through a stretch of clean, well-received sending over time - not by pushing more volume, which deepens the damage. ### Can I monitor deliverability for Outlook the way I do for Gmail? Not as directly. Google Postmaster Tools only covers Gmail. For Outlook and Hotmail, Microsoft offers SNDS and the JMRP feedback loop, which provide some reputation and complaint data. Beyond that, seed-list testing is the main way to monitor inbox placement across Outlook and corporate filters, since those providers expose less reputation data than Gmail. ## Conclusion Deliverability rarely dies overnight. It slides for a week or two while the team stares at reply rates, the one number that moves last. Real monitoring watches the leading indicators instead - bounce rate daily, complaint rate and placement and Postmaster reputation weekly, list hygiene monthly - so you see the cause before you feel the consequence. Pre-decide your thresholds, run the cadence, reduce volume first when a number moves the wrong way, and monitor each sending identity separately so no single domain degrades unwatched. That routine is the difference between a domain you maintain for years and one you have to abandon and rebuild. This is the philosophy built into [FirstSales](https://firstsales.io). FirstSales drafts a personalized cold email for each prospect with AI, then a human reviews and approves it before it sends - so your sending stays clean, human-paced, and the kind of behavior that keeps your monitored metrics in the green instead of fighting them after the fact. Start for $1 and run your first monitored campaign this week.