# LogRocket

The c15t logRocket helper loads LogRocket only after visitors allow measurement in Inth. LogRocket has no stop call for the web SDK. So a withdrawal reloads the page to stop the recording.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/logrocket)
- [LogRocket](https://logrocket.com/)

Keep LogRocket session replay off the page until visitors allow measurement. LogRocket.init runs only after the loader arrives.

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 the app ID from LogRocket Project Setup. It has the form org-slug/app-slug.

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 LogRocket

Before measurement has permission, LogRocket.min.js does not load.

After permission, the c15t logRocket helper loads LogRocket.min.js with crossorigin="anonymous". It calls LogRocket.init(appId, initOptions) after the script loads.

LogRocket documents no consent or stop call for the web SDK. On withdrawal, the helper removes the script element. It calls no LogRocket API. c15t reloads the page by default, and the reload stops the recording.

Set asyncScriptUrl only when you send LogRocket through a proxy on your domain.

## Installation

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

### Wait for permission

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

```ts
logRocket({ appId })
```

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

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

#### Add your app ID

The helper sends the app ID to LogRocket.init. Pass initOptions with JSON values only, so functions such as request sanitizers cannot pass through.

```
import { logRocket } from '@c15t/integrations/logrocket';

export const scripts = [logRocket({ appId: 'your-org/your-app' })];
```

An app ID that is not two segments with a / between them logs an error, and the script 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,
});
```

Remove the original LogRocket install. Before you deploy, set the LogRocket privacy and sanitization settings, so recordings leave out sensitive DOM, input and network data.

## Verify your setup

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

- **Before a choice**: No request goes to cdn.logrocket.io. In the Console, window.LogRocket returns undefined.

- **After you allow measurement**: LogRocket.min.js loads without a page reload, and window.LogRocket exists. With asyncScriptUrl, the logger bundle loads from your proxy URL.

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

Keep the reload on. Without it, recording continues until the page unloads.

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

## Related guides

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

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

- [Sentry](/integrations/sentry)