Google has quietly retired the standalone TCF error report inside AdSense. Publishers who monetize traffic from the European Economic Area, the UK or Switzerland now need to look for broken consent signals in a different place: the Policy center.
Where the consent errors went
The downloadable report used to live under Brand Safety, then Content, then Blocking controls, then European regulations. It listed TCF consent string issues detected over the previous seven days, including the domain or app ID, ad unit path, error code, error count and last detection date.
As of October 15, that file is gone. Google’s Help page says the errors themselves have not disappeared. Instead, they appear in the Policy center, grouped under the ‘Regulatory issue’ label.
These TCF errors are now surfaced in the Policy center, bucketed under the ‘Regulatory issue’ category.
Google frames the move as consolidation, intended to make it easier to spot and fix issues that limit ad serving.
What this means for publishers
The Policy center is already where Google lists sites with problems that restrict or disable ads. It sorts issues by the number of ad requests they affect and shows an account health summary with policy, regulatory and advertiser preference categories. Each issue has a Fix link and instructions for requesting a review.
That is both good and bad. Publishers who never downloaded the old report may now notice consent errors earlier. Publishers who relied on the report may lose detail. Google has not confirmed whether the old error codes, ad unit level breakdown or seven-day detection window made the move.
Key open questions:
- Will individual TCF error codes still be visible, or will they be collapsed into one site-level Regulatory issue?
- Does the seven-day detection window still apply?
- Will app-level errors move as well, or only site issues?
- Will each new consent error trigger the Policy center email notification?
Why consent errors hit revenue
TCF consent errors are not cosmetic. Depending on the code, they can push ad requests into limited ads or non-personalized ads, or leave requests unfilled. Industry figures cited in previous coverage put personalized ads at 50 to 70 percent more revenue than non-personalized inventory.
The shift also lands after a dense year of consent changes: TCF v2.3 enforcement began in early March, fallback consent messages could activate from October 9, and IAB Europe’s compliance report recorded 587 vendor enforcement procedures in 2025, up from 269 the year before.
What to do now
Open the AdSense Policy center and filter for Regulatory issues. Make that part of your weekly account routine, especially if you use a third-party certified CMP and rely on TCF signals. If you see a consent issue, fix it, then request a review through the Policy center details page.
Until Google publishes the missing detail, watch your European revenue by ad unit and keep your own record of consent errors you find.
Source: PPC Land
