Updated · 9 min read
Spam complaints: the playbook for detecting and reducing them
Bounce rates move first. Complaint rates move second, and hit harder. A complaint rate creeping past 0.3% is how the program that was delivering fine last month is suddenly in the promotions tab this month. The mechanics aren't really about spam filters — they're about psychology. What makes a tired user click the spam button instead of unsubscribe is a design problem, not a deliverability one.
By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
The thresholds and the asymmetry
< 0.1%
Healthy complaint rate. Below this, no concern.
0.1–0.3%
Warning zone. Reputation damage is starting to accumulate.
> 0.3%
Active damage. Immediate intervention required.
A complaint is worth 10–20 unsubscribes in ISP reputation terms. Users who complain are telling the filter they didn't expect or want your mail at all.
Here's the asymmetry that makes complaints different. An unsubscribe is a benign signal — the user changes their preferences. A complaint is a negative signal — the user is reporting the sender as a problem. ISPs watch complaints closely because they're the purest indicator of user-reported spam. A program with a 1% unsubscribe rate and a 0.1% complaint rate delivers cleanly. One with a 0.3% unsubscribe rate and a 0.4% complaint rate often doesn't. Same people leaving, very different filter interpretation.
Gmail, specifically, starts treating senders as spam-adjacent at 0.3%+ and the slope gets steep from there. The threshold is effectively the same across major ISPs, with minor variation in how fast they act on it.
What actually triggers a complaint
Unexpected frequency.The biggest driver by a country mile. A user who signed up for "weekly updates" and is now getting three emails a week will complain at roughly 3–5× the rate of a user getting the expected frequency. Complaints land because the pattern violated the deal, not because the content was bad. Content isn't usually the issue.
A difficult unsubscribe flow. The user wants out. The unsubscribe button is small, hidden behind a login, or routes to a preference centre with a seven-item form before the actual opt-out. They hit "report as spam" because it's faster. The unsubscribe page guide covers this pattern in depth.
Content that feels deceptive.Subject line implies transactional but the message is promotional. Links disguised as interface elements. False urgency — "only 2 hours left" five days in a row. Users read these as manipulation, and manipulation is what the spam button is for.
Zero-context re-engagement. A user who hasn't touched your brand in 18 months gets an email out of nowhere. They don't remember signing up. The email feels unsolicited because, to them, it is. This is what the list hygiene policy's sunset rule is built to prevent — cull dormant users before they become complaint sources, not after.
How to detect complaints early
Complaint data reaches you through three channels, each with a different fidelity.
1. ESP feedback loops (FBL).Yahoo, Microsoft, AOL, and Comcast send complaint data back to senders. Gmail notably does not — they surface complaint rates in Postmaster Tools but don't feed back individual complaints, which means you can see the magnitude but not the specific users. Your ESP aggregates everything FBLs send and exposes it in reporting.
2. Google Postmaster Tools. Gmail-specific complaint rate in aggregate form. Check weekly. A spike here is your earliest indicator of a Gmail-specific issue, and Gmail is usually where the first sign of trouble shows up because of their user base size.
3. Unsubscribe rate as a proxy.Complaint rate and unsubscribe rate usually move together. A sudden unsubscribe spike without a corresponding complaint spike means the unsubscribe flow is working — people are leaving, but they're leaving the right way. A complaint spike without an unsubscribe spike means users can't find unsubscribe. That one's fixable today.
,
The four levers to reduce complaint rate
Lever 1: frequency adjustment.Reduce send frequency for the specific cohort driving complaints. Usually it's one identifiable segment — new subscribers getting too many onboarding emails, or dormant users swept into broadcast frequency. Segment the complaint data by cohort and cut frequency for the offenders. Don't cut the whole list.
Lever 2: unsubscribe flow improvement. One click. No friction. No preference-centre-first. Users who can easily leave don't click spam. Covered in depth in the unsubscribe guide.
Lever 3: expectation setting at signup.Tell users what they're signing up for. "Weekly newsletter" with the frequency confirmed at opt-in time. When the sending pattern matches the expectation, complaint rate falls. Straightforward mechanism, often ignored.
Lever 4: aggressive dormant suppression. The hygiene policy's 180-day sunset rule exists specifically to prevent the "I don't remember signing up" complaint. Cutting the dormant segment reliably drops overall complaint rate by about a third. The short-term volume hit is the cost. The sustained reputation is the benefit.
One more worth naming because it comes up: should you suppress users who complain? Yes, immediately. A complaint is a definitive negative signal. Permanent suppression from marketing; transactional is usually fine to continue because it's what the user expects. Continuing to send marketing to someone who complained is one of the most reliable ways to cascade reputation damage across your whole program.
When to pull the emergency brake
Complaint rate above 0.5% on a specific IP or subdomain is emergency territory. Stop sending to that audience segment. Today. Not at the weekly review. The damage compounds with every send, and the reputation recovery from a 1%+ spike is 6–12 weeks of scaled-back volume and tightened targeting — preventing the spike is dramatically cheaper than climbing back from one.
For smaller spikes, recovery is faster, but the protocol is the same: scale volume back, tighten the audience to most-engaged users only, fix the underlying cause (frequency, unsubscribe flow, or dormant suppression), and don't resume normal volume until rates drop and hold below 0.2% for at least two weeks.
The Orbit Deliverability Management skill covers both the preventive policy and the incident-response sequence if complaint rates do spike. Having the workflow ready before you need it is how you avoid 30 days of decisions made under pressure at the end of Q4.
Frequently asked questions
- What's a safe spam complaint rate?
- Gmail publishes 0.3% as the threshold above which they materially degrade delivery. Operator-consensus safe ceiling is 0.1% — one complaint per 1,000 sends. Above 0.3% triggers immediate reputation damage; above 0.5% can shut down deliverability across mailbox providers within days. A single campaign exceeding 0.3% should trigger an immediate pause-and-audit of the list and the last 30 days of sending patterns.
- Why do users mark my emails as spam?
- Three usual reasons. First, they forgot they subscribed — time since signup, frequency mismatch, content drift from what they opted into. Second, the unsubscribe link is hard to find — users take the faster path of hitting "report spam" instead of scrolling the footer. Third, the content is genuinely unwelcome — aggressive promotional content, re-targeted purchase notifications, or topic mismatch. Fixes in order: visible one-click unsubscribe, List-Unsubscribe header implementation, and realistic expectations at signup.
- How do I recover from a spam complaint spike?
- Four-step recovery. Pause the campaign immediately. Identify the segment or subject-line that spiked complaints (usually a large promotional send to a long-neglected segment). Suppress everyone who has complained in the last 90 days plus the non-engaged subset of the complaining segment. Resume sending at reduced volume to only your most-engaged subscribers for 2-3 weeks while reputation signals stabilise. Full recovery typically takes 4-8 weeks.
- Does an unsubscribe damage reputation less than a spam complaint?
- Yes, substantially. Mailbox providers treat unsubscribes as "user managed their preferences" — no reputation impact. Spam complaints are treated as "user experienced unwanted mail" — strong negative signal. Making the unsubscribe path obvious is the single best complaint-rate reduction tactic — users who would have hit "report spam" out of frustration instead take the unsubscribe path, which costs you the subscriber but not the reputation.
- Is a high complaint rate always the sender's fault?
- Mostly. Occasionally a specific audience segment is structurally complaint-prone (purchased lists always, bulk freemium signups often, older demographics on AOL / Yahoo occasionally). But the vast majority of complaint spikes trace to sender decisions: frequency, content-audience mismatch, sunset-flow failure, or sending to re-acquired data that shouldn't have been marketed to without re-confirmation. Treat every spike as a sender-side problem first; it almost always is.
This guide is backed by an Orbit skill
Related guides
Browse allList hygiene: the six-rule policy
List hygiene isn't cleanup; it's a continuous policy that runs automatically. Here's the six-rule policy every lifecycle program should have written down, each tied to a specific deliverability outcome.
Bounce rate management: the thresholds and the fix order
Bounce rate is the easiest deliverability metric to read and the easiest to misread. Here's what each bounce type actually means, the thresholds that trigger real problems, and the fix order when your rate climbs.
Reputation recovery: the 90-day playbook for dropping from High to Low
Domain reputation at Low or Bad isn't a problem you fix this week. It's a 6–12 week project of disciplined sending to engaged users only, while the reputation signals slowly reset. Here's the plan.
Email deliverability — the practitioner's guide
Deliverability isn't a setting. It's the running total of every send decision you've made since you bought the domain. Four pillars hold it up. Break one and the whole program starts leaking.
The unsubscribe page is the most important page in your lifecycle program
The page every lifecycle team ignores is the one quietly deciding sender reputation, suppression-list quality, and the fate of next quarter's deliverability. A short defence of why it deserves the ten-minute rebuild.
SPF, DKIM, and DMARC explained for lifecycle marketers
Three DNS records decide whether your marketing email is trusted or binned. Gmail and Yahoo made all three mandatory for bulk senders in 2024, and the grace period is over. This is the practitioner's explainer: what each one does, how they interact, and the setup order that won't block your own mail.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 54 lifecycle methodologies, 55 MCP tools, native Braze integration. Pay what it's worth.