Reading Google Postmaster Tools: Spam Rate and Compliance

Google Postmaster Tools shows how Gmail sees the mail your domain sends to personal Gmail accounts: the share reported as spam, whether it authenticates, whether it's encrypted, delivery errors, and whether you meet Gmail's sender requirements. Keep the spam rate below 0.1%, and read it alongside your engagement, because the rate only counts mail that reached the inbox.

This guide is based on Google's own Postmaster Tools dashboards documentation, as we read it on 1 October 2026. Where third-party write-ups disagree with it, we say so.

Setting it up

1. Sign in at postmaster.google.com with a Google account.
2. Add the domain you send from, meaning the domain in the From address and the one your mail is DKIM-signed with.
3. Add the TXT (or CNAME) verification record it gives you to your DNS.
4. Optionally add subdomains. Google says that once the primary domain is verified, "you don't need to verify its subdomains", and adding them lets you see their dashboards separately.

Data only appears once you're sending enough mail to personal Gmail accounts. Mail to Google Workspace business accounts doesn't count, which is why B2B senders often see little or nothing.

The dashboards at a glance

Dashboard	What it measures	Good looks like
Compliance status	Whether you meet each sender requirement	"Compliant" on every row
Spam rate	Share of inbox-delivered, DKIM-authenticated mail marked as spam by users	Below 0.1%, steady
IP reputation / Domain reputation	Gmail's rating of your sending IPs and domain: Bad, Low, Medium, High	High
Feedback loop	Spam rate per campaign, using your Feedback-ID header	No identifiers flagged
Authentication	Percentage of mail passing SPF, DKIM and DMARC	Close to 100%
Encryption	Percentage of mail sent over TLS	100%
Delivery errors	Rejected or temporarily failed mail as a share of authenticated mail	Near zero, no spikes

Four facts apply to every dashboard, all from Google's documentation:

• Not real time. "Typically, the data is updated within 24 hours but can take longer."
• UTC. "Postmaster Tools uses Coordinated Universal Time (UTC)", which matters if you're matching a dashboard day against a send at 7pm in New York.
• Gaps on quiet days. "Dashboards might not include all data on days when your outgoing email volume is low."
• Some dashboards count DKIM-signed mail only. If your platform signs with its own domain rather than yours, your domain's dashboards will be thin or empty. Set up DKIM for your own domain. Our DKIM checker shows what's published.

Compliance status

This dashboard is a checklist of Gmail's sender requirements, each marked Compliant, Needs work or No data found.

Applies to all senders	Applies to bulk senders only
SPF and DKIM authentication	DMARC authentication
DNS records (forward and reverse)	One-click unsubscribe
Message formatting	Honor unsubscribe
Encryption
User-reported spam rate

Three behaviours catch people out:

• It reports the primary domain only. If you add email.example.com, the Compliance status dashboard still shows example.com, calculated from the primary domain and its subdomains together. For a subdomain's own numbers, use the other dashboards.
• It lags by up to a week. Google says it "uses a rolling data average that's gathered over multiple days" and that after a fix "it can take up to 7 days for changes to be reflected."
• "No data found" reflects the past. "For configuration based requirements like DNS, your status reflects the settings observed when those emails are received, not your current configuration." To check your DNS as it is right now, use a live check, such as our deliverability audit.

On the "Honor unsubscribe" row, Google adds a warning worth acting on: requests count against you "whether or not your servers receive it," and if a service like Cloudflare blocks them "you're still responsible." Our one-click unsubscribe guide covers how to test for that.

The dashboard also includes a Deliverability analysis tool, which gives recommendations when you send too little mail, messages fail to deliver, you exceed the spam threshold, recipients don't engage, or you don't meet the guidelines.

Spam rate, and why low isn't always good

Google defines the spam rate as "the percent of your messages that are delivered to engaged recipient's Inbox and then marked as spam by the recipient." Mail Gmail filtered to spam on arrival isn't in the calculation.

That creates a trap. If Gmail has already started sending most of your mail to spam, few people see it in their inbox, few report it, and the dashboard rate falls. Google's own troubleshooting describes the pattern twice:

• "Spam rate seems very low compared to the typical rate": the cause given is that "Gmail is automatically sending a significant number of your messages to spam."
• "A high spam rate suddenly changed to a rate of 0": the cause given is that, after a period of high complaints, "many messages are automatically being sent to spam, and recipients aren't reporting any inbox messages as spam."

