# Zendesk Messaging

The c15t zendeskWidget helper loads Zendesk Messaging only after visitors allow functionality in Inth and sets its cookie range from measurement.

## Key facts

- **Tool:** Zendesk Messaging
- **Category:** Support and chat
- **Consent categories:** Functionality, Measurement
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/zendesk)
- [Zendesk Messaging](https://www.zendesk.com/)

Offer Zendesk support chat to visitors who allow functionality, with analytics storage only when they allow measurement too.

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 and c15t in that app. You also need the widget key from Admin Center > Channels > Messaging and social > Messaging > Installation.

This helper covers Zendesk Messaging. Web Widget Classic uses a different API.

[Open the quickstart for your framework](https://c15t.com/docs/frameworks)

## How consent works with Zendesk Messaging

When functionality becomes allowed, the c15t zendeskWidget helper creates the zE command queue and loads the Zendesk snippet.

Before the loader runs, and on each consent change, it sets the Zendesk cookie range. Measurement on gives all, and measurement off gives functional.

On withdrawal, the helper sends none. Zendesk hides the widget and deletes its local and session storage.

The none call does not unload the SDK. So keep reloadOnConsentRevoked on, and c15t reloads the page.

## Installation

Zendesk Messaging has one load mode in c15t. The helper waits for functionality permission.

### Wait for permission

No request goes to Zendesk until the visitor accepts functionality. On withdrawal, Zendesk hides the widget and c15t reloads the page.

```ts
zendeskWidget({ key })
```

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

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

#### Add your widget key

The helper trims and encodes the key. A blank key logs an error, and the widget does not load.

```
import { zendeskWidget } from '@c15t/integrations/zendesk';

export const scripts = [zendeskWidget({ key: 'YOUR_ZENDESK_WIDGET_KEY' })];
```

Use one widget key per page. Zendesk exposes a single global zE API, so two widgets on the same page control each other.

### 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="functionality">
  // 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 Zendesk snippet from your page or tag manager, so it cannot load without consent.

## Verify your setup

Filter DevTools Network by zdassets.com and your Zendesk subdomain. Then test the three states.

- **Before a choice**: No Zendesk loader request appears, and c15t defines no window.zE.

- **After you allow functionality**: The widget loads. Without measurement, its analytics storage stays off.

- **After you withdraw functionality**: Zendesk hides the widget. After c15t reloads, the loader stays absent.

A good snippet.js response alone does not prove that your widget key works. Open a conversation in your widget to check it.

[Open the full Zendesk Messaging guide](https://c15t.com/docs/integrations/zendesk)

## Related guides

- [Ada](/integrations/ada)

- [Crisp](/integrations/crisp)

- [Front Chat](/integrations/front-chat)