Spam complaints plotted over time. This is the most reputation-sensitive line you have: the thresholds that mailbox providers enforce are tiny, so even a small upward drift is serious.
At a glance
The time-series of spam complaints across the selected period, where a complaint is a recipient marking your email as junk. This is the single most reputation-sensitive deliverability signal, because the thresholds mailbox providers enforce are extraordinarily low: major providers such as Gmail and Yahoo expect bulk senders to stay well under a 0.3% complaint rate and to treat 0.1% as the line you should never approach. That low ceiling is why this card uses a trend, not just a rate: a complaint line drifting upward, even by amounts that look trivial, can be the difference between landing in the inbox and landing in spam. A rising trend almost always traces back to consent, relevance, or cadence: people complain when they did not expect the email, do not find it relevant, or are getting too many. Treat any sustained climb here as urgent, well before it shows up as a deliverability drop.
| What it counts | The count of spam complaints per period bucket, plotted as a line over the selected window. |
| API endpoint + statistics field | POST /api/campaign-values-reports and POST /api/flow-values-reports, returning the spam_complaints statistic (with spam_complaint_rate available) per bucket. |
| Email vs SMS aggregation | Email only. SMS complaints and opt-outs are handled through carrier and consent mechanisms, tracked separately under the SMS channel. |
| MPP impact | None. Apple Mail Privacy Protection inflates opens, not complaints, so this line is unaffected by MPP. |
| Chart type | Line. |
| Time window | 30D vsP |
| Alert trigger | Any sustained upward movement in spam complaints, given how low the provider thresholds are, which signals consent, relevance, or cadence problems and real reputation risk. |
| Roles | owner, marketing |
Calculation
Calculated automatically from your Klaviyo data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
An illustrative food brand that raised its send cadence and re-engaged a long-dormant segment in the same fortnight. Reading the dashboard on 14 Apr 26 for the trailing 30 days (14 Mar 26 to 12 Apr 26), the spam-complaint line by week looks like this (illustrative figures):| Week | Delivered | Spam complaints | Complaint rate |
|---|---|---|---|
| 14-20 Mar 26 | 90,000 | 18 | 0.02% |
| 21-27 Mar 26 | 91,000 | 19 | 0.02% |
| 28 Mar-3 Apr 26 | 92,000 | 64 | 0.07% |
| 4-12 Apr 26 | 93,000 | 93 | 0.10% |
- The numbers look small but the trend is alarming. Going from 18 to 93 complaints a week is a roughly fivefold rise, and the rate reaching 0.10% touches the threshold mailbox providers treat as a red line. Small absolute numbers, serious signal.
- The trend matters more than any single day. A single complaint is noise; a line climbing week after week is a pattern. This card exists precisely to catch that drift while the absolute numbers still look reassuringly low.
- The cause is usually consent, relevance, or cadence. The rise here coincides with a higher cadence and a re-engaged dormant segment, which is the textbook recipe: people who had forgotten they subscribed, hit more often, are the most likely to click the spam button.
- Complaints are heavier than unsubscribes. An unsubscribe is a clean exit; a spam complaint actively tells the mailbox provider your mail is unwanted, which damages reputation far more. A rising complaint trend can suppress inbox placement for your entire list, not just the complainers.
- The fix is to pull back and re-permission. Slow the cadence to the dormant segment, send a sunset or re-permission flow, and remove anyone who does not re-engage. Watch this line alongside Unsubscribe Rate; a healthy correction often shows complaints falling as unsubscribes briefly rise, which is the right trade.
Sibling cards merchants should reference together
Spam Complaint Trend is the most reputation-sensitive line. Pair it with these:| Card | Why pair it with Spam Complaint Trend |
|---|---|
| Spam Complaint Rate | The proportion behind the line. The trend shows direction; the rate shows where you sit against the 0.1% and 0.3% thresholds. |
| Sender Reputation Risk | The composite warning. Complaints are one of the heaviest inputs to a reputation-risk flag. |
| Deliverability Drop | The downstream consequence. A rising complaint trend is one of the surest precursors to inbox placement falling. |
| Unsubscribe Rate | The cleaner exit. Encouraging unsubscribes over complaints is the right trade, so watch them together. |
| Email Health KPIs | The deliverability dashboard. Complaints sit alongside bounces and delivery as a combined health read. |
| Bounce Trend | The companion hygiene trend. Rising complaints and rising bounces together is a strong combined warning. |
Reconciling against Klaviyo
Where to look in Klaviyo:- Klaviyo → Analytics → Performance, then the spam-complaints or complaint-rate metric over time.
- Klaviyo → Campaigns and Klaviyo → Flows, then a specific send’s analytics, where complaints are broken out per send.
- Klaviyo → Analytics → Deliverability, for the reputation context and provider-level signals behind a rising line.
| Reason | Direction of divergence |
|---|---|
| Provider feedback lag. Complaints arrive via mailbox-provider feedback loops, which report on a delay. The most recent bucket can under-count until complaints finish landing. | The latest bucket reads low until feedback arrives. |
| Time zone. Vortex IQ buckets by UTC day; Klaviyo uses your account time zone. A complaint near midnight can fall into a different period. | Either direction, usually marginal. |
| Not all providers report. Only providers with feedback loops report complaints, so true complaints to non-reporting providers are invisible on both sides. | Both read low versus reality. |
| Campaign plus flow scope. This card blends campaigns and flows. A campaign-only view will read lower. | Ours reads higher than a campaign-only view. |
| Page caps. Values reporting pages at 50 records per pull, so very high send volumes can see slight aggregation truncation. | Ours can read marginally low for heavy senders. |