fullstory-identify-users

Link user sessions to stable identities after authentication with setIdentity.

11|2|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-identify-users-fullstorydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fullstory-identify-users
Source: https://github.com/fullstorydev/fs-skills/tree/main/core/fullstory-identify-users
Command: npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-identify-users-fullstorydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables applications to safely link user sessions to stable identities, enabling cross-device analytics while preserving privacy.

Core Features & Use Cases

  • Immediate identification after successful authentication to tie session data to a user profile
  • Cross-device session linking so activity on web and mobile can be correlated to a single uid
  • Logout/privacy handling with proper anonymization to avoid identity pollution
  • Platform guidance via SKILL-WEB.md and SKILL-MOBILE.md for web and mobile implementations

Quick Start

After authenticating a user, call setIdentity with a stable uid and include essential properties like displayName and email. Example: 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 link user sessions to stable identities after authentication?

To link user sessions to stable identities, call setIdentity after successful authentication using a stable UID, and include properties like displayName and email to tie session data to the user profile.

What is the best way to handle user anonymization on logout to prevent identity pollution?

Proper anonymization on logout prevents identity pollution by applying platform-specific handling via SKILL-WEB.md and SKILL-MOBILE.md, ensuring session data is safely unlinked from the stable UID without corrupting cross-device analytics.

Does this approach support cross-platform session linking for both web and mobile?

Yes, cross-platform session linking is supported across web and mobile platforms. The Skill provides dedicated platform guidance via SKILL-WEB.md and SKILL-MOBILE.md to correlate activity from different devices to a single UID.

When do I need to apply stable UID identification in my application flows?

Stable UID identification is needed immediately after login flows, app startup, and OAuth or SSO redirects. Applying it at these points ensures cross-device analytics are accurately tied to real user profiles while preserving privacy.

What properties should I include when calling setIdentity for cross-device analytics?

When calling setIdentity for cross-device analytics, you should include a stable UID as the primary identifier, along with essential user properties such as displayName and email to enrich the linked profile data.