Skip to content
Start for free

Default

Capture forms and hand off to meetings with Default, under the consent each part needs. The Pixel waits for measurement, and the Forms SDK waits for functionality.

Inth keeps the consent record of each choice, with the visitor’s country and the policy that applied.

Start for free
pnpm add @c15t/integrations
DefaultWaiting for consent
Before a choice

With the default mode, no Default globals, queues or loader appear.

Turn the switch on, then off, to see what loads.

Before you start

You need an Inth project that connects to your app and c15t in that app. You also need the public key from your Default workspace.

The public key is browser configuration, not a secret API key.

Open the quickstart for your framework

How consent works with Default

Use defaultComPixel for automatic form capture and the Default scheduler handoff. Use defaultComFormsSdk for a standalone SDK install, such as a custom form.

Before the Pixel loads, the helper queues one setConsent command. It maps c15t measurement to Default analytics, and marketing to Default marketing.

With measurement on and marketing off, company identification can run, but Default loads no new Vector script.

On withdrawal, the helper keeps the loader and sends both fields as false. Keep reloadOnConsentRevoked on, since form and partner activity can go on until the page changes.

Installation

The Pixel has two load modes. The Forms SDK always waits for its category.

Installation

In the always mode, the Pixel can capture and send form submissions before consent. Default analytics and marketing do not gate those requests.

Setup steps

  1. Install the integration package

    Add the helpers next to c15t. An import alone does not start Default.

    pnpm add @c15t/integrations

  2. Add your public key

    This file uses the Pixel. Pass category: 'marketing' to make the Pixel wait for marketing instead.

    src/consent-scripts.ts
    import { defaultComPixel } from '@c15t/integrations/default-com';

export const scripts = [defaultComPixel({ publicKey: 'YOUR_PUBLIC_KEY' })];

    Use one helper per page. If you register both, the second one logs an error and does not load.

  3. Or use the standalone Forms SDK

    For a custom form, Pardot or an API proxy, use this file in place of the Pixel file. It waits for functionality.

    src/consent-scripts.ts
    import { defaultComFormsSdk } from '@c15t/integrations/default-com';

export const scripts = [defaultComFormsSdk({ publicKey: 'YOUR_PUBLIC_KEY' })];

    Both files are alternatives. Do not combine their arrays.

  4. Register it with your existing setup

    Add scripts to the c15t configuration that you have now. Keep your Inth endpoint, mode, policy, styles and consent UI.

    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.

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

export default defineConsentConfig({ scripts });

    Pass scripts to the ConsentRoot in your root route. Import helpers in the route module, not in a server function: script configurations carry callbacks.

    src/routes/__root.tsx
    import { scripts } from '../consent-scripts';

<ConsentRoot state={consent} scripts={scripts}>

    Add scripts to the options of your ConsentProvider, next to mode. Keep the banner, dialog and preferences link inside the provider.

    src/consent.tsx
    import { scripts } from './consent-scripts';

<ConsentProvider options={{ mode, scripts }}>

    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.

    app/app.config.ts
    import { scripts } from '../src/consent-scripts';

export default defineAppConfig({
  c15t: { scripts },
});

    Pass scripts to the c15tVue plugin call you have now. The plugin starts one script loader when the app mounts.

    src/main.ts
    import { c15tVue, manifest } from 'c15t/vue/vue-plugin';
import { scripts } from './consent-scripts';

app.use(c15tVue, {
  mode: manifest(),
  scripts,
});

    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.

    src/c15t.client.ts
    import type { C15tClientOptionsExtension } from 'c15t/astro';
import { scripts } from './consent-scripts';

export default { scripts } satisfies C15tClientOptionsExtension;

    Pass scripts as a prop to the ConsentProvider you have now. The provider owns the loader and disposes it on unmount.

    src/App.svelte
    <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>

    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.

    src/routes/+layout.svelte
    <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>

    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.

    index.html
    <script type="text/plain" data-c15t-category="measurement">
  // The vendor's snippet, unchanged
</script>

    Pass scripts to init() from @c15t/browser, next to your mode. With createConsentRuntime, pass scripts to it instead.

    src/consent.ts
    import { init, manifest } from '@c15t/browser';
import { scripts } from './consent-scripts';

const consent = init({
  mode: manifest(),
  scripts,
});
All frameworks

Remove direct Default snippets, tag manager copies and other SDK installs first. The helpers support the current handshake.default.com scripts only.

Verify your setup

Filter DevTools Network by default.com. Then test the three states with the Pixel.

  • Before a choice

    With the default mode, no Default globals, queues or loader appear.

  • After you allow measurement

    index.js loads, and the first setConsent command reads analytics true and marketing false.

  • After you withdraw consent

    The loader stays and receives both fields as false. Then c15t reloads the page.

Default keeps its _dflt_consent cookie after withdrawal. Vector cookies and storage stay too, since the helper does not clear partner data.

Open the full Default guide