Google rolled out Postmaster Tools v2 yesterday afternoon. The new dashboard adds a “Compliance” section that maps directly to the February bulk sender requirements. The other tabs (IP Reputation, Domain Reputation, Spam Rate, Feedback Loop, Authentication, Encryption, Delivery Errors) remain but with updated data layouts.

We logged in this morning to review the new view across our customer base. The data is more readable than v1 and the compliance section finally gives senders a clear answer to “am I meeting Google’s requirements?” without having to interpret indirect signals from spam rate and authentication tabs separately.

This post walks through what the v2 dashboard actually shows, how to read each section, and what to do based on what you see there.

The compliance section is new and operationally critical

The Compliance tab did not exist in v1. It shows three states for each compliance requirement, plus a summary status at the top.

The requirements as Google now displays them: SPF authentication, DKIM authentication, DMARC authentication, valid PTR records (forward-confirmed reverse DNS), Transport Layer Security (TLS), low spam rate, sending domain alignment, and one-click unsubscribe for bulk senders.

Each requirement shows one of three states. “Passing” means the requirement is met across the sender’s traffic. “Issues detected” means some portion of traffic does not meet the requirement and Google has identified the issue. “Not enforced” means the requirement does not apply to this sender (typically for smaller senders below the 5K daily threshold).

The summary at the top consolidates the individual requirement statuses. Senders with all required items “passing” see a green overall status. Senders with any “issues detected” see yellow or red depending on severity.

The actionable value: senders no longer have to interpret across tabs to determine compliance. The single Compliance view answers the binary question directly.

What we are seeing across customer accounts

Across roughly 240 sending domains in our customer base, the compliance breakdown:

About 65% show “all passing” or equivalent. These are the senders who completed authentication remediation before February and have stable sending patterns.

About 25% show issues on one or two requirements. The most common issues: DMARC alignment failures (the sender publishes DMARC but some legitimate mail does not align), TLS not consistently used (some receiver paths drop TLS for various reasons), and one-click unsubscribe header missing for subset of sending (typically a forgotten template or a custom email path).

About 10% show issues across multiple requirements. These are typically senders we have not been working with directly or senders who tried to navigate the requirements without expertise and made mistakes. The remediation for these accounts is significant work; each requirement may take days or weeks to fix.

The breakdown is consistent with what we expected given the February enforcement experience. Senders who did the work see clean compliance status. Senders who did not are getting clear signals about what to fix.

Reading the IP Reputation tab in v2

The IP Reputation tab changed less dramatically than the new Compliance tab but has some refinements.

The four reputation categories remain: High, Medium, Low, Bad. The data shows the percentage of mail volume falling into each category over time, per IP address.

The v2 refinements: time-series resolution is improved (daily granularity rather than the weekly aggregation in v1), the chart legends are clearer, and the historical data goes back further (up to 6 months rather than 30 days).

For senders with multiple IPs, the per-IP breakdown is useful for identifying which specific IPs are dragging overall reputation. We commonly see customer setups where 4 of 5 IPs are “High” reputation and 1 IP is “Medium” or “Low.” The single underperforming IP affects the overall sender perception even though most IPs are healthy.

The IP-level visibility is particularly useful for IP warmup scenarios. New IPs progress from “no data” through “Low” or “Medium” before reaching “High” reputation if the warmup is operated correctly. The v2 dashboard makes the progression more visible.

For senders whose mail goes through ESP shared IPs (SendGrid, Mailgun shared pools), the IP reputation tab shows the shared pool reputation rather than per-customer reputation. The Postmaster Tools view is less directly useful for shared-pool senders than for dedicated-IP senders.

Domain Reputation has clearer presentation

The Domain Reputation tab is similar to IP Reputation but applies to the sending domain rather than IP. The same four categories. Same time-series visualization.

The v2 change here: domain reputation now shows per-subdomain breakdown for senders with multiple subdomains under the same root domain. Previously the dashboard aggregated, which obscured situations where (for example) marketing.example.com had problems but mail.example.com was healthy.

For senders using subdomain separation (which we recommend for sender diversity), the per-subdomain view is operationally useful. You can identify which specific subdomain is producing reputation issues and remediate at the appropriate level.

Spam Rate is the metric Google is enforcing on

The Spam Rate tab has not changed structurally in v2 but takes on additional importance given the February enforcement.

The metric: percentage of delivered mail that recipients mark as spam, calculated daily. The 0.3% threshold is what Google enforces on for bulk senders. Above 0.3% triggers reputation degradation. Above 0.5% can produce throttling and rejection.

The v2 dashboard adds a clear “your spam rate vs threshold” visualization. The historical chart shows your rate over time with a clear line at 0.3% so you can see whether you have ever crossed the threshold and how persistently.

What we are seeing in customer data: most senders are operating well below 0.3%. The senders crossing the threshold are typically cold email operators or B2C senders with aggressive list acquisition. The threshold crossings are not subtle in the data; they appear as obvious spikes when they happen.

The actionable insight from spam rate monitoring: spikes above 0.3% should trigger immediate investigation. A single day above threshold is not catastrophic. Multiple consecutive days above threshold produces reputation damage. Persistent operation above threshold produces throttling and eventual rejection.

Authentication tab now matches Compliance reality

The Authentication tab previously showed pass/fail percentages for SPF, DKIM, and DMARC separately. The v2 refinement: clearer presentation of partial failures and alignment issues that Compliance tab references.

The data shows the percentage of mail that passes each authentication mechanism over time. The visualization makes it easy to see whether failures are concentrated on specific dates (which usually indicates a configuration change that broke things) or persistent (which usually indicates a fundamental authentication issue).

