Visitor identification
Website visitor identification.Recognize return visits.
Cleared cookies and changed IPs can make returning visitors look new. ShieldLabs recognizes them and links visits to risk context, helping you stop repeat abuse and restore familiar experiences.
5eb7-fd5ce812-b603203.0.113.42Recognize returning visitors
Recognize return visits through cleared cookies, incognito browsing and IP changes.
Detect linked users
Connect account activity even when users register under different email addresses.
Reveal account abuse
Get ready-made account abuse and fraud detections with the identification’s risk result.
Welcome trusted visitors
Bring back a familiar experience with recognized identity and the risk context behind each visit.
Persistent visitor identity
Different browser sessions.
The same returning visitor.
A new browser session brings different storage and connection details. ShieldLabs reconnects recognized activity so your product keeps the visit history and account context that matter.
8f3a-2e7cOne persistent identity
Keep a consistent Visitor ID across sessions, cleared cookies, incognito mode and IP changes, preserving the history of return visits.
Identify before sign-in
Understand anonymous traffic from the first visit. No login, name or email address is needed to recognize a browser.
Separate identity references
Receive Visitor ID, Device ID and session identifiers for different parts of the visit.
Web and mobile
Run identification in modern web browsers on desktop, mobile and tablet.
Linked users and high-risk events
Detect linked accounts.
Uncover abuse.
ShieldLabs detects linked users and account abuse around registered accounts. Help protect introductory offers, paid access and customer accounts with ready-made detections.
High-risk events detected
Multi-accounting
Detect linked accounts behind repeated signups, trial abuse and promotional redemptions.
Account sharing
Identify one account used across multiple devices, sessions and different locations.
Account takeover
Receive ready-made account takeover detections to protect sensitive sign-ins.
Impossible travel
Detect conflicting location activity across the identified visits associated with an account.
Analytics dashboard
Follow returning visitors.
Investigate linked users.
Find recognized returning visitors, linked users and detected account abuse. Get ready-made risk assessments and traffic quality results for the sources bringing visitors to your product.
How it works
Start recognizing your visitors.
Connect your product to recognize return visits and receive ready-made risk detections.
- 01
Add the snippet or SDK
Connect your product and start identifying visitors and users.
- 02
Recognize returning visitors
Receive visitor and device identifiers, linked users and ready-made risk results.
- 03
Welcome genuine users
Bring back a familiar experience while protecting your product from abuse.
Developers
Integrate in
5 minutes.
A single API to identify, detect and score. Receive risk data through API responses and webhooks. Integrate selected data points into your business logic to prevent fraud and abuse.
Start identifying your traffic
Start recognizing
your returning visitors.
Start with 5,000 free identifications and see your visitors’ linked user and device activity.
FAQ
Understand the identity
behind a visit.
What is visitor identification?
Anonymous visitor identification recognizes browser visits and repeat activity without revealing a person’s name or email. Registered-user identification associates activity with accounts supplied by your product.
How does ShieldLabs identification help prevent fraud?
ShieldLabs identifies visitors and registered users, detects multi-accounting and other account abuse, and returns named risk signals and identification risk assessments.
How accurate are ShieldLabs identification and risk signals?
ShieldLabs provides 99.9% identification accuracy and 99.9% risk signal detection accuracy.
How does identification connect with bot detection and traffic analytics?
The identified visit carries identity and account context alongside its risk score, detected signals and traffic attribution. Bot and AI-client context helps explain the activity, while risk analytics aggregates scored traffic by source, channel and campaign and lets you follow linked accounts.
Can ShieldLabs keep the Visitor ID after cookies are cleared?
Yes. When recognized device evidence connects the visit to an existing identity, ShieldLabs restores the existing Visitor ID instead of treating the new cookie as a new visitor.
What is the difference between visitors and users?
Visitor identification connects browser activity. A user is an account in your product. Pass the registered account identifier when a user signs in to connect that account with its visits and related activity.
How does the identity graph support entity linking?
The identity graph links recognized browser visitors and devices with account identifiers supplied by your product. This form of identity resolution helps detect multi-accounting across registered users without revealing an anonymous person’s name or email.
Does identification reveal someone’s name or email address?
Account names and email addresses come from your product. ShieldLabs provides the identity and connections around browser activity; it does not recover a person’s name or email address from an anonymous visit.
How do I receive identification results?
The browser snippet collects evidence. Your backend receives identification IDs and context through webhooks or the Server API, where you can use the results in your signup, sign-in and returning-visitor workflows.
Can visitor identification improve guest checkout?
Yes. Recognize a returning browser visit before login and receive its current risk assessment. Your store can use recognized identity to retrieve the saved experience while keeping guest checkout open to genuine buyers.