Hacker News Reader

Comment by cddotdotslash | Hacker News Reader

Do you have a contingency plan if your script/domains start getting blocked by the very AdBlockers they're trying to track? For example, Google Analytics is already blocked by a number of plugins (Ghostery, uBlock, Disconnect, etc.)

View on HN

I hope that doesn't happen because Adblock Analytics is 100% cookieless and doesn't track visitors via any method, we're only interested if ads were displayed or not, but we do have some ideas if it does happen.

I just hope more people start running with NoScript and then all this nonsense is meaningless anyway:)

I'm actually just running a script blocker in default deny now - running an adblocker as well doesn't seem to be necessary.

If cookieless, how do you accurately aggregate/assign pageviews per visitor?

Browser fingerprinting is one possible way.

https://panopticlick.eff.org/

[edit: clarified that this is a solution, I have no knowledge as to whether that is what is done.]

Do you actually know that fingerprinting is used or is just an assumption?

They seem to only be collecting screen resolution, viewport size and whether ads are showing client side (tested by trying to load a file called ads.js that inserts a div into the dom). I assume server-side they combine this with user agent string and ip address.

Screen resolution & viewport size aren't being used. They were added many months ago when we first started development.

So you're just doing UA + IP? Seems like that would be plenty for your use case.

you hope?

This is one of the reasons why you can't get perfect stats if you use GA events to track it, which many articles on the internet suggest.

The only way is to have the complete tracking implementation on your server.

Reply on news.ycombinator.com