Understand how to use Hotjar on Shopify, check which parts of checkout you can observe, and choose when visitor recordings or a public-storefront audit will help your next CRO decision.
Yes, you can collect visitor behaviour on a Shopify storefront with a compatible tracking installation. Hotjar is now part of Contentsquare: its familiar heatmaps, recordings, and feedback tools continue there. Follow the documentation for the platform your account uses, and check checkout coverage separately. Read Hotjar's product update.
Choose CROtrustify when you need a quick, repeatable inspection of visible Shopify trust and conversion friction before you have enough traffic, or before deciding where deeper research should begin.
Choose Hotjar when you need evidence of what real visitors click, ignore, revisit, or struggle with, or when you want to ask users for direct feedback. Heatmaps, session recordings, and surveys help investigate behaviour on pages where collection is supported and correctly configured.
They are usually complements rather than substitutes: the audit creates hypotheses from the storefront; behavioural analytics, surveys, ecommerce analytics, and customer research help confirm or reject them.
Check whether your account uses Hotjar or Contentsquare before following an installation tutorial. For the current Contentsquare Shopify app, the official setup is:
Avoid duplicate tracking when an existing tag is already installed. Then verify that the pages you intend to analyse actually produce data. For an existing Hotjar account, use its matching setup instructions rather than assuming a Contentsquare Tag ID is interchangeable with a Hotjar Site ID.
Follow the official Contentsquare Shopify installation guideA working storefront tag does not establish checkout recording coverage. The current Contentsquare Shopify app documents checkout pageviews on non-Plus plans, while checkout Session Replay and heatmaps require Shopify Plus. Ecommerce event access also depends on the Contentsquare plan.
Contentsquare's web tracking guide says checkout session capture requires its Shopify app on Shopify Plus; the legacy manual installation does not support it. Confirm the route available to your account before relying on a tutorial that only adds a script to the theme.
Check the official tracking and checkout requirementsIf recordings stop at checkout, that alone is not evidence of abandonment. Check Shopify funnel data and test the journey directly. A public Shopify checkout-entry audit can flag visible cart and reassurance issues, but cannot replay private payment sessions.
Side-by-side comparison
| Criterion | CROtrustify | Hotjar |
|---|---|---|
| Primary evidence | Automated checks of publicly observable storefront pages and states | Behaviour analytics and direct feedback from visitors to an instrumented site |
| Setup | Enter a public store domain; no Shopify app or tracking code is required for the baseline scan | Follow the installation guide for your Hotjar or Contentsquare account; verify storefront and checkout coverage separately |
| Live traffic required | No traffic is required to inspect the public storefront | Yes, behavioural evidence such as recordings and heatmaps is created from visitor sessions |
| Typical output | Trust score, weighted categories, observable findings, and a prioritised review list | Heatmaps, recordings, surveys, and—depending on the plan—funnels, trends, and other insight tools |
| Strongest use case | Fast baseline before launch, after a theme change, or when deciding where to inspect first | Understanding what real visitors do and collecting qualitative feedback on specific journeys |
| Important limitation | Cannot observe private analytics, real visitor behaviour, customer intent, margins, or every checkout state | Requires sufficient relevant traffic, correct instrumentation, privacy configuration, and interpretation |
Illustrative scenarios, not measured customer results.
First confirm the drop in Shopify analytics. With enough relevant sessions, use recordings to investigate variant selection and heatmaps to see whether buyers reach delivery information. Missing interactions can suggest a usability problem, but do not establish why a visitor left. Test the suspected issue directly.
A public-storefront audit can flag missing or hard-to-find purchase information before useful session patterns exist. Review the finding, make the delivery terms clear, and validate its effect once traffic arrives. You can run a free Shopify CRO audit to establish that initial review list without installing visitor tracking.
A stronger workflow
Use Shopify or web analytics to identify the device, channel, page, and stage where performance weakens.
Use CROtrustify to collect visible trust, clarity, policy, proof, mobile, cart, and checkout-entry findings.
Use Hotjar recordings, heatmaps, funnels, and surveys where appropriate to look for behavioural support or contradiction.
Fix proven defects first, record the baseline, test material changes, and monitor purchases, revenue quality, refunds, and margin.
Hotjar's documentation states that recordings reconstruct captured session events rather than storing a conventional screen video. It provides input suppression and configurable content suppression, while site owners remain responsible for appropriate configuration, consent, and handling of personal data.
Read Hotjar's official privacy documentationThe baseline audit scans public storefront pages without adding visitor tracking code to the merchant's site. It cannot replace behavioural analytics or private commercial data, and users should review the CROtrustify privacy policy for account, scan, and contact-data handling.
Read the CROtrustify privacy policyRelated Shopify resources
Free storefront scan
Run a free public-storefront scan with no tracking-code installation, then validate the findings with Shopify analytics, Hotjar, and customer evidence where available.