Description

entry_point: "predict_feed" correctly identifies that a trade originated from the Predict feed, but it carries no information about where within the feed the trade came from. We already track predict_feed_tab (e.g. "world-cup", "trending", "sports") and predict_screen (e.g. "world_cup") on Predict Feed Viewed, but those properties were never forwarded to Predict Trade Transaction or Predict Market Details Opened — so trade volume and conversion could not be segmented by tab or surface in Mixpanel.

This PR forwards predict_feed_tab and predict_screen from the feed market cards through to the trade and market-details events, flowing through the same path entry_point already uses:

market card → PredictMarketDetails route params → PredictBuyPreview → analyticsProperties → Predict Trade Transaction

What it does:

• Source screens set the values: PredictFeed passes the active tab key as predict_feed_tab; PredictWorldCup passes the active tab key plus predict_screen: "world_cup".
• Threading layer mirrors the existing entry_point / transactionActiveAbTests plumbing through PredictMarket and the four card variants (PredictMarketSingle, PredictMarketMultiple, PredictMarketSportCard, PredictCryptoUpDownMarketCard), the navigation param types, PredictMarketDetails, and PredictBuyPreview / PredictBuyWithAnyToken.
• Analytics layer emits the two properties (only when present) on Predict Trade Transaction and Predict Market Details Opened.

What does not change:

• entry_point values are unchanged (feed-originated trades remain "predict_feed").
• No new event names.
• No changes to surfaces outside of PredictFeed and PredictWorldCup.

Note: the values are forwarded on the primary buy paths (card tap → details → buy, and direct card buy). The secondary "Outcomes tab inside Market Details" buy path still carries entry_point but not the new tab/screen, since extending it would touch additional nested components beyond the scope of this ticket.

Changelog

CHANGELOG entry: null

Related issues

Fixes: PRED-938

Manual testing steps

Feature: Predict feed tab and screen analytics attribution

  Scenario: user trades from a Predict feed tab
    Given the user is on the Predict feed on the "trending" tab
    When the user taps a market card and places a trade
    Then the "Predict Trade Transaction" event includes predict_feed_tab "trending"
    And the "Predict Market Details Opened" event includes predict_feed_tab "trending"
    And entry_point remains "predict_feed"

  Scenario: user trades from the World Cup hub
    Given the user is on the Predict World Cup screen on a given tab
    When the user taps a market card and places a trade
    Then the "Predict Trade Transaction" event includes that tab key as predict_feed_tab
    And the event includes predict_screen "world_cup"

Screenshots/Recordings

No UI changes — analytics-only enrichment.

Before

N/A

After

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
• I've tested with a power user scenario
• I've instrumented key operations with Sentry traces for production performance metrics

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.