Croct + Microsoft Clarity

Croct sets three custom tags on every session: croct_experiences with the experiences that impacted the session, croct_audiences with the audiences the visitor fits, and croct_experiments with each running experiment and the variant assigned. Each tag carries the full list of values, so a visitor who fits three audiences carries all three names.

It powers qualitative analysis. You can filter recordings and heatmaps by the exact audience, experience, experiment, or variant a visitor was part of, so you watch the sessions that actually matter instead of scrubbing through everything.

Filter session recordings by audience, experience, or experiment variant, compare heatmaps between the variants of an experiment, and spot where personalized visitors drop off, rage click, or hesitate.

The tags are refreshed on every pageview, including in single-page applications, so the session always reflects the audiences, experiences, and experiments that are current for the visitor.

No. The integration waits for the Clarity tracking code when it hasn't loaded yet, so the tags are set regardless of which script loads first.

No. The integration only adds Croct's context alongside the recordings you already capture, so your existing dashboards and heatmaps keep working exactly as before.

Not always. Croct can track several events within 2–3 milliseconds, but Clarity caps how many it keeps: it records up to 100,000 sessions per project per day and starts sampling once your traffic exceeds that, so not every session or event is captured. As a result, you may see fewer events in Clarity than Croct actually tracked. See Clarity's FAQ on sampling and limits for details.

Next to none. The integration is a single script you add to your website, either directly in the HTML or through Google Tag Manager. From there, Croct sets the tags automatically, with no extra tracking code to write or maintain.