ActiveCampaign

activeCampaignTracking waits for marketing consent before creating vendor globals or downloading ActiveCampaign.

Configure ActiveCampaign

Copy the account ID from your ActiveCampaign site tracking snippet and remove the original snippet. Enable site tracking and authorize your site in ActiveCampaign.

npm install @c15t/integrations

pnpm add @c15t/integrations

yarn add @c15t/integrations

bun add @c15t/integrations

import { activeCampaignTracking } from '@c15t/integrations/activecampaign';

export const scripts = [
	activeCampaignTracking({ accountId: 'YOUR_ACCOUNT_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

Missing or blank required values log an error and never load.

Loading and revocation

After consent, the helper creates the callable pgo queue, sets its alias and timestamp, configures the account, and sets setTrackByDefault(false). After the SDK loads it calls process('allowTracking'), which sends the page request itself. The helper sends no duplicate process call at initial load. Once tracking starts, a settled denial reported by an active registration requires a page reload. The helper sends no further tracking or email commands on that page, even after a regrant.

Recreating the helper with the same options or a different email keeps the same SDK tag. After sign-in, register the helper with the contact's email. An email update changes future vendor requests and sends no additional page request. Omitting email, or passing a blank string, clears the runtime's email field after consent. This does not clear tracking cookies, reset the visitor ID, or erase identity already copied into vendor services.

If another script replaces the captured pgo dispatcher, the helper sends no further commands and requires a page reload.

Without a browser document, the script loader does not start ActiveCampaign. Replacing the helper or disposing its loader also requires no browser cleanup.

Use one account, loader URL and contact email across registrations on the page. Every active registration must have its mapped consent before the helper enables tracking. Conflicting registrations withhold further helper commands. Resolving a conflict or remounting a registration does not send another page request on an already activated runtime. Changing accountId or scriptUrl after loading starts requires a new page; the helper logs the conflict and keeps the original SDK. A category change updates c15t eligibility, not vendor configuration. Consent and option updates settle after the current JavaScript turn.

Keep reloadOnConsentRevoked enabled. The fetched runtime has no documented stop command. setTrackByDefault(false) does not stop services already started by allowTracking. Removing its script or registration cannot stop running code, clear stored identifiers or cancel requests. If a running helper changes to a denied category, reload the page as part of that configuration change. The helper logs that a reload is required; reloadOnConsentRevoked observes consent changes, not helper replacements. The permitted tag stays in the DOM across withdrawal and registration disposal to avoid installing a second runtime on remount. A pending download completed without consent or an active registration receives no allowTracking until a consenting registration exists and all active registrations agree on the configuration and have consent. An interrupted mount, failed download or externally detached SDK requires a page reload. The next denied page does not load the tag.

ActiveCampaign uses first-party tracking cookies. Cookie names and other storage can vary with the vendor runtime and account configuration. Inspect your own deployment after grant.

The default loads ActiveCampaign's Diffuser SDK directly from its vendor CDN. During verification, the prism.js URL from ActiveCampaign's tracking snippet redirected to diffuser.js,? and returned 403. The clean CDN URL returned JavaScript, accepted the same pgo queue, and initialized the tracker. The default bypasses that malformed redirect. Use scriptUrl for another region or a proxy and verify that it serves the matching ActiveCampaign runtime.

Verify ActiveCampaign

Check for no diffuser.js, pgo, prismGlobalObjectAlias, cookies or browser storage before consent and after unrelated consent. Grant marketing and confirm the vendor runtime replaces the queue. Verify the page request with your own configured account. Revoke and check that the next denied page does not load the tracker.

Sources: tracking snippet, GDPR flow, and site tracking setup.

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.