Analytics starts with a question
Analytics means using recorded information to understand an experience and make decisions about it. In a game, that experience could be a hand of cards, an introductory tutorial or returning to the application. The main question is not always “how many people?” Sometimes we ask what happened, where a journey stopped or whether a change helped. I am Kian Paknemat, and these different questions mattered while I worked on Dalo. I built Bunny Circus Analytics for configurable reporting, and Dalo uses it, but choosing an analysis still begins with our question.
Events: what happened?
Event analysis is the simplest starting point. An event is something with a clear definition, such as finishing a tutorial or recording a hand’s result. We can count those occurrences or compare their recorded durations. Grouping helps when we want to know which stage was repeated most often. In Bunny Circus Analytics, game events can feed count, average or sum reports, with filters for the relevant information. Counting endings alone cannot explain why a player continued or stopped; that question needs additional evidence.
Journeys: who reached the next step?
Journey or funnel analysis asks a different question: of the people who started one step, who reached the next? Entering the game, seeing the tutorial and starting a first hand form a particular sequence. Putting three independent counts next to each other does not necessarily create a valid funnel. We need to establish that the same people moved through the same order. Here I am explaining a kind of analysis, rather than promising a ready-made feature in my tool. Bunny Circus Analytics offers flexible event reporting, but its general reporting engine does not replace every sequential analysis or complex journey join.
Retention: who became active again?
Retention asks who became active again. My tool’s dashboard checks returns on specific days one, seven and thirty, based on the first observed event. Days that have not finished should not be read as final results. First observation is also not necessarily the registration day, and information that arrives late can change the result. These definitions are not incidental details: they determine what the number actually says. Comparing two periods requires consistent definitions and observation conditions, so that a numerical difference is not misread.
Performance and choosing the right tool
Performance analysis concerns how smoothly the game runs: slowdowns, memory use or execution time for a particular operation. That question differs from the popularity of a game mode and needs suitable measurements of its own. Device information, when the game sends it, provides useful context, but it does not replace a performance inspection tool. My practical suggestion is to write one question and a possible decision first, then choose the kind of analysis. Explore Bunny Circus Analytics to see the tool used by Dalo. Getting-started guidance is available on GitHub, with contact through Telegram.
