Overview

Daily players

Players who opened the game that day, and how many were new

Levels played per day

Clears and crashes

How far players get

% of players who start each level, out of everyone who started level 1

What stands out

Worked out from the numbers on this page

    Retention curve

    % of new players who come back on day 1, 3, 7, 14 and 30

    How this is counted

    The game sends no player ID. Each device keeps two counters in its own save: the day it first played and how many sessions it has had. A cohort is everyone whose first day is the same. "Day 7" counts devices from that cohort that opened the game exactly 7 days later. A player on two devices counts twice; clearing browser data looks like a new player. Cells show "–" until enough days have passed.

    Cohorts

    One row per first-play day. Darker blue = more players came back.

    Progression funnel

    % of players who reach each level · vertical lines mark new worlds

    Clear rate by level

    Clears ÷ (clears + crashes) for every attempt

    Where players crash

    Crashes by how far into the level they happened · darker = more crashes · click a row for detail

    Every level

    Click a column to sort · click a row for detail · ⚠ marks levels where fewer than 55% of attempts clear

    Coins earned per day

    From levels and daily rewards

    Coins spent per day

    Store purchases

    Purchases by category

    Items bought with coins

    Most wanted, can't afford

    Times a player tried to buy an item without enough coins

    Store items

    Click a column to sort

    Platform

    Sessions

    Device

    Sessions

    Screen orientation

    Sessions

    Country

    Sessions · top 12

    Language

    Sessions · top 12

    Session length

    Sessions

    Info pages opened

    How to play, Privacy, Terms, Credits

    Notes

    Country comes from Cloudflare's network lookup; the IP address itself is never stored. Language and orientation come from the player's browser at the start of each session.

    Game errors

    JavaScript errors reported by players' devices, grouped

    Game versions

    Sessions by version

    Event volume

    Everything received in this period

    Latest events

    The newest 200 events received

    Connect your stats server

    Saved in this browser only

    Setup checklist

    1. Create a D1 database and a Worker in Cloudflare (steps in the README).
    2. Set the Worker secret ADMIN_TOKEN to a long random string.
    3. In the game file, set ANALYTICS.url to your Worker's /e address and republish.
    4. Host this admin page behind Cloudflare Access so only you can open it.
    5. Connect here with the Worker URL and the token.

    What the game sends

    Event dictionary · every event also carries platform, device, game version, first-play day, session number and days since first play