Analytics

Cloudflare Web Analytics

Configure Cloudflare Web Analytics

Copy the beacon token from the Web Analytics installation snippet. If Cloudflare adds the beacon to this site automatically, turn that off so the page has one beacon and c15t controls it.

npm install @c15t/integrations@alpha

src/consent-scripts.ts

import { cloudflareWebAnalytics } from '@c15t/integrations/cloudflare-web-analytics';

export const scripts = [cloudflareWebAnalytics({ token: 'YOUR_BEACON_TOKEN' })];

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
`token`	Required	Beacon token, written into the `data-cf-beacon` attribute. The helper trims it. Empty values log an error and the script does not load.
`spa`	`true`	Written into `data-cf-beacon`. Turns on Cloudflare's route tracking for single-page apps. Set `false` for a site with only full page loads.
`scriptUrl`	`https://static.cloudflareinsights.com/beacon.min.js`	Loader URL override.

Loading and revocation

cloudflareWebAnalytics uses the measurement category. Cloudflare Web Analytics sets no cookies, but the helper still waits for measurement permission. It loads beacon.min.js with defer. On revocation the helper removes the script element and calls no Cloudflare API.

Verify Cloudflare Web Analytics

Filter DevTools Network by cloudflareinsights.com. After you allow measurement, beacon.min.js loads and its script element carries data-cf-beacon with your token and "spa":true. Change route in your app and check that the beacon reports the new page.

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.