AdMob and AdSense TCF errors left the old downloadable report — they now sit in Policy center as Regulatory issues
That is a change of queue, not a rewrite of the IAB Transparency and Consent Framework itself. The issues are the same: problems on IAB TCF TC strings attached to ad requests from the EEA, the UK, and Switzerland. What changed on 15 October 2026 is where you look for them.
Since 15 October 2026 the standalone TCF Error Report under Blocking controls → European regulations has been removed; the same IAB TCF string issues for EEA, UK and Switzerland traffic now appear in Policy center under “Regulatory issue” — so waiting on the old download is the wrong queue.
What AdMob’s announcement says
The AdMob announcements page dated October 15, 2026, titled “TCF Error Report migration to Policy Center,” states that the TCF Error Report “has been removed as a standalone downloadable report on the "Blocking controls" > "European regulations" page,” and that these TCF errors “are now surfaced in the Policy Center, bucketed under the "Regulatory issue" category.”
What AdSense’s announcement says
The AdSense announcements page, also dated October 15, 2026, and titled “TCF error report migration to Policy center,” describes the same move with different menu wording: the TCF error report “has been removed as a standalone downloadable report on the Brand Safety, Content, Blocking controls, then European regulations page,” and these TCF errors “are now surfaced in the Policy center, bucketed under the "Regulatory issue" category.” Do not treat the two menu paths as interchangeable.
Where to look now
Open Policy center and review items under Regulatory issue. The shared troubleshooting page for IAB EU TCF v2.3 says TCF error reporting has moved to the Policy center, and that you can view TCF errors detected over the last 7 days there. It gives the product paths as: AdMob — click Policy center; AdSense — click Policy center. The AdMob Policy center overview says you reach it from the sidebar after signing in.
What the AdMob Policy issues page lists
Regulatory issues, in that article’s words, are caused when ads on your app are affected by a country or regional regulatory requirement. For TCF on EEA, UK, and Switzerland traffic, the page describes the following (cited from the AdMob help article; AdSense Help does not publish the same article):
- No CMP — some ad requests from the EEA, the UK, and Switzerland are missing a TCF string. The page says to choose a certified CMP registered with the TCF if you have not already.
- CMP not certified — some ad requests from those regions are missing a TCF string from a certified CMP. If you have your own CMP, the page says to register it for certification; if you use a third-party CMP that has not been certified, it says to encourage that CMP to register.
- Low coverage — a majority of ad requests from the EEA, the UK, and Switzerland are missing a TCF string. The page gives two accompanying explanations: the CMP may not be implemented correctly across all of your inventory, or there is a configuration or certification issue.
- TCF errors — an error or misconfiguration related to the TCF string. Repair detail is on the troubleshooting page for IAB EU TCF v2.3; this article does not walk through those error codes.
The same AdMob page lists the related ad serving status as Restricted ad personalization: “Ad serving is limited in the EEA, the UK, and Switzerland. This may be because your app doesn’t use a certified CMP for user consent or because we’ve detected TCF errors.” That is a regional regulatory serving status, not a payout hold.
The 48-hour note (as written)
On that AdMob Policy issues page, Google states: “If you recently adopted a certified CMP, it may take up to 48 hours for this issue to be resolved and removed from the Policy center.” That sentence is attached to adopting a certified CMP. The pages cited here do not promise same-day clearance, and they do not publish a deduction amount or a fixed end date for every Regulatory issue.
What this article is not
This is not another postal-PIN or identity-verification note. Payout PIN verification is still a separate queue (AdSense $0 ID Before Postal PIN).
Not legal advice. Wording is taken or paraphrased from Google’s public AdMob and AdSense help pages as fetched on 2026-11-10. Follow what your own Policy center shows.
Sources
- AdMob Announcements, “TCF Error Report migration to Policy Center,” October 15, 2026 (https://support.google.com/admob/answer/15269273?hl=en)
- AdSense Announcements, “TCF error report migration to Policy center,” October 15, 2026 (https://support.google.com/adsense/announcements/9189068?hl=en)
- Overview of the AdMob Policy center (https://support.google.com/admob/answer/10448801?hl=en)
- Understand policy issues, regulatory issues, advertiser preferences, and ad serving statuses (https://support.google.com/admob/answer/15697162?hl=en)
- Troubleshooting IAB EU TCF v2.3 implementation, AdMob (https://support.google.com/admob/answer/9999955?hl=en)
- same article on AdSense Help (https://support.google.com/adsense/answer/9999955?hl=en).