Page body
What this module is for
Use Auto Tags Manager to define automatic segmentation rules for CRM users. Operators come here to create a rule, choose which KPI fields should be checked, decide which tags or coupon codes should be added or removed, and control the execution queue when a rule is already running.
Main surfaces
Auto Tags Manager / Listis the operational inventory for existing rules and job status.Auto Tags Manager / Createis the full rule-builder for a new rule.Auto Tags Manager / Detailis the edit workspace for an existing rule.Auto Tags Manager / Reorderchanges the execution or display order of valid rules.
What operators need to know first
- This module is action-heavy. A rule can be saved, estimated, executed, cancelled, restarted, and reordered.
- The create and detail screens use the same backend save endpoint. The difference is whether
autoTagRuleIdis0for a new rule or a real rule ID for an update. - KPI filters are not hardcoded in FE. The backend generates the available field list from
UserKpiSummary, and the form renders only the KPI fields the operator selected. - Job controls on the list screen act on the execution queue, not on the rule definition itself.
Key workflow rules
Create or edit a rule
- Operators choose the rule name, active and valid flags, tag changes, coupon code changes, and the KPI fields that should be used as filters.
- After selecting KPI fields, the screen renders matching controls such as numeric ranges, date ranges, booleans, and text arrays.
- Country, currency, language, top game, and top provider filters use selector controls when those KPI fields are selected.
Estimate before run
Estimate impactcan be executed from the list or directly from the create or detail form.- The estimate does not persist rule changes when the operator is still editing a draft payload.
- Estimate results are intended for operator confidence checks before queuing a real run.
Run and control jobs
Runqueues a real execution job for the selected rule.Cancel jobandRestart jobtarget a specific job record, not the rule definition.- If another active job blocks the rule, the backend rejects the action and returns an explicit message.
Reorder
- Reorder saves one full ordered list of valid rules.
- The backend normalizes the submitted order and rewrites
sortfor every valid rule in the payload.
Backend verification summary
The current verified backend ownership is gs-admin-backend:
GET /api/admin/auto-tag-manager-listGET /api/admin/auto-tag-manager-configPOST /api/admin/save-auto-tag-managerPOST /api/admin/run-tag-rulePOST /api/admin/run-tag-rule/estimatePOST /api/admin/run-tag-rule/estimate-previewGET /api/admin/auto-tag-manager-jobsPOST /api/admin/auto-tag-manager-jobs/:jobId/cancelPOST /api/admin/auto-tag-manager-jobs/:jobId/restartPUT /api/admin/order-auto-tag-manager
No separate gs-casino-backend ownership was verified for the current operator surfaces. Queue execution is still routed through gs-admin-backend casino services and app/utils/tagManager.js.