# Wisepops

The c15t wisepops helper loads Wisepops only after visitors allow marketing in Inth. It gives Wisepops cookie consent after the loader finishes and reloads the page on withdrawal.

## Key facts

- **Tool:** Wisepops
- **Category:** Other
- **Consent categories:** Marketing, Experience
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/wisepops)
- [Wisepops](https://wisepops.com/)

Show Wisepops campaigns only after visitors allow marketing, and give cookie consent to Wisepops after the loader finishes.

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 Wisepops site ID. It is the h value of the loader URL under Settings > Install Wisepops.

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 Wisepops

Before marketing has permission, the c15t wisepops helper creates no Wisepops queue and writes no Wisepops storage.

After permission, the helper queues defaultConsent: 'denied' and loads the v3 loader. When it finishes and consent still holds, the helper calls wisepops('consent', 'granted').

Wisepops has no call to take back consent. So on withdrawal, c15t removes the loader and reloads the page. The new page does not load Wisepops.

Set category: 'experience' when the purpose of your campaigns and your policy fit experience better.

[Read the Wisepops Cookie Consent Mode](https://support.wisepops.com/en/articles/12679556-cookie-consent-mode)

## Installation

Wisepops has one load mode in c15t. The helper waits for marketing permission.

### Wait for permission

No request goes to Wisepops until the visitor accepts marketing. On withdrawal, c15t reloads the page.

```ts
wisepops({ siteId })
```

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

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

#### Add your site ID

Register one array. The experience option also sets browserStorage: true, which keeps visitor data in localStorage in place of cookies.

```
import { wisepops } from '@c15t/integrations/wisepops';

export const scripts = [wisepops({ siteId: 'YOUR_WISEPOPS_SITE_ID' })];

export const experienceScripts = [
  wisepops({
    category: 'experience',
    options: { browserStorage: true },
    siteId: 'YOUR_WISEPOPS_SITE_ID',
  }),
];
```

An empty site ID logs an error, and the loader does not run. Reload the page when you change site IDs.

### 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="marketing">
  // 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,
});
```

Remove every other Wisepops install, such as a tag manager or CMS plugin, so Wisepops loads only through c15t. Wisepops links to Shopify Customer Privacy by itself, and c15t does not sync with it.

## Verify your setup

Use a private window with an opt-in policy. Open DevTools Network, turn off the cache and filter by wisepops. Then test the three states.

- **Before a choice**: No request goes to Wisepops. There is no window.wisepops queue and no new Wisepops cookie or storage entry. Allow only measurement and check again.

- **After you allow marketing**: loader.js?v=3&h=... loads without a page reload. Your campaigns can now show.

- **After you withdraw marketing**: Save your choice. c15t reloads the page. The new page sends no request to Wisepops and has no queue.

With autoPageview: false, call window.wisepops?.('pageview') after each route change. Check permission first, because the queue can stay after withdrawal.

[Open the full Wisepops guide](https://c15t.com/docs/integrations/wisepops)

## Related guides

- [Adobe Target](/integrations/adobe-target)

- [Appcues](/integrations/appcues)

- [Dynamic Yield](/integrations/dynamic-yield)