diff options
| author | jejacks0n <jjackson@gitlab.com> | 2019-08-21 16:51:53 -0600 |
|---|---|---|
| committer | jejacks0n <jjackson@gitlab.com> | 2019-08-21 16:51:53 -0600 |
| commit | f5a9963174f97f9550c65e72e744492d618499b6 (patch) | |
| tree | ea5c084bc6e2a95c320e06611908c5809fd8553f /doc/development/event_tracking/index.md | |
| parent | 40b9e9e5c2d6cff0f375352d256cda1d0d2557ab (diff) | |
| download | gitlab-ce-tracking-documentation.tar.gz | |
Update alerts so Todos are more cleartracking-documentation
Diffstat (limited to 'doc/development/event_tracking/index.md')
| -rw-r--r-- | doc/development/event_tracking/index.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/event_tracking/index.md b/doc/development/event_tracking/index.md index 7068c569010..4153e0e6de6 100644 --- a/doc/development/event_tracking/index.md +++ b/doc/development/event_tracking/index.md @@ -4,8 +4,8 @@ At GitLab we encourage event tracking so we can iterate on and improve the proje To enable the Product team to better understand user engagement, usage patterns, and other metrics that can potentially be improved on, we should attempt to add tracking where possible. To enable this, maintain consistency, and not adversely effect performance we have some basic tracking functionality exposed at both the frontend and backend layers that you can utilize while building features. -Todo: Document the process to define new tracking by integrating with the data team. -{: .alert .alert-danger} +CAUTION: **Todo:** +Document the process to define new tracking by integrating with the data team. ## Enabling tracking |