Entry offer · Consent · GDPR

Consent set up so that analytics and ads both behave correctly

A banner on the page is not consent management. We integrate your CMP with Consent Mode, make tags respect the actual consent state, and verify what fires — and what does not — in each case.

Fixed scope, quoted before we start · from $300
CMP wired to Consent Mode v2Tags respect the real stateEach state verified separately

What usually brings people here

Consent problems tend to surface either as a legal risk or as a hole in the data. Usually both.

A cookie banner is on the site, but tags fire regardless of what the visitor clicks
Consent Mode v2 required by the platforms and not implemented
Analytics traffic collapsed after the CMP went live and nobody knows what is normal
Cookiebot or a similar CMP installed but never connected to GTM
No idea which tags fire in the denied state
EU traffic reporting in a way the rest of the account cannot explain

What the work covers

CMP integrated with GTMYour consent platform wired into the container properly, not bolted on beside it.
Consent Mode v2Analytics and advertising consent signals implemented in the form the platforms now expect.
Tag behaviour per stateEvery tag reviewed against granted and denied states, so nothing fires where it should not.
Regional configurationConsent behaviour scoped to the regions that require it, rather than applied blindly everywhere.
Verification in each stateWe test granted, denied and no-interaction separately and record what actually happens.
Written summaryWhat was changed, what fires when, and what your team should watch afterwards.

How it runs

Four steps, one fixed price

  1. 01

    Access

    GTM, GA4, ad accounts, CMP admin and the site.

  2. 02

    Audit

    We record current tag behaviour in every consent state.

  3. 03

    Implement

    CMP integration, Consent Mode signals and tag conditions.

  4. 04

    Verify

    Each state retested, results written up, handed over.

from $300Consent Mode setup
Describe your case
  • Fixed scope agreed in writing first
  • CMP to GTM integration
  • Consent Mode v2 signals
  • Tag behaviour per consent state
  • Regional configuration
  • Verification and written summary

This is technical implementation, not legal advice. We make the tracking behave the way your consent policy says it should — deciding what that policy is remains with you and your counsel.

FAQ

Before you send accesses

Does this make us GDPR compliant?

It makes your tracking behave according to the consent your visitors give. Compliance also depends on your policies, your banner wording and your legal basis, and those are not ours to sign off on. We will flag anything that looks obviously wrong, but we are engineers, not lawyers.

Will our analytics numbers drop?

If tags were firing without consent, then yes — you will see the true consented volume rather than an inflated one. Consent Mode modelling recovers part of the gap in Google’s reporting. We would rather you know the real number than a comfortable one.

Which CMPs do you work with?

Cookiebot and the other mainstream platforms that expose a proper GTM integration. If you are using something unusual, send us the name and we will tell you before quoting whether it can be wired up cleanly.

Can you do this alongside Conversion API?

Yes, and it is often the right order: get consent behaving correctly first, then build server-side tracking on top of it. Otherwise you are sending server events on a basis nobody has verified.

If the whole stack needs standardising

A single fix stays a single fix. But if the analytics underneath turns out to be worth rebuilding, the full system — validated tracking, all ad spend joined to revenue in your own BigQuery, standard dashboards and conversational analytics — deploys in about a week.

Describe what you are seeing

Send the symptom, the platform and a screenshot if you have one. We come back with what we think is happening, what it would take to fix, and a fixed price — before any work starts.