Audit of your current CMP
We review which Consent Management Platform you have (Cookiebot, OneTrust, Iubenda, Didomi, Usercentrics) and how it integrates with your measurement.
Since March 2024, Consent Mode v2 has been mandatory to use Google audiences and measure conversions reliably. We implement it correctly so you comply with European regulation without losing the ability to measure, optimize and scale your campaigns.
We implement every piece — CMP, GTM, GA4 and ad platforms — so consent is handled properly and your data still drives real decisions.
We review which Consent Management Platform you have (Cookiebot, OneTrust, Iubenda, Didomi, Usercentrics) and how it integrates with your measurement.
Correct configuration of the four signals: ad_storage, analytics_storage, ad_user_data and ad_personalization.
Activation of conversion modeling to recover conversions from users who reject cookies.
We make sure GA4 receives data correctly with and without consent, without distorting reporting.
So your campaigns keep optimizing with audiences and conversions properly declared, not blind.
Combination of both layers to minimize data loss without bypassing user consent.
Platform-specific implementation: WordPress, Shopify, PrestaShop, WooCommerce and headless setups.
Testing with DebugView, Tag Assistant and pre/post data comparison to make sure measurement is consistent.
European privacy regulation and the Digital Markets Act are no longer an intent: they're an obligation. And Google has made Consent Mode v2 the technical toll for keeping its ecosystem usable.
Without Consent Mode v2, you cannot activate custom audiences in the Google ecosystem. With it properly implemented, you keep retargeting and lookalikes alive.
Without Consent Mode v2, users who reject cookies are invisible to your measurement. With it activated and modeled, a significant portion of those conversions is recovered (rough figures from Google: between 30% and 70%).
A bad implementation can cause event duplication, contradictory data across platforms or total measurement loss. That's why audit and QA are core parts of the work.
Five steps so user consent and measurement work together, not against each other.
We review your CMP, GTM, GA4 and ad platforms to detect the current state of consent and measurement.
We define the consent model adapted to your CMS, tools and the project's legal context.
CMP, GTM, tags, events and the four Consent Mode v2 signals — all configured.
End-to-end testing with DebugView, Tag Assistant and the CMP's own tools. We don't sign off without validation.
Ongoing tracking of consent behavior, modeled data and the impact on campaign reporting.
We implement it in every Growzz project as part of the measurement foundation. See how it integrates in real strategies.
See case studiesConsent Mode v2 is not a checkbox: it's a piece that connects legal, technical and marketing. We implement it thinking about the real impact on your campaigns, not as paperwork.
Consent Mode v2 is a Google system that communicates the user's consent state (whether they accept advertising and analytics cookies) to Google platforms: GA4, Google Ads, Display & Video 360. Since March 2024 it is mandatory to use custom audiences and measure conversions completely in the Google ecosystem. Without it, the platforms lose the ability to optimize campaigns with European data.
With Consent Mode v2 properly implemented, not entirely. Google activates what's called "conversion modeling": it estimates what would have happened if those users had accepted cookies, based on the aggregate behavior of similar users who did. Without Consent Mode v2, users who reject cookies are invisible. With it, a significant portion of the data is recovered.
The major CMPs (Cookiebot, OneTrust, Iubenda, Didomi, Usercentrics and others) have native integration with Consent Mode v2. The important thing is not just that the CMP supports it, but that it is correctly configured and connected with GTM and GA4. We audit it on every project before proposing changes.
Yes, and combining them is the current best practice. Server-side reduces data loss caused by ad blockers and browser restrictions, and Consent Mode v2 handles the consent layer. We work both layers depending on each project's state.
Each project is analyzed individually. The proposal depends on your current CMP, the CMS, the complexity of the existing setup and whether it combines with server-side tracking. We work without lock-in and build the proposal after a first conversation.
Let’s talk about your business and build a clear plan to scale with data.