Game Analytics Rapid

Rapidly integrate analytics tracking, player behavior monitoring, and KPI dashboards into game projects.

When to Use This Command

Run this command when you need to:

• Instrument a game with event tracking for player sessions, progression, and monetization
• Set up real-time analytics dashboards for player behavior and game performance KPIs
• Configure A/B testing infrastructure for feature experiments and game balance tuning

Consider alternatives when:

• You need a custom analytics backend rather than integration with existing platforms
• Your game is in early prototype phase and does not yet need analytics instrumentation

Quick Start

Configuration

Copy
name: game-analytics-rapid
type: command
category: game-development

Example Invocation

Copy
claude command:run game-analytics-rapid --engine unity --platform mobile

Example Output

Game Engine: Unity 2023.3
Target Platform: iOS + Android

Analytics Integration:
  [+] Event tracking system initialized (48 event types)
  [+] Session tracking with automatic start/end detection
  [+] Player progression funnel (12 milestone events)
  [+] Monetization tracking (IAP, ads, subscriptions)
  [+] Performance metrics (FPS, load times, memory)

Dashboard Configuration:
  [+] DAU/MAU retention dashboard
  [+] Revenue and ARPU monitoring
  [+] Funnel conversion analysis
  [+] Session length distribution
  [+] Device performance heatmap

Privacy Compliance:
  [+] GDPR consent flow integrated
  [+] COPPA age gate configured
  [+] Data anonymization pipeline active

Event taxonomy: Assets/Analytics/EventTaxonomy.json

Core Concepts

Game Analytics Overview

Aspect	Details
Event Taxonomy	Structured naming for session, progression, economy, and social events
Player Segmentation	Cohort analysis by acquisition date, spend tier, and engagement level
Funnel Analysis	Tracks player progression through onboarding, core loop, and monetization
A/B Testing	Feature flag integration for experiment assignment and result tracking
Privacy Compliance	GDPR, CCPA, and COPPA consent management built into the SDK

Analytics Pipeline Workflow

  Game Client
       |
       v
  +------------------+
  | Track Events     |---> Session, progression, economy
  +------------------+
       |
       v
  +------------------+
  | Batch and Send   |---> Queue events, send on interval
  +------------------+
       |
       v
  +------------------+
  | Process and Store|---> Analytics backend pipeline
  +------------------+
       |
       v
  +------------------+
  | Aggregate KPIs   |---> DAU, retention, ARPU
  +------------------+
       |
       v
  +------------------+
  | Dashboard + Alert|---> Real-time views + anomaly alerts
  +------------------+

Configuration

Parameter	Type	Default	Description
engine	string	auto-detect	Game engine: unity, unreal, godot, custom
platform	string	all	Target platform: mobile, pc, console, web, or all
provider	string	firebase	Analytics provider: firebase, gameanalytics, amplitude, mixpanel
ab_testing	boolean	true	Enable A/B testing infrastructure
privacy	string	gdpr	Privacy framework: gdpr, ccpa, coppa, or all

Best Practices

1. Design Event Taxonomy Before Implementing - Create a complete event naming convention and data schema before writing any tracking code. Changing event names after launch breaks historical data continuity and dashboard queries.

2. Batch Events to Reduce Network Load - Queue analytics events locally and send them in batches every 30-60 seconds. Sending each event individually on mobile devices drains battery and consumes bandwidth.

3. Track Negative Events Too - Do not only track success events. Track failures, rage quits, repeated retries, and uninstalls. These signals reveal where players struggle and where the game needs improvement.

4. Respect Player Privacy From Day One - Implement consent flows before collecting any data, not as an afterthought. Retrofitting privacy compliance into a live game is expensive and risks regulatory penalties.

5. Set Up Anomaly Alerts - Configure alerts for sudden drops in DAU, revenue, or session length. Anomaly detection catches silent failures (broken IAP, server issues) before they are reported by players.

Common Issues

1. Events Not Appearing in Dashboard - The analytics SDK is initialized but events are buffered and never flushed. Ensure the SDK flush method is called on application pause and quit events, especially on mobile platforms.

2. Duplicate Session Events - The session start event fires multiple times due to scene reloading or application lifecycle quirks. Use a singleton analytics manager that tracks session state and prevents duplicate initialization.

3. A/B Test Assignment Not Persistent - Players receive different experiment variants on each session. Store the assigned variant in persistent local storage and send it with every event to ensure consistent experiment analysis.