Skip to main content
Question

Popup not triggering in incognito (Chrome) but works in Safari — desktop only issue?

  • April 1, 2026
  • 3 replies
  • 18 views

Forum|alt.badge.img

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

3 replies

Byrne C
Community Manager
Forum|alt.badge.img+28
  • Community Manager
  • April 2, 2026

Hi ​@patrickdelehanty,

Thanks for the detailed breakdown of the issue you’re facing. Our support team is still looking into this, and will be back in touch with you soon, and we encourage you to continue working with our team on this ticket!

That being said, if any other community members have experienced this issue, and have found a solution, don’t hesitate to share what you’ve found/how you’ve dealt with this!


ArpitBanjara
Principal User II
Forum|alt.badge.img+37
  • Principal User II
  • April 2, 2026

Hey ​@patrickdelehanty 

Difficult to detect without seeing this closely,

I would start checking/digging from here:

Check if the Klaviyo script is even loading in Chrome incognito. Open your site in Chrome incognito, then open DevTools (F12) and go to the Network tab. Filter by "klaviyo." If you see the script being blocked, cancelled, or returning an error, that's your culprit. Safari handles privacy restrictions differently and is generally more permissive about first-party scripts, which would explain why the form fires there but not in Chrome.

Also check if a consent management tool misfiring. If you added or updated something like OneTrust, Cookiebot, Consentmo, or even touched Shopify's Customer Privacy settings around BFCM, Chrome incognito tends to apply those restrictions harder than Safari does. Klaviyo's script powers both tracking and signup forms, so if a consent tool blocks it before the visitor interacts, the form simply never loads, even forms that don't need tracking to display. Klaviyo article on this

Also worth a quick check: view your page source and search for company_id. More than one API key on the page causes exactly this kind of inconsistent behavior. Someone answered this here

I hope this helps and thank you for sharing your question here in the community. Let us know what support replies you with.

Cheers.

Arpit


Forum|alt.badge.img

Hey  ​@ArpitBanjara 

This is great, thank you so much!

Line by line.

  1. I went into Network for Dev Tools, found this. You’ll see first the image shows a 200 OK and then the next line / image shows a 304 Not Modified - is this the issue?
  2. I’ll need to check on this but I’m sure did not have any major changes at that time.
  3. We only have one company_id in our code so I think we’re good there.

Again, appreciate your help here!