Consent Mode v2 & CMP implementation (Cookiebot, CookieHub, Cookie-Script)
Stay GDPR-compliant in how you handle cookies. Keep Google Ads and Meta bidding algorithms effective without breaching user privacy.
Book a free 30-min consultationWhy Consent Mode v2 is mandatory
Consent Mode v2 is required for advertisers targeting users in the European Economic Area. Without correctly configured ad_user_data and ad_personalization parameters you cannot build remarketing audiences, and Smart Bidding in Google Ads loses much of its effectiveness.
Basic Consent Mode
Ad tags are fully blocked until consent is given. Maximum privacy, no pings without consent.
Advanced Consent Mode
Sends anonymous, cookieless pings. Lets Google model conversions when consent is not given.
Supported CMP platforms
Which consent problems have I solved for clients?
Most often the cookie banner “almost” works: it blocks scripts but does not enable them after consent, breaks the purchase path or fires tools before consent. Here are five such situations from my projects. Some descriptions are anonymised, because I also work white-label for agencies and under NDA.
B2B · industrial · Cookie-Script
The banner blocked LinkedIn but never enabled it after consent
After migrating to a new website, Cookie-Script behaved inconsistently and GA4 was missing data. I scanned the cookies, set up conditional script loading by consent category and implemented GA4 with Consent Mode.
Result: Scripts load only after consent, and always after consent. No manual admin intervention.
Read the case study →FinTech · insurance calculator
A banner conflict stopped customers halfway through the calculator
Cookie banner conflicts stopped some users in the calculator and held back remarketing tags. I integrated the CMP with GTM and Consent Mode v2 and removed the UX conflicts along the path.
Result: An error-free path, tags firing according to the user’s choice and a step 1 to 4 funnel visible in the dashboard.
Read the case study →MedTech · Shopify + app · StethoMe
One consent for the domain and the subdomain
The Shopify store and the app dashboard ran on a domain and a subdomain, and a medical app required extra care with data. I configured Consent Mode so that one consent applies in both places.
Result: Users click the banner once, and analytics has been GDPR-compliant from day one.
Read the case study →E-commerce · Poland and Germany
Faulty Consent Mode in a store serving two markets
A store on .pl and .de domains had a faulty Consent Mode setup and a GTM container full of unexplained tags. As part of the audit I fixed the consent implementation and split the data into two GA4 properties.
Result: Correct consent signals in both markets and Google Ads campaigns optimised separately for Poland and Germany.
Read the case study →Consulting · UX · Microsoft Clarity
Heatmaps stopped working after Consent Mode went live
Clarity used to record users before consent, and after Consent Mode was implemented it stopped collecting data. I connected Clarity to the client’s consent banner and moved the script into GTM.
Result: Recordings and heatmaps work again, but only for people who consented.
Read the case study →More examples from GA4, GTM, Meta CAPI and Firebase: all case studies.
Not sure your cookie banner works correctly?
I will run a quick check of how your consent signals are passed. Consent Mode implementation from €225 excl. VAT for simple websites.
Check your Consent ModeLet’s talk about your tracking.
A free consultation: you tell me what is not working, and I tell you where I would start.