We currently track URLs as part of our Snowplow Frontend events. Moving forward we want to de-identify the URLs we send based on https://gitlab.com/gitlab-org/gitlab/-/issues/336779 as the URLs can contain PII data. There can be two approaches to this ### 3. Submit Route structure with Namespace and Project IDs | URL | Route | |-----|-------| | `gitlab.com/my-group/my-awesome-project` | `gitlab.com/group123/project356` | | `gitlab.com/my-group/my-awesome-project/some_folder/some_file.js` | `gitlab.com/group123/project346/:repository_path` | | `gitlab.com/my-group/issues` | `gitlab.com/group123/issues` | | `gitlab.com/checkout` | `gitlab.com/checkout` | ### Rollout Plan We will be rolling this out as follows: 1. Add sentry error tracking for when an exception is raised so that we monitor the errors while masking. MR - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70891 1. Handle `new` action with generic URLs and URLs having PII data. Issue - gitlab#340802 1. Enable feature flag on staging. 1. Monitor the errors and fix any cases arising from exceptions. 1. Enable feature flag on production. The issue for Step 1 is not required, MR is already in progress and should be ready to merge.