Page body
What this page does
This screen edits one existing auto-tag rule. It loads the current rule payload, then reuses the same rule-builder UI as the create flow so operators can change status flags, tags, coupon codes, selected KPI fields, and dynamic KPI filters.
Main sections
- persisted rule identity and flags
- existing tag add or remove rules
- include and exclude filter tags
- coupon code actions
- selected KPI field list
- dynamic KPI filter controls built from backend config
What operators should watch closely
- The form first loads the existing rule through the list endpoint using
autoTagRuleId. - Saving this page still posts to the same save route as create, but the backend switches to update mode when
autoTagRuleIdmatches an existing record. Estimate Impacthere evaluates the current unsaved edit state, not only the last saved version.
Known caveats
- There is no separately verified delete or archive action on this surface.
- If a rule is inactive or invalid after edit, the list screen will still show it as non-runnable even though the save succeeded.
Played Game Categoriesremains hidden in the FE form and is not a current operator-facing section.