Implement a TCF v2.2 CMP integration checklist: purposes, vendors, LIA tests, and audits.
- User
Implement a TCF v2.2 CMP integration checklist: purposes, vendors, LIA tests, and audits.
Assistant
The user wants an implementation checklist for TCF v2.2 (Transparency and Consent Framework) CMP (Consent Management Platform) integration. This checklist needs to cover four specific areas:
- Purposes
- Vendors
- LIA (Legitimate Interest) tests
- Audits
I need to structure this as a practical, step-by-step guide for a developer or product manager implementing a CMP on a website or app.
Understanding TCF v2.2: TCF v2.2 introduced some specific changes compared to v2.0/v2.1:
- It requires more specificity on Purposes (renaming some, removing some).
- Legitimate Interest (LI) is much stricter now. CMPs cannot offer LI as a legal basis for certain purposes (specifically Purposes 3, 4, 5, and 6). Only Consent is allowed for these. LI is generally discouraged for Google products and restricted for many others.
- Vendor flexibility is tighter.
- The UI/UX needs to be very clear (no dark patterns).
Drafting the Checklist Sections:
1. Configuration & Purposes (The "What")
- Input: The Global Vendor List (GVL).
- Action: Define which purposes are active.
- v2.2 Nuance: Purposes 3, 4, 5, 6 (Access/Storage of info) must be Consent only. LI is forbidden for these.
- Special Purpose 1: Security/Fraud (always on, no consent needed but must be disclosed).
- Feature: Sale of Data / Sharing of Data (acting as a TCPA/Sale signal if relevant).
2. Vendor Management (The "Who")
- Scope: Full vendor list vs. Curated list.
- Mapping: Vendors must declare their purposes. If a vendor claims LI for Purpose 4, the CMP must technically enforce that they can't actually rely on it if the user doesn't consent (though technically the GVL is updating to reflect v2.2 rules).
- Google: Specific handling for Google Advertising Products (they have specific requirements regarding LI).
- Downstream: Ensure the tcString is passed to vendors.
3. LIA (Legitimate Interest Assessment) Tests (The "Legal Basis")
- Concept: Before a publisher can assert LI for a vendor, the publisher (or the CMP acting on their behalf) needs to have conducted an assessment.
- V2.2 Change: CMPs are now required to prevent publishers from setting LI for Purposes 3-6.
- Checklist item: Does the CMP UI actually block the LI toggle for those restricted purposes?
- Checklist item: Is the default state of LI "Off"? (It must be).
4. Audits & Validation (The "Verification")
- Tooling: IAB TCF Validator.
- Signal: The
tcString. decoding it to ensure bits are correct. - Tag: Google Tag Manager (GTM) or wrapper integration.
- Logging: Keep records of consent (proof).
5. UI/UX Requirements (Crucial for TCF compliance)
- Do Not Sell / Share links (if in California/US).
- "Reject All" must be as easy as "Accept All".
- Layer 1 (Banner) vs. Layer 2 (Detailed preferences).
Refining the Structure: I'll organize this into a logical flow: Pre-integration setup, CMP Configuration (Purposes/Vendors), LIA/Technical Logic, and Post-Launch Validation.
Self-Correction during drafting: I should mention specific Purpose IDs (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) because the rules differ between them. Purpose 1 (Cookies) is consent only. Purposes 3-6 are consent only in v2.2. Purpose 2, 7-10 can be LI (with caveats).
Detailed Breakdown:
-
Section 1: Purposes & Legal Basis Configuration
- Focus on the "Flexibility" concept.
- Highlight the v2.2 Purposes 3, 4, 5, 6 restriction.
- Mention Special Feature 1 (Geolocation).
-
Section 2: Vendor Integration
- Selecting vendors (Allow All vs. Select Specific).
- Checking the GVL (Global Vendor List) versioning.
-
Section 3: Legitimate Interest (LIA) Logic
- This is the trickiest part. The Publisher (website owner) is liable for LI. The CMP provides the tool.
- Checklist: Did you perform the LIA? (Publisher responsibility).
- Checklist: Is LI defaulting to false?
- Checklist: Is LI disabled for P3-6?
-
Section 4: Audits & Validation
- IAB Validator.
- Cookie scanning.
- tcString decoding.
-
Section 5: UX/UI (The visual layer)
- v2.2 is strict about "Reject All" visibility.
Final Polish: The tone should be professional and directive. Use checkboxes or bullet points for the "checklist" feel.
Let's assemble the response based on these thoughts. I will ensure the distinction between Consent and Legitimate Interest is clear, and that the v2.2 specific restrictions are highlighted.
Specific v2.2 constraints to double-check:
- Purpose 1 (Store/Access info on device): Consent only.
- Purpose 3 (Ad selection personalization): Consent only.
- Purpose 4 (Content selection personalization): Consent only.
- Purpose 5 (Measurement): Consent only.
- Purpose 6 (Ad selection basic): Consent only.
- Purpose 2, 7, 8, 9, 10: Can be LI or Consent.
Wait, let me verify Purpose 6 in v2.2. In v2.1, Purpose 6 was sometimes LI. In v2.2, the IAB Europe clarified that Purposes 3, 4, 5, and 6 cannot be established on the basis of legitimate interest. They must be consent. Purpose 2 (Basic Ads) can be LI. Purpose 7 (Performance/Measurement) - Wait, no. Let's stick to the core v2.2 change: Purposes 3, 4, 5, and 6 are Consent-only. Purpose 1 was always consent only. Purpose 2 allows LI. Purpose 7 (Market Research) allows LI? No, usually P7, P8, P9, P10 are strictly about consent or have specific nuances. Actually, standard practice for v2.2:
- Consent Only: Purposes 1, 3, 4, 5, 6.
- Flexible (Consent or LI): Purposes 2, 7, 8, 9, 10. (I will stick to the most conservative and common interpretation).
Refining the LIA part: The prompt asks for "LIA tests". This usually means: "Test if the CMP correctly handles the logic where LI is asserted."
- Test if LI is off by default.
- Test if LI is hidden for P3-6.
- Test if the user can toggle LI on/off for valid purposes.
Okay, ready to generate. This checklist outlines the technical and operational requirements for implementing a IAB Europe Transparency & Consent Framework (TCF) v2.2 compliant Consent Management Platform (CMP).
TCF v2.2 introduces stricter requirements for transparency, specifically regarding the use of Legitimate Interest and the clarity of user choices.
Phase 1: Purposes & Special Features Configuration
In TCF v2.2, the legal basis options have changed. You must configure your CMP to enforce these rules.
- Purposes 3, 4, 5, & 6 (Consent Only):
- Verify that the CMP does not allow Vendors or the Publisher to set a "Legitimate Interest" (LI) basis for these purposes.
- Rule: These purposes (Personalization, Content Selection, Measurement) strictly require Consent.
- Purpose 1 (Cookies):
- Ensure Purpose 1 is set strictly to Consent. (LI is not valid for storing/accessing cookies).
- Purposes 2, 7, 8, 9, & 10 (Flexible):
- Configure these to allow either Consent or Legitimate Interest.
- Ensure the CMP allows the Publisher to set a "Legitimate Interest" claim for these purposes (e.g., Purpose 2: Basic Ads).
- Special Feature 1 (Precise Geolocation):
- Ensure this gate appears before any geolocation data is passed to vendors.
- Special Feature 2 (Active Fingerprints):
- Ensure this is strictly opt-in (Consent only) and off by default.
Phase 2: Vendor Management & Scanning
A CMP is only compliant if it accurately reflects the vendors actually loading on the page.
- Vendor Scanning:
- Implement a discovery mechanism (crawler) to detect which TCF vendors are present in your ad stack or code.
- Ensure the CMP automatically adds detected vendors to the consent UI list.
- GVL Update Frequency:
- Configure the CMP to fetch the Global Vendor List (GVL) at least daily to ensure new vendors or policy changes are reflected immediately.
- Vendor Retention:
- Implement logic to retain consent for vendors that have been removed from the GVL for a grace period (usually 48 hours) to prevent breaking the ad stack, unless the user re-consents.
- Google Consent Mode v2 Integration:
- Ensure the CMP maps TCF signals to Google’s
ad_storage,ad_user_data, andad_personalizationsignals correctly based on the consent choices.
- Ensure the CMP maps TCF signals to Google’s
Phase 3: Legitimate Interest (LIA) Tests
TCF v2.2 places the burden on the Publisher to prove that Legitimate Interest is valid. The CMP must perform logical tests before asserting LI signals in the TC string.
- LIA Test 1: Purpose Check:
- Logic: Is the purpose being claimed one that allows LI (Purposes 2, 7–10)?
- Action: If Purpose is 3, 4, 5, or 6 Set LI signal to
false.
- LIA Test 2: Vendor Legitimacy:
- Logic: Does the specific Vendor declare LI as a legal basis in the GVL?
- Action: If Vendor says "Consent Only" in the GVL Set LI signal to
falsefor that vendor, even if the Publisher wants it on.
- LIA Test 3: The "Purpose 2" Test (Basic Ads):
- Logic: Can you prove the user reasonably expects to see ads?
- Implementation: Ensure the CMP has a publisher-facing setting to disable LI for Purpose 2 if the content is sensitive or the user model is strictly subscription-based.
- LIA Default State:
- Verify that Legitimate Interest signals are OFF by default in the CMP configuration unless explicitly enabled by the publisher.
Phase 4: User Interface & UX (The UI)
The v2.2 policy emphasizes "Equal Prominence" and "Dark Pattern" avoidance.
- Equal Prominence:
- Ensure the "Reject All" button is visually distinct and equally easy to click as "Accept All."
- Check: Do not make "Reject All" smaller, lighter, or require extra clicks compared to "Accept All."
- Layer 1 (First Layer) Requirements:
- Does it list Purposes clearly?
- Does it clearly state that "Vendors" may use the data (link to vendor list)?
- Layer 2 (Detailed View) Requirements:
- Can users toggle Purposes ON/OFF individually?
- Can users toggle Vendors ON/OFF individually?
- Is there a "Search" bar for vendors?
- Retention Periods:
- Ensure the UI displays the "Cookie Renewal" or "Data Retention" period for each vendor/purpose.
Phase 5: Audits & Technical Validation
Before going live, validate the technical output of the CMP.
- TC String Validation:
- Use a decoder (e.g., IAB Europe’s TC String decoder) to inspect the output string.
- Verify that the
PurposeConsentsbitfield matches your UI choices. - Verify that
PurposeLegitimateInterestsbits are0for Purposes 3, 4, 5, and 6.
- Transparency & Consent Parameters:
- Verify
isServiceSpecificis set correctly (True if only for your app/site, False if cross-context). - Verify
OutOfBandallowed vendors (if used).
- Verify
- Audit Logging:
- Ensure the CMP stores a record of the user's consent history (Timestamp, TC String version, User Interface variation shown) for compliance proof.
- Post-Consent Event:
- Verify the CMP fires a
tcloadedoruseractioncompleteevent immediately after choice so that tag managers (GTM) can fire the correct tags.
- Verify the CMP fires a
Summary of TCF v2.2 Critical Changes
If you are updating from v2.0 or v2.1, strictly check these three items:
- Purposes 3, 4, 5, and 6 are Consent Only.
- "Reject All" must have equal visual weight to "Accept All."
- Vendors cannot rely on LI for "security/fraud" (Purpose 10) if the user objects, unless strict legal exemptions apply.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.