Strictly necessary cookies and profiling cookies: the differences and when you need consent
Every website that uses cookies has to answer one question before choosing a banner: which of its cookies need consent and which do not. The answer lies in the distinction between strictly necessary cookies and profiling cookies, set out in Article 5(3) of the ePrivacy Directive, transposed into the law of every EU country and detailed in the guidelines of national authorities such as the Italian Garante, the French CNIL and the Spanish AEPD. Getting the classification wrong has two opposite consequences: asking for consent for cookies that do not need it, and losing data for nothing, or not asking for cookies that do need it, and remaining exposed to a fine.
What strictly necessary cookies are
Strictly necessary cookies, also called technical cookies, are those required to make the site work or to deliver a service the user has explicitly requested. They do not need consent: describing them in the cookie policy is enough. This category includes:
- Session and authentication cookies, which keep the user logged in while browsing a reserved area.
- Shopping cart cookies in an online store, which remember the chosen products until checkout.
- Security cookies, for example those that protect forms from automated submissions.
- Load balancing cookies, which distribute requests among servers.
- Preference cookies set by the user, such as the chosen language or font size, but only if the user made the choice.
- The cookie that stores the choice made in the banner: without it the banner would return on every page.
The test is necessity: does the cookie serve the service the user is using right now? If yes, it is strictly necessary. If it serves the site owner for purposes other than that service, it is not, however useful it may be.
What profiling cookies are
Profiling cookies build a profile of the user, based on the pages visited and behaviour, in order to show content or advertising in line with their preferences. They may be set only after freely given, specific, informed and documented consent. Profiling cookies include the advertising cookies of Google Ads and Meta, those of retargeting systems, those of marketing automation platforms and in general all cookies that follow the user from one site to another. If these cookies are already in the browser before consent, the banner is useless: the installation has already happened.
The case of analytics
Statistics cookies, such as those of Google Analytics, sit in between and are the most common source of mistakes. Several authorities, including the Italian Garante and the French CNIL, allow audience measurement without consent only if all of these conditions are met:
- The cookies produce aggregated statistics for a single site and do not follow the user across several sites.
- The IP address is masked, at least in its last octet, before storage.
- The third party providing the tool does not combine the data with other information and does not use it for its own purposes.
- The data is not passed on to anyone other than the site owner.
The most widely used tools do not meet all of these conditions: Google Analytics, in its standard configuration, requires consent and must be classified as a statistics cookie to be blocked until the user chooses. The CNIL has published a list of audience measurement tools, such as Matomo in a specific configuration, that are exempt under strict conditions; in Germany, under Section 25 of the TDDDG, reach measurement with cookies generally requires consent.
First party and third party
A second distinction concerns who sets the cookie. First-party cookies are set by the domain of the site you are visiting; third-party cookies by a different domain, such as an advertising platform or a YouTube video embedded in the page. This distinction does not change the consent rules: a strictly necessary third-party cookie does not need consent, a first-party profiling cookie does. What changes is responsibility: the site owner is accountable for the third-party cookies the site sets, and must state in the cookie policy who the third parties are and where to find their privacy notices.
How to classify the cookies on your site
The most reliable method is to look at what actually happens in the browser. Open the site in a private window, open the developer tools and check the cookies present before touching the banner: at that moment only the strictly necessary ones should be there. Then accept everything and compare. For each cookie note the name, domain, duration and purpose, and assign it to one of the four categories banners use: necessary, functional, statistics, marketing. The functional, statistics and marketing categories require consent and each must be acceptable or refusable separately. Repeat the check every time you add a plugin, a pixel or a widget: cookies change more often than you think.
How Konsento handles it
Konsento's scanner does this work for you: it visits the site, detects the cookies present, recognises them from a database of known cookies and assigns them to the correct category. The banner blocks the scripts and iframes of the categories subject to consent until the user chooses, while strictly necessary cookies keep working. The cookie policy is generated from the actual list of cookies found and is updated after every scan you run. All of this is included in a one-time licence of 86 euros per domain, no subscription, with a 15-day free trial: konsento.cloud/en/register. Want to see first which cookies your site sets today? The free scanner shows you in thirty seconds: konsento.cloud/en/verifica-conformita.