The fight over Europe’s cookie banners just got louder. On 10 September 2026, a coalition of 19 consumer organisations, digital rights groups, businesses and academics published an open letter calling on EU institutions to bring back Article 88b—the provision that would let browsers and operating systems transmit consent signals automatically. The article was removed from the Council’s negotiating text in June.
The campaign, called “Kill the cookie banner,” wants the Irish presidency to re-insert the rule into the Digital Omnibus and wants the European Parliament and Commission to defend it. For marketers, the stakes are huge: if the provision survives, most consent pop-ups could disappear, and the consent decision would move from the page to the device.
What Article 88b would actually change
Article 88b would write into the GDPR an obligation for controllers to respect consent—or refusal—sent automatically by a browser, operating system or other user agent. Instead of clicking through a consent management platform on every session, users could set a privacy preference once at device level.
The coalition argues the current banner system produces acceptance rates as high as 90%, while only around 3% of people actually want to be tracked. Ursula Pachl, Head of Policy at noyb, put it bluntly: “There is no valid justification to drop the Commission’s proposal for Article 88b and to uphold the current cookie banner disaster.”
Six conditions the coalition wants
The open letter includes a technical annex with six non-negotiable points:
- Consent by signal must meet the GDPR’s Article 4(11) standard, with per-controller and per-purpose granularity.
- A legally valid refusal or withdrawal signal should take precedence over later consent requests.
- Gatekeepers—including Google in the browser market—should not design or control the signal infrastructure.
- The legal meaning of signals must be set in EU law, not delegated to technical standards.
- Refusal must persist until the user changes it, without re-prompting or degraded access.
- Browsers, operating systems and apps must be able to transmit signals without interference or extra tracking.
The last point is the operational detail for anyone running a consent management platform: a persistent refusal signal would reduce the re-prompting loops that currently inflate aggregate acceptance rates.
What this means for your ad stack
The immediate practical impact is zero. The June removal means the banner stays, the CMP stays, and the Transparency and Consent Framework stays. The measurement headaches attached to broken consent flows also stay. PPC Land has documented a case where Google Ads conversions fell 90% overnight because a banner collected choices without transmitting them.
But the direction of travel matters. Even if Article 88b returns in the form the coalition wants, the phase-in would be two years for websites and four years for browsers and operating systems. That means it is not a near-term planning variable—yet. It is a signal that consent infrastructure will eventually move to the device layer.
For growth and performance teams, the right move is to keep testing consent UX, audit first-party data and server-side measurement, and watch the trilogue. The ad-funded web may not lose all addressable reach, but the party that controls the device will have more influence over how permission is collected.
Source: PPC Land
