fullstory-user-consent

Delay Fullstory session capture until user consent is granted.

11|2|Updated Dec 2, 2025

Search Tags:#compliance #mobile #privacy #web #consent #capture-control #fullstory

Ready to run

npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-user-consent-fullstorydev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fullstory-user-consent
Source: https://github.com/fullstorydev/fs-skills/tree/main/core/fullstory-user-consent
Command: npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-user-consent-fullstorydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fullstory User Consent APIs enable privacy-conscious teams to delay or selectively capture session data until users explicitly opt-in, helping meet regulatory requirements and organizational privacy goals.

Core Features & Use Cases

Holistic consent: Delay ALL capture at startup and start recording only after user consent.
Element-level consent: Allow capturing only elements marked with consent, while other data remains unrecorded.
Cross-platform guidance: Includes web (cookie banners and GDPR) and mobile (iOS/Android/Flutter/React Native) implementation guidance.
Consent state persistence: Store and restore consent decisions across launches and sessions.
Identity coordination: Identify users only after consent is granted.

Quick Start

Review the platform-specific guidance in SKILL-WEB.md and SKILL-MOBILE.md.
Configure capture to start only after consent (for web, set window['_fs_capture_on_startup'] = false; for mobile, adjust platform config to require consent).
Implement a consent UI and call FS('start') on grant and FS('shutdown') on revoke, ensuring consent status is persisted.

Frequently Asked Questions about fullstory-user-consent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I delay Fullstory session capture until user consent is granted?▼

You can delay Fullstory session capture by setting window['_fs_capture_on_startup'] = false on web or configuring your mobile platform to require consent, then triggering FS('start') only after explicit user opt-in.

What is element-level consent for session recording and how does it work?▼

Element-level consent restricts session recording to only capture elements specifically marked as consented, while all other user data and interactions remain unrecorded until broader permission is granted.

Does Fullstory consent management work across both web and mobile platforms?▼

Yes, Fullstory consent management applies across web and mobile apps, providing platform-specific guidance for iOS, Android, Flutter, and React Native to manage session capture consent consistently.

How do I persist user consent state across app launches and sessions?▼

You persist user consent state across app launches and sessions by storing the consent decision in persistent storage, ensuring that capture settings are automatically restored based on the user's previous choice.

Can I integrate a CMP or cookie banner with Fullstory capture control?▼

Yes, you can integrate a Consent Management Platform (CMP) or cookie banner with Fullstory capture control APIs to delay holistic capture or start recording dynamically based on the user's consent interaction.

When should I not use holistic capture delay for privacy compliance?▼

You should avoid holistic capture delay if your application requires identifying users before consent is granted, as identity coordination relies on calling FS('identify') only after explicit user permission is obtained.