FullStory

fullStory waits for measurement consent before creating vendor globals or downloading FullStory.

Configure FullStory

Copy your organization ID from FullStory setup and remove the original snippet. For regional IDs such as o-ABC123-eu1, c15t selects the regional FullStory host and SDK download before loading. That ID uses eu1.fullstory.com and edge.eu1.fullstory.com/s/fs.js. Legacy IDs and the na1 region use the US defaults.

npm install @c15t/integrations

pnpm add @c15t/integrations

yarn add @c15t/integrations

bun add @c15t/integrations

import { fullStory } from '@c15t/integrations/fullstory';

export const scripts = [fullStory({ orgId: 'YOUR_ORG_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

The helper trims organization and endpoint values and treats blank overrides as missing. FullStory-owned host and script values receive the organization's region, replacing an existing region label when needed. Custom proxy or Relay hosts and script paths stay unchanged. The host and script resolve independently: a custom host alone does not change the default script. scriptUrl never changes the SDK's script environment value.

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

Loading and revocation

After consent, the helper creates FullStory's v2 callable queue with six-field command records. Async commands such as FS('getSessionAsync') return promises while the SDK loads and after its dispatcher is ready. It configures captureOnStartup: false and downloads the SDK. An uninterrupted first allowed load calls start. A load that completes while consent is denied, or after the last owner is removed, calls shutdown. After any helper-issued shutdown, regrant or remount calls restart, even if the helper never called start. Optional element consent follows the mapped permission through setIdentity.

Equivalent registrations share one download and recorder. Each registration must grant the mapped consent before capture can start or resume, including registrations that have never loaded. Removing a denying registration reapplies the remaining registrations' consent, including when they use different elementConsent settings. Initial denial creates no FullStory globals or requests. Removing the last registration shuts down capture. Mounting the same configuration again resumes the retained recorder with restart without downloading the SDK again.

Keep orgId, host, script and scriptUrl fixed for the page. c15t compares their effective values, so omitted regional defaults and explicit equivalent endpoints share the recorder. After bootstrap begins, c15t requires a page reload to change these effective settings and rejects incompatible configurations explicitly.

Removing an async script does not guarantee that its pending download cannot execute, so c15t retains the pending bootstrap too. Remounting the same configuration waits for that download instead of inserting another script. If a script update interrupts setup before insertion, the next mount inserts the SDK without initializing FullStory twice.

Without MutationObserver, c15t prevents a second download, but setup interrupted before insertion can require a reload. A nested synchronous mount can leave an outer registration on a source-less placeholder; it still shares the retained recorder and consent state.

FullStory documents init before capture starts; c15t does not support replacing an initialized recorder in place. scriptUrl chooses the downloaded file, while script configures the SDK's environment. An existing FS from another installer must be removed from the site's setup before using this helper.

Shutdown stops capture, but does not erase cookies or unload the SDK. Keep reloadOnConsentRevoked enabled when your policy also requires a fresh page without loaded vendor code. Capture state is reapplied on every page.

FullStory can set fs_uid and fs_cid cookies for one year, fs_lua for 30 minutes, and _fs_tab_id in sessionStorage. Inspect your account configuration for additional storage.

Verify FullStory

Check for no FullStory request, FS, FullStory configuration globals, cookies or browser storage before consent and after unrelated consent. Grant measurement and verify the real v2 dispatcher installed. With your own account, verify capture starts, shutdown stops it, and regrant restarts it once.

Sources: getting started, asynchronous methods, configuration, capture controls, element consent, and cookie consent.

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.