Fullstory Data Scoping & Decoration FAQs

Question 1

Can this skill help map data for anonymous users?

Accepted Answer

Absolutely. It provides strategies for capturing user properties for anonymous visitors via the FS_UID cookie, ensuring that when a user eventually identifies, their previous session data and attributes transfer seamlessly for a complete customer journey view.

Question 2

What does the Fullstory Data Scoping & Decoration skill do?

Accepted Answer

This skill provides a deterministic framework for Claude to help you decide exactly where to capture data within Fullstory. It establishes a clear hierarchy between User, Page, Element, and Event properties to ensure your analytics are searchable, consistent, and efficient.

Question 3

When should I use Page Properties versus Element Properties?

Accepted Answer

Use Page Properties for data that remains constant across the entire URL path (like a Product ID on a detail page). Use Element Properties for item-specific data on multi-entity listing pages (like the position or price of a specific item in a search results grid) to utilize Fullstory's property bubbling logic.

Question 4

Does this skill help with data privacy and compliance?

Accepted Answer

Yes, it includes privacy-first data decoration guidelines. It teaches Claude to identify sensitive PII and recommends the appropriate scope or masking strategy (like hashing IDs or using fs-exclude) to ensure your implementation remains compliant while still providing actionable insights.

Question 5

How does this skill improve my Fullstory implementation?

Accepted Answer

It eliminates common anti-patterns like data duplication across different scopes. By following the 'Capture at the Highest Relevant Scope' rule, it ensures your data is clean, reduces API overhead, and makes it significantly easier to build segments and funnels in the Fullstory UI.

Fullstory Data Scoping & Decoration

Fullstory Data Scoping & Decoration

About

Key Features

Use Cases

About

Key Features

Use Cases