Add telemetry to determine how many users have disabled the new tab page to address bar search handoff preference
Categories
(Firefox :: Address Bar, task, P3)
Tracking
()
People
(Reporter: klubana, Assigned: klubana)
References
()
Details
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
2.92 KB,
text/plain
|
cboozarjomehri
:
data-review+
|
Details |
When we initially implemented the new tab search to address bar hand-off, the preference to disable it was widely advertised.
The preference is only accessible via about:config and is named: browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar
We want to add some telemetry to assess the number of users that turned it off, so that we can use that to help make decisions about future work.
This should be a short-term telemetry probe. We should record both true and false states.
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Comment 2•1 year ago
|
||
Comment 3•1 year ago
|
||
Comment on attachment 9365036 [details]
data-review-request.txt
Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?
Yes.
Is there a control mechanism that allows the user to turn the data collection on and off?
Yes. This collection can be controlled through the product's preferences.
If the request is for permanent data collection, is there someone who will monitor the data over time?
No. This collection will expire in 128.
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 2, Interaction.
Is the data collection request for default-on or default-off?
Default on for all channels.
Does the instrumentation include the addition of any new identifiers?
No.
Is the data collection covered by the existing Firefox privacy notice?
Yes.
Does the data collection use a third-party collection tool?
No.
Result: datareview+
Comment 5•1 year ago
|
||
bugherder |
Comment 6•9 months ago
|
||
Marking the issue as verified fixed. Telemetry reports correctly the value of the browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar preference to glean (used Glean.newtabHandoffPreference.enabled.testGetValue() to check).
Description
•