[Apps] Common issues around Consent Mode and how to resolve them

This type of issue typically arises when Google Consent Mode has been implemented incorrectly and Consent Mode flag analytics_storage is not being set. Please review the following technical documentation section to ensure that you have implemented Google Consent Mode correctly.

Additionally, please ensure you are working with the latest SDK version, as we continuously improve our functionality. For better overview of recent changes, please refer to our changelog.

TCF error 3.3 means that the TCstring is considered invalid, typically if it is over 13 months old. If you are seeing TCF error 3.3 in your Google dashboards, typically this means that some portion of end users have not interacted with the privacy banner for over 13 months.

In order to avoid such issues, please double-check your configuration and review how you have set up banner resurface settings, as these are vital to appropriate banner display. The settings overview can be seen below on the attached image. You can review how each setting impacts the banner resurface in more detail in this Help Center article.

While there is no recommended approach we can provide, a popular setup for configurations outside of EU, such as configurations assigned to the global rule of a Geolocation Ruleset, is setting up a Google Consent Mode based on a GDPR configuration.

Please follow the guidance provided in our technical documentation for the GDPR implementation of Google Consent Mode.