← All articles

Ads & SEO

Meta and Google ad tracking in the EU after consent rules tightened

What stops working in Google Ads and Meta when EU visitors refuse cookies, what modelled conversions and server-side tracking recover, and what they never will.

7 min read

When an EU visitor clicks "reject" on your cookie banner, your Google and Meta tags should stop setting advertising cookies for that person. From that moment, the conversion they may go on to make is invisible to the standard pixel, they can't join a remarketing list, and your ad platforms optimize on a thinner set of data. Two tools recover part of the picture without breaking the rules: Google's consent mode, which sends cookieless signals and lets Google model the missing conversions, and server-side tracking (Google's server-side tagging and Meta's Conversions API), which makes the data you are allowed to send more complete. Neither one is a legal way around a refusal, and anyone who sells it as one is selling you a problem.

This article walks through what breaks, what each fix really does, and a set-up that holds up.

Why the rules feel tighter now

The legal basics haven't changed much: EU rules require consent before non-essential cookies are stored, and the GDPR defines valid consent. What changed is enforcement from three directions:

  • Regulators have taken a harder look at banners. European data protection authorities have flagged missing "reject" buttons, pre-ticked boxes and manipulative button colours; our guide to cookie banners for Canadian businesses lists what their joint taskforce found.
  • Google strengthened enforcement of its EU user consent policy. That policy requires sites using Google products to get valid consent from users in the European Economic Area, the UK and Switzerland for cookies where the law requires it and for ad personalization, and to keep records of that consent. Google can limit or suspend products for advertisers who don't comply.
  • Google's tags now expect consent signals. In November 2023, consent mode gained two parameters, ad_user_data and ad_personalization, on top of the original ad_storage and analytics_storage.

The result: an EU campaign that "worked fine" with a decorative banner and tags firing regardless is now both a compliance risk and, increasingly, a measurement problem.

What you loseWhyPlatform
Observed conversions for refusing usersNo ad cookie connects the click to the purchase or leadGoogle Ads, Meta
Remarketing audiencesRefusing users can't be added to listsGoogle Ads, Meta
Enhanced conversions and user IDs for those usersad_user_data denied disables themGoogle Ads, GA4
Full GA4 sessions and user countsanalytics_storage denied stops analytics cookiesGA4
Signal volume for automated biddingFewer observed conversions to learn fromBoth

Google's developer documentation lays out what each denied parameter does. With ad_storage denied, no new advertising cookies are written. With analytics_storage denied, first-party analytics cookies are not read or written. With ad_user_data denied, user_id and enhanced conversion data are disabled. With ad_personalization denied, remarketing and personalized advertising features don't receive data.

The practical effect is uneven. A business whose EU visitors accept at a high rate loses a little. A business with a strict but fair banner, where many people click reject, can see reported conversions drop sharply overnight, even though real sales are unchanged. That drop is a measurement change, not a performance change, and it is worth telling everyone who reads your reports before you switch.

Consent mode passes the visitor's choice to Google tags. It does not provide a banner; you still need one from a consent management platform.

Basic consent mode keeps Google tags from loading until the visitor interacts with the banner. If they refuse, Google says no data is transferred to it at all. Conversion modelling then relies on a general model.

Advanced consent mode loads tags on page open with consent set to denied by default. If the visitor refuses, the tags send cookieless pings instead of full measurement: consent-state pings, key event pings and Analytics pings that, according to Google, contain only non-identifying data such as a random number generated per page load and the consent state. If the visitor accepts, full measurement is sent. Google uses these pings to model the conversions it can't observe, with an advertiser-specific model rather than a general one.

Two limits matter for small advertisers:

  • Modelling needs volume. Google states that your tag must meet a data threshold before modelling kicks in. A site with a handful of EU conversions a month may never see modelled numbers.
  • Advanced mode sends pings before consent. Some advertisers and some legal advisers prefer basic mode for exactly that reason. This is a judgment call to make with whoever advises you on privacy, not a technical default.

