Skip to content
Start for free

PostHog

Run PostHog product analytics under measurement consent. Load it on each page opted out, or wait for consent, and turn off the modules that you do not use.

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
PostHogWaiting for consent
Before a choice

array.js does not load, and no capture request goes to your API host.

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 the project token that starts with phc_. You also need the region of your PostHog project.

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

How consent gets to PostHog

By default, the c15t posthog helper loads array.js on each page. It calls opt_out_capturing() while measurement has no permission and opt_in_capturing() while it has permission.

The default cookieless_mode: 'on_reject' lets PostHog capture without cookies after a refusal. That needs cookieless server hashing in your PostHog project. Set cookieless_mode: 'never' if a refusal must stop capture.

Use the features switches to skip surveys, heatmaps, dead clicks, Web Vitals or feature flag requests.

If your app already starts posthog-js, keep it. Register a callback-only script that calls opt_in_capturing and opt_out_capturing instead of the helper.

Read PostHog's cookieless guide

Installation

The helper has two modes for when PostHog loads. This guide waits for permission and turns cookieless capture off.

Installation

An opt-out policy or no policy gives optional categories permission before a choice. Then PostHog captures 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 PostHog.

    pnpm add @c15t/integrations

  2. Add your project token and region

    The helper picks the API, UI and loader hosts from region. Set apiHost to send data through a proxy.

    src/consent-scripts.ts
    import { posthog } from '@c15t/integrations/posthog';

export const scripts = [
  posthog({
    id: 'phc_YOUR_PROJECT_TOKEN',
    region: 'eu',
    loadMode: 'after-consent',
    initOptions: { cookieless_mode: 'never' },
  }),
];

    An empty token logs an error, and the script 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

The helper starts PostHog itself. Remove each posthog-js initializer, framework plugin or array snippet that also does.

Verify your setup

These checks use the after-consent mode and an opt-in policy. Open a private window and DevTools Network, and filter by posthog. Then test the three states.

  • Before a choice

    array.js does not load, and no capture request goes to your API host.

  • After you allow measurement

    array.js loads, and capture requests to your API host follow. Send one guarded event and make sure that it goes out.

  • After you withdraw measurement

    Save your choice. c15t reloads the page. The new page sends no capture request.

The posthog global exists before the SDK loads. Check measurement permission before each capture call in your code, for example with useConsent('measurement') in React.

Open the full PostHog guide