Cookies in this hub
23
Analytics cookies measure traffic, sessions, engagement, and behavior across pages. They are widely used for product, marketing, and UX reporting, but in the EU they are still non-essential tracking technologies.
Cookies in this hub
23
Provider families
8
Default consent view
Consent required
Analytics cookies generally require prior consent under ePrivacy and GDPR when they store or access information on the user's device. Pseudonymisation or truncated IP addresses do not turn them into exempt cookies.
Focus on whether analytics scripts load before consent, whether your CMP blocks tags correctly, and whether the cookie list shown to users actually matches what the site sets in production.
Banner copy tip: State what you measure and which vendor is involved, such as Google Analytics or session replay, rather than vague wording like performance improvement.
Need platform-specific implementation advice? Review the matching hub for Shopify, WordPress, WooCommerce, PrestaShop.
GA4 session state cookie. Stores the current session ID and engagement state for the property; one is set per GA4 measurement ID.
Used by Universal Analytics to distinguish users over a 24-hour window. Largely deprecated since GA4 but still found on legacy sites.
Stores information about the time a visitor's identity was synchronised with the lms_analytics cookie for LinkedIn analytics.
Hotjar session cookie. Holds current session data so subsequent requests in the session window are attributed correctly.
HubSpot user token. Identifies a unique visitor and is passed to HubSpot on form submission for contact deduplication.
_gaAnalyticsConsent requiredDistinguishes unique users by assigning a randomly generated client ID. Used by both Universal Analytics and GA4 properties.
_gatAnalyticsConsent requiredThrottles the request rate to Google Analytics on high-traffic sites. Often appears as _gat_gtag_<id>.
_dc_gtm_<container-id>AnalyticsConsent requiredUsed by Google Tag Manager to throttle the request rate to Google Analytics. Set when GTM loads GA on the page.
_hjSessionUser_<id>AnalyticsConsent requiredHotjar user ID cookie. Ensures data from subsequent visits to the same site is attributed to the same user.
_hjFirstSeenAnalyticsConsent requiredIdentifies a new user's first session and indicates whether or not Hotjar's seeing this user for the first time.
_hjIncludedInPageviewSampleAnalyticsConsent requiredSet so Hotjar can determine whether the visitor is included in the data sampling defined by the site's pageview limit.
_hjAbsoluteSessionInProgressAnalyticsConsent requiredUsed by Hotjar to detect a visitor's first pageview session and prevent it being counted multiple times.
_clckAnalyticsConsent requiredPersists the Clarity user ID and preferences unique to the site, so visits to the same site are attributed to the same user.
_clskAnalyticsConsent requiredConnects multiple Clarity page views by a user into a single session recording.
ajs_anonymous_idAnalyticsConsent requiredSegment-generated anonymous visitor identifier. Used to attribute events from non-logged-in users to a stable ID across sessions before they identify.
ajs_user_idAnalyticsConsent requiredSegment user identifier set after a visitor calls analytics.identify(). Used to forward identified events to downstream tools (Mixpanel, Amplitude, etc.).
amplitude_id_<id>AnalyticsConsent requiredStores the Amplitude device and user ID, plus session metadata, so behavioural events can be attributed to a stable user across visits.
optimizelyEndUserIdAnalyticsConsent requiredOptimizely visitor identifier used to bucket users into A/B test variants and measure experiment exposure consistently across visits.
__hstcAnalyticsConsent requiredHubSpot main analytics cookie tracking visitors. Contains domain, utk, initial timestamp, last timestamp, current timestamp, and session number.
__hsscAnalyticsConsent requiredHubSpot session cookie. Tracks sessions: incremented on each new pageview within 30 minutes.
__hssrcAnalyticsConsent requiredHubSpot session-restart flag. Set to 1 when HubSpot detects that the visitor has started a new browser session.
_shopify_yAnalyticsConsent requiredShopify long-term visitor analytics cookie used for tracking returning customers and personalising recommendations.
_shopify_sAnalyticsConsent requiredShopify session analytics cookie used to track the current visit.
Run a CookieSentry scan to see which analytics cookies appear on your live pages before consent, and export a report your privacy team can act on.
Run a free scan →