fullstory-anonymize-users

Anonymize Fullstory sessions with FS('setIdentity', {anonymous: true}) before redirects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers through implementing Fullstory's User Anonymization API to properly end an identified session and start a new anonymous session, ensuring user privacy on logout and during account switching.

Core Features & Use Cases

  • Proper logout handling: anonymize before redirect to prevent the next user's activity from being attributed to the previous user.
  • Account switching and shared devices: cleanly boundaries between identities when users switch accounts or use shared devices.
  • Event tracking before anonymization: optionally capture relevant analytics events (e.g., logout, session timeout) before starting an anonymous session.
  • Privacy-compliance patterns: supports forget-me or privacy-conscious flows while preserving historical analytics.
  • Reference-ready patterns: provides concrete code patterns and pitfalls to avoid.

Quick Start

Implement the anonymization call in your logout flow before any navigation. Example: add a single anonymize call FS('setIdentity', {anonymous: true}) prior to redirecting the user.

Frequently Asked Questions about fullstory-anonymize-users

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

FAQPage Schema
How do I prevent Fullstory session identity bleed on user logout?

To prevent Fullstory session identity bleed, call FS('setIdentity', {anonymous: true}) in your logout flow before any page redirect. This cleanly ends the identified session and starts a new anonymous one, ensuring the next user's activity is not misattributed.

Why does Fullstory attribute the next user's activity to the previous user after logout?

Fullstory attributes activity incorrectly when a session is not anonymized before navigation. Failing to call FS('setIdentity', {anonymous: true}) prior to redirecting causes identity bleed across users on shared devices or account switches.

Can I track a logout event before anonymizing a Fullstory session?

Yes, you can optionally capture analytics events before starting an anonymous Fullstory session. Use FS('trackEvent', ...) to log actions like session timeouts or logouts, then call FS('setIdentity', {anonymous: true}) to anonymize.

What is the best way to handle Fullstory session boundaries for shared devices?

The best way to handle Fullstory session boundaries on shared devices is to implement an anonymization call before any redirect. This cleanly separates identities when users switch accounts or log out.

Does Fullstory user anonymization support re-identification after logout?

Yes, Fullstory anonymization supports subsequent re-identification. You can call FS('setIdentity', {anonymous: true}) to end a session and later re-identify a new user when they log in.