1.0.0
GDPR TCF v2 Vendor List Advanced Settings
Admin access or Domain access to property (property group) with feature access to vendor list management.
The Advanced Settings modal for a GDPR TCF v2 Vendor List allow a user to configure settings that will applied to the entire Vendor List. In this article, we will cover how to navigate to the Advanced Settings modal and provide an overview for each setting.
Navigate to the Advanced Settings of an existing GDPR TCF v2 Vendor List by clicking GDPR on the top navigation bar and selecting TCF v2 from the dropdown menu.
Navigate to an existing Vendor List on the subsequent page and click Edit inline with the Vendor List name.
Click *Advanced settings*.
Use the subsequent modal to edit the Advanced Settings for the Vendor List. Click Apply Changes when finished.

Advanced Setting Glossary

In this section, we will define the individual configurations possible in the Advanced Settings of an GDPR TCF v2 Vendor List.
Setting
Description
CMP Publisher ID
Input your organization's own CMP ID (if available) to utilize your own stack descriptions or translations.
Auto Add New Vendors
Automatically adds newly discovered vendors on your properties to the Vendor List.
Note: Only available for organizations with the Vendor Scanning and Categorization feature.
Add all IAB Vendors
Automatically adds all the vendors from the IAB Global Vendor List (GVL) and keeps them updated daily.
Default IAB Vendor Consent Type
When an IAB vendor declares both consent and legitimate interest for a particular Purpose, the Vendor List will use what is selected in the provided field as the default value.
Note: If a default IAB Vendor Consent Type is configured on an individual Purpose, that value will override this setting for that particular Purpose.
Write 1st Party Cookies to Root Domain
Ensures that consent data is written to the root domain of the property (./example.com). This is useful for properties that utilize subdomains so that the data is shared across all subdomains.
This will ensure that users do not see the same consent message when moving from root to subdomain or visa versa.
Write 1st Party Cookies from the Server
Used to set first-party cookies on the site's top-level domain. It requires a domain to be setup at the same top-level domain of your site and uses CNAME to point to a Sourcepoint provided domain.
This setting should be toggled on if your organization has set up a CNAME subdomain.
Consent Cookies Expiration
The length of time (in days) consent cookies are valid.
Use Special Treatment for Purpose 1 in Countries
Certain countries in European Union may have different interpretations of GDPR legislation. If enabled then Purpose 1 will not be populated in the First Layer Message of Privacy Manager and will not be registered in the consent string.
Display Special Purposes, Features, and Disclosure Only Vendors in Message
Determines whether you will show any vendor Special Features and Special Purposes in the First Layer Message.
List IAB Purpose 1 and Custom Elements First in the Message
If enabled then any custom elements for Purpose 1 will be bumped to the top of the list of Purposes in the First Layer Message
Base Vendor Consent and Reject Actions on Vendor Grants
Vendor grants inform a publisher whether a vendor has been granted consent for all the purposes for which they are asking consent. Generally, this setting is used to manage custom vendors. When enabled, the Vendor List will fire consent and reject actions based on the vendor grant.
Note: A vendor grant only returns a true value when an end-user consents to all purposes for which your organization is requesting. If an end-user consents to only some of the purposes, the vendor grant will return a false value.
Store euconsent-v2 1st Party Cookie
A legacy cookie that Sourcepoint continues to support for early adoptees of the platform.
Manager Publisher Purposes
Click here to learn more about.
Last modified 6mo ago
Export as PDF
Copy link