Contentoren

Advertising & analytics

Consent Mode v2 & Server-Side Tracking in 2026: A GDPR Guide

Consent Mode v2 and server-side tracking in 2026: the four parameters, basic vs advanced, Google's June change, hosting costs and what the Digital Omnibus may change.

19 min readby Contentoren Editorial Team
Share
A web developer and a data protection officer discuss the consent and tracking setup of a small natural cosmetics online shop at a laptop and a printout.

Key takeaways

In short:

  • Consent Mode v2 sends four consent signals to Google: ad_storage, analytics_storage, ad_user_data and ad_personalization. For users in the EEA, Google requires advertisers to send them via Consent Mode or TCF (Google Ads Help).
  • Since 15 June 2026, ad_storage alone decides whether Google Ads cookies and IDs are collected via GA4. Google Signals is no longer a second switch (Google Analytics Help).
  • Server-side tracking improves data quality and control, but it is not a way around consent. ePrivacy and GDPR rules apply in exactly the same way.
  • Digital Omnibus: the EU Council wants consent exemptions for audience measurement and one-click refusal. As of November 2026 this is not yet law. Fix your setup now and build it so that 2027 changes are a configuration task.

Many European advertisers have run Consent Mode since the March 2024 deadline without ever auditing it. Google's June 2026 change makes that riskier: one wrong signal either costs you conversions or sends data to Google Ads after a visitor said no. At the same time, vendors market server-side tracking as the answer to ad blockers, data loss and privacy all at once. This guide separates what is technically true, what the law requires across the EEA and UK, and what you should change in 2026. All facts as of 6 November 2026. This article is not legal advice.

Consent Mode is a Google API through which your cookie banner tells every Google tag what the visitor has agreed to. The tags adjust their behaviour accordingly. Consent Mode is not a banner: it works with your consent management platform (CMP) or your own banner (Google for Developers). "v2" refers to the November 2023 update that added two parameters (Google for Developers).

Parameter Controls Effect when denied
ad_storage Advertising cookies and device IDs No new ad cookies written, existing ones not read; GA4 does not read or write Google Ads cookies
analytics_storage Analytics cookies (e.g. visit duration) No analytics cookies; GA4 receives cookieless pings for modelling
ad_user_data Sending user data to Google for advertising Enhanced conversions and user-provided data are disabled; conversion pings become cookieless
ad_personalization Personalised advertising No remarketing, no personalised audiences

Table source: Google Ads Help, consent mode reference. Two details are often missed: Google states that ad_user_data is required for enhanced conversions and tag-based conversion tracking, and personalised advertising needs both ad_user_data and ad_personalization.

There are also functionality_storage, personalization_storage and security_storage. They don't drive Google ads measurement, but they belong in a clean tag inventory.

What happens if you don't send Consent Mode signals?

Google applies its EU User Consent Policy to users in the EEA, the UK and Switzerland. Advertisers must send consent signals for EEA traffic via Consent Mode or TCF. If a site fails an audit and the advertiser does not engage, Google says it may suspend remarketing, ad personalisation and/or conversion measurement for the account (Google Ads Help). If GA4 lacks the signals, EEA users have been excluded from audiences shared with linked ad products since March 2024 (Google Analytics Help).

Do you need a Google-certified CMP?

Advertisers: no, but it helps. Google says advertisers can use a CMP from its CMP Partner Program but are not required to. Certification is mandatory for publishers serving ads via AdSense, Ad Manager or AdMob (Google Ads Help). A certified CMP saves integration work, but it does not replace reviewing your banner text or configuring it correctly.

Basic or advanced: which implementation fits?

The most important Consent Mode decision is the implementation type.

Basic consent mode Advanced consent mode
Google tags load Only after banner interaction Immediately, with denied defaults
Data without consent None, not even the consent state Cookieless pings (timestamp, user agent, referrer, consent state, ad-click indicator)
Conversion modelling General model Advertiser-specific model
GA4 behavioural modelling Not possible Possible once thresholds are met
Privacy assessment Conservative Needs sign-off from your privacy lead

Sources: Google Ads Help on consent mode, Google for Developers.

Why advanced mode is a judgement call in Europe

Advanced mode loads Google tags before consent and sends cookieless pings on refusal. Article 5(3) of the ePrivacy Directive requires consent for storing information on, or accessing information from, a user's device unless strictly necessary for a service the user requested. Each member state implements it nationally; in Germany, for example, it is § 25 TDDDG. The European Data Protection Board's Guidelines 2/2023 (adopted 7 October 2024) treat distributing JavaScript that instructs a device to send information back as "gaining access" under Article 5(3). Whether cookieless pings fall within that has not been settled authoritatively.

