Skip to main content

Before customers say they never got it

Monitor Review Request Email Deliverability

Fixing a spam problem after customers complain is one job. Noticing the drift before they do is another, and it needs a routine rather than a rescue. Once your review requests leave from your own domain through your own provider, you can watch that domain the way mailbox providers do. Score your current routine below, then keep the checks that are missing on a calendar with an owner.

  • Score your monitoring in two minutes
  • Gmail’s published spam rate thresholds
  • Weekly and monthly checks with an owner

The problem, solved

Why deliverability slips without anyone noticing

  • We cannot see our own sending domain

    When requests leave from a shared address, there is no domain of yours for Gmail to report on, so there is nothing to monitor.

  • Reminders to people who already replied

    Extra emails to customers who have already responded invite spam reports, and spam reports are what Gmail’s threshold counts.

  • Old addresses keep bouncing

    Requests to stale contacts bounce month after month, and repeated bounces wear down the domain’s standing.

  • Nobody owns it

    Deliverability sits between marketing and IT, so each assumes the other is watching.

  • Volume jumps without warning

    A sudden batch to an old list is the classic trigger for a reputation drop.

Flip the switch to see how StoryProof handles each one.

Monitoring scorecard

How well do you watch your requests?

Rate each check yes, partly or no. Thresholds are from Google’s email sender guidelines and the Postmaster Tools help, read on 2026-11-17. They are Google’s rules for Gmail recipients; other mailbox providers publish their own.

Requests leave from your own authenticated domain
DMARC is published, and the From domain aligns
The domain is verified in Gmail Postmaster Tools
Someone reads the spam rate weekly against 0.1% and 0.3%
Bounces in your provider are reviewed and removed
A monthly test request goes to inboxes you control

Scores are worked out in your browser and not saved or sent.

In StoryProof

Put the routine on a calendar

  • You will need
  • StoryProof on Pro or above with your own provider connected
  • DNS access for the sending domain
  • A Google account for Postmaster Tools
  1. 1

    Send from a domain you can watch

    Connect your own email provider in StoryProof, so requests leave from your domain.

  2. 2

    Verify the domain in Postmaster Tools

    Add the DKIM or SPF domain, copy the DNS record it shows and click Verify. Data appears only after verification, and may be missing on low volume days.

  3. 3

    Weekly: read the spam rate

    The owner writes down the week’s spam rate and delivery errors. Anything above 0.1% pauses new batches until the cause is found.

  4. 4

    Monthly: clean and test

    Remove bounced addresses from your contacts, then send a test request to your three seed inboxes. Requests are email only, so this is the only channel to test.

What happens next: If a reading goes wrong, switch to the spam troubleshooting page for the fix, then come back to this routine once it recovers.

Before you start

What monitoring cannot tell you

  • Gmail data covers Gmail only

    Postmaster Tools reports on mail to personal Gmail accounts. Outlook, Yahoo and company mail servers are outside it.

  • Low volume means gaps

    Google notes data can be missing when a day’s volume is too low. Small senders may see empty days; that is not a fault.

  • StoryProof is not claimed to report deliverability

    Nothing on this page says StoryProof shows opens, bounces or spam rates. Those readings come from Google and your own provider.

  • Policy reading, not legal advice

    Thresholds and rules here are Google’s as read on 2026-11-17. They change, and a reviewer should confirm them.

  • Steps as of 2026-11-17

    Postmaster Tools steps follow Google’s help page on that date and have not been run on a live domain by us.

FAQ

Questions people ask

Short answers to what usually comes up next.

Is open rate a good deliverability signal?

It is a weak one, since many mail apps load or block images in ways that blur it. Spam rate, bounces and seed tests are more direct.

We send far fewer than 5,000 emails a day. Does DMARC matter?

Google only requires it above that volume, but every sender must have SPF or DKIM. DMARC is cheap to add and protects your domain from spoofing.

How long until Postmaster Tools shows data?

Verification usually updates within minutes. Data needs enough daily volume, so a small sender may see gaps.

Who should own this?

Whoever already owns the company’s email domain records, with the testimonial lead reading the weekly number.

Still have a question? Ask the StoryProof team or book a demo.

Send requests from a domain you can watch

Connect your own email provider to StoryProof and keep an eye on every request that leaves.

Sources

  1. Email sender guidelines, Google Workspace Admin Help. Checked 2026-11-17.
  2. Get started with Postmaster Tools, Google Workspace Admin Help. Checked 2026-11-17.

Last updated 2026-11-17.