Main Domain Cookie
With JENTIS, you can easily capture complete user journeys across all your subdomains. The Main Domain Cookie feature allows you to configure whether first-party identifiers (f.e. JENTIS User-ID) are implemented at your website’s main domain or subdomain level in your containers. With just one click, all data can be shared across the main domain and all its subdomains, ensuring consistent user sessions, unified tracking, and a clearer understanding of how users engage with your entire digital ecosystem.
In this article, we’ll explain how to configure this when creating or editing a container and how to verify if the JENTIS cookie is set on your main domain or subdomain, and how to configure
Why does it matter which level the cookie is set at?
Imagine a user starts their journey on shop.example.com and later visits blog.example.com. If cookies are set at the subdomain level, their session won’t carry over, making capturing their interactions across these different subdomains difficult. This fragmentation disrupts your ability to analyze cross-domain behavior.
The same happens on journeys between subdomains and the main domain. If a user starts their journey on shop.example.com and then visits example.com with cookies set at the subdomain level (shop.example.com), capturing their interactions across both of them won’t be possible.
By setting cookies at the main domain level (e.g., .example.com), data can be shared across all subdomains. This ensures consistent user sessions, unified tracking, and a clearer understanding of how users engage with your entire digital ecosystem.
The Main Domain Cookie feature in JENTIS allows you to configure whether first-party identifiers are implemented at the main domain or subdomain level. This flexibility is essential for businesses managing multiple websites within the same main domain. With just one click, all data can be shared across the main domain and all its subdomains, ensuring consistent user sessions, unified tracking, and a clearer understanding of how users engage with your entire digital ecosystem.
Setting Cookie on the Main Domain
This feature determines whether first-party identifiers (f.e. JENTIS User-ID) is stored at the website’s subdomain or main domain level in your containers.
To configure this, go to Account Settings on the JENTIS Platform and click on Containers. Then, create a new container by clicking on Add New Container, or choose the container you want to edit and click on the three dots > Edit.
You will see the Main Domain Cookie feature in the Advanced Settings on your container configuration.
By default, the Main Domain Cookie option is enabled, which means the first-party identifiers are configured to be set at the main domain level.
To demonstrate the impact of setting the JENTIS Cookie on the main domain or subdomain levels, let's consider the following example:
JENTIS is implemented in this domain https://ckion-dev.jtm-demo.com/. The behavior of the JENTIS First-Party User ID (jts-rw cookie) can be observed based on whether the Main Domain Cookie is enabled or disabled:
If the Main Domain Cookie is ENABLED (Default behavior):
The cookie is set on the main domain level, in this case:
.jtm-demo.com.This means the cookie is accessible across all sub-domains of
jtm-demo.com, such asckion-dev.jtm-demo.com,analytics.jtm-demo.com, etc.
If the Main Domain Cookie is DISABLED :
The cookie is set on the current sub-domain level, in this case:
ckion-dev.jtm-demo.com.This means the cookie is only accessible within the specific sub-domain
ckion-dev.jtm-demo.comand not shared with other sub-domains.
Important: Be aware that disabling the Main Domain Cookie (which sets the JENTIS cookie on the subdomain) will result in users from the subdomain receiving different identifiers, such as JENTIS User-ID. This change can impact your tracking and data consistency.
What happens with existing container configurations?
In case you’ve already had a container configured before :
If your container is configured to your main domain (e.g.,
example.com), the Main Domain Cookie option will be ENABLED. This means the first-party identifiers will be set at the main domain level.If your container is configured to a subdomain (e.g,.
shop.example.com), the Main Domain Cookie option will be DISABLED. This means the first-party identifiers will be set at the subdomain level.
To change this configuration, follow the steps mentioned above.
How to verify the domain where the JENTIS Cookie is set:
To check in which domain the JENTIS First-Party Cookie is set, follow these steps:
Open your browser's Developer Tools by pressing F12.
Navigate to the Application tab (or its equivalent, depending on your browser).
In the sidebar, go to Storage > Cookies and select the domain of your current website.
A list of cookies set on your domain will be displayed.
Look for the jts-rw cookie name, which stores the JENTIS First-Party User ID. In the Domain column, you can see the specific domain where the cookie is set:
If we use the previous example domain https://ckion-dev.jtm-demo.com/, this means:
With the Main Domain Cookie ENABLED, the domain should appear as
.jtm-demo.com.With the Main Domain Cookie DISABLED, the domain should appear as
ckion-dev.jtm-demo.com.
DISABLED | ENABLED |
|---|---|
CODE
 |
CODE
 |
If you have any questions or suggestions, contact us through our Helpdesk.