# Gorgias Chat

The c15t gorgiasChat helper loads Gorgias Chat only after visitors allow functionality in Inth, and turns off its Segment analytics without measurement.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/gorgias)
- [Gorgias Chat](https://www.gorgias.com/)

Support shoppers with Gorgias Chat once they allow functionality. Its Segment analytics stays off unless 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 public app key from the v3 installation snippet in your Gorgias Chat settings.

A v2 snippet uses an applicationId. Pass that value as appKey with version: 2.

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

## How consent works with Gorgias Chat

Before functionality has permission, the c15t gorgiasChat helper adds no script, global, cookie or storage from Gorgias.

After consent, c15t adds the loader to the body. When the widget is ready, the helper calls disableSegment() if measurement is off.

Gorgias has no call to turn Segment on again. It stays off for that page, even if the visitor then allows measurement.

Gorgias has no shutdown API. On withdrawal, c15t removes the loader and reloads the page, and the reload stops the widget.

## Installation

Gorgias Chat has one load mode in c15t. The helper waits for functionality permission.

### Wait for permission

No request goes to Gorgias until the visitor accepts functionality. On withdrawal, c15t reloads the page.

```ts
gorgiasChat({ appKey })
```

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

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

#### Add your app key

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

```
import { gorgiasChat } from '@c15t/integrations/gorgias';

export const scripts = [gorgiasChat({ appKey: 'YOUR_GORGIAS_APP_KEY' })];
```

The key is the last part of the config.gorgias.chat/bundle-loader URL in your snippet.

### 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 other Gorgias snippets and automatic installs from your theme, tag manager or store app. The Gorgias loader skips duplicate installs.

## Verify your setup

Use your own app key in a private window with an opt-in policy. Filter DevTools Network by gorgias. Then test the three states.

- **Before a choice**: No Gorgias script or request appears.

- **After you allow functionality**: The loader requests your app key, and the widget appears. With measurement denied, check its Segment requests.

- **After you withdraw functionality**: The page reloads, and the new page makes no Gorgias request.

The reload does not remove cookies or storage that Gorgias created. A placeholder app key still returns HTTP 200, so check that the widget appears.

[Open the full Gorgias Chat guide](https://c15t.com/docs/integrations/gorgias)

## Related guides

- [Intercom](/integrations/intercom)

- [YouTube](/integrations/youtube)

- [Zendesk Messaging](/integrations/zendesk)