@tsteur opened this Issue on December 24th 2020 Member

Use case:

Someone downloads a page from your website and stores it locally. Then the user opens it and the user will be tracked and the URL might look like


This way we actually track personal data potentially by accident without knowing.

  • We would always exclude page urls with this protocol by default
  • There should be a method to opt out of this feature so you can track these requests if needed.
  • We create an FAQ to document this behaviour / feature.

As this could be seen as a BC break we need to maybe wait for Matomo 5 for this and/or clearly announce this and warn users of this change.

@tsteur commented on March 19th 2021 Member

see https://developer.matomo.org/guides/jstracker-core this would need to be changed in js/piwik.js see how to embed tracking code https://developer.matomo.org/guides/tracking-javascript-guide

@tsteur commented on May 10th 2022 Member

This would be a great new privacy feature which be quick to implement 👍

@peterhashair commented on October 4th 2022 Contributor

@tsteur just found we have something similar, but not the same. Do we consider removing that one?

@tsteur commented on October 4th 2022 Member

@peterhashair we would keep it to not break the API as some people might use this

@peterhashair commented on November 4th 2022 Contributor
@sgiehl commented on November 7th 2022 Member

@peterhashair the new method should also be added here: https://developer.matomo.org/api-reference/tracking-javascript
But as this will be included in Matomo 5 only, we maybe should first start the documentation for 5.x. See https://github.com/matomo-org/developer-documentation/issues/675

@peterhashair commented on November 7th 2022 Contributor

@sgiehl should I wait for the 5.x documentation created? Or should I created PR follow those steps https://github.com/matomo-org/developer-documentation/#how-to-add-docs-for-a-new-matomo-version

@sgiehl commented on November 8th 2022 Member
@justinvelluppillai commented on November 24th 2022 Member

Looks like this is ready now @peterhashair @sgiehl - 5.x-dev documentation is now live.

@peterhashair commented on November 24th 2022 Contributor

@justinvelluppillai added updates.

Powered by GitHub Issue Mirror