# Vercel Analytics

The c15t vercelAnalytics helper loads Vercel Web Analytics only after visitors allow measurement in Inth. It replaces the Analytics component and queues early calls to window.va.

## Key facts

- **Tool:** Vercel Analytics
- **Category:** Analytics
- **Consent categories:** Measurement
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/vercel-analytics)
- [Vercel Analytics](https://vercel.com/products/web-analytics)

Count page views with Vercel Web Analytics only after visitors allow measurement. Calls that your code makes before the script loads wait in a queue.

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 Web Analytics turned on for the project in Vercel.

New to c15t? Complete the quickstart for your framework first. Keep its Inth endpoint, policy, styles and consent UI.

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

## How consent works with Vercel Analytics

Until measurement has permission, c15t does not define window.va. The helper sends no consent signal to Vercel.

When measurement gets permission, the helper defines the window.vaq queue and a window.va stub. Then it loads the script. Calls to window.va wait in the queue until the script is ready.

The helper sets data-sdkn="c15t" on the script element. For a deployment outside Vercel, pass dsn.

## Installation

Vercel Web Analytics has one load mode in c15t. The helper waits for measurement permission.

### Wait for permission

No request goes to Vercel Web Analytics until the visitor accepts measurement. On withdrawal, c15t removes the script and reloads the page.

```ts
vercelAnalytics()
```

An opt-out policy or no policy gives optional categories permission before a choice. Then Vercel Web Analytics 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 the script.

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

#### Add the helper

The default needs no options on Vercel. Set mode or debug only when you need the debug script.

```
import { vercelAnalytics } from '@c15t/integrations/vercel-analytics';

export const scripts = [vercelAnalytics()];
```

The helper does not detect your environment. A debug build that works does not prove your production settings.

### 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="measurement">
  // 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 Analytics component or inject() call from @vercel/analytics, so the script loads one time only. If you already have a scripts array, add the helper to it.

## Verify your setup

Use a private window with an opt-in policy. Open DevTools Network and filter by vercel-scripts. Then test the three states.

- **Before a choice**: No request goes to va.vercel-scripts.com. In the Console, window.va returns undefined.

- **After you allow measurement**: script.js loads from va.vercel-scripts.com with data-sdkn="c15t". Each client side navigation sends one page view.

- **After you withdraw measurement**: Save your choice. c15t reloads the page. The new page sends no request to Vercel Web Analytics.

After withdrawal, window.va still exists. If your code sends custom events through it, check measurement permission before each call.

[Open the full Vercel Analytics guide](https://c15t.com/docs/integrations/vercel-analytics)

## Related guides

- [Adobe Analytics](/integrations/adobe-analytics)

- [Ahrefs Analytics](/integrations/ahrefs-analytics)

- [Databuddy](/integrations/databuddy)