COOKIELESS DEVICE INTELLIGENCE

Device identity for the post-cookie web.

A stable visitor ID that survives cookie clearing, incognito, and storage wipes — returned from one API call, with a confidence score your fraud, growth, and security teams can build on.

● POST /v1/identify 200 OK
// identifying you…

live response · reload in incognito and we'll still recognize you

WHY THIS EXISTS

Half your stack was built on cookies. The other half is about to break.

Safari blocks third-party cookies. Chrome is following. Privacy regulation is tightening every quarter. Users clear browser state on instinct. The result: your fraud rules miss repeat offenders, your attribution undercounts, your account recovery flows trust devices they shouldn't.

You don't need another cookie. You need a way to recognize the device underneath.

RISK Repeat fraudsters look like new users.

A bad actor clears cookies, switches browsers, or spins up a fresh incognito window. Your rules engine sees a new visitor. Your chargeback team sees the same name three weeks later.

GROWTH Attribution drops the second a cookie does.

Safari ITP, iOS ATT, ad blockers, GDPR consent banners. By the time a user converts, the signal that brought them in is gone. You're flying blind on spend.

SECURITY "Trust this device" stops working when state gets wiped.

Step-up auth, device recognition, and recovery flows all assume the browser remembers something. Increasingly, it doesn't.

WHAT IT DOES

Stable device evidence for real product decisions

Fingerprint.dev returns a visitor_id and confidence score from a hosted API. Use it for abuse controls, account security, fraud review, support workflows, and analytics joins where cookies are too brittle.

visitor_550e 92%
requests
4
first seen
12:00
last seen
12:15

WHO IT'S FOR

Three teams. One identifier. Different workflows.

01 Recognize visitors

Get a stable visitor ID and confidence score from each identify request.

02 Apply it to workflows

Use visitor evidence for advertising, fraud detection, verification, and more.

03 Stay cookieless

Use hashed evidence and origin allowlists without storing browser state.

04 Pay by usage

Start free, then scale identify requests on a hosted plan.

Make the first call

import { identify } from "fingerprint.dev";

let result = await identify({
  apiKey: "fp_live_...",
});

console.log(result.visitor_id, result.confidence);

The JavaScript SDK sends hashed browser evidence when available. The hosted API combines it with request evidence and returns a result your product can decide on.

See the full identify flow.

READY?

Watch us identify you. Then identify your users.

Free tier includes 1,000 identify requests a month. No credit card. Five-minute setup. If you can write a fetch call, you can ship this today.