Baseline metrics set 1:

Quantitative metrics - high priority

• Search sessions initiated
• Impressions of search suggestion
• Clicks on suggestions
• Text types into search - i.e. we would want some way to know whether a session was completed using a suggestion, completed using search (they began typing and selected a result), or abandoned

Qualitative metrics - nice to have

• Overall interest in search suggestions
• Overall satisfaction with UI of feature
• Ease of use of functionality itself

Baseline metrics redacted:

Quantitative metrics - high priority

Search sessions started
Clicks on suggestions from extension
Type of session - i.e. we would want some way to know whether a session was completed using a suggestion, completed using search (they began typing and selected a result), or abandoned

Qualitative metrics - nice to have

Overall interest in search suggestions
Overall satisfaction with UI of feature
Ease of use of functionality itself

After discussed with @ovasileva, our goal is to gain a sense of user preferences with minimal instrumentation. The major question we want to understand is "Are people interacting with the prototype suggestion and how frequently? " Based on these, I have drafted an instrumentation spec: link.

@KSarabia-WMF , let me know if you have any questions.

@KSarabia-WMF - assigned this to you for QA. The expectation here is to sign off if no open questions on the spec that are not covered in T372780: Instrument empty state of search experiment remain.