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 four monitoring surfaces (the Dashboard, Retention report, RoAS report, and custom metrics), 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.
Key capabilities #
| Track player retention out of the box | The Retention report shows what percentage of players return on Days 1 through 30, filterable by country, platform, game version, and player cohort. |
| Measure any player behavior you care about | Create custom metrics tied to any player event and track them across experiments, feature flags, and live events. |
| Scope retention to a specific operation | Filter the Retention report to players in a specific live event or experiment variant to see whether that operation affected long-term engagement. |
| Measure return on ad spend by cohort | The RoAS report combines CPI from your MMP integration with LTV data from Satori to show acquisition spend recovery per player cohort, filterable by channel, campaign, country, and experiment variant. |
| Reuse metrics across all operations | Define a metric once and apply it as a goal or monitor metric across experiments, feature flags, and live events. |
| Export to your data warehouse | Send player and event data to BigQuery, Snowflake, Redshift, S3, or Databricks for deeper analysis in your existing BI tools. |
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.
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.
