Remove anonymization Logic for Moments Page Telemetry
Categories
(Firefox :: Messaging System, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: shong, Unassigned)
References
(Blocks 1 open bug)
Details
Currently, what's new panel (WNP) telemetry and Moments page telemetry are both using the client_id anonymization pattern to preserve privacy.
From my understanding, this was an implementation detail, and we don't have a policy reason not to report client_id for telemetry for these messages.
We should fix this, so pings from these surfaces are reporting client_id.
We want to do this, to make it possible / make it easier to answer business questions, like what KPIs are tied to interactions with these messaging surfaces.
|
Reporter | |
Comment 1•5 years ago
|
||
Note: I listed this as blocking 1638891, but I'm not sure it's actually blocking. Just related to.
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
|
|
||
Comment 2•5 years ago
|
||
This is fixed via bug 1638891.
|
||
Comment 3•2 years ago
|
||
I suspect this was fixed by bug 1638891 at the time of the above comments, but was later regressed by the introduction of additional feature IDs for moments pages. Using isInCFRCohort to determine whether to record client_id may have worked if moments pages were deployed using the cfr feature id. But nowadays we use the moments-page feature id. That seems to be the cause of bug 1859039.
|
||
Updated•1 year ago
|
Description
•