> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/consent-center/how-jentis-handles-consent/jentis-cmp-connectors/consent-id.md). # Consent ID To fully understand how consent information is applied in the JENTIS Tag Manager, one essential concept needs to be explained: **Consent ID**. Every time consent is given, JENTIS generates a **Consent ID** that contains: * The **exact timestamp** when the consent was given * A **unique identifier** to make this consent record traceable * The **consent details** (true/false status per category or tool/vendor) This mechanism is critical for **legal and compliance purposes**, as it allows JENTIS to provide accurate consent history for any user in the event of a data disclosure request. #### Why Consent ID Matters * **Parallel storage** – Consent data is stored in JENTIS in addition to your CMP, ensuring redundancy * **Reliability** – In rare cases, CMP data and JENTIS data might differ (e.g., due to cookie deletion) * **Traceability** – Every consent decision remains linked to a unique ID for auditing #### Edge Case Example In the unlikely event that a CMP loses consent data (e.g., a user deletes cookies), JENTIS can still maintain the correct consent status thanks to the stored Consent ID. * **Why this is correct** – Cookie deletion is not an explicit withdrawal of consent; it may be a technical issue or malfunction * **Benefit** – JENTIS continues to apply tracking rules correctly even if CMP-stored data is lost, ensuring compliance and accuracy --- # 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.jentis.com/consent-center/how-jentis-handles-consent/jentis-cmp-connectors/consent-id.md?ask=&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.