fullstory-element-properties

Implement Fullstory Element Properties API across Web, Android, and iOS.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers in implementing Fullstory's Element Properties API across Web, Android, and iOS to decorate interactive UI elements with semantic data, enabling richer analytics without manual instrumentation.

Core Features & Use Cases

  • Cross-platform guidance for defining element properties, building robust data schemas, and applying type mappings for Web, Android, and iOS.
  • Patterns for common UI patterns (e.g., product cards, forms, and list items) with inheritance so parent context automatically flows to children.
  • Real-world use case: instrument a product card to capture productId, price, and category, and ensure those properties are captured on a button press or item interaction.

Quick Start

Create a simple Product Card example:

  • Define attributes data-product-id and data-price on the card.
  • Provide a data-fs-properties-schema mapping to productId, price.
  • Name the element via data-fs-element as "Product Card" and ensure a child button inherits 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 add semantic data to UI elements for Fullstory analytics tracking?

Fullstory element properties allow you to decorate interactive components with semantic data using Web, Android, and iOS APIs. By mapping attributes like product IDs into structured schemas, you enable richer analytics capture without manual event instrumentation.

What is the best way to implement Fullstory element properties across Web, Android, and iOS?

The best way to implement Fullstory element properties is to define robust schemas, apply proper typing for each platform, and set clean values before applying schemas. You must validate JSON schemas and avoid high-cardinality debug data to maintain performance.

Does Fullstory element properties inheritance work for nested UI components like product cards?

Fullstory element properties support hierarchical inheritance for nested UI components like product cards and list items. Parent context automatically flows to children, ensuring properties like productId and price are captured on child interactions such as button presses.

How do I avoid high-cardinality debug data when defining Fullstory element schemas?

To avoid high-cardinality debug data when defining Fullstory element schemas, enforce best practices such as using clean, typed values and validating JSON schemas. This prevents excessive unique values from degrading analytics performance and query speeds.

What limitations should I consider when applying Fullstory element properties to form fields?

When applying Fullstory element properties to form fields, limitations include the requirement to set values before schemas and the risk of capturing high-cardinality debug data. You must ensure proper typing and JSON schema validation to avoid tracking errors.