The Domain and IP Reputation dashboards are being removed from Postmaster Tools, and Google has said plainly why: the data was slow, hard to act on, and able to mislead. Whatever replaces that number in your reporting has to be one you own.
The Domain and IP Reputation dashboards in Postmaster Tools are being retired. What makes the change worth reading closely is not the removal — it is the explanation attached to it. In its own deprecation FAQ, Google states the reason the dashboard is being replaced: reputation data is not easily actionable for most senders, changes in sender behaviour are slow to surface in it, and the view can mislead, because reputation is only one of several factors that decide whether a message reaches an inbox.
That is an unusually honest piece of documentation. The dashboard senders have been screenshotting into monthly reviews for years was, by the admission of the party that built it, a lagging proxy for something the sender can measure directly.
Google postponed deprecating the legacy Postmaster Tools interface after sender feedback, so the old interface is still standing for now — but the direction is unchanged, and v1 will eventually be retired. The practical pieces:
If your team has a script that pulls reputation and posts it into a channel, that script has a shelf life. It also has a replacement path, which is the more interesting question.
The current dashboard can be misleading as reputation is only one of many factors affecting deliverability.
Google, Postmaster Tools deprecation FAQRead the three complaints as a specification, because they generalise to almost every deliverability metric teams keep on a wall: it does not tell you what to do, it moves too slowly to be useful as feedback, and it is one input presented as a verdict.
A reputation label is a summary of many signals — complaint rates, engagement, authentication, bounce handling, volume patterns — collapsed into a single word. Summaries are comforting precisely because they hide the disagreement underneath. The sender in trouble usually knows it from the per-stream detail long before the dashboard agrees: one reactivation campaign dragging the whole domain, one stream mailing people who have not opened anything in a year, one form still collecting consent nobody can prove.
So the question the retirement forces is a good one. If the number that represents your deliverability is going away, what number are you going to put in its place — and can you defend it?
The replacement is not another vendor's reputation score. It is the set of first-party measurements you already have and mostly do not report:
None of this is glamorous, and none of it produces a single word that can be pasted into a slide. It produces something better: a number that moves within days of a change, so that when you make a change you can see whether it worked.
Find every place a reputation figure is reported — the weekly email, the dashboard tile, the spreadsheet someone updates on Mondays — and write down what decision it is supposed to inform. Then replace it with the per-stream measurement that decision actually needs. While you are in there, book the API migration: v1 endpoints are on a clock, and the schema change means someone has to touch code.
Written by the team at LMR — a senior lifecycle marketing studio working in Iterable, Braze, Klaviyo and the tools you already run.
Start a project ↗