Event Dictionary for Usage Ping - Growth Section
Overview
Hello Growth section,
As we ramp up to become a more data driven company, we need a good process in place to manage our product analytics. We currently have 544 metrics in Usage Ping and this will eventually rise to thousands of metrics.
Last week, we introduced the Event Dictionary - a single source of truth for all our product analytics metrics and events. The Event Dictionary includes all product analytics metrics and events we collect at GitLab. It includes the following details:
- Metric name with example values
- Responsible section, stage, or group
- Description of what we're tracking
- Implementation status
- Availability of metric based on plan
- Code path to find the metric
In case you're interested, here are examples of other Event Dictionaries (also known as a Tracking Plans) from other companies:
Note: we've temporarily moved the Event Dictionary from our markdown docs into a Google Sheet for easier editing. We'll eventually move this back into our docs once the majority of changes are done.
How is this related to Performance Indicators?
Having a complete Event Dictionary of metrics / events makes defining the XMAU metrics much easier.
Each metric in the Event Dictionary can potentially be used as an AMAU. AMAU's are the building blocks of our GMAU, SMAU, Section MAU, and MAU Performance Indicators. To better understand how these are all related, see Structure of Product's Performance Indicators.
Completing the Event Dictionary
The goal of this issue is to complete the Event Dictionary for your section.
I have gone through all 544 metrics and have assigned them to each Section.Stage.Group based off my very high-level understanding - there are errors in these assignments, so, please check them.
Section.Stage.Group | PM | Metrics assigned (Aug 7 2020) | Checked Assignment? |
Added Descriptions? |
Added Plans? |
---|---|---|---|---|---|
growth | @hilaqu | ||||
growth.acquisition | @jstava | ||||
growth.conversion | @s_awezec | ||||
growth.expansion | @timhey | ||||
growth.retention | @mkarampalas | ||||
growth.fulfillment | @amandarueda | ||||
growth.telemetry | @jeromezng | 51 |
Next Steps
- Open the Event Dictionary and fill in all the
PM to edit
columns highlighted in yellow. - Check that all the metrics are assigned to the correct Section.Stage.Group. If a metric is used across many groups, assign it to the stage. If a metric is used across many stages, assign it to the section. If a metric is incorrectly assigned to another Section.Stage.Group, let the PM know you have re-assigned it. If you have 0 assigned metrics, look check that your metrics are not incorrectly assigned to another PM.
- Add descriptions of what your metrics are tracking. Work with your Engineering team or the Telemetry team if you need help understanding this.
- Add what plans this metric is available on. Work with your Engineering team or the Telemetry team if you need help understanding this.
- Add a
✅ to the table above once you have completed this.
Future Metrics
For future metrics you plan to track, please add them to the Event Dictionary and put the status as Planned
, In Progress
or Implemented
. Once you've confirmed the metric has implemented and have confirmed the metric data is in our data warehouse, change the status to Data Available
cc: @hilaqu @kathleentam