# Clearbit

The c15t clearbit helper loads the Clearbit tag only after visitors allow marketing in Inth. On withdrawal, c15t removes the tag and reloads the page.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/clearbit)
- [Clearbit](https://clearbit.com/)

Enrich visits with Clearbit company data only for visitors who allow marketing. Until then, tags.js stays off the page.

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 publishable key from your Clearbit tag installation.

Never put a secret Clearbit API key in browser code.

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

## How consent works with Clearbit

Clearbit names visitors and their companies for enrichment. So the c15t clearbit helper uses marketing, not measurement.

While marketing has permission, tags.js loads with a strict-origin-when-cross-origin referrer policy.

The helper sends no consent signal to Clearbit.

On withdrawal, c15t removes the script element and calls no Clearbit API. By default, c15t also reloads the page.

## Installation

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

### Wait for permission

No request goes to Clearbit until the visitor accepts marketing. On withdrawal, c15t removes the tag and reloads the page.

```ts
clearbit({ publishableKey })
```

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

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

#### Add your publishable key

The helper trims the key and encodes it into the loader URL. An empty key logs an error, and the tag does not load.

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

export const scripts = [clearbit({ publishableKey: 'YOUR_PUBLISHABLE_KEY' })];
```

Use scriptUrl to change the loader URL. A blank value falls back to the default.

### 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 the original Clearbit tag, so it cannot load without consent.

## Verify your setup

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

- **Before a choice**: Allow measurement only. Nothing loads from Clearbit.

- **After you allow marketing**: The tags.js request carries your publishable key in its path.

- **After you withdraw marketing**: c15t removes the tag and reloads the page. The new page loads nothing from Clearbit.

Check that no other tag, such as a tag manager copy, still loads tags.js.

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

## Related guides

- [Clay](/integrations/clay)

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

- [RB2B](/integrations/rb2b)