Google Postmaster Tools for Cold Email: How to Read Every Metric

Google Postmaster Tools for Cold Email: How to Read Every Metric

Google Postmaster Tools is the only place Gmail tells you the truth about your sending. Every other deliverability signal you have access to is inference: seed tests, open rates, reply rates, third-party inbox placement scores. Postmaster Tools reports what Gmail itself recorded.

It is also narrower than most people assume, and for cold email specifically it has a structural blind spot worth understanding before you rely on it.

What it covers and what it does not

Postmaster Tools reports on messages sent to personal Gmail accounts, meaning @gmail.com and @googlemail.com addresses. Mail you send to Google Workspace business addresses does not appear. Most B2B cold email lands in Workspace inboxes, so the data you see is a sample of your consumer-domain traffic rather than a picture of your whole campaign.

That sample is still the best proxy available, because Gmail applies the same core reputation machinery to both. Treat it as an early warning system rather than a full report card, and pair it with bounce rate and reply rate data from your sending platform.

Setup takes minutes: add your sending domain at the Postmaster Tools site and verify ownership with the DNS TXT or CNAME record Google provides. Add every sending domain you own, not just the primary one.

The dashboards, one by one

Compliance status

Each of Gmail's sender requirements gets one of three states: Compliant, Needs work, or No data found. This is the fastest triage screen in the product. If authentication, TLS, PTR records, unsubscribe headers, or spam rate are out of line, this dashboard names which one before you have to interpret any graphs.

"No data found" is common for cold email domains and usually means volume to personal Gmail is too low for Google to report, not that something is broken.

Spam rate

Google defines it as the percent of your messages that are delivered to an engaged recipient's inbox and then marked as spam by that recipient.

Two implications people miss. First, the denominator is inbox-delivered mail to engaged recipients, so messages already filtered to spam do not count. A collapsing spam rate can mean your mail stopped reaching the inbox at all. Second, it is a recipient action, so it measures how your copy and targeting land, not your infrastructure.

The thresholds: Gmail requires bulk senders to stay below 0.30 percent and recommends staying below 0.10 percent, avoiding 0.30 percent entirely. For cold outbound, treat 0.10 percent as the ceiling, not the target. Compare against cold email spam rate benchmarks before deciding whether a spike is yours or seasonal.

Domain reputation and IP reputation

Both use the same four-tier scale. Google's own definitions:

Domain reputation follows the From domain. IP reputation follows the sending IP, which on shared infrastructure you do not control alone. If your domain reputation is High while IP reputation is Medium, the problem belongs to your provider's neighbourhood, not your list.

The tier is the wrong thing to watch day to day. The direction is the right thing. A domain sitting at Medium and climbing is healthier than one sitting at High and sliding.

Authentication

Percentage of your mail passing SPF, DKIM, and DMARC. Anything below 100 percent on a domain you fully control means a sending source is misconfigured. Find it before it costs you anything, using the SPF, DKIM, and DMARC setup guide and your DMARC aggregate reports.

Encryption

Percentage of authenticated traffic carried over TLS, inbound and outbound. Modern providers are at or near 100 percent. A dip points at a misconfigured relay.

Delivery errors

Percentage of authenticated mail rejected or temporarily failed, broken out by reason. This is where rate limiting, policy blocks, and bad recipients surface with Gmail's own wording. When a campaign goes quiet, this dashboard tells you whether Gmail is throttling you before your platform's bounce log does.

Feedback loop

Spam rates for campaigns tagged with a feedback loop identifier. Only useful if your sending platform sets FBL headers, which most cold email platforms do not. Skip it unless yours does.

What to do at each reputation tier

The honest operating rule is that reputation is a lagging indicator with a slow recovery curve. By the time a domain reads Low, the sends that caused it happened weeks ago.

• High and stable. Keep going. Increase volume in small steps and watch spam rate rather than reputation for the first signal.
• High and falling. Look at what changed 7 to 14 days ago: a new list source, a new copy angle, a volume jump. Roll that change back before the tier moves.
• Medium. Halve volume on that domain, cut the weakest list segment, and verify everything you are about to send. Do not add new copy variables while you are diagnosing.
• Low. Stop cold sending from the domain entirely. Some operators try to warm their way out; in practice the calendar cost usually exceeds the cost of a replacement domain.
• Bad. Retire it and make sure the replacement domain does not share the same list, copy, or sending pattern that got you here.

This is why we maintain 3x sending capacity for every client campaign. Domains degrade, and the operators who survive it are the ones with spare capacity already warmed.

The cold email blind spot

Postmaster Tools was built for bulk senders running high volume through few domains. Cold email is the inverse: low volume across many domains. Two consequences.

First, per-domain volume to personal Gmail is often below Google's reporting threshold, so you get sparse data or none at all. Google withholds data on low-volume days to protect user privacy. The fix is to add every domain and read them as a portfolio: if three of your twelve domains show Medium, that is a signal even when the other nine show nothing.

Second, reputation is domain-level, so a single bad list dropped onto one domain does not poison the rest. That is the argument for domain separation, and it only works if you are actually monitoring each domain rather than assuming the pool is fine.

Pair the dashboards with a blacklist check whenever delivery errors spike, keep verification tight enough that bounces never contribute, and make sure your compliance footing is solid so complaints stay rare in the first place. For the wider picture, the deliverability guide covers what to change once the data tells you something is wrong.

Want someone watching these dashboards across your whole domain pool? Get a free campaign plan and we will show you how the monitoring is set up.