# Ada

The c15t ada helper imports the Ada Messaging Web SDK only after visitors allow functionality in Inth. On withdrawal, it calls stop() and c15t reloads the page.

## Key facts

- **Tool:** Ada
- **Category:** Support and chat
- **Consent categories:** Functionality
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/ada)
- [Ada](https://www.ada.cx/)

Answer visitors with your Ada AI Agent chat, once they allow functionality. Before that, c15t imports no Ada SDK and Ada gets no request.

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 and c15t in that app. You also need the public handle of your AI Agent from your Ada team.

Set cluster or domain only when Ada gives you a regional configuration.

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

## How consent works with Ada

The c15t ada helper imports the Ada Messaging Web SDK only after functionality has permission. Then it starts the widget with your handle.

The helper keeps the Messaging interface private. It creates no window.adaEmbed or window.adaSettings global.

On withdrawal, the helper calls the Ada stop() method to remove the widget. By default, c15t also reloads the page.

stop() does not delete stored conversations or cookies. Ada has no documented consent signal.

## Installation

Ada has one load mode in c15t. The helper waits for functionality permission.

### Wait for permission

No request goes to Ada until the visitor accepts functionality. On withdrawal, the helper stops the widget and c15t reloads the page.

```ts
ada({ handle })
```

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

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

#### Add your Ada handle

The helper trims the handle. A blank handle logs an error, and Ada does not load.

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

export const scripts = [ada({ handle: 'YOUR_ADA_HANDLE' })];
```

With a Content Security Policy, allow messaging-assets.ada.support in script-src, connect-src and frame-src. Also allow the API origin of your Agent in connect-src.

### 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="functionality">
  // 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 any other Ada module snippet, embed2.js tag or tag manager copy. Ada supports only one Messaging interface per page, so keep one ada helper in your scripts.

## Verify your setup

Use a private window with an opt-in policy. Filter DevTools Network by ada.support. Then test the three states.

- **Before a choice**: No Ada module, manifest, iframe or API request appears.

- **After you allow functionality**: sdk.js and the Ada launcher load. window.adaEmbed stays undefined.

- **After you withdraw functionality**: The helper calls stop(), and c15t reloads the page. The new page makes no Ada request.

Keep the reload on. If consent ends before the SDK import finishes, only the reload ends that work.

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

## Related guides

- [Crisp](/integrations/crisp)

- [Front Chat](/integrations/front-chat)

- [Google Maps](/integrations/google-maps)