Skip to content
Start for free

RudderStack

Route customer events with RudderStack under each visitor's choice. Keep the SDK off the page until measurement, or send consent to your destinations.

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
RudderStackWaiting for consent
Before a choice

rsa.min.js loads. Destinations whose IDs map to a denied category receive no events.

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 source write key and the HTTPS data plane URL from your RudderStack source.

Keep control plane credentials out of the browser.

Open the quickstart for your framework

How consent works with RudderStack

By default, the c15t rudderstack helper loads nothing until measurement has permission. Then it queues load and page, and loads rsa.min.js.

In the default mode, the helper sends no consent signal to RudderStack. On withdrawal, c15t removes the script element.

With consentManagement, the SDK loads on every page in the RudderStack pre-consent mode. It keeps events in a buffer and uses no persistent storage.

The helper then calls rudderanalytics.consent() with the mapped consent IDs in the allowed or denied list.

Installation

The consentManagement option picks the mode. c15t cannot check your destination settings from the browser.

Installation

In destination consent mode, a visitor who turns off the rudderstack vendor gets every mapped ID denied. An empty map throws an error.

Setup steps

  1. Install the integration package

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

    pnpm add @c15t/integrations

  2. Add your write key and data plane URL

    The helper trims the key. A blank, invalid or non-HTTPS data plane URL logs an error, and the SDK does not load.

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

export const scripts = [
	rudderstack({
		writeKey: 'YOUR_SOURCE_WRITE_KEY',
		dataPlaneUrl: 'https://your-data-plane.example.com',
	}),
];

  3. Or map destination consent

    For destination consent mode, map c15t categories to your RudderStack consent IDs.

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

export const scripts = [
	rudderstack({
		writeKey: 'YOUR_SOURCE_WRITE_KEY',
		dataPlaneUrl: 'https://your-data-plane.example.com',
		consentManagement: {
			mapping: {
				measurement: ['YOUR_ANALYTICS_CONSENT_ID'],
				marketing: ['YOUR_ADVERTISING_CONSENT_ID'],
			},
		},
	}),
];

    Storage defaults to strategy none. A preConsent.storage value in loadOptions replaces it.

  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 the original RudderStack snippet, so it cannot load without consent.

Verify your setup

Use a private window with an opt-in policy. Then test the three states in destination consent mode.

  • Before a choice

    rsa.min.js loads. Destinations whose IDs map to a denied category receive no events.

  • After you allow measurement

    Without a reload, destinations with measurement IDs start to receive events.

  • After you withdraw measurement

    c15t reloads the page. Destinations with measurement IDs receive no events from the new page.

In the default mode, rsa.min.js loads only after you allow measurement, with a data-rsa-write-key attribute. Then a page event goes to your data plane URL.

Open the full RudderStack guide