Ads and growth

Attentive

Attentive shows SMS and email signup units and tracks on-site events for its marketing messages. The c15t attentiveTag helper waits for marketing consent before it downloads the Attentive tag. Until then, the page makes no request to Attentive.

Attentive has no supported way to stop a running tag. When the visitor withdraws, c15t reloads the page, and the next page doesn't load the tag.

Configure Attentive

Find the site slug in your Attentive tag URL, https://cdn.attn.tv/<siteSlug>/dtag.js. If you don't have it, ask your Attentive contact for the slug or the full tag URL. Then remove the original tag from your site, so that c15t controls when it loads.

npm install @c15t/integrations

src/consent-scripts.ts

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

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

Register the scripts

Complete your framework quickstart first. Keep its Inth endpoint, policy, styles and consent UI. Remove the vendor's original script, SDK initializer or tag-manager entry, so the vendor loads only through c15t.

The vendor pages put the helper in src/consent-scripts.ts. If your framework quickstart already has a scripts array, such as the one in c15t.config.ts in the Next.js guide, add the helper to that array instead of creating a second file. The scripts export is a configuration, not an initializer. Add it to the c15t provider you already have, at the registration point for your framework below. These are edits to that provider, not a second provider.

Add the configuration to scripts in c15t.config.ts, next to next.config.ts:

import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });

Keep the rest of your config, such as mode and routePrefix, in the same call. ConsentRoot reads the config in the browser, so the layout keeps passing only state. App Router, Pages Router and static export all read the same file. See Next.js scripts and embeds.

Options

Option	Default	Behavior
`siteSlug`	Required	Site slug from the tag URL. Whitespace is trimmed. It can contain only ASCII letters, digits, `_` and `-`. A URL, a path, or a missing or blank value logs an error and never loads the tag, even when you set `scriptUrl`.
`category`	`marketing`	Consent condition for the whole loader.
`scriptUrl`	`https://cdn.attn.tv/<siteSlug>/dtag.js`	Exact tag URL from Attentive or your proxy. Blank values use the default.

Loading and revocation

After consent, the helper adds dtag.js at the end of the body. It creates no queue or globals of its own. Attentive can then download more bundles, create an iframe, show signup units and track events.

On withdrawal, the tag element stays on the page. If the visitor allows marketing again on the same page, the helper reuses that tag instead of adding a second one.

Keep reloadOnConsentRevoked enabled. Attentive has no documented client API that reliably stops all tag behavior. Removing the tag can't unload code that already ran, cancel pending requests or remove every iframe. The helper doesn't use Attentive's undocumented enable and disable methods. The next page doesn't load the tag while marketing is denied.

Cookies and storage

Attentive can set _attn_, __attentive_id, __attentive_dv, __attentive_ss_referrer, __attentive_pv, __attentive_cco, attntv_mstore_email, attntv_mstore_phone, __attentive_ceid, __attentive_domain and __attentive_client_user_id. Some identifiers, such as __attentive_id, last up to 390 days. The reload doesn't delete them. Check cookies and both browser storage areas for your tag configuration.

Verify Attentive

Filter the Network panel by attn.tv. Before consent, and after you allow an unrelated category, check that there is no dtag.js request, no Attentive global or iframe, and no Attentive cookies or browser storage. Allow marketing and inspect the tag and the bundles it loads. Withdraw marketing and confirm that the reloaded page doesn't load them. Test signup units and message delivery only with your own Attentive account.

Sources: Attentive's tag setup and cookie list.

Test in a private window with an opt-in policy. Open DevTools Network, disable the cache and filter by the vendor's domain:

Load the page. No request goes to the vendor before you choose.
Click Reject, then reload. There is still no vendor request.
Open Privacy settings and allow the helper's category. The vendor script loads without a page reload.
Turn the category off again and save. c15t reloads the page, and the new page makes no vendor request.

c15t reloads on revocation because removing a script element does not stop code that already ran. The vendor's listeners, timers and queued events stay alive until the page unloads. If you set reloadOnConsentRevoked: false, stop the vendor yourself. Register a callback-only script whose onConsentChange calls the vendor's opt-out API, as shown in custom integrations, and check the permission before each of your own event calls. The reload does not delete cookies the vendor already set; see clear on revocation for your framework.

The helper lists its vendor by name in the preference dialog, so a visitor can turn it off inside an allowed category. See vendor consent for your framework. The consent verification guide covers navigation, expiry and hosting checks.