# AdRoll

The c15t adrollPixel helper loads AdRoll only after visitors allow marketing in Inth. It queues the first pageView, and c15t reloads the page on withdrawal.

## Key facts

- **Tool:** AdRoll
- **Category:** Advertising
- **Consent categories:** Marketing
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/adroll)
- [AdRoll](https://www.adroll.com/)

Keep AdRoll ad audiences and conversion measurement off the page until visitors allow marketing. Then the first page view goes out with the loader.

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

[Start for free](/dashboard/sign-up)

## Before you start

You need an Inth project that connects to your app, c15t in that app and your AdRoll advertiser ID and pixel ID. Find both under Analytics > Insights > Website > View Pixel.

Under Settings > Data Collection > Visitor Consent, choose Use your existing Consent Banner. Then AdRoll shows no banner of its own.

[Open the quickstart for your framework](https://c15t.com/docs/frameworks)

## How consent works with AdRoll

Before marketing has permission, the c15t adrollPixel helper sets no AdRoll globals and adds no loader.

After permission, the helper sets the AdRoll globals and the window.adroll queue. It queues one pageView and adds the v2 loader of the advertiser.

AdRoll has no API to stop its pixel. So on withdrawal, the helper leaves AdRoll on the page, and the default reload of c15t removes it.

The helper sends no email addresses or other identity data. Send those through the AdRoll JavaScript API, and only while marketing has permission.

## Installation

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

### Wait for permission

No request goes to AdRoll until the visitor accepts marketing. On withdrawal, c15t reloads the page.

```ts
adrollPixel({ advertiserId, pixelId })
```

An opt-out policy or no policy gives optional categories permission before a choice. AdRoll asks for affirmative consent before the pixel loads, so use an opt-in policy.

## Setup steps

#### Install the integration package

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

```
pnpm add @c15t/integrations
```

#### Add your AdRoll IDs

Pass the advertiser ID and the pixel ID. The helper builds the loader URL from them.

```
import { adrollPixel } from '@c15t/integrations/adroll';

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

If your page already defines window.adroll, the helper keeps it and sends the pageView through it.

### Register it with your existing setup

#### Next.js

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.

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

export default defineConsentConfig({ scripts });
```

#### TanStack Start

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

```
import { scripts } from '../consent-scripts';

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

#### React

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

```
import { scripts } from './consent-scripts';

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

#### Nuxt

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.

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

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

#### Vue

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

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

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

#### Astro

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.

```
import type { C15tClientOptionsExtension } from 'c15t/astro';
import { scripts } from './consent-scripts';

export default { scripts } satisfies C15tClientOptionsExtension;
```

#### Svelte

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

```
<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>
```

#### SvelteKit

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.

```
<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>
```

#### HTML: 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.

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

#### JavaScript

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

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

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

Delete the direct pixel snippet and each tag manager copy, so they cannot load AdRoll without consent.

## Verify your setup

Use a fresh browser profile with an opt-in policy. Open DevTools Network and filter by adroll.com. Then test the three states.

- **Before a choice**: No request goes to AdRoll. Allow only another category and check again. No AdRoll globals, cookies, local storage, session storage or IndexedDB appear.

- **After you allow marketing**: The loader loads, and its URL matches the snippet of your account.

- **After you withdraw marketing**: Save your choice. c15t reloads the page, and AdRoll stays blocked on the new page.

AdRoll can write storage as soon as the loader runs. That is why the whole loader waits for consent. Check storage in DevTools as well as Network.

[Open the full AdRoll guide](https://c15t.com/docs/integrations/adroll)

## Related guides

- [Amazon Ads](/integrations/amazon-ads)

- [LinkedIn Insight Tag](/integrations/linkedin-insights)

- [LiveIntent](/integrations/liveintent)