Description

Implements analytics instrumentation for the Predict World Cup experience so the Predict team can measure World Cup feed engagement and entry point performance during the tournament.

This PR:

• Adds MetaMetrics events and Predict analytics/controller trackers for:
  • Predict World Cup Screen Viewed
  • Predict World Cup Screen Tab Changed
  • Predict World Cup Banner Viewed
  • Predict World Cup Banner Clicked
• Tracks the dedicated World Cup screen view with entry_point and the resolved initial predict_feed_tab.
• Tracks World Cup screen tab changes with entry_point and selected predict_feed_tab.
• Tracks main Predict feed World Cup banner impressions and clicks with entry_point: predict_feed.
• Preserves existing deep link attribution behavior, including utm_source suffixes such as deeplink_twitter.
• Keeps the main Predict feed World Cup tab on the existing Predict Feed Viewed session analytics path through PredictFeedSessionManager.

Companion Segment schema changes are expected in segment-schema for the four new mobile events. No new mobile analytics property keys are introduced.

Changelog

CHANGELOG entry: null

Related issues

Fixes: PRED-878

Manual testing steps

Feature: Predict World Cup analytics

  Scenario: user opens the World Cup screen from the main Predict feed banner
    Given Predict World Cup is enabled
    And the main Predict feed banner is visible

    When user views the banner
    Then analytics emits "Predict World Cup Banner Viewed" with entry_point "predict_feed"

    When user taps the banner
    Then analytics emits "Predict World Cup Banner Clicked" with entry_point "predict_feed"
    And the World Cup screen opens
    And analytics emits "Predict World Cup Screen Viewed" with entry_point "predict_feed"

  Scenario: user opens the World Cup screen from a deep link
    Given Predict World Cup is enabled

    When user opens a Predict deep link with feed "world-cup", tab "live", and utm_source "twitter"
    Then the World Cup screen opens on the "live" tab
    And analytics emits "Predict World Cup Screen Viewed" with entry_point "deeplink_twitter"
    And analytics includes predict_feed_tab "live"

  Scenario: user changes tabs on the World Cup screen
    Given the World Cup screen is open

    When user selects a different World Cup tab
    Then analytics emits "Predict World Cup Screen Tab Changed"
    And analytics includes the selected predict_feed_tab

Screenshots/Recordings

N/A. Analytics instrumentation only; no user-facing visual changes.

Before

N/A

After

N/A

Automated testing

• yarn jest app/components/UI/Predict/controllers/PredictAnalytics.test.ts app/components/UI/Predict/controllers/PredictController.test.ts app/components/UI/Predict/components/PredictWorldCupMainFeedBanner/PredictWorldCupMainFeedBanner.test.tsx app/components/UI/Predict/views/PredictWorldCup/PredictWorldCup.test.tsx app/components/UI/Predict/services/PredictFeedSessionManager.test.ts app/core/DeeplinkManager/handlers/legacy/__tests__/handlePredictUrl.test.ts
• yarn generate-method-action-types
• yarn prettier --check on touched files
• git diff --check

Note: yarn lint:tsc was run and failed on unrelated existing Bridge, Trending, transaction-pay, and delegation type errors outside this change.

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.