Tagging information

A visitorId alone might not be particularly useful if you are tracking logged in users, preventing account sharing, generating fraudulent user lists, etc. Fingerprint Pro ships with a feature called tags, allowing you to connect information useful to your application to a visitorId.

Imagine you want to prevent users from sharing accounts on your website. You would need to look for accounts associated with more than one visitorId. Assuming users typically use one browser per device (and browse from mobile or desktop devices), any account with 3+ unique visitorIds raises a red flag.

📘

Note

3+ unique visitorIds under a single account, as described above, is not a universal metric for fraud. This is purely an example. Your application may have different needs and metrics for determining fraudulent activity.

The table below lists common use cases and basic implementation using the FingerprintJS tag and webhooks features.

Use Case

Implementation

Account Takeover Prevention - prevent account theft from malicious login attempts

Tag account username with visitorId. Use webhooks to populate a table with accounts and their tagged visitorIds. Require extra security check at login if unfamiliar visitorId.

Account Sharing Prevention - prevent users from sharing accounts

Tag account username with visitorId. Use webhooks to populate a table with accounts and their tagged visitorIds. Flag accounts that exceed a number of visitorIds.

Credit Card Fraud - block users who repeatedly use faulty credit cards

Tag a unique hash associated with visitorId and their credit card. Use webhooks to populate a table with visitorId and tag object. Flag visitors that exceed a number of credit cards.

📘

Tag relevant information

A tag does not need to be a raw username; you may tag any value unique to a user.


Did this page help you?