From 16f83e28f81458ca28679129fb243e0669f6c76c Mon Sep 17 00:00:00 2001 From: Kevin Chu <kchu@gitlab.com> Date: Tue, 29 Sep 2020 15:17:36 +0000 Subject: [PATCH] Add Data for PM Handbook link --- .gitlab/issue_templates/Snowplow event tracking.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitlab/issue_templates/Snowplow event tracking.md b/.gitlab/issue_templates/Snowplow event tracking.md index a3a1a18fa8ca1..71fa880e08760 100644 --- a/.gitlab/issue_templates/Snowplow event tracking.md +++ b/.gitlab/issue_templates/Snowplow event tracking.md @@ -4,6 +4,7 @@ * Snowplow is currently not used for self-hosted instances of GitLab - Self-hosted still rely on usage ping for product analytics - Snowplow is used for GitLab SaaS * You do not need to create an issue to track generic front-end events, such as All page views, sessions, link clicks, some button clicks, etc. * What you should capture are specific events with defined business logic. For example, when a user creates an incident by escalating an existing alert, or when a user creates and pushes up a new Node package to the NPM registry. +* For more details read https://about.gitlab.com/handbook/business-ops/data-team/programs/data-for-product-managers/ --> <!-- -- GitLab