feat(analytics): onboarding checklist Segment events (TMCU-680)

[wachunei]

Description

Stacked on TMCU-610-shadowbox-checklist-logic (parent PR #28851).

Reason: TMCU-680 requires Segment-oriented tracking for the new wallet home post-onboarding checklist so product can measure funnel performance.

Solution:

• Home Viewed — Fires when the user views each checklist step, with interaction_type: onboarding_checklist, section_name per step (on_ramp, first_trade, notifications), and the same contextual fields as other home impressions (entry_point, visit_number, app_session_id, etc.) via useWalletHomeOnboardingChecklistHomeViewed.
• Ramps Button Clicked — On fund-step primary, location: onboarding_checklist plus standard ramp props (ramp_type, region, ramp_routing, is_authenticated, preferred_provider, order_count) via useWalletHomeOnboardingChecklistFundPress wired from AccountGroupBalance.
• Unified SwapBridge Button Clicked — Checklist trade primary passes a per-call swapButtonClickLocationOverride so location is onboarding_checklist without changing bridge session attribution (useSwapBridgeNavigation + goToSwapsFromOnboardingChecklist in Wallet).
• ActionLocation.ONBOARDING_CHECKLIST — Shared enum value for the onboarding_checklist location string.

Changelog

CHANGELOG entry: Recorded analytics events for the wallet home post-onboarding checklist (Home Viewed per step, Ramps Button Clicked, Unified SwapBridge Button Clicked with onboarding checklist location).

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/TMCU-680

Refs: #28851

Manual testing steps

Feature: Wallet home post-onboarding checklist analytics (TMCU-680)

  Scenario: Home Viewed fires per checklist step
    Given homepage sections v1 and the post-onboarding checklist AB treatment are enabled
    And the user is eligible and sees the checklist on wallet home
    When they land on the fund step, then advance to trade, then notifications
    Then Home Viewed fires with interaction_type onboarding_checklist and section_name on_ramp, first_trade, and notifications respectively (verify in analytics debugger or logs if available)

  Scenario: Add funds sends Ramps Button Clicked with checklist location
    Given the checklist fund step is visible
    When the user taps the fund primary (Add funds)
    Then Ramps Button Clicked includes location onboarding_checklist and standard ramp properties

  Scenario: Trade sends Unified SwapBridge Button Clicked with checklist location
    Given the checklist trade step is visible
    When the user taps the trade primary
    Then Unified SwapBridge Button Clicked includes location onboarding_checklist

Screenshots/Recordings

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Medium Risk
Adds new analytics events and changes swap/on-ramp click attribution paths; risk is mainly incorrect event properties or over/under-firing rather than user-facing breakage.

Overview
Adds Segment-style analytics for the wallet home post-onboarding checklist: fires HOME_VIEWED when each checklist step is shown (with interaction_type: onboarding_checklist and step-specific section_name).

Wraps the checklist fund primary action to emit RAMPS_BUTTON_CLICKED with location: onboarding_checklist before navigating to buy, and updates swaps navigation to accept a per-call location override so checklist trade clicks report onboarding_checklist without altering bridge session attribution. Also introduces ActionLocation.ONBOARDING_CHECKLIST and wires the new callbacks through AccountGroupBalance/Wallet, with new/updated unit tests for these tracking behaviors.

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

[wachunei]

bugbot run

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ 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 d64c94f. Configure here.}

[wachunei]

@copilot resolve the merge conflicts in this pull request

[wachunei]

@copilot resolve the merge conflicts in this pull request

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved and pushed in 0fd1a8f. I merged latest main, fixed all conflict markers, and this PR is mergeable again. No UI changes were introduced in this conflict-resolution merge (screenshot: N/A).

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeWalletPlatform, SmokeMoney, SmokeSwap, SmokeConfirmations
• Selected Performance tags: None (no tests recommended)
• Risk Level: medium
• AI Confidence: 82%

click to see 🤖 AI reasoning details

E2E Test Selection:
The PR introduces analytics instrumentation for the wallet home onboarding checklist (TMCU-680). Key changes:

1. Wallet/index.tsx (core wallet home screen): Refactored to use shared props objects for AccountGroupBalance and AssetDetailsActions, and added goToSwapsFromOnboardingChecklist with ActionLocation.ONBOARDING_CHECKLIST override. This is the main wallet home screen and any regression here would be critical.

2. AccountGroupBalance.tsx: The onFundPrimaryPress prop now uses useWalletHomeOnboardingChecklistFundPress(goToBuy) instead of goToBuy directly. While functionally equivalent (the hook calls goToBuy() after tracking), this wrapping could introduce issues if the hook has bugs.

3. useSwapBridgeNavigation/index.ts: Added optional swapButtonClickLocationOverride parameter to goToNativeBridge and goToSwaps. Backward compatible but touches the swap navigation flow.

4. WalletHomeOnboardingSteps.tsx: Added useWalletHomeOnboardingChecklistHomeViewed hook integration for analytics.

5. New analytics hooks and constants - primarily analytics, low functional risk.

Tag selection rationale:

• SmokeWalletPlatform: Wallet home screen (Wallet/index.tsx) is directly modified with refactoring and new callbacks. The onboarding checklist steps are part of this area.
• SmokeMoney: The fund/buy flow (goToBuy via ramp navigation) is wrapped with new analytics in useWalletHomeOnboardingChecklistFundPress. Ramps/buy flows need validation.
• SmokeSwap: The goToSwaps function has a new optional parameter and goToSwapsFromOnboardingChecklist is wired in the wallet home. Swap navigation needs validation.
• SmokeConfirmations: Required per tag descriptions when selecting SmokeSwap and SmokeMoney, as confirmations are part of those flows.

Performance Test Selection:
The changes are primarily analytics instrumentation (adding tracking events to existing flows) and a DRY refactor of the wallet home screen props. No new UI components are added, no list rendering changes, no state management changes that would affect performance. The new hooks are lightweight (useEffect + trackEvent calls). No performance impact is expected.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
90.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud