Google Analytics
Run Google Analytics under the consent that your visitors give. Choose when the Google tag loads. Then check each consent state before you ship.
Inth keeps the consent record of each choice, with the visitor’s country and the policy that applied.
pnpm add @c15t/integrationsFilter Network by google. No request goes to Google. In the Console, window.dataLayer returns undefined.
Before you start
You need an Inth project that connects to your app, c15t in that app and your Google Analytics measurement ID. The ID starts with G-.
New to c15t? Complete the quickstart for your framework first. Keep its Inth endpoint, policy, styles and consent UI.
Open the quickstart for your frameworkHow consent gets to Google
The c15t gtag helper loads gtag.js, the Google tag. Before the config command, it sends the Consent Mode v2 default. After each consent change, it sends an update.
Measurement controls analytics_storage. Marketing controls ad_storage, ad_user_data and ad_personalization.
c15t grants a type when its category has permission. Otherwise, c15t denies that type.
Use the consentMapping option to set your own map. It replaces the full table, so include each category that Google must still get.
Read the developer guide to Consent Mode v2Installation
The helper has two modes for when the tag loads. Pick the mode that your policy needs.
An opt-out policy or no policy gives optional categories permission before a choice. Then the tag 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 tag.
Configure your Google tag
Use your Google Analytics measurement ID. The mode that you select controls when the tag loads.
src/consent-scripts.ts Replace G-XXXXXXXXXX with your measurement ID. An empty ID logs an error, and the tag does not load.
Register it with your existing setup
Add scripts to the c15t configuration that you have now. Keep your Inth endpoint, mode, policy, styles and consent UI.
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.
c15t.config.ts Pass scripts to the ConsentRoot in your root route. Import helpers in the route module, not in a server function: script configurations carry callbacks.
src/routes/__root.tsx Add scripts to the options of your ConsentProvider, next to mode. Keep the banner, dialog and preferences link inside the provider.
src/consent.tsx 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.
app/app.config.ts Pass scripts to the c15tVue plugin call you have now. The plugin starts one script loader when the app mounts.
src/main.ts 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.
src/c15t.client.ts Pass scripts as a prop to the ConsentProvider you have now. The provider owns the loader and disposes it on unmount.
src/App.svelte 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.
src/routes/+layout.svelte 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.
index.html Pass scripts to init() from @c15t/browser, next to your mode. With createConsentRuntime, pass scripts to it instead.
src/consent.ts
Load the tag one time only. Remove the old Google snippet, any framework loader and any tag manager entry for the same ID. If you already have a scripts array, add the helper to it.
Verify your setup
These checks use the after-consent mode and an opt-in policy. Open a private window, DevTools Network and Google Tag Assistant. Then test the three states.
Before a choice
Filter Network by google. No request goes to Google. In the Console, window.dataLayer returns undefined.
After you allow measurement
The tag loads one time. In Tag Assistant, the first command is the consent default with the mapped types granted. It comes before config.
After you withdraw measurement
Save your choice. c15t reloads the page. The new page sends no request to Google.
With client side navigation, make sure that each route change sends one page view. A second router integration can count it two times. If you set reloadOnConsentRevoked to false, the tag stays on the page and gets an update that denies the types.
Open the full Google tag guide