Open GoogleCodeExporter opened 9 years ago
Seems reasonable. Do you have a list of some common ones that you've come
across already?
Original comment by j...@google.com
on 7 Feb 2014 at 10:58
Yes, a few that look common that I just came accross:
googleads.g.doubleclick.net
ad.doubleclick.net
3814442.fls.doubleclick.net
pixel.quantserve.com
Perhaps consolidating the first three to *.doubleclick.net would be OK.
I will try to come up with more
Original comment by osch...@we-amp.com
on 7 Feb 2014 at 11:10
I wonder if you could get a list of potential tracking filters from
organizations that block ad domains. I'm not sure that all of them use the
pixel method, but it's probably not advisable to optimize javascript or images
used for tracking (especially since it can be used for installation
verification.)
With lazy loading enabled, requests for the tracking image weren't occurring
until I scrolled down to the bottom of the webpage. Partial hostnames that I
recently came across are:
*.c-col.com
ad.doubleclick.net
pixel.quantserve.com
*.doubleclick.net (ie, googleads.g.doubleclick.net)
Ghostery claims to profile and cull over 1,800 trackers and 2,100 tracking
patterns.
https://www.ghostery.com/features
This service has identified 2,518 ad server hostnames that it uses to create a
hostfile to block ad servers.
http://pgl.yoyo.org/adservers/
Original comment by youthpas...@gmail.com
on 7 Feb 2014 at 11:17
One other thing we should probably do is block lazyload for images whose area
on the page is given as 1px or less in the html. A lot of these tracking
images include image size in the markup.
Original comment by jmaes...@google.com
on 8 Feb 2014 at 9:33
Original issue reported on code.google.com by
osch...@we-amp.com
on 7 Feb 2014 at 10:55