Operator guideEN

Activity Tag Rules / Detail

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

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 shows

This page is the operator inspection surface for one stored rule. Use it to confirm the exact activity, tag action, condition set, timestamps, recent application history, and the current active-state before you run, edit, or delete the rule.

Main actions

Estimate Impact checks how many users match the saved condition JSON through the estimator. It does not save, run, add tags, or remove tags, and it does not prove equivalent live webhook filtering.
Run Rule calls the placeholder manual-run endpoint for this rule ID. The traced endpoint returns zeroed counters without enumerating users, changing tags, or creating application rows.
Edit opens the edit form for the current rule.
Delete asks for confirmation and then soft-deletes the current stored rule.
Refresh reloads the current rule payload shown on the detail page.
Back to List leaves the detail page and returns to the rule list.

Main states

Loading appears while the current rule is being loaded.
Rule not found appears whenever the detail page has no usable rule value, including a missing record and a failed read response; the page does not distinguish those causes.
Estimated Impact appears only after the operator runs Estimate Impact successfully.
Recent Applications is a read-only relation section for the latest application rows.

Important caveats

Estimate Impact reflects the condition types implemented in the estimator. The live model evaluates a different legacy key set, so estimator output is not a live-application guarantee.
Run Rule currently returns zeroed result counters and performs no mass processing.
Recent Applications is limited to the latest ten rows requested by the page.
The verified Refresh action reloads the current rule payload. It does not explicitly refresh the Recent Applications relation.
Recent Applications is not a complete event audit: condition-failed and missing-user outcomes do not create rows.
The detail screen does not provide a durable operator-action history for Delete or Run. Recent Applications records live tag outcomes only.

Detail page state handling, relation host behavior, read, estimate, placeholder run, delete, and application-history behavior have been traced. No workspace-settings or casino-side semantic dependency was found.

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.

Calculations7 topicsOpen details

Condition display

Logic: Empty condition objects render as `No conditions`., Known condition keys are rendered with operator-facing labels., Amount conditions can render an operator plus euro amount., Unknown condition keys fall back to the raw key and returned value.

Timestamp formatting

Logic: Created, Updated, Deleted, and Recent Applications dates use the same display helper., Missing dates render as `N/A`., Parsed dates render as `yyyy-MM-dd HH:mm:ss`., Parse failures fall back to the raw returned value.

Estimate Impact query

Logic: Estimate Impact loads the saved rule and estimates current matching users from activity history., The source returns matching-user count, sample user IDs, current rule ID, activity ID, and saved conditions., The page displays the matching-user count and at most the first five sample user IDs., Estimate does not update the rule and does not mutate player tags., Estimate output does not prove equivalent live webhook filtering.

Supported Estimate conditions

Logic: Verified source estimate supports transaction status, sequence, amount, payment method, payment provider, withdrawal-without-deposit, country, document-submitted, ID verification, and KYC conditions., Document-submitted and ID verification checks both use document-label presence in the verified estimate logic., KYC verified uses the source's approved/verified/accepted status list., These estimator keys are not the same keys implemented by the live model evaluator.

Run result caveat

Logic: Run Rule sends the current saved rule ID to the source execution flow., The source validates that the selected rule exists and is active., The source returns processed, added, removed, skipped, and error counters, all zero in the traced implementation., It does not enumerate users, mutate tags, or create application rows.

Delete behavior

Logic: Delete requires browser confirmation before the source request is sent., Source delete uses the activity tag rule model's paranoid delete behavior., On success, the page returns the operator to the Activity Tag Rules list.

Recent Applications scope

Logic: Recent Applications requests ten application rows for the current rule., The source orders the rows by newest application first., The detail page hosts the relation, but the verified Refresh button does not explicitly refresh the relation hook., Condition-failed and missing-user outcomes do not create application rows.

Fields11 topicsOpen details

Rule Name

Visible rule name shown as the detail page heading.

Group: header
Data Type: string

Activity

Activity event that must occur before the rule can apply.

Group: rule-information
Data Type: composite
Display: Activity name with activity code in parentheses.

Tag Action

Whether the rule adds or removes the configured tag.

Group: rule-information
Data Type: composite
Enum Values: add, remove
Display: Add: Add chip plus tag name | Remove: Remove chip plus tag name

Description

Optional operator note stored with the rule.

Group: rule-information
Data Type: string
Caveats: The Description block is hidden when the value is empty.

Conditions

Matching criteria currently stored on the backend rule.

Group: conditions
Data Type: json-object
Display: Empty: No conditions | Populated: Human-readable condition labels and values
Caveats: Stored conditions are used by the estimator, but equivalent live evaluation is not proven.

Status

Current active-state of the rule.

Group: status
Data Type: boolean
Display: True: Active success chip | False: Inactive default chip

Priority

Current execution priority of the rule.

Group: status
Data Type: integer
Display: Priority chip in the page header.

Created

Creation timestamp for the rule record.

Group: timestamps
Data Type: datetime
Display Format: yyyy-MM-dd HH:mm:ss
Fallback: Raw value when parsing fails.

Updated

Last update timestamp for the rule record.

Group: timestamps
Data Type: datetime
Display Format: yyyy-MM-dd HH:mm:ss
Fallback: Raw value when parsing fails.

Deleted

Soft-delete timestamp when present.

Group: timestamps
Data Type: datetime
Display Format: yyyy-MM-dd HH:mm:ss
Caveats: The Deleted timestamp block is shown only when the returned rule has a deleted timestamp.

Estimated Impact

Current estimated number of users matching the rule conditions.

Group: estimate
Data Type: object
Display: Matching Users: Users currently matching | Sample Users: First five sample user IDs when present
Caveats: This block appears only after Estimate Impact succeeds., Estimator output is not proof that live events enforce the saved form conditions.

More help

Activity Tag Rules

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

Activity Tag Rules / Create

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

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.

Activity Tag Rules / List

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

Activity Tag Rules / Applications

Read-only recent recorded application rows inside rule detail, including user ID, tag outcome, timestamp, and captured activity payload.

Affiliate Payment Settings / Detail

Detail/edit shell for one saved affiliate payment-setting record.