Your sending platform records its own delivery attempts. Google's dashboards add receiver-side evidence about messages sent to personal Gmail accounts.
What does Postmaster Tools measure?
Postmaster Tools reports data about mail your domain sends to personal Gmail accounts.
Google's dashboard guide includes complaints, authentication, encryption and delivery errors. These figures do not describe your mail to other providers or Google Workspace recipients.
You verify a domain before selecting its dashboards. Some reports include only DKIM-authenticated mail, so the population can differ from your sending logs.
Google attempts to exclude forwarded messages. Some can still appear in its reports. Label comparisons with your sending logs to show that Google's figures may include forwarded traffic.
What do the main dashboards tell you?
Each dashboard measures a distinct requirement or outcome.
| Dashboard | What it helps you investigate |
|---|---|
| Compliance status | Requirements that your domain meets or needs to repair |
| Spam rate | Recipient spam reports on qualifying inbox deliveries |
| Feedback loop | Complaint patterns grouped by campaign identifiers |
| Authentication | Rates of passing SPF, DKIM and DMARC checks |
| Encryption | Whether mail used an encrypted connection |
| Delivery errors | Authenticated messages rejected or temporarily failed |
A delivery error describes acceptance failure. It does not identify the folder used for an accepted message. A complaint report also differs from automatic spam placement.
Spam complaint rates explains the inbox-based denominator and the risk of misleadingly low results.
What do the compliance statuses mean?
Each status describes whether Google can verify that your mail meets a particular requirement.
| Status | Meaning |
|---|---|
| Compliant | The requirement is met |
| Needs work | Your system or messages need a change to meet the requirement |
| No data found | Google lacks enough qualifying evidence to assess the requirement |
For a Needs work item, use its reported action to repair that requirement. A DNS repair and an unsubscribe-processing repair affect different systems.
Configuration-based results describe settings observed when qualifying messages arrived. A corrected DNS record therefore need not change the displayed result immediately.
The Gmail and Yahoo requirements guide explains the authentication, complaint and unsubscribe obligations.
Why can the dashboards disagree?
The reports can use different message populations, domain boundaries and observation windows.
Compliance status combines primary-domain and subdomain traffic into a primary-domain result. For example, mail from news.example.com contributes to compliance for example.com.
Other dashboards can report a selected subdomain separately. Compare their domain scope before treating different values as a reporting failure.
Compliance uses a rolling average across multiple days. Google also says its datasets differ slightly across dashboards, so their values need not match exactly.
Why is data missing or slow to change?
Low volume, qualifying-message criteria and delayed updates can prevent a dashboard from showing a complete result.
Google withholds some data at low volume to protect recipient privacy. An empty graph does not establish zero complaints or perfect authentication.
Data typically updates within 24 hours. Some updates take longer. A configuration change made this morning may therefore be absent from an afternoon report.
Google advises rechecking compliance after seven days because the rolling result takes time to reflect changes. Keep the repair time and affected requirement with your investigation so you can compare the relevant periods.
How should you use reputation reports or API integrations?
Treat reputation as supporting evidence and check Google's documented fields before depending on a report in automation.
Where available, Google's Domain Reputation and IP Reputation dashboards assess a sender's traffic. A favorable rating does not guarantee inbox placement. It does not cancel a failing compliance requirement.
Google's interface and API notice covers their retirement. It also directs integration migrations. Use that notice and the linked API schema when choosing metrics, because a dashboard's existence does not guarantee API availability.
Do not substitute a missing reputation field with a zero score. That would convert unavailable evidence into an apparent negative result.
How do you compare Gmail with other providers?
You combine Google's reports with delivery events and mailbox measurements covering your other recipients.
With Bird, use Inbox Insights to inspect measured placement by provider. Seed accounts are test mailboxes whose received folders can be inspected.
A provider without measured placements has no placement result. Keep that gap visible instead of treating Google's data as a substitute.
Delivery and deliverability explains which results establish server acceptance and which establish sampled inbox placement.
In short
The reports cover personal Gmail accounts.
They do not measure delivery to Yahoo, Outlook or your full recipient population.
Compliance reports name requirements.
Compliant, Needs work and No data found describe different outcomes for each requirement.
Missing data is not a zero.
Low volume and measurement criteria can leave a dashboard without reportable data.
Changes need time to appear.
Dashboard updates and rolling compliance averages can lag behind a configuration repair.