Personyze can tag each session recording in Microsoft Clarity, Hotjar or FullStory 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.
- 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 propertiescampaign,groupandaction_id:FS('trackEvent', {name: 'Personyze variant', properties: {campaign, group, action_id}}). Search sessions by the event and its properties in FullStory.
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
- Go to Settings → Integrations and open Microsoft Clarity, Hotjar or FullStory.
- Switch on Tag session recordings with the variant.
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 in its When event takes place settings for the shown event, use Tag the session recording with the variant. Tick the tools this action tags in, or none to leave it out. Left off, the action follows the account’s setting.
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: Segment, Mixpanel. These send the campaign’s events to your analytics, rather than tagging recordings.