4 ms·

I only really see three solutions: One is creating a service that uses a sdk that works into whatever webserver you are using and then slightly alters your htm

I only really see three solutions: One is creating a service that uses a sdk that works into whatever webserver you are using and then slightly alters your html to input different detection methods. That would make it impossible to block or possible to detect a block. (index.html was loaded, but .js was not) Allowing a tracker to be served from a subdomain. This way it is not thirdparty and should be okay. Analytics over websockets. --- But it will not be easy and will probably be a weapons race with adblockers. The problem is really only with thirdparty trackers, that when have data across multiple sites can make a much deeper profile about you than a single site can make without you allowing it. So if we can convince everybody about that, that would be great!

herbst 11y ago
I was going to write about how one could fix this with CNAME'ing the tracker/ad services and beeing able to choose custom file names. AFAIK most blockers just block requests based on patterns and not actually look at the DOM (sure some do, but those are paranoid fuckers anyway). You are right that the profile it creates can be scary, and honestly i block everything i can. I just happen to think about the business side as well. Remember when we tracked with images? I dont even remember why, but in the early days all we did was a 1x1 image. Piwik even still supports tracking images, i dont know how good the data can get that way tho.