Hi team,
We’re (LookOurWay) seeing a pretty significant issue with our Klaviyo signup popup not consistently triggering, and trying to narrow down whether this is a targeting, script, or browser-related issue.
Here’s what we’re seeing:
- Popup is set live and appears configured correctly in Klaviyo
- Not triggering in incognito (new session) on Chrome (desktop)
- Does appear in Safari incognito
- Mobile performance seems to have recovered, but desktop has not
- Even after navigating multiple pages (trigger is set to show after 2 page views), it still doesn’t appear in Chrome incognito
- Submit rate dropped significantly post-BFCM (late Nov / early Dec) and has not fully recovered
We’ve already:
- Confirmed the form is live
- Reviewed targeting and triggers at a high level
- Escalated to Klaviyo support
Given the browser-specific behavior (Chrome vs Safari) and desktop-only inconsistency, it feels like this may be:
- A script not firing correctly in certain environments
- Cookie/session or suppression logic behaving differently in Chrome
- Or a frontend conflict impacting popup rendering
Has anyone seen something similar, or have recommendations on what specifically to check next (especially around Chrome behavior, scripts, or targeting conditions)?
Thanks so much!
Patrick // LookOurWay
