This task is intended to capture what data wiring is needed to answer if this feature met its goals.
See epic
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T431812 [EPIC] Visual Editor app journey | |||
| Open | SNowick_WMF | T431992 Visual Editor: Data - Documentation | |||
| Resolved | DLynch | T432853 Visual Editor instrumentation: Modify schema to track sessions coming from the apps in editattemptstep | |||
| Resolved | BUG REPORT | SNowick_WMF | T433000 [BUG] Android app - Add values for `wiki` and `user_editcount` to edit data sent to Editattemptstep | ||
| Resolved | SNowick_WMF | T433909 BUG [Android] Missing action = `abort` events in event.editattempstep | |||
| Open | SNowick_WMF | T434240 Visual Editor: Data - Instrumentation - iOS | |||
| Resolved | SNowick_WMF | T434241 Visual Editor: Data - Instrumentation - Android |
We can currently measure edit success rate (and the inverse abandon rate) using data in event.editattemptstep however we are missing revision_id values for Android edits which will prevent us from being able to answer question about newcomer edits. See https://phabricator.wikimedia.org/T432388 task for engineering to investigate.
Baseline Edit Completion Rate: Data
Date range: 2026-06-01 - 2026-06-30
| Platform | Count Edit Starts | Count Edit Success | % Edit Success |
|---|---|---|---|
| Android | 738917 | 101248 | 13.7% |
| iOS | 299640 | 48522 | 16.2% |
Data Availability
| Data Available Currently | Question: | Data Source |
|---|---|---|
| Yes | Does the introduction of this option result in higher abandonment rate of edits? | event.editattemptstep |
| iOS Yes, Android No | Do we see more ‘newcomers’ becoming successful editors? | JOIN event.editattemptstep and wmf.mediawiki_history (requires revision_id value) |
| TBD | What % of people who are sent to web to edit come back to the app again afterwards? | TBD |
| TBD | Attribution of the edit - how will we track that the person who made this edit originated from the app? | TBD |
Edit attribution:
Init by app_install_id - edit starts in app - savesuccess event with revision_id should include app_install_id and possible flag 'visual edit edit' -
we will only be able to get counts of edit starts and SUCCESSFUL EDITS. User leaves to VE may be an added action OR user who misses any next step is abandon/leave to VE
FYI, bug mentioned above has been split off into T432664: [BUG] Android and iOS edit 'saveSuccess' events missing `revision_id` value in event.editattemptstep, so we will investigate and fix as a part of that task.
Apps Visual Editor Handoff Instrumentation T431812
Dependencies where we still need to map how we will be joining our app data in event.editattempstep with MobileWeb/Visual Editor data generated by users coming from the apps are noted throughout deck, to be updated when we have more info.