Is a cookie banner still required in 2026?
It depends on what your site drops. Here is how to find out.
Consent is required as soon as a site writes information to or reads information from the visitor’s device for a purpose that is not strictly necessary for the service requested: that is Article 5(3) of the ePrivacy Directive 2002/58/EC, still in force on 1 September 2026.
What is moving in 2026 is not the law, it is a proposal. It has not been adopted.
Find your case. The answer fits on one line.
The banner does not depend on your measurement tool. It depends on everything your page loads.
Your site only loads cookieless measurement
There is no analytics cookie to get accepted. What remains is checking that nothing else writes to the device: an embedded video, a map, a live chat, a remote font, a forgotten pixel. That is where the answer is decided, not in the name of your analytics.
Your site loads advertising pixels
Yes, you need a banner. Pixels from Meta, Google Ads, LinkedIn or TikTok write to the device for advertising purposes, and that placement requires freely given, informed consent. On 1 September 2025 the CNIL fined Google 325 million euros and Shein 150 million euros on exactly this ground.
You sell on Shopify or WooCommerce
Yes. Shopify itself sets the _shopify_y cookie, which its own cookie policy lists under Reporting and Analytics with a one-year lifetime. A cart, loyalty or retargeting app adds more. Switching measurement tools does not remove those lines: the platform sets them, not you.
What actually binds you, today.
Five facts in force, each with its date and its source.
| Fact | Date | Source |
|---|---|---|
| The European Commission withdraws the draft ePrivacy Regulation. The ePrivacy Directive 2002/58/EC itself stays in force. | 11 February 2025 | European Commission, COM(2025) 45 final, annex of withdrawals, entry 29 |
| Google excludes from its advertising product audiences any EEA visitor whose consent choice is not passed to it. | early March 2024 | Google Analytics Help, article 14275483 |
| The ad_user_data and ad_personalization parameters are added to analytics_storage and ad_storage in consent mode. | November 2023 | Google for Developers, Consent Mode documentation |
| The CNIL fines Google 325 million euros and Shein 150 million euros for trackers set without valid consent. | decisions of 1 September 2025 | CNIL, decisions SAN-2025-004 (Google) and Shein |
| Shopify lists its _shopify_y cookie under Reporting and Analytics, with a one-year lifetime, and sets it on your store itself. | policy read on 1 September 2026 | Shopify, Cookie Policy (shopify.com/legal/cookies) |
Checked on 1 September 2026. The reason for the withdrawal is written as such in the Commission annex: no agreement is expected from the co-legislators, and the proposal is outdated in view of recent technological and legislative developments. Two of the five rows are not law: Google and Shopify impose their rules on their customers, not on the European Union. We keep them together because a site is subject to both in the same way.
Don't change anything for a text that doesn't exist yet.
The Digital Omnibus would change a lot. It changes nothing until it is adopted.
The Digital Omnibus is a draft regulation put forward by the European Commission on 19 November 2025 under reference COM(2025) 837; on 1 September 2026 it has not been adopted and therefore produces no legal effect.
- Tabled on
- 19 November 2025, by the European Commission, under reference COM(2025) 837.
- Where it stands
- Still under negotiation. The Council has not reached a qualified majority: the Cypriot presidency withdrew its compromise text before handing over to Ireland on 1 July 2026. The European Parliament has not settled its position.
- What has already been dropped
- Article 88b, the browser-level consent signal provision, disappeared from the Council position of 18 June 2026. Only the European Parliament could bring it back.
- Application
- 2027 at the earliest, and only if the text is adopted. In the proposal, Article 88a would apply 6 months after entry into force and Article 88b 24 months after.
- What it changes for you today
- Nothing. A proposal creates no obligation and removes none. Any page announcing a new rule for 2026 has the status wrong.
What Article 88a would do
It would move the rules on consent for device access out of the ePrivacy Directive and into the GDPR, with a limited list of purposes usable without consent: transmitting a communication, the service requested, security, and aggregated first-party audience measurement. It would also require one-click refusal and ban re-asking for six months after a refusal.
What Article 88b would do
It would make consent signals sent at browser level legally binding: a choice expressed once, honored by sites, with no prompt on every visit. It is the only measure in the proposal that would genuinely have removed banners. It was dropped from the Council position of 18 June 2026.
Why you should not count on it
The audience-measurement exemption in Article 88a is drafted in narrow terms: aggregated information about the usage of an online service, solely for that service’s own use. Several law firms have noted that tools measuring across several customers or services would probably not fall within it. Building a plan on a text that is not adopted, and on the narrowest exemption in that text, would be two bets at once.
One reason for a banner, gone. Not all of them — we say so.
Snorklee removes one reason for a banner. Not all of them. Saying so is what makes the rest credible.
What it removes
To count a visit, Snorklee neither writes to nor reads from the device: no cookie, no localStorage, no sessionStorage. The triggering condition of Article 5(3) of the ePrivacy Directive is therefore not met, independently of any exemption. There is no Snorklee analytics cookie to get accepted.
The only thing it can write
An opt-out flag, snorklee_optout, and only if the visitor switches it on themselves. That is the exercise of a right, not audience measurement, and Snorklee also honors the Do Not Track and Global Privacy Control signals. We would rather write it here than let you find it in the source.
What it does not remove
Snorklee removes one reason for a banner, not all of them. An advertising pixel, an embedded video, a map, a live chat, or a Shopify store that sets _shopify_y on its own: each keeps its own obligations. If your page loads anything besides Snorklee, the banner question is still wide open.
What we do not do
We do not give legal advice. This page sets out dated, sourced facts, with a link to each source so you can read it yourself. Qualifying your own site is up to you, with your counsel or your data protection officer.
How the measurement works without cookies: the technical page. What it costs: pricing. The cookies Shopify sets on its own: the detailed article.
Frequently asked questions about cookie banners.
Is a cookie banner required in 2026?
Does the Digital Omnibus abolish cookie banners?
Where does the Digital Omnibus stand on 1 September 2026?
Is Consent Mode v2 mandatory?
Does Shopify force me to have a cookie banner?
Will the ePrivacy Regulation still change the rules?
Does a site that only uses Snorklee need a banner?
Are regulators still fining sites over cookies?
Must Consent Managers register in November 2026 in Europe?
Count every visitor, not only the ones who accept.
€8 per month ex. VAT: 200,000 pageviews, 10 sites, everything included. Hosted in Paris.