Gmail Postmaster Tools and Yahoo Sender Hub: What to Track

Gmail Postmaster Tools and Yahoo Sender Hub are the two consoles that tell you what Gmail and Yahoo think of your sending. Verify every sending domain in both, track spam rate and domain reputation on the Google side, spam rate and the Complaint Feedback Loop on the Yahoo side, and read each metric in the console it came from: the two providers use the same metric name but do not measure complaints against the same set of messages.

When a DTC brand calls us because "the emails aren't landing any more", the first question we ask is not about content or frequency. It is: "do you have access to Postmaster Tools and Sender Hub?" The answer is rarely yes, or else an account was created two years ago by an agency that has since moved on.

Without those two consoles, you are flying blind. Klaviyo or Brevo give you open rate and complaint rate as your ESP measures them. Gmail and Yahoo tell you what they think of you. Those are two different measurements, and only the second one decides inbox placement.

This article covers setup for both tools, how to read the metrics correctly, and above all the interpretation traps we see every month in audits.

What each console actually covers

Before you connect anything, understand the scope. The two tools do not measure the same thing and they are not symmetrical.

Gmail Postmaster Tools only covers sending to @gmail.com and @googlemail.com addresses, according to Google's documentation. Professional Google Workspace mailboxes hosted at Google are not included. If your list is mostly B2B on company domains running Workspace, Postmaster Tools will show you only a fraction of your Google traffic.

Yahoo Sender Hub bundles several pieces: Sender Hub Insights, which displays aggregated deliverability statistics at domain level, the Complaint Feedback Loop, and more advanced data feeds reserved for senders who request access.

The difference in philosophy is stark. Google opens eight self-service dashboards as soon as the domain is verified. Yahoo keeps part of its data behind an explicit access request.

Setting up Gmail Postmaster Tools in practice

Verify the right domain

The most frequent mistake we correct: the brand verified its website domain instead of its sending domain. What matters is the domain that appears in the From field and, above all, in the d= domain of the DKIM signature.

If you send from news.brand.com with DKIM signed on brand.com, verify both. Postmaster splits data by domain, and two subdomains entered badly give you two half-empty dashboards.

Verification goes through a TXT or CNAME record in your DNS zone, following the procedure Google describes. The status only flips once the record has propagated, which depends on your DNS host rather than on the console. If the domain is still unverified several hours after you added the record, re-read the value published in the zone before you suspect Postmaster Tools.

For the SPF, DKIM and DMARC groundwork, our DNS setup guide covers which records to publish and in what order.

The eight dashboards, and the ones that matter

Postmaster Tools exposes eight dashboards: Compliance status, Spam rate, IP Reputation, Domain Reputation, Feedback loop, Authentication, Encryption and Delivery errors.

In our weekly agency reviews, we look at three of them first:

• Spam rate: the most direct signal on your relationship with recipients
• Domain Reputation: the long-term aggregate, slow to degrade and slow to recover
• Delivery errors: the first place a misconfiguration or a dirty list shows up

IP Reputation only means something if you are on a dedicated IP. On a shared IP at an ESP, the indicator reflects the behaviour of every sender sharing that address, not just yours. Plenty of DTC brands read that screen as a verdict on their own programme when it is nothing of the sort: on shared IPs, fix what you control, domain reputation and spam rate.

The reading windows

Dashboards can be viewed over the last 7, 30, 60, 90 or 120 days. As routine, we work in 30 days for the trend and 7 days to check the effect of a specific campaign.

The 120-day view serves one purpose: measuring whether a remediation really held over time after a reputation incident.

Three ways people misread Postmaster Tools

Spam rate does not measure what you think it does

This is confusion number one. The spam rate Postmaster Tools shows does not count messages the Gmail filter classified as spam. Google defines it as the percentage of your messages delivered to the inbox of engaged recipients and then marked as spam by those recipients.

A message filtered automatically before it reaches the inbox does not enter that calculation. You can have a flattering spam rate and a real placement problem: the messages causing trouble did not reach anyone in a position to hit "report spam".

Google does not publish the detail of what counts as an "engaged" recipient, nor the exact denominator used. Read this metric as a voluntary complaint signal, not as an overall spam rate.

The two thresholds are not the same threshold

Google gives two distinct benchmarks: stay below 0.10% spam rate in normal operation, and avoid reaching 0.30%.

