Configure Hotjar and ABConvert
1
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.
2
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.
3
Enable Hotjar in ABConvert
In Integrations, enable Hotjar. ABConvert uses the existing
hj browser function and does not add a second Hotjar snippet.4
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.What Hotjar receives
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_assignmentand 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.