Tags allow Kount customers to send custom information with the Kount Control Login Decision. These user-defined text fields are used in Profile or Policy creation. When a Profile or Policy evaluates as true, any associated tags are sent with the API response.
What is Apply No Decision?
When creating a Policy, there is an action that is taken when the conditions evaluate as true. The available actions are Block, Challenge, and Apply No Decision.
When Apply No Decision is chosen as the action for a Policy, and that Policy evaluates as true, it has no affect on the final decision for the Login. However, any Tags that are associated to the Policy will be sent along with the Login API.
This allows Kount customers to send information via the API when certain conditions exist, even when they do not want those decisions to affect the outcome of a Login.
What are some use-cases for tags?
There are various use-cases for tags, many of them dependent on your organization and how you use data from Kount's Login API. The following are examples of how Tags might be used:
- Assigning tags to inform a businesses internal system to know what type of multi-factor auth to use. If the risk is high, the multi-factor might be very secure, whereas if the risk is low, a simple captcha or other method could be employed.
- Assigning a tag to know that a login event was from a certain region.
- Assigning a tag to allows an Ops team to investigate potential high risk IP addresses or IP Organizations.
Creating and Editing a Tag
On the Kount Control Portal, create a new profile or policy. On the Create Profile, or Create Policy page, click the Tags drop-down menu to display all previously created tags:
To add a new tag, begin typing the tag to populate the list. Press Enter (or select New Tag). If the tag already exists, you can select it from the populated list.
NOTE: Tags are restricted to 3-24 characters in length, they cannot include special characters (hypens and underscores are allowed), and you cannot use more than three tags per Policy or Profile.
When a decision is returned via API, all tags associated to the Profile and Policies that evaluated as true will be within the “tags” block:
"matchedToDevice": "Device not found",