
Cookies & Consent Mode v2: Ask first. Then measure what they allow.
Cookies & Consent Mode v2
Ask first. Then measure what they allow.
In Greece, any cookie or tracking technology the page does not need in order to work, such as analytics and advertising, requires prior consent. Rejecting must be as easy as accepting. Google’s Consent Mode v2 does not replace consent: it carries the visitor’s decision to your measurement and advertising tools.
Tell us about yoursKey facts
- 0
- non-essential cookies before the visitor chooses. Scrolling, carrying on browsing and closing the banner are not consent.Hellenic DPA, recommendations of 25 Feb 2020
- 4
- Consent Mode v2 signals are read by Google’s tools: ad_storage, analytics_storage, ad_user_data, ad_personalization.Google for Developers
- 2024
- Since March, without consent signals, visitors from the EEA are left out of Google’s advertising audiences.Google Analytics Help
- 1,000
- events a day from visitors who declined, for seven days, before GA4 starts estimating their behaviour.Google Analytics Help
Consent before the first cookie.
The rule sits in Article 5(3) of Directive 2002/58/EC and, in Greece, in Article 4(5) of law 3471/2006: storing information on a user’s device, or reading what is already there, is allowed only with their consent, after clear information. The only exception is what is strictly necessary for the service they asked for.
It covers every technology, not only cookies: local storage, pixels, device fingerprinting, mobile identifiers. And it applies even if you process no personal data.
The Hellenic Data Protection Authority (HDPA) spelled the rule out in February 2020. Third-party analytics, such as Google Analytics, and advertising need consent. Visitors must be able to accept or reject with the same number of clicks and from the same level, and to withdraw just as easily. The Authority recommends buttons of the same size, emphasis and colour, and refusing cannot lock the content.
In May 2022 the Authority announced an audit of 30 news and information websites whose banners had no “Reject” on the first layer and highlighted “I agree”. It gave them 15 days, and every site that received its letter complied, with one exception. In 2023 the European Data Protection Board (EDPB) listed the same practices as problematic: a missing reject option, pre-ticked boxes, colours that make refusal hard to read, cookies labelled “essential” when they are not.
Essential
Basket, login, security, load balancing, language, and storing the choice itself. No consent needed, but visitors must be told.
Analytics
Third-party visit statistics, such as Google Analytics. Only with consent.
Advertising
Campaign measurement, remarketing, social media pixels. Only with consent.
Information
For each purpose: what it does, how long it lasts, who is responsible and who receives the data.
Withdrawal
As easy as giving consent. The question is asked again after the same time, whether the answer was yes or no.
No cookie wall
Someone who refuses sees the same content as someone who accepts.

