Google has removed the TCF error report from AdSense as a standalone downloadable report and moved the consent string errors it contained into the Policy center, where they now appear under the "Regulatory issue" category. The change is documented on an AdSense Help page dated October 15, 2026. It affects every AdSense publisher whose ad requests come from the European Economic Area, the UK or Switzerland.

In Short

Google used to keep a separate downloadable list in AdSense showing when a website's cookie consent setup sent broken or missing consent signals for visitors in Europe, the UK and Switzerland. That list is gone, and the same errors now appear in the Policy center, the AdSense dashboard that already shows which sites have problems limiting ads. You now look for consent problems in the same place as policy violations, but Google has not said whether every detail from the old report came along.

What changed on October 15

The Help page announcing the change runs to a single paragraph. According to Google, the TCF error report "surfaced detected issues on the IAB TCF TC strings associated with ad requests from the EEA, UK, and Switzerland." That report "has been removed as a standalone downloadable report" from its previous location, which Google describes as the Brand Safety, Content, Blocking controls, then European regulations page.

The errors themselves have not been retired. According to Google, "These TCF errors are now surfaced in the Policy center, bucketed under the 'Regulatory issue' category." Google frames the move as consolidation, stating that it simplifies "efforts to identify, understand, and resolve issues that impact ad serving on your sites and apps."

That is the full extent of the announcement. The page does not list which error codes are carried over, whether the report's seven-day detection window still applies, or whether the old column structure survives inside the Policy center. No transition period is mentioned. The page is headed "TCF error report migration to Policy center" and carries the date October 15, 2026, one day before this article.

What the old report contained

The report Google removed had a specific structure. When PPC Land covered two new error types added to the TCF report on September 30, 2024, the downloadable file listed errors detected over the previous seven days, with each row showing the domain or mobile app ID, the ad unit path, the error code, the number of times the error occurred and the date it was last detected. That update added error 9.1, for a TCF consent management platform present on a request but not certified by Google, and error 10.1, for requests from the EEA, UK or Switzerland that carried no TCF signals at all.

The error code catalogue grew again this year. In March 2026, when TCF v2.3 enforcement began, Google added error 1.4, triggered when the Disclosed vendors segment of a TC string is missing, malformed or does not include Google's vendor ID, 755. The same coverage described the AdSense path to the report as Brand Safety, then Content, then Blocking controls, then Manage European regulations, which matches the location Google's new Help page gives for the report it has now removed.

Those codes carry different consequences. Some push a request into limited ads, which disable personalization but still deliver creatives; certification failures under code 9 lead to non-personalized ads; others narrow the set of eligible vendors without limiting ads at all. A publisher's response depends on knowing which code fired, on which domain and in which ad unit.

How the Policy center works

The second Help page, an undated "Overview of the Policy center," describes the destination. According to Google, the Policy center "helps you discover, understand, and resolve issues that affect ad serving on your sites." It is reached by signing in to AdSense and selecting Policy center from the menu.

Three kinds of information are listed on the page. Publishers can see which of their sites have issues that affect ad serving. According to Google, "This includes cases when the ad requests are coming from your pages that you've embedded into the sites with issues." Publishers can also read descriptions of each issue, with screenshots where available. And they can find out how to request a review once a problem is fixed.

The main view is a list of affected sites. According to Google, "Issues are automatically sorted by the number of ad requests they affect." The list can also be sorted by site name, status, type of issue or date reported. A Download CSV button offers two choices, Download all items or Download filtered view, producing a file "that contains the details of your sites with issues."

At the top of the page sits an account health summary. According to Google, it shows "how many sites are affected by issues, how many issues are policy issues, regulatory issues, or advertiser preferences, and what percentage of your ad requests are restricted or disabled." Each category can be clicked to filter the list. A separate figure shows the share of account traffic serving without restrictions, though Google notes that clicking it does not create a filter, "because filters are only available for sites with issues."

Each row has a Fix link in the Action column. That link opens an Issue details page with a description of the problem and instructions for resolving it. Notifications go out through two channels: according to Google, when its systems detect a policy or other issue on a site, the publisher is "notified in the Policy center and via email."

Where the regulatory label came from

The three-way split between policy issues, regulatory issues and advertiser preferences is not new to Google's publisher products. In April 2025, Google replaced the old "Must fix" label in the AdMob Policy center with those same three categories. Regulatory issues were described at the time as stemming from geographic requirements such as GDPR or US state privacy laws. They did not have to be fixed, but they restricted which ad types could serve. A missing consent management platform for European users was the example given.

Screenshots arrived earlier still. Google added screenshots to the Ad Manager and AdSense Policy centers in May 2022, reached through the same Fix link and Issue details page described in the current overview. AdSense for Search publishers gained a Policy center of their own in November 2023.

