Monitor unusual changes
Owners and admins can create up to ten enabled monitors per game in Alerts. Choose players, new players, sessions, median session length, errors per user, purchases, resource flow or progression failures. Money metrics use one currency, and resource monitors use one named resource and direction. An optional property scope narrows the data.
After the daily rollup, monitoring compares yesterday with 28 trailing days. At least 14 observed history days are required. The rule removes weekday offsets, uses a median and median absolute deviation with a minimum spread, and compares against your selected confidence threshold. These are statistical heuristics, not guarantees of a problem. Missing observations are not treated as zero.
Monitoring pauses after 90 days or when history is insufficient. Use Keep monitoring to renew. Selected current studio members receive email, or the owner if no recipients are selected. Duplicate job runs do not send duplicate alerts. The anomaly log expires after 180 days. Shared games cannot be monitored by the receiving studio.
Detection does not call AI. Ask Huginn only prefills a question; sending it uses the normal analyst price. MCP list_anomalies and REST /api/v1/data/games/{gameId}/anomalies use standard metered reads. Scoped new-player monitoring is limited to 50,000 registered devices.