Nuxt module

Register the module

Add c15t/vue to modules in nuxt.config.ts and configure it under the c15t key:

export default defineNuxtConfig({
	compatibilityDate: '2026-07-04',
	modules: ['c15t/vue'],
});

c15t/vue is the Nuxt module. You do not install a separate Nuxt package or call app.use(). The quickstart covers the whole setup.

What the module registers

In the browser, the plugin starts the consent modules once the app has mounted. A page with ssr: false has no server HTML to hydrate, so there the plugin starts them before the mount, and the policy request runs while the app mounts. With manifest({ resolve: 'browser' }) the resolver starts loading as soon as the plugin runs, and the modules still start after the mount. Starting reads the stored choice, applies Global Privacy Control, and starts the script loader, clear-on-revocation, the network blocker, the iframe blocker and, with iab set and an IAB policy, the IAB module.

With hosted(), the module also writes a small inline script into the head of each ssr: false page. It calls your backend's /init while the browser parses the HTML, and the plugin uses that response instead of sending its own request.

nuxt.config.ts or app.config.ts

The module merges the c15t key of app/app.config.ts over its options in nuxt.config.ts. Arrays from both files are combined. The module types both keys, including when you register it as c15t/vue.

Module options reach the browser as JSON through runtimeConfig.public, which drops functions. app.config.ts is part of the browser bundle, so it keeps functions.

App config can change while the page runs, through updateAppConfig() or hot reload. The browser applies a change to scripts, networkBlocker, iframeBlocker, vendors, consentCategories, callbacks and reloadOnConsentRevoked. Storage, backend and experiment options are read once when the page loads. mode and routePrefix never change at runtime.

Change the backend URL at runtime

Nuxt applies NUXT_PUBLIC_* environment variables over runtimeConfig.public when the server starts. To point a built app at another backend without rebuilding it, set NUXT_PUBLIC_C15T_BACKEND_URL:

NUXT_PUBLIC_C15T_BACKEND_URL=https://your-project.inth.app \
  node .output/server/index.mjs

NUXT_PUBLIC_INTH_PROJECT_URL works the same way when the build read its URL from that variable or had none. It never replaces a backendURL from nuxt.config.ts or a NUXT_PUBLIC_C15T_BACKEND_URL.

The browser, server rendering and the consent route all use this value. Keep backendURL in nuxt.config.ts: a value in app.config.ts is bundled with the app and takes precedence over runtime config.

When the build bundles a manifest, the policy comes from the build. The consent route serves the bundled snapshot and never downloads one, so the variable only changes where consent saves and session reports go. To use another project's policy, set the URL when you build and build again, or use manifest({ source: 'runtime' }).

The consent route can reach the backend at an address the browser does not use, such as an internal hostname. Set NUXT_C15T_BACKEND_URL for that. Only the consent route reads it, and only when it downloads the manifest at runtime or falls back to the backend's /init.

nuxt generate writes the config into the static files, so a static site picks up a new URL only when you generate it again.

Options

Backend and rendering

Modes

manifest() also takes manifestURL, the URL the build and the server download the manifest from, by default ${backendURL}/manifest. Rendering and deployment explains which mode fits which deployment.

Consent and storage

Scripts, blocking and events

Appearance

Verify

Run nuxt dev and request /api/c15t/init in the default manifest() mode. It returns JSON with the resolved policy for your location. View the source of a page under a policy that asks for consent and find data-testid="consent-banner-root".