> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abconvert.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Clarity Integration

> Tag Microsoft Clarity recordings, heatmaps, and dashboard sessions with the ABConvert test and test group a visitor sees.

<Warning>
  **Pre-release.** This guide applies when the Integrations hub is enabled for your ABConvert account.
</Warning>

Use Microsoft Clarity to review the sessions behind an ABConvert test result. ABConvert adds three session tags and one assignment event after an eligible visitor receives a test group.

## Configure Clarity and ABConvert

<Steps>
  <Step title="Create or select a Clarity project">
    Add your storefront domain to the Microsoft Clarity project that should receive recordings. Install the Clarity tracking code on storefront pages under your analytics-consent policy.
  </Step>

  <Step title="Enable Clarity in ABConvert">
    In **Integrations**, enable **Microsoft Clarity**. ABConvert uses the existing `clarity` browser function and does not need a project ID or a second tracking snippet.
  </Step>

  <Step title="Generate an eligible assignment">
    In a fresh, consented browser, visit a page where an active test can assign the visitor. Preview, forced-assignment, and automation-excluded visits do not send integration tags.
  </Step>

  <Step title="Verify the recording">
    Open **Recordings** in the same Clarity project. Inspect the recording event details for `abconvert_assignment`, then filter by the ABConvert custom tags. New tag names can take 30 minutes to two hours to appear in filter menus.
  </Step>
</Steps>

## What Clarity receives

| Tag or event               | Value                             |
| -------------------------- | --------------------------------- |
| `abconvert_test`           | Test name                         |
| `abconvert_test_group`     | Test group name                   |
| `abconvert_test_and_group` | `<test name> - <test group name>` |
| `abconvert_assignment`     | Fixed Clarity event name          |

The combined tag prevents an ambiguous filter when a visitor is in two tests that use the same test-group name. Names are capped at 255 characters to meet Clarity's tag limit.

## Use cases

* **Review friction by test group:** filter recordings to compare rage clicks, scroll depth, and dead clicks for Control and a non-control test group.
* **Validate a page change:** use the assignment event to find the first recording that saw a new price, layout, or offer.
* **Compare heatmaps:** apply the combined tag before comparing clicks on a call to action across test groups.

## Things to know

* Clarity tags are session context. They do not create a Clarity conversion metric or send order revenue.
* **Connected** confirms ABConvert called Clarity's browser API. Confirm a recording in Clarity before using the tags for analysis.
* Clarity custom tags can be delayed in filter menus. Recording event details may show the tag sooner.
* Rename a running test only if you accept that later recordings use the new tag value. Use a stable test name when you need one filter across the test's lifetime.