JENTIS Data Capturing Platform (DCP) is a first party and server side focused service. For the tag management and consistent data it relies on cookies and local storages. Some are only set if you configure the according tools, some are set per default. Here you will find a complete list of cookies that are set by our service.
The following cookies are set when JENTIS JS SDK (embed code snippet) is integrated on a website with the following conditions:
user actively grants consent to any installed tool in your JENTIS Data Capturing Platform
consent administration is turned off (you have actively turned off the link between your Consent Management Platform and JENTIS vendors)
a single tools vendor is configured with “JENTIS Essential Mode” and consent is actively granted/denied by the website visitor (users decision is awaited)
a single tools vendor is configured with “No Consent” (decision of user is not awaited)
The following cookies are set based on those rules with the following purpose.
The JENTIS first party identifier (User-ID).
The JENTIS session identifier (Session ID).
Activates the JENTIS-Debug-Log function for developers (only set in Preview Mode for JTM users and developers).
JENTIS Storage (Local/Session)
This browser storages are read and written when JENTIS JS SDK (embed code snippet) is integrated on a website.
Storage of Consent-Vendors and JENTIS Consent-ID Settings.
Storage of the ID-Relation between the different collected Document-Types.
Activates the JENTIS-Debug-Log function for developers
Storage of JENTIS-Debug ID
Tool Specific Cookies
JENTIS has multiple tools and configurations available. Those vary based on your individual configuration, of what tools and tags you intend to use. With certain tags and tools according cookies of that tool may be set.
To find out which cookies and data storages will be used you will look that up individually per tool documentation. Right this way: JTM Tools