How do I record visitor sessions and heatmaps with Microsoft Clarity or Hotjar?

Overview

Storeep has two session-recording and heatmap apps you can connect: Microsoft Clarity and Hotjar. Each one loads a small tracking script on your storefront that records how real visitors move, click, and scroll, then shows the results as session replays and heatmaps inside that provider's own dashboard. Both apps are free to install from the Storeep app catalog, and you can run one or both at the same time without conflict.

The recordings and heatmaps themselves live in Clarity or Hotjar, not in Storeep. Storeep's job is to inject the correct script with your ID so the data starts flowing.

Microsoft Clarity

Install and connect Clarity

1. Create a free project at clarity.microsoft.com/projects and copy its Project ID.
2. In Storeep, open Apps, Microsoft Clarity, click Install, and confirm.
3. In the settings panel, set the two fields below.
4. Click Save. Data starts reaching your Clarity dashboard within a few minutes of the next visitor.

Clarity fields

• Activate: when on, the Clarity script loads on your storefront and recording runs. Turn it off to stop tracking without uninstalling the app. It is on by default after install.
• Project ID: your Clarity Project ID. The panel shows an in-app note pointing to clarity.microsoft.com/projects where you can find it. The field accepts up to 20 characters and is required while Activate is on.

Storeep loads Clarity's official snippet and calls its consent step automatically, so Clarity does not show its own cookie consent banner on your store.

Hotjar

Install and connect Hotjar

1. Create a Hotjar account and add your store as a site at hotjar.com, then copy your numeric Site ID.
2. In Storeep, open Apps, Hotjar, click Install, and confirm.
3. In the settings panel, set the two fields below.
4. Click Save. Recordings and heatmaps populate in Hotjar as visitors arrive.

Hotjar fields

• Activate: when on, the Hotjar script loads on your storefront and recording runs. Turn it off to pause tracking while keeping the app installed. It is on by default after install.
• Site ID: your Hotjar Site ID. It must be the numeric ID from your Hotjar account, because Storeep passes it to Hotjar as a number. A non-numeric value will not load any recordings. The field accepts up to 20 characters and is required while Activate is on.

How tracking behaves on your store

• One ID per store, all markets. Each app stores a single Project ID or Site ID for the whole store, so the same script runs across every market, domain, and language of that store. There is no per-market ID.
• Activate is the on/off switch. The script is injected only while Activate is on. Saving with Activate off removes the script on the next page load but keeps your saved ID for later.
• Runs even on access-denied pages. The scripts also load on visitors who hit a blocked or 403 page, so you can replay what blocked traffic tried to do and tune your access rules.
• Bots are excluded. Visitors flagged as fraudulent or bot traffic by Storeep's shield are skipped, so their junk sessions do not waste your recording quota.
• The two apps are independent. Running Clarity and Hotjar together is fine. Each loads its own script and neither interferes with the other.

Things to check

• Only sessions after the script loads are captured. Visits from before you installed and activated the app are not recorded.
• New recordings can take a few minutes to appear in the Clarity or Hotjar dashboard after the first visits.
• If Save shows a validation error, confirm the ID is filled in (it is required while Activate is on) and is no longer than 20 characters.
• Recording volume, retention, and any session limits depend on your plan inside Clarity or Hotjar, not on Storeep. Export anything critical you want to keep long term.
• Changing your ID later: reopen the app from Apps, edit the field, and click Save. The new script takes effect on the next page load.