Description

Migrates the onboarding interest questionnaire from legacy Onboarding Interest Question Viewed/Submitted events to the shared Onboarding Question Viewed/Submitted MetaMetrics events with question_type: 'interest', completing mobile consolidation per segment-schema #590.

• OnboardingInterestQuestionnaire fires ONBOARDING_QUESTION_VIEWED / ONBOARDING_QUESTION_SUBMITTED with question_type: 'interest'.
• Submitted payload is unchanged aside from the discriminator: selected_interests, item_count, skipped, and optional account_type (no name).
• Removed unused ONBOARDING_INTEREST_QUESTION_* constants from MetaMetrics.events.ts.

Analytics note: Segment event names change for the interest step; property shapes are the same plus question_type. Dashboards keyed on Onboarding Interest Question * should filter on question_type: interest instead.

Changelog

CHANGELOG entry: null

Related issues

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

Related: https://github.com/Consensys/segment-schema/pull/590

Manual testing steps

Feature: Onboarding interest questionnaire generic analytics (TMCU-792)

  Scenario: user views the interest questionnaire
    Given the user is eligible for the onboarding interest questionnaire
    And the user has opted in to basic usage data on OptinMetrics

    When the interest questionnaire screen is shown
    Then analytics records Onboarding Question Viewed with question_type "interest"
    And account_type is included only when supplied by the route

  Scenario: user submits interests or skips
    Given the user is on the interest questionnaire

    When the user selects one or more interests and taps Continue
    Then analytics records Onboarding Question Submitted with question_type "interest"
    And selected_interests, item_count, and skipped false are included

    When the user taps Continue without selecting any interests
    Then analytics records Onboarding Question Submitted with question_type "interest"
    And selected_interests is empty, item_count is 0, and skipped is true

Unit tests:

• yarn run jest app/components/Views/OnboardingInterestQuestionnaire/OnboardingInterestQuestionnaire.test.tsx (19 passed)

Screenshots/Recordings

Before

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