# Hotjar

The c15t hotjar helper loads Hotjar only after visitors allow measurement in Inth. c15t sends Hotjar no consent signal. So a withdrawal reloads the page to end the recording.

## Key facts

- **Tool:** Hotjar
- **Category:** Session replay
- **Consent categories:** Measurement
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/hotjar)
- [Hotjar](https://contentsquare.com/hotjar/)

Keep Hotjar recordings off the page until visitors allow measurement. A withdrawal reloads the page, and the reload ends the recording.

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 Hotjar site ID. The site ID is the hjid value in the Hotjar tracking code.

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 works with Hotjar

Before measurement has permission, c15t defines no window.\_hjSettings or window.hj and loads nothing from Hotjar.

After permission, the c15t hotjar helper sets window.\_hjSettings and a window.hj stub that queues calls. Then it loads the Hotjar script. If your page already defines either global, the helper leaves it alone.

c15t sends Hotjar no consent signal, so it cannot tell a recording to stop. On withdrawal, the helper removes the script element, and c15t reloads the page by default.

If you set reloadOnConsentRevoked to false, Hotjar continues to record until the visitor leaves the page.

## Installation

Hotjar has one load mode in c15t. The helper waits for measurement permission.

### Wait for permission

No request goes to Hotjar until the visitor accepts measurement. On withdrawal, c15t reloads the page to end the recording.

```ts
hotjar({ siteId })
```

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

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

#### Add your site ID

The helper sets the site ID as window.\_hjSettings.hjid and uses it in the loader URL. The version option sets hjsv and defaults to 6.

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

export const scripts = [hotjar({ siteId: 1234567 })];
```

An empty site ID or 0 logs an error, and Hotjar 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,
});
```

Delete the Hotjar tracking code from your app. c15t does not control that snippet. If it stays, Hotjar loads and records after the visitor rejects analytics.

## Verify your setup

Use a private window with an opt-in policy. Open DevTools Network and filter by hotjar. Then test the three states.

- **Before a choice**: No request goes to static.hotjar.com. In the Console, window.hj returns undefined.

- **After you allow measurement**: hotjar-\<siteId>.js loads from static.hotjar.com. window.\_hjSettings.hjid holds your site ID. A different ID means that other code set \_hjSettings first. Remove that code.

- **After you withdraw measurement**: Save your choice. c15t reloads the page. The new page sends no request to Hotjar.

Hotjar decides what to mask, not c15t. Watch one recording of a real screen. Make sure that Hotjar hides the fields that you expect. window.hj stays defined after withdrawal, so check permission before your code calls hj().

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

## Related guides

- [LogRocket](/integrations/logrocket)

- [Lucky Orange](/integrations/lucky-orange)

- [Microsoft Clarity](/integrations/microsoft-clarity)