Segments enable you to define specific Person and Transaction Segments that can be used in Screening and Monitoring configurations.
For example, in Screening, you can skip screening terminated Persons or screen SEPA Transactions agains certain List Groups in Screening Flows, to focus your screening efforts where they are most needed.
In Monitoring, you can make sure that Scenarios only Trigger for certain Segments of Persons and Transactions, e.g. Scenario only running when an ATM Transaction is made.
Creating Segments: A Step-by-Step Guide
To set up a Segment in Salv, follow these steps:
Navigate to Segments Configuration:
Go to Admin > Segments
Click on New Segment.
Define the Segment:
Choose whether the Segment is for a Person or a Transaction.
Name your Segment.
Define the Segment rule using JMESPath query language, a powerful tool that allows you to create complex queries based on the data attributes available.
Save Your Segment:
Once you have configured the Segment, click Save.
Note that while editing Segments is not currently supported, you can create as many Segments as you need to accommodate different scenarios.
The data available for creating Segment rules
For Transactions:
All transaction attributes data
Query templates
For Persons:
Person ID and type
All person attributes data, including nested data fields
Person’s status (e.g., TERMINATED_AND_REPORTED)
Query templates
Person tag (a tag is given to a Person when a Screening Alert is marked with a final true positive status; possible tags:
PEP,SANCTION,ADVERSE_MEDIA,ADVERSE_MEDIA_ENTITY,CUSTOM_SCREENING_LIST)If Risk product is used,
personFinalRisk(includes Risk overrides)
Segment recalculation
A Segment is recalculated and refreshed to ensure it remains up to date whenever certain actions occur. There are two types of Segment calculation:
Full Calculation → All Entities are calculated. All full calculation events are shown in the calculation log.
Single Calculation → Individual Entity is calculated. Only failed single calculation events are shown in the calculation log.
Both types have different events that trigger the calculation:
Full Calculation triggers:
Creating a Segment
Adding or updating a Query Template
NB! Custom list updates do not trigger calculation.
Full Calculation manually triggered
Single Calculation triggers:
Entity created or updated (Person or Transaction)
Person status updated
Change in Person tag
Change in Person Risk level (including Risk override)
Failing Segments
A Segment can fail in two scenarios:
The Segment rule is faulty
The rule itself contains errors or references missing data fields
The Entity is faulty
The uploaded entity does not match the expected data structure
Example:
Rule:
tokenize(person.country)If a Person entity lacks the
countryfield, this rule will breakResult: The Person entity is not uploaded, but other correctly formatted entities will not be affected
Some expressions, like
tokenize(person.company_activity), fail when the field is missing. Others, likeperson.company_activity, do not fail even if the field is absent. Due to the complexity of rule evaluation, there is no exhaustive documentation covering all potential failure conditions.
A failing Segment does not block Entity upload (or any other single calculation events) if the Segment is not used in any active Feature (Screening Flows, Automatic Re-screening, Live Scenarios). Entity upload (or any other single calculation events) is only blocked if the failing Segment is used in an active configuration.
What happens when an Entity is uploaded and some of its Segments fail but others don't?
All Segments are calculated.
Failed Segments are checked whether they are used by an active Feature. If yes then there is an error.
Non-failing Segments are applied to the Entity.
Accessing and managing Segments
Each Segment has its own dedicated page, which you can access by clicking on the Segment in the list. On the Segment page, you can:
Edit the Segment: currently, you can only modify the name of the Segment.
View a sample of Entity IDs: the Segment page provides a sample of the IDs of Persons or Transactions that match the Segment rule. This allows you to verify that the Segment is functioning as expected.
View Calculation Log: the log shows all Full Calculation events (both successful and failed), failed Single Calculations, and calculation checkpoints (the checkpoint event is generated after every 100k Entities have been calculated). Read more about calculations below.
Archive the Segment: if a Segment is no longer needed, you can archive it directly from this page.
Recalculate the Segment: you can manually trigger a recalculation.
Default Segments
Salv provides Default Segments that are automatically created for you and can be used in both Screening and Monitoring configurations. These Segments are designed to save you time and simplify setup by giving you a ready-made foundation for grouping Persons and Transactions.
Important: Filling Out Query Templates
Some Default Segments have Query templates in their logic, which act as placeholders for required information. These Query templates must be filled out by you for the Segment to work as intended.
For example:
CUSTOMERS_FROM_HIGH_RISK_COUNTRY is a default Segment that uses a Query template called
high_risk_countries. To make this Segment meaningful and operational, you need to provide ISO country codes (e.g.,RU,IR) for the countries you consider high risk in the associated Query template. Without this input, the Segment won’t function properly in your Monitoring or Screening configurations.
💡 When Using a Default Segment:
Check if the Default Segment you’re using has an associated Query template:
Look for
query_template_as_listfollowed by the Query template's name in the Segment's rule.
Add the necessary details to the Query template. For example, specify high-risk countries, currencies, transaction types, or other required information.