Implementation recovery
Tobi.com Consent Mode Implementation: conversions started counting again
After GDPR cookie‐consent went live, Tobi.com saw an 80% drop in reported sessions—crippling their data-driven decisions. In just 5 days, we rolled out a manual gtag() consent mode via GTM, rebuilt the consent flow, and restored tracking accuracy and trust in their analytics.

What was broken
- 80% drop in sessions after cookie-consent rollout
- All tags blocked by default-deny mode
- No persistence of consent decisions across pages
What we rebuilt
- 01Manually set default deny state for ad_storage & analytics_storage
- 02Created robust consent update functions with dataLayer events
- 03Leveraged localStorage for decision persistence & auto-firing consent_updated
- 04Integrated consent banner UI with on-click handlers
What started working again
- Restored 80% of lost sessions within 30 days
- Reached 98% accuracy in session & event tracking
- Automated consent logic ensures GDPR compliance
- Marketing team regained full confidence in analytics data
“Hassan quickly fixed our consent‐mode setup and brought our session counts back from the brink. His documentation and QA gave us full confidence in our data again.”
WWinston Abiera
Head of Analytics
Delivery path
- 01
Default Consent State Setup
Injected gtag('consent','default',…) above GTM with ad_storage & analytics_storage denied by default
- 02
GTM Initialization & Consent Integration
Placed GTM container snippet below default-consent code and enabled url_passthrough
- 03
Consent Update Functions
Built updateConsent() & saveConsentAndApply() to push consent updates and 'consent_updated' events
- 04
Decision Detection & Banner Logic
Stored & checked user decisions in localStorage; fired consent_updated on page load if set
- 05
QA & Production Roll-out
End-to-end test of consent flow, tag firing, and dataLayer events across key pages
Stop another blind week
Phone ringing. Meta empty. Path clear after we name the restriction.