Digital Omnibus and cookies: proposals versus rules in force

Digital Omnibus and cookies: proposals versus rules in force

On 21 October 2026, the Council of the European Union agreed its position on a proposal to simplify the EU’s digital legal framework. Its announcement included clearer or additional purposes for which consent to certain cookies would not be required, citing audience measurement among the examples.

For a business choosing analytics software, this sounds consequential. Should it change its consent interface today, switch tools or wait for a broader exemption? A negotiating mandate is not the same thing as legislation already in force.

As of 2 November 2026, file 2025/0360(COD) is still progressing through the ordinary legislative procedure. The Council has agreed a position, while the European Parliament’s legislative record reports that committee-level action is still awaited. No general exemption can be inferred from this stage.

Rules currently applicable

In France, Article 82 of the Data Protection Act governs certain trackers within the ePrivacy framework. The CNIL explains that narrowly scoped audience-measurement tools may qualify for a consent exemption under specific conditions. That is not a universal exemption for analytics.

Purposes, implementation and information practices matter. Advertising attribution, cross-site identification and broader marketing uses should not be treated as if they were automatically part of strict audience measurement.

Operationally, document actual fields, destinations, retention, purposes and configuration before taking a compliance position.

The Digital Omnibus proposal

The European Commission proposed a package of digital simplifications in November 2025, including proposed amendments to the ePrivacy Directive and GDPR.

On 21 October 2026 the Council adopted a negotiating mandate. Its statement proposes retaining cookie rules in the ePrivacy framework while clarifying and expanding certain purposes not requiring consent. It cites service provision, audience measurement and device security as examples.

The announcement alone does not define every possible analytics implementation as equivalent. Exact conditions, transition provisions and implementation dates depend on a final act that does not yet exist.

Parliament must establish its position and negotiations between the institutions must conclude. Provisions may change substantially before adoption.

A reliable internal tracker should therefore separate rules currently applicable, the initial proposal, the Council’s position, Parliamentary steps, and eventually final published law.

What the Council’s statement actually covers

The October Council release addresses multiple areas: personal data, cookies and ePrivacy, incident reporting and other digital rules. It is not solely an analytics proposal.

For cookies, the Council describes keeping the ePrivacy regime while broadening or clarifying certain exceptions. Its examples include supplying a service, audience measurement and device security.

A headline claiming that “Europe abolished cookie banners” would therefore go well beyond the evidence. Some uses may become simpler in the future without every tracking purpose receiving identical treatment.

Privacy, security and transparency duties do not automatically vanish because one legal requirement related to terminal-device tracking is revised.

Why analytics teams need to separate purposes

An organisation operating five properties rarely collects data for one purpose only. It may analyse audience, conversions, technical incidents, content engagement, campaigns and authenticated product activity.

The umbrella word “analytics” hides material distinctions. Qualify each activity before deciding on configuration or a consent framework.

Proposed useDecision question
Website audience measurementIs it confined to the publisher’s measurement needs?
Technical troubleshootingWhich information is essential to identify the problem?
Marketing conversion eventsDo purposes go beyond strict audience measurement?
Advertising attributionAre data shared, joined or used for targeting?
Cross-domain analysisAre individual activities linked between properties?

The same vendor may offer multiple configurations. Provider name or cookie absence does not settle the legal analysis.

A decision checklist that works before reform

Inventory the actual technology

List scripts, pixels, storage mechanisms, events and network destinations. Separate strictly scoped audience measurement from broader marketing, product and advertising use.

Our website tracker audit can help identify technical components; supplier documentation and contractual terms remain important.

Describe each purpose plainly

“Improve the user experience” does not necessarily distinguish basic statistics from conversion marketing or individual personalisation. Write the business decision each operation is intended to support and the minimum data needed.

If a tool has several collection modes, document what each actually enables. A mode name is not evidence.

Verify deployed settings

Vendor documentation about an exemption-eligible configuration is not proof that a particular website uses it. Inspect outgoing requests, identifiers, settings and recipients.

The CNIL’s materials emphasise the importance of practical conditions and documentation. General claims of approval should never replace a site-specific review.

