By Siddharth Gangal What email deliverability monitoring covers
Email deliverability monitoring is the continuous measurement of inbox placement rates, spam folder routing, bounce rates, and sender reputation across inbox providers. It gives sales teams a real-time signal when outbound emails stop reaching inboxes — before the damage compounds into domain blocklisting or a collapsed reply-rate baseline.
Deliverability monitoring covers five interconnected measurement layers: inbox placement tracking (which folder each sent message lands in), sender reputation scoring (how ISPs rate the sending domain and IP), authentication compliance monitoring (SPF, DKIM, and DMARC pass rates), bounce classification and management (hard versus soft, suppress versus retry), and spam trap and blocklist detection (whether any sending infrastructure has been flagged by anti-spam networks).
The reason active monitoring matters for outbound sales teams specifically: deliverability decay is silent. A domain that was placing 95% of messages in the inbox in January can slide to 60% inbox placement by March with no visible signal in the ESP's standard send reports. Open rates drop. Reply rates drop. The rep or manager assumes the messaging is at fault and revamps the sequence — spending hours rewriting copy for a problem that is entirely infrastructural.
Google and Yahoo's February 2024 sender policy updates raised the stakes substantially. Google now enforces a spam rate threshold of 0.10% for all bulk senders sending more than 5,000 messages per day to Gmail addresses. Sustained spam rates above that threshold trigger automatic delivery throttling. Rates above 0.30% can result in domain blocklisting across all Gmail routing. Since most B2B companies use Google Workspace as their primary email provider, nearly every outbound sales team's prospect list is predominantly Gmail-routed — making these thresholds operationally binding for any team sending at volume.
Email deliverability monitoring also differs from email analytics. Analytics tracks what recipients do after delivery — opens, clicks, replies. Monitoring tracks what happens before and during delivery — does the message pass authentication, does the ISP accept it, which folder does it land in. The two systems are complementary. Analytics cannot diagnose a deliverability problem. Only monitoring data catches the problem at the source.
Key metrics to track
Five metrics form the core of any email deliverability monitoring program. Each measures a different layer of the delivery chain. Missing any one of them leaves a blind spot that the others cannot compensate for.
1. Inbox placement rate
Inbox placement rate is the percentage of sent messages that arrive in the recipient's primary inbox — not the spam folder, not the promotions tab, not a filtered folder. The target is 90% or above for commercial outbound. Placement below 85% is a warning condition. Below 75% is a crisis that requires immediate investigation. Inbox placement rate is the single most important deliverability metric because it directly measures whether outreach has any chance of being seen. Open rates and reply rates are downstream of inbox placement. Fix placement first; the downstream metrics follow.
2. Spam rate
Spam rate is the percentage of sent messages that recipients report as spam, measured at the ISP level. Google Postmaster Tools shows spam rate data directly for Gmail. The Google/Yahoo 2024 policy establishes the enforcement thresholds: 0.08% triggers a warning condition internally; 0.10% triggers active delivery throttling; 0.30% puts the domain at risk of blocklisting. For a team sending 1,000 emails per day, that means staying under 1 spam complaint per day to remain below the 0.10% threshold. Spam rate is the metric most directly under the sender's control through list hygiene, suppression discipline, and message relevance.
3. Hard bounce rate
Hard bounce rate is the percentage of sent messages that fail permanently — invalid address, non-existent domain, or permanent block. The target is below 2%. Above 4%, ISPs begin interpreting the sending domain as a low-quality sender with poor list hygiene, which triggers reputation downgrades. Hard bounces require immediate suppression from all future sends. A hard bounce rate that rises above 2% is almost always caused by one of three things: purchasing contact lists without verification, failing to verify addresses before sequencing, or retaining contacts that have been unresponsive for more than 18 months without a re-engagement pass.
4. Domain reputation score
Domain reputation score is Google Postmaster Tools' four-tier rating for the sending domain: High, Medium, Low, and Bad. High reputation means Google routes messages from that domain to the primary inbox by default. Bad reputation means Google's filters deprioritize or reject messages from the domain regardless of individual message content. Domain reputation is a lagging metric — it takes weeks of sustained negative signals to move from High to Medium, and weeks of positive sending behavior to recover. Monitor it weekly. A single-tier drop from High to Medium is a serious warning. Two-tier drops are recoverable with extended effort. Three-tier drops — High to Low — typically require spinning up secondary domains while rehabbing the primary.
5. SPF, DKIM, and DMARC pass rate
Authentication pass rate measures what percentage of sent messages pass SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance) checks at receiving servers. Target: 100% pass rate on all three for all active sending domains. Anything below 100% means some messages are failing authentication — which puts them at direct risk of spam routing or rejection under ISP filtering rules. Authentication failures are almost always configuration errors: a DNS record that was not updated after a CRM or ESP change, a DKIM key rotation that broke the alignment, or a subdomain that was set up without inheriting the parent domain's DMARC policy.
Top monitoring tools compared
Six monitoring tools cover the full stack of deliverability measurement. No single tool does everything well. The right combination depends on sending volume, tech stack, and whether the team needs real-time seed-list testing, reputation dashboards, or both.
| Tool | Best for | Key feature | Starts at |
|---|---|---|---|
| Google Postmaster Tools | Gmail domain reputation monitoring | Domain and IP reputation scores, spam rate data direct from Google | Free |
| GlockApps | Inbox placement testing across providers | Send to 80+ seed accounts, get placement breakdown by ISP | $59/mo |
| Mailreach | Domain warm-up + continuous placement monitoring | Automated warm-up sequences + real-time placement score | $25/mo per mailbox |
| MXToolbox | DNS record validation and blocklist checks | SPF/DKIM/DMARC validator, 100+ blocklist lookup | Free (basic); $129/mo (monitoring) |
| Postmark SMTP | Transactional and outbound sending with built-in bounce management | Bounce API, suppression list management, delivery stats per stream | $15/mo for 10,000 emails |
| Microsoft SNDS | Outlook/Hotmail reputation monitoring | IP reputation, spam trap hit rate data for Microsoft properties | Free |
Stack recommendation. For most B2B sales teams, the minimum monitoring setup is: Google Postmaster Tools (free, non-negotiable), MXToolbox for DNS validation and blocklist monitoring, and GlockApps or Mailreach for placement testing. Microsoft SNDS is worth activating if the prospect list includes a significant share of Outlook addresses. Total cost for this stack: under $200/month for a team sending under 10,000 emails per day.
Google Postmaster Tools — details
Google Postmaster Tools is the closest thing to ground truth on Gmail deliverability. It shows domain reputation (four tiers), IP reputation (four tiers), spam rate over time (with the 0.10% threshold marked), DKIM/SPF/DMARC compliance rates, and delivery error rate. The only requirement is domain verification via a DNS TXT record. The data updates daily with a 1-2 day lag. Teams with low sending volume — fewer than 200-300 messages per day to Gmail addresses — may not see data populated in all dashboards, as Google requires a minimum threshold to show statistics. Activate it immediately for every sending domain. It is the first place to look when inbox placement declines.
GlockApps — details
GlockApps runs inbox placement tests by providing a list of seed addresses across Gmail, Outlook, Yahoo, Apple Mail, and other providers. The sender sends a test message to the seed list, and GlockApps reports back which accounts received the message in the primary inbox, spam, promotions, or other folders. This makes it the most direct tool for measuring the actual placement split a live campaign would achieve. GlockApps also provides spam filter analysis — showing which rules individual spam filters applied to the test message — and a spam score breakdown. The limitation is that seed-list testing reflects a synthetic sending condition, not a warm-sending-history relationship. Real campaign placement can differ from seed-list results for well-warmed domains.
Mailreach — details
Mailreach combines two functions: warm-up automation and continuous placement monitoring. The warm-up function sends small volumes of back-and-forth messages between a network of real inboxes to build positive engagement signals on a new or recovering domain. The monitoring function runs background placement checks on a schedule and shows a deliverability score that tracks inbox placement percentage across providers. For teams setting up new sending domains for outbound, Mailreach is one of the most efficient tools for the warm-up phase. For established domains, the monitoring function alone is valuable as a weekly health check.
Alert and threshold setup
Monitoring tools generate data. Alert configurations turn that data into action. Without alerts, a deliverability problem that surfaces in a dashboard on Tuesday goes unread until Friday's weekly review — four days of continued sending into a degraded reputation state. The alert thresholds below represent the operational standards for a B2B outbound team sending at any volume above 100 messages per day.
Spam rate thresholds
Configure a two-tier spam rate alert: a warning alert at 0.08% and a pause alert at 0.10%. The warning alert at 0.08% fires a notification to the sales ops or RevOps owner and triggers a review of the sequences running that day. The pause alert at 0.10% automatically pauses all active sequences on the affected domain until the root cause is identified and corrected. This two-tier structure prevents a single spam complaint spike from halting all sending while still catching the trend before it breaks the 0.10% threshold.
The spam rate alert system requires Google Postmaster Tools data piped into the monitoring workflow. Postmaster Tools does not natively push alerts. Options: manual daily review, or use a tool like GlockApps or a custom webhook that pulls Postmaster data via the API and pushes to Slack or email when thresholds are breached.
Inbox placement rate thresholds
Warning threshold: inbox placement drops below 85% on any single test. Pause threshold: inbox placement drops below 75% for two consecutive tests. Measurement interval: weekly seed-list test on each active sending domain. The warning condition triggers investigation — authentication record review, bounce list audit, recent sequence review for any messages that may have generated elevated complaint rates. The pause condition stops new outreach on that domain while the investigation runs.
Hard bounce rate thresholds
Warning: hard bounce rate exceeds 2% on any sending day. Pause: hard bounce rate exceeds 4% on any sending day. These thresholds apply per domain, not per campaign. A campaign targeting a stale list that generates 6% hard bounces in one day should pause immediately. The bounce data should feed the suppression list the same day — do not wait for a weekly hygiene run to update the suppression list after a high-bounce send.
Blocklist alert
Configure MXToolbox or a similar blocklist monitor to check all active sending domains and IPs against the major blocklist providers — Spamhaus, Barracuda, SORBS, SpamCop — on a daily schedule. Alert fires immediately if any IP or domain appears on a blocklist. Blocklisting requires removal requests submitted to each blocklist provider. Most blocklists will delist a domain within 24-48 hours after removal request submission, provided the underlying issue (spam complaint spike, spam trap hits, or authentication failure) has been corrected. Delisting without correcting the underlying problem results in re-listing within days.
Alert routing. Deliverability alerts should route to the RevOps or sales ops owner, not the individual rep. Reps do not have the context or access to diagnose domain reputation issues. The alert must reach someone who can pull the sequence data, review the bounce logs, and make the call to pause or continue. A Slack channel dedicated to deliverability alerts — with the RevOps owner and sales leadership as members — is the standard setup for teams running outbound at scale.
Inbox placement testing
Inbox placement testing is the process of sending a real email to a controlled list of seed addresses and measuring which folder each address receives the message in. It is the most direct measurement of deliverability — more accurate than reputation scores alone, because it reflects the actual placement decision the ISP makes for that domain, IP, and message combination.
How to run a seed list test
The standard inbox placement test runs in five steps:
- Obtain seed addresses. GlockApps, Mailreach, and Litmus provide seed address lists as part of their service. GlockApps provides 80+ seed addresses across Gmail, Outlook, Yahoo, Apple Mail, and other providers. Mailreach operates a network of real inboxes rather than dedicated seed accounts, which produces placement signals closer to real sending conditions.
- Send the test message. Use the same sending domain, sending IP, and message template that the live campaign will use. Do not test with a different domain or a simplified plain-text version. The placement result must reflect actual sending conditions. Send the message with full authentication in place — SPF, DKIM, and DMARC aligned.
- Wait for results. Most placement tools deliver results within 15-30 minutes. GlockApps shows placement broken down by provider: what percentage of Gmail seeds received in primary inbox, what percentage in spam, and the same breakdown for Outlook, Yahoo, and others.
- Review the placement breakdown. A healthy result shows 90%+ inbox placement across Gmail and Outlook. Any provider showing below 80% placement needs specific attention — check that provider's spam folder for the test message to understand which filters it triggered.
- Document and trend. Log placement results per domain, per week. A trend line that moves from 93% to 89% to 84% over three weeks is a warning signal even if no single data point crosses the alert threshold. Trend direction matters as much as the point-in-time value.
What to test
Test every active sending domain before a new campaign goes live. Test again after any DNS change — SPF record update, DKIM key rotation, DMARC policy change. Test after a bounce spike or spam complaint increase to confirm the domain has recovered before resuming full-volume sending. Test new domains before any warm-up sending begins to establish a baseline. A domain that starts warm-up at 60% inbox placement needs remediation before the warm-up sequence builds on a broken foundation.
Reading the results
Placement test results that show strong Gmail placement (92%) but poor Outlook placement (68%) point to an IP reputation problem with Microsoft specifically — check Microsoft SNDS for the sending IP's reputation and complaint rate. Results that show poor placement across all providers point to domain-level issues: DMARC policy misconfiguration, domain reputation decay, or message content triggering content filters. The provider-specific breakdown in GlockApps is the fastest way to separate IP reputation issues (typically provider-specific) from domain reputation issues (typically consistent across providers).
Bounce and spam trap handling
Bounce handling and spam trap defense are the two list hygiene practices that most directly protect sender reputation. Both require operational discipline — defined rules, automated enforcement, and regular audits — rather than manual case-by-case decisions.
Hard bounce handling
The rule for hard bounces is categorical: suppress immediately. When a message returns a hard bounce code (SMTP 5xx: 550, 551, 553, 554), the address goes onto the suppression list and receives no further sends from any domain or sequence. No exceptions. No "let me try one more time." Hard bounce codes mean the address is invalid or the server has permanently rejected the sender. Continued attempts after a hard bounce signal accumulate as negative reputation signals with the ISP — the receiving server logs repeated delivery attempts to addresses it has already rejected as a pattern consistent with spam behavior.
Most ESPs handle hard bounce suppression automatically within their platform. The risk is multi-platform sending: a contact suppressed as a hard bounce in one ESP may still exist as an active contact in the CRM and in a second ESP's sending list. The CRM must be the single source of suppression truth. Any contact marked as a hard bounce in any sending tool must be marked as suppressed in the CRM so the suppression propagates to all downstream tools and sequences.
Soft bounce handling
Soft bounces (SMTP 4xx temporary failures: 421, 450, 451, 452) indicate a temporary problem — full mailbox, temporarily unavailable server, or message size rejection. The standard retry protocol is three attempts across three days: retry on Day 2, retry on Day 4, suppress on Day 5 if still bouncing. This retry window is sufficient to catch most temporary conditions (vacation auto-responders, brief server outages) while not persisting long enough to generate negative reputation signals from excessive retry attempts.
Some soft bounce codes warrant faster suppression. A 452 (Too many recipients or insufficient system storage) is typically server-side and may resolve quickly. A 421 with a message like "Try again later; sending too fast" indicates a rate-limit response from the ISP — reduce sending velocity on that domain rather than continuing to retry at the same rate. Reading the bounce message content, not just the SMTP code, is necessary for correct handling.
Spam trap defense
Spam traps are email addresses operated by ISPs, anti-spam networks, and blocklist operators to identify senders with poor list hygiene. Two types require different defenses:
Pristine spam traps are addresses that have never opted in to any commercial email and never belonged to a real person. Reaching a pristine trap means the sender is using a scraped, harvested, or purchased list. The defense: never use purchased or scraped contact lists. Verify every email address before first contact using an email verification service (ZeroBounce, NeverBounce, Kickbox). These services check deliverability without sending a message and flag high-risk addresses.
Recycled spam traps are real addresses that became abandoned and were later converted to trap status by the ISP. They look like any other address in a contact database. The defense is engagement-based suppression: any contact with no email open, click, or reply in the past 12-18 months should be moved to a re-engagement campaign before continued outreach. If no engagement on re-engagement, suppress. Sending repeatedly to chronically non-engaging addresses is the behavior that most commonly results in recycled trap hits for B2B senders.
List verification cadence. Verify all addresses at first import, then re-verify any contact with no engagement in 12 months before resuming sends. Most email verification services provide bulk verification APIs that can run against the CRM contact database on a quarterly schedule. The cost of verification — typically $0.001 to $0.005 per address — is negligible compared to the sender reputation cost of a spam trap hit or a blocklisting event.
How Gangly fits
Gangly connects the deliverability monitoring layer to the outbound execution layer in a way that most standalone monitoring tools cannot — because most monitoring tools only report, they do not act on the data within the selling workflow.
When a sending domain crosses the spam rate warning threshold, Gangly flags the affected sequences in the rep's workflow view and surfaces the domain health status alongside the outreach queue. The rep sees that domain X is in warning status before they queue the next batch of sends on that domain — not after. Sequences on affected domains pause automatically at the 0.10% threshold. The rep does not need to navigate to a separate monitoring tool dashboard, identify which sequences use that domain, and manually pause each one.
Because Gangly generates outreach from real buying signals — job changes, funding rounds, hiring posts, technology installs — the messages are personalized by default. Signal-grounded outreach generates significantly lower spam complaint rates than template-based bulk sequences, because the message is relevant to the specific trigger the buyer just experienced. A generic "checking in" email sent to 500 contacts on a Tuesday afternoon produces complaints. An email that opens with "saw you are building out a new enterprise AE team" sent to a VP of Sales who posted a job listing three days ago does not read like spam to the recipient or the ISP.
Gangly also manages the bounce suppression workflow across the full sequence: hard bounces suppress immediately in the CRM record, soft bounces follow the three-retry protocol, and bounce rate metrics surface in the workflow dashboard so the RevOps owner has a unified view of sequence health without switching between the ESP's bounce report and the CRM contact list.
For AEs and BDRs managing multi-domain outbound across accounts, Gangly's domain health view consolidates the status of all active sending domains in one place — reputation tier, current spam rate, inbox placement score, and any active alerts — so the rep knows at a glance which domains are healthy and which need attention before the next batch goes out.
Gangly plans start at $99/seat (Starter), $199/seat (Growth), and $299/seat (Scale). Deliverability monitoring and bounce management are included across all plans.