I find customserver useless if I can't identify the clients somehow.

[robertbaldwin]

I have a license for custom servers, but I cannot identify the client browser and correlate it with the fingerprint ... json file. I tried with localstorage where I see that some variables are saved (clientId, FingerPrintSwitcherLastTimePosted, FP)Can you tell me which script to use in the browser to correlate with the json data? A kind of browser identifier.

[sergerdn]

We don't have such functionality at the moment. You're not the first person to ask about it. I believe we need the UUID of the client's visit to generate it on a visitor landing page and include it in a fingerprint to correlate who this person is.

If we have the UUID, you can do anything you want on your side.

[robertbaldwin]

I wish not to be misinterpreted. Congratulations for these tools. You have some great tools like (perfectcanvas) and UUID would be a great plus. Until then, I will try to identify with hardware Concurrency, screen.availWidth, etc

[morpheus93]

Maybe it's possible to distinguish/mark the particular users with a script like fingerprint.js (https://github.com/fingerprintjs/fingerprintjs or as node-module https://www.npmjs.com/package/@fingerprintjs/fingerprintjs?activeTab=readme). Used it in the past and worked well.

Nowadays they try to sell their overpriced "Pro" version (https://fingerprint.com/) but the free one from github should be enough.

Their are other similar scripts out there for such an approach.

[robertbaldwin]

@morpheus93
Thanks for the idea, but maybe I'm wrong somehow, but every time it gives me a different VISITOR ID with FingerprintJS (I import from custom servers). Here I made a javascript to take part of the browser data + visitor Id FingerprintJS

https://customfingerprints.bablosoft.com/admin/database
Windows, Firefox, v115 - 5 July 1, 2023 01:52:46

"navigator.userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0","screen.availHeight":1019,"screen.availWidth":1707,"screen.colorDepth":24,"screen.pixelDepth":24"screen.availLeft":0,"screen.availTop":0,"outerHeight":1019,"outerWidth":1707,"hardwareConcurrency":16,"maxTouchPoints":0,"window.devicePixelRatio":1.5;Google Inc. (Intel);ANGLE (Intel, Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)
6771291a182c4902880397ffdf3d5fa5

"navigator.userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0","screen.availHeight":1019,"screen.availWidth":1707,"screen.colorDepth":24,"screen.pixelDepth":24"screen.availLeft":0,"screen.availTop":0,"outerHeight":1019,"outerWidth":1707,"hardwareConcurrency":16,"maxTouchPoints":0,"window.devicePixelRatio":1.5;Google Inc. (Intel);ANGLE (Intel, Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)
575eef40ab4ef178b9e226ead89c79a1

"navigator.userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0","screen.availHeight":1019,"screen.availWidth":1707,"screen.colorDepth":24,"screen.pixelDepth":24"screen.availLeft":0,"screen.availTop":0,"outerHeight":1019,"outerWidth":1707,"hardwareConcurrency":16,"maxTouchPoints":0,"window.devicePixelRatio":1.5;Google Inc. (Intel);ANGLE (Intel, Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)
7195a542c943f25a546c0c6bf7459523

"navigator.userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0","screen.availHeight":1019,"screen.availWidth":1707,"screen.colorDepth":24,"screen.pixelDepth":24"screen.availLeft":0,"screen.availTop":0,"outerHeight":1019,"outerWidth":1707,"hardwareConcurrency":16,"maxTouchPoints":0,"window.devicePixelRatio":1.5;Google Inc. (Intel);ANGLE (Intel, Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)
929d2bb026eca0bed50a57418f4206f2

[morpheus93]

@robertbaldwin Strange behaviour. Maybe the developers of the fingerprint.js changed something in their code. In general it should work. You can try a different version from their github or the npm module.
Maybe their is some relevant information in the documentation. It's a while ago I used it.