Closed Bug 1344933 Opened 8 years ago Closed 7 years ago

Awesome Bar Prefs to enable A/B search suggestions testing

Categories

(Firefox :: Search, enhancement, P3)

Product:
Firefox
Component:
Search
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: javaun, Unassigned)

References

Details

(Whiteboard: [fxsearch])

User Story

As a user, I expect the Awesome Bar to provide me the best mix of recommendations, whether they are sites I’ve been to before or search suggestions so I can get there faster

As the team, we need to be able to rapidly experiment on the Awesome Bar results mix, so we can find the optimal mix and increase usage and retention.

AC
* Team has an inventory of existing pref options available for experimentation (COMPLETE)
* Team has the new ability to serve search suggestions on the top, ABOVE the history results. 
* (May later add requirements for a minimum number of visible search suggestions results, or a minimum number above the history).
      No description provided.
It's important to get search suggestions on early if we want to move towards unification. User behavior changes over time, and we need to be able to measure if users are moving from the search bar to the Awesome bar, if volume is growing or falling, etc. We also need to be able to run multiple easy shield studies to find the right result mix and give ourselves maximum runway for success. 

We need level of effort before deciding where this one goes.
Blocks: 1344919
User Story: (updated)
Priority: -- → P3
Summary: [userstory] Awesome Bar Prefs to enable A/B search suggestions testing → Awesome Bar Prefs to enable A/B search suggestions testing
Whiteboard: [fxsearch]
Depends on: 1359899
User Story: (updated)
Now we have:
browser.urlbar.maxHistoricalSearchSuggestions: allows to control number of historical search suggestions
browser.urlbar.matchBuckets: allows to define the mixup of results, currently between Places usual matches and suggestions. In the future we could extend this to more complex mixups as we see fit.

I think both points 2 and 3 are now covered.
Setting a needinfo so this is noticed and eventually we can resolve the bug or add further steps.
Flags: needinfo?(jmoradi)
bug 1378035 is going to add a third pref to control the buckets in a "search" context. The heuristic result will control the context for now, if it's a search we will be in a search context, otherwise we'll be in a general context.
Depends on: 1378035
Now we also have browser.urlbar.matchBucketsSearch to define different buckets when the heuristic result is a search.
I think we can resolve this bug now.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Flags: needinfo?(jmoradi)
You need to log in before you can comment on or make changes to this bug.