Analytics

Adobe Analytics

Configure Adobe Analytics

Copy the full embed URL for your property environment from the Adobe Data Collection embed code. Adobe has no shared loader that takes only an account ID, so adobeAnalytics needs the whole URL. Remove the original embed code.

npm install @c15t/integrations@alpha

src/consent-scripts.ts

import { adobeAnalytics } from '@c15t/integrations/adobe-analytics';

export const scripts = [
	adobeAnalytics({
		scriptUrl:
			'https://assets.adobedtm.com/YOUR_ORG/YOUR_PROPERTY/launch-production.min.js',
	}),
];

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
`scriptUrl`	Required	Full `https:` embed URL of the Tags property environment. Self-hosted embeds work. The helper trims the value. Empty, unparseable and non-`https:` URLs log an error and the script does not load.
`async`	`true`	Loads the Tags library asynchronously. Set `false` only for a legacy synchronous deployment.
`seedAdobeDataLayer`	`true`	Sets `window.adobeDataLayer` to an empty array before the library loads, only when the global is undefined.

Loading and revocation

adobeAnalytics uses the measurement category. The property embed loads only while measurement is allowed. On revocation the helper removes the script element and calls no Adobe API.

The property can load Adobe Analytics, Web SDK and other extensions through its rules. c15t sees only the embed script, so every extension runs under the one measurement permission. If a rule loads a service with another purpose, such as advertising, configure that rule in Adobe to respect your consent model too.

Verify Adobe Analytics

After you allow measurement, the request for your embed URL appears, then the requests from the extensions the property enables. window._satellite exists once the Tags library runs. Check that each extension's requests match the measurement purpose.

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 sets vendor to its script ID, so once you declare that vendor 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.