fullstory-page-properties

Automate Fullstory Page Properties implementation for consistent page naming and context capture.

Updated Dec 20, 2025

Search Tags:#analytics #SPA #web #journeys #page-properties #fullstory

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fullstory Page Properties provide a structured way to attach page-level context to all events, unlocking richer search, Segments, Funnels, and Journeys across web and SPA experiences.

Core Features & Use Cases

Consistent page naming: use a generic pageName to group events across Journeys while attaching specific context as properties.
Rich page context: capture page type, category, author, publish date, pricing, and other metadata to enable precise analysis.
SPA navigation handling: re-set or merge page properties on route changes to maintain accurate page context across navigations.

Quick Start

Use FS('setProperties', { type: 'page', properties: { pageName: 'Dashboard', dateRange: 'last30days', widgetCount: 4 } }) to initialize a page context, then update properties on interactions or navigation as needed.

Frequently Asked Questions about fullstory-page-properties

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

FAQPage Schema

How do I add page context to Fullstory analytics for SPA navigations?▼

To add page context in Fullstory analytics for SPA navigations, use the setProperties API with a defined pageName and reset or merge properties on route changes. This maintains accurate page context for journey tracking.

What are Fullstory page properties and when do I need them?▼

Fullstory page properties are structured metadata attached to page-level events, needed when you want to capture context like page type or category. They unlock richer search, funnels, and journey analytics across web experiences.

How do I implement Fullstory page naming consistently across web apps?▼

Implement consistent Fullstory page naming by defining a generic pageName to group events, then attaching specific metadata as properties. Initialize context using FS setProperties and update it during interactions as needed.

Does Fullstory setProperties work with single page applications?▼

Yes, Fullstory setProperties works with single page applications by allowing you to reset or merge page properties on route changes. This maintains accurate page context across navigations in modern web apps.

What are the limits for Fullstory page properties and pageName values?▼

The limits for Fullstory page properties are 50 properties per page and 1,000 unique pageName values. Enforcing these constraints when defining page context prevents disruption to journey analytics and dashboards.