Guides › Wix, Squarespace & builders › Speed & performance

GA4 Stopped Tracking After Adding a Cookie Banner: Consent Mode Fix

Tracking often fails because the Google tag fires before the banner updates consent. Fix the order.

Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.

Symptom: you added or changed a cookie banner, and now Google Analytics shows far fewer visits or conversions, even though people click Accept.

What usually goes wrong

Google Consent Mode uses signals such as analytics_storage and ad_storage. If the default state loads too late, or the banner never sends an update after the visitor accepts, the tag runs as if consent was denied.

Check in this order

  1. Is the tag firing? Use Google Tag Assistant and the GA4 DebugView. See GA4 not tracking checklist.
  2. Default consent first. The default consent state (usually denied where opt-in applies) must be set before Google tags load. In Tag Manager, set it on the Consent Initialization trigger.
  3. Update on accept. After a click on Accept, the banner must send an update to granted. Check the consent state in Tag Assistant's Consent tab before and after.
  4. Tag order. The GA4 tag should wait for the consent setup, not run before it.
  5. No duplicates. Do not have both a hard-coded Google tag and Tag Manager sending the same events. See duplicate events.
  6. Right ID. Confirm the Measurement ID is correct.

Remember the limits

Some visitors reject cookies, and some browsers and extensions block tags, so analytics will always undercount. See why numbers are lower.

Related: cookie banner guide.

Related guides

Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.

Last updated 2026-11-21.