Consent Mode v2 consultant (EU): CMP, GDPR compliance, modeled conversion recovery
EU Consent Mode v2 consultant: CMP choice (Axeptio, Didomi, Cookiebot, OneTrust), Basic vs Advanced, GDPR audit, modeled conversion recovery.
By Ron Kopelman, freelance analytics consultant — updated May 18, 2026
Google’s Consent Mode v2 has been mandatory since March 2024 for advertisers wanting to keep access to Google Ads remarketing, modeled conversions, and cookieless audiences. It’s not a marketing declaration — it’s a precise technical framework requiring the CMP, web and server-side GTM containers, and GA4/Ads/Meta tags to push gtag('consent', ...) signals at the right moment, in the right order, with the right categories. My role as an EU Consent Mode v2 consultant is to scope CMP selection, deploy a GDPR-compliant implementation, align legal documentation (LIA, processing register), and measure modeled conversion recovery in GA4 and Google Ads.
Why a poorly wired Consent Mode v2 costs you conversions
Four patterns recur on every site I audit.
The CMP never sends consent update signals. The banner appears, the user clicks, cookies drop — but the gtag('consent', 'update', {...}) that announces consent to Google never fires. Consequence: Google Ads sees all traffic in default “denied” mode, applies cookieless modeling, and loses precision on real conversions.
Basic mode chosen when Advanced was correct. Basic outright blocks Google tags before consent — no pings at all. Advanced lets degraded cookieless pings through that feed modeled conversions. On sites with cookie acceptance below 65%, Advanced typically recovers 8-18% additional conversions in GA4.
Inverted CMP ↔ Consent Mode mapping. The CMP has “analytics” and “marketing” categories but pushes analytics_storage when the user accepts marketing, and vice versa. Result: GA4 cookies don’t drop when they should, and ad pixels load when they shouldn’t.
Legal documentation doesn’t match technical reality. The processing register and LIA describe marketing cookies active after consent, but code loads them earlier. A GDPR audit or CNIL inspection reveals the divergence and triggers a notice.
Average recovery measured on the last dozen Consent Mode v2 missions: +12 to +28% Google Ads conversions in 30 days, just from realigning signals. Without changing the CMP. Without changing the acceptance rate.
Standard missions
1. Compliance audit
Complete diagnostic of an existing implementation: actually-sent gtag signals, CMP mapping, GA4/Ads/Meta tag firing, alignment with the processing register and LIA, conformity with latest CNIL guidance.
2. CMP selection and deployment
You’re on tarteaucitron and need to switch, or you’re starting a new site. I help you choose between Axeptio, Didomi, Cookiebot, OneTrust, or a custom solution, then deploy the GTM web + server-side integration.
3. Migration from tarteaucitron
Very common case: tarteaucitron has aged, has no official Consent Mode v2 support, and GDPR-sensitive sites want to upgrade. Migration to Axeptio (FR) or Cookiebot (EU) without service interruption, with consent history recovery when technically possible.
4. Basic vs Advanced arbitration
Short mission (2-3 days) to help you choose between the two modes. I model the gap of Basic vs Advanced on your real volumes, document GDPR implications, deliver a quantified recommendation. See basic vs advanced.
5. sGTM + Consent Mode integration
Advanced case: tracking is server-side, so consent signals must be managed at two layers (browser + sGTM) and events must be routed intelligently based on consent. The sGTM can filter what flows to Meta CAPI, Enhanced Conversions, or third-party platforms.
6. Legal documentation alignment
Often requested by DPO or legal teams ahead of a CNIL inspection. I write or review the LIA, align the processing register with technical reality, validate Data Processing Agreements.
Which CMP to choose in 2026
| CMP | Strength | Limitation | For whom |
|---|---|---|---|
| Axeptio | FR team, transparent pricing, modern UX, recognized banner ergonomics, TCF v2.3 | Less advanced reporting than OneTrust, fewer enterprise integrations | SMB, mid-market, premium FR/EU sites design-conscious |
| Didomi | Native TCF v2.3, exhaustive Google and IAB integrations, multi-brand governance, international compliance | Tier pricing escalates fast, dense admin interface | Groups, multi-brand media, multi-country retail |
| Cookiebot | European pioneer, automatic tracker scan, reasonable pricing, 35+ language support | Dated design, limited UI customization | Multilingual sites wanting a stable, low-touch solution |
| OneTrust | Global enterprise reference, governance integrations, complete audit trail | Setup complexity, high entry ticket, slow FR support | Listed groups, regulated sectors, global compliance constraints |
| tarteaucitron | Open source, free, FR community-rooted | No official Consent Mode v2 support, less active maintenance | Institutional low-budget sites, accepting limits |
For EU mid-market e-commerce and B2B lead gen, I recommend Axeptio in 60% of cases. For multi-brand groups, Didomi. For institutions tied to open source, tarteaucitron correctly maintained is a documented compromise.
Deployment method
- Tag and category mapping: GTM web + server-side inventory, classification of every tag by Consent Mode category.
gtagsignal configuration: from the CMP via dataLayer event → GTM-managedgtag('consent', 'update', ...).consent defaultimplementation: pushed at GTM initialization, before any other tag. Most commonly missed step.- Basic vs Advanced decision: based on acceptance rate, sector and Google Ads dependency.
- Strict acceptance testing: private browsing, consent accepted/refused, on critical journeys.
- Legal documentation aligned: LIA and processing register updated to match technical reality.
Fixed fees
| Mission | Scope | Fee |
|---|---|---|
| Compliance audit | Full diagnostic + prioritized action plan | €1,800 (~3 days) |
| Full Consent Mode v2 deployment | CMP choice + GTM integration + testing + legal alignment | €4,500 (~7 days) |
| tarteaucitron → commercial CMP migration | Choice + deployment + history recovery + testing | €3,800 (~6 days) |
| Basic vs Advanced arbitration | Modeling + quantified recommendation | €1,200 (~2 days) |
| Post-deployment monitoring | Monthly signal audit + compliance KPI | €600/month |
CMP fees billed directly to the vendor (€30-300/month Axeptio/Cookiebot, several thousand €/year Didomi/OneTrust enterprise).
Frequently asked questions
Is Consent Mode v2 mandatory?
Yes for Google Ads and Floodlight advertisers wanting to keep remarketing, custom audiences, and modeled conversions. For sites without Google paid media, not legally required but strongly recommended to preserve GA4 data quality in post-cookie environments.
What’s the CNIL position?
CNIL doesn’t ban Consent Mode v2 — it insists on freedom of consent, clarity of information, and equal ease of refusal vs acceptance. Sanctions in 2024-2025 targeted deceptive banners or hard-to-refuse flows, not Consent Mode usage itself.
Can I keep tarteaucitron?
Yes technically, by manually adding Consent Mode v2 on top (tarteaucitron has no native support). Feasible and I do it for institutional sites, but requires maintenance and CNIL increasingly recommends CMPs with audit trail. For commercial sites, I recommend migrating.
How long does deployment take?
1-2 calendar weeks for standard deployment (5-7 consulting days), plus 30 days observation to measure Google Ads/GA4 conversion impact.