Two more settings help at the margins. url_passthrough carries ad click information in the page URL when cookies are refused, so a conversion on the same site can still be linked to the click. ads_data_redaction removes ad click identifiers from requests when ad_storage is denied.

Server-side tracking: what it does and doesn't do

Server-side tracking moves part of your tagging from the visitor's browser to a server you control, which then forwards events to Google, Meta and others. It improves data quality: fewer events lost to ad blockers and browser restrictions, more control over exactly which fields leave your site, and a single place to strip personal data you don't want to share.

It does not change who has consented. Google's documentation for server-side tagging is explicit on the mechanics: the banner sends choices to the Google tag in the browser, the tag passes them to the server container as parameters, and server-side Google tags are consent-aware. With ad_storage denied, the server-side Google Ads conversion tag doesn't write or read ad cookies, and remarketing tags don't send data to build audiences.

If a vendor tells you server-side tracking lets you "recover" users who refused consent by sending their data from the server instead, that is the same processing the visitor refused, done somewhere they can't see. Don't do it.

Meta: Pixel plus Conversions API

Meta's side works on the same principle with different tools.

The Pixel must respect consent. Meta's own developer documentation shows how: call fbq('consent', 'revoke') before the pixel initializes, on every page, and fbq('consent', 'grant') once the visitor accepts. It also states that each company is responsible for its own GDPR compliance.

The Conversions API (CAPI) sends events from your server to Meta. Meta recommends running it alongside the Pixel, a set-up often called "redundant". When the same event arrives from both sources, Meta deduplicates it using a matching event_id and event name, within a 48-hour window. CAPI improves match rates and resilience to browser restrictions for users who consented. It should be wired to the same consent state as the Pixel, so a refusal in the browser also stops the server event.

Customer data must be hashed. Both Meta and Google expect personal identifiers such as emails and phone numbers to be normalized and hashed (SHA-256) before upload. Hashing protects the data in transit, but under the GDPR hashed personal data is still personal data. It needs a legal basis like anything else.

Offline and CRM conversions

For lead-generation businesses, a large share of value happens after the form: the call, the quote, the signed contract. Uploading those outcomes from your CRM to Google (offline conversions or enhanced conversions for leads) and to Meta (Conversions API) helps the platforms optimize for real customers instead of form fills.

Google's API documentation strongly recommends sending a consent value with each uploaded conversion and warns that without it, conversions may not be attributable. It also notes that Google Ads doesn't support IP address matching for users in the EEA, the UK or Switzerland. Record consent at the moment the lead submits the form, store it in the CRM next to the contact, and send it with every upload.

A set-up that holds up

  1. A real banner. Equal "accept" and "reject" on the first layer, no pre-ticked boxes, a way to change your mind later, and records of consent.
  2. Consent mode v2 on every Google tag, with all four parameters, region-specific defaults for the EEA, UK and Switzerland, and a deliberate choice between basic and advanced.
  3. Meta Pixel with consent revoke and grant, plus Conversions API tied to the same consent state, with event_id deduplication.
  4. Server-side tagging if your volume justifies it, configured to forward consent, not override it.
  5. CRM conversions uploaded with consent values, so the platforms learn from paying customers.
  6. A reporting note explaining that EU conversion numbers changed when consent changed, so no one cuts a good campaign by mistake.
  7. A test every quarter. Open the site in a private window from an EU location, refuse, and check in your browser's developer tools that no advertising cookies are set and no ad requests carry identifiers.

This is general information, not legal advice. Your consent design and the choice of basic or advanced mode should be checked against advice for the countries you target.

How PNE fits

This is the kind of set-up PNE's Analytics service handles for businesses advertising in Europe: banner, consent mode, Pixel and Conversions API wired to the same consent state, and CRM conversions sent back to both platforms. The goal is numbers you can trust and an account you can defend if a regulator or Google asks.

Sources

Free tracking check

Not sure which marketing brings in clients?

Tell us what you track today. We’ll reply with what is missing.

Prefer to talk? Book a free 30-minute call or call (647) 388-2843.

Keep reading