What is the `_hjCachedUserAttributes` cookie?it needs consent first

Set by Hotjar (Hotjar Ltd.). Expires after Session.

Block it until the visitor opts in

Under the ePrivacy Directive (Art. 5(3)) and GDPR, _hjCachedUserAttributes may only be set after the visitor accepts analytics cookies.

Purpose

Stores user attributes sent through the Hotjar Identify API while the user isn't in the sample yet.

Cookie details

Cookie name: _hjCachedUserAttributes
Service: Hotjar
Provider: Hotjar Ltd.
Category: Analytics
Duration: Session
Consent: Required — opt-in

GDPR requirements

Analytics cookies help website owners understand how visitors interact with websites by collecting and reporting information anonymously. Consent is required under GDPR.

For _hjCachedUserAttributes to be compliant, it must be:

Not set on the first visit — not even for a fraction of a second
A consent banner is shown, and the visitor actively accepts analytics cookies
Stays blocked if the visitor rejects or ignores the banner
Listed in your cookie policy with its name, purpose and retention period
Removed or invalidated when the visitor withdraws consent

How to handle it

1
Block it by default
Configure your consent platform (CMP) or tag manager so Hotjar doesn't load until the visitor accepts analytics cookies.
2
Map it to a consent category
Put it under “Analytics” in your CMP configuration.
3
List it in your cookie policy
Name, purpose, provider (Hotjar Ltd.) and expiry (Session).
4
Sign a DPA
Have a Data Processing Agreement with Hotjar Ltd. covering the data this cookie collects.
5
Verify it works
In a private window, reject cookies and confirm _hjCachedUserAttributes is not set.