Operator guideENtagsautomationactivityrules

Activity Tag Rules

Operator documentation for activity-driven tag automation rules, including list, create, edit, detail inspection, and recent application history.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

What this module is for

Use Activity Tag Rules to automate player tag changes after a tracked activity happens in CRM. Operators come here to define what activity should trigger the rule, which tag should be added or removed, and which conditions should narrow the affected users.

Main surfaces

  • Activity Tag Rules / List is the operational inventory for all saved rules.
  • Activity Tag Rules / Create is the create flow, including clone-from-existing behavior.
  • Activity Tag Rules / Edit is the grouped editor that can update one or two backend rules from one screen.
  • Activity Tag Rules / Detail is the inspection surface with estimate, run, and delete actions.
  • Activity Tag Rules / Applications is the recent audit trail shown inside the detail page.

What operators need to know first

  • The list groups paired backend rules into one visible row when the FE decides they belong together. One visible row can represent both an Add rule and a Remove rule.
  • The create and edit screens can save either one backend rule or two backend rules depending on whether Add Tag, Remove Tag, or both sections are enabled.
  • Conditions are available only for the transaction activity codes currently hard-coded in FE: FAILED_WITHDRAWAL, SUCCESS_WITHDRAWAL, SUCCESS_DEPOSIT, and FAILED_DEPOSIT.
  • Estimate Impact is backed by SQL over user_activities and users. Run Rule is routed through a backend execution endpoint, but the current verified service does not prove a full batch mutation loop for all matched users.

Backend verification summary

The verified ownership for this module is in gs-admin-backend:

  • GET /api/admin/activity-tag-rules
  • POST /api/admin/activity-tag-rules
  • GET /api/admin/activity-tag-rules/:ruleId
  • PUT /api/admin/activity-tag-rules/:ruleId
  • DELETE /api/admin/activity-tag-rules/:ruleId
  • POST /api/admin/activity-tag-rules/test
  • POST /api/admin/activity-tag-rules/:ruleId/estimate
  • POST /api/admin/activity-tag-rules/:ruleId/run
  • GET /api/admin/activity-tag-rules/:ruleId/applications
  • GET /api/admin/activities

Supporting condition-option data also uses GET|POST /api/admin/payment-methods/crud through the shared payment-method hook.

No gs-casino-backend ownership was required for the currently verified operator surfaces.

Important caveats

  • The backend stores these rules in auto_tag_rules, even though the FE and operator-facing UI use the wording Activity Tag Rules.
  • The verified estimate query supports only the condition set implemented in buildActivityEstimateQuery. If an FE field exists but is not in that query, operators should not assume estimate coverage.
  • The detail page shows only the latest applications requested by FE, not an unlimited full-history screen.
Related references

Related pages

pageActivity Tag Rules / Create

Create flow for a new activity tag rule, including optional clone-from-existing behavior and condition testing.

pageActivity Tag Rules / Detail

Rule inspection page with backend identity, conditions, timestamps, impact estimate, run action, delete action, and recent application history.

pageActivity Tag Rules / Edit

Edit flow for one backend rule or a grouped add and remove pair, including split or merge behavior and condition testing.

pageActivity Tag Rules / List

Main inventory for activity-driven tag rules, with search, activity and status filters, grouped rows, clone, edit, and run actions.

pageActivity Tag Rules / Applications

Recent application history shown inside the detail page for one rule, including action performed, timestamp, and captured activity data.

pageAuto Tags Manager

Operator documentation for automatic tag rules, including list monitoring, create or edit, queued job control, and manual rule ordering.