# Google Analytics

Load Google Analytics through the c15t gtag helper and keep it under the consent that your visitors give in Inth. The helper sends the Consent Mode v2 default before config and an update after each choice.

## Key facts

- **Tool:** Google Analytics
- **Category:** Analytics
- **Consent categories:** Measurement
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/google-tag)
- [Google Analytics](https://marketingplatform.google.com/about/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](/dashboard/sign-up)

## 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](https://c15t.com/docs/frameworks)

## How 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 v2](/blog/developer-guide-to-consent-mode-v2)

## Installation

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

### Wait for permission

Google gets no request until the visitor accepts measurement. Google cannot model visitors who refuse.

```ts
loadMode: 'after-consent'
```

### Load and signal

Google loads before a choice and gets consent signals. Denied visitors send cookieless pings.

```ts
loadMode: 'always'
```

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.

```
pnpm add @c15t/integrations
```

#### Configure your Google tag

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

```
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.

### Register it with your existing setup

#### Next.js

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.

```
import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });
```

#### TanStack Start

Pass scripts to the ConsentRoot in your root route. Import helpers in the route module, not in a server function: script configurations carry callbacks.

```
import { scripts } from '../consent-scripts';

<ConsentRoot state={consent} scripts={scripts}>
```

#### React

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

```
import { scripts } from './consent-scripts';

<ConsentProvider options={{ mode, scripts }}>
```

#### Nuxt

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.

```
import { scripts } from '../src/consent-scripts';

export default defineAppConfig({
  c15t: { scripts },
});
```

#### Vue

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

```
import { c15tVue, manifest } from 'c15t/vue/vue-plugin';
import { scripts } from './consent-scripts';

app.use(c15tVue, {
  mode: manifest(),
  scripts,
});
```

#### Astro

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.

```
import type { C15tClientOptionsExtension } from 'c15t/astro';
import { scripts } from './consent-scripts';

export default { scripts } satisfies C15tClientOptionsExtension;
```

#### Svelte

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

```
<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>
```

#### SvelteKit

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.

```
<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>
```

#### HTML: 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.

```
<script type="text/plain" data-c15t-category="measurement">
  // The vendor's snippet, unchanged
</script>
```

#### JavaScript

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

```
import { init, manifest } from '@c15t/browser';
import { scripts } from './consent-scripts';

const consent = init({
  mode: manifest(),
  scripts,
});
```

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](https://c15t.com/docs/integrations/google-tag)

## Related guides

- [Google Tag Manager](https://c15t.com/docs/integrations/google-tag-manager)

- [PostHog](https://c15t.com/docs/integrations/posthog)

- [Meta Pixel](https://c15t.com/docs/integrations/meta-pixel)