Google GPDR同意.AdMob错误:检测到IAB TCF v2.0错误我们在一个或多个网站或应用程序上的IAB TC字符串中检测到问题 [英] Google GPDR Consent. AdMob Error: IAB TCF v2.0 errors detected We've detected an issue on your IAB TC string on one or more of your sites or apps

问题描述

实施google

在官方文档故障排除指南中，外观如下:

但是没有有关如何通过SDK进行操作的信息.

您知道如何解决此问题吗?看起来在这种情况下，我为欧盟用户失去了所有流量.

谢谢.

解决方案

免责声明:这只是我的经验按现状" ，也许我错过了一些重要信息，请让我知道！

在应用更新后也出现了此错误，最后经过几次尝试后，该错误消失了.我不是GDPR专家，只是想分享我的经验，也许(希望)有更好的解决方案.

我尝试过的操作(不要这样做，它并没有消除AdMob错误):

• 在AdMob控制台中禁用个性化广告
• 删除UMP库并发布更新
• 删除有错误的广告单元并发布更新

每次尝试后我仍然收到错误消息.我知道，如果没有新的错误出现，它需要一些时间才能消失，但是几天后错误计数正在增加，甚至新添加的广告单元也在报告中，但是我在没有UMP lib的应用程序版本中添加了它们.阅读一些

因此，接下来，我发布了应用程序更新，并在应用程序启动时清除了TCF字符串:

 私人乐趣clearTcfData(context:Context){val prefs = PreferenceManager.getDefaultSharedPreferences(context)val tcfKeys = prefs.all.keys.toList().filter {it.startsWith("IABTCF"，true)}如果(tcfKeys.isNotEmpty()){prefs.edit {tcfKeys.forEach {remove(it)}}}} 

然后不久，我在TCF错误报告中看到的错误减少了，大约10天后，TCF错误标语消失了.另外，我再次启用了个性化广告，因为这不会造成问题.总而言之，最适合我的解决方案是:

• 用旧的欧盟同意书库替换
• 在应用启动时清除其余的TCF字符串
• 发布并等待

After implementing google UMP SDK to get consent for EU users I faced following error on AdMob (iOS and Android apps):

IAB TCF v2.0 errors detected We've detected an issue on your IAB TC string on one or more of your sites or apps. These errors may affect your ability to serve ads to European users. A detailed report is available for you on the EU user consent page.

In downloadable .csv file I see the following:

In official documentation troubleshooting guide looks following:

But there is no info how to do this through SDK.

Do you know how to fix this? As it looks like I loosing all traffic for EU users in this case.

Thank you.

解决方案

DISCLAIMER: this is just my experience "AS IS", maybe I'm missing some important details, then please let me know!

Also had this error after app update, and finally after few attempts it has disappeared. I'm not an expert in GDPR, just want to share my experience, maybe (hope) there is a better solution.

What I've tried (don't do this, it didn't removes AdMob error):

• Disable personalize ads in AdMob console
• Remove UMP lib and release an update
• Remove ad units with errors and release an update

After every of this attempts I still got error message. I know it requires time to disappear, if no new errors comes, but after few days errors count was increasing, and even newly added ad units were in report, but I added them in app version without UMP lib. After reading some TCF strings docs, I realized that TCF strings still exist on user devices and AdMob uses them. After logging all default shared prefs I've got something like:

So, next I released an app update, with TCF strings cleanup on app launch:

private fun clearTcfData(context: Context) {
    val prefs = PreferenceManager.getDefaultSharedPreferences(context)
    val tcfKeys = prefs.all.keys.toList().filter { it.startsWith("IABTCF", true) }
    if (tcfKeys.isNotEmpty()) {
        prefs.edit {
            tcfKeys.forEach { remove(it) }
        }
    }
}

Then soon I saw less errors in TCF error report, and after about 10 days TCF error banner has disappeared. Also I enabled personalized ads again, cause this doesn't cause a problem. To sum up, solution that works for me is:

• Replace UMP lib with old EU consent lib
• Clear remaining TCF strings on app launch
• Release and wait

这篇关于Google GPDR同意.AdMob错误:检测到IAB TCF v2.0错误我们在一个或多个网站或应用程序上的IAB TC字符串中检测到问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！