Update: Global consent for TCF is no longer allowed under the GDPR and is removed as an option.
When implementing TCF with Complianz, you will get the following option;
Do you want to integrate TCF specifically for your website or use global settings? We will explain the difference below. Before we start explaining these, there’s another one in TCF that is not included in Complianz, which is “Group-Specific” – which is a collection of websites in an organization or organizations, but not globally.
Global consent in TCF
The Transparency and Consent Framework consists of a set of technical specifications and policies to which publishers, advertisers, technology providers, and others can conform to and create a so-called digital advertising chain. When you configure TCF for global consent, these user settings are set for all participants (publisher’s websites) in the TCF. For example; If you visited Domain A with global consent and approved consent for all vendors, your next visit on Domain B with global consent will automatically approve consent for the shared vendors. Only the difference in Domain B will require consent. Global consent can therefore also be explained as “Shared Consent in Digital Advertising Chain.”
Consent will be stored with an EU-consentv2 cookie on consensu.org, which is a domain handled by IAB to oversee implementation.
Consent Specific to your Website
If you choose “Consent specific to your website,” consent will not be stored on the shared domain by IAB, as explained above, but in the browser of your website visitor. You will see a new cookie called cmplz-tcf-consent, which saved the settings specifically for your website. This will not change functionality, but consent on your website will not count towards other publishers who use global consent.
