1876433 - Glean.js automatic click event instrumentation v2

Status: NEW

(Data Platform and Tools :: Glean: SDK, enhancement, P3)

Description

[Bruno Rosa [:brosa]]

This work will be v2 of the work completed in https://bugzilla.mozilla.org/show_bug.cgi?id=1867294

In v2 we want to capture additional info for each client event including:

• page_referrer - Need only the origin for cross domain requests. For same site requests, need at least the path as well (to understand how users navigate through pages). All of this is what browsers' default referrer policies already limit Bedrock to.
• url - Need the origin, path, and likely also the ability to capture specific query parameters. Capturing these query parameters are useful because they often run multi-variant experiments on their pages. So, a visitor might land on say https://www.mozilla.org/en-US/ and then get redirected to an experiment cohort, that might be something like https://www.mozilla.org/en-US/?v=2. When looking at the experiment results, they might want to see how many click events variations 1, 2, or 3 generated over a given time period. They often use this when rolling out say a new feature, or a redesign of a product landing page - to make sure it performs well before everyone sees it.
• target - We want to collect some data about the target of the click happening - https://developer.mozilla.org/en-US/docs/Web/API/Event/target

We also want to revisit previous conversations about

• Tagging elements
• What all elements should we collect events for
• etc

If anyone else has anything else that should be included in v2, please feel free to start up the conversation here.