Monitoring & Stop Rules

Run this dashboard at the end of every sending day during the 7–14 day ramp. Once the ramp is complete, check weekly as a minimum. One named person owns the daily check — log results in a shared tracking sheet.

Where the numbers come from (the Postmaster blind spot)

Google Postmaster Tools only populates its dashboards once you are sending meaningful volume to Gmail addresses. A club ramp starts nowhere near that level. Day 1 is Tier A — roughly 15% of the active base, around 105 sends for a 700-member club. With a typical Gmail share of roughly 35–40% on a UK club list, that is approximately 40 Gmail sends on Day 1 — far below the volume at which Postmaster shows data. The practical consequence: during exactly the days the gates in this page matter most, Postmaster is usually blank.

That blind spot does not leave you flying blind — it just means Postmaster is not the gate. Use this hierarchy, in order:

A blank Postmaster dashboard is normal at club volume and is NOT a green light. Gate the ramp on Mailgun events — complaints, bounces, and deferrals — backed by replies, clicks, and seed-panel reads. Postmaster data, when it eventually appears, is a bonus cross-reference, not the gate.

Why opens are not a gating metric

Remove open rate from your warm-up scorecard. It is not reliable, and acting on it will mislead you.

• Apple Mail Privacy Protection (MPP) pre-fetches the tracking pixel at delivery — regardless of whether the human ever reads the message. This inflates recorded open rates by roughly 40–50% for Apple Mail users. You cannot distinguish machine-triggered from human-triggered opens.
• Google does not track or verify third-party open rates. A strong recorded open rate in GHL does not confirm Gmail inbox placement.
• Gmail retired its domain and IP reputation dashboard on 30 September 2025. Do not attempt to read inbox placement from it. The primary gating signals are Mailgun FBL complaint and bounce events, with the Postmaster spam-rate indicator as a cross-reference once it shows data.
• GHL on a custom SMTP connection shows only opens and clicks — delivery status, bounces, deferrals, and complaint data must be read in Mailgun analytics directly (and in Google Postmaster once it shows data).

A club can show 60% opens while Gmail is routing every message to the spam folder, with Apple devices pre-fetching the pixel. You would see no bounce, no filed complaint, and a healthy-looking dashboard — while no human reads a single email.

The real scorecard: spam complaint rate (Mailgun FBL events), hard bounce rate, soft bounce and deferral rate, unsubscribe rate, authentication pass rate, Google Postmaster spam-rate signal (when it shows data), Microsoft SNDS complaint trend, per-provider block and rejection rates, click rate, reply rate, and real club conversions (bookings, enquiries, event sign-ups).

Daily metrics dashboard

Threshold notes

Spam complaint rate at golf-club scale. For a 700-member list, 0.10% equals roughly one complaint per 1,000 recipients. A single complaint moves the needle meaningfully. Monitor cumulative complaint counts per campaign, not only percentages.

Hard bounce in context. A rate above 2% on a golf club list almost always means the list was not properly cleaned before import, or an older unmaintained segment was added prematurely. The response is to identify the specific tranche that caused the bounces and validate it before any further use — not simply to pause.

Authentication pass rate. A drop below 100% that cannot be explained by a known, temporary DNS propagation event is a configuration fault. SPF, DKIM, and DMARC must all align with the From domain — for example, info@mail.highgategc.co.uk authenticated against mail.highgategc.co.uk, not the root. Any alignment failure can trigger permanent SMTP rejection under Google and Yahoo's 2025/2026 sender requirements.

Soft bounce nuance. A small number of soft bounces during warm-up is normal — mailbox-full errors and temporary server issues happen. What matters is a rising rate on a specific provider, which usually signals that provider is rate-limiting or deferring your traffic. Hold that provider's share; do not cut everyone else.

Manual throttling note. GHL has no native send-throttling — it bursts the full queue against the shared Mailgun pool rate limit (~300/hr on Flex plans). Batch and cap sends per hour at cutover. Never one bulk blast, regardless of where you are in the ramp.

End-of-day decision logic

Work through these checks in order. Stop at the first failure and act on it before proceeding.

