Skip to main content

Analyze Heyflow events with Hotjar

Learn how to integrate Hotjar to get detailed insights into user behavior, with session recordings and heatmaps that reveal how visitors interact with your funnels.

⭐ Available in the following bundle: Insights Bundle

⭐ Bundle included in the following plans: Scale

⭐ Available on the following legacy plans: Pro, Agency, Business

👀 Not sure which plan you're on? Check your subscription here.

Hotjar is a behavior analytics and user feedback tool that helps businesses understand how visitors interact with their website and improve user experience.

Connect Heyflow with Hotjar to send event and user data from Heyflow directly to your Hotjar account. This helps you to understand how users interact with your funnel and optimize your funnels based on real-user insights.

With Heyflow's Hotjar integration, you can:

  1. Send Heyflow event & user data directly to Hotjar
    Send events and user behaviour from Heyflow straight into your Hotjar account — no coding or external tools needed.

  2. Track user interactions with heatmaps
    Visualize how users engage with your funnel using Hotjar’s heatmaps.

  3. Record sessions to understand user behavior
    Capture individual user sessions to see exactly how visitors navigate your funnel and identify areas for improvement.

Setup

❗New Hotjar setups now use Contentsquare

Hotjar is now part of Contentsquare, and new sign-ups are set up through Contentsquare. If Contentsquare gives you a tag snippet (for example https://t.contentsquare.net/uxa/abc123.js) instead of a numeric Site ID, the Hotjar integration below won't work with it. Follow the steps in "Setting up with a Contentsquare tag" further down instead.

If you already have a numeric Site ID from an existing Hotjar account, you can keep using the Hotjar integration as described below.

  1. Within your flow, go to “Connect” and then to the tab “Tracking”
    ​

  2. Click on Hotjar and insert your Site ID.
    ​

  3. Click on Connect and publish your flow again.

  4. Optional: In Hotjar, verify if Hotjar is capturing data by inserting your domain and click on Verify installation.
    ​

  5. Congratulations, your Heyflow is now connected to Hotjar!

Where to find your Site ID in Hotjar?

Follow the instructions below, to get all necessary information for the integration.

  1. Log in to your Hotjar account.
    ​

  2. New Hotjar accounts can no longer be created. If you've just signed up through Contentsquare, you won't have a Site ID. Follow the steps in "Setting up with a Contentsquare tag" below instead.
    ​

  3. If you’ve already been using Hotjar, you should head over to Organizations Settings (on the upper right in your account), then click on Organizations and sites (on the top left), and choose + New Site or find the desired ID in the list:
    ​

Setting up with a Contentsquare tag

  1. In your flow, go to Connect > Tracking > Hotjar and make sure the Site ID field is empty.
    ​

  2. Add the tag in the Head tab of your flow's custom code. If your flow doesn't use Heyflow's cookie banner, paste the snippet exactly as Contentsquare provides it.
    ​
    If your flow uses Heyflow's cookie banner, use the snippet below instead, so Contentsquare only loads after the visitor accepts analytics cookies. Replace YOUR_TAG_ID with your Tag ID, which is the part of your Contentsquare snippet between /uxa/ and .js. For example, in https://t.contentsquare.net/uxa/abc123def4567.js, the Tag ID is abc123def4567.

  3. Check that the code ends with only one closing </script> tag, then publish your flow again.

<script type="text/plain" data-cookieconsent="analytics">
  (function () {
    var tag = document.createElement('script');
    tag.src = 'https://t.contentsquare.net/uxa/YOUR_TAG_ID.js';
    tag.async = true;
    document.head.appendChild(tag);
  })();
</script>

Troubleshooting

I'm receiving double events

If you're seeing duplicate pageview events in your Hotjar reports when using Heyflow, it's likely related to how Hotjar handles Single Page Applications (SPAs) like Heyflow.

Why is this happening?

Heyflow is a Single Page Application (SPA). This means flow steps (pages) load dynamically without a full page reload or URL change - specifically, the URL after the # symbol (called a fragment) changes, but Hotjar doesn't treat that as a new page by default. To ensure Hotjar tracks each flow step as a separate page, we're manually triggering page events using the Hotjar SPA API.

❗ However, there's a catch: If you've already customized your Hotjar settings to track fragment changes, and you're now using our new integration that manually sends events, you might see double pageviews - one triggered by your custom setup and one by Heyflow’s tracking.

How to Fix It

  1. Check your Hotjar configuration:
    Go to your Hotjar site's settings and ensure that you haven’t enabled fragment tracking or added custom JavaScript to track page changes.
    ​

  2. Use one tracking method only:

    • If you’re using Heyflow's built-in Hotjar support, there’s no need to manually modify the Hotjar script or enable fragment tracking.

    • If you've previously customized Hotjar yourself, we recommend removing those changes to avoid conflicts.
      ​

💬 If you're having any other issues with our Hotjar integration, please contact the support.

Related Articles
Did this answer your question?