How to Add Hotjar to WordPress
The easiest way to add Hotjar to WordPress is with a plugin that places the tracking code for you. With Conversion Bridge, you're done in minutes:
- Install and activate Conversion Bridge.
- Go to Settings → Conversion Bridge and enable Hotjar.
- Paste your Hotjar Site ID. You'll find it in Hotjar under Sites, listed next to your site name.
- Save. Hotjar starts recording sessions and building heatmaps right away.
You don't need to copy the full embed code from Hotjar. The Site ID is enough, and Conversion Bridge outputs the official tracking script in the right place on every page. The Hotjar setup guide walks through each step with details.
Hotjar WordPress Plugin
A good Hotjar plugin for WordPress should do more than paste the basic snippet into your header. That part is easy. The value comes from what WordPress knows about your visitors that Hotjar doesn't.
Here's what Conversion Bridge adds on top of the standard tracking script:
- User identification. Logged-in users are identified to Hotjar with their user ID, email, name, and role. That means you can search recordings in Hotjar by a specific user, like the customer who emailed you about a checkout problem.
- Membership and role data. If you run a membership plugin, membership levels are passed along too. Filter recordings by tier and see how paying members use your site differently than free visitors.
- Custom conversion events. When someone submits a form or completes a purchase in any of your connected plugins, Conversion Bridge fires a Hotjar event. Those events become filters, so you can watch only the sessions where a conversion happened.
- No double tracking. If another plugin or custom code already loads the Hotjar script, you can tell Conversion Bridge to skip adding it again.
Conversion Bridge connects Hotjar to 71 WordPress plugins, so events from your forms, checkout, and memberships flow in without writing any code.
Why the Basic Snippet Alone Isn't Enough
The standard Hotjar tracking code records sessions and builds heatmaps, and that's it. Every visitor is anonymous. Every recording looks the same in the list. When you want to find the session where someone abandoned checkout, you're scrolling through hours of footage hoping to spot it.
Identification and events fix that. Identified users mean you can jump straight to a specific person's sessions. Conversion events mean you can pull up only the recordings where a form was submitted, or filter the other way and watch sessions where visitors got close but never converted. That second group is usually where the real answers are.
I built the Hotjar integration this way because the recordings are only useful if you can find the right ones. Hotjar gives you the footage. WordPress knows who the people are and what they did. Conversion Bridge connects the two.
If you already use Hotjar alongside another analytics platform, that works too. Conversion Bridge sends the same conversion events to all 19 supported platforms at once, so Hotjar shows you the behavior while your analytics tool counts the numbers.
