A deliverability case study: how a clean authentication setup masked a domain reputation problem linked to a non-opted-in list import.
Case at a glance
Domain reputation dropped from “High” to “Medium” over approximately three weeks. Spam rate at the point of investigation was 0.18%, above Google’s recommended 0.10% ceiling. The probable source was a CRM import of roughly 15,000 non-opted-in trade-show contacts, with sends touching that segment generating complaint rates of approximately 0.32%, compared to a 0.08% baseline from the existing opted-in list. Following suppression of the imported segment and a period of restricted, engagement-focused sending, spam rate returned below 0.10% by week three. Domain reputation recovered to “High” in Postmaster Tools after approximately five weeks of consistent clean sending.
The Problem: Authentication Was Clean, Delivery Wasn’t
SPF, DKIM, and DMARC can all pass while Gmail still sends your marketing emails to spam. In this case, a B2B SaaS sender had correctly configured all three protocols and confirmed authentication results were green across every tool they ran. Despite that, a growing share of their newsletter was landing in Gmail spam folders, confirmed through seed-list testing across personal Gmail accounts.
The client’s initial assumption was an ESP bug. Authentication looked fine on their end, so the problem had to be somewhere else. It wasn’t an ESP bug. It was domain reputation, and it had been deteriorating for weeks.
What Google Postmaster Tools Showed
We pulled Google Postmaster Tools data first, since the authentication layer was already confirmed clean. Two signals stood out immediately.
Domain reputation
Domain reputation had slipped from “High” to “Medium” over approximately three weeks. According to Google’s own reputation descriptions, “Medium” indicates a history of legitimate sending with occasional spam meaningful enough to affect inbox placement, even when authentication passes. “High” indicates very low spam rates and compliance with sender guidelines.
Spam rate
Spam rate was sitting at 0.18%. Google’s sender guidelines recommend keeping spam rates below 0.10% and avoiding rates of 0.30% or higher. At 0.18%, the sender was well above the 0.10% ceiling, which warranted immediate investigation.
Critically, Postmaster Tools data is not real-time. Google typically updates dashboards within 24 hours, but changes may take longer to reflect. We treated the 0.18% figure as a trend signal rather than an instantaneous measure of current sending behavior an indicator that complaint exposure had been elevated over a period of sends, not a precise snapshot of a single day.
The combination of declining domain reputation and an elevated spam rate pointed away from headers and authentication and toward recipient quality and recent list changes.
Also Read: Why Your Emails Are Going to Spam (And How Actually to Fix It): A Technical Guide
The Investigation: Overlaying Reputation Data Against Send History
Because authentication was clean, we shifted focus to identifying what had changed on the sending side. We overlaid the Postmaster Tools domain reputation history against campaign dates and CRM sync timestamps to look for a timing match.
Before concluding that a list import was the cause, we also checked for other plausible explanations: recent changes to sending volume, infrastructure modifications, authentication alignment across third-party senders, unsubscribe processing behavior, and any change in campaign content or cadence. None of those variables showed a change that corresponded with the timing of the reputation decline.
The CRM sync did.
The Root Cause: 15,000 Non-Opted-In Trade Show Contacts
A CRM sync approximately a month before the reputation decline had added roughly 15,000 contacts imported from a trade-show badge-scanning system. Those attendees had interacted with the company at an event, exchanging badge scans, but had not explicitly opted into the newsletter or any ongoing email communication. Event interaction is not equivalent to newsletter opt-in.
Google’s sender guidelines are explicit on this point: senders should only send to people who want to receive messages, and recipients should opt in directly.
To isolate the impact, we segmented sends by list source and compared complaint behavior at the campaign level. Sends touching the imported segment were generating complaint rates approximately four times higher than sends to the existing opted-in list, roughly 0.32% versus 0.08%, as measured in the sending platform by list segment.
Those figures are distinct from the 0.18% domain-level spam rate reported in Postmaster Tools, which reflects Gmail’s aggregate view of user-reported spam across all sends to the domain. The campaign-level complaint differential explains how the domain-wide Postmaster Tools figure was being driven up: the high-complaint segment was pulling the overall rate above Google’s recommended ceiling and degrading domain reputation across all sends, not just those touching the imported contacts.
Also Read: How to Stop Emails Going to Spam in Gmail: Complete Guide
The Fix: Remove the Segment and Restrict Volume to Engaged Recipients
We isolated and suppressed the imported segment entirely. We then temporarily reduced overall sending volume and restricted sends to the highest-engagement tier of the existing opted-in list for two weeks.
This wasn’t IP or domain warming in the conventional sense; the infrastructure was already established. It functioned as reputation recovery: by restricting sends to recently engaged, opted-in recipients, we reduced complaint exposure and established a cleaner sending pattern without the high-complaint segment in the audience.
The Result
In this account, spam rate dropped back below 0.10% by week three of the recovery sends. Domain reputation returned to “High” in Postmaster Tools after approximately five weeks of consistent, clean sending to the opted-in segment.
That timeline reflects what happened in this specific case. Reputation recovery rates depend on sending volume, the severity of the preceding decline, and how consistently clean the subsequent sends are. Postmaster Tools data also reflects rolling averages, not instantaneous reputation shifts.
Authentication was never misconfigured. SPF, DKIM, and DMARC passing correctly meant the delivery problem was harder to attribute at first glance because the infrastructure looked fine.
What This Case Teaches About Gmail Deliverability
Passing authentication does not equal earning inbox placement
Gmail’s sender guidelines confirm that authenticated messages are less likely to be rejected or marked as spam, but authentication verifies the sender and helps establish message legitimacy. It does not determine placement on its own. Gmail also evaluates recipient responses and other sending signals, which means a technically valid, correctly authenticated message can still land in spam if those signals are unfavorable.
Domain reputation is the metric to watch when authentication passes
If SPF, DKIM, and DMARC are healthy and delivery is still degrading, domain reputation and spam rate in Postmaster Tools are the next places to look, not headers.
List source can matter more than list size
A relatively small segment of non-opted-in contacts can produce disproportionately high complaint rates and affect domain reputation across the entire sending domain, even when the rest of the list is healthy and engaged.
Reducing volume alone was not enough
In this case, restricting sends without first removing the high-complaint segment would have slowed the damage but not addressed the cause. Suppressing the imported segment was the key intervention; reducing volume to engaged recipients supported the recovery by limiting complaint exposure while the domain’s sending pattern stabilized.
Also Read: Why Your Emails Are Going to Spam (And How Actually to Fix It): A Technical Guide
When Authentication Passes but Gmail Placement Deteriorates: The Checks That Mattered in This Case
If authentication is confirmed clean and Gmail placement is still deteriorating, work through the following in order:
- Check domain reputation in Postmaster Tools. A move from “High” to “Medium” is often the first visible signal of a complaint-rate problem.
- Check spam rate in Postmaster Tools. Google recommends keeping spam rates below 0.10%; sustained rates above that level can hurt inbox placement for bulk senders sending to Gmail.
- Look for recent list imports or CRM syncs. Overlay the reputation history against the dates of any list additions to identify a timing match.
- Segment and compare complaint rates by list source. Identify whether the complaint signal is concentrated in a specific segment.
- Check sending volume for sudden spikes. A large increase in volume without a corresponding reputation history can trigger throttling or elevated spam scoring.
- Review recent infrastructure or content changes. New subdomains, new ESP configurations, or significant template changes can affect authentication alignment.
Also Read: Case Study 2: Email Deliverability Drop After Moving to a Dedicated IP
Yash is an SEO expert, website designer, and digital marketing strategist dedicated to helping businesses grow through search-driven strategies and high-performing websites. With expertise in technical SEO, on-page optimization, keyword research, website design, and conversion-focused development, he creates digital experiences that attract traffic, engage users, and drive measurable business results.
Yash is the founder of RevealRank, an SEO and digital marketing agency that helps businesses increase their online visibility through SEO, AI search optimization (AEO), paid advertising, content marketing, and performance-focused web design. Under his leadership, RevealRank delivers tailored strategies that enable brands to rank higher in search engines, generate qualified leads, and achieve sustainable growth.
