Closed Bug 1079465 Opened 10 years ago Closed 7 years ago

Add telemetry probes to measure Awesomebar search suggestions usage

Categories

(Firefox :: Address Bar, defect, P5)

defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: wselman, Unassigned)

References

Details

(Whiteboard: [metrics][suggestions][fxsearch])

User Story

Goal here:

Demonstrate that Search Suggest is an improvement against awesomebar-only suggestions.  Specifically, that it requires less effort to achieve the same results.  These measures would be part of that campaign.  

During the experimental phase, additional measures might be needed to understand how to structure and develop heuristics around the suggestions.

Add probes for experimental build to test search suggestions. Probes should measure:
1. Search suggestion success (data returned, suggestions selected)
2. Search terms
3. Keystroke count
Add probes for experimental build to test search suggestions. Probes should measure: 1. Search suggestion success (data returned, suggestions selected) 2. Search terms 3. Keystroke count
Depends on: 1079452
Flags: firefox-backlog?
Summary: Add telemetry probes to measure search suggestions usage → Add telemetry probes to measure Awesomebar search suggestions usage
Goal here: Demonstrate that Search Suggest is an improvement against awesomebar-only suggestions. Specifically, that it requires less effort to achieve the same results. These measures would be part of that campaign. During the experimental phase, additional measures might be needed to understand how to structure and develop heuristics around the suggestions.
Flags: firefox-backlog? → firefox-backlog+
Flags: qe-verify?
Flags: qe-verify? → qe-verify-
Hi Kev, can you look at what info we'd want from telemetry? is it all that is mentioned in user story or more? we can move up to measure success / change once we know what to measure.
Rank: 40
User Story: (updated)
Flags: needinfo?(kev)
Priority: -- → P4
Whiteboard: [metrics][suggestions][fxsearch]
Not sure if this is still a thing, but it's useful information. Adding rweiss (who will hate me for doing so), and search really does need a UT review.
Flags: needinfo?(kev) → needinfo?(rweiss)
Currently we are already collecting the number or times a search suggestion is selected in the awesomebar.
:kev, are you asking for this to be measured on release desktop users?
Flags: needinfo?(rweiss) → needinfo?(kev)
:rweiss - more we need to take a look at what's being collected, and make sure folks who care about these things are aware, too. basically a telemetry dictionary review. Basically a review of settings and counters info collected, and further discussion with folks who are involved in decisions/discussions search-related. Also a good opportunity to discuss event-based ideas.
Flags: needinfo?(kev)
Dave, is there anything still relevant here that other bugs/probes are not covering already? Fwiw, this seems to predate suggestions already being enabled in the Address Bar, and thus I suspect it's just a wontfix.
Component: Search → Address Bar
Flags: needinfo?(dzeber)
Priority: P4 → P5
I agree this is probably wontfix. It sounds like this was a requested for a specific experiment. We have probes or bugs filed broadly covering 1 (number of search suggestions shown, how often a search suggestion result is selected and its position in the list) and 3 (query length). If 2 means collecting the text of the search queries, that is not on the table.
Flags: needinfo?(dzeber)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.