From Friday July 1, 2022 we're moving accounts that were created before April 20, 2022 to our updated pricing model.
Under the updated pricing model, we've grouped Surveys and Feedback into a separate product called Ask that’s priced based on the number of responses you want to collect across Surveys and Feedback. Heatmaps and Recordings will be grouped into a separate product called Observe and will still be priced based on the number of daily sessions.
Both products, Observe and Ask, will have the Basic (free), Plus, Business, and Scale plans available, and the selected plan can be different for each product.
See the Updating our pricing model blog post for all the details on this update.
Although Hotjar does not have an A/B testing feature, we do enable you to monitor your pre-existing A/B test. The setup options for keeping track of each of your variations are:
Tracking Variations with Different URLs
With this setup, Hotjar is able to record Heatmaps for the A/B test if the URL is different for each variation.
Example:
Control: http://www.domain.com/products/
Variation: http://www.domain.com/products-2/
Two separate Heatmaps should be created, in this case, to track both pages. Our targeting rules could be:
Contains: products/
Contains: products-2/
You can view our Heatmap Guide to learn how to setup Heatmaps as well as Page Targeting for Heatmaps to learn which targeting rule best suits your site.
Tracking Variations on the Same URL
If your A/B test loads different content randomly each time a new user lands on the page, tracking can be done by Using Events for Heatmap Targeting. This method is currently only available on our Observe Plus, Observe Business, and Observe Scale plans.
You may need to consult your web developer for Events implementation, since it involves adding JavaScript to your site.
It is not possible to trigger a Heatmap screenshot based on an event
It isn't possible to trigger a screenshot based on an event, however you can filter Heatmap session data based on an event. When filtering, Hotjar will show data collected from sessions where users triggered the event at some point during their session. This doesn't mean the Heatmap screenshot will be captured at the moment the event fired.
For A/B testing purposes, ensure the event names you're using are unique to the page being tested.