Roblox Analytics

by TabooHarmony38826be57ee37bcf023e9c2b85681bea3909281cNo licenseListed Oct 9, 2026Updated Oct 9, 2026

Use when tracking player behavior, economy events, or funnels with AnalyticsService, including event taxonomy, rate limits, and batching.

Instructions onlyData & Analytics

AI-generated overview

Reference for instrumenting Roblox games with AnalyticsService: event types, rate limits, batching, and economy health signals.

What it does: This skill is a reference guide for tracking player behavior, economy events, and funnels in Roblox games using the built-in AnalyticsService. It covers the three event types (Custom, Economy, Funnel), rate limits and batching, event and field caps, logging rules, and dashboard timing. It also describes economy health signals such as sink/source ratio, inflation, whale concentration, and cohort retention, and points to a fuller reference file with code examples and API tables.
When to use it: Use it when adding or reviewing AnalyticsService instrumentation in a Roblox experience, or when tracking player behavior, currency flow, or funnel progression. It is also meant for diagnosing a broken in-game economy from telemetry signals.
Requirements: No scripts; instructions only. It assumes access to Roblox's built-in AnalyticsService and the Creator Hub dashboard, and references an additional file, references/full.md, for detailed examples.

Roblox Analytics Reference

Load when tracking player behavior, economy events, or funnels, or when building AnalyticsService instrumentation.

Key rules:

Use AnalyticsService (built-in). No third-party analytics SDK needed.
Three event types: Custom (counters/values), Economy (currency flow), Funnel (step progression)
Rate limit: 120 + (20 × CCU) calls per minute. Batch where possible.
Max 100 custom events, 10 resource types, 10 funnels, 3 custom fields per event.
Log events AFTER successful operations, not on attempt. Failed attempts log nothing.
Report the balance the authoritative mutation RETURNED at commit, unchanged. Never recompute it from the leaderstats replica: it already reflects the grant; re-adding double-counts.
Custom fields (up to 3) slice data without burning event cardinality.
Economy events track sources (earned) and sinks (spent) separately.
Funnel steps need not fire in order; skipped intermediate steps are auto-back-filled as completed when a later step logs.
Events appear on Creator Hub dashboard after ~24 hours. Use "View Events" for real-time validation.
Prefer server-side logging for accuracy; client-side only for UI interaction tracking.
Creator Rewards: no AnalyticsService grant event. Analytics for leading indicators (session duration, onboarding, referral milestones); Creator Dashboard for payout attribution.

Economy health (decision layer):

Instrument from day one; you cannot backfill history when the economy breaks.
Log source AND sink per currency with SKUs + the committed mutation's returned balance.
Health signals: sink/source ratio, inflation (CurrencySources - CurrencySinks), whale concentration (high ARPPU + low ARPDAU), price elasticity, sink sufficiency, D1/D7 cohorts. Thresholds are heuristics, not Roblox statements.
Economy breaks: verify events exist + correct, read narrowest broken signal, change ONE lever, re-check. Telemetry reports what broke; the user owns the design decision.

Cross-refs: roblox-growth-design for audit workflow; roblox-monetization for the purchase funnel.

Need more detail? Load references/full.md for the complete reference with code examples, API tables, and edge cases.

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.