Tips lesson

Is Google Analytics GDPR Compliant? What EU Rulings Mean for Your Site

Nathan Hollis Nathan Hollis · · 8 min read
Is Google Analytics GDPR Compliant? What EU Rulings Mean for Your Site

Google Analytics is the world’s most widely used web analytics tool. It’s also the one that keeps getting ruled illegal in the EU. If you’re running a website with European visitors and you’ve landed here asking “is Google Analytics GDPR compliant?” — the honest answer is: it depends, but for most sites, the default setup is not compliant, and several EU data protection authorities have said so explicitly.

That matters. Not because you’ll necessarily face an enforcement action tomorrow, but because understanding why GA fails the GDPR test helps you make a clear-eyed decision about what to do next — whether that’s making GA compliant with significant effort, or switching to a privacy-first analytics tool that sidesteps the problem entirely.

What makes an analytics tool GDPR compliant?

The GDPR restricts transfers of personal data to countries outside the EU/EEA unless adequate protections are in place. That restriction sits at the heart of the Google Analytics problem. When a European user visits your site and GA loads, their IP address, browser fingerprint, and behavioral data flow to Google’s servers in the US. That’s a personal data transfer to a third country — specifically, to a country whose surveillance laws (FISA Section 702, Executive Order 12333) give US intelligence agencies access to data held by US companies.

A tool earns GDPR compliance status by meeting several conditions simultaneously:

  • Lawful basis — either valid consent or a legitimate interest that holds up under scrutiny
  • Data minimization — collecting only what’s necessary for the stated purpose
  • Third-country transfer safeguards — no transfer to a country without “adequate” protection unless supplementary measures genuinely protect the data
  • Processor agreements — a compliant Data Processing Agreement (DPA) in place with any sub-processors

Google Analytics touches all four of these. On the transfer question, it’s the hardest one to resolve.

Is Google Analytics GDPR compliant? What the EU rulings say

In January 2022, Austria’s data protection authority (DSB) issued the first ruling in a coordinated wave brought by the privacy advocacy group noyb. The case involved an unnamed Austrian website operator who used Google Analytics with a DPA in place and had attempted to anonymize IP addresses. The DSB concluded that the transfer of data to Google in the US was still illegal under GDPR — because IP anonymization happened after data reached Google’s servers in the US, and because Google remained theoretically subject to US surveillance law regardless of contractual protections.

The full decision is documented on GDPRhub (DSB Austria, 2021-0.586.257). It referenced the Schrems II ruling from the Court of Justice of the European Union (C-311/18, July 2020), which invalidated the EU-US Privacy Shield framework and made clear that Standard Contractual Clauses alone don’t guarantee adequate protection when the destination country’s surveillance laws can override them.

Austria was the first. France’s CNIL followed in February 2022, Italy’s Garante in June 2022, Sweden’s IMY issued fines in 2023. The pattern across all these decisions was consistent: Google Analytics creates a transfer of personal data to the US that can’t be adequately protected under GDPR as the tool is typically deployed.

These weren’t fringe interpretations. They came from national data protection authorities working in coordination, applying the same CJEU logic across different jurisdictions.

Does the EU-US Data Privacy Framework change anything?

In July 2023, the European Commission adopted its adequacy decision for the EU-US Data Privacy Framework (DPF), replacing the invalidated Privacy Shield. Google has since self-certified under the DPF. On paper, this means transfers to Google under the DPF now have a legal basis — the adequacy decision provides the required third-country transfer mechanism.

However, the practical picture is more nuanced. The DPF was designed to address specific concerns, but some privacy lawyers and noyb itself have flagged that the underlying US surveillance laws (FISA 702 in particular) remain unchanged. The first court challenge has already failed. On 3 September 2025 the EU General Court dismissed an action to annul the DPF (Latombe v Commission, case T-553/23). That ruling can still be taken to the Court of Justice. If a later challenge succeeds — as challenges to both Safe Harbor and Privacy Shield succeeded — the legal basis for GA disappears again.

So the current position is: GA transfers may be lawful under the DPF right now, but the DPF carries legal risk that Privacy Shield did not.

The GA4 GDPR risk table

Here’s how the main GDPR risk factors map to GA4’s default configuration:

Risk factor GA4 default behaviour Can you mitigate it?
US data transfer All data processed on Google servers (US) Partially — Consent Mode v2 reduces data sent without consent, but data still goes to Google
IP collection IP anonymized server-side, but full IP reaches Google first No — anonymization happens after transfer
Cookie consent requirement GA4 uses cookies (_ga, _gid) that require prior consent under ePrivacy Directive Yes — Consent Mode v2 with consent banner
Cross-site tracking Google uses measurement data across its ad network by default Partially — disable ads personalization in DPA, but DPA compliance requires active management
Data retention Event data kept for 2 or 14 months, your choice in Admin Yes — reduce in GA4 settings under Data Settings > Data Retention
Processor agreement Google’s DPA available; must be actively executed Yes — sign Google’s DPA; required but not sufficient on its own

Can you make GA4 usable in the EU?

