Fix GA4, GTM and Cookie Consent Tracking Issues

@shobha1987

Hi - I think Cookiebot's auto-blocking is your root cause, not Consent Mode itself. That type="text/plain" data-cookieconsent="statistics" on the GTM container usually isn't hand-written - it's Cookiebot's automatic cookie blocking rewriting the tag. So GTM never executes before consent, and if GTM never executes, Consent Mode never gets the chance to send its cookieless pings. That's your 97%. Cookiebot's recommendation is right, but order matters more than people expect: the consent default snippet (analytics_storage, ad_storage, ad_user_data, ad_personalization all denied) has to run before Cookiebot loads, then Cookiebot, then GTM unblocked. And it has to be Advanced Consent Mode - in Basic, tags simply don't fire pre-consent, which is exactly what you're seeing. The invalid data-cookieconsent="necessary" goes too. One thing I'd rather say now than after you've paid: even done perfectly, your numbers won't return to the old opt-out levels. Advanced mode sends cookieless pings and GA4 fills gaps with behavioural modelling, but modelling only starts once you clear Google's daily thresholds. Expect a large recovery, not a full one. I'd validate both paths - consented and not - with Tag Assistant, GA4 DebugView and GTM's Consent Overview before signing off. Question: is automatic blocking switched on in your Cookiebot dashboard, or was that attribute added by hand? Rs 1,500, 2 days. Cheers, Shobha

@tyronet2

The key issue here is not whether GA4 works after consent—you have already confirmed that it does—but whether the current Cookiebot implementation is preventing GTM and Consent Mode from operating at all before consent. I can trace this at the JavaScript and network level, starting with script execution order, GTM Consent Initialization, Cookiebot callbacks, and the current type="text/plain" container blocking. I’ll verify analytics_storage, ad_storage, ad_user_data, and ad_personalization through each consent state, inspect the actual GA4 requests and cookies in DevTools, and validate behavior with Tag Assistant and DebugView. If container-level blocking is preventing the intended cookieless measurement, I’ll restructure the implementation so GTM can initialize correctly while consent controls determine what tags are permitted to do. I’ll then regression-test consenting and non-consenting journeys, UTM attribution, page views, and conversions, and document the root cause and final configuration clearly. Can you share the current GTM/Consent Mode snippets and Cookiebot configuration so I can review the execution flow first?

@rohank2502

Your site went opt-in and GA4 visibility fell ~97%. That is almost never lost visitors. It is tracking going dark until people click Accept. From what you already found, users who consent send page_view with UTMs intact, and everyone else sends nothing. I will confirm that on your live pages in a short screen recording before I touch anything. You get the miss shown, then a fix that restores measurement while people have not consented, and full tracking after they accept. Before/after on real sessions so you can see traffic again, not a guess. I do not claim a Cookiebot case file. You get the diagnosis on your site first, then the fix. Root-cause recording within 24 hours of GTM access and the live URL. Full repair inside 3 days once you approve the change. Share GTM access and the live URL and I start the recording today?

@sanket99799

Hi, I’m Sanket, a digital analytics specialist experienced with GA4, GTM, Cookiebot and Google Consent Mode. Your 97% drop in GA4 visibility clearly needs root-cause diagnosis rather than simply reinstalling tracking. I can audit the complete Cookiebot → GTM → Consent Mode → GA4 implementation and identify where measurement is being blocked. I can handle: • Audit GTM loading and Cookiebot consent configuration • Review Consent Mode v2 and Advanced Consent Mode • Validate analytics_storage, ad_storage, ad_user_data and ad_personalization • Test behaviour before and after consent • Verify cookieless GA4 signals when consent is denied • Inspect browser/network requests and JavaScript • Validate UTM attribution and campaign tracking • Implement the required fix • Test using Tag Assistant, GA4 DebugView and browser DevTools • Confirm normal tracking remains intact after consent I’ll reproduce the issue first, identify the exact cause, then implement the minimum necessary changes. I’ll also document what was causing the visibility loss, what was changed, and how the final setup was validated. My focus is restoring maximum legitimate analytics visibility while respecting the opt-in consent architecture. Regards, Sanket

@CliveMSoftware

I've debugged similar Cookiebot + GTM + GA4 setups where conditional container loading was blocking cookieless tracking. My approach: audit your current Consent Mode v2 implementation to verify consent states are properly declared, review GTM container loading sequence to ensure it fires before consent (removing the blocking type=text/plain attribute), validate that Advanced Consent Mode is enabled to send privacy-preserving signals for non-consenting users, and use Tag Assistant + DebugView to confirm GA4 receives events pre and post-consent. I'll identify whether the 97% drop is from GTM being blocked or Consent Mode misconfiguration, implement the fix, and validate that UTM attribution persists while respecting privacy. Ready to start immediately and deliver a fully tested solution.

@HectorCorporate

Your symptom points to a container-level block, not a GA4 config issue. With type="text/plain" + data-cookieconsent="statistics", Cookiebot stops GTM from executing before consent, so Consent Mode defaults never fire and no cookieless pings are sent — the ~97% gap is all non-consenting traffic. Plan: - Load GTM unconditionally; consent control moves into GTM/Consent Mode. - gtag consent 'default' = denied before the GTM snippet and before Cookiebot, with wait_for_update. - Advanced Consent Mode: url_passthrough + ads_data_redaction; remove the invalid data-cookieconsent="necessary". - Map Cookiebot categories to analytics_storage, ad_storage, ad_user_data, ad_personalization via consent 'update'. - Consent checks on GA4/Ads tags; confirm no cookies are set pre-consent. Validation: GTM Consent Overview, Tag Assistant, DebugView, and /collect network inspection (gcs G100 vs G111, gcd, dma) in denied and granted states, plus a UTM attribution regression check. Note: under opt-in, part of the gap returns as modeled data, not raw hits. Needed: GTM access and the ability to edit the head snippet.

@pratikpatel3675

Hi, A 97% drop after moving from opt-out to opt-in strongly suggests the Cookiebot + GTM + Consent Mode architecture is blocking analytics signals before consent. I would investigate the actual implementation rather than simply reinstalling GA4 or GTM. I would audit how Cookiebot loads GTM, the GTM Consent Overview, Consent Mode v2 defaults/updates, and the states of analytics_storage, ad_storage, ad_user_data, and ad_personalization. I would then test the site before and after consent using Tag Assistant, GA4 DebugView, browser DevTools and network requests to determine exactly what signals are being sent and whether GTM is being blocked at the container level. If Advanced Consent Mode is appropriate, I would implement it correctly while ensuring: Privacy-preserving signals before consent No unauthorized cookies or tracking Normal GA4 tracking after consent UTM/campaign attribution remains intact Existing conversion tracking continues working No regressions for consenting users I will also provide a clear explanation of the root cause, changes made, and validation results, rather than treating the issue with a generic tracking setup. I can start immediately.

@gopikasakthivel

Hi, I can help identify why GA4 tracking dropped after the Cookiebot consent changes. I’ll review the Cookiebot, GTM and Consent Mode setup, check the tracking before and after consent, find the root cause, and implement the required fix. I’ll also validate GA4 events, UTM tracking and consent behavior to make sure everything works correctly after the fix. I can start immediately and complete it within 1 day.

@VproTechDigital

Hi, I’m an experienced GA4, Google Tag Manager, Cookiebot, and Consent Mode specialist with hands-on expertise troubleshooting production tracking issues. I can audit your complete Cookiebot + GTM + GA4 setup, identify why analytics visibility dropped, and implement the correct Consent Mode v2 architecture. I’ll specifically review GTM loading, consent states, Advanced Consent Mode, cookieless GA4 signals, UTM attribution, and pre/post-consent behavior. I’ll validate everything using Tag Assistant, GA4 DebugView, browser developer tools, and network requests. My focus is finding the root cause—not simply reinstalling tags—and ensuring privacy compliance while restoring accurate analytics, attribution, sessions, and conversion tracking for consenting users.

@samana275

I have hands-on experience with GA4, GTM, Consent Mode, Cookiebot, and debugging production tracking. I can identify the root cause, implement the correct fix, and validate attribution end-to-end.