Hotjar is a behaviour analytics tool that helps site owners understand how visitors use their site through heatmaps, session recordings, surveys and feedback widgets.
_hjDoneTestersWidgets
Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in
365 days
_hjMinimizedTestersWidgets
Hotjar cookie. This cookie is set once a visitor minimises a Recruit User Testers widget. It is used to ensure that the widget stays minimised when the visitor navigates through the site
365 days
_hjShownFeedbackMessage
This cookie is set when a visitor minimises or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimised immediately if they navigate to another page where it is set to show
365 days
_hjTLDTest
When the Hotjar script executes, Hotjar tries to determine the most generic cookie path it should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, Hotjar tries to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed
Session
_hjCookieTest
This cookie checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set
Session
_hjUserAttributesHash
User Attributes sent through the Hotjar Identify API are hashed and cached in this cookie so Hotjar knows when an attribute has changed and needs to be updated. The cookie is refreshed while the visitor stays active
2 minutes
_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 immediately after creating it so the expected storage time is under 100ms
Under 100ms
_hjHasCachedUserAttributes
This cookie lets Hotjar know whether the User Attributes cached in the _hjUserAttributes local storage item are up to date
Session
_hjid
Hotjar cookie. This cookie is set when the visitor first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behaviour in subsequent visits to the same site will be attributed to the same user ID
365 days
hj_visitor
Hotjar uses cookies to enhance the user’s experience on the website, for example to complete forms, navigate the site, and identify returning users and offer related content. Users can control the use of cookies at the individual browser level
Session
_hjIncludedInSample
Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels
365 days
_hjClosedSurveyInvites
Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not reappear if it has already been shown
365 days
_hjDonePolls
Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not reappear if it has already been filled in
365 days
_hjMinimizedPolls
Hotjar cookie. This cookie is set once a visitor minimises a Feedback Poll widget. It is used to ensure that the widget stays minimised when the visitor navigates through the site
365 days
_hjSessionResumed
A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection
Session
hjViewportId
This cookie stores user viewport details such as size and dimensions
Session
_hjSessionStorageTest
This cookie checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set
Session
_hjSession_
A cookie that holds the current session data. This ensures that subsequent requests within the session window will be attributed to the same Hotjar session
30 minutes
_hjSessionUser_
Hotjar cookie. This is set when a user 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 behaviour in subsequent visits to the same site will be attributed to the same user ID
365 days
_hjSessionTooLarge
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
Session
_hjSessionRejected
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 the WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues
Session
_hjptid
This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site
Session
_hjAbsoluteSessionInProgress
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
30 minutes
_hjFirstSeen
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.
30 minutes
_hjIncludedInPageviewSample
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by the site’s page view limit
30 minutes
_hjIncludedInSessionSample
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by the site’s daily session limit
30 minutes
