Analysis settings
1. Feature overview
On the Analysis Settings page, you can specify the core events used to automatically obtain related metrics on the Engage workbench, and configure the Frequently Used Metrics used to analyze operation performance.
2. Specify core events
Specify which of your events serve as the New User Event, Active Event, and Top-up Event. After the configuration succeeds, the built-in metrics related to activity, new users, and payment in Key operation metrics become available, and you can use them to monitor daily operational data such as activity and payment.
After you click Edit, the settings become editable, and you can configure the corresponding events for the New User Event, Active Event, and Top-up Event.
- Custom events are not supported
- Event property filters are supported (custom properties and dimension table properties are not supported yet)
| Core event | Description |
|---|---|
| New User Event | Select the event that represents new users to observe metrics such as new players and day-1 payment rate of new players. A common choice is character creation (or registration) |
| Active Event | Select the event that represents player activity to observe metrics such as Active Players and active payment rate. A common choice is user login |
| Top-up Event | Select the event that represents a successful top-up to observe metrics such as Paying Players and Payment Rate. A common choice is the payment event |
3. Add frequently used metrics
Starting from V4.3, you can set performance metrics in operation tasks to measure players' metric data within a period after they are reached, which helps you evaluate how players perform after being reached.
You can add operation performance metrics in two ways: customize them in the task, or set them as frequently used metrics and then select them directly. In the Metrics settings of an operation task, performance metrics are added separately for three stages, Push Succeeded, Delivered, and Clicked, by clicking + Metrics for each.
On the Frequently Used Metrics page, click Create metric to open the metric creation page. You only need to define the metric's calculation logic and statistical window to create a frequently used metric. The Attrib. Window specifies the time range after the trigger within which behavioral data is counted. For example, you can count players' payments within 12 hours after a successful push.
Defining operation performance metrics with a custom formula is not supported yet.