Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ghostery for Chrome 8.4.7 fails to recognize Matomo Tracker in some websites while recogninizing it in others #513

Closed
luisAtMonday opened this issue Mar 19, 2020 · 2 comments

Comments

@luisAtMonday
Copy link

@luisAtMonday luisAtMonday commented Mar 19, 2020

Description

I'm one of the web developers working on these 3 sites, all for the same client:

https://www.dieversicherer.de/versicherer
https://gdv.de/de
https://en.gdv.de/

All of these sites have Matomo-Tracking built in, with the expected script in the head of each site:

<script type="text/javascript" async defer src="//analytic.gdv.de/matomo.js"></script>

Expected Behavior

Ghostery recognizes the "matomo.js" in the script source and blockes the Tracker on all sites

Actual Behavior

The Tracker is only being blocked on dieversicherer.de
On the other 2 sites the Tracker isn't being recongnized.

Steps to Reproduce

  1. Go to each of the sites

Versions

  • Browser: Google Chrome Version 80.0.3987.132
  • OS: Mac OS 10.14.6
  • Node: 6.9.2
  • NPM: 3.10.9
@ghost
Copy link

@ghost ghost commented Mar 21, 2020

For me, it caught the one in the first website. However, I can confirm that nothing is shown on the other ones.

@christophertino
Copy link
Member

@christophertino christophertino commented Mar 27, 2020

This is because Ghostery considers analytic.gdv.de/matomo.js to be first party on https://gdv.de/de and https://en.gdv.de/. By default Ghostery blocks third-party tracking. You can enable first-party blocking in Settings > General Settings > uncheck "Allow trackers created by site owners".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants