fullstory-analytics-events

Define and emit semantic analytics events via Fullstory's trackEvent API.

11|2|Updated Dec 2, 2025

Search Tags:#analytics #mobile #web #data-collection #trackEvent #event-naming

Ready to run

npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-analytics-events-fullstorydev

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fullstory's Analytics Events API enables teams to define and emit semantically meaningful events using trackEvent, capturing moments that traditional DOM-based data can't express.

Core Features & Use Cases

Semantic event naming (e.g., Product Added, Order Completed) to enable precise funnels.
Rich properties with optional schemas for strong typing and robust segmentation.
Cross-platform guidance; platform-agnostic concepts with web/mobile implementation details in SKILL-WEB.md and SKILL-MOBILE.md.
Use cases include funnel analysis, feature adoption tracking, API/performance events, and non-DOM data collection.

Quick Start

Create your first trackEvent call with a descriptive event name and a properties map, for example Product Added with product_id, price, currency, and quantity; then consult the platform-specific guides for web or mobile.

Frequently Asked Questions about fullstory-analytics-events

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

FAQPage Schema

How do I track custom analytics events outside the DOM on web and mobile?▼

To track custom analytics events outside the DOM, use the trackEvent API to emit semantic events with typed properties. Apply platform-specific implementation details for web and mobile to capture non-DOM moments like API calls or feature usage.

What is semantic event naming and why use it for analytics tracking?▼

Semantic event naming uses descriptive titles like Product Added or Order Completed to enable precise funnel analysis. This approach ensures your analytics events capture meaningful user moments rather than generic clicks, improving segmentation accuracy.

Can I attach typed properties to trackEvent calls for robust segmentation?▼

Yes, trackEvent supports rich properties with optional schemas for strong typing. This allows you to attach structured data like product_id, price, and currency to events, enabling robust segmentation and filtering during analysis.

Does the trackEvent API work for both web and mobile platforms?▼

Yes, trackEvent provides platform-agnostic concepts with specific implementation guidance for both web and mobile. Separate platform-specific guides detail how to apply the API across different environments to capture events consistently.

What are the rate limit constraints when emitting analytics events?▼

The trackEvent API enforces guidelines for rate limits to prevent data overload. You should consult these constraints to avoid hitting ceilings when emitting high-frequency events, ensuring reliable analytics data collection without throttling.