Add granular telemetry for AI Controls preference changes
Categories
(Firefox :: Settings UI, enhancement, P2)
Tracking
()
People
(Reporter: sopsal, Assigned: mstriemer)
References
(Blocks 1 open bug)
Details
(Whiteboard: [recomp])
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
This bug supports the broader effort to centralize AI related user controls in Firefox Settings.
While telemetry already exists for the 'Block AI enhancements' toggle, this ticket adds more granular instrumentation by introducing a feature_pref_change event that is recorded when a user changes the preference of any feature under AI controls.
feature (string)
pdfjsAltText
smartTabGroups
linkPreviewKeyPoints
smartWindow
sidebarChatbot
translations
selection (string)
available
enabled
blocked
chatbot
Updated•19 days ago
|
Updated•17 days ago
|
| Assignee | ||
Comment 1•6 days ago
|
||
Updated•6 days ago
|
| Assignee | ||
Comment 2•6 days ago
|
||
[Tracking Requested - why for this release]: feature specific telemetry for AI Controls which went out in 148
Comment 3•6 days ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: Telemetry to better understand usage of the AI Controls section
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Verify the browser.ai_control_is_blocking metrics are always correct based on pref values, and the browser.ai_control_changed events fire for each AI Control dropdown change
- Risk associated with taking this patch: low
- Explanation of risk level: Telemetry only additions with tests
- String changes made/needed: No
- Is Android affected?: no
| Assignee | ||
Comment 4•6 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D286375
Updated•6 days ago
|
Comment 6•5 days ago
|
||
| bugherder | ||
Updated•3 days ago
|
Updated•3 days ago
|
Updated•3 days ago
|
Comment 8•2 days ago
|
||
Verified as fixed in our latest Beta 149.0b6 and our latest Nightly build 150.0a1 (2026-03-07)
Description
•