## Summary The only Service Usage Data usage tracking we receive is via our Service Ping, which currently only sends aggregate metrics (for the most part, there are a some (~ dozen) data points which are identifiers like UUID, instance version, etc.). From a product perspective, we'd like to get more granular insight into behavior at the user, namespace and project levels. By implementing event tracking (like Snowplow in SaaS), we'd be able to conduct SM to SaaS comparisons at this level. ## Iteration Opportunities 1. [ ] MVC 1. [ ] Deploy Snowplow toggle to SM instances (separate from Service Ping) 1. [ ] Instrument the Snowplow toggle, create adoption dashboard 1. [ ] Measure participation of event-based tracking, generate awareness 1. _MAYBE_ Create adoption offers (like [Registration Features](https://about.gitlab.com/releases/2021/07/22/gitlab-14-1-released/#registration-features)) 1. [ ] Unify event-based tracking with Service Ping toggle (would require transparent notice to the community)