Our recommendation: start with basic mode. Move to advanced only once your data protection adviser has assessed and documented the pings. This is not a decision for marketing alone.

When does Google actually model?

For small accounts, modelling is often a promise without effect. Google publishes these thresholds:

  • Google Ads conversion modelling: at least 700 ad clicks over 7 days per country and domain grouping (Google Ads Help).
  • GA4 behavioural modelling: advanced implementation, at least 1,000 events per day with analytics_storage='denied' for 7 days, and 1,000 daily users with consent on at least 7 of the previous 28 days (Google Analytics Help). Even then, eligibility is not guaranteed.

Take a hypothetical regional service business with 400 clicks a week: it will never reach the Ads threshold. For accounts like this, an honestly earned consent rate and imported offline conversions matter more than the basic-versus-advanced debate.

What changed on 15 June 2026?

Until mid-June 2026, linked GA4 properties needed two switches turned on before GA4 collected Google Ads cookies and IDs: the Google Signals setting in GA4 and the Consent Mode signal. Since 15 June 2026, Google says Consent Mode is the single control. Google Signals now only governs whether GA4 data is associated with signed-in users for behavioural reporting in Analytics (Google Analytics Help, "Updates to Google Analytics Data Controls").

In practice:

  • Banner wrongly sends ad_storage as granted: data reaches Google Ads even when the visitor refused. Previously, a disabled Google Signals setting partly caught this. That is a privacy risk.
  • Banner never sends ad_storage, or always sends denied: you lose conversions and remarketing audiences, and Google shows no error.

Already announced: later in 2026, ad_personalization is due to become the only control over whether linked GA4 data is used for personalisation in Google Ads. As of 6 November 2026, Google had not published a date (Google Analytics Help). Audit all four signals now, not just ad_storage.

What is server-side tracking and what does it do?

Server-side tracking (or server-side tagging) means the browser no longer sends measurement data directly to Google, Meta, LinkedIn and others. Instead it sends it to a server on your own domain, for example measure.yourcompany.eu. That server, typically a server-side Google Tag Manager container (sGTM), processes the data and forwards it to each platform. Google explicitly recommends running the server container on a first-party domain (Google for Developers).

What server-side tracking actually delivers

  • Control: you see and filter which fields go to which platform, e.g. truncating IP addresses or removing URL parameters.
  • More resilient measurement: requests to your own domain are blocked less often than requests to known tracking domains. How much that helps depends on audience and browsers. There is no reliable, universal percentage.
  • Fewer scripts in the browser: one data stream instead of several pixels can improve page speed.
  • Server-to-server connections: confirmed purchases, qualified leads or CRM status changes can be sent from your backend.

What server-side tracking does not do

  • It does not replace consent. Advertising and analytics tracking still needs consent under the ePrivacy rules and a legal basis under GDPR. The server forwards data; the obligations stay with you.
  • It does not avoid international transfers. If the data then goes to US platforms, that is still a transfer you must safeguard.
  • It does not "beat" ad blockers for people who refused. Continuing data flows via the server after a refusal is a legal problem, not a measurement fix.

How the pieces fit: Consent Mode is configured in the web container. The Google tag adds the consent parameters to each request sent to the server container, and Google tags in the server respect them (Google for Developers). For Meta, LinkedIn, TikTok or OpenAI tags in the server, you must configure consent checks yourself, because only Google's tags are consent-aware out of the box.

Google tag gateway: the lightweight option

If you only need Google tags in a first-party context, Google tag gateway for advertisers runs through your existing CDN, load balancer or web server, with no tagging server of your own. It does nothing for Meta, LinkedIn or ChatGPT Ads, which need sGTM or direct APIs.

Which ad platforms offer server-side APIs?

All major ad platforms now recommend combining a browser pixel with a server API, using deduplication via a shared event ID.

Platform Server API Notes from the vendor
Google Ads / GA4 sGTM, enhanced conversions, offline import Consent parameters are inherited from the web container
Meta (Facebook/Instagram) Conversions API Can be set up in Events Manager with no code and no setup fees; deduplicated with the Pixel
LinkedIn Conversions API Deduplicated with the Insight Tag; supports offline conversions
TikTok Events API Recommended alongside the Pixel with deduplication
ChatGPT Ads (OpenAI) Conversions API Complements the Measurement Pixel; deduplicated by Pixel ID, event name and ID; up to 1,000 events per batch

OpenAI deserves attention because ChatGPT Ads is a new channel and you can set up measurement properly from day one. For the channel itself, costs and setup, see our guide to ChatGPT Ads in Europe.

Remember: server events containing hashed email addresses are still personal data. Only send them when the matching consent exists. For Google, that is ad_user_data.

How much does server-side tracking cost?

