What Google contributes
- Daily user-reported spam ratio and confidence bounds
- Domain and IP reputation
- SPF, DKIM, DMARC and encryption ratios
- Delivery errors
- Spammy Feedback-Loop IDs and ratios when thresholds are met
How it works
Google sees the complaint. Klaviyo holds the send.
SpamSpike connects those two evidence sets, investigates the strongest candidates and keeps uncertainty visible from start to finish.
What Klaviyo contributes
- Campaign and campaign-message IDs
- Flow, flow-action and flow-message IDs
- Names, status, channel and update timing
- Campaign, message and flow relationships
- No profile, event or write access
Exact matches first. Correlation last.
The system never labels timing alone as the cause.
Connect Postmaster
Import verified domains, daily Gmail signals and Feedback-Loop identifiers when Google publishes them.
Connect Klaviyo
Index campaign, campaign-message, flow, action and flow-message IDs using read-only access.
Calibrate headers (coming soon)
Will compare known campaign and flow test headers with the Klaviyo IDs already imported. Not live yet.
Detect an incident
Find complaint spikes, reputation movement or meaningful compliance changes.
Map and investigate
Resolve exact identifiers first, then compare timing, audience and alternative explanations.
Act and monitor
Return three actions with an owner, then compare later readings with the incident baseline.
What the result means.
Plain labels replace made-up causal percentages.
Exact match
A Google token matches a Klaviyo object, or a pattern repeatedly proven from received headers.
Multiple signals
Send timing, unusual audience, Klaviyo movement and Postmaster changes align.
Timing only
A send occurred near the spike, but no strong identifying evidence connects it.
Map tokens. Never guess namespaces.
Match the Google token to an indexed Klaviyo object ID.
Use an account pattern only after repeated calibration proves its field position.
Resolve child objects back to the campaign or flow marketers recognise.
Leave unresolved tokens visible and use nearby sends as possible candidates only.
Important limit: SpamSpike cannot identify the Gmail user who complained. It investigates aggregated signals published daily, and only when Google's thresholds are met.
Connect the source that sees the signal to the source that knows the send.
Read-only. Revoke at any time.
Start the investigation