Skip to content
Start for free

RB2B

Find the companies and US visitors behind your traffic with RB2B, only after visitors allow marketing. Until then, no RB2B request leaves the page.

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

Allow only another category. No vendor requests, reb2b global, cookies or storage 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 account key from Script Setup in RB2B, where the snippet calls reb2b.load.

Add your domain in RB2B first. The RB2B script does not run on domains that you have not added.

Open the quickstart for your framework

How consent works with RB2B

Before marketing has permission, the c15t rb2b helper defines no reb2b global and loads nothing.

After consent, the helper loads your account script. It sends no identify calls and sets no rb2bConfig.

RB2B has no documented stop API. So on withdrawal, c15t reloads the page, and RB2B stays blocked while consent stays off.

The helper runs once per page load. In client routed apps, use full page links for each page view that you want RB2B to count.

Installation

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

Wait for permission. No request goes to RB2B until the visitor accepts marketing. On withdrawal, c15t reloads the page.

rb2b({ accountKey })

An opt-out policy or no policy gives optional categories permission before a choice. Then RB2B loads on the first page. This guide uses an opt-in policy.

Setup steps

  1. Install the integration package

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

    pnpm add @c15t/integrations

  2. Add your account key

    The helper trims and encodes the key. An invalid or blank key logs an error, and RB2B does not load.

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

export const scripts = [rb2b({ accountKey: 'YOUR_RB2B_KEY' })];

    RB2B labels some of its cookies functional, but the helper uses marketing. Pass scriptUrl only if your dashboard snippet uses another supported URL.

  3. 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="marketing">
  // 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 direct snippet and any tag manager copy, so they cannot bypass c15t. Do not add your own reb2b stub.

Verify your setup

Use a fresh browser profile. Check Network and storage in DevTools. Then test the three states.

  • Before a choice

    Allow only another category. No vendor requests, reb2b global, cookies or storage appear.

  • After you allow marketing

    The loader URL matches the one in your account snippet.

  • After you withdraw marketing

    c15t reloads the page, and RB2B stays blocked on the new page.

The reload does not clear RB2B storage, such as _reb2buid. Check the current account script for the full list of cookies.

Open the full RB2B guide