
This post talks about: Getting started guides, Software updates
In short
Analytics cookies are used to measure visits and how people use your website. They are not technical cookies, and the rule is consent. Some European authorities, for example in Italy, France and Spain, allow statistics without consent, but always with a notice and only if all of their conditions are met: aggregate statistics, truncated IP, no matching with other data and no sharing with others. The rules vary from country to country. Third-party analytics used as they are do not meet these conditions: in our view, they should be treated as profiling tools and activated only after consent.
You want to know how many people land on your services page, where they come from and where they stop. You install Google Analytics in five minutes and the numbers start coming in.
Then a doubt creeps in: do these cookies need the banner? They’re “just statistics,” after all.
The short answer is: it depends on how you use them, and in most cases, yes. In this guide we look at why, and at what has to be true for you to do without it.
What are analytics cookies?
Analytics cookies, also called analytical cookies or statistics cookies, are the tools a website uses to measure its own traffic. They are used to assess how effective a service is, to design a website or to measure its “traffic”: the number of visitors, also broken down by geographic area, time of day or other characteristics.
In practice, they answer questions like these:
- how many visits did the website get this month?
- which pages are read the most?
- where do visitors come from: Google, social media, newsletters?
- how many people come back a second time?
They are installed by analytics platforms such as Google Analytics, Matomo or the statistics modules of some plugins. To recognize returning visitors, they usually store an identifier in the browser: Google Analytics 4, for example, uses the _ga cookie, which according to Google’s documentation is used to distinguish individual users and lasts two years; with the default settings, the expiry is renewed at every visit.
Are analytics cookies technical cookies?
No. European authorities have been saying so for a long time: as early as 2012, the Article 29 Working Party (which brought together the supervisory authorities and has since been replaced by the EDPB) concluded in its Opinion 04/2012 on Cookie Consent Exemption that not even first-party analytics are exempt from consent.
Technical cookies (coming soon) are those strictly necessary to make the website work, or a service the visitor has asked for: the cart, the login, the language. Your website works perfectly well without knowing how many visits it had yesterday. Statistics are useful to you, not to the visitor.
Some national authorities, however, open a door: under certain conditions they allow analytics cookies without consent, like technical cookies, but always with a notice. This is where almost all the misunderstandings start.
When do analytics cookies not require consent?
Only where a national authority allows it, and under specific conditions. The general rule is consent: Article 5(3) of the ePrivacy Directive exempts only what is strictly necessary to provide the service requested by the visitor, and statistics are not. The EDPB Guidelines 2/2023 on the scope of Article 5(3) take a strict approach: the rule applies to any information stored on or read from the device, whether it is a cookie or not.
Some national authorities, however, allow statistics without consent if the tool is configured to keep data to a minimum. Examples, with conditions that are not identical, are the Italian data protection authority (Garante), the French one (CNIL) and the Spanish one (AEPD). The recurring conditions are these:
- the data is minimized before it reaches whoever processes the statistics, so that the cookie does not allow a single visitor to be singled out. Masking part of the IP address is one of the possible measures, but on its own it does not make the data anonymous;
- the statistics are used only to measure the website’s audience, on behalf of the data controller, and are aggregate or anonymous;
- they cover a single website or a single app, without following the person across different websites;
- the data is not matched with other processing, such as customer databases or statistics from other websites;
- the data is not passed on to third parties for their own purposes.
The details vary from country to country. Two examples:
- the Italian guidelines (para. 7.2) require masking at least the last of the four numbers of an IPv4 address, giving an uncertainty of 1 in 256, and allow statistics across several websites of the same data controller or the same group. They also consider analytics that the data controller uses directly, on its own, for aggregate statistics as equivalent to technical cookies;
- the French CNIL and the Spanish AEPD indicate as a benchmark a cookie lifetime of thirteen months, with no automatic renewal, and data retention of no more than twenty-five months.
Where the exception exists, the conditions must all be met at the same time. If even one is missing, analytics cookies once again require prior consent. And in any case, the visitor must be informed in the cookie policy. Before relying on the exception, check the rules in your country.
Some people also choose statistics tools designed to work without a banner: this is possible only where the authority allows the exception and if the tool genuinely meets all the conditions. The topic deserves a separate in-depth look.
Why do we say that third-party analytics are profiling tools?
Because they are not strictly necessary: European rules distinguish technical cookies, which are what the website needs to work, from everything else, starting with profiling cookies (coming soon). Analytics are not technical. Treating them as equivalent to technical cookies, where that is allowed, is an exception, and like all exceptions it must be demonstrated, not assumed.
Our view is clear-cut: third-party analytics should be treated as profiling tools until they are configured to meet all the conditions that the authority in your country requires for the exception, where the exception exists. The reasons are concrete:
- they assign each visitor an identifier that lasts months or years and recognizes them every time they come back;
- they send the data to an external company, which processes it on its own servers;
- they are often linked to advertising platforms, or become linked with one click in the settings;
- they record individual journeys, not just totals.
Treating them as technical “because they’re just statistics” is the mistake we see most often. It leads to leaving them active before consent, which means using them without the required consent. Authorities, for their part, don’t talk about any particular product: the same rules apply to all analytics platforms.
Google Analytics and GDPR: do you need consent?
Yes, as a rule: Google Analytics is a third-party analytics service and falls into the strictest case. Even in countries that allow the exception, to use it without consent you would have to guarantee all the conditions listed above, including those that depend on Google: that it does not combine the data with other processing and does not pass it on to others.
In practice, many installations go beyond simple counting. When the Google Analytics property is linked to a Google Ads account, for example, Google’s documentation explains that the tags set additional cookies to measure interactions for advertising purposes. At that point, aggregate statistics are only part of the job.
For the vast majority of websites, then, our advice is simple:
- block Google Analytics until the visitor accepts;
- place it in the banner in a clear category, such as “Statistics”;
- use Google Consent Mode v2 to tell Google about the visitor’s choice. Consent Mode does not replace consent: it adapts the behavior of Google’s tags to the choice made on the banner. We explain it in Supporting Consent Mode v2.
Consent Mode has two modes. In basic mode, Google’s tags don’t load until the visitor makes a choice, and nothing reaches Google before then. In advanced mode, the tags load as soon as the page opens and, until there is consent, they send Google cookieless signals. According to EDPB Guidelines 2/2023, these transmissions may also fall within Article 5(3) of the ePrivacy Directive, which requires consent unless one of its exemptions applies. My Agile Privacy® lets you switch to basic mode. Which one to use is a choice to assess with your privacy consultant.
If you still need to install it, follow the step-by-step guide How to install Google Analytics in accordance with GDPR.
Technical, analytics and profiling cookies compared
| Technical cookies | Analytics cookies | Profiling cookies | |
|---|---|---|---|
| What they are for | Making the website or a requested service work | Measuring visits and use of the website | Recognizing the visitor and personalizing advertising |
| Examples | Cart, login, language, choice made on the banner | Visit counts, most-read pages, traffic sources | Meta Pixel, Google Ads remarketing |
| Is consent required? | No | Yes, as a rule. Some authorities allow exceptions if all of their conditions are met | Yes, before installing them |
| Is a notice required? | Yes | Yes | Yes |
What your website needs to do, in 4 steps
- List your analytics tools. Not just Google Analytics: also plugin statistics, heatmaps, session recordings, testing tools. There is often more than one.
- Check the conditions for each one. Who processes the data? Is the IP masked? Are the statistics aggregate only? Does the provider match or pass on the data? If you can’t answer all these questions with certainty, treat it as a tool that requires consent.
- Block the ones that don’t meet the conditions until the visitor accepts, with a banner that lets visitors choose by purpose.
- Describe them in the cookie policy, including those that don’t require consent: which tool, who provides it, what it collects, how long the cookies last.
What My Agile Privacy® does
My Agile Privacy® is the WordPress consent management plugin designed to carry out these steps for real, not just on the surface.
- Cookie Shield detects third-party services on your website and, in Live mode, blocks them automatically until the visitor gives consent, as European rules require.
- Granular consent: the visitor can accept a statistics service and refuse advertising ones, or vice versa: they choose service by service.
- Support for Google Consent Mode v2, Microsoft UET Consent Mode and Clarity Consent Mode, each of which can be enabled with a checkbox.
- Cookie policy and privacy policy included, prepared with the Policy Assistant and updated when the rules change.
- Support from human experts: if you have a question about how your analytics are configured, a real person answers, not a bot.
FAQ - Frequently Asked Questions
Back to Getting started guides

