fullstory-observe-callbacks

Observe Fullstory 'start' and 'session' lifecycle events with async callbacks.

Updated Dec 20, 2025

Search Tags:#integration #callbacks #web #observer #session-url #fullstory

Ready to run

npx skills add https://github.com/rcmaples/btx --skill fullstory-observe-callbacks

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables developers to observe Fullstory lifecycle events (start and session) in web applications, allowing real-time reactions instead of polling or manual checks.

Core Features & Use Cases

Real-time event listening: Subscribe to Fullstory 'start' and 'session' events and handle callbacks.
Session URL capture: Access the session URL and forward it to analytics, support tools, or error reporting services.
Safe lifecycle management: Implement observer creation and cleanup to prevent memory leaks in SPA and traditional apps.
Integration patterns: Use with analytics or 3rd-party tools to enrich data when Fullstory is ready.

Quick Start

Register observers for 'start' and 'session', log or forward the URL when a session event fires, and ensure you call disconnect() 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 capture the Fullstory session URL in real time instead of polling?▼

You can capture the Fullstory session URL by registering an observer for the 'session' event, which fires asynchronously and provides the URL directly to your callback for forwarding to analytics or support tools.

What Fullstory lifecycle events can I observe in a web application?▼

You can observe 'start' and 'session' lifecycle events in web applications, enabling real-time reactions for initialization awareness and session URL capture without manual checks.

How do I safely clean up Fullstory event observers in an SPA to prevent memory leaks?▼

To prevent memory leaks in SPAs, implement proper lifecycle management by calling disconnect() on your observers during component cleanup to safely remove Fullstory event listeners.

Does this Fullstory observer pattern work when the FS script is unavailable or blocked?▼

Yes, the observer pattern enforces resilience when FS is unavailable, ensuring your web application handles missing Fullstory scripts gracefully without breaking existing functionality.

Can I use Fullstory callbacks to integrate session data with third-party analytics tools?▼

Yes, you can use Fullstory callbacks to integrate session data with third-party analytics tools by forwarding the captured session URL from the 'session' event to enrich your analytics data.