Hosting is usually the smallest cost. Setup, testing and maintenance are the real drivers.

Option Running cost (as of November 2026) Best for
Google Cloud Run (self-managed) Google estimates about USD 45 per server per month, with a recommended minimum of 2 servers; 2–10 servers handle roughly 35–350 requests per second (Google for Developers) Teams with cloud skills and strict control requirements
Managed hosting, e.g. Stape Free up to 10,000 requests; Pro USD 20/month up to 500,000 requests; Business USD 100/month up to 5 million requests (monthly billing, cheaper annually) (Stape pricing) SMEs without DevOps, fast start
Google tag gateway No server cost of its own; uses existing infrastructure Google tags only, first-party context

The main cost drivers:

  1. Request volume: every event counts. A shop with many page views and e-commerce events quickly reaches millions.
  2. Number of platforms: each server API needs mapping, deduplication and testing.
  3. Privacy documentation: data processing agreements with the host and platforms, records of processing and possibly a DPIA.
  4. Maintenance: platforms change APIs and templates. Without monitoring, a failed server container only shows up once conversions disappear.

Client-side or server-side: what fits which company?

Company type Recommendation Why
Local service business, small budget, Google Ads only Client-side with Consent Mode v2 (basic), enhanced conversions for leads Server cost and upkeep are out of proportion; modelling thresholds won't be met anyway
B2B company on Google Ads and LinkedIn Ads Client-side plus CRM feedback (offline conversions, LinkedIn Conversions API) Value lies in the qualified lead, not the form submission
Online shop on several ad channels Server-side (sGTM) with Meta CAPI, TikTok Events API, possibly OpenAI CAPI One data stream for all channels, purchase confirmed from the backend, deduplication
Large publisher or platform with an in-house tech team Server-side, self-hosted (Cloud Run or EU hosting) Full control over data fields, location and cost at high volume
Regulated sectors (health, finance, legal) Privacy review first, then minimal data sharing Sensitive data in URLs or events is a bigger risk than missing conversions

Change now or wait for 2027?

The Digital Omnibus is a European Commission legislative package of 19 November 2025 that, among other things, would revise the cookie rules. The Council of the EU adopted its negotiating position on 21 October 2026 (Council of the EU press release). According to an analysis by law firm Heuking (in German), the Council text:

  • keeps the cookie rules in Article 5(3) of the ePrivacy Directive rather than moving them into the GDPR, as the Commission had proposed;
  • adds consent-free purposes: aggregated audience measurement (including by processors, if aggregated and anonymised), security, contextual advertising and its measurement including frequency capping;
  • requires one-click refusal and a four-month waiting period before asking again after a refusal (Commission proposal: six months);
  • had already dropped the obligation to respect browser signals in June 2026.

This is not law yet. The European Parliament has not adopted its position, and trilogue negotiations follow. Heuking does not expect entry into force before 2027; the EU aims to finish its simplification packages by the end of 2027. Personalised advertising and remarketing remain consent-based under the Council text.

UK note: the UK has already moved. Under the Data (Use and Access) Act 2025, a new Schedule A1 to PECR has been in force since 5 February 2026. It allows storage or access for statistical purposes to improve your own website or service without consent, provided users get clear information and a simple, free way to object. Advertising cookies are not covered. Check the ICO's current guidance before relying on it.

Action Now Wait for 2027 Why
Audit Consent Mode v2 with all four parameters ✅ Google policy applies; the 15 June 2026 change is already live
"Reject" on the first banner layer, equally prominent ✅ Matches regulators' current practice and the Omnibus draft
Log consent with timestamp, purpose and banner version ✅ GDPR accountability; groundwork for future waiting periods
Sort the tag inventory by purpose (necessary, security, audience measurement, advertising) ✅ Lets you move services out of the banner later via configuration
Server-side tracking for shops running several channels ✅ Benefits don't depend on the Omnibus
Audience measurement without consent (EU) ⏳ Not covered by current Article 5(3) rules; reassess once in force
Hard-code a re-ask waiting period ⏳ (prepare as a parameter) Duration still differs between Council and Commission
Shrink or remove the banner ⏳ Advertising tracking stays consent-based
  1. Build a tag inventory: list every tag, pixel, cookie and server endpoint with purpose, vendor, legal basis and consent category.
  2. Configure the CMP: accept and reject equally prominent on the first layer; name "ads personalisation" explicitly; link to Google's Business Data Responsibility Site (Google Ads Help).
  3. Set defaults: gtag('consent', 'default', …) with all four parameters set to denied, before any measurement command, on every page (Google for Developers). Use wait_for_update for asynchronously loading banners.
  4. Check updates: acceptance, refusal and later withdrawal must each trigger an update command; the choice is stored and applied on the next page load.
  5. Decide the implementation type: basic or advanced, documented with your privacy adviser.
  6. Secure non-Google tags: Meta, LinkedIn, TikTok, OpenAI, heatmap tools and so on fire only after consent, in the browser and in the server container.
  7. Enhanced conversions and offline import: only send with ad_user_data = granted; feed CRM status (e.g. "qualified lead", "won deal") back.
  8. Test deduplication: the same event ID for pixel and server API.
  9. Contracts and documentation: update data processing agreements, privacy notice and records of processing.
  10. Set up monitoring: weekly check of consent rate and conversions; alerts if the server container goes down.

