fullstory-getting-started

Configure the Fullstory Browser API v2 to capture and mask user interactions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, framework-backed guide to implementing the Fullstory Browser API v2 in a web application, including privacy controls, identity management, page and event tracking, and industry-specific guidance.

Core Features & Use Cases

  • Initial setup: snippet installation and configuration per v2 guidelines.
  • API overview and decision framework for choosing among Identity, Page Properties, Element Properties, Events, and Privacy controls.
  • Industry-specific guidance and integration patterns to align with privacy and compliance.

Quick Start

Install the Fullstory Browser API v2 snippet on your site following the guide in SKILL.md. Enable privacy controls (fs-exclude/fs-mask) as appropriate for your industry and data sensitivity. Identify users on login, set basic page properties, and track a key event to validate the integration.

Frequently Asked Questions about fullstory-getting-started

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

FAQPage Schema
How do I set up Fullstory Browser API v2 to capture user interactions?

To set up Fullstory Browser API v2, install the tracking snippet on your site, configure privacy controls like fs-exclude and fs-mask, identify users on login, set page properties, and track key events to validate the integration.

What is the best way to configure privacy controls when implementing Fullstory?

The best way to configure Fullstory privacy controls is by applying fs-exclude and fs-mask attributes to sensitive elements, ensuring your user interaction capture remains compliant with industry-specific data sensitivity requirements.

How do I choose between Identity, Page Properties, and Events in Fullstory API v2?

Choose between Fullstory Identity, Page Properties, and Events by using the API decision framework, which aligns your tracking needs with user identification on login, page-level context, and specific interaction tracking respectively.

Can I use Fullstory Browser API v2 for industry-specific compliance requirements?

Yes, Fullstory Browser API v2 supports industry-specific compliance by providing targeted guidance and integration patterns that align privacy controls and data masking with your sector's data sensitivity regulations.

Why does my Fullstory instrumentation require privacy-first configuration?

Fullstory instrumentation requires privacy-first configuration to prevent capturing sensitive user data, utilizing fs-exclude and fs-mask attributes to ensure compliant and effective user interaction analytics across modern web apps.