Track marketing notification opens

[peachbits]

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

• Tested on iOS device
• Tested on Android device
• Tested on small-screen device (iPod Touch)
• Tested on large-screen device (tablet)

No visual changes — this is push-payload parsing plus navigation/analytics, no new UI.

Description

Recognizes a marketing push notification and, when the user opens the app from it, reports the campaign open to analytics and navigates to an optional deep link.

• parsePushMessage now recognizes a { type: 'marketing', campaignId, url? } FCM data payload and returns a new MarketingLink deep-link type. An unrecognized or malformed url degrades to track-only.
• On open (background tap or cold start), the deep-link handler dispatches a Marketing_Notification_Opened PostHog event carrying the campaignId, then navigates to the optional deep link through the existing handler.
• Adds a PushMessageParser unit test.

Verified with the unit test and end-to-end on a real Android device against a local push server: the open was tracked in PostHog and the deep link navigated.

The sending side lives in edge-push-server (companion PR EdgeApp/edge-push-server#78). This PR is the receiving side and is safe to merge on its own — it only acts on notifications that carry the marketing payload.

---

Note

Medium Risk
Push URLs can drive navigation for all campaign recipients; the allow-list mitigates operator error or compromised send keys, but expanding destinations or parser gaps could still route users to sensitive flows.

Overview
Marketing push notifications (type: marketing with campaignId and optional url) are now recognized when the user opens the app from the notification.

parsePushMessage returns a new MarketingLink deep-link type. Optional URLs are parsed through the existing deep-link parser; only allow-listed campaign destinations (home, wallets, earn, markets, swap, buy/sell quotes, promotions, fund-account modal) trigger navigation—sensitive or unlisted targets (recovery, edge-login, arbitrary scenes, provider returns) are track-only. Wrapped deep.edge.app URLs are judged by their inner destination; malformed URLs still record the open.

On handle, DeepLinkingActions logs Marketing_Notification_Opened to analytics with campaignId, then navigates via the shared link handler when a permitted link was parsed. PushMessageParser.test.ts covers destinations, refusals, attribution wrappers, and existing price-change payloads.

^{Reviewed by Cursor Bugbot for commit 1cdb570. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Scene allow-list ignores nested screens

Medium Severity

isAllowedMarketingLink only checks a scene's sceneName, then handleLink passes the full query into navigate. An allowed edge://scene/edgeTabs URL can therefore set screen to devTab or extraTab. Those tabs are hidden in the menu (ENV.DEV_TAB / missing extraTab config) but remain registered, so a campaign can open the production debug scene or mount ExtraTabScene, which throws when config.extraTab is missing.

 

^{Reviewed by Cursor Bugbot for commit ff38b7b. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 83177c4. Configure here.}