Example incident · sample data

Gmail complaint spike

Data through 6 AprilView all sends

Worked example. This incident shows the evidence format with sample data. Your real incidents appear under Incidents.

Open incident

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.

Identified

Campaign: “Your profile qualified”

Campaign · Sent 5 Apr at 09:02 · Klaviyo ID 01HTQV7J4S8NCZ2A9YF4

Open in Klaviyo

Exact 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.

Feedback-ID token01HTQV7J4S8NCZ2A9YF4

Google FBL ratio0.47%

Audience42,180 profiles

Show raw evidence

source: google_postmaster.trafficStats
domain: northstargoods.com
date: 2026-04-05
spammyFeedbackLoops[0].id: 01HTQV7J4S8NCZ2A9YF4
spammyFeedbackLoops[0].spamRatio: 0.0047

resolution: exact_object_id
klaviyo_object.type: campaign-message
klaviyo_object.parent_campaign: "Your profile qualified"
calibration_version: v1 (verified 2026-03-28)

Likely

High Intent Flow · Email 1

Flow message · Sent 5 Apr at 11:18 · Klaviyo ID Qx7m2P

Multiple 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.

Timing2h 16m after campaign

Audience3,941 profiles

Evidence gapNo published FBL ID

Competing explanations

Signals checked before naming a send

DKIM, DMARC and encryption stayed stable

No authentication movement explains the complaint increase.

No unusual delivery-error increase

Deferrals and rejections remained inside the 30-day range.

Audience quality remains a possible shared factor

Both sends included profiles outside the recent-engagement segment.