# TCF v2.2 Summary of Purposes/Features The aim of this article is to present the purposes and features behind the [TCF framework policies](https://iabeurope.eu/understanding-the-upcoming-transparency-consent-framework-v2-2/) approved by the IAB, which came into effect on November 20th, 2023. ☝️Key Concepts: **Consent:** users must opt-in to the concerned feature/purpose before vendors may use it. \ **Legitimate Interest:** users have the option to opt-out of the specific feature or purpose in question. #### **1 - Purposes** Vendors can establish flexible purposes, on purposes 2, and 7 to 11. \ This gives more power to Publishers, through [publisher restrictions](https://7560723.hs-sites.com/knowledge/parameter-the-publisher-restrictions-in-the-didomi-console?__hstc=47810744.e3242b41382537f7888fc4b653667b70.1755531154382.1757177104072.1757183146078.48&__hssc=47810744.7.1757183146078&__hsfp=3866128941). * **Purpose 1 - Store and/or access information on a device**\ Legal basis: consent\ SDK ID: cookies * **Purpose 2** - **Use limited data to select advertising**\ Legal basis: consent / legitimate Interest\ SDK ID: select\_basic\_ads * **Purpose 3 - Create profiles for personalised advertising**\ Legal basis: consent\ SDK ID: create\_ads\_profile * **Purpose 4 - Use profiles to select personalised advertising**\ Legal basis: consent\ SDK ID: select\_personalized\_ads * **Purpose 5 - Create profiles to personalise content**\ Legal basis: consent\ SDK ID: create\_content\_profile * **Purpose 6 - Use profiles to select personalised content**\ Legal basis: consent\ SDK ID: Select\_personalized\_content * **Purpose 7 - Measure advertising performance**\ Legal basis: consent /legitimate Interest\ SDK ID: measure\_ad\_performance * **Purpose 8 - Measure content performance**\ Legal basis: consent/legitimate Interest\ SDK ID: measure\_content\_performance * **Purpose 9 - Understand audiences through statistics or combinations of data from different sources**\ Legal basis: consent/legitimate Interests\ SDK ID: market\_research * **Purpose 10 - Develop and improve products**\ Legal basis: consent/legitimate Interest\ SDK ID: improve\_products * **Purpose 11 - Use limited data to select content**\ Legal basis: consent/legitimate interest\ SDK ID: use\_limited\_data\_to\_select\_content #### **2- Special purposes** Users do not have the option to opt-out of these special purposes * **Special Purpose 1 - Ensure security, prevent and detect fraud, and fix errors**\ Legal basis : Legitimate Interest * **Special Purpose 2 - Deliver and present advertising and content**\ Legal basis: Legitimate Interest * **Special Purpose 3 - Save and Communicate Privacy Choices**\ Legal basis: Legitimate Interest #### **3- Features** The features are not conditioned on user consent, they provide more information on how vendors use users' personal data. They will be no possibility of accepting or refusing these features. * **Feature 1 - Match and combine data from other data sources** * **Feature 2 - Link different devices** * **Feature 3 - Identify devices based on information transmitted automatically** #### **4- Special features** * **Special Feature 1 - Use precise geolocation data**\ Legal basis : Consent\ SDK ID: geolocation\_data * **Special Feature 2 - Actively scan device characteristics for identification**\ Legal bases : Consent\ SDK ID: device\_characteristics ☝️Special features and purposes can be managed in stacks that will regroup them by categories. In a nutshell, here is a schema : ![iab purposes TCFV2.2-1](/files/ZO2eIqoRi5aStbH5OH2b) #### 5 - This how they should appear in your consent notice: * **First view (notice view)** :\ \- The complete list of purposes or the stacks (**1**) + purpose number 1. (**2**)\ \- Special features or stack 1 (including both special features). (**3**) \- Personalised ads and content **(1)** \- Advertising and content measurement **(1)** \- Audience research and services development **(1)** \- Store and/or access information on a device **(2)** \- Precise geolocalisation data **(3)** \- Identification through device scanning **(3)** ![stacks\_for article](https://support.didomi.io/hs-fs/hubfs/stacks_for%20article.png?width=688\&height=123\&name=stacks_for%20article.png) * **Second view (preference view)**:\ \- All purposes and/or stacks. (1)\ \- Special features. (2)\ \- Special purposes. (3)\ \- Features. (4)\ ![2nd layer](https://support.didomi.io/hs-fs/hubfs/2nd%20layer.png?width=688\&height=953\&name=2nd%20layer.png) * **Third view (vendor's view)**:\ \- List of legal basis that are linked to purposes used by every partner. (**first image**)\ \- List of additional data processing. (special purposes & features)\ \- Categories of data\ \- Device storage\ \- A link redirecting to the privacy policy of the concerned vendor.\ ![2vendor view](https://support.didomi.io/hs-fs/hubfs/2vendor%20view.png?width=377\&height=356\&name=2vendor%20view.png) ![vendorview3.](/files/7LwYPH8a4mtaV0bnSEEz) You can see [here](https://register.consensu.org/translation) the list of IAB TCF v.2.2 purposes descriptions and their translations. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-tcf/iab-tcf-2.2/tcf-v2.2-summary-of-purposes-features.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.