Example incident · sample data
Gmail complaint spike
Gmail complaints rose after two high-intent sends.
One campaign is identified by Feedback Loop data. One flow message is a likely secondary contributor. Authentication and encryption did not materially change.
Campaign: “Closing tonight”
Campaign · Sent 23 Aug at 09:02 · Klaviyo ID 01HTQV7J4S8NCZ2A9YF4Exact token match. Google published a spammy Feedback Loop identifier that matches this imported Klaviyo campaign. This proves an unusual complaint signal for traffic carrying the identifier. It does not prove this campaign explains every domain complaint.
Show raw evidence
source: google_postmaster.trafficStats domain: bramble.co date: 2026-08-23 spammyFeedbackLoops[0].id: 01HTQV7J4S8NCZ2A9YF4 spammyFeedbackLoops[0].spamRatio: 0.0047 resolution: exact_object_id klaviyo_object.type: campaign-message klaviyo_object.parent_campaign: "Closing tonight"
High Intent Flow · Email 1
Flow message · Sent 23 Aug at 11:18 · Klaviyo ID Qx7m2PMultiple signals, no usable identifier. Send timing, a high-intent audience and the message expectation align with the complaint window. This is a likely contributor, not an identified source.
No authentication movement explains the complaint increase.
Deferrals and rejections remained inside the 30-day range.
Both sends included profiles outside the recent-engagement segment.