Skip to content
MailToolFinder
How-To

Google Postmaster Tools v2: A Gmail Deliverability Guide

By MailToolFinder Team · · Updated · 8 min read

Google Postmaster Tools helps you investigate mail sent to personal Gmail accounts. Its dashboards show compliance, user-reported spam and delivery errors, but a dashboard alone cannot explain why your campaign changed. You also need the sending logs and audience history behind it.

Google’s current deprecation notice, checked October 10, 2026, says it has postponed retirement of the legacy v1 web interface. It encourages a move to v2, which launched in 2024 and excludes the old Domain and IP Reputation dashboards. It gives no revised web retirement date. The v2 API is available, and Google says it plans to retire the v1 API and asks developers to migrate.

This guide uses v2 Compliance Status and your own evidence to diagnose Gmail delivery problems.

What you need before you start

You cannot investigate what you are not measuring. Before a problem hits, have these four things in place:

  • Postmaster Tools access, with domain ownership verified using Google’s TXT or CNAME procedure. Compliance Status reports for the primary domain and includes subdomain traffic; it does not provide a separate compliance verdict for each sending subdomain.
  • Gmail’s Feedback Loop configured, using a Feedback-ID header to group complaint data by campaign or stream. Check your platform’s implementation and Google’s DKIM and domain verification requirements.
  • Event-level data from your sending platform (accepted, deferred, rejected, bounced, opened, clicked, unsubscribed) filterable by recipient domain. If you cannot isolate Gmail from everything else, you cannot tell a Gmail problem from a general one.
  • A record of what you changed and when. Sending volume, audience source, DNS edits, template changes, platform migrations. Most deliverability investigations end with “we changed something three weeks ago.”

Step 1: Confirm you actually have a Gmail problem

Start by establishing what changed, when it changed, and who it affected. Three questions, in that order.

Segment your last 90 days of sending by recipient domain. If accepted rates and engagement fell across Gmail, Outlook, and Yahoo at the same time, investigate shared changes to your sending setup or audience first. If Gmail alone declined, keep going. If Gmail held steady while another provider dropped, you have been investigating the wrong mailbox provider for the last hour.

Also check where the mail is landing. Marketing email arriving in the Promotions tab is not a deliverability failure. That is where Gmail files marketing email, and chasing it into the Primary tab is a losing project.

Step 2: Read Compliance Status before anything else

Read the checks that apply to your traffic in the Compliance Status dashboard. Google distinguishes requirements for all senders from bulk-sender checks, including DMARC and one-click unsubscribe. Status can show Compliant, Needs work or No data found; it is not a universal binary test.

Google’s sender guidelines require reported spam rates below 0.3% and recommend staying below 0.10%. The recommended target is not the same as the required ceiling.

Fix anything failing here first. A broken DKIM signature on one sending subdomain explains a lot more than any reputation score ever did, and it is a concrete thing you can repair this afternoon. Our SPF, DKIM and DMARC guide covers the records themselves.

Compliance does not guarantee inbox placement. Check your current configuration as well as dashboard status, which can reflect earlier traffic and take several days to catch up.

Step 3: Treat Deliverability Analysis as a clue

Google documents Deliverability Analysis under Compliance Status. Its recommendations cover insufficient volume, failed delivery, complaint levels, recipient interaction and sender requirements. The categories below paraphrase those topics; they are not exact interface messages or proof of a single cause.

Diagnostic category (paraphrased) Possible issue to investigate Where you look next
Insufficient sending volume Google may lack enough data Your own event data; do not inflate sends for the dashboard
Failed delivery Rejections or deferrals may be elevated SMTP response codes, volume changes, one stream or all
Sender requirement issue One or more applicable requirements need attention Compliance Status for the specific check
Elevated reported spam Inboxed mail is generating complaints Feedback-ID data by campaign, audience and acquisition source
Negative recipient feedback Permission or relevance may need attention Permission, frequency, recently added segments
Limited recipient interaction The available interaction signals are weak Whether mail is inboxed and ignored, or already filtered
Positive recipient feedback Some traffic shows favorable signals Compare this traffic against your weaker segments

