If a decent share of your list uses Gmail, and for most newsletters it’s a big share, you need some way of knowing how Gmail sees you. The problem is that Gmail doesn’t tell you much directly. There’s no per-complaint feedback loop like Yahoo’s, and you can’t see where each email landed.

Google Postmaster Tools is the closest thing you get. It’s free, it takes a few minutes to set up, and it’s worth checking every week. It won’t tell you everything, but it will tell you when something’s going wrong, usually before your open and click numbers make it obvious.

One thing to know upfront: the tool changed a lot in 2025. Google retired the original version on September 30, 2025, and the new one works differently. If you’ve read older guides (including an earlier version of this one), some of what they describe is gone.

What Google Postmaster Tools is

It’s a dashboard showing how Gmail handles mail sent from your domain: how much of it users mark as spam, whether it passes authentication, whether Gmail is rejecting any of it, and whether you meet Gmail’s sender requirements.

It only covers Gmail, and only once you’re sending a reasonable volume to Gmail addresses. Smaller senders often see little or no data, which isn’t a sign of a problem.

How to set it up

Go to postmaster.google.com, sign in with a Google account, and add your domain. Google gives you a TXT record to add to your domain’s DNS to prove you own it. Verification is often close to instant, but DNS changes can take a little while to show up.

A couple of things worth knowing:

  • Add the domain you actually send from, the one in your From address. If you send newsletters from a subdomain like news.yourbrand.com, think about which level you want to monitor.
  • Data only shows for mail that’s properly authenticated with SPF and DKIM on your domain. If your ESP still signs with its own domain, sort that out first.
  • There’s no historical data. It starts collecting from the day you add the domain, so set it up before you need it.

To share access, open the domain’s settings and add other people’s Google accounts. That’s easier than sharing one login around the team.

What the dashboards show

Google Postmaster Tools dashboard showing spam rate data for a domain

The screenshot above is from the original version of the tool. The current interface looks different, but the core data is similar.

Compliance status

This is the main page now. It checks your domain against each of Gmail’s sender requirements: SPF and DKIM, DMARC, alignment, one-click unsubscribe, TLS, valid reverse DNS, and your spam rate. Anything marked as needing work is the first thing to fix, because since November 2025 Google has been actively deferring and rejecting mail that doesn’t comply.

It also includes a deliverability analysis that gives you Google’s own recommendation about your domain’s status. It’s the closest thing to a direct opinion from Gmail you’ll get.

Spam rate

This is the most useful number in the tool. It’s the share of your emails that Gmail users marked as spam, counted against mail delivered to the inbox rather than everything you sent.

Google asks senders to keep it below 0.3%, and recommends staying under 0.1%. In practice, a healthy newsletter usually sits well below that. A one-day blip after a particular send isn’t worth panicking about, but a rate that creeps up over a few weeks is. It usually means you’re mailing people who’ve forgotten they signed up, or sending more often than they expected.

Feedback loop

Gmail’s feedback loop doesn’t tell you who complained. Instead, you add a Feedback-ID header to your emails, and Postmaster Tools shows which of those IDs are getting unusually high complaint rates. It’s mainly built for ESPs spotting problem customers, and it only shows data above a certain volume, so an empty report is normal for many senders.

Authentication and encryption

These show what share of your mail passed SPF, DKIM and DMARC, and what share was sent over TLS. If your setup is right, they’ll sit near 100% and you won’t need to look at them often. A sudden drop usually means something changed: a new sending service, an edited DNS record, or a DKIM key that’s been rotated incorrectly.

Delivery errors

This shows mail Gmail rejected or temporarily deferred, with a reason. The reasons are genuinely useful, things like rate limits being exceeded, suspected spam, DMARC policy failures, low sending reputation, or a missing reverse DNS record. If this graph starts climbing, it’s telling you exactly where to look.

What’s no longer there

The old version had IP reputation and domain reputation dashboards, rating you as High, Medium, Low or Bad. A lot of guides still tell you to watch them. They’re gone from the current version.

That’s a loss, honestly, because they were a simple early warning. These days you have to infer your reputation from the other signals: your spam rate, any delivery errors citing reputation, and how your opens and clicks at Gmail compare with other providers.

Automating it with the Postmaster Tools API

Checking the dashboard by hand is fine for one domain. If you manage several brands, each sending from its own domain, it gets tedious quickly, and it’s easy to miss the one that’s slowly getting worse. That’s where the Postmaster Tools API helps.

The API gives you the same data as the dashboard, in a form you can pull into your own reports. Google made version 2 of it generally available in February 2026, and says the original version will be retired, so build anything new on version 2. With it, you can:

  • pull a domain’s statistics, like spam rate and delivery errors, for any date range in one request
  • check a domain’s compliance status against Gmail’s sender requirements, including the deliverability verdict
  • query several domains in one batch, which is the useful part when you’re looking after multiple brands

Setting it up takes a little technical work. You create a project in Google Cloud, switch on the Postmaster Tools API, and sign in with a Google account that already has access to the domains in Postmaster Tools. The API only returns data for domains that account has verified. Google’s migration guide covers the details, including which requests replaced the old ones.

What people usually build with it is simple: a scheduled script that runs once a day, writes each domain’s spam rate and compliance status into a spreadsheet or dashboard, and sends an alert when something crosses a line you’ve set, like a spam rate creeping towards 0.1%. For a team running several newsletters, one daily summary across every brand is much easier to keep on top of than logging in to check each domain.

What to do when the numbers slip

Don’t overreact to one bad day. A small spike after a single send happens. Look for trends over a week or two.

Find when it started. Use the date range to match the change against what you did. A new signup source, a big import, a change in sending frequency, a new template or a reactivated old segment are the usual suspects.

Fix the cause, not the symptom. If complaints are up, look at who’s complaining: often it’s recent signups from one source, or long-inactive subscribers. If delivery errors mention authentication, check your DNS records. If they mention reputation, cut back to your most engaged readers for a while.

Keep checking. Recovery takes time. Send to your best readers, keep complaints low, and watch the dashboards for a few weeks rather than a few days.

Is it worth the effort?

Yes. It’s the only direct view you get into how the biggest mailbox provider sees your newsletter, it’s free, and the compliance page alone can save you from finding out about a problem the hard way.

Just don’t treat it as the whole picture. It only covers Gmail, it needs a certain volume before it shows anything, and a quiet dashboard doesn’t always mean everything’s fine. Use it alongside your own numbers, broken down by provider, and you’ll spot most problems early.

References

  1. [1] postmaster.google.com — postmaster.google.com
  2. [2] sender requirements — support.google.com
  3. [3] feedback loop — support.google.com
  4. [4] Postmaster Tools API — developers.google.com
  5. [5] migration guide — developers.google.com