Per conversation with @SNowick_WMF on October 20:
@SNowick_WMF will look into Android Search Data and analyze trends for search by source and decline in start events.
It’ll help us for more clarity in regards to impact of the recent search changes on Android.
Bonus fix: In our conversation, we realized that results in the Android Search Actions Weekly chart are incorrect as the number for start should be higher than results.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Dbrant | T256819 [EPIC] Improve search experience | |||
| Resolved | SNowick_WMF | T259883 Analytics about usage of search | |||
| Resolved | SNowick_WMF | T266056 Trend analysis for search by source and decline in start events |
@schoenbaechler Hi Robin - I was able to find out why counts for results are higher than start in the MobileWikiAppSearch schema. For every start there are 2 searches initiated: one for title and and one for full text, so when results are returned they are automatically double the start events. Additionally when a user scrolls to see more results that counts as a result event as well, and this can generate multiple counts while scrolling. When we move to the MEP platform we may consider adding a singular result_returned event separate from these counts so that we are able to do a 1:1 start vs result event comparison, as it stands now the results count doesn't allow for that.
Ok, thx for investigating, @SNowick_WMF. I’m wondering then, should we remove results from that chart completely? Not sure if it provides additional value until MEP.