A customer opens your site on a phone, installs the app, then returns on a laptop to finish comparing. Your web SDK counts one visitor. Your native SDK counts another. A cleared cookie or an in-app browser adds a third. A stable visitor id web and mobile does not come from a cleverer fingerprint: it comes from your own identifier, passed on purpose between the two SDKs.
Fingerprints are device-level by design. A phone and a laptop share almost no attributes, so nothing in a fingerprint makes them the same person, and that limit is useful because it keeps the device signal honest. Cross-device identity has to come from the system that already knows it: your accounts.
Why one person looks like three visitors
Each surface mints its own identifier for reasons that have nothing to do with your customer. Web gets a cookie or stored value, cleared by browser settings, incognito, or the in-app browser a social app opens on your behalf. Native gets a per-install identifier from the operating system that resets on reinstall. Your backend has the account record, already stable and already yours.
The identifier that should win is the one you mint server-side. Prynt Identify keeps a device-level visitorId for device and network signals; your own ID is what rolls those device records up to one person. Our device fingerprinting page covers how that device layer is built.
Keep three layers separate: your user ID (stable, never derived from a device), the device visitorId (one per browser profile or app install), and a link table mapping userId to visitorId with a timestamp and a merge source. The relationship is many-to-one, one person to several devices. Model it that way from day one.
Pass the identifier from both SDKs
The pattern is the same on web and native. The SDK keeps its own visitorId; you tell it which account the device belongs to.

on login or signup:
userId = accounts.id // server-minted, not from the device
deviceId = sdk.currentVisitorId // web or native
link(userId, deviceId, source: "login")
Parameter names differ between the web and native SDKs, so check the docs instead of guessing. Two habits matter more than the syntax:
- Link at the first authenticated action. Login, signup, password reset, checkout. Wait for the purchase and you lose the entire evaluation window.
- Link, never overwrite. Keep earlier devices attached. Someone who upgrades a phone is the same person with a new device.
The anonymous window before login
Before authentication there is no account to link, so you rely on device-level signals: fingerprint, network, behavior. Treat that window as probabilistic in your reporting, and merge the anonymous record into the account at login instead of starting a fresh history. Our accuracy page explains what those signals can and cannot support.
Edge cases that break a naive merge
Reinstall and device upgrades
An uninstall wipes the local store and the operating system issues a new install identifier. Your account ID does not change, which is why the account, not the install, is the anchor.
One phone, two accounts
Shared family devices and reseller logins are normal. Link devices to accounts many-to-many and let the session, not the device, decide which account is active now. Device-level risk stays attached to the device while accounts change.
One person, several business accounts
B2B products need two identifiers: the person and the tenant. Prynt Replay accepts identify(userId, { accountId }), so sessions can be listed inside your own admin per company or per user. Send both from the first event.
Guests who convert
A guest checkout followed by account creation should reuse the existing visitor record rather than fork it. Merge on conversion and keep the pre-login events in the same history.
Use one identity in decisions, not just dashboards
Once devices roll up to one person, controls stop leaking. A signup blocked on web and retried in the app is the same human. A bonus claimed from a second device is the same bonus. A paywall meter counted per device and per account does not reset in an incognito window. Prynt Control answers allow, step-up or block per use case with a reason code, and your code makes the final call. Analysis gains too: funnels that survive a channel switch, session lists that show phone and laptop together, native mobile replay tied to the same user.

Keep the merge auditable
Write a merge log with the source that triggered each link, and make merges reversible. Send a keyed hash instead of a raw identifier where you can, document the purpose, and keep the consent record next to the link. Months later someone will ask why two records became one, and the log is the answer.
FAQ

Does a reinstall create a new visitor?
At the device level, yes: the local store is gone and the operating system issues a new install identifier. At the account level, no: the next authenticated session links the new device to the same user ID, and the history stays with the person.
Can a fingerprint match web and mobile on its own?
No. A fingerprint describes a device and its environment, and a phone and a laptop differ in nearly every attribute. Fingerprints are strong within one device across visits and weak across devices by design. Use them for the anonymous window and use your account ID for the cross-device link.
Should we send the raw user ID to the SDK?
Send what the linking decision needs. If the raw value is not required for reporting, send a keyed hash and keep the mapping in your own database, where you control retention and access.
One identity, two SDKs
If you already run an account system, you are one integration away from a single view of each visitor. Start with Prynt Identify on the free plan, 5,000 identifications a month and no card, then pass your user ID from the web and native SDKs and watch the duplicates collapse. Create your account at pryntid.com.
Try it free
Prynt is device intelligence with a free plan: 5,000 identifications a month, visitor IDs with confidence and bot detection — no credit card. Upgrade to Pro for VPN, proxy, tampering and behavioral signals.