## Current navigation adoption metrics (during beta) We could not do the heavier DB query or time based tracking that would be required to have this ship. Based on having only 3 months to hit our 16.0 release, we are using two alternate methods instead: **As an interim for our PI updates we are using the following to see beta adoption** - Sisense: [Clicks on the toggle in many views](https://app.periscopedata.com/app/gitlab/1130331/PDI1111:-Tracking-New-Navigation-Toggle-(Sass)) - Issue: https://gitlab.com/gitlab-data/product-analytics/-/issues/1111 - Querying the DB in this [spreadsheet](https://docs.google.com/spreadsheets/d/1itgWwpDAP20WVUqylogyfSjxT34kS_96DLnxlqBAFJE/edit#gid=740586793) for total on/off/null - Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/407163 ## In development Right now a DBT model is being created that will allow us to track our metrics in Sisense. - 5/5 - A [Sisense table](https://app.periscopedata.com/app/gitlab/1130331/PDI1111:-Tracking-New-Navigation-Toggle-(Saas)?widget=16667777&udv=0) was [created](https://gitlab.com/gitlab-org/gitlab/-/issues/383328#note_1377533473) that is starting to show our data! :tada: - **Our proposed metric for the new navigation adoption** is the ratio of pageviews with old navigation vs new - Our system cannot easily do user tracking for example how many users have enabled - We needed another way - Link to graph in Sisense - **Our proposed metric (and potential longterm PI metric)is ratio of pageviews that are navigated from navigation clicks** - The intent is how much does navigation get a user to where they _wanted_ to go - Link to graph in Sisense - Both of these will be in a new dashboard that is being created: - A new PI metric will be determined when we have viewed the following data - https://gitlab.com/gitlab-org/gitlab/-/issues/383328 - Data is working on this issue: https://gitlab.com/gitlab-data/product-analytics/-/issues/1110 - A DBT and performance are taking a long time because it is a big query