refactor(perps): differentiate screen_type for perps screen viewed events

[michalconsensys]

Description

Previously, both PerpsTabView (the Perps tab on wallet home screen) and PerpsHomeView (the dedicated Perps home screen) were using the same screen_type value (homescreen) for PERPS_SCREEN_VIEWED analytics events. This made it impossible to distinguish between the two screens in analytics dashboards.

This PR introduces two distinct screen type values:

• wallet_home_perps_tab - Used when viewing the Perps tab within the wallet home screen
• perps_home - Used when viewing the full dedicated Perps home screen

The legacy HOMESCREEN value is preserved with a comment indicating it should not be used for new implementations.

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/TAT-1835

Manual testing steps

Feature: Perps screen analytics differentiation

  Scenario: user views Perps tab on wallet home
    Given user is on the wallet home screen
    When user taps on the Perps tab
    Then PERPS_SCREEN_VIEWED event is fired with screen_type: "wallet_home_perps_tab"

  Scenario: user navigates to Perps home screen
    Given user is on any screen in the app
    When user navigates to the Perps home screen (via manage balance or navigation)
    Then PERPS_SCREEN_VIEWED event is fired with screen_type: "perps_home"

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.

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

Separates analytics tracking to uniquely identify Perps views across app surfaces.

• Updates PerpsTabView to emit PERPS_SCREEN_VIEWED with screen_type wallet_home_perps_tab
• Updates PerpsHomeView to emit PERPS_SCREEN_VIEWED with screen_type perps_home
• Extends constants/eventNames.ts with WALLET_HOME_PERPS_TAB and PERPS_HOME; marks HOMESCREEN as legacy

^{Written by Cursor Bugbot for commit a3fbd97. This will update automatically on new commits. Configure here.}

[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.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokePerps
• Risk Level: low
• AI Confidence: 90%

click to see 🤖 AI reasoning details

The changes are limited to analytics event property values in the Perps feature:

1. eventNames.ts: Added two new screen type values (WALLET_HOME_PERPS_TAB and PERPS_HOME) and marked the old HOMESCREEN as legacy
2. PerpsHomeView.tsx: Changed analytics event from HOMESCREEN to PERPS_HOME
3. PerpsTabView.tsx: Changed analytics event from HOMESCREEN to WALLET_HOME_PERPS_TAB

These are purely analytics/tracking changes that:

• Don't modify any UI components or user-facing behavior
• Don't change business logic or data flow
• Are isolated to the Perps feature module
• Only affect what analytics data is sent (screen type naming)

The SmokePerps tag is appropriate because:

• The changes are in Perps-specific files
• E2E tests exist for Perps functionality (perps-add-funds.spec.ts, perps-limit-long-fill.spec.ts, etc.)
• Running these tests will verify the Perps feature still works correctly after the analytics changes

No other tags are needed since the changes don't affect any other features or core functionality.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud