Random User ID that identifies the user.

Tracks if the visitor is coming from a webinar registration.

    Secure- 1PSIDCC

Cookie required to use website options
and services.

Used by CDN Akamai for the Akamai cache function, used by the website to optimize the response time between
the visitor and the website.

SPAM protection service provided by Google that helps protect websites
from spam and abuse.

Used to play YouTube videos
embedded on the website.

Cookie for chat history, stored until the
browser is closed.

Visitor ID as identified in Conversational Cloud. Identifies a browser as long as the cookie is not
deleted.

Provides technical support to the chat function to make sure that the chat on the website works as intended, e.g. by identifying the browser which enables us to remember ongoing and previous chats as well as know where a user is
visiting the website from.

Store the user's consent about
accepting/rejecting cookies

1 year

Session

wordpress_test_cookie             

WordPress sets a test cookie for every
visitor to check if the browser accepts cookies.

current session

Session

1 year

Used to collect and use personalised
data in order to deliver targeted and personalised advertising.

1 year

Used by Facebook to store and track visits across websites. The expiration is
controlled by settings in the plugin.

Used by Baidu Analytics to limit the frequency of requests. Baidu Analytics collects information in an anonymous form, including the number of visitors to the website and blog, where visitors have come to the website from and the
pages they visited.

Session

Stores used keyword and search
engine.

Google Analytics uses the _ga and _gid cookies to distinguish unique users and pages that users have seen. The _ga cookie counts the number of visits to a page or post.

2 years

Contains campaign related information.
If Google Analytics and Google Ads accounts are linked, Google Ads website conversion tags will read this cookie unless the user opts out.

Used by Google Analytics to track conversions. Reads and filters requests from bots and then identifies users across browsing sessions.

1 min

3rd Party

Analytical

Session

3rd Party

Analytical

Google Analytics uses the _ga and _gid cookies to distinguish unique users and pages that users have seen. The _gid cookie prevents repeats views of a
page or post by a visitor.

1 day

30 Minutes

Stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample.
Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the
cookie will be used regardless of whether a Feedback tool is present.

Session

3rd Party

Analytical

Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal, used to ensure that the same invite does not reappear if it
has already been shown.

1 year

3rd Party

Analytical

Hotjar cookie that is set once a user completes a survey using the On-site Survey widget, used to ensure that the same survey does not reappear if it has
already been filled in.

1 year

3rd Party

Analytical

If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.

Set when a session/recording is reconnected to the Hotjar servers after
a break in connection.

Session

3rd Party

Analytical

Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal
from the WebSocket server if the session size exceeds the limit.

Hotjar cookie that is set when a user minimizes or completes Incoming Feedback so that the Incoming Feedback will load as minimized immediately if the user navigates to
another page where it is set to show.

When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives
until it fails. After this check, the cookie is removed.

User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to
be updated.

Set when a page that supports multiple languages on hotjar.com is visited so content is always loaded in the
preferred language when available.

Baidu Analytics Tongji. Records a unique ID used to generate statistical
data on how a visitor uses the website.

Used by Google DoubleClick to determine whether the website advertisement has been properly displayed and collect data in order to
show relevant advertising to the visitor across the web.

HSID, SSID, APISID and SAPISID cookies enable Google to collect user information for videos hosted by
YouTube.

The number of visits, including the time of the first visit, the previous visit, and
the current visit.

Set to identify a new user's first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user
sessions.

Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID unique to that site on the browser and ensure that behavior in subsequent visits to the same site
will be attributed to the same user ID.

Set to let Hotjar know whether user is included in the data sampling defined
by the site's pageview limit.

Set to let Hotjar know whether user is included in the data sampling defined
by the site's daily session limit.

Checks if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost
immediately after it is created.

Under 100ms

Hotjar cookie that is set once a user minimizes an On-site Survey widget, used to ensure that the widget stays minimized when the user navigates
through the site.

Added when a Recording starts and read when the recording module is initialized to see if the user is already in
a recording in a particular session.

Updated when a user recording starts and when data is sent through WebSocket (the user performs an action that Hotjar records).