Cookie Policy

Information about our use of cookies

Our website uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website and also allows us to improve our site.

A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer’s hard drive.

We use the following cookies:

You can find more information about the individual cookies we use and the purposes for which we use them in the table below:

Cookie Purpose Expiration time
_ga Google cookie used to distinguish users. 2 years
_gat Google cookie used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_. 1 minute
_gid Google cookie used to distinguish users. 24 hours
_fbp Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers 180 days
_lfa Used by Leadfeeder to to store and track audience reach. 2 years
li_at Used by Linkedin to authenticate Members and API clients 1 year
_hjClosedSurveyInvites Hotjar cookie that is set once a visitor interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. 365 days
_hjDonePolls Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. 365 days
_hjMinimizedPolls Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site. 365 days
_hjShownFeedbackMessage Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show. 365 days
_hjid 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. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. 365 days
_hjRecordingLastActivity This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). Session
_hjTLDTest 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. Session
_hjUserAttributesHash 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. Session
_hjCachedUserAttributes This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. Session
_hjLocalStorageTest This cookie is used to check 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
_hjIncludedInPageviewSample This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s pageview limit. 30 minutes
_hjIncludedInSessionSample This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s daily session limit. 30 minutes
_hjAbsoluteSessionInProgress This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. 30 Minutes
_hjFirstSeen This is 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. Session
hjViewportId This stores information about the user viewport such as size and dimensions. Session
_hjRecordingEnabled This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session. Session
_supercharge-2015_session Currently not in use. session
consentAgreed Detect if user accepted the cookie policy no expiration

 

You block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of our site.

 

rotate phone rotate your phone to browse our website