---
title: "Connect Microsoft Clarity to Rig — Rig guide"
description: "Connect Microsoft Clarity to Rig with a Data Export API token and build a daily history of traffic, scroll depth and click behaviour."
canonical: "https://rig.so/guides/connect-microsoft-clarity"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect Microsoft Clarity to Rig

Sync Microsoft Clarity's daily engagement snapshots into Rig: traffic, active time, scroll depth and rage, dead and error clicks, split by device, channel, URL and country. Clarity connects with one Data Export API token per project.

## Before you start

- You need to be an **admin** of the Clarity project. Only project admins can generate a Data Export token.
- Clarity's export is a dashboard summary of the last 24 hours. It carries no individual sessions or recordings, so the history Rig holds starts on the day you connect.

## Step 1: Generate a Clarity Data Export token

1. Open your project in Microsoft Clarity.
2. Go to **Settings** and open **Data Export**.
3. Click **Generate new API token** and give it a name.
4. Copy the token straight away. Clarity shows it once, so generate a new one if you lose it.

## Step 2: Connect it in Rig

New to Rig? Watch how to find Connections

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`.
2. Search for **Microsoft Clarity**, open the card and click `Connect`.
3. **Data Export API token (JWT)**: paste the token you generated.
4. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
5. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection.

## What Rig pulls in

Microsoft Clarity lands in its own `microsoft_clarity` schema in your warehouse:

- **Insights overview**: headline traffic and engagement metrics for the project.
- **Insights by device**: the same measures by browser, device type and operating system.
- **Insights by channel**: traffic by source, medium, campaign and channel.
- **Insights by URL**: popular pages and how people behave on them.
- **Insights by country**: traffic and engagement by country or region.

Each row carries a `snapshot_date`, the UTC day it was pulled. New snapshots are appended, so the tables grow into a daily time series.

## Good to know

- Clarity allows 10 export requests per project per day. Rig spends five on a sync and runs it at most once per UTC day, which leaves room for your own use of the export.
- A second sync on the same UTC day returns nothing by design, so the Sync button will not add data until the next day.
- Clarity returns at most 1,000 rows per request with no paging, so a site with very many URLs sees its most prominent ones.
- To disconnect Microsoft Clarity, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

## What people use this for

- Track frustration signals over time
- Join behaviour signals to revenue
- Compare behaviour across devices and sources

[More ideas for using Microsoft Clarity](https://rig.so/integrations/microsoft-clarity)

## Microsoft Clarity documentation

- [Clarity Data Export API](https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-data-export-api)

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-microsoft-clarity)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)