Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

TCF 10.1 Error in AdMob Despite Correct UMP Implementation

33 views
Skip to first unread message

captaintech

unread,
Mar 17, 2025, 1:53:58 PMMar 17
to Google Mobile Ads SDK Developers
Description of the Problem:

I am experiencing the TCF 10.1 error in AdMob, even though I have implemented Google's User Messaging Platform (UMP) correctly and am using the latest SDK versions.

I have already removed all mediation networks, waterfalls, and any third-party ad sources. Currently, I am only using AdMob ads directly.

Additionally, in the AdMob report, I see that six ad units are still being reported, but three of them were completely deleted more than three weeks ago and no longer exist in my AdMob account. However, the TCF 10.1 error is still being logged for these non-existent ad units.

Implementation Details:
  • Consent Management: I am using Google's UMP SDK to handle user consent.
  • SDK Versions:
    • Google Mobile Ads SDK:  23.6.0
    • UMP SDK:  3.1.0
  • AdMob Setup:
    • No mediation, only AdMob ads
    • No custom consent implementation, only UMP
Steps Taken to Fix the Issue:
  1. Implemented Google's UMP SDK as per the official documentation.
  2. Ensured the app requests and displays the consent form before loading any ads.
  3. Verified that the consent status is being retrieved correctly before requesting ads.
  4. Checked that the TC string is being generated by the UMP SDK.
  5. Confirmed that my app is not sending ad requests before the user provides consent.
  6. Ensured all SDKs are fully updated to the latest versions.
  7. Removed all third-party ad sources, mediation networks, and waterfalls to ensure a clean setup.
  8. Verified that no outdated or unused ad units exist in my app’s code.

Despite following all best practices, I am still receiving the TCF 10.1 error. This means AdMob is not receiving the required TCF signals, even though the UMP SDK should be handling this automatically.

Request for Help:

Has anyone encountered this issue before? Could there be a problem with how AdMob processes UMP signals, or is there an additional step I might be missing?

Any guidance or suggestions would be highly appreciated!

Mobile Ads SDK Forum Advisor

unread,
Mar 17, 2025, 9:11:20 PMMar 17
to shayeg...@gmail.com, google-adm...@googlegroups.com

Hi,

Thank you for contacting the Mobile Ads SDK support team.

After your concern is reviewed, I understand that you are facing the TCF 10.1 error. Error code 10.1 indicates that there are no TCF signals on ad requests and the request is from EEA, UK, or Switzerland but lacks TCF signals. Suggested action is to integrate with a TCF CMP that is certified by Google.

In order to investigate this issue further kindly provide us with the below information:

  • app ID
  • ad unit ID
You can provide the following details via reply privately to the author option.
 
Thanks,
 
Google Logo Mobile Ads SDK Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-03-18 01:10:35Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vHAjZ:ref" (ADR-00295064)



Reply all
Reply to author
Forward
0 new messages