Google Just Changed Who Gets to Bid on Your Inventory — Did You Notice?

On June 5, 2026, Google quietly updated its list of “commonly used” ad technology partners for AdSense publishers. No big announcement. No email with a subject line that says “action required.”

For most publishers, nothing visibly changed. The ads kept running, the revenue kept coming in, and life went on.

But under the hood, something important shifted — and if you’re a publisher who has never actively managed your Ad Technology Partners list, there’s a real chance your revenue was affected without you knowing it.

What Are Ad Technology Partners and Why Do They Matter?

When a user visits your site in Europe (or the UK, or Switzerland), your Consent Management Platform (CMP) collects consent on behalf of the vendors who want to serve, target, or measure ads on your inventory. The key word is “on behalf of” — your CMP needs to know which vendors to ask consent for.

Google provides AdSense publishers with a “commonly used set” of Ad Technology Partners — a pre-curated list of the vendors that Google determines are most relevant to publisher revenue globally. If you’ve never touched your partner settings, this list is your default. It’s the list your CMP is working from.

As of June 5, that list changed.

What Changed? and What It Means for Your Revenue?

Google has been running this experiment since April 20, testing an updated partner set with a subset of publishers. The June 5 date marked the potential full rollout — meaning the changes are either already live on your site or about to be.

Here’s the part that matters:

Any vendor removed from the commonly used set no longer automatically receives user consent through your default configuration.

No consent = no personalized ads = significantly lower CPMs, or no bid at all from that vendor.

And Vise Versa — vendors added to the list now receive consent they didn’t have before, which could actually improve competition and CPMs on your inventory.

The current list has 199 partners. It includes the biggest names in programmatic — Amazon, The Trade Desk, Microsoft, Index Exchange, Magnite, PubMatic, Criteo, LiveRamp, DoubleVerify, and many others.

But the specific mix matters, and if a vendor you depend on for meaningful revenue was quietly dropped, you’d have no way of knowing unless you checked.

The Problem Nobody Is Talking About

Most publishers have never looked at their ATP list.

They set up AdSense, accepted the defaults, and moved on.

I don’t say that as a criticism — the whole point of the commonly used set is to make this easy for publishers who don’t have the time or technical resources to manage it actively.

But “easy” and “optimized for your specific revenue” are not the same thing.

There’s another layer of complexity here worth understanding, The 199 partners on Google’s list fall into two consent frameworks — the IAB Global Vendor List (GVL) and Google’s own Additional Consent (AC) specification.

Some vendors are on both, Some are only on the Google AC spec — and if your CMP only handles the standard IAB Transparency and Consent Framework, those vendors may not be receiving proper consent signals regardless of what the list says.

This is the kind of thing that causes revenue leakage that’s genuinely hard to diagnose.

Your fill rate looks fine, Your CPMs look normal, But a meaningful slice of demand isn’t actually bidding because the consent chain broke somewhere nobody looked.

What You Should Do Right Now

1. Check your current partner list. Log into your AdSense account → Privacy & messaging → European regulations settings → “Your ad partners.”

This shows you exactly who is and isn’t receiving consent on your inventory today.

2. Know who your top demand partners are. Cross-reference the ATP list with the vendors driving meaningful revenue for you, If any of them are missing, add them manually via a custom list.

3. Consider taking control with a custom list. Once you select “Do not automatically include commonly used ad partners,” you create a locked custom list that won’t change when Google updates the default, You’ll need to manage it yourself — but you’ll stop being surprised by changes you didn’t approve.

4. Talk to your CMP provider. Ask them specifically whether they handle both IAB TCF and Google Additional Consent, If they only support one, you may have a consent gap for a significant portion of your demand partners.

The Bigger Picture

This is the third significant change Google has made to publisher-side ad infrastructure in less than a year — after the TCF v2.3 migration mandate in February 2026 and the replacement of the ad networks blocking control with the authorized buyers system in November 2025.

The direction of travel is clear: Google is standardizing and streamlining how consent and demand flow through publisher inventory.

Each change is framed as being “beneficial for publishers.” Some of them genuinely are, But the cumulative effect is that publishers who aren’t paying attention are losing more control over their own supply chain with each update.

The publishers who come out of this period in the best shape will be the ones who understand what’s running on their inventory — not the ones who trusted the defaults and hoped for the best.

If you haven’t looked at your ATP settings recently, today is a good day to start.

Have questions about how the ATP changes might be affecting your specific setup? Feel free to reach out.