# Overview This GA release moves us closer to our vision "to continue to extend DevSecOps across it's most painful gap - measuring user value" by making the initial features to store, query and visualize quantitative usage data generally available. The [Group Direction page](https://about.gitlab.com/direction/analytics/product-analytics/#general-availability-ga) should be considered the source of truth if the description there differs from this. # User Stories for GA release The things we want users to be able to accomplish after the first GA release are listed below. Any additional functionality should not hold up the release. ## Project Setup <details><p> 1. As a Product Analytics Customer, I want to be able to setup an application to use Product Analytics, so I can start instrumenting events. 1. As a Product Analytics customer I want to see the setup of product analytics, so i can remember how to instrument my application when i forget. </p></details> ## Code Instrumentation in partnership w/ ~"group::analytics instrumentation" <details><p> 1. As a developer, I want to be able to instrument my app to collect Audience data, so I can see how many users of the software we have. 2. As a developer, I want to be able to instrument my app to collect event/behavior data, so I can see when users take specific actions in my software. </p> </details> ## View built in Dashboards <details><p> 1. As a Product Analytics customer I want to see the audience dashboard, so i can track unique visitors for pages I have instrumented so I can understand how many unique users my software has. 1. As a Product Analytics customer I want to see the behavior dashboard, so i can track actions by unique user for events I have instrumented so I can understand actions being taken by users in my software. </p></details> ## View Usage Data In Application / billing * Fix any bugs from MVC of viewing usage from https://gitlab.com/groups/gitlab-org/-/epics/10890+ * MVC for Customer Monthly Billing https://gitlab.com/groups/gitlab-org/-/epics/11107+ ## Connect to Self Managed Product Analytics Stack * MVC from https://gitlab.com/groups/gitlab-org/-/epics/8921+ for Self Managed stacks. # Other GA Launch Criteria 1. Rate limiting is in place for Gitlab provided Product Analytics Stack 1. Security/Infra work complete for deployment into infrastructure managed environment(s) - Defined SLAs for various parts of the stack that can be used for future capacity planning. Shared with AInst 1. Confidence in data parity for Internal Events through the Ruby SDK (some % TBD) ## Unique to managed services GA: 1. Pricing / Packaging is approved - SKU is created and tested - Messaging to Beta customers about transition to GA including any paid plan and off boarding date is created and sent before any public GA announcement. 1. Customers can purchase access to the managed product analytics stack