Google Postmaster Tools guide: setup, metrics, and fixes

Google Postmaster Tools is the closest thing to a reputation dashboard the email world offers. It's free, it's the canonical source for how Gmail sees you, and it's the first place to look when placement degrades. If you send any volume to Gmail, you should be reading PMT every Monday.

If you need the broader reputation map, start with the reputation hub and then use PMT to validate the Gmail-specific side of the problem.

Setup in three steps

The eight dashboards

Reading domain reputation

Reputation is bucketed: Bad / Low / Medium / High. Movements between buckets are the signal — a steady High is unremarkable; a drop from High to Medium is a fire alarm. The dashboard updates daily but reflects rolling 7-day windows.

The Feedback Loop campaign IDs

Gmail's FBL is dashboard-only — but it's per-campaign if you set the Feedback-ID header. Add the header to every send, and PMT will show you which campaigns generate complaints. This is the single most useful diagnostic tool in your kit.

Feedback-ID: <CampaignID>:<CustomerID>:<MailType>:<SenderID>

# Example:
Feedback-ID: spring-promo-2026:cust-1234:marketing:example.com

When dashboards are empty

• Below ~100 messages/day to Gmail — Google won't display data.
• Recent reputation reset — domain reputation can briefly go blank during resets after a major change.
• Verification expired — re-verify if the TXT record was removed.
• New IP — IP reputation populates only after the IP has been sending for several days.

What PMT doesn't tell you

• Per-message decisions — no log of which messages went to spam.
• B2B vs consumer breakout — all Gmail traffic is mixed in.
• Yahoo, Microsoft, Apple — different receivers, different (or no) tools.
• Inbox placement % — inferred via seed-list services, not exposed by Google.

Additional guidance: Google Postmaster Tools v2: The Compliance Dashboard Guide

Google Postmaster Tools v2 is Gmail's free report card for senders: verify your domain once at postmaster.google.com, and Google shows your spam rate, SPF/DKIM/DMARC pass rates, encryption, and sender compliance status in one Compliance dashboard. Keep your reported spam rate under 0.1% and every compliance row green — that is the entire game for Gmail inbox placement in 2026.

Most senders set it up, glance at the domain reputation dial once, and never come back. That's a waste. Here's how to actually read it.

What changed in v2 — and why it's better

Postmaster Tools v1 was a collection of disconnected dashboards: domain reputation here, IP reputation there, spam rate somewhere else, each with its own quirks. Google retired v1's interface and consolidated around a domain-based model in v2.

The structural changes that matter:

• One verification, whole-domain data. Verify the domain once (DNS TXT record), and you see data aggregated across that domain — no per-subdomain archaeology unless you add subdomains separately.
• Compliance Status dashboard as the front page. Instead of hunting across panels, v2 leads with a single view showing whether you meet Gmail's sender requirements: authentication pass rates, spam rate, one-click unsubscribe, and more.
• Spam rate front and center. The user-reported spam rate got promoted from a buried chart to a headline compliance metric with explicit thresholds.

The philosophy shift is the point: Google stopped making you infer compliance from scattered charts and started telling you directly, row by row, whether you pass.

Setting it up (10 minutes, once)

1. Go to postmaster.google.com and sign in with a Google account — again, use a shared team account, not an individual's.
2. Add your sending domain (the root domain you send from, e.g., example.com).
3. Google gives you a TXT record to publish:

TXT @ "google-site-verification=abc123..."

1. Publish it, click verify. Data starts appearing within roughly 24–48 hours, with a daily lag.

Two gotchas. First, if you send from subdomains (mail.example.com, news.example.com), data rolls up under the verified root domain, but adding the subdomains separately gives you per-subdomain views — worth doing if your mailstreams differ. Second, verify with the domain you authenticate with (your DKIM d= domain and/or SPF domain), since that's what Google attributes reputation to.

The Compliance Status dashboard, row by row

This is the view to check weekly. Each row maps to a requirement from Google's sender guidelines:

The beauty of this dashboard is that it converts "why is Gmail rejecting me" into a checklist. If a row goes red, that's your answer. Since November 2025, Gmail has been issuing permanent 5xx rejections for bulk mail that fails authentication requirements:

550 5.7.26 This mail has been blocked because the sender is
unauthenticated. Gmail requires all senders to authenticate with
either SPF or DKIM.

If you're seeing that rejection, the Compliance dashboard will show exactly which authentication row failed. Our Gmail 550 5.7.26 error fix guide walks through remediation row by row, and the Gmail/Yahoo bulk sender rules post covers the full requirement set this dashboard is grading you against.

The spam rate panel: the number that runs your life

The spam rate in Postmaster Tools is the percentage of your inboxed mail that Gmail users marked as spam. Two numbers define your life:

• Under 0.1% — the target. Google's stated expectation for healthy senders.
• 0.3% — the ceiling. Sustained rates at or above this put you in rejection/bulk-folder territory, and Google has said plainly that senders above it lose eligibility for mitigation.

Why Postmaster spam rate ≠ your ESP's complaint rate

This trips up everyone. Your ESP reports complaints based on feedback loops — and Gmail's feedback loop is not a per-user complaint feed. The Postmaster spam rate is computed by Google from its own user signals, on mail delivered to the inbox, among users with sufficient history. Consequences:

• Your ESP might show 0.05% complaints while Postmaster shows 0.25%. Both can be "correct" — they measure different populations.
• Postmaster's rate is the authoritative one for Gmail placement. Optimize against it, not your ESP's number.
• Mail that lands in spam doesn't generate spam reports the same way, so paradoxically, a deliverability collapse can lower your measured spam rate. Don't celebrate a dip during a placement crisis.

