game-analytics

name	game-analytics
description	Game analytics tracks player behavior and game performance. This guide Use when this capability is needed.
metadata	{"author":"amnadtaowsoam"}

Game Analytics

Skill Profile

(Select at least one profile to enable specific modules)

• DevOps
• Backend
• Frontend
• AI-RAG
• Security Critical

Overview

Game analytics tracks player behavior and game performance. This guide covers metrics, event tracking, funnel analysis, and analytics platforms for understanding player engagement, optimizing gameplay, and improving retention.

Why This Matters

Game analytics is critical for gaming platforms as it directly impacts:

• Game Balance: Data-driven difficulty adjustments
• Monetization: Optimize in-app purchases
• Retention: Identify and address churn points
• User Experience: Remove friction points

---

Core Concepts

1. DAU/MAU/WAU: Daily/Monthly/Weekly Active Users
2. Retention: Day 1, 7, 30 retention rates
3. Funnel Analysis: Conversion through game stages
4. Cohort Analysis: Track groups by install date
5. A/B Testing: Compare feature variants
6. Player Segmentation: Group players by behavior
7. LTV: Lifetime Value calculation
8. Real-time Dashboard: Live metrics visualization

Inputs / Outputs / Contracts

Skill Composition

• Depends on: None
• Compatible with: None
• Conflicts with: None
• Related Skills: None

Quick Start / Implementation Example

1. Review requirements and constraints
2. Set up development environment
3. Implement core functionality following patterns
4. Write tests for critical paths
5. Run tests and fix issues
6. Document any deviations or decisions

# Example implementation following best practices
def example_function():
    # Your implementation here
    pass

Assumptions

• Player IDs are unique and persistent
• Event tracking doesn't impact gameplay performance
• Analytics platform integration available
• Database supports efficient aggregation queries

Compatibility

Platform	Event Tracking	Funnels	Cohorts
Unity Analytics	Yes	Limited	Yes
GameAnalytics	Yes	Yes	Yes
Mixpanel	Yes	Yes	Limited
Amplitude	Yes	Yes	Yes
Custom	Yes	Yes	Yes

---

Test Scenario Matrix (QA Strategy)

Type	Focus Area	Required Scenarios / Mocks
Unit	Core Logic	Must cover primary logic and at least 3 edge/error cases. Target minimum 80% coverage
Integration	DB / API	All external API calls or database connections must be mocked during unit tests
E2E	User Journey	Critical user flows to test
Performance	Latency / Load	Benchmark requirements
Security	Vuln / Auth	SAST/DAST or dependency audit
Frontend	UX / A11y	Accessibility checklist (WCAG), Performance Budget (Lighthouse score)

Technical Guardrails & Security Threat Model

1. Security & Privacy (Threat Model)

• Top Threats: Injection attacks, authentication bypass, data exposure

• Data Handling: Sanitize all user inputs to prevent Injection attacks. Never log raw PII
• Secrets Management: No hardcoded API keys. Use Env Vars/Secrets Manager
• Authorization: Validate user permissions before state changes

2. Performance & Resources

• Execution Efficiency: Consider time complexity for algorithms
• Memory Management: Use streams/pagination for large data
• Resource Cleanup: Close DB connections/file handlers in finally blocks

3. Architecture & Scalability

• Design Pattern: Follow SOLID principles, use Dependency Injection
• Modularity: Decouple logic from UI/Frameworks

4. Observability & Reliability

• Logging Standards: Structured JSON, include trace IDs request_id
• Metrics: Track error_rate, latency, queue_depth
• Error Handling: Standardized error codes, no bare except
• Observability Artifacts:
  • Log Fields: timestamp, level, message, request_id
  • Metrics: request_count, error_count, response_time
  • Dashboards/Alerts: High Error Rate > 5%

Agent Directives

1. Always track key events without impacting performance
2. Anonymize user data for privacy compliance
3. Use sampling for high-volume events
4. Define clear funnels for conversion tracking
5. Set up cohorts for retention analysis
6. Monitor real-time metrics for operational issues
7. Act on insights from analytics data

Definition of Done (DoD) Checklist

• Tests passed + coverage met
• Lint/Typecheck passed
• Logging/Metrics/Trace implemented
• Security checks passed
• Documentation/Changelog updated
• Accessibility/Performance requirements met (if frontend)

Anti-patterns / Pitfalls

• ⛔ Don't: Log PII, catch-all exception, N+1 queries
• ⚠️ Watch out for: Common symptoms and quick fixes
• 💡 Instead: Use proper error handling, pagination, and logging

Reference Links & Examples

• Internal documentation and examples
• Official documentation and best practices
• Community resources and discussions

Versioning & Changelog

• Version: 1.0.0
• Changelog:
  • 2026-02-22: Initial version with complete template structure

---

Converted and distributed by TomeVault — claim your Tome and manage your conversions.