---
title: AdRoll
description: Load AdRoll with c15t after marketing consent and verify its
  loader, storage and revocation behavior.
seoTitle: AdRoll consent with c15t
seoDescription: Load the AdRoll pixel only after marketing consent. Learn what
  adrollPixel queues, which storage AdRoll sets and how to verify it.
icon: radar
group: integrations
lastModified: "2026-10-26T22:16:35Z"
lastAuthor: Kaylee
---
AdRoll retargets site visitors with ads and measures conversions. The c15t
`adrollPixel` helper waits until the `marketing` category is allowed before it
sets the AdRoll globals, queues the first `pageView` and adds the loader.

AdRoll has no API to stop its pixel. When the visitor withdraws, the helper
leaves AdRoll on the page, and c15t's default page reload removes it.

## Configure AdRoll

Copy the advertiser ID and pixel ID from Analytics > Insights > Website > View
Pixel. Under Settings > Data Collection > Visitor Consent, choose **Use your
existing Consent Banner**. Otherwise AdRoll can show its own banner. AdRoll's
instructions for an existing banner say to wait for affirmative consent before
you deploy the pixel. The helper loads AdRoll once the `marketing` category is
allowed. Under an opt-out policy that can happen before the visitor chooses, so
use an opt-in policy if you need affirmative consent. Delete the direct pixel
snippet and any tag manager copy, so they can't load AdRoll without consent.

|Package manager|Command|
|:--|:--|
|npm|`npm install @c15t/integrations`|
|pnpm|`pnpm add @c15t/integrations`|
|yarn|`yarn add @c15t/integrations`|
|bun|`bun add @c15t/integrations`|

```ts title="src/consent-scripts.ts"
import { adrollPixel } from '@c15t/integrations/adroll';

export const scripts = [
	adrollPixel({ advertiserId: 'ADVERTISER_ID', pixelId: 'PIXEL_ID' }),
];
```

## Register the scripts

Complete your [framework quickstart](/docs/frameworks) 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.

**Next.js**

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

```ts title="c15t.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](/docs/frameworks/next/scripts).

**TanStack Start**

Import the configuration into your root route and pass it to the existing
`ConsentRoot` as a top-level prop. Keep the loader from the
[TanStack Start quickstart](/docs/frameworks/tanstack-start/quickstart):

```tsx title="src/routes/__root.tsx"
import { scripts } from '../consent-scripts';

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

Import vendor helpers in the root route module, not in a server function.
A server function's return value must be serializable, and script
configurations carry callbacks. See
[TanStack Start scripts](/docs/frameworks/tanstack-start/scripts).

**React**

Add the configuration to the existing `ConsentProvider` options, next to
`mode`:

```tsx title="src/consent.tsx"
import { scripts } from './consent-scripts';

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

`mode` is the `manifest()` value from the
[React quickstart](/docs/frameworks/react/quickstart). Keep the banner,
dialog and preferences link inside the provider. See
[React scripts and embeds](/docs/frameworks/react/scripts).

**Nuxt**

Register the scripts under the `c15t` key in `app/app.config.ts`. Adjust the
relative import to where you created `consent-scripts.ts`:

```ts title="app/app.config.ts"
import { scripts } from '../src/consent-scripts';

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

The Nuxt module merges this over its options in `nuxt.config.ts` and starts
one script loader in the browser after hydration, once it has applied the
visitor's stored choice and privacy signals. Keep `scripts` out of
`nuxt.config.ts`, which reaches the browser as JSON and drops the vendor
callbacks. Write the vendor IDs into `consent-scripts.ts`. See
[Nuxt scripts and embeds](/docs/frameworks/nuxt/scripts).

**Vue**

Pass the scripts to the existing `c15tVue` plugin call in `src/main.ts`:

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

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

Keep your existing `mode` and other options. The plugin starts one
script loader when the app mounts, after it has applied the visitor's stored
choice. Do not also call `createScriptLoader` from a component. See
[Vue scripts and embeds](/docs/frameworks/vue/scripts).

**Astro**

Add the scripts to the client entrypoint from the
[Astro quickstart](/docs/frameworks/astro/quickstart), `src/c15t.client.ts`,
which the integration finds on its own. Keep `astro.config.mjs` as it is.
If the module already exports scripts, combine the two arrays.

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

export default { scripts } satisfies C15tClientOptionsExtension;
```

Vendor helpers contain callbacks, and the integration options in
`astro.config.mjs` are serialized into the page, so do not put helpers in
the integration's `scripts` option. The integration passes the client
entrypoint to the one runtime every page shares, including across
`ClientRouter` navigation.

**Svelte**

Import the scripts in the component that owns your existing provider and
pass them as a top-level prop:

```svelte title="src/App.svelte"
<script lang="ts">
  import { ConsentProvider, manifest } from 'c15t/svelte';
  import { scripts } from './consent-scripts';
</script>

<ConsentProvider mode={manifest()} {scripts}>
  <!-- Keep your application, consent UI and preferences link here. -->
</ConsentProvider>
```

Retain the styles and consent UI from the [Svelte quickstart](/docs/frameworks/svelte/quickstart).
The provider owns the loader and disposes it on unmount.

**SvelteKit**

Add the scripts to the existing `ConsentRoot` in the root layout. Keep the
handle and the layout load from the [SvelteKit quickstart](/docs/frameworks/sveltekit/quickstart).

```svelte title="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()}
  <!-- Keep your consent UI and preferences link here. -->