Why the move matters for publishers in Europe

Placing consent errors next to policy violations changes how they are seen. Under the old arrangement, a publisher had to know the TCF error report existed, navigate to a settings page under Brand Safety and download a file. The Policy center is where Google already sends publishers when ads are restricted, and where the account health summary reports the share of ad requests that are restricted or disabled. A consent misconfiguration now sits in that same queue, sorted by the volume of ad requests it affects.

Will that make consent errors easier to catch? For publishers who never opened the old report, the errors are now harder to miss. For those who relied on it, the answer depends on detail Google has not yet published. The old report was organized by error code and ad unit path; the Policy center is organized by site. If the Regulatory issue entries collapse several error codes into one site-level item, a publisher running a consent management platform across many ad units could find it harder to pinpoint which TC string fault is costing revenue. Neither Help page resolves that question.

The financial stakes are not trivial. Limited ads serve without personalization, and ad personalization is what lifts yield on European inventory. PPC Land's coverage of AdSense consent settings has cited industry figures putting personalized ads at 50 to 70 percent more revenue than non-personalized ones, a range that is not Google's own. Requests that fail more serious checks can go unfilled entirely, earning nothing.

The migration lands at the end of a dense run of consent-related changes for AdSense publishers in the EEA, the UK and Switzerland. Google removed the account-level non-personalized ads control in May 2025, steering publishers towards TCF signals instead. It announced mandatory migration to TCF v2.3 on November 3, 2025, with enforcement beginning in early March 2026.

The changes did not stop there. In April 2026, Google auto-enrolled AdSense publishers in consent message optimization, effective May 7. In June, it set August 3 as the start of IP-based ad measurement and personalization in the EEA, UK and Switzerland, adding a new feature to its TCF registration. In July, Google revised the default list of ad technology partners for the third time since spring 2025. And on September 9, it gave publishers 30 days to opt out of automatic fallback consent messages, which Google's own consent tool serves when an ad request arrives without a TC string. That control could activate from October 9, less than a week before the TCF error report was removed.

The two changes interact. A request arriving without a TC string was exactly the condition error 10.1 was built to flag. With fallback messages now enabled by default for many accounts, some of those errors may stop appearing at all, because Google's own message fills the gap. Publishers using a third-party certified CMP are not enrolled in the fallback by default, and for them the Policy center becomes the main place to spot missing or broken signals.

Enforcement outside Google

The framework itself is under tighter supervision. IAB Europe's 2025 compliance report, covered by PPC Land in March 2026, recorded 587 vendor enforcement procedures in 2025, up from 269 the year before, and 51 procedures against consent management platforms. Eighty percent of policy audits failed the requirement to disclose TC string storage in the secondary layer of the consent interface. Those figures concern IAB Europe's own enforcement rather than Google's ad serving decisions, but they show how often the strings that feed AdSense are malformed or incomplete.

Gaps between the two Help pages

The two documents do not line up perfectly. The migration notice says the errors help resolve issues "on your sites and apps." The Policy center overview refers only to sites throughout: it lists "which of your sites have issues," sorts by "site name" and describes a CSV of "your sites with issues." AdSense is a web product, and the reference to apps may reflect wording shared with AdMob and Ad Manager, where the TCF report has also existed. Google has not said whether app-level TCF errors in those products are moving as well.

The overview also says publishers are notified by email when an issue is detected. The migration notice does not say whether TCF errors, now classed as regulatory issues, will trigger those emails. Under the old arrangement, the report had to be downloaded; there was no indication that each new error generated a message.

Finally, the migration notice describes the old location as the "European regulations" page, while PPC Land's March 2026 coverage recorded the menu label as "Manage European regulations." The difference is likely a matter of labelling rather than a separate page, but it is a reminder that the Help page was written after the report had already gone.

Timeline

Summary

Who: Google, through AdSense Help documentation, affecting AdSense publishers that receive ad requests from users in the European Economic Area, the UK and Switzerland.

What: The TCF error report, which listed problems with IAB TCF TC strings attached to ad requests, has been removed as a standalone downloadable report. The errors now appear in the AdSense Policy center under the "Regulatory issue" category, alongside policy issues and advertiser preferences.

When: The Help page documenting the change is dated October 15, 2026. The companion Policy center overview page carries no date.

Where: In AdSense, the report previously sat under Brand Safety, Content, Blocking controls, then European regulations. The errors now appear in the Policy center, reached from the main AdSense menu.

Why: According to Google, the move simplifies "efforts to identify, understand, and resolve issues that impact ad serving." Google has not said whether error codes, ad unit detail or the seven-day detection window carry over to the Policy center.