Those two numbers do not read the same way. 0.10% is the cruising target. 0.30% is the red line, the one you must not even brush against occasionally, including on a Black Friday send peak.

In practice, we set an internal alert well before that. As soon as an account goes above 0.08% on a single day, we open the subject: which campaign, which segment, which collection source. Waiting for 0.10% to react means reacting after the degradation has started.

An empty dashboard is not a green dashboard

Google notes that on low-volume days, dashboards may not include all data in order to protect the privacy of Gmail users. A brand sending two campaigns a month will therefore see a lot of gaps.

The exact minimum volume that triggers display is not published by Google. Do not guess it and do not rely on figures circulating in the industry: the official documentation only says data may be missing when volume is low.

Add to that the fact that data is typically updated within 24 hours, sometimes longer. Opening Postmaster Tools two hours after a send tells you nothing.

Gmail bulk sender status: a permanent decision

Google defines a bulk sender as any sender who sends close to 5,000 messages or more to personal Gmail accounts within a 24-hour period. Two details matter enormously.

First, counting happens at primary domain level. Google states that all messages sent from the same primary domain are counted together. Splitting marketing and transactional across two subdomains does not divide the 5,000 counter.

Second, the status is permanent. Google writes that bulk sender status has no expiry date and that senders classified as such remain so permanently. Cutting your volume after Black Friday does not move you back into the small-sender category.

The operational consequence is simple: if your Gmail list pushes you over that threshold even one day in the year, you have to meet the bulk sender requirements all year. Our article on the Google and Yahoo sender requirements for 2026 covers the full specification.

The Gmail Feedback Loop: the only way to know which campaign draws complaints

Spam rate tells you things are degrading. The Feedback Loop tells you where.

The mechanism relies on a Feedback-ID header you add to your sends. Google describes the a:b:c:SenderId format, with up to three optional identifiers you choose and one mandatory sender identifier. That last one has to stay stable over time, otherwise you lose the history of your reports. Google also constrains its form: the sender identifier runs 5 to 15 characters, and Google recommends keeping it consistent across your mail stream.

The split we recommend at the agency: reserve one identifier for the nature of the send (campaign or flow), one for the family (welcome, abandonment, promo), one for the targeted segment. That gives you a complaint table pointing straight at the faulty component.

Watch the generation condition. Google specifies that FBL reports are only generated if a given identifier appears in a certain volume of mail as well as in distinct spam reports over the day. That volume is not quantified in the documentation.

The practical translation: if you split your identifiers too finely, each bucket becomes too small to report. Start broad, then refine on the categories that cause problems.

Setting up Yahoo Sender Hub

The authentication requirements

Yahoo draws a distinction between two levels. All senders need at least SPF or DKIM. Bulk senders need SPF and DKIM, plus a valid DMARC policy of at least p=none, with DMARC passing.

On the best practices page we checked, Yahoo does not publish the number of messages per day that defines a bulk sender on their side. Do not transpose Gmail's 5,000: nothing in Yahoo's documentation validates that equivalence. The healthy reflex is to meet the bulk requirements on both sides as soon as you send at volume.

Yahoo's spam rate

Yahoo asks senders to stay below 0.3% spam rate, using exactly the same label as Google for that metric. On the same page, Yahoo specifies that spam rate is calculated in their system on the basis of messages delivered to the inbox, and advises you to take that into account when you use Complaint Feedback Loop data to recalculate the rate yourself.

Same name, same threshold, different denominator: one more reason not to put Gmail spam rate and Yahoo spam rate side by side in the same dashboard as if they were the same measurement. Google measures complaints against messages delivered to the inbox of engaged recipients, Yahoo against messages delivered to the inbox. The scope of the denominator is not the same. Track each metric in its own console, with its own history.

Unsubscribes and list-unsubscribe

Among its bulk sender requirements, Yahoo requires you to process unsubscribes within 2 days. On Klaviyo or Brevo, native unsubscribe is immediate. The risk sits elsewhere: in custom unsubscribe links pointing at a homemade page, or in syncs to a third-party CRM running as a weekly batch.

On list-unsubscribe, Yahoo's bulk sender requirements ask for a functional list-unsubscribe header supporting one-click unsubscribe for marketing messages and subscribed messages. The RFC 8058 POST method is presented there as strongly recommended, not as an obligation. The operational check is simple: send yourself a test, confirm the native unsubscribe link displays at the top of the message in a Yahoo mailbox, and that the click removes the address with no intermediate page.

