Operator guideEN

Auto Tags Manager / Detail

Edit surface for one existing auto-tag rule, using the same dynamic rule builder as create but with a persisted rule payload and ID-backed updates.

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

What this page does

This screen edits one existing auto-tag rule. It loads the current rule payload, loads the current KPI field config, then reuses the same rule-builder page as the create flow so operators can change status flags, priority, tags, coupon codes, selected KPI fields, and dynamic KPI filters.

Main sections

  • persisted rule identity and flags
  • rule priority
  • existing tag add or remove rules
  • include and exclude filter tags
  • coupon code actions
  • selected KPI field list
  • dynamic KPI filter controls built from source config

What operators should watch closely

  • The form first loads the existing rule through the list endpoint using autoTagRuleId.
  • Saving this page still uses the same save flow as create, but the source switches to update mode when autoTagRuleId matches an existing record.
  • Estimate Impact here evaluates the current unsaved edit state, not only the last saved version.
  • Detail loading is not the same as list visibility. A direct detail route can request a rule by ID even when the normal list filters to valid rules.

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 Categories remains hidden in the form and is not a current operator-facing section.
  • If the route ID does not resolve to an existing rule, the verified page can still render the shared form with default values. Do not save that state unless you intentionally want to create a new rule.
More details

Definitions and formulas

Open only the section you need. The relevant section opens automatically when you request help for a specific item on screen.

Calculations14 topicsOpen details

Detail rule load

Detail can open a specific rule by id even when normal list mode filters to valid rules.

Inputs
route rule id, list endpoint detail query
Formula
The detail page calls the list hook with limit 1, page 0, and autoTagRuleId from the route. The source switches the query to id-only lookup when autoTagRuleId is supplied.

Detail initial values

Existing saved rule values become the starting edit draft.

Inputs
loaded rule row, source KPI config
Formula
The form initializes autoTagRuleId from loaded id or autoTagId, then pre-fills ruleName, active, isValid, priority, tags, coupons, selected KPI fields, played game categories, and dynamic config keys from the loaded rule.

Missing rule fallback

A missing rule id can look like a blank create-style form; do not save unless creating a new rule is intended.

Inputs
empty detail load result, shared form defaults
Formula
If no loaded rule row is passed to the shared form, it falls back to autoTagRuleId 0, empty strings/lists, active true, isValid true, and priority 0.

KPI config generation

The fields available in Select KPI Fields come from source KPI summary metadata, not a hardcoded page list.

Inputs
UserKpiSummary raw attributes, source excluded field list
Formula
The source excludes identity and metadata fields, then maps KPI column data types to range, dateRange, text, boolean, or unknown control types.

Selected KPI field order

The filter controls move as operators select fields; this is a page ordering rule, not source priority.

Inputs
available KPI field list, selected KPI field list
Formula
The selector sorts all available KPI fields alphabetically. In the dynamic filter area, selected fields are shown before unselected fields, and later-selected fields are placed earlier among selected controls.

Dynamic config payload

Save and Estimate Impact use the same source-style config keys produced by the visible KPI filters.

Inputs
selected KPI fields, source field type config, visible dynamic filter values
Formula
Range fields write min_ and max_ keys; dateRange fields write mode plus either exact from/to dates or relative-minute period keys; text fields write string arrays; boolean fields write true, false, or an empty Any value; selector fields write selected values.

Save Rule payload

Save Rule persists the full edit draft for the current rule id.

Inputs
loaded rule id, rule information fields, tag and coupon arrays, hidden played-game categories value, selected KPI fields, dynamic config payload
Formula
The page sends autoTagRuleId, ruleName, active, isValid, priority, tag arrays, coupon arrays, playedGameCategories, selectedKpiFields, and config to the shared save flow.

Source update or create

Detail updates are safe only when the rule id resolves to the intended existing rule.

Inputs
detail save payload, existing rule lookup by autoTagRuleId
Formula
The source updates AutoTagsManager when autoTagRuleId resolves to an existing rule; otherwise the same service can create a new rule. After save, the source can sync changed priority to queued jobs in pending, paused, or retrying states, except active force-run jobs that preserve a higher priority.

