0.47%
User-reported spam rateAbove Google's 0.3% limitGmail complaint diagnosis for Klaviyo
Your Gmail spam rate spiked. Klaviyo says everything is fine.
SpamSpike joins Google Postmaster and Klaviyo, names the send behind the spike, and hands you the evidence plus the three moves to make before you send again.
Read-only connections No inbox access No individual complaint data
Nnorthstargoods.com Open incident
0.5%0.3%0.1%0.47%
7 Jan8 Mar6 Apr
Gmail user-reported spam · last 90 daysComplaints rose after two high-intent sends.
Identified
“Your profile qualified”Campaign · exact Feedback-ID match · 5 Apr
Likely
High Intent Flow · Email 1Timing and audience-risk match · 5 Apr
01Pause the repeated angle02Narrow the Gmail audience03Reset the expectation in copy
Narrow read-only scopes Credentials encrypted at rest Evidence strength always visible
Same day. Two completely different stories.
Google publishes one aggregate spam number per day. Klaviyo keeps reporting near-zero complaints. Between those two dashboards sits the question that decides your next send: which message did this?
0.01%
Reported complaint rateLooks fineGmail users report spam to Google, not to Klaviyo. Only Postmaster sees it, and only as one anonymous daily number. SpamSpike exists to close that gap.
Spam checkers score the message you have not sent.
Pre-send tools grade a hypothetical. They cannot explain the incident already sitting in your Postmaster account.
SpamSpike investigates the incident you already have.
It joins Google's complaint signal to the campaigns and flows you recognise, and shows how strong the evidence is at every step.
From “something is wrong” to “here is what we change.”
Connect the evidence.
Google Postmaster's daily signals on one side. Your Klaviyo campaigns and flow messages on the other.
Map the likely source.
Feedback-Loop tokens are matched to exact Klaviyo IDs first. Weaker candidates stay clearly separated.
Act before the next send.
Evidence strength, competing explanations, and three prioritized actions, each with an owner.
Clear about what the data can prove.
Every candidate is labelled Identified, Likely or Possible. Missing data is named as missing, never presented as “everything is fine.”
Aggregated and delayed
Postmaster publishes daily account-level signals, not a real-time complaint feed.
Thresholds apply
Feedback-Loop IDs appear only when Google has enough traffic and distinct reports.
No recipient identities
SpamSpike cannot identify the Gmail user who complained.
Your sending tools stay read-only.
The first version cannot send, edit, suppress or pause anything in Klaviyo.
- Google Postmaster read access only
- Klaviyo campaign and flow reads only
- Credential encryption at rest
- Immediate revoke and delete-data controls
- Confidence labels on every conclusion
One focused investigation. Not another subscription.
We map the signals, name the strongest contributors, show the evidence and give you a prioritized recovery plan.
See pricing and scopeStraight answers before you connect.
Can you always identify the exact campaign?
No. Exact mapping depends on Google publishing a usable Feedback-Loop identifier that contains a Klaviyo ID. Otherwise SpamSpike shows lower-confidence candidates, labelled as such, and says so. Header calibration for exact flow mapping is planned but not live yet.
Do you need my Gmail inbox?
No. SpamSpike connects to Google Postmaster Tools, not your mailbox. It cannot read email or identify who complained.
Will you change my Klaviyo account?
No. The first version is read-only. It cannot send, edit, suppress or pause campaigns or flows.
Stop guessing which send did it.
Connect the evidence before the next campaign goes out.
Investigate my spike