Insights & player activity
Notice the change · Know what to review
Connect player retention monitoring with casino KPI alerts. Define returning-player activity, compare a suitable baseline and keep the affected cohort and next investigation with the signal.
AskDataInsightsPlayer activity / Returning players
Where should I look when returning-player activity changes?
Return fell from 44% to 38% compared with last week. Open the affected player groups and review the movement.
In AskData
The notification leads to a specific review with the context needed to act.
The starting point
New-player growth hides weaker return activity when both groups sit inside one total. A useful signal separates the returning group and carries the comparison into the review.
Insights brings the returning-player movement into view. Analytics connects it with the affected groups and their activity. Aggregate business monitoring sits alongside the operator’s individual player-protection procedures.
What this enables
The analysis workflow
Specify the qualifying event, prior activity condition, brand scope and observation window. Use the same rule for current and comparison periods.
Account for weekday patterns and cohort maturity. Keep population size and the activity rate visible together.
Verify freshness, missing sources and changes in event definitions. Decide how repeated movements should be grouped into a single review.
Include the metric, period and group, then give the reviewer a route to the relevant analytical view and a way to record the next step.
Connect the records
Write the rule as a small working record rather than a threshold without context.
| Rule component | What to specify | Why it matters |
|---|---|---|
| Metric and group | Activity event, prior condition, exclusions and identity scope. | A stable meaning of “returning” across periods. |
| Comparison | Baseline, observation window and cohort maturity. | A fair reading of changes in activity. |
| Data quality | Freshness, completeness and definition checks. | A missing feed does not become a misleading business alert. |
| Review route | Recipient, related analysis and record of follow-up. | The notification has a useful operational destination. |
After implementation
Track whether the rule produces useful reviews. Revisit a rule that repeatedly produces irrelevant or incomplete notifications.
| Measure | How to check it |
|---|---|
| Time to review | Time from complete data becoming available to the signal and the first relevant review. |
| Review usefulness | The share of signals that lead to a recorded analytical finding or justified next step. |
| Data-related noise | Signals explained by delayed records, definition changes or incomplete feeds. |
Tell us about your casino and the decisions you want to understand.