> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abconvert.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Hotjar Integration

> Send an ABConvert test and test-group attribute plus an assignment event to Hotjar sessions for recordings, heatmaps, and surveys.

<Warning>
  **Pre-release.** This guide applies when the Integrations hub is enabled for your ABConvert account. Hotjar User Attributes and session capture require a supported Hotjar plan and configuration.
</Warning>

Use Hotjar to find recordings and heatmaps for people who saw a test group. ABConvert sends anonymous User Attributes and a fixed event after an eligible assignment.

## Configure Hotjar and ABConvert

<Steps>
  <Step title="Install Hotjar and enable session capture">
    Add the Hotjar tracking code to storefront pages under your consent policy. Enable session capture for the Hotjar site that receives recordings and heatmaps.
  </Step>

  <Step title="Enable User Attributes">
    In Hotjar, enable User Attributes for the site if your plan includes them. ABConvert uses anonymous identification, so it does not send a customer ID, email address, or other direct identifier.
  </Step>

  <Step title="Enable Hotjar in ABConvert">
    In **Integrations**, enable **Hotjar**. ABConvert uses the existing `hj` browser function and does not add a second Hotjar snippet.
  </Step>

  <Step title="Verify an eligible session">
    Visit an eligible active test in a fresh, consented browser. In Hotjar, filter recordings by the `abconvert_assignment` event and inspect the `abconvert_test` and `abconvert_test_group` User Attributes.
  </Step>
</Steps>

## What Hotjar receives

| Item                                  | Value            |
| ------------------------------------- | ---------------- |
| `abconvert_test` User Attribute       | Test name        |
| `abconvert_test_group` User Attribute | Test group name  |
| `abconvert_assignment` event          | Fixed event name |

ABConvert uses two fixed attribute names because Hotjar limits a site to 100 unique User Attribute keys. The attributes are updated for the most recently applied assignment, so use the event filter when a visitor can enter more than one concurrent test.

## Use cases

* **Find recordings for a test group:** filter recordings to investigate why people in a test group abandon a product page.
* **Target feedback:** show a Hotjar survey after an assigned visitor reaches a page, then compare answers by test-group attribute.
* **Compare heatmaps:** filter Heatmap session data by `abconvert_assignment` and a test-group attribute before comparing click patterns.

## Things to know

* Hotjar plan access and session capture determine whether attributes and events become usable in recordings or heatmaps.
* A local ABConvert handoff does not confirm Hotjar stored an event. Verify in Hotjar with a real eligible session.
* Do not put personal data in test or test-group names. Hotjar User Attributes are retained in Hotjar's service.
* ABConvert does not install Hotjar or create Hotjar surveys for you.