5 GDPR Tracker Myths That Get Websites Fined
Google Analytics is not automatically compliant. Consent banners are not a shield. Here are five widely-believed myths about trackers, cookies, and GDPR that are costing businesses real money.
The fines keep coming, and trackers, cookies, and analytics tools that operators believed were compliant keep turning up in enforcement decisions. They were not compliant.
Here are five myths that keep appearing in enforcement decisions.
Myth 1: "A cookie banner makes us compliant"
A cookie banner is a mechanism for collecting consent. It does not guarantee consent is valid. Regulators look at how consent is obtained:
- Was the "accept all" option visually prominent and the "reject" option hidden or harder to reach? Dark pattern — consent invalid.
- Did the banner fire analytics or advertising trackers before the user clicked accept? Pre-ticking — consent invalid.
- Did the user have a way to withdraw consent as easily as they gave it? If not — consent invalid.
France's CNIL fined Google €150 million and Facebook €60 million in December 2021 because refusing cookies took several clicks while accepting took one. The EDPB's Cookie Banner Taskforce report (January 2023) lists missing reject buttons, pre-ticked boxes, and misleading banner design as problems, after noyb filed hundreds of cookie banner complaints. A banner is necessary but not sufficient.
Myth 2: "We use server-side tagging so no trackers appear in the browser"
Server-side tagging moves the data collection to your server before forwarding it to analytics or ad platforms. Some businesses assume this hides them from regulators.
It does not. The GDPR applies to the processing of personal data, not to where the JavaScript runs. If you are passing IP addresses, user IDs, or behavioural data to a third party like Google or Meta — even via your own server relay — the same lawful basis requirements apply.
Myth 3: "Google Analytics is fine because everyone uses it"
Not automatically, and the reason has changed. In 2022 the Austrian DSB (January), the French CNIL (February), and the Italian Garante (June) each found that using Google Analytics transferred personal data to the US in breach of GDPR Chapter V, because US surveillance law gave US authorities access to it.
Since 10 July 2023 the EU-US Data Privacy Framework has allowed transfers to US companies that self-certify under it, and the EU General Court upheld the Framework on 3 September 2025 (an appeal is pending). That removes the transfer problem for certified providers. It does not remove the rest: analytics cookies still need valid consent before they fire, and you still need a documented lawful basis for every tracker.
Myth 4: "Legitimate interests covers our analytics"
Article 6(1)(f) — legitimate interests — is a real GDPR lawful basis, but it is not what governs cookies. Under Article 5(3) of the ePrivacy Directive, storing or reading information on a visitor's device needs consent unless it is strictly necessary to provide the service they asked for. That applies whichever GDPR basis you pick, and the EDPB's Guidelines 1/2024 on legitimate interest say consent is likely the appropriate basis for cookies and electronic marketing.
Legitimate interests can still matter for processing that does not touch the device, with a documented balancing test. For cookies and trackers, plan on consent.
Myth 5: "We only need to worry if we have EU users"
The GDPR's territorial scope (Article 3(2)) covers processing related to offering goods or services to people in the EU, or monitoring their behaviour in the EU. You do not need an EU office or server.
The EDPB's Guidelines 3/2018 are specific: the mere accessibility of your website in the EU is not enough to show you target EU users. Factors that can show targeting include a language or currency used in EU countries combined with the ability to order in it, delivery to EU countries, advertising aimed at EU countries, and mentioning EU customers. Trackers that monitor the behaviour of visitors in the EU can bring you into scope under the monitoring limb. Where you are based is not a shield.
What to actually do
- Scan your site for trackers before they scan it for you. Know what's firing, not just what you intentionally installed.
- Check your consent mechanism against the EDPB's guidelines on consent (05/2020). Reject paths must be as easy as accept paths.
- Audit international transfers — every tracker that phones home to a US-based service is a potential transfer. Document your transfer mechanisms (SCCs, etc.).
- Document your lawful bases per purpose, not per tool.
Total GDPR fines rose again in 2025, according to DLA Piper's January 2026 survey. Enforcement is not slowing down.
Run a free tracker scan at /demo to see what is firing on your site before a regulator does. For a deeper gap analysis, the full audit pack at /pricing generates your remediation report.
Related
Regulatory Signals
Scan your site or AI system now
Detect trackers, check legal page adequacy, classify EU AI Act risk, and generate policy documents — in minutes.
Run a free scan