| • JKatzWMF | |
| Apr 17 2015, 12:23 AM |
| F152768: search-page-03.png | |
| Apr 22 2015, 6:44 PM |
| F152761: search-js-03.png | |
| Apr 22 2015, 6:40 PM |
| F152756: search-js-03.png | |
| Apr 22 2015, 6:38 PM |
For the new header (currently in alpha), we need to see if it has a negative impact on searches. It will not be enough to capture search button clicks (because now that is just a "header" click.
Now we also have to send an event when text is first entered into search box.
from: https://meta.wikimedia.org/wiki/Schema:Search
"session-start"
"impression-results"
"click-result"
Use cookies rather than sendBeacon to save the click-result event.
JonK says we should probably reuse the existing schema (with a new field for the mobile mode): https://meta.wikimedia.org/wiki/Schema:Search
@dr0ptp4kt, we are trying to track search events on mobile and were wondering whether we should alter the existing Schema:Search [1] that the desktop uses to add an extra field, or clone this schema? The extra field that we need is the mobilemode field which will contain data about the mobile mode, i.e. alpha, beta, or stable. I think this maybe useful for apps as well. What are your thoughts on that? If I am not mistaken, the schema was designed to be used by MobileWeb as well.
I've created the MobileWebSearch schema so that we can implement and test this without waiting on a decision about whether or not to use the Search schema. If we do decide to use Search schema, then it should be trivial to merge any changes.
Change 207761 had a related patch set uploaded (by Phuedx):
Add new events to SearchOverlay
Change 207762 had a related patch set uploaded (by Phuedx):
Hygiene: Generalise the futureLog mechanism
Change 207763 had a related patch set uploaded (by Phuedx):
Log MobileWebSearch events