VisualEditor/Metrics

Key indicators

Indicator	Definition and rationale	Frequency	Effort required	Breakdowns
Editing success rate	Proportion of init events that lead to saveSuccess events. Alerts the VE team to significant usability issues.	Daily. Tactical metric.	Already tracked in the edit analysis dashboard. Daily frequency is useful, although it displays significant seasonality (higher on weekends)	Project, user experience, WikiEditor or VisualEditor
VE adoption	Proportion of edits tagged as VisualEditor. Tracks the "market" success of VisualEditor. Should we filter for article namespace only, like the EE metrics did? Are VE and wikitext sampling at the same rate?	Weekly.	Not tracked?	Project. Platform. User experience?

Other possible indicators

General

• Hourly edits

Edit schema

The Edit schema collects all the data we need to analyze the edit funnel.

Things to do:

• Instrument the editing facility in the apps?
  • James isn't convinced that editing in apps is an important feature
• Start actually recording platform type
  • Ideally this would be by directly testing screen size and so on
  • If that's too difficult, we could instead a to integration (maybe we should do that anyway)
• Start using the integration field
  • We are not recording any integrations other than page

• Figure out why all recently events have not been validated
• Visualize it using a Sankey diagram?

Merge MobileWebEditing schema into Edit schema

→ T110272

Editor performance

Indicator	Key?	Definition	Breakdowns
Editor load time		Time between init and ready events. Are there better performance metrics? Something similar in Grafana. (action.init.timing + action.ready.timing)	WikiEditor or VisualEditor

Editor engagement dashboard

https://edit-analysis.wmflabs.org/editor-engagement/