So read spam rate against something independent, such as opens, clicks, replies or a handful of Gmail seed inboxes. A falling spam rate with falling engagement is bad news.

The thresholds, from Google's sender guidelines and FAQ:

Spam rate	What Google says
Below 0.1%	The target
Above 0.1%	Already "a negative impact on email inbox delivery for bulk senders"
0.3% or higher	"An even greater negative impact"; bulk senders lose eligibility for mitigation until they're below 0.3% for 7 consecutive days

Spam rate is calculated daily, and Google says that after you fix the cause it can take up to 7 days to fall back into compliance.

Reputation, and the v2 confusion

Google's documentation describes four reputation ratings for IPs and domains:

Rating	Google's description (abridged)
High	"History of very low spam rates, and complies with Gmail's sender guidelines"
Medium	"History of sending legitimate email, but occasionally sends spam"
Low	"History of sending a significant volume of spam regularly"
Bad	"History of sending a high volume of spam regularly. Email from this domain or address is almost always marked as spam or rejected"

One detail matters for anyone sending through an ESP: "The Domain Reputation dashboard only displays messages sent from the exact domain used for DKIM and SPF authentication."

Now the confusion. Several third-party articles say that Postmaster Tools v2 removed the IP and Domain Reputation dashboards and moved everyone onto the new interface in 2025. Google's own dashboards page, as we read it on 1 October 2026, still lists both reputation dashboards and describes the ratings above. We couldn't confirm the removal from a Google source, so we're not repeating the date. If your account doesn't show reputation, treat Compliance status and spam rate as the primary signals. That is where Google's own documentation puts its emphasis either way.

Feedback loop

The feedback loop dashboard shows spam rates per campaign, but only if you tag mail with a Feedback-ID header. Google's Feedback Loop page gives the format:

Feedback-ID: CampaignID:CustomerID:MailTypeID:SenderId

SenderId is mandatory, 5 to 15 characters, and should be consistent across the stream. The other three fields are optional identifiers of your choice. The message must be DKIM-signed by your domain after the header is added. Reports appear only when an identifier has enough volume and enough distinct spam reports, so a small campaign may never show, which Google says usually means it generated very little spam.

Don't use a value that is unique to every message. Google says not to, because nothing would aggregate.

Delivery errors, authentication and encryption

Delivery errors shows rejected and deferred mail as a share of authenticated mail. A spike almost always has a matching SMTP code in your ESP's logs. Look there first. Gmail's codes name the problem directly (4.7.27 for SPF, 4.7.30 for DKIM, 4.7.28 for rate limiting), and the full list is in our bulk sender requirements post.

Authentication should be close to 100% for SPF, DKIM and DMARC. A DMARC figure below the SPF and DKIM figures usually means mail passes but doesn't align with your From domain. See moving DMARC to enforcement for how to read alignment.

Encryption should be 100%. TLS is a requirement for all senders, and most established ESPs already use it.

A diagnosis table

You see	Likely cause	Do this
Compliance: DMARC "Needs work"	No _dmarc record, or no policy in it	Publish v=DMARC1; p=none; rua=...; wait up to 7 days
Compliance: one-click "Needs work" but headers are present	Spam reports on mail that lacks the headers (another stream?)	Use the Feedback Loop dashboard to find which mail
Spam rate 0.15% and rising	List or targeting problem	Cut older, unengaged segments; check signup sources
Spam rate near zero, engagement falling	Mail going to spam on arrival	Check seed inboxes; reduce volume to engaged recipients only
Domain reputation falls after a new campaign	That campaign's audience	Pause it; review list source and bounce rate
Delivery errors spike	Rate limiting or authentication failure	Read the SMTP codes; back off per Google's 4.7.28 guidance
All dashboards empty	Low volume to Gmail, or DKIM signed by your ESP's domain	Set up custom DKIM; accept that B2B-only senders may see little

The practical takeaway

Check Compliance status weekly and after any change to your sending setup, remembering it lags by days. Read spam rate daily against an independent engagement measure, and treat 0.1% as the ceiling. When a dashboard moves, find the matching SMTP codes in your sending logs before changing anything. Postmaster Tools tells you how Gmail sees you. Your bounce logs tell you why.