What Consent Mode v2 does, and what it does not.
Consent Mode is how your banner tells Google’s tags what the visitor decided. Version 2 adds two signals to ad_storage and analytics_storage: ad_user_data, for whether user data may be sent to Google for advertising, and ad_personalization, for whether personalised advertising is allowed.
Since early March 2024, Google has required anyone using its tools for visitors from the European Economic Area to collect consent and send it these signals, to keep measurement, personalisation and remarketing. Without them, EEA visitors are left out of advertising audiences.
It can be installed in two ways. In basic mode, Google’s tags do not load before the choice, and if the visitor declines, nothing is sent. In advanced mode, they load with refusal as the default and send signals without cookies, from which Google makes more detailed estimates for your account. Because advanced mode sends data before the choice, and because the EDPB considers that Article 5(3) also covers techniques without cookies, the choice between the two is best made with your lawyer.
Consent Mode is not a banner. If you show Google ads on your own site, through AdSense, Ad Manager or AdMob, Google has required a certified consent management platform (CMP) using the IAB’s TCF since 16 January 2024. If you only advertise, you can use one of Google’s partners or your own banner, and it is your responsibility that it follows the law.
ad_storage
Whether cookies or identifiers may be stored for advertising.
analytics_storage
Whether cookies or identifiers may be stored for analytics, such as the length of a visit.
ad_user_data
Whether user data may be sent to Google for advertising.
ad_personalization
Whether personalised advertising, such as remarketing, is allowed.
What you measure when the visitor says no.
When a visitor declines, there is no cookie and no remarketing for them. What you see about their visits is, at best, an estimate.
In advanced mode, Google estimates conversions and behaviour from the cookieless signals, with models that learn from those who consented. To do so, GA4 needs at least 1,000 events a day from visitors who declined, for seven days, and 1,000 visitors a day who consented, on seven of the last 28 days. Many small e-shops never reach those thresholds. And estimates appear in reports, not in audiences or data exports.
That is why we also measure from your side. Orders are always recorded in your e-shop, whatever the cookies, and they are the steady yardstick against which to check what the platforms report. Server-side measurement, with a container in a space you control, gives you control over what leaves for each platform.
It does not bypass consent, though. Google’s tags on the server read the consent state and adjust to it, and wherever the rule requires consent in the browser, it requires it there too.
Observed
What is measured from visitors who consented: per visit, exact, available for audiences.
Modelled
What Google fills in with models for those who declined, if the account has enough volume. In aggregate, not per visitor.
Server-side
An intermediate point in a space you control, which decides what is sent where. It runs only for visitors who consent.
Your own data
Orders, enquiries and newsletter sign-ups with explicit consent. They count however the cookies change.
How we got here.
- 25 Feb 2020
The HDPA publishes its cookie recommendations: consent for analytics and advertising, equal refusal, no cookie wall.
- 9 May 2022
The HDPA announces an audit of 30 websites over the reject option on the first layer.
- 17 Jan 2023
The EDPB adopts the report of its cookie banner taskforce.
- 16 Jan 2024
Google requires a certified TCF CMP from sites showing its ads to visitors in the EEA and the UK.
- Mar 2024
Without consent signals, EEA visitors are left out of Google’s advertising audiences.
- Oct 2024
The EDPB finalises its guidelines on the technical scope of Article 5(3): pixels, fingerprinting, URL tracking.
- 19 Nov 2025
The European Commission proposes moving the cookie rules into the GDPR, with one-click refusal. Until it is adopted, today’s rules apply.
What to do now, in order.
First a picture of what happens today, then the settings.
List what the page sets today before any choice: cookies, local storage, pixels, third-party scripts.
Split them into essential and non-essential. Whatever is not needed for what the visitor asked for waits for consent.
Put “Accept” and “Reject” on the first layer, with the same size and colour, and choices per purpose with no pre-ticked boxes.
Connect the banner to Consent Mode v2, with every signal on refusal until the visitor chooses, and decide on basic or advanced mode with your lawyer.
Check that every tag respects the choice: Google, Meta, TikTok, heatmaps, chat. One that slips through is enough.
Put a link to change the choice on every page, and update the cookie policy with purpose, duration and recipients.
Keep records: what was asked, when, and what the visitor chose.
From the banner to the signal.
We work on the site and the accounts you already have. The legal judgement belongs to your lawyer. We make sure the site does exactly what your policy says.
Audit of what is set today
A scan before and after each choice: which cookies, which scripts, to which recipients. On one page, with priorities.
A CMP with equal choices
“Accept” and “Reject” on the first layer, choices per purpose, a change link on every page, in Greek and English.
Consent Mode v2
The four signals to Google Ads and GA4, refusal by default, in the mode you decide, and a check that they arrive correctly.
Tag clean-up
What is not used goes. What stays waits for the consent that belongs to it, Google’s, Meta’s and every other tool’s.
Server-side measurement
Where it makes sense for your volume: a container in a space you control, for cleaner data, running only for visitors who consent.
Documentation
A cookie table with purpose, duration and recipients, the CMP settings and a change log. For you and for your lawyer.
Start with usPart of Advertising
What people ask most.
Yes. Under the HDPA’s recommendations, third-party analytics such as Google Analytics is allowed only with consent. Without it, GA4 stores no cookies. In advanced Consent Mode it sends only cookieless signals, used for estimates.
The HDPA requires that visitors can refuse with the same number of clicks, and from the same level, as they accept. In practice, if there is an “Accept all” on the first layer, an equal “Reject all” belongs beside it. In 2022 the Authority audited websites on exactly this point.
Not by law. Google requires it: since March 2024, to keep measurement, personalisation and remarketing for visitors from the EEA, you must collect consent and send Google the signals. Without them, EEA visitors are left out of advertising audiences.
Basic sends nothing before consent or after a refusal, and relies on a general Google model. Advanced sends cookieless signals and allows estimates specific to your account, if it has enough volume. Because advanced mode sends data before the choice, decide on it together with your lawyer.
If you show Google ads on your site through AdSense, Ad Manager or AdMob, yes: since 16 January 2024 for visitors from the EEA and the UK, using the TCF framework. If you only advertise, it is not mandatory: you can use a Google partner or your own banner, as long as it follows the law.
No. It changes the route the data takes, which passes first through a point you control. Google’s tags there read the consent state, and the EDPB considers that Article 5(3) also covers techniques without cookies. It is a complement, not a way around.
No. According to the HDPA, refusing must not block access to the content, so a “cookie wall” is not allowed. And the question is asked again after the same time, whether the answer was yes or no.
Possibly. On 19 November 2025 the European Commission proposed, in its Digital Omnibus package, to move the rules into the GDPR, with one-click refusal, a six-month wait before asking again after a refusal, and respect for browser settings. At our last check the proposal had not been adopted, so today’s rules apply.
Sources
- Directive 2002/58/EC (ePrivacy), Article 5(3) (EUR-Lex)
- Hellenic DPA: recommendations on cookies and trackers, 25 Feb 2020 (in Greek)
- Hellenic DPA: action on informational websites’ cookies, 9 May 2022
- EDPB: Guidelines 05/2020 on consent
- EDPB: report of the cookie banner taskforce, 17 Jan 2023
- EDPB: Guidelines 2/2023 on the technical scope of Article 5(3)
- Google for Developers: consent mode overview
- Google Analytics Help: consent settings for EEA visitors
- Google Analytics Help: behavioural modelling
- Google AdSense Help: certified CMP requirements
- Google for Developers: server-side tagging and consent mode
- European Commission: the Digital Omnibus proposal, 19 Nov 2025
Facts last checked: 23 September 2026






















