Add the domain that authenticates your mail, verify ownership, then interpret the dashboard against the messages you actually send to personal Gmail accounts. For a cold email operation with several sending domains, that first choice matters more than the verification click. A blank dashboard can mean low Gmail volume, an unverified domain, or a mismatch between the domain you added and the one in the message's authentication headers. It does not mean your mail reached the inbox.
This guide follows Google's current Postmaster Tools setup, dashboard definitions, and sender guidelines, checked October 22, 2026. The workflow is documentation-based; we have not verified a private sending account for this article.
Decide whether Postmaster Tools covers your recipients
Postmaster Tools reports on mail sent to personal Gmail accounts, ending in @gmail.com or @googlemail.com. It does not report your whole campaign, nor does it measure delivery to business mailboxes hosted on Google Workspace or Microsoft 365. If a campaign mainly targets work addresses, Postmaster Tools may give you very little data even when campaign sends and replies are visible elsewhere. Google also withholds some data when a day's Gmail volume is low to protect recipients' privacy. It publishes no universal minimum message count in the setup instructions; don't plan around an unsourced threshold.
Use it alongside the evidence you already control: message bounces, sending-provider logs, reply and opt-out handling, and a controlled received message whose full headers you can inspect. None of those substitutes for Gmail's own reputation or user-reported spam data. Conversely, a green Postmaster status does not certify inbox placement for each message.
Step 1: Identify the authentication domain from a delivered message
Before adding a domain, send a controlled message from the exact mailbox or service you intend to monitor to a personal Gmail account you control. In Gmail, open the message's Show original view. Record four values:
| Header or result | What to read | Why it matters |
|---|---|---|
From: |
The address the recipient sees | This is the domain DMARC evaluates for alignment. |
DKIM-Signature: d= or dkim=pass header.d= |
The domain that signed the message | Google says you can add this domain to Postmaster Tools. |
Return-Path: or spf=pass smtp.mailfrom= |
The SPF envelope-sender domain | Google also lets you add this domain. It may differ from From:. |
dmarc=pass or dmarc=fail |
The receiver's DMARC result | A pass needs SPF or DKIM authentication aligned with From:. |
Google's setup instructions say to add either the DKIM d= domain or the SPF Return-Path domain. If the two are the same, Postmaster Tools uses messages signed by SPF, DKIM, or both for dashboard data. Do not add only the visible From: domain by assumption when the actual signer and Return-Path belong to another domain. First check your sending provider's documented custom authentication setup. If your domain authentication is failing, fix that before interpreting reputation data; our Google Workspace DKIM troubleshooting guide covers that narrower issue.
Worked example: three names in one campaign
Suppose a controlled message shows From: Sam <sam@try-acme.example>, dkim=pass header.d=try-acme.example, and spf=pass smtp.mailfrom=bounces.try-acme.example. The .example names are illustrative, not a configuration to publish. Add try-acme.example to see data associated with its DKIM signer. If you need to inspect the bounce subdomain separately, add bounces.try-acme.example too. Google's setup page says subdomains can have independent dashboards when separately added; once the primary domain is verified, its subdomains need not be verified again. The Compliance status dashboard is an exception: Google says it reports at the primary-domain level even when a subdomain is selected.
Now suppose the message instead shows dkim=pass header.d=mail.vendor.example and smtp.mailfrom=mail.vendor.example while the visible From stays try-acme.example. Adding only try-acme.example cannot make those authenticated messages appear under that domain. Check the vendor's options for signing and Return-Path with a domain you control, and recheck the delivered headers. Do not assume a DNS TXT record by itself changes the message your provider sends.
Step 2: Add and verify the domain
- Sign in to Postmaster Tools with a Google or Google Workspace account. Open Manage Domains, choose Add new domain, enter the chosen authentication domain, and select Create.
- From that domain's menu, select Verify domain. Copy the TXT or CNAME record that Postmaster Tools gives this account into your DNS provider. The record's name and value are account-specific; don't copy a value from another person's tutorial.
- Return to the verification window and select Verify. Google's help says the status usually updates right away but can take up to ten minutes. If verification fails, check the exact DNS host and value, wait for the record to resolve, then retry with the new string Google provides if needed.
- Confirm the domain shows verified before relying on its dashboards. Google allows you to postpone verification, but says no email information appears until you complete it.
For an agency, keep ownership of the DNS and access list explicit. Google's setup guide says you can add other Google-account users to a verified domain through Manage users; the invite does not automatically notify them. Use separate verification records if different Google accounts each need to establish ownership. If the sender is a separate registered domain rather than a subdomain, add and verify that domain on its own. Do not conflate try-acme.example with acme.example.
Step 3: Read the dashboards without inventing a diagnosis
Select the verified domain, a dashboard, and a 7, 30, 60, 90, or 120-day range. Google says Postmaster Tools dates use UTC and typically update within 24 hours, sometimes longer. A change to DNS or sending practice will not appear immediately; the Compliance status display can take up to seven days to reflect a fix.
| Dashboard | What it tells you | What it cannot establish |
|---|---|---|
| Compliance status | Whether Google currently sees specific sender requirements met for the primary domain; some rows apply only to bulk senders. | That every subdomain or individual message will reach the inbox. |
| Spam rate | The share of relevant Gmail messages that recipients manually marked as spam. | How many messages Gmail automatically filtered to spam. Google says a very low or zero reported rate can coexist with poor reputation. |
| Authentication | The share of observed mail passing SPF, DKIM, and DMARC checks. | Which particular DNS or provider setting caused a failure; inspect a message's headers. |
| Domain/IP reputation | Google's rating for the observed authenticated domain or sending IP. | A transferable rating for other domains or providers. Google limits domain reputation to the exact authentication domain. |
| Delivery errors | The share of authenticated messages rejected or temporarily failed by Gmail. | Failures at unrelated mailbox providers or a campaign-wide bounce rate. |
Google's sender guidelines call for SPF or DKIM from all senders, plus both and DMARC for senders above its bulk threshold; they also cover DNS, TLS, message format, spam rate, and unsubscribe rules for applicable messages. Do not use one Postmaster number as a shortcut around the full policy. A cold outreach message's applicable requirements depend on the message and sending pattern, not a label you give the campaign.
Troubleshoot an empty or surprising dashboard
The domain is unverified. Check the verification state on Manage Domains and query the exact TXT or CNAME name that Google gave you. A DNS record for Workspace ownership is not automatically the Postmaster record for this Google account.
You have little mail to personal Gmail. Compare the selected UTC dates with actual sends to @gmail.com and @googlemail.com. Google says privacy protection can remove data on low-volume days. An empty panel cannot be converted into a zero spam rate or a good reputation grade.
You added the wrong domain. Reopen a recent delivered message and compare DKIM d= and SPF smtp.mailfrom with the domain selected in Postmaster Tools. If you changed providers or added sending subdomains, repeat the check per sending path. The root and a separately registered outreach domain are not interchangeable.
Compliance says “No data found.” Google's dashboard guide says this state can reflect insufficient qualifying received mail. It evaluates configuration from messages Google received, not merely what your DNS says today. Verify the current DNS with Google's Admin Toolbox and inspect a new message, then let the dashboard update.
Spam rate looks perfect but results are poor. The panel shows user reports, not all automatic filtering. Google explicitly warns that a low or zero reported rate can occur when Gmail is already sending many messages to spam. Check reputation and delivery errors together, then review targeting, consent, complaint handling, authentication, and message quality. There is no safe sending-volume trick that turns a blank dashboard into proof of placement.
If a technical check finds an SPF permerror, follow our SPF lookup-limit guide. If your DKIM or Return-Path domain differs from the visible From domain, check DMARC alignment on a sending subdomain. For a portfolio of domains needing aggregate DMARC reporting, our monitoring tools comparison covers that separate job. Postmaster Tools measures a slice of Gmail traffic; it is one input to an operating review, not a substitute for the underlying message evidence.
