Open jmcmurry opened 8 years ago
Also: see what can be done via google analytics first
@cmungall @kltm just a gentle nudge that you were going to compare technologies for this release so that we can implement for Christmas. Any insights yet, perchance?
Implicit in this is that we first investigate and leverage all that Google Analytics can offer.
Drop-in Google Analytics works great for things like page transitions, but is quite weak on things like clicks and exits. They do allow more invasive tracking, but that requires essentially tying tracking codes to every button and link.
Separately, especially since you offer an API, you'll need to have server-level tracking to see what kinds of data is being grabbed, either by directly link-in or other API (GA can only help on pages and interfaces where JS runs).
Also, and I think I brought this up before, some people who are looking for rare diseases might not be wild about their every click being tracked. One might want to consider opt-out, and a clear message to that end (a la a lot of EU sites and EU tracking policies).
If one is going a more GA route, it might be worth considering the very nice Piwik (https://piwik.org/), which offers customization, keeping your data private, and is OSS.
I have had no chance to do this, and not really an area I have much experience in
On 19 Nov 2015, at 7:00, Julie McMurry wrote:
@cmungall @kltm just a gentle nudge that you were going to compare technologies for this release so that we can implement for Christmas. Any insights yet, perchance?
Reply to this email directly or view it on GitHub: https://github.com/monarch-initiative/monarch-app/issues/1014#issuecomment-158082025