> 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 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.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-tcf/tcf-string.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.