Add simplified sync pixels

[MiSikora]

Task/Issue URL: https://app.asana.com/1/137249556945/project/1216103556496795/task/1216422585541219?focus=true
Tech Design URL (if applicable): N/A
API Proposals URL(s) (if applicable): N/A

Description

Brings the simplified Sync (v2) setup flow to pixel parity with the legacy setup flow and with iOS, adds a set of new Sync settings pixels, and tags sync setup pixels with a ui_version parameter so each pixel records whether it came from the simplified or the legacy UI. It also changes one setup behavior so restoring a previous session reuses the current device (this is the legacy behavior).

New Sync settings pixels:

• Opening the Sync settings screen fires m_settings_sync_open.
• Tapping "Sync This Device" fires m_settings_sync_back_up_this_device_tapped.
• Starting the recover synced data flow fires m_settings_sync_recover_synced_data_tapped.
• Confirming recovery on the "Recover your synced data" screen fires m_settings_sync_recovery_confirmed_tapped.
• The prompt that asks whether to sync this device or another device fires m_settings_sync_another_device_prompt_shown when it appears.
• Choosing an option on that prompt fires m_settings_sync_another_device_prompt_option_tapped, with an option of this_device_only or sync_another_device.

Simplified Sync setup parity:

• The simplified scan and manual entry screens now fire the setup pixels that previously only fired in the legacy flow, including the scan QR screen shown (sync_setup_scan_qr_screen_shown), the barcode and manual code screens shown, code recognized success and failure, setup finished, setup failed, and setup abandoned.
• The deep link setup path now fires its started, success, and abandoned pixels from the simplified flow.
• Account switching now fires its ask to switch, accepted, cancelled, and switched pixels from the simplified flow.
• Restoring a previous session now fires the auto restore success and failure pixels.
• A sync_login pixel is fired on every successful setup.

ui_version parameter:

• Sync setup, login, signup, error, account switching, and auto restore pixels now include a ui_version parameter, set to v2 when the simplified sync UI is enabled (useSimplifiedSync) and v1 otherwise.
• The sync-setup wide event carries the same ui_version value in its metadata.

Behavior change:

• When restoring a previous session from Sync settings, the stored recovery payload's device id is now passed through when the code is processed, so the restore reuses the existing device record instead of registering a new device.

Note

I added only some basic tests that verify the ui_version parameter. I'll expand them in a followup PR after adding TestParameterInjector.

Steps to test this PR

I think there are too many pixels to write a comprehensive testing scenario. I documented Pixels for the simplified UI in this task. I tested it in the following way:

1. Set up Device A with the useSimplifiedSync feature flag enabled.
2. Set up Device B with the useSimplifiedSync feature flag disabled.
3. Split the terminal into 2 pans and run adb -s <DEVICE_ID> logcat -s RxBasedPixel:V in each pane.
4. Have a Device C that you'll be able to use to show QR codes, etc.
5. Run the same user journeys using both devices and compare logged pixels.

UI changes

N/A

---

Note

Low Risk
Changes are mostly telemetry definitions and pixel firing in sync setup UI; the only functional change is passing a preserved device id on session restore, which aligns with legacy behavior and is localized to sync account processing.

Overview
Adds analytics parity for the simplified Sync setup UI and new Sync settings telemetry, plus a small restore behavior fix.

ui_version on sync pixels: Setup, login, signup, errors, account switching, and auto-restore events now include ui_version (v1 / v2 from useSimplifiedSync). The sync-setup wide event adds the same field in metadata.

New settings pixels: Definitions and firing for opening Sync settings, backup-this-device, recover-data taps/confirmations, and the “this device vs another device” prompt (shown + option tapped).

Simplified flow pixel wiring: v2 screens and ProcessSyncCodeViewModel now emit the setup pixels that legacy already had (scan QR shown, parse success/failure, finished/failed/abandoned, deep link lifecycle, account switch, auto-restore success/failure, sync_login). SyncCodeSource replaces raw code strings in contracts so scan/paste/deep link/restored paths are distinguished for pixels and restore logic.

Restore behavior: Restoring a previous session passes the preserved device id from auto-restore payload into processCode so the existing device record is reused.

^{Reviewed by Cursor Bugbot for commit 1e1965f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[MiSikora]

• Simplified sync translations #9414
• Parameterize sync pixels tests #9413
• Apply correct edge to edge handling in simplified sync #9412
• Add simplified sync pixels #9401 👈 (View in Graphite)
• Clean up sync code before integrating pixels #9386
• Avoid signing out of a device when renaming it #9374
• Handle simplified sync deep linking #9373
• Handle restore on reinstall sync scenario #9368
• Simplified sync UI updates #9363
• Handle v1 exchange sync codes #9362
• Handle sync recovery basic scenario #9356
• Add syncing with another device logic and navigation #9343
• Add generic handling of v1 sync errors #9337
• Add sync with another device UI #9334
• Detect scanned QR sync codes #9333
• Handle sync code pasting #9332
• Refactor simplified sync class names #9329
• Handle sync logic on the displayed QR code page #9328
• Display sync QR code in simplified sync #9321
• Make remove device dialog destructive #9317
• Mitigate sync settings UI race condtions #9316
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Privacy Review task: https://app.asana.com/0/69071770703008/1217193904757982

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

There are 3 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f8b12f6. Configure here.}