Analytics for GitLab.com: Discussion
Overview
TL;DR: How should we solve our analytics problem on GitLab.com? What factors should we consider when integrating an analytics tool, and which products should we consider?
Due to the nature of on-premise software and GitLab's approach on privacy for our customers, we receive no insightful data back from most customers aside from low-fidelity, opt-out usage statistics. As a result, it's a challenge for us to learn about how users actually use GitLab.
If we add stronger analytics to GitLab.com, however, we might be able to get some solid insights on some key questions we have. Tools to consider might be analytics products like Mixpanel, Amplitude, Heap, KeenIO, and tons more (it's a crowded space!).
I'd love to move forward with a solution and/or open up discussions with vendors on the week of 2018-03-12.
Open questions for feedback
-
If all of the data on GitLab.com was made available to you, what types of questions would you be curious to answer with it?
-
Are there any features or characteristics of an analytics tool that are particularly valuable to you?
-
Are there specific analytics tools you've experienced in the past? Any feedback or concerns to share?