Industry News

AdSense Is Now Picking Your Consent Message Based on Revenue

By Paul Lovell · September 14, 2026 · 4 min read

Google has documented a feature called consent optimization in AdSense that decides, per visitor, which consent message to show — based on which one is likely to make you more money.

In Google's own words, it "shows your site visitors the consent message that's most likely to drive revenue based on past performance and session data." It applies to traffic from the European Economic Area, the UK and Switzerland, and it's controlled by a setting called Optimize my consent message in the setup section of your European regulations message.

What it's actually choosing between

There are two message types, and the difference between them is not cosmetic.

A standard message is the blocking consent prompt most people picture: the visitor has to make a decision before they get on with using the site. A limited message is non-blocking — Google describes it as a way of monetising users who are unlikely to generate high revenue from personalised advertising. The visitor isn't forced into a decision; you serve non-personalised ads instead.

The trade-off Google is optimising across is a familiar one. Limited messages earn less per user but face far less friction. Standard messages earn more from the people who consent, but fewer people get that far. Consent optimization is Google running that calculation per session rather than making you pick one posture for your whole audience.

One documented constraint matters: if you've turned off legitimate interest controls, Google won't serve limited messages at all. You've removed one of the two options, so there's nothing left to optimise between.

The part nobody has documented

Alongside this, a second control — Maximize message coverage — has started appearing in AdSense's Privacy & messaging section. Barry Schwartz spotted it in the UI, and it's worth naming him because there is currently no Google help page describing it. I checked the European regulations message documentation, the consent optimization page, the CMP setup guides and Ad Manager's equivalent articles. None of them mention it.

That's an unusual state for a consent control to ship in. Everything else in this area of AdSense is heavily documented, for the obvious reason that publishers in these regions are operating under regulatory requirements and need to be able to describe what their site does.

Until Google publishes something, the honest position is that the setting exists and its behaviour is unconfirmed. Treat descriptions circulating elsewhere as inference rather than fact.

Why this deserves more than a shrug

If you run AdSense on EEA, UK or Swiss traffic, a control that varies your consent experience by visitor changes what you can truthfully say about your site.

Your privacy documentation may now be describing something that isn't happening. If your privacy policy says visitors are asked to consent before personalised ads are served, and consent optimization is quietly serving some of them a non-blocking limited message instead, those two statements have drifted apart. That's a documentation fix, not a technical one, but it's yours to make.

Your consent rate metric changes meaning. If you track consent rate as a KPI, a shift in the mix between standard and limited messages will move that number without anything about your audience changing. A rising consent rate might just mean more people are seeing a message that doesn't ask them for much.

You didn't necessarily choose this. These are optimisation controls in a section most publishers configured once and never revisited. Worth opening Privacy & messaging and looking at what's actually on.

What I'd do

Open Privacy & messaging in AdSense and read the current state of both controls before deciding anything. Note which are on.

Then decide deliberately rather than by default. Revenue optimisation on consent messaging is a legitimate choice, and for a lot of publishers it will be the right one. But it's a choice with a compliance surface attached, and the setting being on because it defaulted on is a worse position than the setting being on because you looked at it.

If you have a legal or DPO function, tell them this exists. The mechanism — varying the consent experience by predicted revenue — is exactly the kind of detail they'd rather hear from you in September than from a regulator later.

And on Maximize message coverage: leave it alone until Google documents it, unless you're willing to own behaviour you can't currently describe.

Sources