Resurface UI, if a new vendor was added from the GVL
If utilizing this function, the CMP will automatically resurface once it has been published after a vendor has been added to the TCF Global Vendor List. Vendors can only manually be added to the Global Vendor List.
Vendors must adhere to the consent signal. Only when a consent signal that includes the vendor is present, the vendor is allowed to operate according to the legal basis.
Not using this function results in a slower introduction of new vendors while using this function will lead to more frequent resurfacing of the CMP.
Resurface UI, if a vendor claims a previously undisclosed Purpose or changes its declared Legal Basis for a previously disclosed Purpose
TCF’s Global Vendor List is updated weekly and automatically followed by the CMP. If an existing vendor in a configuration changes their registered legal basis for TCF, utilizing this function will automatically resurface the CMP. Depending on the number of vendors, this may occur frequently. Not using this function means vendors must respect the existing consent signal until a new consent signal is granted by the user.
Not using this function results in slower adoption of new purposes or legal bases and reduces the frequency of CMP resurfacing.
Configure TCF Consent Resurfacing Interval in Admin UI
Overview
You can now control how often your users see the TCF consent banner again, choosing any interval between 1 and 13 months directly from the Admin UI.
Steps
Log in to your Usercentrics Admin UI.
Navigate to Configuration and open your CMP settings.
Locate the TCF Settings section under Legal Specifications.
Find the Resurfacing Period field and enter a number between 1 and 13 (representing months).
Click Save to apply your changes.
Publish your configuration to push the updated interval live to your users.
What to Expect
Once saved, your users will see the TCF consent banner again after the number of months you selected. For example, setting the value to 6 means a user who has already given consent will be asked again after 6 months.
If no value is set, the configuration defaults to 13 months. The system also applies the following automatic safeguards:
A value below 1 month defaults to 1 month
A value above 13 months defaults to 13 months
Note that TCF resurfacing cannot be fully deactivated — only the interval can be adjusted. This is a TCF compliance requirement managed at the Admin level.
Resurface UI, if the ATP list is updated (a vendor was added or removed)
If utilizing this function, the CMP will automatically resurface once it has been published after a vendor has been added to the Google vendor list. Using this function will lead to increased user interaction with the CMP; however, it depends on adding vendors manually.
If not using the function, the newly added vendor shall respect that they are not part of the consent signal. Only when users provide a consent signal that includes the vendor can the vendor operate according to the legal basis. This results in a slower introduction of new vendors.
Apply GDPR only to EU and EEA users
When this function is active, the TCF CMP will only show to users in the EU and EEA. For non EU/EEA users, the CMP will not surface, and it will set an automatic consent, but without any TCF signal.
If this function is deactivated, then the TCF CMP will show globally, utilizing the TCF signal for all users. To apply TCF in the UK and Switzerland, deactivating this function is required.
Further controls for where the CMP surfaces can be managed via Geolocation Rulesets.
Do not disclose Purpose 1 (Store and/or access information on a device)
Not disclosing Purpose 1 is an edge use case within TCF, applicable only to companies based in countries where consent is not required to “store and/or access information on a device.”
To use this function, the Publisher Country Code (PublisherCC) must be correctly set for a country permitting special treatment for Purpose 1 within TCF. Google Ad Manager describes this scenario as an exception to scenario 1.2 limited consent scenario.
Not disclosing Purpose 1, if based in a jurisdiction where disclosure is required, may cause issues with your TCF vendors.
Publisher Country Code
Country code of the country that determines the legislation of reference. Normally corresponds to the country code of the country in which the publisher's business entity is established.
To successfully apply TCF's "Do not disclose Purpose 1" option, it is important to carefully evaluate the Publisher Country Code settings, and ensure this corresponds to your jurisdiction. For further information, please read section "Do not disclose Purpose 1 (Store and/or access information on a device)".