Skip to content
kumo

Insights

Insights is in the wiki’s menu, beside People. It is where the studio’s numbers live: production, the stores, marketing and the game itself.

A dashboard is a page of charts the studio builds for itself, from any of its sources:

  • The board: production flow, velocity and cumulative flow are the first dashboard.
  • Builds and QA: builds, bugs and crashes.
  • The stores: Steam sales and wishlists, App Store sales, Google Play installs and sales, read from the stores’ own reports with the studio’s keys.
  • Marketing: how each post did, read back from where it was sent. See Marketing.
  • Your game’s events, below.
  • Anything else an automation fetches: an API that needs a key goes through an automation, so the key never sits in a dashboard.

A chart can be a formula over others, or join two sources.

The game sends its events to the studio’s own server with one key per project. Each engine has a sender: an Unreal plugin, a Unity package and a Godot addon, or your own calls to the Game events API. Events are stored for analysis at scale, and Insights reads them as counts, cohorts, ranges and spots on a level map.

The same key carries reports from the in-game reporter and crashes, so bugs and analytics come from the same build.

Change a value in the live game without a new build. Each key has rules, taken in order: which builds, which platforms, and what share of players. A player’s place in a share is fixed per player and per key, so the same player sees the same value every time.

The engine plugins ask at launch and every 15 minutes, release builds included, and keep the last answer on disk. Every change is kept in a history, and producers and leads may make them.