1. Is the spam complaint rate below 0.10%? Read it from Mailgun FBL events (and Postmaster when it shows data — it usually will not at ramp volume).

   • Yes → proceed to check 2.
   • No (0.10%–0.20%) → hold volume growth; suppress all recorded complainers immediately; audit the segment, subject line, and content of the campaign that generated complaints; do not advance to the next ramp stage until the rate returns to green for three consecutive days.
   • No (> 0.20%) → pause all promotional sends; suppress all complainers; reduce audience to Tier A only; audit consent evidence and segment quality before resuming; do not restart growth until the rate holds below 0.10% for two to three consecutive clean send days.
   • No (0.30% or above) → treat as a hard failure; stop all promotional sends immediately; escalate to the agency deliverability lead; audit consent basis for every contact in the segment; do not resume until a full root-cause analysis is complete.

2. Is the hard bounce rate below 2.0%?

   • Yes → proceed to check 3.
   • No (2.0%–3.0%) → pause adding any new segments; identify which list tranche caused the bounces; remove all hard-bounced addresses permanently from GHL; run those records through LC Email validation before any further use; do not advance the ramp.
   • No (above 3.0%) → stop new volume entirely; re-validate the full remaining mailable list using GHL's built-in validation; assess whether the Intelligent Golf export was improperly cleaned.

3. Is the soft bounce / deferral rate below 5% on all major providers?

   • Yes → proceed to check 4.
   • No on one provider → hold that provider's share of the next send; do not reduce overall volume unless two or more providers show stress; check Microsoft SNDS if the affected provider is Outlook/Hotmail.
   • No on multiple providers → hold all volume growth; check Spamhaus DBL and ZEN, Google Postmaster, and SNDS simultaneously.

4. Has any provider returned a 5xx hard rejection with a reputation reason?

   • No → proceed to check 5.
   • Yes for one provider → isolate that provider's contacts; do not send to them again until the block is resolved; for Outlook use SNDS and the Microsoft Sender Support portal; for Gmail use Postmaster; for Yahoo use the Yahoo Postmaster site.
   • Yes for multiple providers → treat as systemic; stop all sends; check authentication records, blocklist status, and sending IP reputation before any further campaigns.

5. Is Google Postmaster domain reputation at High or Medium? (Only applicable once Postmaster shows data — a blank dashboard is normal at club volume; treat it as "no data" and proceed to check 6, gating on the Mailgun signals above.)

   • Yes, High or Medium and holding → proceed to check 6.
   • Medium with downward movement → slow the ramp; return to Tier A only; monitor daily.
   • Low or Bad → stop adding volume; reduce to ultra-engaged Tier A only; check authentication alignment; review recent content.

6. Are click rate, reply rate, and conversion metrics stable or improving as audience grows?

   • Yes → proceed to the advancement rule below.
   • Flat despite volume growth → hold the ramp at current level; the newly added audience is not as engaged as earlier tiers; review whether you have advanced too quickly through the tier structure.
   • Falling as volume increases → roll back to the previous stage's volume; the most recently added segment is dragging down average engagement; tighten the audience and hold for five to seven days before attempting to re-expand.

Stage advancement rule

Advance after 2–3 consecutive clean send days at each stage — clean means spam complaints below 0.10%, hard bounces below 0.50%, and authentication at ~100%, with every metric in the dashboard within green thresholds. A longer 7-day stability view applies only to post-ramp steady state, not to per-stage advancement during the ramp.

• If any metric enters amber during the count, the clock resets. Hold at current volume, resolve the cause, and start the clean-day count again once all metrics are back to green.
• If any metric reaches a pause/stop threshold, follow the relevant stop rule, resolve the issue, and only restart the clock once you have confirmed the fix is working.
• Never increase volume on the same day a metric enters amber. Wait, diagnose, re-evaluate.
• After the full ramp is complete, maintain weekly monitoring. Sending reputation is not permanent — a significant list-quality problem or a content mistake can move Postmaster reputation downward even after months of stable delivery.

Default ramp frame: the engagement-gated ramp runs approximately 7–14 days on the pre-warmed shared Mailgun IP. This is domain and subdomain reputation building — not IP warming (the shared IP is already warm). The 30/60-day calendar schedule is the documented fallback for clubs with genuinely messy or stale data; it is not the default.

What to do on each red flag

Spam complaint rate enters amber (0.10%–0.20%)

• Suppress every contact who filed a complaint immediately — do not wait for the next day's check.
• Identify the segment, subject line, and content of the campaign that generated complaints. Was it more promotional? Did it reach a lower-engagement tier? Was the from name unfamiliar?
• Hold volume at current level — do not advance the ramp.
• Check whether unsubscribe links were broken or hard to find. A member who cannot unsubscribe quickly will sometimes report as spam instead.
• Do not restart growth until the rate holds below 0.10% for at least three consecutive sending days.

Spam complaint rate enters stop threshold (> 0.20% / approaching 0.30%)

• Pause all promotional sends immediately.
• Suppress all complainers.
• Reduce audience to Tier A only.
• Audit the consent basis for the segment that generated complaints — is there clear permission or soft opt-in evidence for these contacts?
• Review content: was it clearly identifiable as being from the club? Was the topic something members would expect and want?
• Do not resume growth until the rate holds below 0.10% for two to three consecutive clean send days.
• If you cannot identify a clear root cause, engage your ESP (Mailgun / LC Email) and consider a voluntary pause of one to two weeks before restarting with a smaller, cleaner audience.

Hard bounce rate enters amber (0.5%–2.0%)

• Stop importing or mailing any new data tranches until the source of the bounces is identified.
• Pull the bounce report from GHL and Mailgun analytics. Which domains are bouncing? Is it a cluster of corporate addresses, old personal addresses, or a specific membership category?
• Remove all hard-bounced addresses permanently from GHL. Do not re-mail them.
• If the tranche came from a specific Intelligent Golf export segment (e.g., lapsed members), validate that segment through LC Email validation before any further use.

Hard bounce rate above 2.0%–3.0%

• Pause all new volume additions.
• Run the affected tranche — and ideally the full remaining mailable list — through GHL's built-in email validation tool.
• Assess whether this is a systemic data quality problem. If so, validate the entire import before resuming.

Hard bounce rate above 3.0%

• Stop all promotional sends.
• Re-validate the entire mailable list.
• Audit the Intelligent Golf export process: were suppression lists, historical bounces, and consent flags correctly applied before import?
• Do not resume until bounce rate is confirmed below 0.5% across a validation sample.

Soft bounce / deferral rate above 5% on a specific provider

• Isolate that provider's contacts into a separate smart list in GHL.
• Hold their share of the next campaign — do not cut their volume to zero permanently; hold until the deferral pattern clears.
• For Outlook/Hotmail: check Microsoft SNDS for IP health signals and JMRP for complaint-loop data. If there are signs of a sending IP block, use the Microsoft Sender Support form.
• For Gmail: check Postmaster for the sending subdomain. A deferral spike often precedes a reputation downgrade.
• Resume that provider's share only once deferral rates drop back below 2% over two to three consecutive days.

Google Postmaster domain reputation moves to Low or Bad

• Reduce send volume immediately to Tier A only.
• Do not add any new contacts to the queue until reputation recovers.
• Verify authentication alignment: confirm SPF, DKIM, and DMARC are all passing at 100% for the sending subdomain.
• Review the most recent two or three campaigns for content issues: image-heavy layouts, URL shorteners, or topics Gmail's algorithms might classify as a promotional blast.
• Check that the custom tracking CNAME (e.g. link.highgategc.co.uk) is correctly configured. Using a shared or generic GHL tracking domain leaks reputation from other senders on that pool.
• A Low reputation typically requires one to three weeks of consistent, low-volume, high-engagement sending before it improves. A Bad reputation may take longer. Do not attempt to accelerate recovery by sending more volume — it makes it worse.

Unsubscribe rate above 1.0%

