skills.rest
fullstorydev
fullstorydevOFFICIAL
Explore all skills by this author →
WebsiteGitHub

fullstory-page-properties

Attach page-level context to events with named pages and mergeable properties.

11|2|Updated Dec 2, 2025
Search Tags:#context#mobile#SPA#journeys#page-properties#setProperties
One-click install
npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-page-properties-fullstorydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fullstory-page-properties
Source: https://github.com/fullstorydev/fs-skills/tree/main/core/fullstory-page-properties
Command: npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-page-properties-fullstorydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Page properties provide session-scoped context that enriches every event on a screen by naming pages and attaching contextual data. This avoids ad-hoc, inconsistent data collection and enables powerful journeys, search, and segmentation across web and mobile.

Core Features & Use Cases

  • Define a named page with pageName so all events on that page carry consistent context.
  • Persist contextual data across navigation on that page (and reset on navigation) to support journeys and funnels.
  • Capture common contexts (search terms, checkout steps, article metadata, dashboard views) with page-level properties that complement event data.

Quick Start

On your app startup or screen/view appearance, call the Page Properties API to set the initial page name and properties. For example: FS('setProperties', { type: 'page', properties: { pageName: 'Product Detail', productId: 'SKU-123', category: 'Electronics' } });

Frequently Asked Questions about fullstory-page-properties

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

FAQPage Schema
How do I attach page context to events for SPA and mobile journey analysis?▼

Attach page context to events by calling setProperties with a type of page and a defined pageName. This enriches all events on that screen with session-scoped contextual data to support search, segmentation, and journey analysis.

What is the best way to manage page properties during screen navigation?▼

Manage page properties by merging data on repeat setProperties calls for the same screen and resetting them upon navigation. This ensures contextual data persists accurately for the current view without bleeding into unrelated screens.

Does setProperties work with both web and mobile platforms?▼

Yes, setProperties applies across both web and mobile platforms. You can use the same page properties API to name pages and capture contextual data consistently regardless of the user's device environment.

What is the limit for unique pageName values when defining page properties?▼

The system enforces a limit of 1,000 unique pageName values. You must honor this constraint when naming pages to avoid exceeding the maximum allowed unique page identifiers during implementation.

How do I capture search terms and checkout steps using page properties?▼

Capture search terms and checkout steps by passing them within the properties object of your setProperties call. This attaches common contextual data at the page level, complementing individual event data for deeper funnel analysis.

Related Skills

Explore More Software Engineering Skills→
rcmaplesrcmaples

fullstory-user-properties

Set and update Fullstory user attributes with setIdentity and setProperties.

Community
Advanced
Productfculty-aipmProductfculty-aipm
70

cohort-analysis

Analyze cohort retention tables or CSVs to compute D1/D7/D30 rates and identify drop-offs.

Community
Intermediate
PostHogPostHog
58

integration-django

Integrates PostHog analytics into Django applications via middleware and AppConfig.

Official
Advanced
unoplatformunoplatform
9

uno-toolkit-command-extensions

Bind UI controls to MVVM commands via attached properties in XAML.

Official
Intermediate