# Attentive

The c15t attentiveTag helper loads the Attentive tag only after visitors allow marketing in Inth. Attentive has no stop API, so c15t reloads the page on withdrawal.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/attentive)
- [Attentive](https://www.attentive.com/)

Show Attentive SMS and email signup units only to visitors who allow marketing. Until then, the page makes no request to Attentive.

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 site slug from your Attentive tag URL.

The tag URL looks like https://cdn.attn.tv/\<siteSlug>/dtag.js. Copy the part between cdn.attn.tv and dtag.js.

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

## How consent works with Attentive

Before marketing has permission, the c15t attentiveTag helper downloads nothing from Attentive.

After permission, the helper adds dtag.js at the end of the body. It creates no queue or globals of its own. Attentive then loads its bundles, signup units and events.

Attentive has no documented way to stop the tag once it starts. So on withdrawal, c15t reloads the page. The next page does not load the tag.

If the visitor allows marketing again on the same page, the helper reuses the tag. It does not add a second one.

## Installation

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

### Wait for permission

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

```ts
attentiveTag({ siteSlug })
```

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

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

#### Add your site slug

The helper builds the tag URL from your site slug.

```
import { attentiveTag } from '@c15t/integrations/attentive';

export const scripts = [attentiveTag({ siteSlug: 'YOUR_SITE' })];
```

The helper does not call the undocumented Attentive methods that turn the tag on or off.

### 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 the original Attentive tag from your site, so c15t controls when it loads.

## Verify your setup

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

- **Before a choice**: Allow only another category. No dtag.js request, Attentive global, iframe, cookie or storage appears.

- **After you allow marketing**: The tag loads, and you can inspect the bundles that it loads.

- **After you withdraw marketing**: c15t reloads the page, and the new page does not load the tag.

Some Attentive identifiers, such as \_\_attentive\_id, last up to 390 days. The reload does not delete them. Test signup units only with your own account.

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

## Related guides

- [Customer.io](/integrations/customer-io)

- [HubSpot](/integrations/hubspot)

- [Insider](/integrations/insider)