• Review whether content is genuinely relevant to the members receiving it. High unsubscribes often signal a mismatch between what the club is sending and what members expected.
• Check frequency: are you sending more campaigns per week than members received through Intelligent Golf?
• Review the preference centre: are members offered granular opt-down options, or only a binary unsubscribe? A well-structured preference centre (e.g., opt out of offers but stay on course updates) can convert some full unsubscribes into partial opt-downs.
• Hold ramp advancement and do not add new audience tiers until the rate drops below 0.30%.

Authentication pass rate drops below 100%

• This is a configuration fault, not a list quality problem. Do not pause volume for this alone, but do not advance the ramp either.
• Check the specific failure mode via DMARC aggregate reports (rua address on the club's DMARC record): is it SPF alignment failure, DKIM alignment failure, or both?
• The most common GHL cause: the From domain does not exactly match the DKIM signing domain. For example, sending from info@mail.highgategc.co.uk but the DKIM key is on highgategc.co.uk. Correct the signing domain in GHL LC Email settings.
• Confirm the SPF include: for Mailgun/LC Email is published on the subdomain (mail.highgategc.co.uk), not only on the root.
• Do not advance the ramp until pass rate is back at 100%.

Reading Google Postmaster Tools

Postmaster is the most authoritative Gmail-side signal available once it shows data — which at club volume is typically not during the ramp (see the Postmaster blind spot above). During the ramp, gate on Mailgun events; treat Postmaster as a bonus cross-reference that becomes meaningful mainly at full-list steady state. Verify both the root domain and the sending subdomain (e.g. both highgategc.co.uk and mail.highgategc.co.uk) for full visibility.

The critical nuance: a low spam rate does not guarantee inbox placement

Gmail may route mail to the spam folder without it appearing in the user-reported spam rate. When Gmail's algorithms automatically classify a message as spam, the filtering action does not increment the spam rate counter — because the user never actively reported it.

What you will see instead: domain reputation at Medium or drifting toward Low, lower-than-expected engagement, and no sharp complaint spike. Flat complaint rate plus falling domain reputation is the signature of algorithmic filtering starting — usually caused by low engagement from the latest audience tranche, or by content that resembles a promotional blast.

Do not interpret a spam rate of 0.00% as confirmation that all mail is landing in the inbox. Always cross-reference spam rate with domain reputation, deferral rates, and real engagement metrics.

Daily Postmaster routine during warm-up

• Check domain reputation for both root and subdomain. A single day's movement from High to Medium is not a crisis — watch for a trend.
• Check spam rate. Even a single tick above zero is worth reviewing at golf-club list sizes.
• Check authentication pass rate. Any degradation is a configuration fault to fix immediately.
• Use delivery errors to diagnose any 5xx rejections from Gmail specifically.
• Set up email alerts in Postmaster so a reputation change does not go unnoticed overnight.

When Postmaster data is not yet visible: Postmaster only populates when you have sent meaningful volume to Gmail addresses, and club ramp volumes (tens of Gmail sends per day in the early stages) are usually below that threshold. Expect the dashboards to stay blank for much or all of the ramp — this is normal and is not a green light; keep gating on Mailgun events, replies, and seed-panel reads. If data still has not appeared once you are at full-list steady state, confirm you have verified the correct subdomain in Postmaster, not only the root domain.

Microsoft SNDS and JMRP

For clubs with a significant Outlook/Hotmail/Live share, enrol in both services at https://sendersupport.olc.protection.outlook.com/snds/:

• Smart Network Data Services (SNDS): IP-level data including complaint rate, trap hits, and filter status.
• Junk Mail Reporting Programme (JMRP): individual complaint feedback-loop notifications delivered to a nominated address.

Monitor SNDS weekly at minimum and daily during warm-up. An SNDS status of Red means Microsoft is actively filtering or blocking your mail — hold all Outlook/Hotmail sends and use the Microsoft Sender Support form immediately.

Quick-reference pause matrix

Use this as a desk reference for the person running daily checks.

Roles and escalation

Escalation triggers: any metric reaching a pause/stop threshold; any 5xx rejection from a major provider; Google Postmaster domain reputation reaching Low or Bad; authentication pass rate below 100% for more than one consecutive day.

Read alongside Ramp Schedule, Data Prep & List Hygiene, Operator Runbook, Compliance — UK GDPR & PECR, and Email Templates.