fullstory-observe-callbacks

Subscribe to Fullstory lifecycle events using the FS('observe', ...) API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to subscribe to Fullstory lifecycle events via the web observe API, allowing real-time reactions to capture start and session URL events without polling.

Core Features & Use Cases

  • Real-time event subscriptions: listen for 'start' and 'session' events and react accordingly.
  • Cross-tool integration: forward session URLs to analytics, logging, or support tools.
  • Lifecycle-driven UI: enable features when Fullstory begins capturing or when a session URL becomes available.

Quick Start

Register observers with FS('observe', { type: 'session', callback: ... }); and optionally an observer for 'start'. Always disconnect observers on cleanup.

Frequently Asked Questions about fullstory-observe-callbacks

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

FAQPage Schema
How do I subscribe to Fullstory lifecycle events in the browser?

You can monitor Fullstory lifecycle events by registering observers with the FS('observe', ...) API to listen for 'start' and 'session' events, allowing real-time reactions without polling.

What is the Fullstory observe API used for?

The Fullstory observe API is used to subscribe to real-time lifecycle events like 'start' and 'session', allowing applications to react immediately when capturing begins or a session URL becomes available.

Can I forward Fullstory session URLs to analytics or support tools?

Yes, you can forward Fullstory session URLs to analytics, logging, or support tools by subscribing to 'session' events via the observe API and passing the URL to your integrated tools.

How do I prevent memory leaks when using Fullstory web callbacks?

To prevent memory leaks when using Fullstory web callbacks, always disconnect your observers during the cleanup phase of your web workflow after subscribing to lifecycle events.

Does the Fullstory observe API require polling to get session URLs?

No, the Fullstory observe API does not require polling. It provides real-time updates for session URL and start events directly through registered web callbacks, eliminating the need for continuous polling.

When should I listen for the Fullstory start event?

You should listen for the Fullstory start event when you need lifecycle-driven UI updates, such as enabling specific features only after Fullstory has officially begun capturing data.