Analytics

Umami Analytics

Configure Umami Analytics

Copy the website ID from your Umami tracking code. The helper passes it to the script as data-website-id. For a self-hosted Umami instance, set scriptUrl to your instance's tracker script.

npm install @c15t/integrations@alpha

src/consent-scripts.ts

import { umamiAnalytics } from '@c15t/integrations/umami-analytics';

export const scripts = [umamiAnalytics({ websiteId: 'YOUR_WEBSITE_ID' })];

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
`websiteId`	Required	Set as `data-website-id`. Empty or whitespace-only values log an error and the script does not load.
`hostUrl`	None	Host that receives events, set as `data-host-url`.
`autoTrack`	None	`false` sets `data-auto-track="false"` and stops automatic tracking.
`domains`	None	Domains to track, set as `data-domains`. Pass a comma-separated string or an array; the helper joins an array with commas.
`tag`	None	Tag attached to events, set as `data-tag`.
`beforeSend`	None	Name of a global function, set as `data-before-send`. Function values are not supported.
`scriptUrl`	`https://cloud.umami.is/script.js`	Loader URL override.

Loading and revocation

umamiAnalytics uses the measurement category. The tracker loads only while measurement is allowed. On revocation the helper removes the script element and calls no Umami API. Umami sets no cookies, but c15t still waits for measurement permission before loading it.

A beforeSend hook can change events before Umami sends them. It is not a consent check. Define the named global before the tracker loads.

Verify Umami Analytics

After you allow measurement, the tracker script loads with your data-website-id, and a request to /api/send goes to Umami or to your hostUrl. If your code calls window.umami.track, 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.