Hotjar for PrestaShop: heatmaps and session recordings that reveal problems

Last reviewed June 2026, Hotjar still pairs heatmaps and recordings with its survey/feedback layer, and the consent-gating and masking checks below reflect current GDPR practice. Treat any pricing figure as directional and confirm Hotjar's current plans.

Heatmaps and session recordings tell you where a customer stalled, the cursor that hovered over the carrier list for nine seconds, the checkout form abandoned at the phone field. What they can't tell you is the sentence going through that person's head: "I couldn't find the delivery date," or "I left to check if this code works anywhere else." Hotjar's reason to exist on a PrestaShop store is that it closes that last gap. On top of the heatmaps and recordings you can get for free elsewhere, it lets you ask the customer directly, in the moment, on the exact page where they hesitated, and then read the answers next to the recording of what they did. That combination is what justifies a paid tool, and it's the lens this guide uses.

If you only need to see behaviour, click maps, scroll depth, rage clicks, dead clicks, Microsoft Clarity does that with no session cap and no bill, and we cover it end-to-end in Microsoft Clarity for PrestaShop. This post is for the next question: when is Hotjar's feedback layer worth paying for, and how do you wire it into a PrestaShop store so the data is actually trustworthy?

What Hotjar adds that free heatmap tools don't

Strip Hotjar down and it has the same two observational pillars as everyone else, heatmaps that aggregate clicks and scroll depth across visitors, and session recordings that replay an individual journey. Those are table stakes, and on the observation-only side a free tool matches them. Hotjar earns its price on three capabilities that sit on top:

• On-site surveys and feedback widgets. A poll that fires on the product page, an exit-intent question on the cart, a sliding feedback tab pinned to the checkout. This is the qualitative layer, the customer telling you the "why" in their own words instead of you inferring it from a cursor path.
• Conversion funnels with drop-off recordings. Define the steps home → category → product → cart → checkout → order confirmation, and Hotjar shows you the percentage lost at each, with one click to watch recordings of only the sessions that dropped at that step.
• Segmentation and filtering. Slice recordings by device, traffic source, whether a rage click occurred, or whether the session reached the order-confirmation URL, so you watch the 25 sessions that matter, not 2,000 that don't.

So what? On a PrestaShop store the practical payoff is specific: the funnel tells you the checkout step that leaks, the filtered recordings show you the body language of the people who leaked, and the survey on that page tells you the sentence behind it. One leak, three angles, same tool, that's the workflow a free heatmap can't assemble on its own.

The PrestaShop pages where the survey layer pays off

Generic "add a survey" advice is useless. The value comes from putting the right question on the right PrestaShop controller. Here's where the feedback layer earns its keep on a typical store, mapped to the actual page:

The order-confirmation survey is the one most merchants skip and the one that pays the most, because it captures friction reported by buyers who pushed through it anyway. Those are the easiest wins on the board: the objection was survivable once, so removing it converts the next customer who wasn't as patient.

Installing Hotjar on PrestaShop without breaking consent

Hotjar is a single JavaScript snippet, so the installation question is really a placement question, and on PrestaShop the wrong placement is the difference between clean data and a GDPR problem. Three routes, in order of how we'd recommend them:

• Through Google Tag Manager (recommended). If you already run GTM, add Hotjar as a Custom HTML tag and gate it behind a consent trigger. This keeps the snippet out of your theme files entirely, so it survives theme updates, and it lets you fire the tag only after the visitor accepts analytics cookies. Setting up the container itself is covered in Google Tag Manager for PrestaShop.
• A header-injection / custom-code module. If you don't run GTM, a module that injects code into the displayHeader hook (the hook that PrestaShop fires inside the page <head>) keeps the snippet out of your head.tpl and out of harm's way at upgrade time. Make sure the module lets you defer the script until after consent.
• Editing the theme's head.tpl directly. Possible, but it's the route we'd avoid: the snippet vanishes the next time you switch or update the child theme, and you'll be hand-managing the consent gate. Use it only as a last resort.

Whichever route you pick, two PrestaShop-specific rules are non-negotiable. First, do not fire Hotjar before the visitor consents to analytics cookies, list it under the analytics category of your cookie banner and load it on consent, not on page load. Second, verify input masking on your own checkout. Hotjar masks text inputs by default, but custom or one-page checkouts can render fields in ways the default rules miss, and a session recording must never capture an email, address, or anything resembling card data. Watch a few of your own recordings end-to-end before you trust the masking.

If you load Hotjar through a custom-code module rather than GTM, the practical shape of "fire only after consent" is to keep Hotjar's loader inside a function and call it on the consent signal rather than on page load:

<script>
function loadHotjar() {
  (function(h,o,t,j,a,r){
    h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)};
    h._hjSettings={hjid:YOUR_SITE_ID,hjsv:6};
    a=o.getElementsByTagName('head')[0];
    r=o.createElement('script');r.async=1;
    r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv;
    a.appendChild(r);
  })(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv=');
}
// Only load once your cookie banner reports analytics consent.
if (window.localStorage.getItem('analytics_consent') === 'granted') {
  loadHotjar();
}
document.addEventListener('cmp:analytics-accepted', loadHotjar);
</script>

Swap YOUR_SITE_ID for your Hotjar site ID, and replace the consent check and event name with whatever your PrestaShop cookie module actually exposes, the flag and event names differ between consent modules, so read yours rather than trusting the placeholders.

Hotjar or free Clarity? A straight comparison

This is the real decision, so here it is without hedging. The two tools overlap on observation and diverge on everything that costs money.

