-
Print
-
DarkLight
JENTIS is a first party server side tracking tool. For the tag management and data part it relies on cookies and local storages. Some are only set if you configure the according tools, some are always set per default. Here you will find a complete list of cookies that are set by our technology.
JENTIS Cookies
This cookies are set when JENTIS JS SDK (embed code snippet) is integrated on a website.
Cookie Name | Purpose | Duration |
---|---|---|
jts-rw | The JENTIS first party identifier (User-ID). | 2 Years |
jctr_sid | The JENTIS session identifier (Session ID). | 30 Minutes |
jts_log | Activates the JENTIS-Debug-Log function for developers (only set in Preview Mode for JTM users and developers). | 1 Year |
JENTIS Storage (Local/Session)
This browser storages are read and written when JENTIS JS SDK (embed code snippet) is integrated on a website.
Storage Name | Purpose |
---|---|
jentis.consent.data | Storage of Consent-Vendors and JENTIS Consent-ID Settings. |
jentis.core.tracker.rawdata-controller | Storage of the ID-Relation between the different collected Document-Types. |
jts_preview_version | Activates the JENTIS-Debug-Log function for developers (only set in Preview Mode for JTM users and developers). |
jts_debug | Storage of JENTIS-Debug ID (only set in Preview Mode for JTM users and developers). |
Tool Specific Cookies
JENTIS has multiple tools and configurations available. If some tools are used special cookies are set. So the following list does not apply to all JENTIS implementations, but are based on an individual configuration of JENTIS.
TBD – This list will be updated shortly.