Session Recordings Tagged with the Variant (Clarity, Hotjar, FullStory, Crazy Egg and more)

Personyze can tag each session recording in Microsoft Clarity, Hotjar, FullStory, Crazy Egg, Mouseflow, Smartlook, Lucky Orange, LogRocket, Contentsquare or PostHog with the campaign and the A/B group the visitor was shown. You can then filter the recordings by variant: watch how people who saw version B used the page, next to the people who saw version A.

Personyze never loads these tools itself. It calls the tool’s own script, which must already be on your page.

What each tool receives

The tag is sent once per variant per page, when the action is shown: the same confirmed view that the campaign’s reports count. Below, <label> is Personyze: <campaign> · <group>.

• Microsoft Clarity — a custom tag: clarity('set', 'Personyze', '<campaign> · <group>'). In Clarity, filter recordings under Filters → Custom tags. Free.
• Hotjar — an event: hj('event', 'Personyze-<campaign>-<group>'). Anything but letters and digits in a name becomes _. Filter recordings by the event in Hotjar. Events need a paid Hotjar plan (Observe Plus or higher). On the free plan nothing is recorded.
• FullStory — an event named Personyze variant, with the properties campaign, group and action_id: FS('trackEvent', {name: 'Personyze variant', properties: {campaign, group, action_id}}). Search sessions by the event and its properties in FullStory.
• Crazy Egg — a recording tag: CE2.addTag('<label>'). Filter by the tag in the Recordings dashboard. Crazy Egg tags only the visits it is recording, and it has no free plan.
• Mouseflow — a recording tag: _mfq.push(['tag', '<label>']). Filter under Session Replay → Filters.
• Smartlook — an event: smartlook('track', '<label>', {campaign, group, action_id}). Filter under Sessions → New filter → Events. A name longer than 200 characters is cut.
• Lucky Orange — an event: LO.events.track('<label>', {campaign, group, action_id}). Events work as filters across Lucky Orange, recordings included. It has no free plan.
• LogRocket — an event: LogRocket.track('<label>', {campaign, group, action_id}). Filter with the Custom Event filter. LogRocket must be on the page as its script: a copy built into your site’s own code cannot be reached.
• Contentsquare — a dynamic variable per campaign: _uxa.push(['trackDynamicVariable', {key: 'Personyze: <campaign>', value: '<group>'}]). Filter session replays by the variable. Sending variables from code needs the Growth plan or higher.
• PostHog — an event named Personyze variant, with the properties campaign, group and action_id: posthog.capture('Personyze variant', {campaign, group, action_id}). Filter replays by the event and its properties. PostHog must be on the page as its snippet: a copy built into your site’s own code cannot be reached.

Two campaigns on one page are two tags. A campaign that runs no A/B test is tagged with its name alone. The group part appears only where there is a test to tell apart.

Turning it on for the whole account

1. Go to Integrations → Marketplace and open your recording tool’s card: Microsoft Clarity, Hotjar, FullStory, Crazy Egg, Mouseflow, Smartlook, Lucky Orange, LogRocket, Contentsquare or PostHog.
2. Under Tag session recordings with the variant, switch the tool on.

This is the same setting as the Tag session recordings with the variant row in Settings → Site profile → Analytics: switching it in either place changes both. It is the account’s default, and applies to every on-site campaign.

Choosing for one action

One action can choose otherwise. Open the action and go to its last step, Track & follow up. Under Watch it in your recordings, each tool is a tile: a tap turns it on or off for this action.

• While the action follows the account, the account’s tools read On – your account’s default.
• The first tap gives the action a choice of its own, starting from the account’s tools. Turn every tile off to leave the action out.
• To follow the account again, open More, for developers on the same step and switch off Tag the session recording with the variant.

Good to know

• The tool’s script must be on the page. If it loads late, for example from a tag manager or after a cookie banner, Personyze waits up to ten seconds for it. After that, the tag is sent at the variant’s next view.
• Campaign and group names are readable in your tracking script. Once a tool is switched on, the names of your active on-site campaigns and their A/B groups are part of the Personyze script your site loads, so anyone who reads that script can see them. Name campaigns accordingly.
• Consent is unchanged. Tagging runs under your account’s consent mode, like the rest of the tracker. The recording tool’s own consent is still handled by your site’s banner.
• An action that belongs to two campaigns at once is not tagged, because the page cannot tell which campaign showed it.

Related: Track & follow up (where an action tags its recordings, reports to your analytics and adds people to a list), Segment, Mixpanel. These send the campaign’s events to your analytics, rather than tagging recordings.