Limited interaction needs further investigation. Some recipients may ignore inboxed mail; other messages may be filtered before recipients see them. Sending logs, campaign context and controlled inbox placement tests can help distinguish those possibilities, but a seed test is only a sample.

Step 4: Interpret spam rate carefully

Gmail’s reported spam rate counts complaints from mail that reached the inbox. That single detail changes how you read it.

A rate of 0.00% is not proof of healthy placement. Google lists automatic spam filtering as one possible reason for low or suddenly zero user-reported spam: fewer messages reach inboxes where recipients can report them. Investigate the change alongside delivery and engagement data; do not assume zero complaints proves filtering either.

Compare trends across several days and check significant daily changes. Low volume can hide data, while a sudden complaint spike still warrants investigation.

Step 5: Use your own event data as the primary evidence

Your sending platform sees things Gmail’s dashboard never will: the exact SMTP response text on a deferral, the hour a rejection pattern started, which template was sending at the time.

Pull these for Gmail recipients specifically and compare against a stable control period:

  • Accepted, deferred and rejected counts, with response codes
  • Bounce classification, split hard versus soft
  • Opens, clicks, replies and unsubscribes
  • Volume and send frequency per recipient
  • Performance broken out by campaign, segment, sending domain and IP

The point is not to stare at every chart until one confesses. You are looking for the moment the line bent and what else moved at the same time.

Postmark is the strongest platform in this category for diagnosis, mostly because of how much detail it keeps. Message streams separate transactional from broadcast traffic so a marketing problem cannot drag down password resets, full message content is retained for 45 days by default, and bounce data is classified rather than dumped as raw SMTP text. The Basic plan runs $15/month for 10,000 emails as of September 2026, and DMARC monitoring is a $14/month per-domain add-on through DMARC Digests.

The limitation is scope. Postmark bans cold outreach outright, enforces content policies more strictly than most competitors, and is not built to run a general marketing programme. It is a diagnostic instrument, not a marketing suite.

Postmark

Transactional email service for apps, owned by ActiveCampaign

4.3/5

Postmark, originally built by Wildbit and acquired by ActiveCampaign in 2022, is a transactional email service laser-focused on deliverability and speed. It consistently achieves...

Free plan · from $15/mo Verified Jul 14, 2026

Step 6: Add evidence beyond Google’s dashboards

A reputation grade is one view of sending performance. Whether you use legacy dashboards or v2, combine Google’s reports with other evidence rather than treating a grade as an inbox-placement measurement.

Inbox placement testing. Seed lists tell you where controlled messages land at each provider. They are a sample, not a census, and seed accounts do not behave like real recipients, so treat a clean seed result as weak evidence rather than proof.

Blocklist monitoring. Useful for catching a listing quickly. A listing on a minor blocklist often has no measurable effect on Gmail placement, so confirm impact in your own data before you panic.

DMARC aggregate reports. These show every source sending as your domain and whether it authenticates. They explain authentication and infrastructure, not whether anyone wants the mail.

Mailgun packages inbox placement and reputation monitoring into Optimize, sold separately from its Send plans, a detail worth knowing before you budget. Send pricing runs from a free tier at 100 emails/day up to $90/month for 100,000 emails on Scale, with dedicated IP pools and send-time optimisation appearing at that level. The catch is that the deliverability tooling most people associate with the brand is not in those numbers. Additional dedicated IPs are $59 per IP per month on top.

Mailgun

Transactional email API for developers, owned by Sinch

4.1/5

Mailgun is a Sinch-owned transactional email API platform founded in 2010, designed for developers who need reliable, high-volume email delivery via REST API or SMTP. It offers...

