Skip to content

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.

Start for free
pnpm add @c15t/integrations
Google AnalyticsWaiting for consent
Before a choice

Filter Network by google. No request goes to Google. In the Console, window.dataLayer returns undefined.

Turn the switch on, then off, to see what loads.

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 framework

Installation

The helper has two modes for when the tag loads. Pick the mode that your policy needs.

Installation

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

  1. Install the integration package

    Add the helpers next to c15t. An import alone does not start the tag.

    pnpm add @c15t/integrations
  2. Configure your Google tag

    Use your Google Analytics measurement ID. The mode that you select controls when the tag loads.

    src/consent-scripts.ts
    import { gtag } from '@c15t/integrations/google-tag';
    
    export const scripts = [
      gtag({
        id: 'G-XXXXXXXXXX',
        category: 'measurement',
        loadMode: 'after-consent',
      }),
    ];

    Replace G-XXXXXXXXXX with your measurement ID. An empty ID logs an error, and the tag does not load.

  3. 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
    import { defineConsentConfig } from 'c15t/next';
    import { scripts } from './src/consent-scripts';
    
    export default defineConsentConfig({ scripts });

    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
    import { scripts } from '../consent-scripts';
    
    <ConsentRoot state={consent} scripts={scripts}>

    Add scripts to the options of your ConsentProvider, next to mode. Keep the banner, dialog and preferences link inside the provider.

    src/consent.tsx
    import { scripts } from './consent-scripts';
    
    <ConsentProvider options={{ mode, scripts }}>

    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
    import { scripts } from '../src/consent-scripts';
    
    export default defineAppConfig({
      c15t: { scripts },
    });

    Pass scripts to the c15tVue plugin call you have now. The plugin starts one script loader when the app mounts.

    src/main.ts
    import { c15tVue, manifest } from 'c15t/vue/vue-plugin';
    import { scripts } from './consent-scripts';
    
    app.use(c15tVue, {
      mode: manifest(),
      scripts,
    });

    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
    import type { C15tClientOptionsExtension } from 'c15t/astro';
    import { scripts } from './consent-scripts';
    
    export default { scripts } satisfies C15tClientOptionsExtension;

    Pass scripts as a prop to the ConsentProvider you have now. The provider owns the loader and disposes it on unmount.

    src/App.svelte
    <script lang="ts">
      import { ConsentProvider, manifest } from 'c15t/svelte';
      import { scripts } from './consent-scripts';
    </script>
    
    <ConsentProvider mode={manifest()} {scripts}>
      <!-- Your app and consent UI -->
    </ConsentProvider>

    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
    <script lang="ts">
      import { ConsentRoot } from 'c15t/svelte';
      import { scripts } from '../consent-scripts';
    
      let { children, data } = $props();
    </script>
    
    <ConsentRoot state={data.consent} {scripts}>
      {@render children()}
    </ConsentRoot>

    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
    <script type="text/plain" data-c15t-category="measurement">
      // The vendor's snippet, unchanged
    </script>

    Pass scripts to init() from @c15t/browser, next to your mode. With createConsentRuntime, pass scripts to it instead.

    src/consent.ts
    import { init, manifest } from '@c15t/browser';
    import { scripts } from './consent-scripts';
    
    const consent = init({
      mode: manifest(),
      scripts,
    });
All frameworks

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