Cookie used to identify a session instance for the user

This cookie is written to help with site security in preventing Cross-Site Request Forgery attacks.

Used to store information about whether visitors have given or declined the use of cookie categories used on the site.

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.

Hotjar cookie. This cookie 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. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.

This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.

The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information.

Contains a unique identifier used by Google Analytics to determine that two distinct hits belong to the same user across browsing sessions.

Contains a unique identifier used by Google Analytics to determine that two distinct hits belong to the same user across browsing sessions.

Used to throttles number of requests received by users