| Table of Contents | ||
|---|---|---|
|
Usercentrics Web TCF CMP
As stated in our Google Consent Mode tech doc, “Google also supports the IAB's TCF framework with its ad systems. Consent Mode is meant to be used by advertisers not using a TCF CMP implementation. However, we also recommend implementing the Consent Mode default state into your website if you are using a TCF implementation. This recommendation is due to the fact that the necessary consent signals for for TCF CMPs (if you’re working with Google) we also recommend you:
Follow Step 1 of the documentation to set default consent states in the Google Consent Mode context
Activate Advertiser Consent Mode in the Admin Interface of your TCF CMP configuration / SettingID under Configuration → CMP Settings tab → Advertiser Consent Mode, if you’d like Google to infer consent for
ad_storage,ad_user_dataandad_personalization
...
That means we recommend following Step 1 of the documentation, even if you are using TCF.
Learn more about:
...
The Transparency & Consent Framework
...
based on its TCF Purposes → Google Consent Mode storage types mapping (details from Google).
Add TCF Vendor 755 (Google Advertising Products) to your TCF CMP configuration / SettingID in the Admin Interface under Service Settings → Global Vendor List tab.
Usercentrics Web TCF CMP
If you’re using our Apps SDK (for native apps) or Unity SDK (mobile games), we recommend reading the associated technical documentation and following it closely to use Google Consent Mode in an app-specific context with your TCF CMP: