1251454 - Probe to measure toggle between different states of "Always | Never | Only on Wifi" for data savings settings

Status: RESOLVED DUPLICATE of bug 1251749

(Firefox for Android Graveyard :: Metrics, defect)

Description

[Barbara Bermes [:barbara] - NI please!]

I believe we only track if somebody opens that pref but not what they set it to.

We should track the change of the settings (and what kind) for "Show images" and "Show Web Fonts".

Comment 1

[:Margaret Leibovic]

We do already have this for "Show images": http://mzl.la/1THBFMP

This probe name isn't good, and the description doesn't indicate what the buckets are, but I see in the code it's 0 = never, 1 = always, 2 = wifi

I think this probe is actually broken though, because I'm not seeing any values for 0 (well, except for some noise) ...

Comment 2

[Mark Finkle (:mfinkle) (use needinfo?)]

I would like us to move away from histograms and look for event data ways to capture this data. I think it's more useful to look at what people are changing in relation to other events. Examples:

1. Saw onboarding talk about data saver, and soon after turn it on (never or wifi)
2. Saw a prompt for Tab Queues and turned it on (boolean)
3. Saw a notification for updated content, didn't like it and turned it off (via the settings button)

We track event probes for any changes to preferences: (edit.1, settings, name-of-pref). I wonder how useful it would be to change to: (edit.1, settings, ["name-of-pref", "value"])

where value would be (0, 1) for booleans, integer for modes, and "*" for user entered strings? I used "*" because we need to be careful with data that could uniquely identify someone.

SQL and Spark are both capable of "unpacking" the array, if needed.

Comment 3

[:Margaret Leibovic]

I'm going to fix this in bug 1251749.

As part of that bug we should also remove the inaccurate histogram probes.