We should track how many users have profile images once we enable the feature.
Created attachment 8606410 [details] [diff] [review] Add telemetry probe for profile images.
Attachment #8606410 - Flags: review?(markh)
Comment on attachment 8606410 [details] [diff] [review] Add telemetry probe for profile images. Review of attachment 8606410 [details] [diff] [review]: ----------------------------------------------------------------- I don't have a real problem with this, but I guess I also don't see a whole lot of value as it stands - I expect that once it reports a value it will continue to report the exact same value forever (assuming people don't regularly remove a profile image or change the FxA account used by the profile). It will also only report when the user visits about:preferences#sync, but I guess that might change in the future. In short, I'm wondering what benefit there is to the client tracking this when it seems the server will have the canonical reference for how many users have profile images and it doesn't need to rely on the user visiting certain parts of the UI to trigger it. https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Adding_a_new_Telemetry_probe also says to get a privacy review for all new probes, so I'll take the same opportunity to see what Benjamin thinks in general.
Attachment #8606410 - Flags: review?(markh) → review?(benjamin)
Profile images are a feature of FxA, right? Will we be able to get this information as part of the FxA server data? Is this metric going to feed a specific report? Or who is going to monitor this data? The problem with this only showing up whtn visiting about:preferences seems to be an important problem.
You're right-- this metric would actually track how many users see a custom profile image in the Sync pref pane (until it's displayed elsewhere in the browser). I'll close this for now since it's not clear how useful that metric is, and we don't have a report for FxA yet that I know of.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.