Change Details

**User Story** - As the Editing and App Growth teams - We want to join two events that are happening on different platforms into one editing session - So that we can track the full edit session funnel across platforms - Which will mean it’s treated as one coherent flow This task relates to modifying the schema to track sessions coming from the apps in editattemptstep, so that the Init event that originates in the app is joined with web. This will enable us to understand where a user came from, and therefore track users who attempt to make an edit but may drop off / fail along the way. Please could the Editing team pick up this task to enable The App Growth team to fully track the editing journey between app and web?

**User Story** - As the Editing and App Growth teams - We want to join two events that are happening on different platforms into one editing session - So that we can track the full edit session funnel across platforms - Which will mean it’s treated as one coherent flow This task relates to modifying the schema to track sessions coming from the apps in editattemptstep, so that the Init event that originates in the app is joined with web. This will enable us to understand where a user came from, and therefore track users who attempt to make an edit but may drop off / fail along the way. Please could the Editing team pick up this task to enable The App Growth team to fully track the editing journey between app and web? --- **Derived Requirement** Ensure VisualEditor edit session instrumentation includes a non-empty `app_install_id` in the web `integration=page` Init event when an editing session originates from a Wikimedia app, allowing the app and web events to be joined into a single editing session. **Test Steps** **Test Case 1: Ensure app-originated editing sessions include app installation information** 1. Open the Wikimedia app on a supported mobile device or emulator. 2. Start an editing journey in the app that transitions to the web VisualEditor. 3. Complete the action that opens the web editing experience. 4. Monitor the instrumentation events generated by the web editing experience. 5. Locate the `integration=page` Init event associated with the editing session. 6. Inspect the event parameters. 7. Verify that `app_install_id` is present and contains a non-empty value. 8. **✅❓❌⬜ **AC1:** The web `integration=page` Init event for an app-originated editing session contains a non-empty `app_install_id` value.** == QA Results - TestFlight | **AC** | **Status** | **Details** | | ----- | ----- | ----- | | 1 | ✅|T432853#12290638

**User Story** - As the Editing and App Growth teams - We want to join two events that are happening on different platforms into one editing session - So that we can track the full edit session funnel across platforms - Which will mean it’s treated as one coherent flow This task relates to modifying the schema to track sessions coming from the apps in editattemptstep, so that the Init event that originates in the app is joined with web. This will enable us to understand where a user came from, and therefore track users who attempt to make an edit but may drop off / fail along the way. Please could the Editing team pick up this task to enable The App Growth team to fully track the editing journey between app and web? --- **Derived Requirement** Ensure VisualEditor edit session instrumentation includes a non-empty `app_install_id` in the web `integration=page` Init event when an editing session originates from a Wikimedia app, allowing the app and web events to be joined into a single editing session. **Test Steps** **Test Case 1: Ensure app-originated editing sessions include app installation information** 1. Open the Wikimedia app on a supported mobile device or emulator. 2. Start an editing journey in the app that transitions to the web VisualEditor. 3. Complete the action that opens the web editing experience. 4. Monitor the instrumentation events generated by the web editing experience. 5. Locate the `integration=page` Init event associated with the editing session. 6. Inspect the event parameters. 7. Verify that `app_install_id` is present and contains a non-empty value. 8. **✅❓❌⬜ **AC1:** The web `integration=page` Init event for an app-originated editing session contains a non-empty `app_install_id` value.** == QA Results - TestFlight | **AC** | **Status** | **Details** | | ----- | ----- | ----- | | 1 | ✅|T432853#12290638