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

# Microsoft Clarity

> Give the operator console read access to Microsoft Clarity insights — generate a data-export API token on the project and enter it, mindful of Clarity's ten-requests-a-day quota.

# Microsoft Clarity

Powers the operator console's Clarity insights card — sessions, engagement, dead and rage clicks on the marketing site.

**Scope: Global defaults** only — a platform operator feature.

## 1. In Clarity

1. [clarity.microsoft.com](https://clarity.microsoft.com) → open the project → **Settings → Data export → Generate new API token**. You must be an **Admin** on the project.
2. Name it for the console so it can be revoked independently, and copy it.
3. The project id is the segment in the project URL — useful context, not needed by the API.

## 2. Enter it in KnoxCall

**Settings → Integrations → Global defaults → Microsoft Clarity** → *Configure*:

| Field                                   | Value                |
| --------------------------------------- | -------------------- |
| **Data-export API token**               | The token            |
| **Clarity project ID** *(display only)* | From the project URL |

**Save credentials.**

## 3. Verify

The operator console's *Test connection* makes one minimal live-insights call. **It spends one of the day's requests.**

## Things that bite

* **Hard quota: roughly ten export requests per project per day.** Every test click and every uncached page load burns one, which is why the console caches aggressively.
* **Aggregated only.** Clarity returns insights over a one-to-three-day window; live visitor counts come from [GA4](/integrations/setup/google-analytics).
* **No environment fallback exists for this type.**