The honest recommendation for most PrestaShop merchants: start with Clarity for the observational layer, it's free and there's no reason not to run it, and add Hotjar specifically when you need to ask customers questions, not just watch them. Pricing tiers shift, so treat any monthly figure here as directional and confirm Hotjar's current plans before you buy; the structural difference (Clarity = free observation, Hotjar = paid observation plus the feedback layer) is what's stable. Many serious stores run both: Clarity always-on for volume, Hotjar switched on for a focused diagnosis when a funnel step starts leaking.

Using Hotjar funnels to find the leak, then fix it

The funnel is where Hotjar turns a vague "checkout converts badly" into a coordinate. Build the funnel from your PrestaShop URLs, category listing, product, cart (?controller=cart), the order page (?controller=order), and the order-confirmation page as the success step. Hotjar then reports the drop at each transition and lets you open recordings of only the sessions that fell out at the step you care about.

The pattern we see most often on PrestaShop: the steep drop isn't on the checkout form, it's on the cart-to-checkout transition, and the filtered recordings plus the cart survey converge on the same culprit, an obvious, empty coupon field that sends customers off to Google hunting for a code, where a share of them simply don't come back. The fix is cheap (hide it behind a "Have a code?" link), but you only know to make it because three Hotjar views pointed at the same spot. That's the loop: funnel finds the step, filtered recordings show the behaviour, survey supplies the reason, you ship a targeted change.

Where Hotjar stops and other tools start

Behavioural tools are diagnostic, not a measurement system. Keep the boundaries clean so you don't end up with three tools doing one job badly:

• For the numbers that quantify the leak, conversion rate, checkout abandonment, the funnel as a metric over time, Hotjar gives you a sampled view, while GA4 is the source for behavioural traffic and funnel metrics; for actual orders and revenue, your PrestaShop back-office order data stays the source of truth. See the GA4 metrics that actually matter, and if GA4 isn't installed yet, the complete GA4 setup guide.
• For deciding which metrics deserve attention at all, so you investigate real leaks, not vanity numbers, start with what to track and what to ignore.
• For privacy-first analytics where third-party session capture is a concern, weigh the trade-offs in Matomo vs Google Analytics.
• For the financial picture behind the behaviour, margin, refunds, true revenue per channel rather than session counts, that's reporting, not heatmaps. Financial Revolution is built for that side of the store.

One more reason to verify your masking and check who's actually in your recordings: a meaningful slice of "sessions" on a modern store aren't human. Automated shoppers and crawlers now move through PrestaShop carts, and they'll pollute your Hotjar funnels if you don't filter them. We documented the phenomenon in Google Storebot is shopping in your store. Segment by real traffic before you draw conclusions, or you'll redesign a page for a bot.

The discipline that makes it worth the money

Hotjar's failure mode is the same as every behavioural tool: hours of watching recordings that change nothing. Paying for it only makes sense if it drives changes, so run it on a routine rather than a binge. Watch a small batch of filtered checkout recordings weekly; read the open-text survey answers next to them; review the funnel monthly to catch a step that's started to slip; and after every layout or checkout change, watch recordings of the new version to confirm the fix did what you intended instead of moving the friction somewhere else.

The payoff is concrete. Free observation tells you a page is losing people; that's Clarity's job and it does it for nothing. Hotjar earns its line item when you need the customer's own words attached to that loss. The survey answer that turns "they abandoned the cart" into "the shipping cost surprised them," which is a sentence you can actually act on. Run the free layer always, switch on the paid layer when you have a specific leak to interrogate, and keep the two jobs, measuring versus understanding, in the tools built for each.

Frequently asked questions

Is Hotjar worth paying for if I already run Clarity?

Only when you need to ask customers questions, not just watch them. Clarity covers heatmaps, recordings, and frustration signals for free with no session cap, so for pure observation it's hard to justify Hotjar's bill. Hotjar earns the line item when a funnel step is leaking and you want the customer's own words attached to it. The on-page survey and exit-intent poll that turn "they abandoned the cart" into "the shipping cost surprised them." Run Clarity always; switch Hotjar on for a focused diagnosis.

What does Hotjar's free tier actually cover for a PrestaShop store?

It exists, but it's capped at a small number of daily sessions, fine for a low-traffic store or a short diagnostic burst, limiting for anything busy. If you want always-on observation across all your traffic without paying, that's Clarity's job, not Hotjar's free tier. Use Hotjar's free plan to trial the survey layer, then decide whether the paid volume is worth it for your store's traffic.

Will Hotjar capture my customers' personal data in recordings?

It masks text inputs by default, but "default" isn't "verified." Custom and one-page PrestaShop checkouts can render fields in markup the default rules miss, so a recording could capture an email or address if you don't check. Watch several of your own checkout and account-page recordings end-to-end before you trust it, list Hotjar under your cookie banner's analytics category, and never let it fire before consent.

How do I keep bot traffic out of my Hotjar funnels?

Segment by real, human traffic before drawing any conclusion. A meaningful share of modern store sessions are automated, crawlers and shopping bots that move through carts without behaving like shoppers, and they distort funnel drop-off rates and recordings alike. Filter them out first; otherwise you risk redesigning a page around behaviour no customer ever exhibited. We cover the phenomenon in Google Storebot is shopping in your store.

Can Hotjar tell me my conversion rate or revenue?

No, and it's not built to. Hotjar's funnel is a diagnostic view, often sampled, that shows you where sessions drop. For the actual conversion-rate trend and behavioural traffic numbers, GA4 is the source; for real orders and revenue, your PrestaShop back office is the source of truth. Keep measuring and understanding in separate tools, or you'll end up trusting a sampled number for a decision that needs an exact one.