Page MenuHomePhabricator

Add instrumentation to report and dialog navigation buttons
Closed, DeclinedPublic5 Estimated Story Points

Description

This task involves the instrumentation of the report button so that we evaluate who’s engaging with it and what are they doing afterwards.

Requirements

The report button is instrumented such that we know:

  • Bucketed edit count
  • Location of the report button (e.g. talk section heading, comment)
  • Access method (mobile or desktop)
  • Where within the flow people get to (are they abandoning at any time, are they able to successfully submit?) Track clicks of the cancel button and proceed button

Note
The overall metrics and instrumentation plan is available here (includes implementation guide)

Event Timeline

Madalina updated the task description. (Show Details)
Madalina updated the task description. (Show Details)

The account state of the people who click it (logged in/out)

I believe in the latest designs, we don't allow logged-out users to click on the button. Do you want to log impressions for how many logged-out users see the "report" button in the overflow menu?

We had a conversation about logged-out users yesterday. The current proposal is to show a greyed out button for users who are not logged in however we will probably change that to redirecting them to sign-in. Until this is clarified we should not log impressions for logged-out users.

JKieserman set the point value for this task to 3.Aug 2 2023, 1:28 PM
JKieserman renamed this task from Add instrumentation to report button to Add instrumentation to report and dialog navigation buttons.Aug 2 2023, 1:35 PM
JKieserman updated the task description. (Show Details)
JKieserman subscribed.

The biggest chunk of this work is getting the information we need from discussion tools (where was the button clicked, topic or comment) in order to log the button event correctly

This is obsolete, new instrumentation tickets will be added.