ON THIS PAGE
By Efe Berke Colaker, Founder at GetleadReviewed by the Getlead editorial team for accuracy. Last updated August 2026.
Bounce rate gets the attention because it is visible in every sending tool. The metric that actually ends programs is the one most teams never look at. Because it lives at the mailbox provider rather than in your dashboard.
Complaint rate is the share of delivered messages that recipients mark as spam. Google publishes 0.3% as the ceiling for bulk senders and 0.1% as the level to operate at. Those numbers are small enough that the arithmetic surprises people the first time they run it.
How the rate is calculated, and where it is measured
Complaint rate is complaints divided by messages delivered, not messages sent, and it is calculated per provider. Gmail scores your Gmail traffic, Microsoft scores your Outlook traffic, and neither knows or cares about the other.
Two consequences follow. First, small sends are volatile: on 300 delivered messages a single complaint is 0.33%, already over the line. Second, a clean overall average can hide a provider specific problem. So an aggregate number from a sending tool is not a substitute for the provider view.
What counts as a complaint
Pressing the report spam button is the obvious one. Moving a message to the spam folder counts at most providers. Deleting without reading does not count directly, but it feeds the engagement signals that decide placement, which is the same problem one step removed.
The arithmetic on small sends
For example, run the numbers on a realistic campaign. Send 2,000 messages, get 1,900 delivered, and the ceiling allows you five complaints before the domain is at the limit. Six people out of 1,900 having a bad morning is enough. That is not a scare statistic, it is the design of the system: providers set the bar where only genuinely wanted mail clears it.
The corollary is that complaint rate is noisy at low volume and should be read as a trend rather than a single reading. One complaint in a 300 message test week is a signal to watch, not a crisis. Three weeks in a row at that level is a targeting problem you have already been paying for.
Spam complaint rate is the share of delivered messages that recipients mark as spam, calculated separately by each mailbox provider and never reported back to the sending tool.
For example, a campaign delivering 1,900 messages reaches the 0.3% ceiling at six complaints and the 0.1% operating level at two. That is why a single mistargeted segment can breach the limit without anything else changing.
Where to actually see your number
You cannot manage this metric from your sending tool. Three free sources give you the real view, and setting all three up takes under an hour.
Postmaster Tools needs enough volume before it reports a rate. That is itself informative: if you are too small to be measured, you are also small enough that a handful of complaints is a large percentage.
Set these up before the first campaign, not after the first problem. Historical data is what lets you tell a bad week from a bad direction, and you cannot backfill it.
Google Postmaster Tools is the free service that reports complaint rate, domain reputation and authentication results for Gmail traffic.
What actually moves the number down
In descending order of effect, based on what changes when teams fix each one.
- Targeting. People complain when a message has nothing to do with them. Tightening the segment beats every copy change ever tested.
- List quality. Old records reach people who changed roles, or spam traps that were harvested along the way. Verification removes the first category and reduces the second.
- Frequency. The same prospect hit by three sequences from three reps is a complaint waiting to happen. Suppression across campaigns is a complaint control, not just hygiene.
- Obvious exit. A visible unsubscribe and a working one click header give annoyed recipients a cheaper option than the spam button.
- Copy and framing. Real but smaller. Misleading subject lines and false familiarity convert curiosity into irritation.
The ordering matters because teams work it backwards. Rewriting copy is the most visible thing to do and the least effective. Cutting a segment from 12,000 recipients to 900 feels like giving up and is usually where the complaint rate collapses.
Why verification helps a complaint problem
It sounds like a bounce fix, not a complaint fix. The link is that unverified lists are old lists. And old lists contain people who left the role, addresses converted into spam traps. And generic mailboxes where any commercial message is treated as spam by policy. In our verification data 23.9% of raw records are invalid outright and another 16.7% are catch-all. So 40.7% of the file is either dead or unconfirmable.
The unsubscribe paradox
Teams hide the unsubscribe link because every opt-out feels like a lost lead. The trade is terrible. An opt-out removes one contact from a list they were never going to buy from. A spam complaint damages delivery to every other recipient at that provider, including the ones who were interested.
Make the exit obvious and make it work in one click. The RFC 8058 header is what mailbox providers check, and Gmail surfaces it as a native button. So a link buried in the footer does not satisfy it.
Honor the request within 48 hours across every campaign and every mailbox, not just the one that sent the message. Suppression that lives inside a single campaign is how a prospect who opted out last month receives a fresh sequence from a different rep.
Containment: stop one segment from poisoning everything
Even with good process, some segment will eventually miss. The question is what that mistake costs, and the answer is architectural rather than tactical.
- Send outbound from dedicated domains, never the domain that carries invoices and support replies.
- Split volume across several mailboxes so one flagged mailbox does not stop the program.
- Run new segments at low volume first and read complaint data before scaling.
- Keep one segment per campaign so the complaint signal points at something specific.
- Suppress at send time, including customers, open opportunities and prior opt-outs.
The one segment per campaign rule is the cheapest diagnostic you will ever add. When four segments share a campaign you learn that something went wrong. When they are separate you learn which thing. Pair it with dedicated sending domains and the blast radius of any mistake stays small.
How many mailboxes, and how much per mailbox
Two or three mailboxes on each of two sending domains covers most small team volumes with room to spare. Keep each mailbox well under provider limits rather than at them: Google Workspace allows 2,000 messages a day and Microsoft 365 allows 10,000 recipients a day. But cold outbound at those levels is a reputation experiment, not a plan.
A conservative working figure is a few dozen sends per mailbox per day after warm-up. That sounds small until you multiply: six mailboxes at 40 a day is 7,200 sends a month. That is more than most teams can follow up on properly anyway.
Blast radius is how much of your sending infrastructure a single bad segment can damage, which is an architectural choice rather than a tactical one.
Recovering after you breach the ceiling
Recovery is slow, boring and mostly about volume discipline. There is no reset button, and anyone selling one is selling a new domain.
- Stop sending from the affected domain and mailbox immediately. Continuing while you investigate deepens the hole.
- Identify the segment that produced the complaints. Without one segment per campaign this step is guesswork.
- Remove that segment from the database, not just from the campaign.
- Re-verify everything still queued, because the complaint spike often coincides with stale data.
- Resume at roughly a tenth of previous volume and increase weekly while the rate stays flat.
- Expect several weeks before placement recovers, and treat that as the cost of the lesson.
Teams that skip the pause and simply switch to a new domain repeat the incident within a quarter. Because the cause travelled with the list rather than staying with the domain. The list is the thing to fix.
Sources and method
First-party data (Getlead, 2026): the verification split of 43.4% confirmed valid, 23.9% invalid, 16.7% catch-all and 16.0% unknown comes from 383,368 addresses analyzed through live SMTP verification. And the 0.51% bounce rate comes from 34,973 tracked sends. Both are aggregated and anonymized at campaign level, with the full method published in our cold email benchmark study.
External sources: the 0.3% spam complaint ceiling, the 0.1% recommended level and the reputation reporting available to senders (Google Workspace sender guidelines and Postmaster Tools, 2026); one click unsubscribe as specified in RFC 8058.
US commercial email obligations, including accurate headers, a physical postal address and a working opt-out honored within 10 business days, come from the FTC CAN-SPAM compliance guide.
Provider thresholds change without notice. Figures were checked in August 2026.
Frequently asked questions
What is a good spam complaint rate for cold email?
Under 0.1% is the operational target and 0.3% is the hard ceiling published for bulk senders. Because the rate is calculated on delivered messages, three complaints per thousand delivered puts you at the limit. And on smaller sends a single complaint can exceed it.
How do I check my spam complaint rate?
Register your sending domain in Google Postmaster Tools for Gmail traffic and Microsoft SNDS for Outlook traffic. Sending tools cannot measure complaints because the signal never leaves the mailbox provider. Both services are free and take under an hour to set up.
Does deleting an email count as a spam complaint?
No, only marking as spam or moving the message to the spam folder counts at most providers. Deleting without reading still hurts, because engagement signals feed placement decisions, but it does not enter the complaint rate directly.
What causes a high spam complaint rate?
Poor targeting first, stale list data second, over frequency third, and hard to find unsubscribe options fourth. Copy quality matters least of the five, which is why rewriting subject lines rarely fixes a complaint problem while cutting the segment usually does.
Can I recover from a spam complaint spike?
Yes, but slowly. Stop sending from the affected domain, identify and remove the segment that caused it, re-verify the remaining list, then resume at roughly a tenth of previous volume and increase weekly while the rate stays flat. Expect several weeks before placement recovers.
Is complaint rate more important than bounce rate?
They fail differently. Bounces are a data quality signal you can see immediately, and verified lists in our data bounce at 0.51%. Complaints are a relevance signal you can only see at the provider, and they carry a much lower tolerance, so they end programs faster.