A real question in Dalo
While building Dalo, installation counts alone were not enough to guide decisions. I wanted to understand the journey from entering the game to starting and finishing a hand, and which design choices deserved another look. A general chart could not answer every question specific to the game. I am Kian Paknemat, and I built a custom analytics path for that need. It is now introduced as Bunny Circus Analytics, and Dalo uses it. My aim was to find answers relevant to the game, rather than accumulate more numbers.
When a hand’s ending is missing
Imagine that the start of a hand is recorded, but its ending is missing. Before blaming difficulty, we should separate several possibilities: the player may have left, the application may have closed, or the ending event may not have arrived yet. This example illustrates a way of thinking; it does not disclose Dalo’s actual statistics. Good analysis helps me choose a more precise next question. Instead of saying “players are not interested,” I can inspect the definitions of a start and an ending, and the path between them, before testing a small change.
Reports that fit the game
Bunny Circus Analytics includes more than the Unity component that sends information. It also has a self-hosted dashboard where each game can have separate event definitions, required data and reports. For example, I can build a report counting recorded endings or averaging the duration of completed hands. Reports can group and filter the relevant data. That flexibility matters because Dalo’s questions need not match those of a level-based game. The dashboard defines the information contract; the game itself still has to send each event at the right moment.
Data quality before judgment
Delivery is part of report quality too. The Unity client keeps accepted events in a local queue and retries temporary connection problems. However, being queued does not mean that information has reached the server, and the queue has a capacity limit. A small number therefore does not always describe player behavior; the event definition or delivery path may need attention. I keep analytics separate from game rules: a reporting failure should not determine a hand’s result, coins or whether someone can play.
Where to learn more
The tool is designed for a lightweight start and greater control over reports. Self-hosting also makes the project owner responsible for maintenance, backups and care of the data. Dashboard retention is calculated from first observation and specific return days, so the meaning of a metric should be read before drawing conclusions. Visit the Bunny Circus Analytics product page to learn about the tool. Source and getting-started guidance are available on GitHub, and you can visit Telegram for updates or contact. Dalo is my example of using this approach.
