# Vector

The c15t vector helper loads the Vector pixel only after visitors allow marketing in Inth. Vector has no stop API, so c15t reloads the page on withdrawal.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/vector)
- [Vector](https://www.vector.co/)

Learn which people and companies visit your site only after they allow marketing. Vector stays off the page until then.

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 the pixel ID from Settings > Pixel in Vector.

The Vector consent example needs ad consent. So this helper uses the marketing category.

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

## How consent works with Vector

Before marketing has permission, the c15t vector helper creates no Vector global and loads no SDK.

After permission, the helper creates window.vector with a queue for load, identify and on. It queues load(pixelId), then adds the async SDK. It sends no identify calls of its own.

Vector has no documented stop API. So keep the default c15t reload on withdrawal. Without it, Vector code and partner calls can go on until the next page.

The reload does not clear Vector storage. The helper does not call the undocumented block or removeVisitor methods.

## Installation

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

### Wait for permission

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

```ts
vector({ pixelId })
```

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

## Setup steps

#### Install the integration package

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

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

#### Add your pixel ID

Copy the ID from the install snippet where it calls vector.load. The helper keeps SDK methods that are on the page now.

```
import { vector } from '@c15t/integrations/vector';

export const scripts = [vector({ pixelId: 'YOUR_PIXEL_ID' })];
```

Form capture and company lookup by IP depend on your account settings. The IP hooks of Vector cover only that lookup.

### 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,
});
```

Remove the direct snippet and each tag manager copy, so they cannot load Vector without consent.

## Verify your setup

Use your own pixel ID on a domain that your Vector account allows. Open a fresh browser profile with an opt-in policy.

- **Before a choice**: Deny optional categories, then allow only measurement. No Vector global, SDK request or storage appears.

- **After you allow marketing**: pixel.js loads once.

- **After you withdraw marketing**: c15t reloads the page, and Vector stays blocked on the new page. Check Network, cookies and storage.

The Vector CSP guide lists cdn.vector.co, api.vector.co and a.usbrowserspeed.com. The SDK can also contact idx.liadm.com, so check the requests of your account first.

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

## Related guides

- [X Pixel](/integrations/x-pixel)

- [AdRoll](/integrations/adroll)

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