# Mixpanel

The c15t mixpanelAnalytics helper loads the Mixpanel SDK on each page and keeps it opted out until visitors allow measurement in Inth. Each consent change calls the related Mixpanel opt-in or opt-out method.

## Key facts

- **Tool:** Mixpanel
- **Category:** Analytics
- **Consent categories:** Measurement
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/mixpanel-analytics)
- [Mixpanel](https://mixpanel.com/)

Load Mixpanel on each page and keep it opted out until visitors allow measurement. Events from a visitor who already agreed stay in order.

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 32 character project token from your Mixpanel snippet.

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 Mixpanel

The c15t mixpanelAnalytics helper loads the Mixpanel SDK on each page, before a choice. It uses the measurement category with alwaysLoad.

The helper sets opt\_out\_tracking\_by\_default and opt\_out\_persistence\_by\_default to true. So a visitor with no stored opt-in starts opted out. Mixpanel then tracks nothing and stores no visitor ID.

Before the SDK loads, the helper queues opt\_in\_tracking or opt\_out\_tracking. Mixpanel runs that call during init, before queued track calls. It calls the related method again on each consent change.

The SDK writes an empty mp\_\* cookie as it starts and removes it in the same page load.

## Installation

Mixpanel has one load mode in c15t. The SDK loads on each page and follows measurement permission.

### Load opted out

The SDK loads before a choice but stays opted out. It sends events only while measurement has permission.

```ts
mixpanelAnalytics({ token })
```

An opt-out policy or no policy gives optional categories permission before a choice. Then Mixpanel opts in 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 the Mixpanel SDK.

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

#### Add your project token

The helper sends the token to mixpanel.init. Your initOptions merge over the opt-out defaults.

```
import { mixpanelAnalytics } from '@c15t/integrations/mixpanel-analytics';

export const scripts = [
  mixpanelAnalytics({ token: '0123456789abcdef0123456789abcdef' }),
];
```

The token must be 32 hexadecimal characters. Any other value logs an error, and the script does not load.

### 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 Mixpanel snippet, so the SDK loads only through c15t. Before load, the helper queues track, identify, reset and register on the default instance only.

## Verify your setup

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

- **Before a choice**: The request to cdn.mxpnl.com appears before you choose. mixpanel.has\_opted\_out\_tracking() returns true. Call mixpanel.track('Test'). No event goes to Mixpanel.

- **After you allow measurement**: Without a page reload, has\_opted\_out\_tracking() returns false, and events go to Mixpanel.

- **After you withdraw measurement**: Save your choice. c15t reloads the page. The new page loads the SDK opted out.

Named instances and people.\* calls do not go into the queue. Check measurement permission before you call them.

[Open the full Mixpanel guide](https://c15t.com/docs/integrations/mixpanel-analytics)

## Related guides

- [Pendo](/integrations/pendo)

- [PostHog](/integrations/posthog)

- [Amplitude](/integrations/amplitude)