When visiting a site of a tracker company, e.g. addthis.com, almost the complete sites gets blocked Ghostery detects the tracking urls for normal object like images.
I assume this happens since the pattern for the tracker detection is too broad and matches everything from the domain.
I wonder if it would be possible to detect this smarter, e.g. not detect the 1st party urls if you are on the domain itself.
(otoh, whitelisting the tracker for the specific domain works as well)
-
Hi Alexander,
Thanks for using Ghostery!
Ghostery doesn't block first party trackers. Which browser and version of Ghostery are you using? -
-
-
-
Are you doing this?
![[attempting to open addthis.com]](https://d2r1vs3d9006ap.cloudfront.net/s3_images/969581/addthis_inline.png)
That's not the correct location for their home page. If you try to open it, their server issues a "301 Moved Permanently" redirect to tell your browser it should open www.addthis.com instead.
This can be intercepted if Ghostery is set to Look for and prevent redirection, because *.addthis.com matches a detection pattern for AddThis. [Bugs Version 242]
![[screenshot]](https://d2r1vs3d9006ap.cloudfront.net/s3_images/969582/prevent_inline.png)
However, if you open www.addthis.com directly, some blocking can still occur, but an automatic partial whitelisting gets applied:
![[screenshot; site doesn't appear broken]](https://d2r1vs3d9006ap.cloudfront.net/s3_images/969583/homepage_inline.png?1381352388)
We can make adjustments (e.g. changing the detection patterns and/or adding a "firstPartyUrls" property, which is probably what will happen here).
I believe this issue affects a relatively small number of trackers. Please post URLs for any specific cases you'd like to see investigated.
-
-
I think I can live with whitelisting the company pages with per-domain whitelisting, I think I either have an incorrect ghostery database or I have some setting wrong.
I see a completely blocked page on a few tracker domains when I visit them directly, e.g.
http://www.nanigans.com/
https://www.kissmetrics.com/
http://www.parsely.com/
https://segment.io/
https://chartbeat.com/
https://mixpanel.com/
http://customer.io/
http://www.olark.com/ -
-
Yeah, this is going to be fixed at some point soon. Essentially, we will load the domain only trackers as its own whitelist, if the tracker was .addthis.com we will auto-load firstPartyUrl to be addthis.com or something similar.
This is waiting for the new engine rollout so we can add this. -
Loading Profile...



Twitter,
Facebook, or email.
CHAMP
EMPLOYEE
CHAMP
