Analytics

Clearbit

Configure Clearbit

Use the publishable key from your Clearbit tag installation. Do not put a secret Clearbit API key in browser code.

npm install @c15t/integrations@alpha

src/consent-scripts.ts

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

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

Register the scripts

Complete your framework quickstart first. Keep its Inth endpoint, policy, styles and consent UI. Remove the vendor's original script, SDK initializer or tag-manager entry, so the vendor loads only through c15t.

The vendor pages put the helper in src/consent-scripts.ts. If your framework quickstart already has a scripts array, such as the one in c15t.config.ts in the Next.js guide, add the helper to that array instead of creating a second file. The scripts export is a configuration, not an initializer. Add it to the c15t provider you already have, at the registration point for your framework below. These are edits to that provider, not a second provider.

Add the configuration to scripts in c15t.config.ts, next to next.config.ts:

import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });

Keep the rest of your config, such as mode and routePrefix, in the same call. ConsentRoot reads the config in the browser, so the layout keeps passing only state. App Router, Pages Router and static export all read the same file. See Next.js scripts and embeds.

Options

Option	Default	Behavior
`publishableKey`	Required	Publishable key. The helper trims it and URL-encodes it into the default loader URL. Empty or non-string values log an error and the script does not load.
`scriptUrl`	`https://tag.clearbitscripts.com/v1/<publishableKey>/tags.js`	Loader URL override. A blank value falls back to the default.

Loading and revocation

clearbit uses the marketing category, not measurement. Clearbit identifies visitors and their companies for enrichment, so c15t treats it as marketing even though these docs list it with analytics. The tags.js script loads with referrerpolicy="strict-origin-when-cross-origin" only while marketing is allowed. On revocation the helper removes the script element and calls no Clearbit API.

Verify Clearbit

Filter DevTools Network by clearbitscripts.com. After you allow marketing, the tags.js request carries your publishable key in its path. Allowing measurement alone loads nothing from Clearbit.

Test in a private window with an opt-in policy. Open DevTools Network, disable the cache and filter by the vendor's domain:

Load the page. No request goes to the vendor before you choose.
Click Reject, then reload. There is still no vendor request.
Open Privacy settings and allow the helper's category. The vendor script loads without a page reload.
Turn the category off again and save. c15t reloads the page, and the new page makes no vendor request.

c15t reloads on revocation because removing a script element does not stop code that already ran. The vendor's listeners, timers and queued events stay alive until the page unloads. If you set reloadOnConsentRevoked: false, stop the vendor yourself. Register a callback-only script whose onConsentChange calls the vendor's opt-out API, as shown in custom integrations, and check the permission before each of your own event calls. The reload does not delete cookies the vendor already set; see clear on revocation for your framework.

The helper sets vendor to its script ID, so once you declare that vendor a visitor can turn it off inside an allowed category. See vendor consent for your framework. The consent verification guide covers navigation, expiry and hosting checks.