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