Analytics events
Read daily traffic and client-reported SDK event counts.
On this page
Tracked events
gameReady, gameplayStart, gameplayStop and happyMoment each count under their method name. track(event, data) counts a custom event name. loadingProgress, saves, room calls and ads do not increment analytics. Ordinary custom data is discarded; the reserved stars event uses only a bounded integer for challenge progress. Direct first-party events are stored as game/day/event aggregate counts. Anonymous HTTP events are rate-limited and omit known bots and configured internal addresses. Never include personal data.
await ZUQ.track("level_complete", {level: 4});Event limits
Use 1–40-character names starting with a letter and containing only letters, numbers, underscore, period or hyphen. The server accepts at most 100 distinct event-name rows per game/day and applies request rate limits; the wrapper limits SDK messages to 240 per minute. Client reports can be blocked, duplicated or forged and are not authoritative gameplay or financial records.
Dashboard reporting
Choose a game, available reporting window and date range in Analytics. Daily plays are anonymous server page loads, visitors are daily unique visitors, and SDK events are separate counts. Timestamps use your viewing time zone, named beside each timestamp. Existing aggregate reporting buckets retain their source boundaries and cannot be rebinned from daily totals. Missing traffic data is displayed as a gap, never zero. Traffic requires the existing Numbers aggregation job. Visitor totals across days are visitor-days, not deduplicated people. Inspector events never enter live statistics.