> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-tcf/tcf-string.md).

# TCF String

The TCF (Transparency and Consent Framework) string is a standardized method for managing user consent in the digital advertising industry, developed by IAB Europe. It encodes a user's consent choices regarding personal data processing and cookie usage in compliance with regulations like the GDPR. This string, stored in the user's browser, informs websites and advertisers about permissible tracking and advertising practices based on the user's preferences.

Several methods exist to decode a TCF string, such as using online decoders like  [Uniconsent TCF Decoder](https://www.uniconsent.com/tcf-decoder) or [IABTCF](https://iabtcf.com/#/decode). These tools enable you to input the TCF string and obtain a readable format of the encoded data, including consents and user preferences.

This string, encoded in the "euconsent-v2" cookie is generated by the Didomi SDK and shared with all scripts on the page, allowing only consented vendors to process user data.

Vendors will retrieve information through the \_\_tcfapi function instead of the euconsent-v2 cookie; refer to this [article ](https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/TCFv2/IAB%20Tech%20Lab%20-%20CMP%20API%20v2.md#details-for-vendors)for more information.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-tcf/tcf-string.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.