# Microsoft Clarity

The c15t clarity helper loads Microsoft Clarity only after visitors allow measurement in Inth. It sends measurement and marketing choices to Clarity through the Consent V2 API.

## Key facts

- **Tool:** Microsoft Clarity
- **Category:** Session replay
- **Consent categories:** Measurement, Marketing
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/microsoft-clarity)
- [Microsoft Clarity](https://clarity.microsoft.com/)

Load Microsoft Clarity only after visitors allow measurement, and send each choice through the Clarity Consent V2 API.

Inth keeps the consent record of each choice, with the visitor’s country and the policy that applied.

[Start for free](/dashboard/sign-up)

## Before you start

You need an Inth project that connects to your app, c15t in that app and the Clarity project ID. The ID follows https://www.clarity.ms/tag/ in your Clarity tracking code.

New to c15t? Complete the quickstart for your framework first. Keep its Inth endpoint, policy, styles and consent UI.

[Open the quickstart for your framework](https://c15t.com/docs/frameworks)

## How consent gets to Clarity

The c15t clarity helper loads Clarity only while measurement has permission.

Before the loader runs, the helper queues clarity('consentv2', ...). Measurement sets analytics\_Storage, and marketing sets ad\_Storage.

Each later change sends a new consentv2 call. So if a visitor allows marketing later, ad\_Storage changes without a reload of Clarity.

On withdrawal, Clarity stays on the page and gets analytics\_Storage: 'denied'. c15t reloads the page by default. Denied storage limits what Clarity stores. It does not stop all Clarity requests.

[Read the Clarity Consent V2 API](https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-consent-api-v2)

## Installation

Clarity has one load mode in c15t. The helper waits for measurement permission.

### Wait for permission

No request goes to Clarity until the visitor accepts measurement. Each choice then goes to Clarity through consentv2.

```ts
clarity({ id })
```

An opt-out policy or no policy gives optional categories permission before a choice. Then Clarity loads on the first page. This guide uses an opt-in policy.

## Setup steps

#### Install the integration package

Add the helpers next to c15t. An import alone does not start Clarity.

```
pnpm add @c15t/integrations
```

#### Add your project ID

The helper builds the loader URL from the ID. Use defaultConsent only to replace the values in the first consentv2 call.

```
import { clarity } from '@c15t/integrations/microsoft-clarity';

export const scripts = [clarity({ id: 'YOUR_PROJECT_ID' })];
```

An empty ID logs an error, and the script does not load. defaultConsent: true gives ad storage permission even when the visitor refuses marketing.

### Register it with your existing setup

#### Next.js

Add scripts to c15t.config.ts, next to next.config.ts. Keep the rest of your config, such as mode, in the same call. App Router, Pages Router and static export read the same file.

```
import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });
```

#### TanStack Start

Pass scripts to the ConsentRoot in your root route. Import helpers in the route module, not in a server function: script configurations carry callbacks.

```
import { scripts } from '../consent-scripts';

<ConsentRoot state={consent} scripts={scripts}>
```

#### React

Add scripts to the options of your ConsentProvider, next to mode. Keep the banner, dialog and preferences link inside the provider.

```
import { scripts } from './consent-scripts';

<ConsentProvider options={{ mode, scripts }}>
```

#### Nuxt

Register scripts under the c15t key in app.config.ts. Keep them out of nuxt.config.ts, which reaches the browser as JSON and drops the helper callbacks.

```
import { scripts } from '../src/consent-scripts';

export default defineAppConfig({
  c15t: { scripts },
});
```

#### Vue

Pass scripts to the c15tVue plugin call you have now. The plugin starts one script loader when the app mounts.

```
import { c15tVue, manifest } from 'c15t/vue/vue-plugin';
import { scripts } from './consent-scripts';

app.use(c15tVue, {
  mode: manifest(),
  scripts,
});
```

#### Astro

Add scripts to the client entrypoint, which the integration finds on its own. Keep helpers out of astro.config.mjs: its options are serialized into the page.

```
import type { C15tClientOptionsExtension } from 'c15t/astro';
import { scripts } from './consent-scripts';

export default { scripts } satisfies C15tClientOptionsExtension;
```

#### Svelte

Pass scripts as a prop to the ConsentProvider you have now. The provider owns the loader and disposes it on unmount.

```
<script lang="ts">
  import { ConsentProvider, manifest } from 'c15t/svelte';
  import { scripts } from './consent-scripts';
</script>

<ConsentProvider mode={manifest()} {scripts}>
  <!-- Your app and consent UI -->
</ConsentProvider>
```

#### SvelteKit

Add scripts to the ConsentRoot in the root layout. Import helpers in the layout component, not in +layout.server.ts: a server load cannot send functions to the browser.

```
<script lang="ts">
  import { ConsentRoot } from 'c15t/svelte';
  import { scripts } from '../consent-scripts';

  let { children, data } = $props();
</script>

<ConsentRoot state={data.consent} {scripts}>
  {@render children()}
</ConsentRoot>
```

#### HTML: Paste the vendor’s snippet behind consent

The helpers need a bundler. On a page with the c15t script tag, paste the vendor’s own snippet instead and keep it inert until visitors allow its category. Helper options, such as loadMode, do not apply.

```
<script type="text/plain" data-c15t-category="measurement">
  // The vendor's snippet, unchanged
</script>
```

#### JavaScript

Pass scripts to init() from @c15t/browser, next to your mode. With createConsentRuntime, pass scripts to it instead.

```
import { init, manifest } from '@c15t/browser';
import { scripts } from './consent-scripts';

const consent = init({
  mode: manifest(),
  scripts,
});
```

Remove the old Clarity tracking code, so Clarity loads only through c15t. A visitor who turns off the microsoft-clarity vendor gets both channels denied.

## Verify your setup

Use a private window with an opt-in policy. Open DevTools Network and filter by clarity. Then test the three states.

- **Before a choice**: No request goes to www.clarity.ms. Allow only marketing. Clarity still does not load, because it waits for measurement.

- **After you allow measurement**: The request to www.clarity.ms/tag/\<id> appears without a page reload.

- **After you withdraw measurement**: Save your choice. c15t reloads the page. The new page sends no request to Clarity.

If your code calls window.clarity directly, check measurement permission before each call.

[Open the full Clarity guide](https://c15t.com/docs/integrations/microsoft-clarity)

## Related guides

- [Sentry](/integrations/sentry)

- [Vercel Speed Insights](/integrations/vercel-speed-insights)

- [FullStory](/integrations/fullstory)