When a transaction monitoring rule is triggered, Flagright creates an alert. Alert grouping controls how those hits are bundled: whether related hits roll up into one alert or split into several. You set this per rule, in the rule's alert configuration step. It doesn't change whether the rule hits, only how the hits are grouped into alerts.
The four grouping options
Single alert for all counterparties:All hits for the rule are grouped into one alert, regardless of counterparty or payment instrument. Best when you want one consolidated alert to review.
Separate alert for each counterparty: One alert per counterparty. A single transaction between a sender and receiver can create more than one alert (one per side). Best when each counterparty needs its own investigation.
Separate alert for each payment identifier: One alert per payment identifier (e.g. per card, account, or wallet). Best when the payment instrument is what you're investigating.
Separate alert for each counterparty user ID: One alert per sender/receiver user ID pair. Payment identifier and counterparty name are ignored. Best for monitoring flows between your own users, one alert per user-to-user relationship.
How the user ID pair option works
This is the newest option, so it's worth a closer look. A few things to know:
Alerts are grouped by the origin and destination user IDs only. Payment identifier and name are ignored.
Direction matters: transactions from user A to user B are grouped separately from user B to user A.
New transactions with the same user pair are added to the existing open alert, rather than creating a duplicate.
If a transaction is missing a user ID on one side, all such transactions are grouped together into one alert.
See it for yourself
The easiest way to understand the difference is to test it:
Create a simple rule that always hits (e.g. transaction amount greater than 0).
Set its grouping option to "Separate alert for each counterparty user ID" and activate it.
Send four transactions: two from A to B, one from B to A, and one from A to C.
You should get three alerts: one for A to B (holding both transactions), one for B to A, and one for A to C. Open the A to B alert and confirm both A-to-B transactions are grouped inside it.