universal-data-scoping-and-decoration

Decide data scope for Fullstory attributes across user, page, element, and event levels.

11|2|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/fullstorydev/fs-skills --skill universal-data-scoping-and-decoration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: universal-data-scoping-and-decoration
Source: https://github.com/fullstorydev/fs-skills/tree/main/meta/universal-data-scoping-and-decoration
Command: npx skills add https://github.com/fullstorydev/fs-skills --skill universal-data-scoping-and-decoration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This meta-skill provides a deterministic framework to decide where to store data (user, page, element, or event) to maximize searchability, avoid duplication, and ensure consistent Fullstory implementation across API types.

Core Features & Use Cases

  • Scope guidance: decide the correct scope for attributes to minimize duplication.
  • Inheritance rules: explain how properties propagate from user to page to elements and events.
  • Privacy-aware design: integrate privacy controls at each scope and provide guidelines for masking or excluding sensitive data.

Quick Start

Example: On a Product Detail Page, assign productId and productName as Page Properties, place itemVariant on each product card as Element Properties, and track purchases as Events.

Frequently Asked Questions about universal-data-scoping-and-decoration

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

FAQPage Schema
How do I prevent duplicate data when setting up Fullstory page properties and events?

To prevent duplicate data in Fullstory, apply deterministic data scoping rules that enforce hierarchical placement across user, page, element, and event scopes. This ensures properties inherit correctly and avoids redundant data capture.

How does Fullstory property inheritance work across user, page, and element scopes?

Fullstory property inheritance propagates values hierarchically from user to page, then to elements and events. This scoping framework ensures child scopes inherit parent attributes, maintaining consistency without duplicating properties at every level.

What is the best way to scope data on a multi-entity listing page for Fullstory analytics?

For multi-entity listings, assign shared identifiers as page properties and place variant-specific attributes as element properties on each item card. This scoping strategy ensures searchability while keeping individual element data distinct and non-duplicated.

How do I apply privacy controls and masking to Fullstory event tracking?

Apply privacy controls at each data scope level by integrating masking or exclusion rules for sensitive attributes before event tracking. This privacy-aware design ensures user, page, and element properties comply with data restrictions while remaining searchable.

When should I use element properties instead of page properties in Fullstory?

Use element properties for attributes specific to individual components on a page, like a product card's variant, and page properties for entity-level data like productId. This scope distinction maximizes searchability and prevents property duplication across listings.