Roblox Analytics

作者 TabooHarmony38826be57ee37bcf023e9c2b85681bea3909281c無授權條款收錄於 2026年10月9日更新於 2026年10月9日

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

AI 產生的概覽

關於使用 AnalyticsService 為 Roblox 遊戲埋點的參考：事件類型、速率限制、批次處理與經濟健康訊號。

功能: 這個技能是一份參考指南，說明如何使用 Roblox 內建的 AnalyticsService 追蹤玩家行為、經濟事件與漏斗。內容涵蓋三種事件類型（Custom、Economy、Funnel）、速率限制與批次處理、事件與欄位數量上限、記錄規則，以及儀表板顯示時間。它也描述經濟健康訊號，例如消耗/來源比、通膨、鯨魚玩家集中度與同期群留存，並指向更完整的參考檔案以取得程式碼範例與 API 表格。
適用情境: 適用於在 Roblox 體驗中加入或檢視 AnalyticsService 埋點，或需要追蹤玩家行為、貨幣流動與漏斗進度時。也用於依據遙測訊號診斷遊戲內經濟失衡。
執行需求: 不需要指令碼，僅為說明文件。假定可使用 Roblox 內建的 AnalyticsService 與 Creator Hub 儀表板，並引用附加檔案 references/full.md 以取得詳細範例。

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.

授權條款：無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。