How do you audit data quality?

Testing with Tag Assistant

Open Google Tag Assistant and run three scenarios in a fresh browser profile: reject, accept, withdraw consent. Each time, check:

  • The first "Consent" event shows all four parameters as denied (column "On-page Default").
  • After interacting with the banner, "On-page Update" reflects the actual choice.
  • Under "Tags", only tags matching the choice fire.
  • After refusal, no _gcl_* or _ga cookies are set, and the network tab shows no requests to Meta, LinkedIn or TikTok.

Diagnostics in Google Ads and GA4

  • Tag Diagnostics in Google Ads, GA4 or GTM: messages such as "Some pages missing consent for EEA users" or "missing EEA consent for ads personalization" point to pages without signals or an incomplete v2 setup (Google Ads Help).
  • GA4 consent settings: Admin → Data collection and modification → Consent settings shows, per data stream, whether ad_user_data and ad_personalization are arriving (Google Analytics Help).

Plausibility check

Compare three numbers every month: consent rate from your CMP, conversions in Google Ads, and actual enquiries or revenue from your CRM or shop. If Google Ads conversions dropped sharply from 15 June 2026 while real enquiries did not, the cause is almost always ad_storage or ad_user_data. If the consent rate is implausibly close to 100 %, check whether the banner sends granted before the visitor decides.

These numbers feed your bidding directly: Smart Bidding, AI Max and Performance Max only learn from reported conversions. Our guide to AI Max vs Performance Max explains why that matters before the DSA migration. If you are considering replacing GA4 altogether, see our comparison of GA4 alternatives under GDPR.

Conclusion

In 2026, Consent Mode v2 is no longer a formality. Since 15 June, ad_storage alone decides whether GA4 collects Google Ads data, and ad_personalization is set to follow. Audit the four signals, your banner design and your consent logs first. Server-side tracking pays off mainly for shops and companies running several ad channels, and it never replaces consent. The Digital Omnibus may exempt some measurement purposes from consent from 2027 onwards. Until then, current national rules apply. If you structure your setup by purpose today, you can adopt the new rules later through configuration.

Contentoren sets up tracking and reporting as part of our web analytics service, including Consent Mode, server-side tagging and CRM feedback, priced individually by scope. For the privacy assessment of your banner, advanced mode and processor agreements, we offer privacy, GDPR and EU AI Act consulting at a day rate of €1,200 (incl. VAT). This does not replace legal advice from a lawyer in individual cases. A no-obligation first call clarifies which route fits your account.

Frequently asked questions

What is Consent Mode v2?

Consent Mode v2 is Google's API that passes your cookie banner's consent decision to Google tags. Version 2 added ad_user_data and ad_personalization to the original ad_storage and analytics_storage parameters. It is not a banner itself; it works with your consent management platform.

What changed in Consent Mode on 15 June 2026?

According to the Google Analytics Help Center, since 15 June 2026 Consent Mode is the single control for whether Google Ads cookies and IDs are collected via GA4 for linked Google Ads accounts. The Google Signals setting now only affects behavioural reporting inside Analytics. A misconfigured ad_storage signal therefore directly affects your ads data.

Is server-side tracking GDPR compliant?

Server-side tracking is a technical architecture, not a legal basis. It does not remove the consent requirement under Article 5(3) of the ePrivacy Directive and national laws, nor GDPR obligations. Used with proper consent checks, it improves data control and quality; used to keep sending data after a refusal, it creates a compliance problem.

How much does server-side tracking cost?

Google estimates about 45 US dollars per Cloud Run server per month and recommends at least two servers. Managed hosts such as Stape offer a free tier for 10,000 requests and a Pro plan at 20 US dollars per month for up to 500,000 requests (as of November 2026). Setup, testing and maintenance usually cost more than hosting.

Should I wait for the Digital Omnibus before changing my cookie banner?

No. The Digital Omnibus is not yet law: the Council adopted its position on 21 October 2026, the European Parliament has not, and entry into force is not expected before 2027. Current national cookie rules still apply. Structure your tag inventory by purpose now so future exemptions can be applied through configuration.