fullstory-user-properties

Set and update Fullstory user attributes with setIdentity and setProperties.

Updated Dec 20, 2025

Search Tags:#analytics #progressive-profiling #crm-sync #user-properties #setIdentity #setProperties #fullstory

Ready to run

npx skills add https://github.com/rcmaples/btx --skill fullstory-user-properties

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fullstory-user-properties
Source: https://github.com/rcmaples/btx/tree/main/.claude/skills/fullstory-user-properties
Command: npx skills add https://github.com/rcmaples/btx --skill fullstory-user-properties

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fullstory's User Properties API lets developers create richer, searchable user records by setting and updating attributes that persist across sessions, enabling better segmentation, personalization, and CRM alignment.

Core Features & Use Cases

Progressive profiling: progressively enrich anonymous and identified users over time as you learn more.
CRM sync: mirror key CRM fields in Fullstory to provide context for sales and support.
Lifecycle updates: reflect status changes (signup, plan changes, onboarding progress) directly in user profiles.

Quick Start

Identify a user with FS('setIdentity', { uid: user.id, properties: { displayName: user.name, email: user.email } }); then enrich with FS('setProperties', { type: 'user', properties: { companyName: data.company, plan: data.plan, onboardingStep: data.step } });

Frequently Asked Questions about fullstory-user-properties

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

FAQPage Schema

How do I enrich anonymous user profiles in Fullstory for better analytics segmentation?▼

Fullstory user properties allow you to progressively enrich anonymous profiles by applying setProperties to add attributes as you learn more. This supports segmentation and personalization across sessions before explicit identity is established.

What's the best way to sync CRM data to Fullstory user records?▼

Syncing CRM data to Fullstory involves using setProperties to mirror key CRM fields into user records. This provides essential context for sales and support teams by maintaining alignment between Fullstory and your CRM.

How do I track user lifecycle changes like onboarding progress in Fullstory?▼

Track lifecycle changes in Fullstory by calling setProperties to update status fields like onboardingStep or plan on the user profile. This reflects real-time status changes across sessions for accurate lifecycle analysis.

Do I need to call setIdentity before using setProperties for Fullstory user attributes?▼

Yes, establishing initial identity is required. You must call FS('setIdentity') with a uid and properties first, which enables subsequent setProperties calls to enrich the identified user record.

Does Fullstory enforce schema typing when setting user properties?▼

Yes, Fullstory enforces explicit typing via schema when setting user properties. This ensures attribute data remains consistent and valid for segmentation, personalization, and analytics queries.

Can I batch user property updates in Fullstory to avoid hitting rate limits?▼

Yes, you can batch user property updates to respect API rate limits. Batching multiple setProperties calls optimizes network requests and prevents throttling when synchronizing lifecycle updates or CRM data.