Also note the volume threshold: Google only shows spam-rate data for days and domains with meaningful volume (historically on the order of a few hundred+ messages to Gmail per day). Low-volume senders will see empty charts — absence of data is not a zero spam rate.

IP reputation vs. domain reputation: read domain first

Postmaster Tools still shows both reputation panels — typically graded Bad / Low / Medium / High — but the weight has shifted decisively. Gmail's filtering since 2024–2025 is domain-reputation-first: your DKIM-signing domain carries your history with it, across IPs, across ESP migrations.

Practical implications:

• Domain reputation is your credit score. It moves slowly, in both directions. A week of spammy behavior can take a month of clean sending to repair.
• IP reputation still matters for new infrastructure — a fresh IP with no history gets scrutinized — but a High domain reputation on a Medium IP generally delivers fine.
• Shared-IP senders: IP reputation reflects everyone on the pool. Another reason domain reputation is the metric you control.

For the full argument and the cases where IP still dominates (Outlook consumer, corporate filters), see domain reputation vs. IP reputation.

The Feedback Loop tab

Gmail's feedback loop (FBL) works differently from everyone else's. You don't get per-complaint messages. Instead, you embed an identifier header in your mail (via your ESP's FBL support), and Postmaster Tools shows complaint rates aggregated by that identifier — campaign ID, list ID, whatever you choose.

Set it up if you send multiple mailstreams from one domain. Without identifiers, you see one blended complaint rate and can't tell whether your newsletter or your re-engagement campaign is the problem. With them, the Feedback Loop tab becomes a per-campaign spam rate report. Mechanics and caveats (including which ESPs support it) are in our email feedback loops guide.

The API: pull it before it expires

Postmaster Tools keeps a limited history window, and the Compliance view is inherently "today." The Postmaster Tools API lets you pull daily domain stats — spam rate, reputation, authentication pass rates, encryption — into your own warehouse.

What practitioners build with it:

• Trend charts over 6–12 months. Domain reputation decay is gradual; the dashboard's short window hides it.
• Alerts on spam rate crossing 0.1%, so you catch the climb at 0.12% instead of discovering 0.4% two weeks later.
• Cross-provider views. Gmail spam rate next to Microsoft SNDS complaint rate next to your bounce logs. Reputation problems rarely hit one provider in isolation — the cross-check tells you whether you're looking at a Gmail-specific issue or a mailstream-wide one.

If you don't want to run the pipeline yourself, this is one of the things WillItInbox does out of the box: it syncs your Postmaster Tools data (plus Microsoft SNDS and Yahoo imports) into the same monitoring view as your DMARC drift scans and deliverability test scores — so when your Gmail spam rate starts climbing, you see it next to the authentication and DNS state that explains it. The free deliverability tester covers the per-message side (authentication, DNS, headers, content, links across 70+ checks), and the sender compliance checker grades your domain against the same bulk-sender requirements the Compliance dashboard measures. For the ongoing picture, the DMARC and domain monitoring view is where Postmaster Tools syncs land — your Gmail spam rate and reputation trend alongside DMARC alignment and domain drift scans, instead of in a separate tab you forget to open.

A weekly operating rhythm that actually works

Postmaster Tools only pays off if it's part of a routine, not a panic-visit. The cadence we recommend to senders above ~5,000 Gmail recipients a day:

Daily (30 seconds, automated): spam rate and compliance status. If you're pulling the API, alert on spam rate > 0.1% for any day, or any compliance row flipping from green. If you're not automated, at minimum check after every major campaign.

Weekly (10 minutes): the full dashboard. Look at the 7-day spam-rate trend, not any single day — daily numbers are noisy at moderate volumes. Check the domain reputation dial for drift from High to Medium. Scan authentication pass rates for dips below ~99%, which usually mean a new sending service went live without DKIM configured, or a DNS change broke SPF.

Monthly (30 minutes): correlate. Overlay spam-rate spikes on your campaign calendar. The senders who stay out of trouble are the ones who can say "the 0.14% day was the re-engagement blast to 18-month-inactive subscribers" and then kill that campaign type. Also review which subdomains and mailstreams carry the worst rates — Postmaster's per-subdomain views make this easy if you verified them separately.

After any infrastructure change: ESP migration, new dedicated IP, new subdomain, DNS provider move — check authentication rows within 48 hours. Most "Gmail suddenly hates us" incidents trace to a change someone made, not a Google policy shift.

One discipline that separates professionals from tourists: write down your baseline. If your normal spam rate is 0.04%, a 0.09% day is a 2x anomaly worth investigating even though it's technically "under threshold." Thresholds are where Google punishes you; your baseline is where you catch problems early.

What Postmaster Tools won't tell you

Keep the blind spots in mind so you don't over-trust the tool:

• No user-level data. You will never see who marked you as spam. Aggregate only.
• Minimum volume thresholds. Quiet days and low-volume domains show nothing. A gap in the chart is not a clean bill of health.
• Gmail consumer only. Google Workspace (business Gmail) uses overlapping but not identical filtering, and Postmaster data reflects the consumer side.
• No content or placement diagnostics. It tells you that users complain, not why. Diagnosis still requires test sends, header analysis, and your own engagement data.
• Delayed data. Roughly 24–48 hours behind. It's a rearview mirror — a good one, but a mirror.

Use it as the authoritative record of how Gmail sees you, and pair it with real test sends for the "why."

Use the Microsoft SNDS guide for Outlook-specific evidence, domain monitoring for DNS and authentication changes, DMARC monitoring for unknown sender sources, and a deliverability test for the actual message.

Continue this inbox placement and reputation monitoring workflow with the commercial page, the core guide, the implementation docs.