Seed inbox and Postmaster monitoring across client-isolated domains
Agencies that glance at one blended deliverability chart are flying blind. Client A's sending domain can be melting while Client B still looks fine. Google Postmaster Tools and seed inbox tests measure different things. You want both, and you want them labeled by client domain inside isolated workspaces.
GTM already separates client identities, send windows, and compliance gates. Monitoring has to follow the same isolation.
What Postmaster tells you (and what it does not)
Google Postmaster Tools reports domain-scoped signals such as spam rate, reputation, authentication, and delivery errors once volume is high enough to populate data.
Important nuance from Google's own materials:
- Spam rate is driven by users marking messages as spam after delivery to the inbox, not by Gmail auto-filtering to Spam
- Sender guidelines tell bulk senders to keep spam rates low in Postmaster Tools
- Google recommends staying under 0.1%; rates at or above 0.3% carry a much sharper delivery penalty, and bulk senders may lose mitigations until they stay under 0.3% for seven consecutive days
Postmaster will not show true inbox placement across Outlook, Yahoo, and corporate gateways. It will not warn you early if volume is too low to chart.
What seed inboxes tell you
Seed tests place known addresses across providers and show whether a specific message landed in inbox, promotions, or spam at that moment.
Use seeds to:
- Spot placement cliffs after copy, link, or DNS changes
- Compare providers your ICP actually uses
- Validate a new sending domain before you scale cold volume
Do not treat a perfect seed run as proof that engaged-user complaint rates are healthy. Seeds do not complain like real prospects.
Per-client monitoring map
For each client workspace, maintain a row:
| Domain | Postmaster verified | Spam-rate alert | Spam-rate pause | Seed set | Last seed | Owner |
|---|---|---|---|---|---|---|
| tryclient.com | yes/no | 0.1% | 0.3% or rising fast | list id | date | name |
Rules of thumb that match Google's published guidance:
- Alert when spam rate trends toward or above ~0.1%
- Pause new cold volume if you hit ~0.3% or if rate spikes hard day over day
- Investigate authentication failures and delivery errors before you "just add inboxes"
Keep primary corporate domains out of cold outbound so a monitoring incident on a sending domain does not take down payroll mail.
Cadence that fits agency life
Daily (per active domain):
- Bounce rate and provider rejects inside the sending tool
- Complaint or feedback-loop signals when available
- Any Postmaster spam-rate point that moved sharply
- Inbox or OAuth locks
Weekly:
- Seed run on the templates you actually send (not a lab-only HTML blob)
- Reputation and authentication panels in Postmaster
- Confirm caps were not silently raised
- Compare positive reply and booked conversation trends so you do not misread a placement drop as "bad copy only"
At every DNS or platform change:
- Fresh seed test before ramp resumes
- SPF/DKIM/DMARC pass check
- Tracking domain review
Incident play when placement or spam rate breaks
- Pause cold sends for that client domain (not every client)
- Leave warm-up-only or stop entirely based on severity
- Check authentication, list quality, and recent copy/link changes
- Re-run seeds after the fix
- Resume with a reduced cap, not the old peak
Do not "push through the dip" to hit a weekly send commitment. That is how one client's domain becomes a case study in delisting.
Why isolation is the monitoring feature
If two clients share a domain pool, your Postmaster chart cannot tell you whose list caused the complaints. Client-isolated sending domains and workspaces make spam rate, seeds, and pause authority attributable.
That attribution is also what buyers ask for when they want an audit trail before trusting AI send.
Operator checklist
- Every sending domain enrolled in Postmaster with the right owner
- Alert and pause thresholds written per client
- Seed list covers Gmail plus the providers your ICP uses
- Monitoring dashboard filtered by workspace, not agency blended totals
- Pause authority named (AM cannot override deliverability lead without a note)
- Change management: DNS/copy/tooling changes trigger a seed retest
Where GTM fits
GTM helps agencies run find -> qualify -> write -> send/reply/book with client-isolated workspaces, email plus LinkedIn, and a compliance gate that stays on. Seed and Postmaster monitoring is how you keep those sending domains alive long enough for the motion to book conversations.
Get on the waitlist: trygtm.com/waitlist.