Technically, you can reduce the risk significantly. The honest checklist looks like this:

  1. Implement a consent management platform (CMP) and use Consent Mode v2 — GA4 only fires tracking cookies after a user consents
  2. Sign Google’s Data Processing Amendment — make sure it covers all Google Analytics services you use
  3. Disable “Google signals” data collection in GA4 settings to avoid cross-device tracking without explicit consent
  4. Set data retention to the minimum (2 months)
  5. Disable ads personalization in your DPA settings
  6. Document your legitimate interest or consent basis in your privacy policy, specifically naming Google Analytics

Does doing all of this make GA4 fully GDPR compliant? Not with certainty. The third-country transfer issue still exists — you’re still sending data to Google in the US. Under the current DPF it has a legal basis, but that basis is contested. What these steps do is bring your GA4 setup as close to defensible as the tool currently allows.

For many businesses, particularly those with EU-based audiences and compliance teams actively monitoring regulatory developments, that ongoing uncertainty is the deciding factor in switching tools.

GDPR-compliant analytics alternatives

The simplest way to avoid the GA GDPR problem is to use a tool that doesn’t create it. Privacy-focused analytics tools achieve this primarily by not collecting personal data in the way GA does — no persistent identifiers, no IP storage, no data sent to US servers.

The core compliance checklist for an alternative tool:

Compliance factor What to look for
No personal data collection No IP storage, no persistent cookies, no cross-site tracking
EU data residency Servers located in the EU or EEA; no US transfers
No consent banner required Cookieless tracking means no ePrivacy Directive trigger
Transparent data processing Open-source or independently audited; clear DPA available
Self-hosting option You control where data lives entirely

Tools worth evaluating include Plausible (Estonian company, EU servers, open-source), Fathom (Canadian company with EU data center routing), Matomo (self-hosted option gives you full control), and Simple Analytics (Netherlands-based, cookieless). For a full breakdown of how these compare on features and price, see the Plausible vs Fathom vs Rybbit comparison.

I’ve run several of these tools alongside GA4 on client sites for extended periods. The loss in raw data volume is real — cookieless tools can’t track across sessions or devices. But for most marketing decisions, you genuinely don’t need that granularity. Pageviews, referral sources, and goal completions answer 90% of the questions site owners actually ask.

What about first-party data?

Some teams want to keep GA4 for its integration with Google Ads and Search Console, while handling the consent problem through architecture rather than switching tools. That’s a legitimate path. A first-party data strategy — where you collect behavioral data on your own servers and feed aggregated signals back to GA4 — can reduce what you’re sending to Google while preserving conversion measurement.

Server-side tagging via Google Tag Manager is the main technical approach here. It’s not trivial to implement, and it adds hosting costs, but it’s the architecture that large EU publishers are using to maintain GA4 integration with reduced compliance risk. The key point: even with server-side tagging, the data still ultimately flows to Google, so the transfer question doesn’t fully disappear.

The practical decision framework

Here’s how I’d frame the decision for most site owners:

  • Small site, EU audience, no ads dependency: Switch to a privacy-first alternative. The compliance overhead of making GA4 defensible outweighs the benefits at this scale. Cookie banners alone hurt conversion rates measurably.
  • Medium business, EU audience, using Google Ads: Implement Consent Mode v2 properly, sign the DPA, and monitor DPF developments. Keep GA4, but document your compliance decisions and review them annually.
  • Enterprise, EU regulated sector: Get legal counsel. DPF risk plus sector-specific regulations (healthcare, finance) create a compliance picture that’s too fact-specific for general guidance.

The one thing I’d push back on is the idea that “everyone uses GA so regulators won’t come after me.” That was true in 2020. The coordinated 2022 wave of DPA decisions, followed by fines in Sweden in 2023, shows that enforcement is real even for non-enterprise sites. Compliance by obscurity is a diminishing strategy.

Is Google Analytics GDPR compliant — the bottom line

The honest answer remains: out of the box, no. With significant configuration work and an active compliance posture, GA4 can be deployed in a way that’s defensible under current EU-US Data Privacy Framework rules — but that legal basis is contested and has already been invalidated once. Several EU data protection authorities have ruled that earlier GA deployments were illegal specifically because of the US transfer mechanism.

For sites that need the simplest path to GDPR compliant analytics, the alternative tools — Plausible, Fathom, Matomo self-hosted — avoid the problem structurally rather than patching around it. For sites that need to keep GA4 for ads integration, Consent Mode v2 plus a properly executed DPA is the minimum starting point. Either way, “do nothing” is no longer a defensible option.

If you’re evaluating Plausible specifically as a replacement, the Plausible Analytics review covers what you’d gain and what you’d give up in practical detail.

And if you’re wrestling with whether your site actually needs a consent banner at all — the cookie consent banner decision flowchart walks through it systematically.

First published . Last updated .

Nathan Hollis

Nathan Hollis

Analytics tutor · GA4 & GTM

Web analytics consultant with 15+ years of experience helping businesses turn raw data into actionable insights. Former analytics lead at digital agencies across the US, now focused on privacy-first tracking strategies.

More about me →