Free plan · from $15/mo Verified Nov 18, 2026
Feature Mailgun Postmark
Rating 4.1/5 4.3/5
Starting Price $15/mo $15/mo
Free Plan 100 emails/day, 1 custom sending domain, tracking and analytics 100 emails/month, never expires, test integration and side projects
Founded 2010 2009
Email Templates 25 20
Integrations 40 30
Independent Inbox Test No independent test 98.7%
Marketing Automation No No
A/B Testing No No
Landing Pages No No
Segmentation No No
Drag & Drop Editor No No
SMS Marketing No No
Ecommerce Features No No
API Access Yes Yes
Multi-Language No No
Web Push Notifications No No
Live Chat No No
Advanced Analytics Yes Yes

See full Mailgun vs Postmark comparison

If you are choosing a platform primarily on inbox performance, our best deliverability tools comparison ranks the field, the Mailgun vs Postmark breakdown weighs the two head to head, and the Postmark pricing page covers what the volume tiers actually cost as you grow.

Step 7: Change one variable, then wait

Once you have a hypothesis, test it properly. Change one meaningful thing. Hold a comparable cohort steady. Allow time for dashboard updates: Google says compliance changes can take up to seven days to appear. Monitor SMTP errors and complaints during that period so you can respond if sending gets worse.

Common single-variable changes worth trying, roughly in order of how often they work:

  1. Suppress the audience segment added immediately before the decline
  2. Cut send frequency to Gmail addresses by half
  3. Move one stream to a separate authenticated subdomain
  4. Reduce volume to the level of your last stable month and hold it there
  5. Run a confirmed re-opt-in to your dormant segment, then suppress non-responders

Keep a rollback plan for each. If you change four things at once and placement recovers, you have learned nothing you can reuse.

Common mistakes

Relying on a single score. A reputation grade can become a shortcut for understanding delivery. Every candidate (seed test scores, third-party reputation grades, blocklist counts) measures a fragment. Combining them into a hypothesis works. Treating any one as the new mood ring does not.

Blaming Gmail first. Mailbox providers do ship bugs and adjust thresholds. But external explanations should come after you check your own changes. If the decline is limited to Gmail, started on a specific date, and no other sender you know reported the same thing, look at what you did.

Suppressing everyone who looks inactive. “No engagement” from Gmail can mean the mail is already in spam. Mass-suppressing those addresses removes the evidence and the audience at the same time. Investigate placement before you sunset a segment.

Routing around an unsubscribe with a second domain. Recipients do not see your infrastructure diagram. They told your brand to stop. Stream separation protects important mail from problems elsewhere; it is not a way to keep mailing someone who said no.

Manufacturing volume for the dashboard. If Gmail reports insufficient data, sending more to trigger a verdict is exactly the behaviour that creates the problem you are trying to diagnose.

What success looks like

Keep a dated record of the affected traffic, your hypothesis, the change you made and the result. That makes the next investigation easier.

Review applicable compliance checks, reported spam and SMTP acceptance trends together. Aim for Google’s recommended spam rate below 0.10% and avoid reaching 0.30%. Compare acceptance and engagement against a stable period for your own traffic. Choose an acceptance target that fits your traffic and remember that SMTP acceptance does not prove inbox placement.

Use observed changes to test your explanation. A compliant status, low complaint rate or clean seed test alone cannot establish that the campaign reaches every subscriber’s inbox.

Best for Deliverability Diagnosis

Postmark

Transactional email service for apps, owned by ActiveCampaign

4.3/5

Free plan · from $15/mo

Sources

  1. Postmaster Tools deprecation notice — Google — accessed 2026-10-10
  2. Postmaster Tools dashboards — Google — accessed 2026-10-10
  3. Email sender guidelines — Google — accessed 2026-10-10
  4. Set up Postmaster Tools — Google — accessed 2026-10-10
  5. Gmail Reputation Data Is Dead. Now What? — Mailgun — accessed 2026-09-01
  6. Gmail Feedback Loop — Google Support — accessed 2026-10-10
  7. Postmark Pricing — Official — accessed 2026-09-01
  8. Mailgun Pricing — Official — accessed 2026-09-01

For retirement timing, follow Google’s deprecation notice. Mailgun’s linked commentary provides vendor context, but it does not override Google’s current statement that legacy web retirement is postponed.

Share this article

Related Articles