On 21 October 2026, EU ambassadors agreed the Council's negotiating position on the Digital Omnibus, the package that rewrites parts of the GDPR, the ePrivacy Directive and several other digital laws. For cookies, the headline is simple: the rules stay in the ePrivacy Directive, but the list of purposes that need no consent grows from two to six, and audience measurement is on it.
That matters to anyone who runs web analytics. It also does not change anything today. This article explains what the Council agreed, how it differs from the Commission's November 2025 proposal, what the audience-measurement exemption actually requires, and what you should (and should not) do now.
Not legal advice. This article describes a legislative text that is still being negotiated. Check with your DPO or a lawyer before changing how you ask for consent.
Where the Digital Omnibus stands in November 2026
The Digital Omnibus started as a European Commission proposal published on 19 November 2025 (reference COM(2025) 837, procedure 2025/0360(COD)). Like every EU regulation, it needs the agreement of both the Council and the European Parliament.
- Council: the Permanent Representatives Committee (Coreper) agreed the mandate on 21 October 2026. The text was circulated the next day as Council document 14756/26, and the Council announced it in a press release.
- European Parliament: the file sits with a joint ITRE/LIBE committee, with Aura Salla (EPP) and Marina Kaljurand (S&D) as rapporteurs. At the time of writing the Legislative Observatory lists its status as awaiting committee decision.
- Next step: once Parliament has a position, the three institutions negotiate a final text in trilogues.
So what follows is the Council's opening position, not the final law.
What the Commission proposed for cookies
The Commission wanted to move the cookie rules out of the ePrivacy Directive and into the GDPR, through two new articles:
- Article 88a GDPR would have required consent for storing or reading personal data on a person's device, with four exceptions: transmitting a communication, providing a service the user explicitly asked for, security, and "aggregated information about the usage of an online service to measure the audience", carried out by the controller "solely for its own use". Refusing had to be possible with a single click, and a refusal would block a new request for six months.
- Article 88b GDPR would have obliged websites to accept consent and refusals sent as automated, machine-readable signals, and obliged large browser makers to provide the means to send them.
What the Council changed
The Council's mandate deletes both articles. Instead, it rewrites Article 5(3) of the ePrivacy Directive, the provision behind today's cookie banners. The core rule stays: storing or reading information on a user's device needs consent. What changes is the list of exceptions.
Six purposes that need no consent
Under the Council text, storing or reading information on a device, and the processing that follows for the same purpose, is lawful without consent "to the extent it is solely related to and strictly necessary for" one of these purposes:
- Transmission of an electronic communication over a network.
- Providing a service, including its functionality, explicitly requested by the user.
- First-party audience measurement: creating anonymous aggregated information about the usage of an online service to measure its audience (more on the conditions below).
- Media audience measurement under Article 24 of the European Media Freedom Act, provided personal data are pseudonymised after collection and the user is not tracked outside the measured service.
- Security: maintaining or restoring the technical security of the service or of the device.
- Contextual advertising measurement: measuring the display and performance of ads based only on the content of the page or a single search query, without personal data, profiling or tracking across sites.
Today's Article 5(3) has only the first two. Purposes 3 to 6 are new at EU level.
Four months, one click
When a site does ask for consent, the user must be able to refuse "with a single-click button or equivalent means". After a refusal, the site may not ask again for the same purpose for at least four months. After consent, it may not ask again for as long as that consent remains valid.
No browser signals
With Article 88b gone, there is no obligation for websites to honour automated consent signals and no obligation on browser makers to send them.
Enforcement and timing
Member states would have to make their GDPR supervisory authority the enforcer of Article 5(3). That would end the split in countries where a telecom regulator enforces the cookie rules today. Member states would get 24 months after adoption to transpose the new rules; that figure is still in square brackets in the text, so it can move.
Commission proposal vs Council position at a glance
| ePrivacy today | Commission (Nov 2025) | Council (Oct 2026) | |
|---|---|---|---|
| Where cookie rules live | ePrivacy Art. 5(3) | GDPR Art. 88a and 88b | ePrivacy Art. 5(3), rewritten |
| Consent-free purposes | 2 | 4 | 6 |
| Audience measurement exempt | No (national variations) | Yes, by the controller for its own use | Yes, by the provider or on its behalf |
| Single-click refusal | Not in the text | Yes | Yes |
| Wait after a refusal | Not regulated | 6 months | 4 months |
| Browser consent signals | No | Yes (Art. 88b) | No |
| When it applies | In force | 6 months after entry into force | Transposition within 24 months (bracketed) |
The audience-measurement exemption, read closely
For analytics, purpose 3 is the one that counts. The Council's wording allows consent-free measurement only when all of these hold:
- the output is anonymous aggregated information about how the service is used;
- the purpose is measuring the audience of that service, not of other sites;
- it is done by the provider of the service, or by a third party on its behalf, so an analytics vendor acting as a processor qualifies;
- the data collected is not processed for another purpose, not shared with third parties, and not combined with data from third parties.
On top of that sits the general test: the access must be "solely related to and strictly necessary for" this purpose. An analytics setup that also feeds an ad network, builds cross-site profiles or reuses visitor data for the vendor's own products falls outside it.
This is close to what some regulators already allow. France's CNIL has long exempted audience measurement from consent under strict conditions, and the Netherlands has a similar exception for analytics with little or no privacy impact. The Digital Omnibus would turn that patchwork into one EU-wide rule.
What it does not change
Two things are worth keeping in mind:
- Article 5(3) is about the device, not just cookies. The EDPB's Guidelines 2/2023 on the technical scope of Article 5(3) (final version adopted 7 October 2024) treat tracking pixels, URL tracking and other techniques as covered too. The new exemptions apply to those techniques in the same way.
- The GDPR still applies to whatever you collect. An exemption from consent under ePrivacy does not remove the need for a lawful basis, data minimisation and the rest of the GDPR. Our GDPR guide for web analytics covers those requirements.
What this means for your website now
Nothing changes yet. Until the Digital Omnibus is adopted and transposed, today's Article 5(3) and your national implementation apply. If you use Google Analytics or another tool that sets cookies or reads device data for purposes beyond the exemption, keep asking for consent. The same goes for Google Consent Mode V2, which is about Google's ad requirements and is unaffected.
But the direction is clear. Both the Commission and the Council want first-party, aggregated audience measurement out of the consent banner. If you are choosing an analytics tool now, it makes sense to pick one whose design already fits that profile, so you do not have to migrate again in two years. Three questions to ask a vendor:
- Does the tool store or read anything on the visitor's device?
- Does the vendor reuse, sell or combine your visitors' data with other data?
- Is the output aggregated statistics, or individual visitor profiles?
And a banner has a cost today. Banners lower data quality and conversion rates, as we described in Cookie Consent Banners Are Killing Your Conversion Rate. A smaller banner, or none at all, is worth having long before the Omnibus applies.
Where ClearAnalytics fits
ClearAnalytics sets no cookies and stores nothing on the visitor's device. It counts unique visitors with a hash that rotates every day and cannot follow anyone across days or sites (how that works). The output is aggregated statistics for your own site, processed in the EU, and we do not share visitor data with third parties or use it for anything else. That is the same profile the audience-measurement exemption describes in both the Commission and the Council texts.
If you want analytics that does not depend on how the trilogue ends, you can compare the plans and start on the free tier.
We will update this article when the European Parliament adopts its position.