Audit the current state
Whether Consent Mode is installed at all, and if so, whether the signals are mapped correctly.
Reporting & Compliance
Stop losing EEA traffic to a missing signal
Required for EEA traffic since March 2024, and easy to configure wrong. We map your consent banner to Google's signals correctly, so declined consent gets modeled instead of just vanishing.
Trusted by
The Mercer Brand
Fugazzi
Barista Essentials
Lensvelt
Coco & Sebas
The Mercer Brand
Fugazzi
Barista Essentials
Lensvelt
Coco & Sebas
What it costs you
What a missing consent signal actually costs
The damage doesn't show up as an error message. It shows up as EEA traffic that quietly stopped existing in your reporting.
01
Declined consent means invisible, not just untracked
Without Consent Mode wired up, a visitor who declines cookies disappears from conversion reporting entirely, not just from remarketing lists.
02
Signals mapped to the wrong category
A default implementation guesses at how your CMP's categories map to Google's signals, and that guess is wrong more often than accounts realise.
03
GA4 and Ads quietly disagree
Two different consent configurations drifting apart over time means GA4 and Ads eventually disagree about the very same visitor.
The fix
What we set up
A handful of consent signals, mapped correctly between your CMP and Google's tags, then verified — not just switched on and assumed to be right.
01
Consent Mode v2 signals installed
ad_storage, analytics_storage, ad_user_data and ad_personalization, all four wired in properly instead of a partial implementation that only covers analytics.
Deliverable: CMP & consent audit
02
Mapped to your CMP's real categories
Matched to how your consent platform's categories actually work, not the default guess most implementations ship with and never revisit.
Deliverable: Consent Mode v2 configured
03
Basic or advanced implementation
Whichever your CMP actually supports, chosen deliberately rather than defaulted to whatever a plugin happened to install first.
Deliverable: Implementation chosen & verified
04
Modeled conversions verified
Checked that declined-consent traffic is actually populating modeled conversions, not just assumed to be working because the tag fired.
Deliverable: Modeling verified
05
GA4 consent aligned
GA4's own consent settings aligned to the same signal set as Ads, instead of drifting apart as two separately configured systems.
Deliverable: GA4 alignment checked
06
Checked against Google's diagnostics
Verified through Google's own consent diagnostics tooling before we call it done, not left as a setting nobody ever confirmed was working.
Deliverable: Compliance documentation
Process
How the setup runs
Map consent signals
Your CMP's categories connected to Google's consent parameters, matched to what they actually mean.
Verify modeling
Checked that declined-consent traffic is being modeled, not just dropped from reporting.
Document and hand over
A written record for your own compliance file, not just a setting nobody can explain later.
What clients say
Don't just take our word for it
We'd turned on Consent Mode ourselves using the plugin defaults and EEA traffic basically vanished from reporting overnight. Mapping it into the account properly recovered most of that volume within the modelled numbers.
Our consent signals had been mapped to the wrong categories since the CMP was installed two years ago. Nobody had ever checked, because the banner itself looked fine to every visitor.
GA4 and Google Ads had been configured with two completely separate consent setups for years. Aligning them to one signal set closed a gap our finance team had been quietly working around.
We only had basic Consent Mode installed and had no idea advanced modeling existed. Switching to it recovered a meaningful share of the EEA conversions we'd been missing for over a year.
Our legal team flagged that we needed Consent Mode v2 and we had no idea where to start. Having someone document exactly what was configured and why made our compliance review painless.
We'd assumed our developer had already handled Consent Mode when the new banner launched. An actual check found the signals were only partially wired up, and analytics_storage had been ignored the whole time.
We switched CMPs last year and nobody remapped the consent signals to the new platform's categories. Six months of EEA data had been quietly wrong before anyone noticed the drop.
We assumed our developer had wired up Consent Mode when the banner shipped two years ago. An actual check found it had never been connected to anything — the banner just sat there doing nothing.
Consent rates on our banner looked healthy, so we assumed the downstream setup was fine too. The gap wasn't the banner at all — it was what happened, or didn't happen, after someone clicked it.
Questions
Common questions
Do we need this if most of our traffic isn't in the EEA?
Google's requirement applies to any EEA traffic your account serves, even if it's a small share. It's worth configuring even for a small percentage.
Which consent platforms do you support?
Any CMP that supports the Google Consent Mode API — that covers most major platforms, including Cookiebot, OneTrust and Complianz.
Is this a legal compliance service?
No — we configure the technical implementation correctly. Whether your consent banner itself meets your specific legal obligations is a question for your legal counsel.
What happens if we switch CMPs later?
The signal mapping needs to be redone against the new CMP's categories — usually a short piece of work rather than a full rebuild.
Start here
Find out what your account is actually reporting
Send us access and we will come back with a written audit: what is tracked, what is double-counted, what is missing, and what we would change first.
No pitch deck · No lock-in · Findings are yours either way