Filter the fingerprint after harvesting

[bebetter]

Hello everyone
After harvesting the Fingerprint with Perfect Canvas, how to remove FP that comes from bots and filter only FP from real devices?
Thank you!

[simplyx]

@bebetter
When gathering:

• If you use custom servers, do some filtering on your own site. Either with analytic tools (example: Yandex Metrica) or traffic checker (DataDome/Integral Ad Science/Clickease etc.)
• Use good combination of tags, not just "Chrome". Set minimum browser version etc.

After gathering:

• Load fingerprint, test on sites like https://bot.incolumitas.com/, https://abrahamjuliot.github.io/creepjs/ or https://amiunique.org/fp and check for anomalies. Ignore everything which is validated through Canvas Fingerprint, as you don't use Perfect Canvas Fingerprint for that specific site. A Windows Chrome fingerprint with navigator.hardwareConcurrency < 4 and deviceMemory < 4 is probably a virtual machine, so you can delete that fingerprint. You can also parse the fingerprint.json file and check it offline with BAS. Shouldn't be hard to automate. If you don't use custom servers, this process shouldn't be required. Pretty sure a filter that checks the authenticity of the user is applied before obtaining the fingerprint (if some mod can confirm).

[morpheus93]

@Fox "Pretty sure a filter that checks the authenticity of the user is applied before obtaining the fingerprint (if some mod can confirm)."

Maybe you can give us some information about the filtering and selection that is applied to fingerprints from the FPS-API? Thank you.