fullstory-async-methods

Coordinate Fullstory async API calls with timeouts and error handling.

11|2|Updated Dec 2, 2025

Search Tags:#async #initialization #error-handling #web #session-url #Fullstory #sequencing

Ready to run

npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-async-methods-fullstorydev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fullstory-async-methods
Source: https://github.com/fullstorydev/fs-skills/tree/main/core/fullstory-async-methods
Command: npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-async-methods-fullstorydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web applications often need to coordinate multiple actions with the Fullstory browser SDK. This skill provides a structured approach to safely waiting for initialization, obtaining session URLs, and sequencing analytics calls without blocking the UI.

Core Features & Use Cases

Initialization waiting: wait for FS bootstrap before performing dependent actions.
Session URL retrieval: obtain the session replay URL for reporting or support.
Error handling & sequencing: gracefully handle failures and ensure correct ordering of identity, properties, and events.
Conditional logic: enable or bypass features based on FS availability.

Quick Start

Start by waiting for Fullstory readiness, then identify the user, and finally track an event. Example steps:

await FS('getSessionAsync')
await FS('setIdentityAsync', { uid: 'user-id', displayName: 'User' })
await FS('trackEventAsync', { name: 'Session Start' })

Frequently Asked Questions about fullstory-async-methods

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

FAQPage Schema

How do I wait for Fullstory initialization before calling other methods?▼

Use async API variants such as setIdentityAsync and trackEventAsync with proper timeouts and try/catch blocks. This approach handles sequencing and failures gracefully without blocking the user interface.

What's the best way to get a Fullstory session URL for support reporting?▼

Retrieve the session replay URL by awaiting the getSessionAsync method. This provides the current session URL needed for support reporting once the Fullstory browser SDK has fully initialized.

Why does blocking the UI happen during Fullstory analytics tracking?▼

Blocking the UI occurs when using synchronous Fullstory calls before initialization completes. Using async variants with timeouts and try/catch error handling prevents blocking user flows during analytics sequencing.

Can I conditionally bypass Fullstory features if the SDK is unavailable?▼

Yes, you can enable or bypass features based on Fullstory availability. By using async methods with error handling, you can implement conditional logic that safely skips SDK-dependent actions if initialization fails.

Do I need to sequence Fullstory identity and event tracking calls?▼

Yes, proper sequencing ensures correct ordering of identity, properties, and events. Await setIdentityAsync before calling trackEventAsync to maintain data integrity without blocking the web UI.