View as Markdown

Performance monitoring

In Satori, performance monitoring is built into the same system you use to run experiments and live events, so you don’t need a separate analytics tool to evaluate what you launched.

Satori provides six monitoring surfaces, each suited to a different aspect of your game.

For analysis beyond what the console provides, Satori’s data export integrations send your player and event data to your existing data warehouse.

Session configuration determines how accurately Satori attributes events to players, sessions, and your metric calculations. To understand how to ensure data accuracy, see Understand session management.

How Satori is different #

Monitor game health #

Track active users, installs, session patterns, and revenue at a glance from the Satori Dashboard. These metrics are available from day one with no custom events or configuration required.

Satori Dashboard showing DAU, WAU, MAU, installs, and session metrics

Monitoring connected to operations #

Most analytics setups separate the tool you use to run campaigns from the tool you use to measure them. In Satori, both are part of the same system. Metrics pull from the same player event stream that powers your segments and experiment enrollment, so the numbers you see reflect what your operations actually did.

One metric, used everywhere #

Define a metric once against a player event and it becomes available as a goal or monitor metric in any experiment or live event. No duplicate configuration.

Retention and RoAS filtered by operation and variant #

The retention and RoAS reports can be scoped to players in a specific live event or experiment variant. You can ask “what was D7 retention for players who saw Variant B?” You can achieve this level of attribution directly inside Satori without relying on outside business analytics tools.

Funnel analysis on live analytic data #

Pick any sequence of in-game actions (onboarding steps, purchase flows, live event progressions) and build a funnel to see where players drop off. Set a time limit for any step or for the whole player journey. Results refresh automatically. If a player action is tracked, you can build a funnel around it.