</ConsentRoot>
```

Import vendor helpers in the layout component, not in `+layout.server.ts`:
a server load cannot send functions to the browser. Prerendered, static and
SPA-mode pages use the same `scripts` prop. If you pass an externally owned
`runtime` to the provider, register scripts when creating that runtime instead.

**HTML**

The helpers in `@c15t/integrations` are ES modules that need a bundler. On a
page that loads the c15t script tag, paste the vendor's own snippet instead
and keep it inert until its category is allowed:

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

Use the category this guide names for the vendor. c15t runs the snippet
once that category is allowed, and reloads the page when the visitor
withdraws it. Helper options on this page, such as `loadMode`, do not apply
to a pasted snippet. See [HTML scripts](/docs/frameworks/html/scripts).

**JavaScript**

Pass the scripts to `init()` from `@c15t/browser`, next to your mode:

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

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

Keep the mode from your quickstart. With
`createConsentRuntime` from `c15t/runtime`, pass `scripts` to it instead.
A kernel you create yourself needs a loader from
`c15t/modules/script-loader`. Attach one loader per kernel. See
[JavaScript scripts](/docs/frameworks/javascript/scripts).

## Options

|Option|Default|Behavior|
|--|--|--|
|`advertiserId`|Required|Public advertiser ID from the v2 snippet. Trimmed and URL-encoded into the loader path. If it's missing or blank, c15t logs an error and never loads AdRoll.|
|`pixelId`|Required|Public pixel ID from the same snippet. Trimmed. If it's missing or blank, c15t logs an error and never loads AdRoll.|
|`scriptUrl`|`https://s.adroll.com/j/<advertiserId>/roundtrip.js`|Override for the account-specific v2 loader. A blank value uses the default.|

## Loading and revocation

When `marketing` is allowed, the helper sets `adroll_adv_id`, `adroll_pix_id`,
`adroll_version` and `__adroll_loaded`. It creates the `window.adroll` array
queue with `setProperties`, `identify` and `track` stubs. Each stub pushes the
method name and its arguments object, which is the format AdRoll replays. The
helper calls `track('pageView')` once, then adds the advertiser's v2 loader as
an async script. The generic `https://s.adroll.com/j/roundtrip.js` is a
different, legacy v1 loader.

If your page already defines `window.adroll` or any of those methods, the
helper keeps them and sends the `pageView` through them. On server-rendered
pages, the helper doesn't start from the server HTML. It always starts in the
browser script loader, also when the visitor's consent was saved earlier.

The helper doesn't send email addresses or other identity data. Send further
events and identity data through AdRoll's JavaScript API, and only while
marketing and any vendor consent stay granted.

AdRoll documents no public stop or teardown API, and the helper sends no
withdrawal command. On withdrawal, it keeps the loader element on the page.
Keep c15t's default `reloadOnConsentRevoked` enabled. With reload disabled,
loaded code, partner pixels and timers can keep running until the visitor
navigates. If the visitor grants consent again on the same page, the helper
reuses the loader and doesn't send a second `pageView`.

## Cookies and storage

NextRoll's privacy notice names the `__adroll`, `__ar_v4`, `__adroll_shared`
and `__adroll_fpc` tracking cookies. The served code also writes consent
cookies, local storage such as `__adroll_consent_data`, session storage such as
`adroll_tpc` and `adroll_flgs`, and an `adroll` IndexedDB database. Account and
partner settings change this list. AdRoll can set storage as soon as the loader
runs, which is why the whole loader waits for consent.

## Verify AdRoll

In a fresh browser profile, deny consent and allow only an unrelated category.
Filter Network by `adroll.com` and confirm that no requests, globals, cookies,
local storage, session storage or IndexedDB appear. Grant `marketing` and check
the loader URL against your account snippet. Withdraw consent and confirm the
page reloads. AdRoll must stay blocked on the new page. Check storage in
DevTools as well as Network.

The c15t monitor runs public house-account IDs with collection blocked, because
AdRoll's sample IDs return access-denied responses. It also blocks the JSONP
consent check. It confirms that the SDK starts and stays behind consent. It
doesn't confirm your account's configuration, conversion delivery or partner
behavior.

Sources: [installation article](https://help.adroll.com/hc/en-us/articles/360040116252),
[existing consent banners](https://help.adroll.com/hc/en-us/articles/360003797191-Custom-Existing-Cookie-Consent-Banners),
[JavaScript API](https://apidocs.nextroll.com/guides/pixel-javascript-api.html)
and [NextRoll privacy notice](https://www.nextroll.com/privacy).

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

1. Load the page. No request goes to the vendor before you choose.
2. Click Reject, then reload. There is still no vendor request.
3. Open Privacy settings and allow the helper's category. The vendor script
   loads without a page reload.
4. 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](/docs/integrations/building-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](/docs/integrations/overview#vendor-switches-and-cookie-cleanup).

The helper lists its vendor by name in the preference dialog, so a visitor can
turn it off inside an allowed category. See
[vendor consent for your framework](/docs/integrations/overview#vendor-switches-and-cookie-cleanup). The
[consent verification guide](/docs/guides/verify-consent) covers navigation,
expiry and hosting checks.