Do I need a cookie banner for Google Analytics?
Short answer: in the EU and UK, generally yes. Google Analytics sets cookies and processes personal data, so you usually need prior, informed consent, which in practice means a cookie banner, before it loads. A cookieless tool avoids that.
Why Google Analytics needs consent
Google Analytics (GA4) sets cookies in the visitor's browser and processes identifiers and IP data. Under the ePrivacy rules (Article 5(3)), storing or reading information on a device needs consent unless it is strictly necessary, and analytics that profiles a user is not treated as strictly necessary. So in the EU and UK you generally need to ask first, before the GA script runs, which is what a compliant cookie banner does.
- GA sets cookies (for example the
_gaidentifier). - It processes IP and device data to build analytics.
- That combination generally triggers a prior-consent requirement in the EU and UK.
"Consent mode" is not the same as no banner
Google offers a consent mode to adjust GA behaviour based on a visitor's choice, but it still assumes you have a consent mechanism in place. It is a way to handle consent, not a way to skip asking. You still show the banner.
How to avoid the banner
The reliable way to not need a banner for analytics is to use a tool that sets no cookies and stores no personal data, so there is nothing to consent to. That is how PlainStats works: no cookies, no device storage, aggregate counts only. See cookieless analytics and the broader question do I need a cookie banner for analytics.
Related
Sources
- ePrivacy Directive 2002/58/EC, Article 5(3): eur-lex.europa.eu.
- European Data Protection Board guidance: edpb.europa.eu.
General information, not legal advice, and rules differ by country and change over time. Confirm the current position with a data protection officer or qualified counsel.