3 ms·
Instead of a script to embed, these firms could provide an API to identify users from the server side. The scripts that captures the profile would be served by
by troels 14y ago
Instead of a script to embed, these firms could provide an API to identify users from the server side. The scripts that captures the profile would be served by the sites themselves rather than from third party services. ... Toast.
Not really. If they share data on the server side, they wouldn't be able to share a cookie - they would have to rely on other means to identify you, such as IP address etc. Not entirely impossible, but not as precise either. And that is spoofable through proxies etc.
- d_j_s 14y agoCookies are only used to track your return on that one particular domain. The matching of browser profiles won't be done on the client side. These scripts will only track you and not receive information.
- troels 14y agoNo, but the identification relies on a cookie placed on the 3rd-party site (leadlander.com). With that domain blocked, there would not longer be a way to identify the user across different sites, which is a key element of this thing working.
- d_j_s 14y agoThat's not correct, you as a user run a snippet of leadlander js code on your web page. This code has no access to the cookies on a leadlander domain. I've worked on a similar tracking snippet/system for http://www.projectcounter.org/ http://www.projectcounter.org/ and this was one of the first things we attempted. If you block the leadlander domain(s) the script will obviously not run and also consequently won't be able to send fingerprint details back.