# IAB TCF The IAB Europe is the European-level association for the digital marketing and advertising ecosystem. They created the transparency and Consent Framework (TCF) which is a GDPR consent solution that standardizes consent collection mostly for ad tech providers. The main goal of the TCF is to help all parties in the digital advertising chain ensure that they comply with the EU’s GDPR and ePrivacy Directive when processing personal data or accessing and/or storing information on a user’s device, such as cookies, advertising identifiers, device identifiers, and other tracking technologies. It indicates to the users which data are collected and how the website and its partners will use them. It also gives everyone a common language to simplify communication with users. While using the TCF, CMP must allow the user to make granular and specific consent choices for purposes on one side, and vendors on the other. You can have a closer look at their policies: [https://iabeurope.eu/iab-europe-transparency-consent-framework-policies](https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/) (Appendix B. C. c. iii) ### Vendors List - IAB Europe Standard list: [Vendors List – IAB Europe](https://iabeurope.eu/vendor-list/) JSON formatted list for vendors: JSON formatted list for purposes: ### How do I know if I need to use the IAB integration or not? Deciding whether to use the IAB integration depends on several factors: 1. **Type of Vendors:** If you are working with vendors that are part of the IAB's Transparency and Consent Framework (TCF), it's advisable to use the IAB integration. This framework helps in managing consent across different vendors who adhere to the IAB standards. 2. **Compliance Needs**: The IAB TCF is designed to help organizations comply with GDPR and ePrivacy regulations when processing personal data or accessing/storing information on a user's device. If your operations fall under these regulations and involve such data processing, using the IAB TCF could be beneficial. 3. **Operational Requirements:** If your digital advertising operations require a standardized method to manage user consents and data processing permissions across multiple vendors, the IAB TCF provides a structured and widely accepted framework for doing so. 4. **Vendor Requirements:** Some vendors may specifically require IAB TCF compliance for integration. Check with your vendors if they are part of the IAB TCF and if they require integration through this framework. ### Consent notice requirements to benefit from the IAB TCF integration Using our IAB TCF integration requires displaying a standard text on the 1st layer of your banner. A standard text is a notice text that is validated by the [IAB Europe](https://iabeurope.eu/) as a text that enforces [TCF policies on the content of the notice (initial layer)](https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/#_________Appendix_B_User_Interface_Requirements___________). When you enable the IAB integration in the console, Didomi automatically provides you with a standard text that has already been validated by the IAB. You won't be able to change your text directly in the console (> customization > content editor > specific settings). The text field will be grayed out). These TCF policies guide the content of the 1st layer of your banner, which must follow a certain number of rules including: * Complete list of data processing and legal bases used by your organization and its partners * Information about the data stored and accessed from the user device by your organization and by third parties * The indication that both your organization and third parties (to be listed) are processing personal data from the user * Examples of personal data being processed * Information on legitimate interest as a legal basis and the possibility for users to object For more detailed information, don’t hesitate to read the [IAB documentation](https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/#:~:text=and%20Publisher%20restrictions.-,Appendix%20B%3A%20User%20Interface%20Requirements,-A.%20Scope) (Appendix B: User Interface Requirements). If you don’t like Didomi’s standard text, your DPO/ legal team can help you draft an alternative compliant text. If so, you can submit your alternative text by following [this process](/consent-management-platform-cmp/frameworks-regulations/iab-tcf/add-custom-standard-text-to-consent-notice.md) to our support team. It will be reviewed and validated by our legal department before being made available in the console. This allows a slight customization of the 1st layer while benefiting from IAB integration. --- # 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.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.