# Databuddy

The c15t databuddy helper loads Databuddy only after visitors allow measurement in Inth, or loads it disabled until they do. It also controls session replay and stops it on withdrawal.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/databuddy)
- [Databuddy](https://www.databuddy.cc/)

Run Databuddy analytics and session replay under measurement consent. Choose when databuddy.js loads and turn off the data that you do not 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 client ID from your Databuddy project.

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 Databuddy

The c15t databuddy helper sets window.databuddyConfig and its disabled key from consent. On withdrawal, it disables the tracker, stops session replay and c15t reloads the page.

Databuddy collects some data unless the site turns it off. Use the features switches to stop collection of interactions, Web Vitals, errors or outgoing links.

Set replay to load replay.js. The helper adds it only while measurement has permission, in each load mode. Replay masks page text and typed input by default.

Do not also add replay.js as a plain script tag. Outside c15t, it can start to record before the visitor makes a choice.

## Installation

The helper has two modes for when Databuddy loads. Pick the mode that your policy needs.

### Wait for permission

No request goes to Databuddy and Databuddy stores nothing until the visitor accepts measurement.

```ts
loadMode: 'after-consent'
```

### Load and signal

databuddy.js loads on each page and stores a visitor ID in localStorage, but disabled stops data transfer.

```ts
loadMode: 'always'
```

Databuddy's own guidance is to wait for consent where prior consent is necessary. Use always only where your policy allows it. 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 client ID

The helper sends the client ID to the script as data-client-id. The features switch in this example stops interaction capture.

```
import { databuddy } from '@c15t/integrations/databuddy';

export const scripts = [
  databuddy({
    clientId: 'YOUR_CLIENT_ID',
    loadMode: 'after-consent',
    features: { interactions: false },
  }),
];
```

An empty client ID 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 each old Databuddy or replay.js script tag, each \<Databuddy /> component from @databuddy/sdk and any code that sets window.databuddyConfig. A value that is already there overrides the helper.

## Verify your setup

These checks use the after-consent mode and an opt-in policy. Open a private window and DevTools Network and Application. Then test the three states.

- **Before a choice**: No request goes to cdn.databuddy.cc or basket.databuddy.cc. localStorage has no did key.

- **After you allow measurement**: databuddy.js loads without a reload, with your data-client-id. With replay on, replay.js loads and a POST to /replay follows after you scroll.

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

replay: { maskText: false } records page text. Use it only on pages that show no personal data, such as names, email addresses or order details.

[Open the full Databuddy guide](https://c15t.com/docs/integrations/databuddy)

## Related guides

- [Fathom Analytics](/integrations/fathom-analytics)

- [Google Analytics](/integrations/google-analytics)

- [Matomo Analytics](/integrations/matomo-analytics)