Install, identify, verify
From zero to a stable visitorId in a few minutes.
01 Install
Load the agent from the CDN — no build step, and it defines Prynt globally:
<script src="https://api.pryntid.com/cdn/prynt.umd.js"></script>
To bundle it instead, install the package file (it is not on the npm registry yet):
npm install https://pryntid.com/downloads/prynt-js-1.0.0.tgz
Server SDKs (Node, Python, Go, PHP, Java, Ruby, .NET), mobile SDKs and edge connectors: see SDKs & downloads.
02 Identify a browser
// With the script tag, Prynt is a global. With the package: import Prynt from '@pryntid/js';
const prynt = await Prynt.load({
apiKey: 'pk_live_your_public_key',
endpoint: 'https://api.pryntid.com',
extendedResult: true, // include Smart Signals
});
const result = await prynt.identify({ tag: { action: 'signup' } });
console.log(result.visitorId); // vst_… (stable)
console.log(result.confidence.score); // e.g. 0.985 — computed per request
console.log(result.smartSignals?.bot); // { result: false } 03 Verify on your server
Never trust the browser response alone. Confirm it from your backend with the secret key:
curl "https://api.pryntid.com/v1/events/REQUEST_ID" \ -H "Authorization: Bearer sk_live_your_secret_key"
04 Send your user id (linkedId)
linkedId is your own, stable user or account id. Prynt uses it to connect
devices and accounts, which powers three things:
- Account sharing: the same account on many devices (shared or resold logins).
- Multi-accounting: one device behind many accounts, for example free-trial or bonus
abuse. This is also what
accountsOnDevicecounts at signup. - Account clusters: the identity graph that links accounts, devices and IPs into rings.
The large platforms build their abuse systems on a real account id for the same reason. All of these features need the value to be the same for an account forever. Without it they have nothing to work with, and with the wrong value they give wrong answers.
- Use your database user / account id: the same on every visit, every device and every app.
- Never use a session id, request id, cookie value or random token. These change on every visit, so one person becomes thousands of "accounts" and sharing and multi-account results stop making sense.
- Never send a raw email or phone number. Send the internal id, or a salted hash if that is all you have.
- Anonymous visitors: leave
linkedIdout. Don't send"guest","null"or"undefined".
In the browser, once the user is known:
// After login / signup: your database user id, the same on every visit and every device.
const prynt = await Prynt.load({
apiKey: 'pk_live_your_public_key',
linkedId: String(currentUser.id), // e.g. "84123" or "user_84123"
});
await prynt.identify({ tag: { action: 'login' } });
// Or per call, when the user signs in after the page loaded:
await prynt.identify({ linkedId: String(user.id), tag: { action: 'login' } });
// Anonymous visitors: leave linkedId out. On your server, right after signup, attach the new account to the identification it came from, so the next signup from that device sees it:
// Node (@pryntid/node) — right after you create the account
await prynt.updateEvent(requestId, { linkedId: String(user.id) });
# Python
prynt.update_event(request_id, linked_id=str(user.id))
// Go
_, err = client.UpdateEvent(ctx, requestID, strconv.Itoa(user.ID))
// PHP
$prynt->updateEvent($requestId, (string) $user->id);
// Java
prynt.updateEvent(requestId, String.valueOf(user.getId()));
# Ruby
prynt.update_event(request_id, linked_id: user.id.to_s)
// .NET
await prynt.UpdateEventAsync(requestId, user.Id.ToString());
# Plain HTTP
curl -X PUT "https://api.pryntid.com/v1/events/REQUEST_ID" \
-H "Authorization: Bearer sk_live_your_secret_key" \
-H "Content-Type: application/json" -d '{"linkedId": "84123"}' Wrong vs right:
linkedId: sessionId // ✗ new value every visit: thousands of fake "accounts" linkedId: crypto.randomUUID() // ✗ new value every request linkedId: user.email // ✗ personal data: use the id, or a salted hash linkedId: 'guest' // ✗ placeholder: leave linkedId out instead linkedId: String(user.id) // ✓ stable for the life of the account
Only have an email? Hash it on your server with a secret salt:
// Node — only when you have no internal id. Keep the salt secret and never change it.
import { createHmac } from 'node:crypto';
const linkedId = createHmac('sha256', process.env.LINKED_ID_SALT)
.update(email.trim().toLowerCase())
.digest('hex'); Check your integration. The console shows a status under Install › Send your user id, and the Overview shows a warning when something is wrong. The status is computed from your last 14 days of traffic:
- Not sent: fewer than 0.5 % of identifications carry a
linkedId. - Looks like a session id: three or more
linkedIds per device on average, a new id on most return visits, or 1.5 or more per device where most ids are seen once and never again. - Email / phone: 5 % or more of the values look like an email address or phone number.
Response shape
{
"requestId": "req_…",
"visitorId": "vst_…",
"visitorFound": true,
"confidence": { "score": 0.985, "level": "high" },
"smartSignals": {
"bot": { "result": false },
"incognito": { "result": false },
"vpn": { "result": false },
"tor": { "result": false },
"datacenter": { "result": false },
"residentialProxy": { "result": false },
"ipReputation": { "result": false, "score": 0.0 }
}
} How matching works
The agent collects ~20 entropy signals — canvas, WebGL, audio, fonts, math/FPU, hardware,
timezone and more. Some are hashed on-device (canvas and audio, for example); others, such as the
installed-font list and WebGL parameters, are sent as-is so the server can match them by
similarity. The server fuses them with entropy-weighted scoring and reconciles redundant client
storage (cookie + localStorage + IndexedDB) into a stable visitorId plus a
confidence score. Drift is reconciled on every visit, so a browser update or a partial signal
change is matched back to the same device instead of creating a new identity.
Prynt Control
Decisions, friction steps, clusters and the case queue, on the Control plan:
Prynt Reveal
Know which companies visit your website and act on it: Reveal docs — install guides, CSP & storage, consent & CMPs, webhooks and limits & credits.
Prynt Replay
Session replay with inputs masked twice: install, identify users and companies, replay in your own admin and the API reference.
Prynt Gate
Identity, spoofing detection and blocking for your servers and ports: quick start, agent and bouncer, log sources (Traccar, SIA DC-09, sshd, fail2ban, Stalwart, coturn, Vector, Fluent Bit), the API reference and an example with GPS trackers and an alarm receiver.