Description

In the "trade with any token" flow, the custom confirm button performs its own validation but was not tracking when standardized blocking alerts (e.g. useInsufficientPayTokenBalanceAlert, useNoPayTokenQuotesAlert) fire. This meant validation errors like "insufficient funds" and "insufficient source token balance for relay deposit" — which account for the majority of deposit failures — were invisible in Mixpanel.

This PR adds two useEffect hooks in PerpsOrderViewContentBase that fire PERPS_ERROR analytics events when:

1. Blocking pay-token alerts appear (e.g. insufficient balance for relay quote totals, no quotes available) — tracked as error_type: 'validation' with the alert's human-readable message.
2. Insufficient pay-token balance warning appears (custom margin-only check) — tracked as error_type: 'warning' with standardized insufficient_balance key.

Both events include error_type, error_message / warning_message, screen_name, and screen_type properties, following the existing PERPS_ERROR schema.

Note: the UI integration (button disabling + alert message rendering) was already in place. This PR adds only the missing analytics tracking and corresponding unit tests.

Changelog

CHANGELOG entry: null

Related issues

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

Manual testing steps

Feature: Pay-token validation error tracking in analytics

  Scenario: user sees blocking pay-token alert tracked in analytics
    Given the user is on the Perps order screen with "trade with any token" enabled
    And the user has selected a custom payment token (not Perps balance)

    When the relay quote returns an insufficient balance alert
    Then a PERPS_ERROR event fires with error_type "validation" and the alert message
    And the Place Order button is disabled

  Scenario: user sees no analytics event when using Perps balance
    Given the user is on the Perps order screen
    And the user is paying with their Perps balance (not a custom token)

    When blocking pay-token alerts would otherwise fire
    Then no PERPS_ERROR event is tracked (hasCustomTokenSelected is false)

Screenshots/Recordings

N/A — no UI changes; analytics-only.

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.