Page body
What this form does
Use this form to create a new automatic tagging rule. Operators define the rule identity, choose how tags or coupon codes should change, and select the KPI fields that should decide whether a user belongs to the rule target.
Main sections
- rule identity and status flags
- tag add or remove actions
- include and exclude filter tags
- coupon code changes
- selected KPI fields
- dynamic KPI filter controls generated from backend config
What operators should watch closely
- The form does not show every KPI field by default. Operators first choose KPI fields, then the screen renders the relevant controls.
- Dynamic KPI filters can be numeric ranges, date ranges, booleans, or text arrays.
Estimate Impacton this form uses the current unsaved payload and does not require the rule to exist yet.
Known caveats
- The backend-generated KPI config is the source of truth for which filter fields are available.
Played Game Categoriesis still present in the FE form code but hidden from normal operator use on this surface.- Saving a new rule still uses the same backend endpoint as editing; the difference is that the create payload keeps
autoTagRuleIdat0.