Description

Mobile only kept deep-link UTM / attribution_id in memory (via AppStateEventListener / processAttribution). After the first foreground pass the deeplink is often cleared, and onboarding → Wallet Setup Completed usually happens in a later session, so acquisition data was lost and could not be attached to conversion analytics.

This PR adds a dedicated Redux slice for attribution with redux-persist + MMKV (separate from root filesystem persist). It exposes saveAttribution, clearAttribution, and expireAttributionIfStale (default 7-day TTL). Data is written when:

• AppStateEventListener.processAppStateChange runs after processAttribution() (still gated by dataCollectionForMarketing inside processAttribution), and
• handleDeeplink sees a URI with acquisition params while marketing consent is on (covers cold open / session split).

Privacy: No persistence when marketing consent is off; persisted data is cleared when the user opts out of marketing data collection and when onboarding is cleared (CLEAR_ONBOARDING). Root persist blacklists attribution so it is not double-stored with the nested MMKV persist.

Includes unit tests for the slice (save / clear / expire), marketing sagas, deeplink handler, app state listener, and persistConfig blacklist expectations

Jira: https://consensyssoftware.atlassian.net/browse/TO-717

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: Persist deep-link attribution (marketing consent on)

  Scenario: User opens app from acquisition deeplink and survives process restart
    Given marketing data collection for analytics is enabled
    And the app handles a deeplink URL that includes utm_source (and optionally attribution_id/other utm_* params)

    When the user fully terminates the app and launches MetaMask again without using the same deeplink

    Then persisted Redux state under the attribution slice still contains the saved acquisition fields (and capturedAt) until TTL or opt-out

  Scenario: User disables marketing consent after attribution was saved
    Given marketing data collection for analytics was enabled
    And attribution had been persisted from a prior deeplink or foreground attribution capture

    When the user turns off marketing data collection for analytics in settings

    Then persisted attribution is cleared (no acquisition payload remains in the attribution slice)

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.