- Grow 📧 Monetize
- Posts
- 📩 Gmail's seven verdicts, decoded
📩 Gmail's seven verdicts, decoded
Passing every check is not the same as reaching the inbox
Gmail deliverability takes more than a correctly configured sending domain.
You need three things working together: a sound technical setup, subscribers who understand what they signed up for, and a routine for adjusting your sending as their response changes.
This is the playbook I use for newsletters that are healthy and for newsletters that are in trouble.
One note before we start. I will flag what Google actually requires separately from my own operating rules. The segment windows and performance thresholds below are my practices. They are not Google's filtering formula, and they do not guarantee inbox placement.
A CRM so smart, it updates itself.
HubSpot's CRM is so smart, it now updates itself. Calls get logged and summarized the moment they end. New leads get researched and a first outreach drafted, automatically. Deals move forward on their own, with next steps flagged before you have to ask.
Even the one repetitive task you've been meaning to fix can now run itself, no code required. Customers using it are already seeing the difference.
This isn't the CRM you have to work hard to figure out. It's the one already working before you log in.
*Ad
1. Set up Postmaster Tools while things are calm
Before you change a segment or try to diagnose a Gmail problem, set up Google Postmaster Tools and verify your sending domain.
Your ESP shows you the sending side. Postmaster shows you Google's view: spam complaints, compliance, authentication, and delivery errors.
You need both to understand what is happening.
Do this while performance is healthy, so checking it becomes routine. If you wait until clicks drop or complaints spike, you start your investigation with no baseline to compare against.
You can read that data in Postmaster directly or pull it into a monitoring platform. Either way, getting Gmail's own numbers is step one.
2. Name the problem before you touch anything
First, separate delivery failures from a drop in reader response. Each symptom points somewhere different:
Messages rejected: start with the exact rejection reason, authentication, DNS, and message formatting.
Messages delayed or rate-limited: start with the SMTP response, your sending pace, and recent volume changes.
Messages accepted but response drops: start with Postmaster reporting, audience selection, acquisition, and content.
Complaints increase: start with signup expectations, sources, frequency, and audience expansion.
A "delivered" event only means the receiving system accepted the message. It does not tell you where it landed.
Promotions is also an inbox tab. Treat a tab-placement concern separately from mail going to spam.
Before changing anything, write down when the problem started and what changed around that time. That is your starting point.
3. Check the technical foundation on a live send
If you send 5,000 or more messages a day, Gmail's Email Sender Guidelines expect the following:
Compliance status reviewed in the Postmaster Tools dashboard.
SPF and DKIM authentication.
DMARC with alignment to the visible From domain.
Valid forward and reverse DNS.
TLS encryption.
Proper message formatting.
One-click unsubscribe headers plus a visible unsubscribe link.
Google accepts p=none as the minimum DMARC policy. Stronger enforcement should come after you have verified every legitimate sending source. My recommendation is p=quarantine, and realistically p=reject, because I expect full enforcement to arrive eventually.
Inspect an actual live campaign to confirm all of this. A "connected domain" badge in your ESP is not a substitute for checking the message it really sends.
Confirm that unsubscribes are processed within 48 hours. A footer link alone does not replace the required one-click headers.
Two details people miss. Google's published requirements apply to personal Gmail accounts and do not apply identically to inbound Google Workspace mail. And once you are classified as a bulk sender, that label sticks, even if your volume later falls.
If a technical check fails, fix it first. Segment changes will not solve a technical problem.
The holiday streaming season is almost here
Are you ready? As revealed in our holiday playbook, Roku Ads Manager lets you easily set up, measure and optimize your self-serve holiday ad campaign. You can even create a shoppable ad unit that lets streamers buy directly from their remote.
*Ad
4. Read Postmaster as a set of answers
Once your domain is verified, put Postmaster in your regular review. I look at compliance status, Deliverability Analysis, spam rate, authentication, encryption, and delivery errors together, because each answers a different question.
Are we meeting Google's requirements?
Are messages failing?
Are readers reporting us as spam?
Is Google flagging a problem with how recipients interact with us?
What Google's seven verdicts mean, and what I do about each
Google documents seven reasons behind its Deliverability Analysis verdicts. They point at what needs attention, though they do not reveal every signal Google uses. The responses are mine.
✅ "Users signal they want to get your email messages." A positive reader-feedback signal. Encouraging, but no guarantee every message reaches the inbox. What I do: keep the strategy that is working. Test increases in frequency, acquisition, or audience size one at a time rather than treating a good verdict as permission to expand everything.
⚠️ "Users signal they don't want to get your email messages." Google is seeing negative recipient feedback, and its documentation does not say which behaviors add up to this verdict. What I do: tighten the sending audience and review acquisition, frequency, and signup expectations. If something changed recently, start there. Passing authentication will not fix an audience problem.
⚠️ "Users don't take action on your messages." Google is reporting limited recipient action without naming which engagement metric is responsible. I would not dismiss it. What I do: review recent clicks, the age of the sending audience, and how much of the segment qualifies only through opens or the new-subscriber window. Check whether the content still matches the reason people subscribed.
⚠️ "Not enough outgoing email." Google does not have enough qualifying volume to assess you. This is neither good nor bad. What I do: keep a steady cadence to subscribers who want the newsletter. Do not add unengaged recipients or invent extra sends just to make a dashboard fill in.
🚨 "You don't meet our sender requirements." A sender-compliance issue. Open the compliance details to see which requirement failed. What I do: fix that specific failure. Authentication, DNS, unsubscribe handling, and spam complaints each need a different fix, and a generic "needs work" label is not enough to choose one.
🚨 "Your spam rate is high." This may appear as "You don't meet our sender requirements," with "needs work" showing in the Compliance Status section. Google's API defines it as a spam rate above 0.10%, so you can see this warning while still under 0.30%. What I do: investigate immediately instead of waiting for the higher line. Review recent acquisition, audience expansion, frequency, and content changes, then pull back whatever is driving the complaints. 0.30% is not a comfortable operating target.
🚨 "Many messages have delivery errors." This may also appear as "You don't meet our sender requirements," with "needs work" under Compliance Status. The verdict alone does not identify the cause. What I do: get the actual SMTP responses from the ESP. Work out whether Gmail is temporarily deferring or permanently rejecting messages, then address the stated reason. Not every failure means a bad address.
Green checkmarks do not answer every question
A domain can pass every compliance requirement and still get an unfavorable reader-feedback verdict.
That is not a contradiction. Authentication proves who sent the message. It says nothing about whether the recipient wants to keep receiving it.
I read the compliance checks and the Deliverability Analysis together, then compare them with our sending history and reader response. If the technical checks pass but Google flags negative feedback, that is my cue to examine the audience and sending strategy instead of hunting for a DNS fix.
Postmaster data is not real time, either. What you change today may not show up right away.
Your ESP is missing part of the complaint picture
Gmail does not send individual spam complaints back to your ESP through a traditional feedback loop. So a low complaint rate in your ESP does not mean Gmail subscribers are not hitting the spam button.
Google provides aggregate reporting through Postmaster Tools, including campaign-level feedback when the required identifiers and reporting thresholds are met.
Aim to keep Gmail's reported spam rate below 0.10%, and never reach 0.30%. The higher number is a ceiling, not a target to hover just under.
A low spam rate can still hide a problem
When more of your messages go straight to spam, fewer reach inboxes where readers can report them. Your complaint rate can fall while your deliverability gets worse. Google notes this itself: more automatic spam placement means fewer chances for inbox recipients to complain.
That is why I pair the spam rate with delivery errors, unique clicks per send, and click rate. I also check whether we changed the sending audience or volume.
A falling complaint rate is good news when reader response is holding or recovering. On its own, it does not mean the problem is fixed.
5. Build a Gmail Base Sending Segment
My Base Sending Segment (BSS) has three ways in and one way out:
Recent click, OR
Recent open, OR
Recent signup.
Suppressions (unsubscribes, complaints, and the rest) apply across the entire segment.
A general example: clicked within 60 days, OR opened within 30 days, OR subscribed within 10 days.
That shows the structure. It is not a blanket recommendation for every Gmail newsletter. For frequent newsletters, I use tighter Gmail windows when performance calls for it.
Watch the opener and new-subscriber filters closely, because they can keep someone eligible without any recent click.
And review who actually qualifies through each filter. A smaller click window does not make the whole segment stricter if a broad opener filter still lets the same people in.
6. Expand a healthy program slowly
To test higher frequency, build a separate clickers-only segment using the recent-click window from your Gmail BSS.
Add one extra weekly send to that group. Review unique clicks per send, click rate, complaints, and delivery across several sends before adding another.
Once frequency is stable, test a slightly wider click window:
Widen it in both places, the BSS and the clickers-only segment.
Hold frequency steady.
Review the resulting sends.
Continue only if the signals stay healthy.
Widen opener eligibility separately, and only after clicker performance is stable.
Handle acquisition the same way. Do not increase incoming subscribers, broaden eligibility, and add sends all at once. Google itself advises gradual volume increases and consistent pacing over sudden bursts.
Attio is the #1 fastest-growing CRM on Brex and Ramp.
Built for the most ambitious companies in GTM, Attio is an end to end revenue platform that allows teams to run multiple plays across different revenue motions and lifecycles.
Teams at the frontier are already building on it: Granola, turbopuffer, Modal, and many many more.
*Ad
7. Decide your tightening triggers in advance
My main engagement warning: unique clicks per send fall at least 30% for three consecutive sending days, compared with the preceding 14-day average.
So if comparable Gmail sends averaged 1,000 unique clicks and now produce 700 or fewer for three sending days, I investigate.
Compare like with like. A deliberate audience reduction can lower total clicks without meaning placement got worse. Check audience size, click rate, content, and any measurement changes.
Here is how I respond to each signal:
Gmail complaints reach or exceed 0.30%: investigate immediately.
Complaints exceed 0.30% on three sending days within seven calendar days: escalate restrictions on acquisition and new subscribers.
Google indicates recipients do not want the mail: tighten the audience immediately.
Sharp open-rate decline: cross-check clicks, delivery errors, and provider reporting.
Authentication or DNS failure: fix the technical issue.
The repeated-complaint rule is an escalation step. It is not a reason to ignore the first bad day.
When complaints rise, inspect the signup experience and acquisition changes. When clicks fall, also check content, frequency, and who is still eligible.
8. Tighten in stages, openers first
When the evidence says the sending audience is weakening, I usually shrink the opener and new-subscriber windows first. For example:
Openers: a 30-day window becomes 15 days.
New subscribers: a 10-day window becomes five days.
Clickers: recent clickers still qualify through the click filter.
If performance keeps sliding, tighten again. An opener window might move 30, then 15, then 7, then 3 days, depending on where you started and how bad it is. As the opener window nears seven days, I also reassess the click window and shorten it where needed.
For persistent Gmail problems, I switch to a separate seven-day-clickers-only segment. Neither an open nor a recent signup gets someone into those recovery sends.
If performance stays weak but messages are still being accepted, I keep sending to that restricted recent-clicker segment while I investigate. I do not recommend halting sends entirely just because engagement or inbox placement is poor.
I would only consider pausing Gmail traffic if messages are not being delivered and a high share of sends are returning delivery errors. In that case, the error responses tell you what to fix and when to resume.
That is a conditional recovery move, not the first response to every dip.
9. A severe collapse gets a harder response
An open-rate drop of more than 50% for three consecutive sending days triggers an urgent review in my playbook.
I confirm it against clicks and delivery data before treating it as a placement problem. Open tracking alone can mislead you.
A first restriction might be: opened within one day, OR clicked within 30 days, with the new-subscriber exception removed.
For a fuller Gmail repair, I go to seven-day clickers only.
During repair, I want unique-click volume to rebuild to at least 70% of the comparable pre-decline baseline before I consider expanding. I judge that alongside complaints, delivery, and audience size.
That checkpoint keeps me from declaring victory because a tiny segment posts an impressive click rate. It is not a promise that every restricted audience can hit it.
10. Restore eligibility one step at a time
For routine tightening, my default is to hold the restricted level for seven sending days. Before expanding, I want click rate above the pre-tightening average for that whole stretch, with complaints and delivery also healthy.
Then restore one step.
If opener eligibility went from 30 days to 15 to 7, walk it back the same way. Do not jump from seven straight to 30.
Partial steps help too. If you cut a 60-day window to 30, try 45 before going back to 60.
For a deeper repair, one possible path: seven-day clickers, then 15-day clickers, then 30-day clickers with seven-day openers.
Keep frequency steady while you change eligibility, and review each expansion before making the next.
My step-back trigger: comparable click performance drops 30% for two consecutive sending days versus the last stable level.
Remember that rolling windows keep moving. Preview the qualifying audience before you expand. A bigger window may add fewer people than you expect, because their last engagement has aged too.
Subscribers who stay outside regular sending need a defined reactivation and sunset process. Repeatedly widening the BSS to reach them defeats the whole point of restricting it.
11. Handle deferrals by the error code
Temporary rate-limiting is a different problem from audience recovery.
For Gmail quota error 4.7.28, Google tells senders to pause for at least 10 minutes, identify the quota involved, and retry through a single connection. If that fails, wait another 10 minutes. Your ESP should be handling this retry and pacing for you.
A temporary deferral does not prove an address is invalid. A permanent policy rejection does not necessarily mean the mailbox is gone, either.
Get the exact response before you decide whether to suppress a recipient or repair your sending setup.
Eligible, compliant bulk senders can escalate unresolved delivery issues to Google. Google's condition of seven consecutive days of acceptable spam rate for mitigation eligibility is separate from my seven-sending-day observation window. Neither guarantees recovery.
12. How I watch Gmail day to day
I use a monitoring dashboard that breaks newsletter performance out by mailbox provider and pulls Google's reporting into the same workflow. Here is the order I work in:
Start with the affected provider. I review delivery, clicks, unsubscribes, and complaints for Gmail on their own. Overall numbers can hide a provider-specific decline.
Review the alert and the trend. I check what triggered the alert, whether it is sustained, and which dates the readings cover. Then I line that timeline up against acquisition changes, segment adjustments, and frequency.
Check the compliance details underneath. This tells me whether I am looking at a technical requirement or a reader-response problem.
The tool surfaces the issue. I decide what to change and watch the sends that follow, looking for enough evidence to keep the adjustment, tighten further, or start restoring eligibility.
13. Your weekly Gmail review
Once a week, and more often during a problem, answer these:
Technical: are messages failing checks or being deferred?
Postmaster: what does it report, and how recent is that data?
Clicks: are unique clicks per send and click rate holding?
Eligibility: who qualifies through clicks, through opens, and through the new-subscriber window?
Changes: what moved in acquisition, frequency, content, or infrastructure?
Results: what did you adjust, and what happened afterward?
Write down the answers and the dates of every change.
That record makes the next call easier. You can see whether you are repeating a pattern, whether an adjustment worked, and whether an improvement has lasted long enough to justify expanding.
Reply and tell me which Postmaster verdict you are seeing right now. If it is one of the yellow or red ones, I want to know what changed right before it showed up.
GM.



