Tags are small bits of information that agents can add to alerts, cases, rules, entities, instruments, and events (transactions/actions).
Tags are key:value pairs such as `sector:europe`, `priority:l1`, `user-type:beta`, `type:fraud`.
Tags can be used in any way you want; to triage alerts, to use in rule (model) logic, to categorize cases, to search entities and more.
Tags are complimentary to custom data; however, tags can be added anytime in the dashboard, unlike custom data.
Tags cannot be deleted!
Tags for Alerts and Cases
Tags can be used to dispose, detail, and filter alerts and cases.
For example, if your organization assigned severity, tier or priority levels to your cases, you may elect to use the tags: `severity:0`, `severity:1`, `severity:2`.
This is a great way to escalate cases between agents on the same team.
Tags for Entities and Instruments
Tags can be used to further detail entities and instruments.
For example, your organization my elect to use KYC tools and determine that an entity is on an FBI watchlist. While there is no immediate action to be taken since this entity has not been flagged by Unit21; the tag: `kyc:watch` is appropriately added to the entity to quickly identify it in the future.
Tags for Events
Tags can be used to further identify events.
For example, a bank that wants to label the way checks are deposited can use the tags: `type:in-app`, `type:in-person`, `type:atm` when sending transactional information to Unit21. This information can be useful if the check is ever investigated in a fraud case.
Tags for Rules (Models)
Tags can be used in rules/models to filter objects.
For example, if you create a model to flag abusive users on your platform, you may elect to remove beta testers or elite users from this rule. A good way to do this is to use the tag: `user-type.` Then, when creating your model, you can filter out beta and elite users by filtering out the tags `user-type:beta` and `user-type:vip`.
Tags for SARs
A handy feature of tags is that they can be used to autofill the Narrative section of a SAR report.
If a case that has a templated tag, that tag’s template autofills when you turn the case into a SAR. This saves time when you have to file similar SARs from multiple transactions─just tag them all, configure the tag from Configuration > Tags, and write the template only once.
There is a Tag limit of 1000 per organization.
There is a tag limit per organization of 1000 tags. If you reach the limit in a synchronous operation, you will see an error message.