fullstory-identify-users

Link browser sessions to stable user identifiers in Fullstory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers in correctly identifying users in Fullstory to link sessions to stable user IDs, enabling reliable analytics, searchability, and cross-device tracking while preserving user privacy.

Core Features & Use Cases

  • Identify users immediately after authentication to ensure session data is associated with the correct uid.
  • Maintain identity across page navigation, SPA/SSR, and OAuth/SSO callbacks; support anonymization flows when switching accounts.
  • Use properties (displayName, email, role, plan) for discoverability and segmentation; prefer setIdentity for initial linking and setProperties for updates.

Quick Start

Identify a logged-in user and link their session: FS('setIdentity', { uid: user.id, properties: { displayName: user.name, email: user.email } })

Frequently Asked Questions about fullstory-identify-users

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

FAQPage Schema
How do I identify users in Fullstory to link browser sessions to stable user IDs?

Use setIdentity to link browser sessions to stable user identifiers by passing a uid and properties object immediately after authentication. This ensures accurate analytics and cross-device tracking while maintaining user privacy.

When should I use setIdentity versus setProperties for Fullstory user analytics?

Use setIdentity for the initial linking of a user session to a uid, and use setProperties for updating user attributes like displayName, email, role, or plan. This distinction ensures reliable session searchability and accurate user segmentation.

Can I use email addresses as the uid when identifying users in Fullstory?

Using email addresses or other PII as the uid is discouraged. To preserve user privacy, you should use a stable, internal user identifier for the uid, while passing the email as a property for discoverability and segmentation.

How do I maintain user identity across SPA page loads and OAuth/SSO callbacks for web analytics?

Apply setIdentity across login, page load, and OAuth/SSO callbacks to maintain a single identity across devices and sessions. This ensures session data remains associated with the correct uid during SPA and SSR navigation.

What is the best way to anonymize users in Fullstory when switching accounts?

To anonymize users when switching accounts, use the anonymize function provided by the Skill. This breaks the link between the browser session and the previous uid, ensuring subsequent session data is not associated with the prior user.