Chapter navigation
The four declaration families: Purposes / Special Purposes / Features / Special Features
consentRole & classification
The four declaration families on the Transparency & Consent Framework (TCF) side: Purposes (11 current + 12–24 reserved) / Special Purposes (2) / Features (3) / Special Features (2). Field models differ: Purposes have both Consent and Legitimate Interest (LI) channels, Special Features are Opt-In only.
- GPP section
- §2 (TC String Core)
- Four families
- P×11 · SP×2 · F×3 · SF×2
- Status
- GVL v2 / TCF 2.2
String & field layout
| Family | Count | Legal basis | TC String encoding |
|---|---|---|---|
| PurposesPurposes | 1–11 current (12–24 reserved) | Consent + Legitimate Interest (LI) dual channel; LI deprecated for P3–P6 in 2.2 | PurposesConsent (24 bits) + PurposesLITransparency (24 bits) bitfields |
| Special PurposesSpecial Purposes | 2 | Legitimate Interest only; always applies, not user-objectable | Not encoded in the TC String (always applies) |
| FeaturesFeatures | 3 | Always active, supporting the purposes; no independent legal-basis toggle | Not encoded in the TC String |
| Special FeaturesSpecial Features | 2 | Explicit opt-in (consent) required | SpecialFeatureOptIns (2 bits) bitfield |
PurposesP1–P11
- P1Store and/or access information on a device
- P2Use limited data to select advertising
- P3Create profiles for personalised advertising
- P4Use profiles to select personalised advertising
- P5Create profiles to personalise content
- P6Use profiles to select personalised content
- P7Measure advertising performance
- P8Measure content performance
- P9Understand audiences through statistics or combinations of data from different sources
- P10Develop and improve services
- P11Use limited data to select content
Special PurposesSP1–SP2
- SP1Ensure security, prevent fraud, and debug
- SP2Technically deliver ads or content
FeaturesF1–F3
- F1Match and combine data from other data sources
- F2Link different devices
- F3Identify devices based on information transmitted automatically
Special FeaturesSF1–SF2
- SF1Use precise geolocation data
- SF2Actively scan device characteristics for identification
Purpose names follow the official wording of IAB Europe TCF Policies / the Global Vendor List (TCF 2.2 revision); 11 was added in 2.2 and 12–24 are reserved.
Carriage & access
Of the four families, only Purposes (Consent + LI bitfields) and Special Features (the Opt-In bitfield) are actually written into the TC String Core segment; Special Purposes and Features always apply and are not encoded. For the bit-level layout see TC String bit-level breakdown →
Version deltas
TCF 2.2 / Global Vendor List v2 官方措辞
Wording follows the Global Vendor List (GVL) v2 (the TCF 2.2 baseline), the same source as the purposes/specialFeatures already integrated in spec.json. Later GVL revisions adjusted Special Purposes wording (e.g. SP1 became 'Ensure security, prevent and detect fraud, and fix errors', SP2 became 'Deliver and present advertising and content', and 'Save and communicate privacy choices' was added); the GVL version must be stated when citing and v2 wording must not be mixed with later revisions.