Mida + Hotjar integration

Tag Hotjar session recordings and heatmaps with Mida test and variant IDs to watch real users in each variant.

Analytics & Data Data out Client-side Works with Mida A/B Testing & Personalization

About Hotjar

Hotjar is a behavior analytics tool used by 1M+ websites for session recordings, heatmaps, on-page surveys, and feedback widgets. It's the industry standard for understanding the qualitative 'why' behind visitor behavior — a perfect complement to the quantitative 'what' from Mida A/B tests.

How the Hotjar integration works

Mida calls hj('event', ...) to tag the active Hotjar session with mida_conversion_{test_id} and mida_conversion_{test_id}_{variant} tags whenever a visitor converts. Inside Hotjar you can then filter session recordings and heatmaps by those tags to watch only users who saw a specific variant — or only those who converted on it.

Requirements

  • Hotjar tracking code installed on the page.
  • Mida tracking code installed on the page.
  • Hotjar Plus or Business plan for event-based filtering on recordings.

Use cases

Watch recordings of users who converted on the winning variant

Filter Hotjar recordings by the mida_conversion_{test_id}_{variant} tag for the winning variant — replay 20–30 sessions and you'll typically uncover the exact UX moment that drove the lift.

Compare heatmaps between variants

Tag enough sessions per variant and Hotjar lets you build separate heatmaps per variant. Useful for confirming a hero-redesign test actually changed where attention goes.

Trigger Hotjar surveys on specific variants

Use Hotjar's targeting rules to show a 'Why didn't you sign up?' survey only to visitors tagged with the losing variant — fast qualitative feedback on what went wrong.

Find UX bugs that only appear in one variant

If a variant under-performs unexpectedly, filter Hotjar recordings by that variant and skim 10 sessions. Broken layouts, mis-positioned CTAs, and form issues jump out immediately.

Shared data

Mida and Hotjar exchange the following events:

Event Direction Description
mida_conversion_{test_id} Data out Tags the Hotjar session for the test on conversion.
mida_conversion_{test_id}_{variant} Data out Tags the Hotjar session for the specific variant on conversion.

Frequently asked questions

Why are only conversion events sent, not exposure?

Hotjar's free and Observe plans cap how many event tags can be applied to a session. We deliberately keep the volume low so you don't burn through quota.

Do I need a paid Hotjar plan?

Tagging sessions with hj('event') works on every Hotjar plan, but filtering recordings and heatmaps by event requires Hotjar Plus or above.

Can I tag exposure events too?

Not via the standard integration. If you need exposure-level tagging, use Mida's Webhook integration to call Hotjar's API yourself.

Ship A/B tests 10x faster — connected to your stack

Mida is the lightweight A/B testing and personalization platform that integrates with the tools you already pay for.