fullstory-user-consent

Implement Fullstory User Consent API flows for privacy-compliant session recording.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/rcmaples/btx --skill fullstory-user-consent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fullstory-user-consent
Source: https://github.com/rcmaples/btx/tree/main/.claude/skills/fullstory-user-consent
Command: npx skills add https://github.com/rcmaples/btx --skill fullstory-user-consent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers in implementing Fullstory's User Consent API to ensure privacy-compliant session recording for web applications.

Core Features & Use Cases

  • Holistic consent control: Delay all capture until user consent and start recording only after approval.
  • Element-level consent: Enable or disable capture for pre-defined elements that require explicit permission.
  • CMP integration & withdrawal: Integrate with CMPs (OneTrust, CookieBot, TrustArc) and provide a clear withdrawal path for users.
  • Audit-ready flows: Persist consent state locally and optionally back to a backend for compliance records.

Quick Start

Use the Fullstory User Consent skill to implement a GDPR-compliant consent flow that delays all capture until consent and starts capture after consent, with a banner and withdrawal option.

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 recording until GDPR consent is given?

You can implement element-level consent using Fullstory's User Consent API to enable or disable capture for pre-defined elements. This allows you to restrict recording only to specific page sections that require explicit permission.

How do I integrate Fullstory consent with a CMP like OneTrust or CookieBot?

Integrate Fullstory consent with a CMP like OneTrust or CookieBot by mapping the CMP's consent state changes to the Fullstory User Consent API. This links the consent management platform directly to your session recording controls.

What is the best way to handle user consent withdrawal for web session replays?

The best way to handle user consent withdrawal for web session replays is to provide a clear withdrawal path that immediately triggers the Fullstory API to shut down recording. You should also persist the updated consent state locally and optionally back to your backend for audit-ready compliance.

Can I persist Fullstory consent state locally for CCPA and GDPR audit compliance?

Yes, you can persist Fullstory consent state locally to maintain audit-ready compliance flows for GDPR and CCPA. Saving the consent state locally and optionally backing it up to a backend creates a reliable record of user permission for session recording.

Does Fullstory session recording work with element-level consent for specific page sections?

Yes, Fullstory session recording works with element-level consent, allowing you to enable or disable capture for pre-defined elements. This ensures that sensitive page sections requiring explicit permission are excluded from the recording.