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
Feature/Make client-side analytics configurable #76
Feature/Make client-side analytics configurable #76
Conversation
543b91a
to
7f6cce2
Compare
c6b5174
to
e4fd74e
Compare
To tell the truth, I embedded the hard-coded tracking ID for knowing how many people are using doccano. Through Google Analytics, I can know the number and it motivated me a lot: But I can understand what you say. This feature is useful for people who want to set their own ID. Hmmm... Is there any way to know how many users using doccano but at the same time the user can set their own ID? |
No problem. I really appreciate your help. |
Wow, great to see the usage. In any case, even after this merge, the tracking ID still defaults to yours; the user actively must set the environment variable to an empty string to remove the tracking (like |
The doccano application currently contains Google Analytics with a hard-coded tracking ID. This means that every deployment of doccano will send analytics to the same account. In order to support new deployments of doccano bringing their own analytics, this change makes the Google Analytics tracking ID configurable via a setting.
Additionally, the Google Analytics Javascript will now only be included in the page if the tracking ID is present which means that deployments can also opt-out of Google Analytics altogether.
For users who're looking for an alternative to Google Analytics, this change also adds an option to use Azure Application Insights for client-side monitoring.