Two numbers, both a percentage of a list, both used to judge a sender - and they are produced by completely different events.
A bounce is a machine telling you a mailbox cannot receive your mail. A complaint is a person pressing a button that says your mail was unwanted. Only one of them can be fixed by verifying addresses.
The two mechanisms side by side
| Bounce rate | Complaint rate | |
|---|---|---|
| Who produces it | The receiving server, automatically | The recipient, deliberately |
| What it is about | Your list data - the address stopped working | Your message - the person did not want it |
| What lowers it | Fresh data and a probe at send time | Relevance, consent, frequency |
| Can verification fix it | Yes - that is what probing is for | No - a verified address can still complain |
| Published guidance | 2-5% for checked contacts vs 10-35% for static resold databases | Gmail: keep below 0.10%, never reach 0.30% or higher |
The complaint figures come from Gmail's email sender guidelines: bulk senders are asked to keep the user-reported spam rate in Postmaster Tools below 0.10% and to prevent it from reaching 0.30% or higher. Since June 2024, senders above 0.30% are ineligible for mitigation, and eligibility returns after seven consecutive days below that line.
Why the numbers are not comparable
They differ by two orders of magnitude. A list with 4% bounces is ordinary and fixable. A complaint rate of 0.3% is a deliverability incident. Treating one as if it were the other is how a team ends up relaxed about the wrong metric.
The denominators differ. Bounces are measured against your send volume. Complaints are measured against mail that reached the inbox, which means the rate goes up when your mail gets through - not when it fails.
Bounces are decay, complaints are judgement. 23% of contacts change jobs annually (ZoomInfo, 2025) and 40% of email addresses are dead within two years (NeverBounce), so some bounce volume is guaranteed even with a perfect list. A person who marked you as spam yesterday does not become a fan today.
Relevance is not a list property. 42% of B2B data goes stale within a year (Harvard Business Review, 2024), but no amount of freshness stops an unwanted send to a live, verified address.
What verification actually buys you
Verification removes the noise that makes the second number unreadable.
A list full of dead addresses produces bounces and zero engagement. Dead rows are exactly where an unwanted send is cheapest to make and hardest to notice: nobody complains about mail they never received, and nobody replies to it either. Clearing them means the addresses you do send to are the ones that can respond - so the signal you get back is about your message rather than about your data.
Verification does not buy you the right to send. Existence is not interest.
The practical split
- Probe at send time, not on a schedule. Deliverable is a statement about now, with a date attached.
-
Do not treat a verified address as consent. The three honest states are deliverable, undeliverable, and
unknownfor catch-all domains. All three are about mailboxes. - Keep one-click unsubscribe and honour it fast. Gmail's guidelines make it a requirement for bulk senders; a complaint is what someone does when leaving is harder than reporting.
- Watch both numbers on separate surfaces. Postmaster Tools reports spam rate and reputation; your pipeline reports bounces. Neither replaces the other.
- Send less when the complaint rate rises. Google documents up to seven days for a spam rate to recover after fixes, and more volume during a spike makes the hole deeper.
TAPAC probes the mailbox inside the search that found the contact and returns deliverable, undeliverable or unknown, plus the time of the probe and the source page or profile the address came from. Checked contacts carry a published 2-5% bounce rate against 10-35% for static resold databases, on pay-per-use pricing of $0.10-0.50 per contact with 100 free searches.
For the complaint rate there is no equivalent shortcut. That is the point: verification fixes the list, and only relevance fixes the complaints.
npx -y @tapacapi/mcp # tools: tapac_find_contacts, tapac_status
# hosted: https://tapacapi.com/mcp
# REST: POST https://tapacapi.com/v1/contacts/search
Top comments (0)