Priority validation

Use whole numbers from 0 to 100 only.

Inputs
priority value
Formula
The page constrains the input to min 0, max 100, step 1. The source rejects supplied priority values that are not integers from 0 to 100.

Repeatable array inputs

Add tag, remove tag, include tag, exclude tag, coupon code, and text KPI arrays must be entered one value at a time.

Inputs
typed tag or coupon value, existing field array values
Formula
The repeatable field component strips commas from typed input, trims the value when adding, ignores empty values, and does not add a value that is already present in the current array.

Draft impact estimate

The estimate is a confidence check for the current edit draft, not a stored rule run.

Inputs
current unsaved edit payload, source draft estimate flow
Formula
Estimate Impact sends the current unsaved edit payload to the draft estimate flow; the source wraps the request body as a rule, normalizes it as an override rule, and returns an estimated affected-user count without saving the rule.

Users Affected chip

The chip shows the latest estimate in the current browser session.

Inputs
estimate response count
Formula
The page reads count from response data, queue data, or root response count, converts it to a number, and shows Users Affected only after a successful estimate.

Detail navigation

Leaving manually always goes to the list; successful save follows browser history.

Inputs
Back to List click, Save Rule success
Formula
Back to List routes directly to /auto-tags-manager. Save success calls browser back after the source request succeeds.

Save button in-flight state

Treat toast result and navigation as the reliable save confirmation.

Inputs
form submit state, async save wrapper
Formula
The button label can switch to Saving through form submit state, but the verified submit wrapper does not return the async save promise as a durable in-flight lock.
Fields34 topicsOpen details

Loading...

Plain loading text shown until the existing rule request is no longer loading and KPI config is available.

Group
page-state
Data Type
loading-state
Editable
false
Caveats
The verified page logs KPI config failure but does not render a dedicated operator-facing config-load error alert.

Edit Auto Tags Rule

Identifies that this form edits an existing automatic tag rule.

Group
page-header
Data Type
text
Editable
false

Rule ID

Existing rule identifier used by the shared save endpoint to update instead of create.

Group
rule-information
Data Type
integer
Editable
false
Caveats
If no existing rule data is loaded, the shared form can fall back to autoTagRuleId 0 and behave like create mode on save.

Rule Information

Groups the rule identity, priority, and status flags.

Group
rule-information
Data Type
section
Editable
false

Rule Name

Human-readable name for the persisted rule.

Group
rule-information
Data Type
string
Editable
true

Priority

Numeric priority used to order rules and sync queued jobs ahead of lower-priority work.

Group
rule-information
Data Type
integer
Editable
true
Allowed Range
Min: 0 | Max: 100 | Step: 1

Active

Controls whether the rule can be executed from the list.

Group
rule-information
Data Type
boolean
Editable
true

Is Valid

Controls whether the rule is treated as valid for manager list and run workflows.

Group
rule-information
Data Type
boolean
Editable
true

Tags

Groups tag changes applied when a user matches the rule.

Group
tag-actions
Data Type
section
Editable
false

Add Tags

Tags to add when the rule matches a user.

Group
tag-actions
Data Type
string-list
Editable
true
Caveats
Values are added one at a time; commas are stripped and duplicate values are ignored by the field component.

Remove Tags

Tags to remove when the rule matches a user.

Group
tag-actions
Data Type
string-list
Editable
true
Caveats
Values are added one at a time; commas are stripped and duplicate values are ignored by the field component.

Filter Tags

Groups tag-based audience filters used before rule actions are applied.

Group
filter-tags
Data Type
section
Editable
false

How Filter Tags Work

Explains that include tags narrow the audience first and exclude tags remove users from that audience.

Group
filter-tags
Data Type
helper-copy
Editable
false

Include Tags

Rule will only apply to users who have at least one listed include tag.

Group
filter-tags
Data Type
string-list
Editable
true
Caveats
Values are added one at a time; commas are stripped and duplicate values are ignored by the field component.

Exclude Tags

Users with any listed exclude tag are ignored by the rule.

