Metrics

Spam Complaint

Definition

A spam complaint is recorded when a recipient marks one of your messages as spam, usually by clicking the report-spam button in their inbox. It is the single most damaging negative signal a sender can collect: the recipient is telling their mailbox provider, in the clearest possible terms, that your mail is unwanted. A rising complaint rate lowers your sender reputation fast.

  • Triggered when a recipient clicks “report spam” on a message
  • One complaint outweighs many opens; it is the costliest engagement signal
  • Providers relay complaints to senders through a feedback loop in ARF format
  • Gmail asks bulk senders to keep the complaint rate under 0.3%, ideally below 0.1%
At a glance
Triggered by The report-spam button
Measured as Complaint rate (complaints / delivered)
Reported via Feedback loops (FBL)
Report format ARF (RFC 5965)
Gmail limit < 0.3% (target < 0.1%)
Reputation hit Severe, and fast

What happens when someone complains

When a recipient clicks the report-spam button (or moves a message into the spam folder), their mailbox provider records a complaint against the sender. Internally, the provider treats this as a strong vote that your mail is unwanted, and it feeds straight into how it filters your future messages. Because the signal comes from a real human deliberately rejecting your mail, it carries far more weight than a passive non-open: a common rule of thumb is that one complaint does more damage than dozens of opens can repair.

The complaint also affects the recipient’s own view: future mail from you is more likely to skip their inbox entirely. Multiply that across a list and a high complaint rate quietly suppresses delivery for everyone, not just the people who complained. This is why complaints are tracked as a headline metric in Google Postmaster Tools and treated as a hard ceiling by the bulk-sender rules.

How complaints reach the sender: feedback loops

Most senders never see the individual report-spam click directly. Instead, providers relay complaints through a feedback loop (FBL): when a user complains, the provider packages the offending message into an Abuse Reporting Format report (ARF, defined in RFC 5965) and emails it back to the sender or their ESP, provided they have registered for the loop in advance.

Providers implement this differently. Yahoo and Microsoft run traditional address-level FBLs that name the complaining recipient so you can suppress them. Gmail does not expose individual complainers; instead it offers an aggregate Feedback Loop dashboard in Postmaster Tools that reports a spam rate per campaign, which you enable by embedding a special FBL identifier header in your mail. Either way, the purpose is the same: give you an early warning so you can stop mailing people who do not want you before your reputation collapses.

The core fields of an ARF feedback report relayed to a sender 
Feedback-Type: abuse
User-Agent: SomeMailProvider/1.0
Version: 1
Original-Mail-From: bounce@example.com
Original-Rcpt-To: subscriber@example.net
Arrival-Date: Tue, 09 Jun 2026 14:02:11 +0000

The numbers that matter

Complaints are judged as a rate, not a raw count: complaints divided by messages delivered. Since February 2024, Google’s bulk-sender rules tell anyone sending 5,000 or more messages a day to Gmail to keep the spam rate reported in Postmaster Tools below 0.10%, and never reach 0.30% or higher. Cross the 0.3% line and Gmail can start routing your mail to spam or rejecting it; you only become eligible for relief once the rate stays under 0.3% for several consecutive days.

These percentages sound tiny, and that is the point. At a 0.3% rate, just 3 complaints for every 1,000 delivered messages is enough to trigger heavier filtering, so a single bad campaign to a poorly sourced list can tip you over. The practical takeaway is that complaints must be measured and managed continuously, not reviewed after the damage is done. You can track the trend for your domain in the Postmaster Tools spam-rate dashboard.

How to keep complaints down

  • Only mail people who asked. Double opt-in and removing purchased or scraped addresses is the biggest single lever on complaint rate.
  • Make unsubscribing trivial. A visible unsubscribe link plus one-click unsubscribe gives unhappy recipients an easy exit so they leave instead of hitting report-spam.
  • Honour complaints instantly. Feed every FBL report into your suppression list and never mail that address again.
  • Match expectations. Send the cadence and content people signed up for; surprise frequency and bait-and-switch subject lines are complaint magnets.

The path of a spam complaint

A recipient clicks “report spam” on your message
Their mailbox provider records a complaint against your domain
If you are registered, the provider relays it
Yahoo / Microsoft: address-level FBL Gmail: aggregate spam-rate dashboard
Your complaint rate rises and reputation drops
Over 0.3%: filtering or rejection
Suppress the complainer to protect the rest of the list

Spam complaint vs unsubscribe

Spam complaint Unsubscribe
Recipient action Hits report-spam Clicks unsubscribe
Reputation impact Severe Minimal
Tells the provider This sender is a spammer I just want to leave
Counts toward Complaint rate Unsubscribe rate
Best response Suppress and investigate Suppress, no alarm

By the numbers

0.3%
The spam-complaint rate Gmail tells bulk senders never to reach; crossing it can send your mail to spam.
0.1%
The complaint rate Google recommends staying under for healthy, resilient deliverability.
3 / 1,000
How few complaints per thousand delivered messages it takes to hit the 0.3% threshold.

Common mistakes

Ignoring feedback-loop reports
An FBL report names someone who already rejected your mail. Failing to suppress them means you keep mailing a guaranteed complainer, driving your rate higher with every send. Automate suppression from every FBL.
Hiding or omitting the unsubscribe link
When recipients cannot easily leave, they reach for the report-spam button instead, which is far more damaging than an unsubscribe. Make unsubscribing obvious and one click away.
Mailing purchased or scraped lists
People who never opted in complain at high rates. A single send to a bought list can blow past the 0.3% threshold and torch a reputation you spent months building. Only mail addresses that opted in.
Watching raw counts, not the rate
Ten complaints is fine across a million sends and catastrophic across a thousand. Providers judge the rate, so track complaints as a percentage of delivered mail, not as a total.

Frequently asked questions

What is a good spam complaint rate?
Gmail’s bulk-sender rules ask you to keep the spam rate reported in Postmaster Tools below 0.10% and to never reach 0.30% or higher. In practice, treat 0.1% as your target and 0.3% as a hard ceiling: cross it and Gmail may start filtering or rejecting your mail until the rate recovers.
How do I find out who marked my email as spam?
Through a feedback loop. Yahoo and Microsoft run address-level FBLs that name the complaining recipient in an ARF report so you can suppress them. Gmail does not reveal individual complainers; it gives you an aggregate spam-rate dashboard and a campaign-level Feedback Loop in Postmaster Tools instead. Register for each provider’s loop to receive the reports.
Why do spam complaints hurt so much?
Because they are a deliberate, human signal that your mail is unwanted, which is exactly what spam filters are built to detect. One complaint carries more weight than many passive opens, and a rising complaint rate suppresses delivery for your entire list, not just the people who complained.
How can I reduce spam complaints?
Only mail people who explicitly opted in (ideally via double opt-in), make the unsubscribe link visible and add one-click unsubscribe, suppress every address that complains via a feedback loop, and send the content and frequency recipients actually signed up for. Most complaints come from unwanted, unexpected, or hard-to-escape mail.
Reviewed by Jennifer Jackson, Email Deliverability Analyst · June 2026 ← Back to glossary