Can I track purchases in Hotjar?

Yes. When purchase tracking is enabled and the module is allowed to track the visitor, it fires a Hotjar purchase event from the PrestaShop order-confirmation hook. The front-office template calls hj('event', 'purchase') on the order confirmation page.

This is useful for Hotjar analysis because you can filter recordings, heatmaps, surveys or funnels around sessions that reached a purchase, then inspect the behavior before the order was placed. It helps answer questions such as where buyers hesitated, what checkout steps they replayed, or which page patterns appear in successful sessions.

It is not a replacement for revenue analytics or server-side order reporting. Hotjar receives the named event for behavioral segmentation; the module's order details are mainly used to build local event context and are not a full transaction feed.

The feature depends on the normal Hotjar module guards. The module must be enabled, the Hotjar Site ID must be configured as digits, purchase tracking must be enabled, and the visitor must pass the module's tracking checks such as consent handling when consent respect is enabled. If tracking is not allowed, the order-confirmation hook returns nothing.

When the hook runs, the module builds local purchase context from the PrestaShop order, including values such as order ID, currency, total value, item count and product identifiers. That context is assigned to the order-confirmation template and can be used by the module's local event recording/demo tooling, but the Hotjar Events API call made by the template is still the simple named event purchase.

In Hotjar, use the purchase event as a behavioral marker. For totals, tax, margin, attribution, refund handling or authoritative conversion reporting, keep using PrestaShop order data or an analytics platform designed for transaction reporting.