| Pginer-WMF | |
| Aug 31 2023, 10:26 AM |
| F41651528: add-languages-event.webm | |
| Jan 5 2024, 1:26 PM |
| F32401021: more-options.png | |
| Aug 31 2023, 10:26 AM | |
| File Not Attached |
The Language selector was extended to support additional actions that could affect the list of languages in which a Wikipedia page is available (T289840).
Access to Content translation was provided there but it has not been instrumented yet. This ticket proposes to instrument the action so that we can track how many users access the tool through each entry point (T328913).
The ticket will cover instrumentation for desktop and mobile versions of the entry point.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T289839 Update current language selector to incorporate key improvements form the new design | |||
| Resolved | ngkountas | T289840 Add "quick actions" menu to the current language selector | |||
| Resolved | ngkountas | T345335 Instrument access to translation from "more options" in the language selector | |||
| Resolved | KCVelaga_WMF | T353615 Update CX event schema to allow additional sources: language_selector_options & followup_after_publishing |
@Pginer-WMF do we know what should be the event source for this entrypoint? In the list of the available event sources I cannot find any source that seems relevant.
Hi @ngkountas
This is related to the frequent_languages source (an indicator in the "Suggested Languages" section of the language selector that surfaces frequently-accessed missing languages as an opportunity to translate them; T290972).
Although it belongs to the same menu, I would suggest creating a new event source. After a quick look at the data, frequent_languages is the most frequent entry point, which as of now is coming from the missing languages suggestion. Clearly, the language selector has high traffic, and users possibly have two ways to proceed: using missing languages suggestions or going to more options and clicking on translate. It would be good to differentiate these two pathways.
So, I'd suggest naming the new event source language_selector_options.
@KCVelaga_WMF Thank you for your response. I was wondering if we can also add this event_source to the list with the valid event sources, inside the event schema, as using this event_source without previously adding it there, would lead to failed event submissions.
Change 982891 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):
[mediawiki/extensions/ContentTranslation@master] CX: Instrument ULS "Add languages" entrypoint
Change 982891 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] CX: Instrument ULS "Add languages" entrypoint
@ngkountas yes! I will work on it this week to update the event_source enum values. I was checking logstash and realized events with followup_after_publishing are causing errors as the schema hasn't updated. I will update with both of them.
Change 983678 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):
[mediawiki/extensions/ContentTranslation@master] CX3 Build 0.2.0+20231218
Change 983678 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] CX3 Build 0.2.0+20231218
This task can be considered as done. As we can see on the following screencast, the campaign URL parameter is properly set to ulsaddlanguages and the event is properly logged with the language_selector_options event_source.