fullstory-element-properties

Attach business context to UI elements for analytics and filtering.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Element properties enable attaching business context to UI elements for enhanced analytics and filtering, reducing reliance on separate event data and enabling cross-platform insights.

Core Features & Use Cases

  • Inherit properties from a parent container to all child elements, ensuring consistent context during interactions.
  • Define a typed, readable properties schema that supports robust filtering, grouping, and analytics across web and mobile.
  • Use across product cards, forms, lists, and interactive widgets to capture rich, actionable context with each interaction.

Quick Start

  • Add a data-fs-element label to the target element and define a data-fs-properties-schema that maps each data attribute to a type and an optional readable name.
  • Set the attribute values before assigning the schema, then apply the schema and finalize naming to complete the setup.
  • Verify that child elements inherit parent properties and test by triggering an interaction to confirm the captured properties.

Frequently Asked Questions about fullstory-element-properties

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

FAQPage Schema
How do I attach business context to UI elements for analytics?

To attach business context to UI elements for analytics, add a data-fs-element label and define a data-fs-properties-schema that maps each data attribute to a type and an optional readable name, ensuring rich filtering across platforms.

What are element properties and when do I need them for web and mobile analytics?

Element properties are typed schema mappings that attach business context to UI elements. You need them to enable fine-grained analytics, robust filtering, and cross-platform insights across web and mobile without relying on separate event data.

Can child elements inherit properties from a parent container during interactions?

Yes, child elements can inherit properties from a parent container. By applying a properties schema to the parent, all child elements automatically receive consistent business context during user interactions across product cards, forms, and lists.

What is the correct sequence for applying a properties schema to an interactive widget?

The recommended sequence for applying a properties schema is to first set the attribute values, then assign the schema, and finally finalize element naming to complete the setup and ensure accurate event capture.

Does this element properties schema approach work across both web and mobile interfaces?

Yes, this element properties schema approach is platform-agnostic and works across both web and mobile interfaces, supporting strict type mappings for element properties and robust cross-platform analytics.

Why are my analytics events missing inherited properties from parent containers?

Analytics events miss inherited properties if attribute values are not set before assigning the schema. Apply the schema to the parent container and test by triggering an interaction to verify that child elements correctly inherit the context.