Limiter
Enabled rulesets block abusive identify traffic automatically; pass ruleset_id on Events GET for inline evaluation in your backend.
Visitor identificationIdentify returning
Identify returning
visitors.
Cookieless visitor identification and browser fingerprinting that recognize returning visitors across VPNs, incognito, and cleared storage. Slim SDK in the browser; authoritative smart signals on your server. originId is not a unique-human identifier; gate sensitive actions on confidence plus account.
Identify session
Production key · visitor intelligence
@digitalfingerprintjs/clientslim responseserver enrich
POST https://api.digitalfingerprintjs.com/api/identify → originId oid_7f3c…a91e → eventId evt_2k8m…p4wq GET https://api.digitalfingerprintjs.com/api/events/evt_2k8m…p4wq → vpndetected→ botclear→ score42medium
Fraud fields server-side only · 5-minute event window · Events API authoritative
Quick start
Install via official CDN or npm i @digitalfingerprintjs/client, then init with a public API key (platform-managed integrity via hostname allowlist). Never put a secret server key or signingSecret in the page.
<script src="https://cdn.digitalfingerprintjs.com/v1/originid.global.js" crossorigin="anonymous"></script>Integration
Ship in minutes, not months
Official CDN or npm in minutes. Production keys return a slim response; your backend fetches smart signals and suspect scores via the Events API.
Industries
Trusted across regulated and high-growth verticals
From fintech and marketplaces to SaaS, gaming, healthcare, and beyond, teams use DigitalFingerprint for visitor identification wherever identity drives risk, revenue, or trust — including fraud prevention, analytics, and returning-visitor recognition.
FintechE-commerce & retailMarketplacesSaaS & subscriptionsGamingEdTechHealthcareTravel & hospitalityMedia & publishingInsuranceCrypto & Web3B2B & enterprise
≥99%
same-browser returning visitor identification (control/test methodology, n=500)
50/50
incognito reloads, one Origin ID on live production
Real devices
iPhone Safari & Android Chrome on AWS Device Farm (production apex)
Production benchmark 2026-07-02, desktop Selenium, AWS Device Farm mobile, and incognito continuity on live apex.
Platform
Visitor identification that holds up under pressure
Cookieless browser fingerprinting in, enriched intelligence out. Fraud logic stays server-side and authoritative so you can identify returning visitors with confidence.
VPN & proxy resilient
Browser fingerprinting keeps visitor identification stable when IPs change. Server-side enrichment adds confidence beyond network signals alone.
Smart Signals
Bot detection, tampering, incognito, velocity, and IP intelligence — computed server-side on every identify call.
Drop-in SDK
npm or script tag. One init call returns a persistent visitor ID (originId); fraud fields stay on your server.
Suspect score
Every enriched event includes confidence, match level, and fraud-oriented scoring your rules can act on.
Account linking
Pass linkedId at identify time and use account-link at signup to surface duplicate-account abuse before it scales.
How it works
Three steps to persistent identity
Step 1
Install DigitalFingerprint
Add via npm or script tag on your origin.
Step 2
Collect signals
95+ canvas, WebGL, audio, hardware, and storage probes in-browser.
Step 3
Enrich server-side
Your API returns a slim SDK payload; fetch fraud fields via Events.
server.ts
// Authoritative enrichment: never trust browser fraud fields
const res = await fetch(
`https://api.digitalfingerprintjs.com/api/events/${eventId}`,
{ headers: { Authorization: `Bearer ${API_KEY}` } }
);
const { smartSignals, suspectScore, riskLevel } = await res.json();