AdSense moves TCF errors to the Policy center: where publishers should look now

Google has moved AdSense TCF errors into the Policy center, retiring the standalone downloadable report from its previous location. An October 15 announcement places the errors under the Regulatory issue category.

For publishers, the immediate change is where to investigate consent-string problems. The announcement does not introduce a new TCF deadline or establish a change in earnings. An old troubleshooting checklist may now send a team to a report that has been removed.

What moved, and who should check

The AdSense announcement concerns detected issues in IAB Transparency and Consent Framework consent strings, commonly called TC strings, associated with ad requests from the European Economic Area, the United Kingdom and Switzerland.

That scope follows the relevant ad requests. A publisher based elsewhere can still have traffic from those regions; the language of its website does not by itself settle whether the report matters to its operation.

Google identifies the previous location as Brand Safety → Content → Blocking controls → European regulations. The new destination is the Policy center. Its wording describes the migration as implemented, but does not give a separate rollout-completion date or establish the interface seen in every account.

Start with the specific issue

Google's Policy center documentation explains that publishers can inspect affected sites, filter issue categories and open Fix for details and resolution instructions. For a TCF problem, use the reported issue to determine what needs attention before changing the consent setup.

Where the issue involves the consent management platform, or CMP, its provider may need to investigate configuration or the string being produced. Moving the report does not itself repair that underlying problem, and the migration is not evidence that every publisher has an error.

Consent errors should also remain separate from invalid traffic investigations. Our guide to investigating invalid AdSense traffic addresses that different workflow. Neither a reporting move nor a consent diagnosis should become a catch-all explanation for a revenue fluctuation.

CSV exports need a fresh check

The Policy center documentation offers Download CSV for all items or a filtered view. That establishes an export option, not equivalence with the retired TCF report's fields or historical coverage.

If an agency, developer or internal process consumes the old file, compare the available columns with what that process requires. Historical retention and complete field parity were not established in the announcement or this review. Do not promise a drop-in replacement without inspecting the output.

Publishers can now update their internal instructions to point to the Policy center and record the issue details used for any investigation. The practical value of the change will depend on that workflow; Google's description of simpler resolution is a company claim, not a measured result from a publisher account.