Group
filter-tags
Data Type
string-list
Editable
true
Caveats
Values are added one at a time; commas are stripped and duplicate values are ignored by the field component.

Coupon Codes

Groups coupon-code changes applied when a user matches the rule.

Group
coupon-actions
Data Type
section
Editable
false

Add Coupon Codes

Coupon codes that should be assigned to matched users.

Group
coupon-actions
Data Type
string-list
Editable
true
Caveats
Values are added one at a time; commas are stripped and duplicate values are ignored by the field component.

Remove Coupon Codes

Coupon codes that should be removed from matched users.

Group
coupon-actions
Data Type
string-list
Editable
true
Caveats
Values are added one at a time; commas are stripped and duplicate values are ignored by the field component.

Played Game Categories

Hidden field retained in the form payload model but not visible to normal operators on the detail surface.

Group
hidden-game-categories
Data Type
string-list
Editable
false
Caveats
The field is inside a hidden section in the verified edit form.

Choose Which KPI Fields to Filter On

Explains that the operator must choose KPI fields before matching dynamic filters appear.

Group
kpi-selection
Data Type
section
Editable
false

Select KPI Fields

Chooses which backend-generated KPI fields should become active filters on this rule.

Group
kpi-selection
Data Type
string-list
Editable
true
Caveats
Available options are generated from backend KPI summary fields and sorted alphabetically by the frontend.

User KPI Filters

Contains controls rendered only for the selected KPI fields.

Group
kpi-selection
Data Type
section
Editable
false

User KPI Filters

Persisted KPI filter payload stored for the rule.

Group
kpi-selection
Data Type
json-object
Editable
true
Caveats
Field types come from backend-generated config, not from a hardcoded frontend list.

Min / Max KPI filters

Numeric KPI filters where operators can set lower and upper bounds.

Group
kpi-selection
Data Type
numeric-range
Editable
true

Specific Dates / Relative Period

Date KPI filters that can use exact dates or relative minute windows.

Group
kpi-selection
Data Type
structured-date-range
Editable
true

Country, Currency, Top Game, Top Provider, Language

Special multi-select controls shown only when those KPI fields are selected.

Group
kpi-selection
Data Type
selector-list
Editable
true

Text KPI filters

Text KPI filters rendered as repeatable string arrays.

Group
kpi-selection
Data Type
string-list
Editable
true
Caveats
Values are added one at a time; commas are stripped and duplicate values are ignored by the field component.

Any / True / False

Boolean KPI filters where empty means Any, otherwise True or False.

Group
kpi-selection
Data Type
boolean-filter
Editable
true

Back to List

Leaves the detail form and returns to the manager list without saving.

Group
action-bar
Data Type
action
Editable
true

Users Affected

Shows the latest successful estimate count for the current unsaved edit draft.

Group
action-bar
Data Type
estimate-result
Editable
false

Estimate Impact

Runs a backend estimate for the current unsaved edit draft without saving it.

Group
action-bar
Data Type
action
Editable
true

Estimating...

Button text shown while the draft estimate request is running.

Group
action-bar
Data Type
loading-state
Editable
false

Save Rule

Persists updates to the existing auto-tag rule when the rule id resolves.

Group
action-bar
Data Type
action
Editable
true

Saving...

Button text intended for the form submitting state.

Group
action-bar
Data Type
loading-state
Editable
false
Caveats
The verified submit wrapper does not return the async save promise, so operators should rely on toast result and navigation rather than this label as a durable in-flight lock.
More help

Related pages

Auto Tags Manager

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

Auto Tags Manager / Create

Full rule-builder for a new automatic tagging rule, including priority, tag actions, coupon actions, KPI field selection, and draft impact estimation.

Auto Tags Manager / List

Rule inventory with search, direct navigation to create or reorder, row-level run controls, and job history or recovery actions.

Auto Tags Manager / Order

Manual drag-and-drop ordering screen for valid auto-tag rules, with a single save action that rewrites sort positions.

Activity Tag Rules / Detail

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

Activity Tag Rules / Edit

Edit flow for one stored rule or an existing grouped add/remove pair, including grouped form rebuild, condition testing, and update-only save behavior.