Tracking & data protection

Google Consent Mode & server-side tracking, set up for you

Without a properly configured consent signal, Google discards your advertising data – and your campaigns optimise into thin air. I set up Google Consent Mode, Tag Manager and server-side tracking on your website so that your figures are right and data protection rules are met.

Also as a subcontractor for agenciesSign-off with a traceable test log
★★★★★Google review

“I have enjoyed working with Mr Hanstein for many years and keep referring internet marketing clients of ours to him for website overhauls and tracking implementations. What I particularly value about working together is that he thinks along and asks questions. And when there are problems, I get an "I'll take care of it", and then all I have to do is wait for the email saying the problem has been fixed. Thank you, and here's to many more years of successful collaboration.”

Translated from German · Show original

„Ich arbeite seit vielen Jahren gerne mit Herrn Hanstein zusammen bzw. verweise immer wieder Internet-Marketing-Kunden von uns zur Überarbeitung Ihrer Website und zur Trackingimplementierungen an Herrn Hanstein. Ganz besonders schätze ich an der Zusammenarbeit, dass er mitdenkt und nachfragt. Und wenn es Probleme gibt, kommt ein "kümmere mich drum", dann muss ich nur noch auf die Mail warten, dass das Probleme behoben wurde. Danke und auf die nächsten Jahre erfolgreicher Zusammenarbeit.“

Holger Schulz · Online marketingRead it on Google →

Why even experienced developers hand this over:Consent Mode v2, the connection to the cookie banner, Tag Manager, a server-side container, passing conversions on to Google Ads and Meta – each part is documented on its own, but how they work together is not. One wrongly set signal, and weeks of campaign data are unusable. This interplay is exactly what I set up – and verify in a way you can trace.

What I set up

  • Google Consent Mode v2 – correctly connected to your cookie banner (e.g. Borlabs, Usercentrics, Cookiebot)
  • Google Tag Manager – a tidy container instead of scripts sprawling through the source code
  • Server-side tagging – your own tagging server for more robust data and a faster website
  • Conversion tracking for Google Ads and Meta – including enhanced conversions
  • Google Analytics 4 – events that match your goals instead of default noise
  • Test log for sign-off – every signal documented: what fires when, and with which consent

Part of a GDPR-compliant website – this is the most technically demanding part of it.

What Consent Mode changes

Without it, a visit where the user declines is lost to your analytics – and depending on the sector, half of all users decline. With it, anonymous signals are kept, and Google uses them to model the missing figures:

In the process, no identifiers are set and no cookies are written. You won’t get perfect figures, but you will have a basis for decisions again.

What Google Consent Mode is

Consent Mode is an interface between your cookie banner and the Google tags on your website. The banner – in the jargon, the CMP or consent management platform – asks the visitor. Consent Mode passes the answer on to Google Analytics, Google Ads and Tag Manager so that they act accordingly: measure when consent has been given, and hold back when it has not.

Technically, this happens via four signals. analytics_storage and ad_storage control whether cookies for analytics and advertising may be set. Version 2 added ad_user_data (may user data be sent to Google for advertising?) and ad_personalization (may personalised advertising, such as remarketing, be shown?). If the two new signals are missing, Google treats the data as if nobody had consented.

Why Google has required it since March 2024

The background is the EU’s Digital Markets Act (DMA). It obliges large platforms to obtain verifiable consent for the use of personal data for advertising purposes. Google passes this obligation on to advertisers: since March 2024, websites with visitors from the European Economic Area need Consent Mode v2 for remarketing lists, audiences and conversion measurement in Google Ads to keep working. Without the signals, the lists shrink and bidding strategies work with incomplete data.

Basic or Advanced: the two variants

Basic Consent Mode

The Google tags only load once the visitor has consented. Before that, nothing is transmitted, not even an IP address. If someone declines, the visit stays invisible. Google only roughly fills the gap with a general model.

Advanced Consent Mode

The tags load immediately, but in the “denied” state. Without consent, they send cookieless pings: no cookies, no identifier – but the IP address, time and browser details. From these, Google models the missing conversions much more accurately.

The advanced variant delivers better figures, but is disputed under data protection law: even a cookieless ping transfers the IP address to Google before anyone has consented. Which variant you use is something you decide with your legal adviser. I set up both properly and explain the difference using your own figures.

Typical implementation mistakes

  • Default state set too late: the default “denied” must be in place before the first tag loads – otherwise the tags measure without consent in the first few milliseconds.
  • Banner sends no update: the visitor consents, but the signal never reaches Google. The data is missing without anyone noticing.
  • Only version 1 implemented: ad_user_data and ad_personalization are missing, so remarketing and audiences in Google Ads run empty.
  • Duplicate implementation: one Analytics code hard-coded in the theme and a second in Tag Manager – one of them doesn’t check for consent.
  • Online shops without a purchase signal: the order is measured, but transmitted without a value and without the consent status.

