Analytics

Vercel Analytics

Configure Vercel Analytics

Enable Web Analytics for the project in Vercel. Remove the Analytics component or inject() call from @vercel/analytics so c15t loads the script once.

npm install @c15t/integrations@alpha

src/consent-scripts.ts

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

export const scripts = [vercelAnalytics()];

Register the scripts

Complete your framework quickstart 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.

Add the configuration to scripts in c15t.config.ts, next to next.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.

Options

Option	Default	Behavior
`dsn`	None	Project DSN for deployments outside Vercel, set as `data-dsn`.
`disableAutoTrack`	None	`true` sets `data-disable-auto-track="1"` and stops automatic page views.
`mode`	None	`'development'` loads the debug script. `'auto'` and `'production'` load the production script. The helper does not detect your environment.
`debug`	None	`true` loads `https://va.vercel-scripts.com/v1/script.debug.js`.
`endpoint`	None	Custom ingestion endpoint, set as `data-endpoint`.
`scriptUrl`	`https://va.vercel-scripts.com/v1/script.js`	Loader URL override. Takes precedence over `mode` and `debug`.

The helper also sets data-sdkn="c15t" on the script element.

Loading and revocation

vercelAnalytics uses the measurement category. When measurement becomes allowed, the helper defines the window.vaq queue and a window.va stub, unless they exist, then loads the script. Calls to window.va made before the script finishes loading wait in window.vaq.

On revocation the helper removes the script element and calls no Vercel API.

Verify Vercel Analytics

After you allow measurement, script.js loads from va.vercel-scripts.com with data-sdkn="c15t", and each client-side navigation sends one page view. With debug or mode: 'development' the helper loads script.debug.js instead, so a working debug build does not prove your production settings. After revocation window.va still exists, so if your code sends custom events through it, check measurement permission before each call.

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

Load the page. No request goes to the vendor before you choose.
Click Reject, then reload. There is still no vendor request.
Open Privacy settings and allow the helper's category. The vendor script loads without a page reload.
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, 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.

The helper sets vendor to its script ID, so once you declare that vendor a visitor can turn it off inside an allowed category. See vendor consent for your framework. The consent verification guide covers navigation, expiry and hosting checks.