On the substance of unsubscribes, the real lever is still reducing the number of people who want to leave: a sustainable frequency, segmentation, and a preference centre that offers a pause rather than a permanent exit.

Yahoo's Complaint Feedback Loop

Yahoo specifies that its Complaint Feedback Loop programme only supports DKIM-signed email and operates at domain level. Without DKIM correctly signed on the domain you register, you will receive nothing.

Complaints arrive in ARF format, Abuse Reporting Format, to let the sender remove the recipient from subsequent campaigns. That last point is the operational goal: the FBL stream only has value if suppression is automated in your ESP. An ARF file landing in a mailbox nobody reads is worth exactly nothing.

The Performance Feeds

Yahoo offers two richer data feeds, described on its Email Deliverability Performance Feeds page. The Placement Feed covers where messages land: inbox deliveries, spam folder placements, other folders, delivery errors and complaints. The Campaign Performance Feed covers aggregated behaviour towards campaigns: messages delivered, opens, reads, clicks and deletions. Yahoo specifies that both provide aggregated counts only and report no behaviour at the level of an identified user.

Access is not self-service: Yahoo points you to its sender teams, through the contact address given on that same page, to find out about the programme and its conditions.

Spam folder placement is precisely the information Postmaster Tools does not give you on the Gmail side: the volume actually classified as spam, and not only voluntary complaints. For a brand doing real volume on Yahoo, the access request is worth the trip.

The monitoring routine we run at the agency

A verified Postmaster account nobody opens produces no value. Here is the rhythm we hold on the accounts we operate.

D+1 matters: because the data is not real time, a check on the evening of the send shows nothing you can act on.

When an indicator slips, the diagnostic sequence does not change. We look first at what changed in collection (new popup, new giveaway, list import), then at the targeted segment, then and only then at the content. In the vast majority of audits, the cause is upstream: a signup source bringing in addresses that did not ask for anything. That is the underlying subject of our deliverability guide and of our list hygiene method.

If you are already in a degraded situation, with explicit error responses from receiving servers, the entry point is rather email blocklist removal.

What these tools will not tell you

Postmaster Tools and Sender Hub are reputation consoles, not placement tools. They do not show you which Gmail tab your emails land in, nor whether a specific segment is filtered.

They also do not cover Outlook, or the French ISPs Orange, Free and SFR, which carry serious weight on a French list. A spotless Gmail dashboard tells you nothing about those domains.

Finally, neither one gives a firm timeframe for a degraded reputation to recover. Google publishes no duration on the pages we checked. At the agency, we reason in clean volume sent rather than in days elapsed: what repairs a reputation is a run of sends to people who open and do not complain, not the passage of time.

If you want your full setup reviewed, authentication, collection, segmentation and reputation monitoring, that is exactly what our Klaviyo agency does on Shopify accounts, and what our Brevo agency does on Brevo stacks. Book a deliverability and CRM diagnostic if you want us to look at your sending domains with you.

FAQ

Should I verify the root domain or the sending subdomain in Postmaster Tools?

Both. Google splits data by verified domain. Verify the root domain and every subdomain you use in From or in the DKIM signature, otherwise you will get partial dashboards without understanding why.

My Postmaster dashboard is empty, is that a good sign?

No, it is a sign of missing data. Google states that dashboards may not include all data on low-volume days, in order to protect the privacy of Gmail users. The minimum volume required is not published: check the Google documentation rather than relying on estimates.

Can I compare Gmail spam rate and Yahoo spam rate directly?

No. Google measures complaints against messages delivered to the inbox of engaged recipients, while Yahoo says it calculates its rate on the basis of messages delivered to the inbox. The scope of the denominator differs: track each metric in its own console, with its own history.

If I reduce my volume, do I leave Gmail bulk sender status?

No. Google states that bulk sender status has no expiry date and that senders classified as such remain so permanently. Once the threshold is crossed, the requirements apply continuously.

How do I find out which campaign generates complaints at Gmail?

Through the Feedback Loop, by adding a structured Feedback-ID header to your sends. Be careful not to split too finely: Google only generates reports if an identifier appears in a certain volume of mail and in distinct spam reports over the day, a volume that is not quantified in the documentation.