There are several search-related areas to measure in the next sprint (33.3). An etherpad to collect these is here: https://firefox-ux.etherpad.mozilla.org/areas-to-measure-for-33-3-sprint. The list so far: 1. Search suggest on newtab and on about:home * How often is it being used? * How often do users re-query immediately after a suggested search (possibly a mistaken click)? 2. Search via search history items in awesomebar results (bug 1034381) * How often are previous searches being clicked in awesomebar results? (this would be compared with searches clicked after that bug is finished) 3. Clicking on the awesomebar results for "this will search $searchprovider" vs. just hitting enter * How often to users click enter for a search string vs click the awesome bar results? 4. Searches urls with bogus protocols made from URL bar going to Google rather than error pages (already landed via bug 982428) * Are more searches being made via the URL bar? * Are Google-specific strings (eg site: define: and math) being used more? 5. How often are people searching for strings via the URL bar vs the Search bar? * Our data on this is old * Could help inform bug on adding search suggestions to awesomebar (bug 958204) Some others will likely be needed.

Notes for later: "selections" are defined as "clicks on" or "enter keypresses when focused". 1a) Log selections of searchSuggestTable (when it lands, dependent on bug 612453 (about:home) and bug 1028985 (newtab). 1b) On each query, check to see if the previous query was less than (say) 30 seconds ago. If it is, then log it as a re-query. 2a) Log selections of awesomebar results that "are like" the url in the current search provider. 2b) Once bug 1034381 lands, log clicks on awesomebar results that UnifiedComplete.js thinks are searches. 2c) Perhaps log whether it's the users current engine or not? 3) Log the type of selection (enter key or mouse click) on all the above. 4a) This may need to be uplifted, to see if "more" searches are being done. 4b) Looking for Google-specific strings is tricky, because of things like "webcal:" which redirect to your calendar provider. Maybe for pre-bug-982428 we can log a count of urls we try to go to which end up at the error page? On the other hand, it might be easier to hook into the files changed in https://bugzilla.mozilla.org/attachment.cgi?id=8445128&action=diff and send the notifications from there. 5) For search bar, check in http://mxr.mozilla.org/mozilla-central/source/browser/components/search/content/search.xml#455 For urlbar, check in http://mxr.mozilla.org/mozilla-central/source/browser/base/content/urlbarBindings.xml#261

Forgot to add: how many searches are done via about:newtab and about:home

Okay, I believe this is all the bugs that need to be filed. Boriss, would you please double-check to make sure I didn't leave anything out, and re-open the bug if I forgot something? Thanks!

(I'm pretty sure we don't need Boriss to comment on this anymore.)