> For the complete documentation index, see [llms.txt](https://docs.avada.io/cookie-help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avada.io/cookie-help-center/integrations/iab-tcf-v2.3-compliance.md).

# IAB TCF v2.3 Compliance

### What IAB TCF is, in a nutshell

The IAB’s Transparency and Consent Framework (TCF) is a standardized system designed to enhance transparency and ensure compliance in digital advertising under GDPR regulations. It provides guidelines and technical specifications to help Consent Management Platforms (CMPs) manage user consent and preferences for data processing.

Think of it as a standardized system that tells your marketing tools exactly what data each customer has agreed to share.

{% hint style="info" %}
Check the [official website](https://iabeurope.eu/transparency-consent-framework/) of IAB for more detailed information.
{% endhint %}

Starting July 2024, to comply with the [EU User Consent Policy](https://support.google.com/adsense/answer/13554116?hl=en#zippy=%2Cgoogle-certified-cmps), publishers are required to adopt a CMP that has been integrated with the IAB Europe Transparency and Consent Framework (TCF) when serving personalized ads to users in the EEA, the UK and Switzerland 

### How to set up IAB Consent Framework on Hello Cookie

To implement the IAB consent framework, follow the below steps:

{% embed url="<https://app.arcade.software/share/jPWg3wtWOuvEXBiwbCO5>" %}
Transparency and Consent Framework integration
{% endembed %}

### How it works

A user's consent preference includes their choices and consent regarding vendors, purposes, and special features as outlined by the TCF framework. Once activated, the IAB TCF sends consent signals to vendors through the Consent Management Platform (CMP) when the user interacts with the website. These signals communicate the user's consent settings for each vendor and purpose, helping vendors determine if they have permission to process the user’s data for specific purposes.

For the cookie banner, the text in the first banner and preferences popup are longer and cannot be edited. This is due to strict wording guidelines in IAB TCF v2.3, designed to ensure users receive clear and concise information about how their data will be collected and processed. This TCF’s banner will be displayed in GDPR regions only.

\
And that’s it! You’ve successfully implemented IAB TCF v2.3 compliance with Avada Cookie Consent. If you have questions or need assistance, don’t hesitate to reach out. We’re here to help!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.avada.io/cookie-help-center/integrations/iab-tcf-v2.3-compliance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.