When a European ad request reaches Google Ad Manager without a valid TCF consent string, Google serves limited ads, and many buyers can no longer bid the way they did. In your reports that looks like weak demand: lower eCPM in the EEA, the UK and Switzerland. The Serving restriction dimension and the TCF error report show which it is.
This matters this month for a specific reason. Google has been switching on a control called "Maximize message coverage", which shows Google's own consent message on pages where no TCF consent platform is detected. PPC Land reported that AdSense accounts were told on 9 September that automatic activation would start on or after 9 October 2026. If your European numbers moved in the last two weeks, consent belongs on the list of causes next to demand, and you can rule it in or out with one report.
Why a consent problem shows up as a demand problem
Google decides how to serve each request from the consent signal on it. When the TC string is missing, empty, unreadable or from an uncertified CMP, the request does not fail outright. It drops to a lesser serving mode, and the drop is quiet.
Limited ads are the mode most of these requests land in. Google's help page lists what still works there: guaranteed and non-guaranteed line items, and programmatic demand (Google demand, Authorized Buyers, Open Bidding and SDK bidding) as long as programmatic limited ads are switched on in your network settings. They are on by default. What stops working is anything that needs a local identifier or personal data: audience targeting, remarketing, interest-based categories, frequency caps and conversion tracking. A line item that uses any of those is not eligible for a limited ads request.
So the auction still runs, with fewer buyers able to price the impression the way they want to. Fill can hold up, because house and network line items still serve, while the average price sinks. A yield manager reading a Country report sees Germany and France soften and calls it seasonal demand.
The error codes on Google's TCF troubleshooting page tell you which signal went wrong. These are the ones that matter most for revenue:
| Error code | What happened to the consent signal | What Google serves |
|---|---|---|
| 2.1a | No TC string reached the tag because the CMP was still a stub, loading or in error | Limited ads |
| 2.1b | gdpr=1 was set but the consent string was empty |
Limited ads |
| 2.2a to 2.2c | The string could not be decoded or held bad data | Limited ads |
| 10.1 | A request from the EEA, UK or Switzerland carried no TCF signals at all | Limited ads |
| 1.4 | The disclosed vendors section required in TCF v2.3 is missing or does not include Google (vendor 755) | Google cannot use the request |
| 9.1 | The CMP is not certified by Google | Non-personalized ads |
TCF v2.3 has been mandatory for Google since 1 March 2026. A CMP that was never updated, or a custom implementation that writes an old string, produces 1.4 errors, and those requests are worse off than limited ads.
What changed in October: Google's fallback consent message
"Maximize message coverage" is a single checkbox, and it covers every site and app in the account, including those managed in AdSense or AdMob. When it is on and no TCF CMP is detected on a page, the Google Publisher Tag serves a fallback consent message to users in the EEA, the UK and Switzerland. The fallback uses default styles, the vendor list from your European regulations settings, and two buttons, "Manage Options" and "Consent". If a certified CMP, Google's or a third party's, collects consent successfully, no fallback is served.
For a network with consent gaps, that can change the numbers in either direction:
- Pages that had no CMP (a new subdomain, a microsite, an old section template) start collecting consent, so their share of limited ads should fall and eCPM should rise.
- Pages where a slow third-party CMP was mistaken for a missing one could show two banners. PPC Land lists that interaction as an open question Google has not answered. If it happens, users see two prompts, and consent rates can drop.
Either way, a step change around 9 October in one country group is more likely to be consent than demand. The report below shows which.
The report that separates consent from demand
Build this in Ad Manager reporting and save it:
- Dimensions: Date, Country, Serving restriction, Demand channel.
- Metrics: Impressions, Revenue, and eCPM as revenue per 1,000 impressions.
- Date range: 28 days, so you see the weeks before and after 9 October and compare the same weekdays.
- Filter Country to the EEA countries, the UK and Switzerland. Keep one non-European market you know well as a control.
Then read it in this order.
First, the share of impressions under the "Limited ads" value of Serving restriction, by country, week by week. If that share jumped in one country or one week, you have found your cause before looking at a single buyer.
Second, eCPM inside personalized traffic only. If it held steady while the blended number fell, demand did not weaken. More of your traffic moved into a cheaper serving mode.
Third, Demand channel inside limited ads. If Ad Exchange and Open Bidding revenue on limited ads is close to zero, check that programmatic limited ads are still switched on in your network settings. Someone may have turned them off.
Fourth, the control market. If it moved the same way as Europe, look at demand after all. Consent does not travel outside the regions that require it.
Google notes that forecasting does not treat limited ads as a separate serving mode and lumps it in with non-personalized and basic ads, so a forecast will not show you this split. The delivery report will.
Download the TCF error report
Google keeps a per-ad-unit error file for the last seven days. In Ad Manager go to Admin, then EU user consent, and click "Download TCF error report". The button only appears when errors were detected in that window, so an absent button is a good sign.
The file has five columns: domain or app ID, ad unit path, error code, error count and last detected date. Sort by error count. A large 2.1a count on one domain usually means the CMP loads after the ad call on that template, and the fix is in the page order, not in the CMP settings. A 10.1 count on a domain is a page with no CMP at all, which is the case the fallback message was built for. Any 1.4 is a CMP that needs updating to v2.3 today.
Check Prebid on its own
Everything above covers Google's tags. Prebid reads consent separately, and Google's error file will not show a Prebid problem.
The TCF consent management module waits up to 10,000 milliseconds by default for an already-discovered CMP to return a string. If the CMP times out or errors, the Prebid docs say the auction either is canceled or proceeds without consent information, depending on configuration. When the CMP does not respond in time, gdprApplies falls back to defaultGdprScope, which is false unless you set it. The TCF control module enforces purposes 1, 2 and 7 by default, and a bidder without a legal basis for purpose 2 (basic ads) can be kept out of the auction.
Open an article page from a European IP, then run this in the console:
pbjs.getConfig('consentManagement')
Check that the timeout and defaultGdprScope are what you think they are. Then filter the network tab by your bidders' endpoints and confirm the requests carry a gdpr flag and a non-empty consent string. A bidder whose bid rate fell only in Europe, while its timeouts did not change, is the Prebid version of the same consent problem.
Should you leave Maximize message coverage on?
Leave it on if any part of your network runs without a CMP, or if your error report shows 10.1 or 2.1a errors you cannot fix this week. Google's message is plain, but every user who consents through it moves that request out of limited ads.
Look harder if you run a third-party certified CMP that loads late. Test a page from a European IP with the setting on and count the banners. If you see two, fix the load order or turn the setting off and accept the gap until you do. Google's help page also says you remain responsible for a consent revocation link on your sites, and the fallback does not add one for you.
The checkbox sits under Privacy and messaging, on the European regulations message card, in Settings, in the "Maximize message coverage" section.
One thing to check tomorrow
Run the Serving restriction report for the last 28 days and look at the limited ads share by country, before and after 9 October. If it moved, download the TCF error report the same morning, while the seven-day window still covers the change, and send the top three ad unit paths to whoever owns the CMP.
Optimon reads your own Ad Manager and Prebid data each morning, so a shift like this shows up as a cause by country and serving mode, with the revenue attached, instead of a vague drop in demand.
FAQ
How do I know if my EU revenue drop is a consent problem and not a demand problem?
Run an Ad Manager report with Country and Serving restriction as dimensions. If the share of impressions under "Limited ads" went up in the EEA, the UK or Switzerland while eCPM inside personalized traffic held steady, the buyers did not leave. Your requests lost their consent signal.
What is Google's "Maximize message coverage" setting?
It is an account-level control in Privacy and messaging, under the European regulations message settings. When it is on and no TCF consent platform is detected on a page, Google's own consent tool shows a fallback message to users in the EEA, the UK and Switzerland. If your own certified CMP collects consent, no fallback message is served.
Does a consent problem in Ad Manager also affect my Prebid bidders?
Separately, yes. Prebid reads consent through its own consent management module, and its TCF control module can keep a bidder out of the auction when the string gives that bidder no legal basis for basic ads. Google's fallback setting and error report cover Google's tags, so check Prebid on its own.
Sources
- Maximize message coverage (Google Ad Manager Help)
- Troubleshooting IAB EU TCF v2.3 implementation (Google Ad Manager Help)
- Limited ads (Google Ad Manager Help)
- Google gives AdSense publishers 30 days to opt out of fallback banners (PPC Land)
- TCF Consent Management Module (Prebid.js documentation)
- TCF Control Module (Prebid.js documentation)
