Common Questions: What changed in v2?

What changed in v2?

Version 2 of the policy and technical specification marks significant updates to better support GDPR legislation and enhance the user experience, while remaining flexible to account for unique scenarios within the framework.

Changes across the Framework are listed below and grouped according to supporting documentation for: the TC String, the Global Vendor List, and the CMP API.

Within the Transparency and Consent String (TC String)

• Special jurisdiction handling using publisher country code
• Publisher TC String for publisher legal basis establishment*
• Publisher restrictions added
• Legitimate interest establishment signals added
• “Right to object” to legitimate interests support added
• Out-of-Band (OOB) legal basis support
  • Created Allowed Vendors TC String segment
  • Created Disclosed Vendors TC String segment
• Enhanced TC String Encoding
  • TC String segmentation (core, publisher, oob segments)
  • Revised Macro support
• Text revisions based on requests for clarification/consistency

Within the Global Vendor List (GVL) Format

• Includes recent policy updates
• Better wording to distinguish between “policy version” and “GVL version”

Within the Consent Management Platform API

• Event Listeners, Support for CMP status change, such as when a user makes an active choice, and a new TC string is generated
• New parameter order
• New function signature name
• Inclusion of passing “version” argument
• Addition of in-app “command” for in-app specific values
• Updates to support special jurisdiction, handling Out-of-Band (OOB) , and publisher restrictions