# Plausible Analytics

The c15t plausibleAnalytics helper loads Plausible Analytics only after visitors allow measurement in Inth. A queue stub holds calls that your code makes before the tracker loads.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/plausible-analytics)
- [Plausible Analytics](https://plausible.io/)

Load Plausible Analytics only after visitors allow measurement. Calls that your code makes before the tracker loads wait in a queue.

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 script ID from your Plausible snippet. It is the \<id> part of the pa-\<id>.js file name.

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 works with Plausible

Plausible sets no cookies, but c15t still waits for measurement permission. Until then, c15t does not define window.plausible. The helper sends no consent signal to Plausible.

When measurement gets permission, the helper defines a window.plausible stub that queues calls. Then it loads the tracker.

Sites with the legacy snippet can pass domain instead of scriptId. Then use extension to choose features such as file downloads and outbound links.

## Installation

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

### Wait for permission

No request goes to Plausible until the visitor accepts measurement. On withdrawal, c15t removes the script and reloads the page.

```ts
plausibleAnalytics({ scriptId })
```

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

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

#### Add your script ID

The helper loads pa-\<scriptId>.js and sends your other options, such as customProperties, as init options.

```
import { plausibleAnalytics } from '@c15t/integrations/plausible-analytics';

export const scripts = [plausibleAnalytics({ scriptId: 'YOUR_SCRIPT_ID' })];
```

If scriptId and domain are both empty, the helper 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 Plausible snippet, so the tracker loads only through c15t. If you already have a scripts array, add the helper to it.

## Verify your setup

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

- **Before a choice**: No request goes to plausible.io. In the Console, window.plausible returns undefined.

- **After you allow measurement**: pa-\<scriptId>.js loads without a page reload. A page view request goes to plausible.io/api/event or to your endpoint.

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

After withdrawal, window.plausible still exists. If your code sends custom events through it, check measurement permission before each call.

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

## Related guides

- [Promptwatch](/integrations/promptwatch)

- [Rybbit Analytics](/integrations/rybbit-analytics)

- [Statable](/integrations/statable-analytics)