ae-risk-monitoring
AE Risk Monitoring
Build a closed loop outside AE: query AE read-only, evaluate rules in an external runner, persist deduplication state, deliver through an approved messaging channel, and audit alert quality.
Customer problem and outcome
Use this Skill for game operations managers, risk operators, and data engineers who need fast evidence without relying on AE native alerts. It covers account farms / credential abuse, login or traffic drops, withdrawal activity, and custom game-economy or payment formulas.
Trigger and boundary
Trigger when the user asks to monitor AE/TE event data for account bursts, traffic drops, withdrawals, payment failures, or custom formulas. This Skill may notify operators about risk evidence; it is not a substitute for a transactional fraud engine or human investigation.
Do not use this Skill when:
- The user requires AE native alert tasks or notice configuration.
- The required outcome is real-time transactional blocking, account banning, withdrawal freezing, or another automated enforcement decision.
- Event freshness cannot be measured but the requested rule interprets missing events as a business outage.
- The request is only for historical analysis with no recurring monitoring, deduplication, or delivery requirement; use the appropriate AE analysis workflow instead.
- The project, event, property, identity, currency, status, or destination cannot be verified.