LiveIntent

LiveIntent's LiveConnect tag identifies visitors for people-based ad targeting and measurement. The c15t liveIntentTag helper waits until the marketing category is allowed before it creates the liQ queue and adds your account's tag.

LiveConnect has no API to stop it. When the visitor withdraws, the helper leaves the tag on the page, and c15t's default page reload removes it.

Configure LiveIntent

Copy the tag ID from your account's LiveConnect base tag. Use the filename without .min.js. Don't test with the public a-00xx tag from LiveIntent's examples. It's live production code, not a sandbox or a default for your account. Then delete the direct base tag and any tag manager copy, so they can't load LiveConnect without consent.

npm install @c15t/integrations

pnpm add @c15t/integrations

yarn add @c15t/integrations

bun add @c15t/integrations

import { liveIntentTag } from '@c15t/integrations/liveintent';

export const scripts = [liveIntentTag({ tagId: 'YOUR_TAG_ID' })];

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.

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

export default defineConsentConfig({ scripts });

Options

Loading and revocation

When marketing is allowed, the helper sets window.liQ to an empty array, pushes any events onto it in order, then adds one async loader. If your page already defines liQ, the helper keeps it and pushes the events onto it. Once it loads, LiveConnect replaces the array with its own client.

For later events, call window.liQ.push with a plain event object, and only while marketing and any vendor consent stay granted. A function queue or method-and-arguments tuples don't match LiveConnect's event format.

Where GDPR applies, LiveIntent documents further TCF requirements, along with GPP and legacy US privacy signals. c15t's marketing category doesn't replace a TC string. Zeta's guide names purposes 1 to 4, but the public example bundle served during testing required more purposes and special features. Confirm your account's production tag and requirements with LiveIntent. Don't request extra purposes just to satisfy the public example.

LiveIntent documents no stop or withdrawal command for the full runtime. On withdrawal, the helper keeps the loader element and sends no withdrawal event. Keep c15t's default reloadOnConsentRevoked enabled. With reload disabled, existing clients, listeners and sync frames can keep running until the visitor navigates. If the visitor grants consent again on the same page, the helper reuses the loader and doesn't push events a second time.

Cookies and storage

The served code writes the _lc2_fpi, _lc2_fpi_js, _li_dcdm_c, _li_ss and lidids.* cookies, and _li_duid and _li_ss in local storage. Some cookies request lifetimes up to 730 days, which browsers can shorten. Partner and account settings can add storage.

For CSP, the main hosts are b-code.liadm.com, idx.liadm.com, rp.liadm.com, rpr.liadm.com and i.liadm.com.

Verify LiveIntent

In a fresh browser profile, deny consent and allow only an unrelated category. Filter Network by liadm.com and confirm that no requests, globals, cookies, local storage or session storage appear. Grant marketing and check the loader URL against your account's base tag. Withdraw consent and confirm the page reloads. LiveIntent must stay blocked on the new page. Check storage in DevTools as well as Network.

Sources: base tag guide, Shopify tag example, event tags, privacy requirements and services privacy policy.

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

1. Load the page. No request goes to the vendor before you choose.
2. Click Reject, then reload. There is still no vendor request.
3. Open Privacy settings and allow the helper's category. The vendor script loads without a page reload.
4. 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.