For DMARC specifically, the tab now shows alignment vs raw pass/fail. Mail that passes SPF or DKIM but fails DMARC alignment is now visible as a distinct category. This is the data many senders need to address the partial-compliance issues that the Compliance tab flags.

Feedback Loop tab shows complaint patterns

The FBL tab shows which specific mail (by domain, IP, or content type) is producing user complaints. The granularity is helpful for identifying problem segments within otherwise-healthy operations.

We commonly see customers whose overall spam rate is healthy but a specific subset of mail (one specific campaign, one specific sender domain, one specific time of day) produces disproportionate complaints. The FBL tab makes this visible.

The v2 refinement: filtering options to view by IP, domain, and campaign. Previously the data was aggregated and required spreadsheet export to slice by these dimensions.

TLS Reporting (Encryption tab) reflects real network conditions

The Encryption tab shows percentage of mail delivered over TLS. The target should be approaching 100% for modern infrastructure.

What we see: most senders are at 99%+ TLS for outbound traffic to Gmail. The 1-2% that lacks TLS is typically from specific receiver-side issues (older systems, fallback paths, certain network conditions) rather than sender-side configuration.

The compliance requirement: bulk senders need TLS for outbound. The Compliance tab references TLS as a check item. Senders with TLS rates below 99% should investigate. Senders below 95% have a configuration issue that needs immediate attention.

The Encryption tab in v2 shows TLS handshake errors with specific reason codes when known. This is useful for diagnosing the specific cases where TLS failed.

Delivery Errors gives the SMTP-level view

The Delivery Errors tab maps the actual SMTP errors Gmail returned for the sender’s mail. The categories: 421 temporary failures, 550 permanent rejections, and various sub-categories.

This is where the actual enforcement decisions appear most clearly. A customer with deliverability questions can compare their internal sending logs against the Delivery Errors tab to confirm which mail Gmail is rejecting and why.

The v2 refinement: error category breakdown with explanations. Previously the dashboard showed error codes without much context. Now each error code has a brief explanation of what triggers it and what to investigate.

For the 550 5.7.26 (authentication failure) errors, the explanation now points to which authentication mechanism (SPF, DKIM, DMARC) failed. For 550 5.7.1 (policy block) errors, the explanation indicates whether it is DMARC policy, content policy, or reputation policy. For 421 (throttling) errors, the explanation indicates the throttling reason (complaint rate, sending rate, reputation).

The error context makes triage faster. Senders troubleshooting deliverability issues can identify the specific cause from the dashboard rather than guessing or searching documentation.

The dashboard limitations we still see

V2 is an improvement but not complete. Several limitations remain.

The data lag is still significant. Updates to the dashboard happen on a 24-48 hour delay from actual events. A sender who launched a problematic campaign on Monday will not see the data impact until Wednesday at earliest. Real-time monitoring requires SMTP-level log analysis at the sender side, not dashboard reliance.

The data granularity does not go below domain/IP level. Per-campaign or per-list analysis requires the sender to correlate dashboard data with their own sending logs. The dashboard alone cannot answer “which specific campaign caused the spam rate spike.”

The dashboard only shows Gmail-side data. Comparable visibility into Microsoft, Yahoo, and other receivers requires separate tools (SNDS for Microsoft, similar for others). Senders managing cross-receiver deliverability still need multiple data sources.

The historical depth is still limited. The 6-month window in v2 is better than v1’s 30 days, but year-over-year analysis requires saving exports periodically.

The action recommendations are vague. The Compliance tab tells you what is wrong but does not give specific remediation steps for your sending pattern. Senders need to interpret the issue and figure out the fix themselves.

Given the v2 release, we are updating our customer-facing recommendations.

Check the Compliance tab weekly at minimum. The summary status answers “am I meeting Google’s requirements?” in seconds. Any non-passing status warrants investigation that week, not next month.

Use the per-IP and per-subdomain breakdowns to identify problem segments. Aggregate views obscure issues that targeted views reveal.

Monitor the Spam Rate tab for trend changes, not just absolute values. A rising trend below 0.3% can become a problem above 0.3% in a few weeks. Catching the trend early prevents the threshold crossing.

Cross-reference the Delivery Errors tab with your sending logs. The error data from Google plus your own log data tells the complete story of what is happening to your mail.

Save monthly exports of dashboard data. The 6-month window is limited; long-term trend analysis requires preservation.

Train marketing and engineering teams to read the dashboard. Email deliverability is no longer purely an engineering concern; marketing teams making campaign decisions need visibility into what those decisions are doing to reputation.

The compliance enforcement is real

The Compliance tab existing is operationally important. Senders can no longer claim ignorance about whether they meet Google’s requirements. The dashboard answers the question directly. The answer is in the sender’s account whenever they choose to look.

Google’s enforcement has been measured but consistent. Senders who are not meeting requirements see degradation that compounds over time. Senders who are meeting requirements see stable or improving deliverability.

The trajectory is clear: requirements will continue to tighten, additional checks will be added, the gap between compliant and non-compliant senders will widen. The work to comply now is cheaper than the work to remediate after deliverability has degraded significantly.

For senders reading this in March 2024: check the Compliance tab today. Address any non-passing status this month. The senders who treat this as ongoing operational practice will be the ones whose deliverability remains stable as Google continues to evolve enforcement.

The dashboard is the visibility into the enforcement. The enforcement is the consequence of the rules. The rules continue to evolve. Senders who treat all three as connected, ongoing operational concerns will be the ones who continue to reach inbox at scale.