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
JS tracker should not track anything when the protocol is file:// to avoid tracking personal data by accident #17017
Comments
see https://developer.matomo.org/guides/jstracker-core this would need to be changed in |
This would be a great new privacy feature which be quick to implement 👍 |
@peterhashair we would keep it to not break the API as some people might use this |
Add documents here. https://matomo.org/?post_type=faq&p=59435&preview=true |
@peterhashair the new method should also be added here: https://developer.matomo.org/api-reference/tracking-javascript |
@sgiehl should I wait for the |
Let's wait till matomo-org/developer-documentation#675 is done |
Looks like this is ready now @peterhashair @sgiehl - 5.x-dev documentation is now live. |
@justinvelluppillai added updates. |
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/strange-item-in-analytics/53432/2 |
And what about tracking in Electron based application ? UI is often served with file:// protocol. It the case of my application. The solution explained here https://fr.matomo.org/faq/how-to/enable-file-protocol-tracking/ is not really a good solution. Is there another solution? |
@manufitoussiwit Guess that depends a bit how you have integrated Matomo into that application. If you use the TagManager it would be easy to add an additional call like this. Otherwise I think there might only be the possibility to adjust the tracker file yourself to enable file tracking. |
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.
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.
The text was updated successfully, but these errors were encountered: