Entry offer · Consent · GDPR
Consent Mode and GDPR tracking for ecommerce stores
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.
Consent Mode setup at a glance
- Service
- CMP wired to the container, tag behaviour verified in every consent state
- Price
- from $300, quoted before any work starts
- Covers
- CMP integration, Consent Mode signals, tag behaviour per state, verification
- Platforms
- Shopify, WooCommerce, Google Tag Manager, Cookiebot and similar CMPs
- You get
- Analytics and advertising tags that behave correctly whether consent is granted or declined
- Not included
- Legal advice on what your business is required to ask for
What usually breaks when consent is added
Consent problems tend to surface either as a legal risk or as a hole in the data. Usually both.
What the consent work covers
How it runs
What a Consent Mode setup costs
- 01
Access
GTM, GA4, ad accounts, CMP admin and the site.
- 02
Audit
We record current tag behaviour in every consent state.
- 03
Implement
CMP integration, Consent Mode signals and tag conditions.
- 04
Verify
Each state retested, results written up, handed over.
FAQ
Consent Mode and GDPR tracking questions
What is Consent Mode?
It is the signal layer between your consent banner and your Google tags. Instead of removing tags when someone declines, it tells them to behave differently. Tags that are simply deleted on decline and tags that are told to respect a declined state produce very different reports.
Do I need Consent Mode if I already have a cookie banner?
A banner collects the choice. Consent Mode is what carries that choice to the tags. Many stores have the first without the second, which is why their tags keep firing exactly as before.
Which CMP should I use?
Whichever one you already have, provided it can emit consent signals to the container. Cookiebot and comparable services do. We integrate the one you run rather than moving you to a different vendor.
Will my analytics data drop after consent is implemented?
Reported numbers usually fall, because part of your traffic was being measured without a basis for it. The figures you see afterwards are the ones you can actually stand behind.
How do you verify it works?
We test each consent state and record what fires and what does not in each one. Granted, declined and no choice yet are three different states, and a setup that handles two of them is the one that fails an audit.
Does this cover GDPR compliance?
It covers the technical half: making your tags behave according to the consent you collected. What your business is legally required to ask for, and how, is a question for your counsel. We implement the decision rather than make it.
Does consent affect Google Ads and Meta too?
Yes. Advertising tags sit under the same signals as analytics tags, and conversions collected without the right consent state cause problems further down the line. We check both in the same pass.
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 deploys in about a week: validated tracking, all ad spend joined to revenue in your own BigQuery, standard dashboards and conversational analytics.
Describe your consent setup
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.