Keep responsibilities and evidence

Record the approved configuration, notice version, responsible persons and review date. Multi-site organisations need to know who can add events, alter collection settings or install a new third-party script.

This is as much an operational governance problem as a legal one.

Monitor the actual legislative outcome

Use the European Parliament’s Legislative Observatory and EUR-Lex rather than commentary alone. Once a final act exists, assess its conditions, commencement dates and implementation implications before changing systems.

Should a team postpone analytics selection?

Not necessarily. Business needs exist now: understandable site trends, shared reporting, restrained collection and reliable technical configuration.

Waiting for uncertain legislation can delay those improvements without producing better evidence. Prefer tools whose configuration is inspectable, data flows are documented and purposes can be kept separate.

Do not buy a promise about future law. Evaluate what the supplier can demonstrate today.

What privacy-first analytics can realistically offer

Pomelo’s privacy-first approach centres on limited collection, clear governance and cookieless measurement by default. That can be relevant to a team’s choices, but it does not justify claims such as “no banner in all circumstances” or “automatically exempt”.

Review actual purposes, configuration and applicable rules. A possible future reform should not be treated as a product feature.

What to watch next

The consequential signals are progress in Parliament on 2025/0360(COD), any interinstitutional agreement and publication of final law with dates of application. National and European regulatory guidance may subsequently clarify operational questions.

Until then, the CNIL’s existing material remains an important reference for audience-measurement configurations in France.

Communicate legislative uncertainty inside the organisation

Regulatory announcements can create different expectations. Marketing hears “fewer banners”; engineering imagines simpler configuration; the data-protection lead wants to know the exact legal scope. These reactions are not necessarily opposed, but they concern different decisions.

Use a short review with three columns. The first lists requirements already applicable to each site, referencing the CNIL’s current guidance and the actual deployment. The second records legislative proposals and negotiating positions with official sources and dates. The third lists possible implementation changes that should remain on hold until a final applicable basis has been verified.

That format prevents two opposite mistakes. An organisation should not defer all analytics improvements simply because future legislation might change. Nor should it switch off a consent mechanism on the assumption that a proposed amendment will eventually become law in its current wording.

Multi-site teams should coordinate their interpretation while preserving property-specific decisions. A public blog, a contact form and an authenticated product can have different processing purposes, despite sharing an analytics supplier. The review record should show why each configuration was chosen rather than copying one site-wide rule everywhere.

Revisit the record on a genuine procedural milestone, not every time a commentary article repeats an old proposal.

Why identical terminology can hide different configurations

Even after a reform, teams will still need to inspect what software actually does. Two products labelled “analytics” may use different identifiers, retention periods or data recipients. Within one product, a change from basic traffic statistics to campaign attribution may alter purposes and data flows.

That is why procurement documents should identify the configuration being assessed, not simply the product name. Record the event categories, storage mechanisms, sharing arrangements and technical controls. If a vendor changes defaults, review whether the legal interpretation still matches the deployment.

This operational discipline is valuable even without new legislation: it reduces the chance that a later website redesign, agency script or marketing integration quietly expands the collection scope beyond what the original decision covered.

Conclusion: decide under the rules in force

The Council’s 21 October announcement is a meaningful policy development, not a change that automatically takes effect. It opens a negotiating stage.

The most durable preparation is clear documentation: separate purposes, useful events, limited data, known recipients and accountable configuration owners. Those practices benefit the organisation under current and future rules.

FAQ

No. As of 2 November 2026, the Council’s position is a negotiating step, not a final general exemption.

Does the Council mention audience measurement?

Yes. Its statement includes audience measurement among examples of purposes to be clarified or broadened. The final legal scope remains subject to the legislative process.

Not on the basis of this announcement alone. Actual trackers, purposes and currently applicable law must be reviewed.

Where can the process be followed?

The official file 2025/0360(COD) is available through the European Parliament’s Legislative Observatory and EUR-Lex.

Sources

Just the right measure, for all your websites.

Pomelo is opening gradually. Join the first teams measuring right and help shape what comes next.