# Rybbit Analytics

The c15t rybbitAnalytics helper loads Rybbit Analytics only after visitors allow measurement in Inth. Session replay, Web Vitals and other features run under that same choice.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/rybbit-analytics)
- [Rybbit Analytics](https://rybbit.com/)

Load Rybbit Analytics, its session replay and Web Vitals under one measurement choice. Add your site ID and turn on only the features that you need.

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 site ID from your Rybbit tracking 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 works with Rybbit

The c15t rybbitAnalytics helper loads script.js only while measurement has permission. It sends no consent signal to Rybbit.

Options such as sessionReplay and webVitals run inside the same script. So each feature that you turn on runs under the same measurement permission.

Boolean options become 'true' or 'false' data attributes. An option that you do not set adds no attribute, so Rybbit keeps its own default.

## Installation

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

### Wait for permission

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

```ts
rybbitAnalytics({ siteId })
```

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

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

#### Add your site ID

The helper sends the site ID to the script as data-site-id. Set analyticsHost to load Rybbit from a different host.

```
import { rybbitAnalytics } from '@c15t/integrations/rybbit-analytics';

export const scripts = [rybbitAnalytics({ siteId: 'YOUR_SITE_ID' })];
```

### 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 Rybbit snippet, so the script 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 rybbit or your analyticsHost. Then test the three states.

- **Before a choice**: No request goes to app.rybbit.io. Click Reject and reload. There is still no request.

- **After you allow measurement**: script.js loads without a page reload. Its script element has your data-site-id and a data attribute for each option that you set.

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

If your code calls window.rybbit.event or window.rybbit.identify, check measurement permission before each call.

[Open the full Rybbit Analytics guide](https://c15t.com/docs/integrations/rybbit-analytics)

## Related guides

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

- [Umami Analytics](/integrations/umami-analytics)

- [Vercel Analytics](/integrations/vercel-analytics)