To clarify, is this about the mobile talk overlay, or just when you view the desktop talk page from a mobile device?

In T301026#7685327, @DLynch wrote:

To clarify, is this about the mobile talk overlay, or just when you view the desktop talk page from a mobile device?

I'm glad you thought to ask, @DLynch. Does the below resolve the ambiguity you noticed and/or bring new thoughts/questions to mind?

This ticket is about determining what – if any – new instrumentation we'll need to add to the three versions of mobile talk pages [i] that will exist once all DiscussionTools features become available on mobile. Note: this instrumentation is all in service of completing the analyses we are planning in T298072.

Talk Page Versions

Description	Screenshot
The MobileFrontend talk page overlay
The Read as wiki page view
The Read as wiki page view with the suite of mobile DiscussionTools enabled (T278588)	TBD

i. Maybe there will technically be two NOT three versions of mobile web talk pages?

@ppelberg

Here is the current draft instrumentation spec, where I've taken an initial pass at reviewing and defining all the instrumentation that will be needed to measure the metrics identified to evaluate DiscussionTools on Mobile (as described in the measurement plan).

The spec includes columns that identify events to be tracked, whether they are currently instrumented in either of the two possible talk page versions (Read as Wiki Page or Mobile Front End) and where the existing instrumentation is implemented.

Summary of findings from the review :

• MobileWebUIActions: The MobileWebUIActions schema currently tracks clicks to start a new discussion and views to a talk page on mobile, which are events we need to track for the planned analyses. If we decide to use this schema for our planned analyses, we will need to resolve the following:
  • Resolve T295490 to make the click tracking that is present in the MobileFrontend talk page overlay within the "Read as wiki page" view.
  • This schema does not appear to log clicks to start a reply or clicks to start a page or section edit, which are identified as forms of talk page engagement in our measurement plan. This instrumentation should be added if we plan to use this schema to measure bounce rate.
  • This schema does not include a unique identifier (only a unique session id). We would need to look into adding a unique identifier with this schema if we want to look at per user metrics vs per session metrics.

• EditAttemptStep and Talk_Page_Edit:
  • No data is being tracked in the current mobile frontend talk experience. We would need to add any relevant events to the mobile talk overlay actions. Column B of the spec identifies the key talk page events that we want to track. Mapping these events to the actions people can take within the mobile front end talk experience will be completed as part of T302108.
  • There is an unresolved bug related to EAS recording all Wikiedtior edits as desktop edits. See T249944. Need to confirm the extent of impact of this (if there is any) on the planned analyses for this project.

On 10 March (yesterday), @DLynch, @MNeisler, and I met to discuss the findings Megan posted in T301026#7765304 and the questions they brought about so that we can decide how to move forward with instrumenting the mobile talk overlay and read as wiki page views.

The action items that emerged during this meeting are documented below. I've also added the ===Approaches section to the task description which now contains the three instrumentation approaches we discussed during yesterday's meeting.

10 March Meeting Outcomes

@ppelberg This has been in the needs sign-off column on the product analytics kanban since March. Is there work left to do here for @MNeisler?

In T301026#7897349, @mpopov wrote:

@ppelberg This has been in the needs sign-off column on the product analytics kanban since March. Is there work left to do here for @MNeisler?

hi @mpopov! There could be more work for @MNeisler. Tho, I don't think we will know whether there is more work to be done or not until after T303654 is resolved.