HOMEPAGE | Blog | Is Google Analytics GDPR-Compliant?

Is Google Analytics GDPR-Compliant?

Publication Date 19 November 2026
Last Updated 19 November 2026
Is Google Analytics GDPR-Compliant?

Google Analytics 4 can be used in line with the GDPR, but it is not compliant by default. Compliance depends on how you set it up: valid consent before tracking starts, a data processing agreement with Google, a lawful route for transfers to the US, accurate privacy notices and sensible retention settings.

The question became urgent after several EU regulators found that earlier versions of Google Analytics breached the GDPR’s transfer rules. The legal position has since changed, but those rulings still shape how many businesses approach GDPR Google Analytics setups today. This guide explains what the regulators decided, what changed afterwards and how to configure GA4 step by step.

It covers the EU GDPR and the ePrivacy rules on cookies. If you need background on the regulation itself, read our GDPR compliance guide. This article is general information, not legal advice.

Why Google Analytics Raises GDPR Questions

Google Analytics measures how visitors use your website. To do that, it sets cookies and collects identifiers and interaction data. Under the GDPR, an online identifier that can single out a person counts as personal data, even if Google does not collect names or email addresses.

Roles matter here. You decide why and how the analytics data is used, so you are the controller. Google processes the data on your behalf, so it acts as a processor. That means you need a data processing agreement with Google and a lawful basis for your own use of the data. Our guide on controllers and processors explains the distinction in more detail.

Three separate legal questions apply to a GDPR Google Analytics setup:

  • Consent: Do cookies and similar technologies need permission before they run?

  • Transparency: Do your privacy notice and cookie policy describe the tool accurately?

  • Transfers: Is there a valid legal route for data that reaches Google’s US infrastructure?

A problem with any one of them can make a setup non-compliant, even if the other two are in order.

What Data Does Google Analytics Collect?

Data type

Examples

Why it matters

Cookie identifiers

The _ga cookie and its property-specific companion

Distinguish returning visitors and can be personal data

Device and browser data

Browser, operating system, screen resolution

Can contribute to identifying a person in combination

Interaction data

Pages viewed, clicks, time on site, conversions

Reveals behaviour linked to an identifier

Location data

Approximate location derived from the connection

Sensitive when combined with other data

User-defined IDs

User ID or other custom identifiers you send

Directly links analytics to an account

In GA4, Google states that it does not log or store IP addresses for users, so the manual IP anonymisation step used in Universal Analytics is no longer needed. That removes one concern, but it does not replace consent, contracts or accurate notices. Review Google’s own explanation in its GA4 IP address help page.

Did EU Regulators Ban Google Analytics?

Not exactly. Between 2022 and 2023, several authorities concluded that using Google Analytics without sufficient safeguards breached the GDPR’s rules on international transfers. The complaints followed the 2020 Schrems II judgment and a coordinated set of 101 complaints from the privacy group noyb. The concern was that identifiers sent to US servers could be accessed under US surveillance law.

Country

Authority

Timing

Outcome

Austria

DSB

Decision December 2021, published January 2022

Found that the transfers lacked adequate protection

France

CNIL

February 2022

Issued formal notices and gave organisations one month to comply

Italy

Garante

June 2022

Found that transfers through Google Analytics were unlawful

Denmark

Datatilsynet

September 2022

Said lawful use required supplementary measures

Norway

Datatilsynet

Early 2023

Reached a preliminary conclusion that use breached transfer rules

Sweden

IMY

2023

Ordered four companies to stop using the tool

These decisions concerned data transfers, not the idea of web analytics itself. They also predate the framework described below, so they do not answer today’s question on their own.

What Changed After the Rulings?

On 10 July 2023, the European Commission adopted an adequacy decision for the EU-US Data Privacy Framework (DPF). Certified US companies can receive EU personal data under that decision, and Google is certified. For many organisations, this restored a legal route for the transfers that had triggered the earlier rulings.

The framework is still being challenged. The EU General Court dismissed a challenge to it on 3 September 2025. The claimant appealed to the Court of Justice, and the appeal is pending as Case C-703/25 P. Earlier transfer frameworks were struck down by the same court, so many privacy teams keep a fallback in place, such as standard contractual clauses, and monitor the case.

Two points to remember:

  • The DPF covers transfers only. It does not give you a lawful basis, valid consent or an accurate privacy notice.

  • Check the current status before you publish or rely on it. The case may have progressed since this article was written.

Do You Need Consent for Google Analytics?

In most cases, yes. National laws implementing the ePrivacy Directive generally require consent before a site stores or accesses information on a visitor’s device, unless the technology is strictly necessary for a service the visitor requested. Analytics cookies are not usually treated as strictly necessary, and the GDPR sets the standard for that consent: it must be freely given, specific, informed and unambiguous.

Some regulators, such as France’s CNIL, allow limited exemptions for audience measurement that meets strict conditions. Do not assume a standard Google Analytics setup qualifies. Check the conditions in each country you target.

In practice, you should:

  • Keep analytics tags inactive until the visitor agrees.

  • Offer Accept and Reject options of equal prominence.

  • Let visitors withdraw consent as easily as they gave it.

  • Record the consent choice.

