Developer Guide
Analytics & Telemetry
Understanding Crowdon Analytics
Crowdon provides privacy-conscious, developer-owned launch metrics. Because external games are hosted on independent developer infrastructure, the platform maintains clear distinctions between observed browser actions and verified gameplay.
Metric Definitions
| Metric | Definition | Availability |
|---|---|---|
| Game Detail View | A qualifying view of your game's public details page (active tab for ≥1s; deduplicated in 10-minute windows). | Observed (Active) |
| Launch Attempt | A client request initiated by a player clicking "Play Game". | Observed (Active) |
| Recorded Launch | An authorized launch where the approved external destination was returned and persisted. | Observed (Active) |
| Launch Conversion Ratio | (Recorded Launches / Qualifying Detail Views) × 100. Event-count ratio; can exceed 100% on repeat launches. | Calculated (Active) |
| Verified Play Session | Confirmed gameplay session on the remote host with arrival and heartbeat telemetry. | Future (CRD-011) |
| Verified Playtime | Cryptographically validated active playtime for player rewards and achievements. | Future (CRD-012) |
Privacy & Retention Invariants
- No IP or Device Fingerprinting: Crowdon never stores persistent raw IP addresses or hardware fingerprints.
- Consented Tracking: First-party visitor estimation cookies default to off and require player opt-in.
- UTC Aggregations: All analytics are aggregated and reported in UTC calendar days.
- Retention Policy: Raw event records are purged after 90 days; daily aggregates are retained for 730 days (2 years).