diff options
| author | jejacks0n <jjackson@gitlab.com> | 2019-09-16 14:48:47 -0600 |
|---|---|---|
| committer | jejacks0n <jjackson@gitlab.com> | 2019-09-16 14:48:47 -0600 |
| commit | 0ed3f09c9ac82c0df9b2e619c9dee92a34b14017 (patch) | |
| tree | 6967e046d4824940b56f3a3449d819a1baf8d1d9 | |
| parent | 12b4a028339ba565c2b939cba022173865231790 (diff) | |
| download | gitlab-ce-docs-tracking-updates.tar.gz | |
Add details about contacting the data teamdocs-tracking-updates
| -rw-r--r-- | doc/development/event_tracking/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/event_tracking/index.md b/doc/development/event_tracking/index.md index 946b00c5bb5..efc61d13cb0 100644 --- a/doc/development/event_tracking/index.md +++ b/doc/development/event_tracking/index.md @@ -26,7 +26,7 @@ Event tracking can be implemented on either the frontend or the backend layers, In GitLab, many actions can be initiated via the web interface, but they can also be initiated via an API client (an iOS applications is a good example of this), or via `git` directly. Crucially, this means that tracking should be considered holistically for the feature that's being instrumented. -The data team should be involved when defining analytics and can be consulted when coming up with ways of presenting data that's being tracked. This allows our event data to be considered carefully and presented in ways that may reveal details about user engagement that may not be fully understood or interactions where we can make improvements. +The data team should be involved when defining analytics and can be consulted when coming up with ways of presenting data that's being tracked. This allows our event data to be considered carefully and presented in ways that may reveal details about user engagement that may not be fully understood or interactions where we can make improvements. You can [contact the data team](https://about.gitlab.com/handbook/business-ops/data-team/#contact-us) and consult with them when defining tracking strategies. ### Frontend |