Hotjar uses the cookie `_hjFirstSeen` to mark a user’s initial visit — setting a flag for 30 minutes after their first session begins.
Service client
- This is a True/False flag set by the cookie._hjFirstSeen30 minutesHotjar sets this cookie to identify a new user’s first session.
- This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites._ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site’s analytics report.
- The `_hjAbsoluteSessionInProgress` cookie (lasting 30 minutes), helps Hotjar identify when a user’s session starts with their first pageview.
- The `_hjFirstSeen` cookie holds a binary value to determine if this is a user’s first time interacting with Hotjar. Meanwhile — `_hjIncludedInPageviewSample` (2 minutes) and `_hjIncludedInSessionSample` (2 minutes) decide whether a user is included in the site’s pageview and daily session sampling limits.
- **Issuu**’s `_iutk` cookie—valid for **5 months and 27 days**—tracks interactions across its products — while **Vimeo**’s `_vuid` (2 years) assigns a unique identifier to embedded videos for analytics.
**LinkedIn**’s `bcookie` (2 years) identifies browsers via share buttons and ads, `bscookie` (2 years) logs user actions, `langsession` maintains language preferences, and `lidc` (1 day) assists in server routing. Meanwhile, **Unsplash**’s `ugid` (1 year) is set for tracking purposes.
Hotjar’s `_hjAbsoluteSessionInProgress` cookie (active for half an hour), tracks when a user’s browsing session begins, recording their first pageview. The `_gid` cookie, stored for **1 day** by **Google Analytics**, contains a unique account identifier and compiles user behavior data to generate performance analytics. Unlike `_ga` , 2 years,, which records visitor activity and session details for analytics, `_gid` restricts its scope to the domain it’s set on, preventing cross-site tracking.