Skip to content

TCF Framework Configurations

Framework Settings

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.

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.

Resurface UI, to remind users of their right to opt-out after 13 months

While utilizing this option is not strictly required by the Transparency & Consent Framework 2.2, some TCF vendors may still require renewal of the TC string after 13 months.

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

Using this function means the TCF framework will only apply to users in the EU and EEA (utilizing the gdprApplies function in the __tcfapi). The CMP can still be surfaced globally, just without a TCF signal outside applicable jurisdictions.

If this function is deactivated, the TCF signal applies wherever the CMP is used. To apply TCF in the UK and Switzerland, deactivating this function is required. Controlling 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.