Our guide to GDPR and website cookie rules covers these requirements in more depth.

GDPR Google Analytics Checklist: How to Configure GA4

Use this checklist to set up GA4 in a way that supports GDPR compliance.

  1. Collect consent before analytics runs. Connect your cookie banner to your Google tags so that analytics does not fire until consent is given. A cookie consent tool can handle cookie discovery, preference controls and consent records.

  2. Implement Google Consent Mode v2. Consent Mode passes the visitor’s choices to Google tags using signals such as analytics_storage, ad_storage, ad_user_data and ad_personalization. Google requires these signals for advertising features on EU traffic. Use a consent platform that supports it and test the result with our Google Consent Mode Checker.

  3. Accept Google’s data processing terms. You can find them in your account settings. Keep a record of when you accepted them.

  4. Update your privacy policy and cookie policy. Name Google Analytics, describe what it collects and why, list the cookies and their durations, explain how to opt out and state your lawful basis. Our privacy policy generator and cookie policy generator can help you start.

  5. Set data retention. Standard GA4 properties offer 2 or 14 months for event-level data. Choose the shortest period that meets your reporting needs, in line with the storage limitation principle.

  6. Review advertising and sharing settings. Turn off Google signals, advertising features and data-sharing options you do not need. Each extra feature adds purposes you must explain and justify.

  7. Keep personal data out of GA4. Check URLs, query strings, event parameters and custom dimensions for email addresses, names or other identifiers. Remove them at the source.

  8. Prepare for deletion requests. Know how to use GA4’s data deletion tools so you can act on erasure requests within the one-month response window.

  9. Test the real behaviour. Open a clean browser session, reject cookies and check your network requests. Repeat for acceptance and withdrawal. Our Cookie Checker can help you see which cookies your site sets.

  10. Document your decisions. Keep your data processing agreement, transfer assessment, consent records and review dates. Accountability means you can show your work.

Basic vs Advanced Consent Mode

Consent Mode can be implemented in two ways, and the difference matters for compliance.

Setup

How it works

Consideration

Basic

Google tags do not load until the visitor consents

Simplest to explain, but you lose measurement for visitors who decline

Advanced

Tags load and send cookieless signals when consent is denied; consented visitors are measured normally

Allows modelling of missing conversions, but you should assess whether the signals are acceptable in your market and describe them in your notices

Choose the option your legal adviser is comfortable with and make sure your banner wording matches what actually happens.

Server-Side Tagging and Privacy-Focused Alternatives

Server-side tagging sends data to a server you control before it reaches Google. That gives you a place to remove or reduce identifiers and to control what is forwarded. It improves control, but it does not remove the need for consent, notices or a lawful transfer route.

If you want to reduce compliance complexity, you can also consider alternative analytics tools such as Matomo, Plausible, Simple Analytics or Fathom. Some can be configured without cookies, which may reduce or remove consent requirements in certain countries. Check each tool’s configuration and the national rules before you drop your banner.

Common Mistakes With GDPR and Google Analytics

Mistake

Why it is a problem

Fix

Loading Google tags before consent

Analytics cookies and requests start without permission

Gate tags on consent and test it

Assuming the DPF makes everything compliant

It addresses transfers only

Cover consent, notices and contracts too

Banner and Consent Mode not connected

Visitor choices are not passed to Google

Use a Consent Mode-compatible platform and verify signals

Leaving retention at the longest setting

Data is held longer than needed

Set the shortest suitable period

Sending emails or names in URLs

Personal data reaches Google unintentionally

Clean URLs and event parameters

Outdated privacy policy

Notice does not match processing

Review it after each analytics change

 

Frequently Asked Questions

Not automatically. Google Analytics 4 provides tools and certifications that support compliance, but you must configure consent, contracts, notices and retention correctly. The tool is only one part of the picture.

Yes, it can be used lawfully if your setup meets the GDPR and ePrivacy requirements. Earlier regulator decisions concerned transfers to the US before the Data Privacy Framework existed. Check the current status of the framework and your national rules.

Usually yes. Analytics cookies are generally not strictly necessary, so consent is normally required before they run. Some countries allow narrow exemptions for limited audience measurement, so confirm the rules where you operate.

Google states that GA4 does not log or store IP addresses, so you do not need the manual anonymisation setting from Universal Analytics. You must still address consent, notices and the other requirements.

Yes. A controller must have an agreement with any processor that handles personal data for it. Accept Google’s data processing terms in your account and keep a record.

Transfers that rely only on the framework would need another legal route, such as standard contractual clauses with supplementary measures. Keep a fallback plan and follow the pending Court of Justice appeal.

Yes. Your notice should say that you use Google Analytics, what it collects, why, how long the data is kept, who receives it and how visitors can object or withdraw consent. Cookie details can sit in a cookie policy that is linked from your notice.

It can be used under the UK GDPR and the Privacy and Electronic Communications Regulations, which require consent for non-essential cookies. The UK GDPR is a separate framework, so check UK-specific guidance.