Works with your stack
Cookie consent for Hotjar
held, then loaded
The Hotjar plugin adds Hotjar to every page once a site ID is saved. It has no consent setting. Cookie Rocks holds the Hotjar script before the choice and loads it after a yes, without a reload.
By Contentsquare · contentsquare.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Hotjar
WordPress plugin
- Tested version
- 1.0.16
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 1.0.16 tested
- Active installs
- 60,000+
What Hotjar adds to your visitors’ browser
Trackers it loads
- Hotjar →Statistics9 browser storage keys
What matters for consent with Hotjar
No setting to wait
The plugin prints the Hotjar snippet in the head of every page, for logged-in users too. It has no consent setting, no filter and no WP Consent API support.
Held by its address
The snippet has no script handle, so a banner can only hold it by the address it loads from. Cookie Rocks holds Hotjar this way.
Starts on the same page
After a yes, Hotjar loads at once, on the page the visitor is on.
Cookie Rocks with Hotjar
- Holds the scripts it adds to your pages, such as tags, pixels or a chat, until the visitor consents. In advanced Consent Mode, Google’s tags load with consent denied instead.
What our tests found on Hotjar
Good to know · HotjarCookie Rocks holds the Hotjar plugin's script until Accept all
On a test WordPress with the Hotjar plugin 1.0.16 and a dummy site ID, Cookie Rocks holds static.hotjar.com/c/hotjar-<id>.js before the choice and loads it after Accept all, without a reload.
Seen in our tests, 17 October 2026, Hotjar 1.0.16.
Set before the choice · HotjarThe Hotjar plugin loads Hotjar on every page with no consent setting
It prints the Hotjar code in the head once a site ID is saved, logged-in users included. With no filter or WP Consent API support, a banner can only hold it by its address.
Read in its code, 16 October 2026, Hotjar 1.0.16.
Full detail
The official Hotjar plugin 1.0.16 prints the classic Hotjar snippet inline in wp_head (loading static.hotjar.com/c/hotjar-<id>.js) once a site ID is saved, on every front page, logged-in users included, without a script handle. It has no consent setting, no filter and no WP Consent API support, so a banner can only hold it by its address.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- Hotjar 1.0.16, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Its own tags, set with a test ID, do not load before the choice and load after “Accept all”.
- Settings of the test: Hotjar site ID (test value).
- Last run: Hotjar 1.0.16 on 7 November 2026, with WordPress 7.1.3.
Analytics and ad pixels
Other plugins of the same kind.
Questions
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For Hotjar users
Hotjar waits for a yes.
no reload needed
Every feature of the complete plugin for 30 days, no card. Hotjar keeps working as it does today.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.