1908105 - GCP-Onboarding: Telemetry measuring success and allowing to write a block maybe on hacks.mozilla.org with insightful data

Status: NEW

(Core :: Privacy: Anti-Tracking, task, P3)

Description

[Manuel Bucher [:manuel] {{ fyi: PTO Jul 26 - Aug 17 }}]

To be able to tell a compelling story, I'd like to land a few telemetry probes. One hard thing that we have to clear with data beforehand is how we get telemetry just from the region we are interested in (Do we need to use Nimbus for the rollout and then only look at telemetry on users who rolled into the experiment?). Could influence decision on Bug 1908102.

• How many users enabled GPC on their own before the rollout (https://sql.telemetry.mozilla.org/dashboard/GPC). Difference for legally binding states to others.
• What is the retention of users opting in/opting out
  • Check with #data to figure out a good way to only look at telemetry from users in the state that we will show the dialog in.
• User choice when giving dialog
• Does the user choice change over time after giving the dialog
• How many users have GPC enabled after the rollout

This is the collection of telemetry collected in the GPC-Onboarding: Engineering Kick-Off-document.
This bug probably better serves as a meta bug for telemetry for the GCP-onboarding project. Landing individual probes should be done in bugs blocking this bug and can be opened when we reached the point that we want to land telemetry. The probes only need to live as long as the project so can expire after 6months and be removed afterwards.