Change Details

The [[ https://schema.wikimedia.org/#!/secondary/jsonschema/analytics/legacy/mobilewebuiactionstracking | MobileWebUIActionsTracking ]] schema allows us to log information about how users interact with mobile web UI elements. We're interested to understand more about the Overflow menu added as part of #advanced_mobile_contributions. These events do not currently tell us anything about where the user came from, only their destination, which makes it hard to understand where users are seeing the menu. This issue came up in particular because we wanted to split the data by user vs article namespaces. There is an overlap in the links present in both namespaces, as identified in T305928. We could get the data we need if events were stored with the namespace of the page the user is on when the event is fired.

The [[ https://schema.wikimedia.org/#!/secondary/jsonschema/analytics/legacy/mobilewebuiactionstracking | MobileWebUIActionsTracking ]] schema allows us to log information about how users interact with mobile web UI elements. We're interested to understand more about the Overflow menu added as part of #advanced_mobile_contributions. These events do not currently tell us anything about where the user came from, only their destination, which makes it hard to understand where users are seeing the menu. This issue came up in particular because we wanted to split the data by user vs article namespaces. There is an overlap in the links present in both namespaces, as identified in T305928, and knowing which interactions are from users in user space versus articles will be helpful. We could get the data we need if events were stored with the namespace of the page the user is on when the event is fired.

The [[ https://schema.wikimedia.org/#!/secondary/jsonschema/analytics/legacy/mobilewebuiactionstracking | MobileWebUIActionsTracking ]] schema allows us to log information about how users interact with mobile web UI elements. We're interested to understand more about the Overflow menu added as part of #advanced_mobile_contributions. These events do not currently tell us anything about where the user came from, only their destination, which makes it hard to understand where users are seeing the menu. This issue came up in particular because we wanted to split the data by user vs article namespaces. There is an overlap in the links present in both namespaces, as identified in T305928, and knowing which interactions are from users in user space versus articles will be helpful. We could get the data we need if events were stored with the namespace of the page the user is on when the event is fired.