Cookie database

Hotjar cookies

33 cookies set by Hotjar, each with its purpose and consent category.

Privacy policy: https://www.getbeamer.com/privacy-policy

CookieCategoryPurpose
_BEAMER_DATE_MarketingSet by Beamer (hotjar.com). Stores the latest date in which the feed or page was opened.
_BEAMER_FILTER_BY_URL_MarketingThis cookie is set by Beamer to store whether to apply URL filtering on the feed
_BEAMER_FIRST_VISIT_MarketingSet by Beamer (hotjar.com) to store the date of the user’s first interaction with insights.
_BEAMER_LAST_POST_SHOWN_MarketingSet by Beamer (hotjar.com). Stores the timestamp for the last time the number of unread posts was updated for the user.
_BEAMER_USER_ID_MarketingSet by Beamer (hotjar.com) to store an internal ID for a user.
hj_visitorAnalyticshotjar uses cookies to enhance the user’s experience on our website, for example to complete forms, navigating the site, and identify returning users and offer related content. Users can control the use of cookies at the individual browser level.
_hjAbsoluteSessionInProgressFunctionalThe 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.
_hjCachedUserAttributesAnalyticsThis 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.
_hjClosedSurveyInvitesAnalyticsHotjar 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 re-appear if it has already been shown.
_hjCookieTestFunctionalThis cookie checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set.
_hjDonePollsAnalyticsHotjar 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 re-appear if it has already been filled in.
_hjDoneTestersWidgetsAnalyticsHotjar 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.
_hjFirstSeenFunctionalThe 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.
_hjHasCachedUserAttributesAnalyticsThis cookie sets when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites. Ensures data from subsequent visits to the same site are attributed to the same user ID.
_hjidAnalyticsHotjar cookie. This cookie is set when the customer 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 behavior in subsequent visits to the same site will be attributed to the same user ID.
_hjIncludedInPageviewSampleFunctionalThis cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's page view limit.
_hjIncludedInSampleAnalyticsHotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.
_hjIncludedInSessionSampleFunctionalThis cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit
_hjLocalStorageTestFunctionalThis 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.
_hjMinimizedPollsAnalyticsHotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.
_hjMinimizedTestersWidgetsAnalyticsHotjar cookie. This cookie is set once a visitor minimizes a Recruit User Testers widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.
_hjptidFunctionalThis 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.
_hjSession_FunctionalA cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session.
_hjSession_2740120AnalyticsHolds current session data for Hotjar, ensuring subsequent requests are attributed to the same session.
_hjSessionRejectedFunctionalIf 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.
_hjSessionResumedFunctionalA cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
_hjSessionStorageTestFunctionalThis cookie checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set.
_hjSessionTooLargeFunctionalCauses 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.
_hjSessionUser_FunctionalHotjar cookie that 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 behavior in subsequent visits to the same site will be attributed to the same user ID.
_hjShownFeedbackMessageAnalyticsThis cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show.
_hjTLDTestFunctionalWhen 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.
_hjUserAttributesHashFunctionalUser 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.
hjViewportIdFunctionalThis cookie stores user viewport details such as size and dimensions.

Running Hotjar on your site? A free Conzent scan shows which of these cookies are set before consent, and the banner blocks them until the visitor agrees.

Last updated 2026-09-27.