fullstory-user-consent

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.

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.

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.

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.

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.

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.