Suspect Score
Suspect Score is an easy way to integrate Smart Signals into your fraud protection work flow. It is a weighted representation of all Smart Signals present in the payload that helps identify suspicious activity.
What is Suspect Score
Suspect Score is a single value representing how many Smart Signals indicative of suspicious or fraudulent activity were triggered for a particular requestId
. Each triggered Smart Signal is represented by a positive integer called a weight. Weights are additive, meaning that the more Smart Signals return a positive value, the higher the final score.
It's part of the Smart Signals payload available in Server API, Webhooks and Sealed Client Results.
Suspect Score Weights
Each Smart Signal has its own weight, contributing to the final score. The weights are currently based on the probability that the selected Smart Signal is triggered on a global scale. Smart Signals that are less likely to be triggered have stronger weights, and vice versa.
Weights might have slightly different values based on the request's originating platform (web, Android and iOS). This is caused by different representation of average traffic for each platform.
N/A in the table below means that the signal is not reflected in the Suspect Score. This might happen for two reasons - either the signal is not available on that particular platform (see our Smart Signals Cheat Sheet page for signal availability) or the signal had low incidence rate and would skew the computation too much (the weight would be extremely high).
Weights Table
Smart Signal | Web/Browser | Android | iOS |
---|---|---|---|
Bot Detection (bot.type == bad ) | 7 | N/A | N/A |
Incognito Detection (incognito ) | 4 | N/A | N/A |
VPN Detection (timezoneMismatch ) | 3 | 4 | 4 |
VPN Detection (publicVPN ) | 4 | 5 | 5 |
VPN Detection (osMismatch ) | N/A | N/A | N/A |
VPN Detection (auxiliaryMobile ) | N/A | 6 | 6 |
Tampering Detection (tampering ) | 8 | N/A | N/A |
Virtual Machine Detection (virtualMachine ) | 14 | N/A | N/A |
Remote Control Tools Detection (remoteControl ) | N/A | N/A | N/A |
Developer Tools Detection (developerTools ) | N/A | N/A | N/A |
Velocity Signals (velocity ) | N/A | N/A | N/A |
Privacy-Focused Settings (privacySettings ) | 6 | N/A | N/A |
IP Blocklist (emailSpam ) | 14 | 12 | 13 |
IP Blocklist (attackSource ) | 13 | 13 | 13 |
Tor Exit Node (tor ) | 14 | 16 | 17 |
Public Proxy (proxy ) | 14 | 12 | 15 |
Android Emulator Detection (emulator ) | N/A | 9 | N/A |
Rooted Device Detection (rootApps ) | N/A | 12 | N/A |
Cloned App Detection (clonedApp ) | N/A | 9 | N/A |
Jailbroken Device Detection (jailbreak ) | N/A | N/A | 10 |
Frida Detection (frida ) | N/A | 14 | N/A |
High-Activity Device (highActivity ) | 6 | 5 | 6 |
How to Use Suspect Score
Suspect Score can be used to flag and review possible suspicious activity. It can be used to quickly integrate Smart Signals into your fraud protection workflow without the need to explore fraud correlations of individual Smart Signals.
"suspectScore": {
"data": {
"result": 0
}
}
"suspectScore": {
"result": 0
}
Custom Weights Configuration
Because Suspect Score values are computed based on statistical analysis over our global data, there might be a lot of cases where individual weights need some tweaks depending on the use case.
As an example, some customers might want to exclude VPN flags from the final Suspect Score computation because a large amount of their visitors use a VPN by default (this is typical in some specific industries).
Our Dashboard has an interface to assign custom weights to each Smart Signal, tailoring the score to precisely match particular scenarios. To configure Suspect Score weights, follow these steps:
- Go to the Dashboard
- Navigate to Smart Signals -> Suspect Score
- Select the correct tab based on the platform for which you would like to configure the weights (Web, iOS SDK or Android SDK)
- Input your preferred weights as integers between 0 and 10000 on the right
- Click on Save Changes
The changes will propagate in a matter of minutes and you will start receiving the Suspect Score based on your custom weights.
Disabling a Weight Completely
Some scenarios like the one mentioned above with the high VPN incidence rate might result in the need to disable a particular Smart Signal. In those cases it's possible to set the weight to zero through a dedicated button in the user interface.
The changes have to be saved at the bottom of the page to propagate.
Restoring Defaults
We will always provide a set of default values based on our internal understanding of Smart Signal incidence rates (the statistical analysis mentioned in a previous section). Individual Suspect Score weights can be restored to those defaults by clicking on the restore default weight value button.
The changes have to be saved at the bottom of the page to propagate.
Updated 14 days ago
Want to know the detail about each individual Smart Signal? Visit our Smart Signals Overview page to get more information.