In the Trusted Location API, the request response to check whether a device is in a familiar location or not has reliability and match type fields.
The field called reliability displays how confident we are of our trustworthiness result about some location. The possible values are:
In case the user is in a familiar location, the reliability is HIGH when the location is the user's usual places, or if the user visited that location many times.
In case the user isn't in a familiar location, the reliability HIGH indicates that we are confident that we know the user's familiar locations.
|MEDIUM||When the user associated with the given installation is at a familiar location which he often visits.|
|LOW||In case the user is in a familiar location, the reliability is LOW when the location was visited just a few times by the user.|
|NO_DATA||When there is no available information for the installation's location history.|
The match_type field refers to which type of match was utilized to produce a result with a given reliability, using the following rules:
|GPS_ONLY||When we are only able to perform comparisons by GPS sensors.|
|WIFI_SCAN||When we are able to perform comparisons by WiFi sensors, but no matched connected networks were found.|
|WIFI_CONNECTION||When we are able to perform comparisons by WiFi sensors, and matched connected networks were found.|
|WATCHLISTED||When the device is shared by more than one User ID and these users have very distinct frequent locations or the device has been associated with multiple fraud reports from customers.|
|NO_DATA||When we are unable to produce results. In that case, other evidences fields will be zeroed.|
|ALLOWED||When the device has been inserted in the allow list for your app id by querying the Feedback API.|