Overview
The Trigger For feature allows you to define which Persons or Transactions can activate a Scenario - in other words, which entities the Scenario will run for. This lets you focus your monitoring on specific types of entities or activity, and avoid triggering alerts for irrelevant cases.
Note: “Trigger For” only determines whether a Scenario is triggered by a specific entity. It does not limit the data used inside the Scenario query.
For example, if your Scenario creates an alert for all transactions over €5,000, and you use Trigger For to include the Individual Customers Person Segment and exclude the ATM Withdrawals Transaction Segment, the Scenario will only run for transactions over €5,000 made by individual customers, and will not be triggered by ATM withdrawals - even if they are over €5,000 and made by individuals.
Currently, the "Trigger For" feature is available for Real-time and Post-event Scenarios but not for Periodic Scenarios.
💡 Segments are defined separately. Learn more here.
How It Works
Every Scenario runs in response to an Alerting entity - either a Person or a Transaction - depending on your Scenario setup.
The Trigger For configuration lets you control whether the Scenario should be activated by the entity, based on which Segments it belongs to.
You can define two types of Segment-based filters:
Included Segments: the Scenario only runs if the Entity matches all of these Segments.
Excluded Segments: the Scenario is skipped if the Entity matches any of these Segments.
Included vs Excluded Segments
Included Segments
Use AND logic. The Entity must match all selected Segments to trigger the Scenario.
Example: Only run for Transactions that are both outgoing and ATM withdrawal type.
Excluded Segments
Use OR logic. If the Entity matches any of the selected Segments, the Scenario will be skipped.
Example: Skip the Scenario if the customer is low risk or customer is inactive.
❗️Please note: Included and Excluded Segments use different logic when selecting multiple Segments:
Included = AND - the Entity must match all to trigger the Scenario
Excluded = OR - the Scenario is skipped if the Entity matches any
Combining Included and Excluded Segments
You can use Included and Excluded Segments together to define precise conditions.
💡Segment Exclusion overrides inclusion:If an Entity matches both an Included and an Excluded Segment, the Scenario will not run. This means that even if the Entity meets all Included Segment conditions, it will still be excluded if it matches any Excluded Segment.
For example:
Included Segment: Individual Customers
Excluded Segment: Low Risk Persons
Result:
A transaction made by an individual will not trigger the Scenario if that person is also tagged as low risk.
Person Segments
You can select Person Segments for Scenarios where the alerting entity is either a Person or a Transaction, and the Scenario type is Real-time or Post-event.
For Person as an Alerting entity Scenarios: Selecting a Person Segment in "Trigger For" ensures the Scenario only applies to specific Persons matching the Segment's criteria.
For example, if you are monitoring changes in customer industry, you might want to focus only on Legal Entity Customers. By selecting the corresponding Segment, the Scenario will only run for those customers.
For Transaction as an Alerting entity Scenarios: Selecting a Person Segment in "Trigger For" ensures the Scenario only runs when Transactions are made or received by Persons in the Segment.
For instance, if you want to apply stricter thresholds for Transactions involving high-risk individuals, you can select a Risk-Based Segment, ensuring the Scenario targets only those Transactions.
Transaction Segments
You can select Transaction Segments for Scenarios where the alerting entity is a Transaction, and the Scenario type is Real-time or Post-event.
For example, if you are monitoring transactions exceeding a certain amount, you might apply a risk-based approach by setting different thresholds for Transactions involving high-risk jurisdictions. By selecting a Transaction jurisdiction based Segment, the Scenario will only run for Transactions originating from or sent to high-risk countries, allowing you to apply stricter thresholds to these higher-risk Transactions.