This is checked with Google’s Tag Assistant and the consent view in Tag Manager’s preview mode: for every page view, you can see which state applies and which tag actually sends data.

Implementing Consent Mode v2 step by step

Whether you use Google Tag Manager (GTM) or gtag.js, the implementation follows the same pattern:

  1. Set the default state. Before any Google tag loads, all four parameters are set to “denied” for visitors from regions that require consent. A short wait_for_update gives the banner time to load.
  2. Connect the consent banner. The CMP sends an update as soon as the visitor decides – “granted” for the categories they allowed, “denied” for the rest.
  3. Map categories to parameters. Statistics consent controls analytics_storage; marketing consent controls ad_storage, ad_user_data and ad_personalization.
  4. Respect returning visitors. The stored decision must be applied on every page load, before tags fire – not only on the first visit.
  5. Test and document. Check every consent state in Tag Assistant and in the network requests, and record the result for sign-off.

In GTM, many certified CMPs provide a template that handles the default and the update. That saves work, but it doesn’t replace the test: a template set up with the wrong categories sends the wrong signals.

Consent Mode and the IAB TCF

The IAB Transparency & Consent Framework (TCF) is an industry standard for passing consent to advertising vendors. Google requires a certified CMP that supports the TCF for publishers who show Google ads on their own website (AdSense, Ad Manager). For businesses that only advertise with Google Ads and measure with Analytics, Consent Mode v2 is the relevant requirement; a Google-certified CMP makes it easier, and the TCF is optional.

Which regions it applies to

Google’s EU user consent policy covers visitors from the European Economic Area, the UK and Switzerland. In these regions, Consent Mode v2 is required for remarketing, audiences and full conversion measurement. Elsewhere, local laws decide – in the USA, for example, several states such as California have their own privacy laws with opt-out rights. Consent Mode can be configured by region, so that a website applies “denied” by default in Europe and different rules elsewhere.

How to check whether Consent Mode works

  • Tag Assistant: shows the consent state on every page and which tags fired with which state.
  • Network requests: Google requests carry consent parameters (gcs, gcd) that reveal the state actually sent.
  • Google Ads and Analytics: the consent diagnostics show whether Google receives the signals on all pages.

How the setup works

Also as a subcontractor: agencies and freelancers hand their tracking setup over to me and deliver it under their own name.

AuditWhat is installed on your website, and what actually fires? A quick check with a clear list of faults.
PlanWhich events do you need for which decision? No more, no less.
SetupConsent Mode, container and conversions – aligned with your data protection setup.
Sign-offA joint test with a log: you see in black and white that everything measures correctly.

Frequently asked questions about tracking

Do I really need Consent Mode?

If you use Google services such as Ads or Analytics in the EU: yes. Without a correct consent signal, Google restricts data collection and campaign optimisation – your advertising becomes more expensive without you noticing.

What does server-side tracking do for me?

The data runs through your own server instead of straight from the browser. That makes measurement more robust, improves loading time and gives you control over which data is passed on. It is not mandatory – I will tell you honestly whether it is worth it for your advertising budget.

Is the whole thing GDPR-compliant then?

I set up the technology so that it follows your consent setup – only what the visitor has allowed is measured. The legal assessment of your privacy policy remains the job of your legal adviser; if you wish, I can work with them directly.

Since when has Consent Mode v2 been mandatory?

Since March 2024 for anyone who uses Google Ads or Google Analytics with visitors from the European Economic Area and wants to keep remarketing, audiences and complete conversion data. No law prescribes Consent Mode itself – Google makes it a condition for these features.

Do I still need a cookie banner?

Yes. Consent Mode doesn’t ask anyone; it only passes on what the banner has asked. Without a consent management platform, there is no consent for it to transmit.

Basic or Advanced – which do you recommend?

It depends on how important accurate advertising data is to you and how your legal adviser assesses the cookieless pings. For most small businesses with a modest advertising budget, Basic is enough. If you put a lot of money into Google Ads, you benefit noticeably from the advanced modelling – but then the decision should be documented.

Do I need the IAB TCF?

Only if you show Google ads on your own website (AdSense, Ad Manager). If you only advertise with Google Ads and use Analytics, what Google requires is Consent Mode v2 connected to your consent banner.

Does Consent Mode apply to UK visitors?

Yes. Google’s EU user consent policy covers the European Economic Area, the UK and Switzerland.

Your campaigns deserve figures you can rely on.

Request setup →