The spam complaint rate is the share of recipients who mark your mail as spam. It is one of the most direct signals mailbox providers receive about a sender, because it comes from the people the mail was meant for. A small rise can change where your messages land. This guide explains how the rate is measured, what Google asks senders to stay under, how feedback loops report complaints and what to do when the number goes up.
What a complaint is
When a person presses the spam or junk button on a message, the mailbox provider notes it against the sender. It also uses the action to train its filters, so that similar messages are more likely to go to the junk folder for that person and for others. Complaints are different from bounces and unsubscribes. A bounce means the message could not be delivered. An unsubscribe means the person withdrew consent and told you directly. A complaint tells the provider, not you, that the mail was unwanted, which is why it carries so much weight.
| Signal | Who receives it | What it means |
|---|---|---|
| Hard bounce | Sender (via the server reply) | The address is invalid or refuses mail |
| Unsubscribe | Sender | The person no longer wants this mail, and told you |
| Spam complaint | Mailbox provider, sometimes the sender | The person judged the mail to be unwanted or abusive |
| Deletion without reading | Mailbox provider only | A weaker sign of low interest |
How the rate is calculated
The common definition is complaints divided by messages delivered, expressed as a percentage. If 2 people complain out of 4,000 delivered messages, the rate is 0.05 percent. Details vary, so rely on each provider for its own figure.
complaint rate = complaints / delivered messages x 100
Example: 6 / 5,000 x 100 = 0.12 percent
Small numbers can mislead. One complaint among 200 messages is 0.5 percent, which looks alarming but is a single person. Look at trends over days and at volumes large enough to be meaningful, and break the data down by campaign or stream.
What the thresholds are
Google publishes requirements for senders to Gmail. In its sender guidelines, it asks that user-reported spam rates, as shown in Postmaster Tools, stay below 0.10 percent and that they never reach 0.30 percent. Google also states that bulk senders must make it easy to unsubscribe. Our guide to the Gmail, Yahoo and Outlook bulk sender requirements covers the broader rules. Other providers have their own programmes and thresholds, which they may not publish in the same way. Treat the Google figures as a sensible ceiling for every stream, and aim well under them.
| Rate (Gmail, user-reported) | How to read it |
|---|---|
| Under 0.10% | Within Google guidance; keep watching the trend |
| 0.10% to 0.30% | Above the recommended level; investigate and act now |
| 0.30% or more | Google advises senders never to reach this level; treat as urgent |
Check the source. Thresholds and tools change over time. Confirm the current figures in Google's documentation before you set alerts, and see our guide to Google Postmaster Tools for how to view your domain data.
How feedback loops work
A feedback loop is a service where a mailbox provider tells the sender about complaints. When a recipient marks a message as spam, the provider sends a report to an address or endpoint you registered. Many reports use the Abuse Reporting Format, known as ARF and defined in RFC 5965, which is an email that includes the original message headers and a note that the user reported it.
- Registration. You usually register a sending domain or IP address with each provider that offers a loop, and prove that you control it.
- Report content. Reports typically identify the message, often with a copy of the headers, and may remove personal details of the recipient.
- Coverage varies. Some large providers offer loops, some offer aggregated data only, and some offer nothing. Gmail is a notable case where you rely on the aggregated rate in Postmaster Tools.
- Processing. Reports need to be parsed and turned into suppressions, otherwise the same person may be mailed again.
If you send through a platform, the platform usually registers for the loops and processes the reports on your behalf. Ask what your platform handles, what shows up in your events and what you need to register yourself, especially if you use a dedicated IP address. See dedicated IP versus shared IP for how reputation is shared or separated.
Why people complain
Complaints come from a small number of root causes. Knowing them helps you decide what to fix.
| Cause | What it looks like | Fix |
|---|---|---|
| No clear permission | The person does not remember signing up | Use confirmed opt-in; show your name and the reason they are receiving the mail |
| Surprise content | Mail differs from what was promised | Set expectations at sign-up and keep to them |
| Too frequent | Complaints rise with volume | Offer a frequency choice; cut low-value sends |
| Irrelevant | Mail is not useful to this person | Segment; stop mailing people who never engage |
| Hard to leave | The unsubscribe link is hidden or broken | Make it visible and honour it quickly |
| Bought or old list | Recipients never asked for the mail | Do not use; clean the list |
Reducing complaints: a practical sequence
- Make leaving easy. Put a plain unsubscribe link in every marketing message and add the List-Unsubscribe headers. Our guide to one-click unsubscribe explains how. People who can leave in one click rarely need to press spam.
- Say who you are. Use a recognisable From name and address, and remind people why they are receiving the mail.
- Match the promise. Send what people signed up for, at the pace you said.
- Segment and sunset. Mail the engaged first and stop mailing people who have gone quiet. See our guide to list hygiene and sunset policies.
- Separate streams. Keep marketing apart from receipts and account mail, so a complaint problem in one does not damage the other. See separating transactional and marketing streams.
- Suppress at once. When a complaint report arrives, stop marketing mail to that address immediately.
A worked example: tracking down a spike
A retailer sees its Gmail spam rate rise from 0.04 percent to 0.14 percent over a week. The team compares campaigns and finds that the increase is concentrated in one promotion sent to a segment that was imported from an event two years earlier. Most of those contacts had never engaged. Subject lines in that campaign also promised a gift that the body of the email did not make clear.
The team takes four actions. They pause mailing to the imported segment and move it into a re-engagement series. They rewrite the promotion so that its subject and body agree. They check that the unsubscribe link works in the main mail apps and add the one-click header to the stream. Finally, they set an alert at 0.08 percent in their reporting so that they notice sooner next time. Over the following weeks the rate falls back as volume shifts to engaged recipients. The figures here are illustrative, and a real recovery depends on the provider and the size of the problem.
What not to do
- Hide the unsubscribe link to keep numbers up. It tends to turn unsubscribes into complaints.
- Contact people who complained. They have told their provider they do not want mail from you.
- Judge only by the average. One bad campaign or source can be lost in a healthy average. Break it down.
- Ignore small senders. Low volume makes the rate swing, but a few complaints still hurt a new domain. Warm up carefully as described in our warm-up guide.
- Forget authentication. Complaint feedback is tied to your domain and IP address. If you have not set up SPF, DKIM and DMARC, start with authenticating your domain.
Seeing complaints you cannot explain? Send us the campaign details and dates and we will help you read the data.
Further reading and sources
Frequently asked questions
What is a spam complaint?
A spam complaint happens when a recipient marks a message as spam or junk in their mail app. The mailbox provider records it as a signal about the sender, and some providers also report it back to the sender through a feedback loop.
What spam complaint rate is acceptable?
Google asks bulk senders to keep their user-reported spam rate below 0.10 percent and to avoid ever reaching 0.30 percent. Treat those as upper limits, and aim for a rate well below them.
How is the complaint rate calculated?
In general, it is the number of complaints divided by the number of messages delivered to the inbox, shown as a percentage. Providers differ in exactly what they count, so use each provider own reporting for its own figure.
What is a feedback loop?
A feedback loop, or FBL, is a service where a mailbox provider sends the sender a report each time a recipient marks a message as spam. Many reports use the Abuse Reporting Format described in RFC 5965. Not every provider offers one.
Does Gmail send feedback loop reports?
Gmail does not send individual complaint reports in the usual way. It shows an aggregated spam rate in Google Postmaster Tools, and a feedback loop for senders is available in a limited form. Check the current Google documentation for details.
What should I do when someone complains?
Stop mailing that address for marketing, add it to your suppression list and review which message triggered it. Do not email the person to ask why, because that can make matters worse.
Why do people mark mail as spam instead of unsubscribing?
Usually because the unsubscribe link is hard to find or seems unreliable, because they do not remember signing up, or because the mail feels irrelevant or too frequent. Clear links and honest expectations reduce complaints.
Can transactional mail cause complaints?
Yes, though the rate is usually lower. Receipts and account notices that the recipient did not expect, or that arrive for the wrong person, can still be marked as spam. Keep such mail accurate and relevant.
How fast does reputation recover after a spike?
It depends on the provider and the size of the problem. Fix the cause first, reduce volume to your most engaged recipients and then increase gradually. Recovery can take days or weeks, and we cannot promise a specific time.