Skip to content
GROWTH DEPT.CRO

Microsoft Clarity + Growth Dept CRO

Tag each Clarity session with the visitor's test group, so recordings and heatmaps can be filtered by group.

  • A cro_<test id> custom tag per test
  • Set after the shopper's consent
  • One switch in Integrations
With Clarity tagging on, the storefront sets a cro_<test id> custom tag to the visitor's group key on every page view. Filter recordings and heatmaps by that tag to watch how each group used the page.

At a glance

Does Growth Dept CRO work with Microsoft Clarity?

What does Clarity receive?

A custom tag named cro_<test id> with the visitor's group key.

Does Growth Dept CRO add Clarity to my store?

No. Clarity's own tag must already be on the store; without it the tags do nothing.

When are tags set?

Once per page view, after the shopper's analytics consent.

Who can turn it on?

Admins and owners, with a switch in Integrations.

How it works

How Microsoft Clarity and Growth Dept CRO work together

Switch it on

Turn on Clarity tagging in Integrations.

A visitor enters a test

The runtime notes the group before the page paints.

The session is tagged

Clarity records cro_<test id> with the group, for filtering later.

Get started

To get started

  1. 01

    Check Clarity is installed

    Clarity's own tag must already load on your store.

  2. 02

    Turn on tagging

    Integrations, Microsoft Clarity, Connect.

  3. 03

    Filter by group

    In Clarity, filter recordings and heatmaps by the cro_<test id> tag.

What it works with

Every storefront test typeTheme installs
clarity.microsoft.com

FAQ

Microsoft Clarity questions

Does it work if Clarity loads late?
Yes. The storefront queues the tags with Clarity's own queue, and Clarity reads them when it loads.

Find out what is worth testing on your store.

Book a 45-minute call with the Growth Dept team. We look at your store and your traffic, and tell you which tests to run first.