Skip to content

Turn on event tracking for Canary Deploys

Problem

We are not tracking all events in Snowplow on .com or self-managed and as such don't have the proper data to glean insights and drive product decisions. We have shied away from this in past due to performance concerns.

This is a P1 issue and should be activated upon ASAP if at all possible. Lack of data is impacting marketing, Growth experiments, product decisions, and .com growth.

Proposal

Turn on all event tracking in Snowplow for canary deploys for .com. This means anyone who has opted into canary deployments using next.gitlab.com would have all events tracked. This does not include PII information. Due to an unknown, unproven performance impact, we recommend making the change here in case it needs to be rolled back.

This would mean making a change to the current snowplow header implementation.

We should add link click tracking, form tracking, and time tracking. These should all be one-line additions to the header file above.

We should also turn on full backend event tracking for canary deploys if possible.

Result

Next steps (if any)

Work with engineering to understand what's needed to turn it on.

cc @ebrinkman

Edited by Luca Kisielius