# Clay

The c15t clay helper loads Clay web intent only after visitors allow marketing in Inth. On withdrawal, it sends denyCookieConsent and c15t reloads the page.

## Key facts

- **Tool:** Clay
- **Category:** Other
- **Consent categories:** Marketing
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/clay)
- [Clay](https://www.clay.com/)

See which companies visit your site with Clay web intent, once visitors allow marketing. Measurement alone loads nothing from Clay.

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 id from Settings > Web intent > JavaScript Snippet in Clay.

Clay resolves IP addresses to companies and can use device fingerprints. That is why the helper waits for marketing.

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

## How consent works with Clay

Before marketing has permission, the c15t clay helper loads nothing. No Claydar global or vendor storage appears.

After consent, a script element in the body loads the Clay tracker. On load, the helper queues giveCookieConsent.

On withdrawal, the helper calls denyCookieConsent when it is available. Denial moves identifiers into session storage, but it does not stop requests.

So keep reloadOnConsentRevoked on. The reload ends the tracker, and Clay stays blocked on the next page.

## Installation

Clay has one load mode in c15t. The helper waits for marketing permission.

### Wait for permission

No request goes to Clay until the visitor accepts marketing. On withdrawal, c15t reloads the page.

```ts
clay({ siteId })
```

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

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

#### Add your site ID

The helper trims the ID and encodes it into the loader URL. A blank or invalid ID logs an error, and Clay does not load.

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

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

Allow cdn.claydar.com and api.claydar.com in your CSP. For a proxy, keep the id query parameter in scriptUrl.

### 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="marketing">
  // 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 direct Clay snippet or tag manager copy, so it cannot bypass c15t. The Clay CMP detection does not cover c15t.

## Verify your setup

Filter DevTools Network by claydar.com. Then test the three states.

- **Before a choice**: Deny, or allow measurement only. No requests, Claydar global or vendor storage appear.

- **After you allow marketing**: One init.v1.js loader with your site ID loads, then the tracker.

- **After you withdraw marketing**: c15t reloads the page, and Clay stays blocked on the new page.

The tracker uses claydar\_\* cookies and local storage, with a device ID cookie that lasts one year. Your account settings can change this list.

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

## Related guides

- [Clearbit](/integrations/clearbit)

- [Default](/integrations/default-com)

- [RB2B](/integrations/rb2b)