GoodWallet 2 Welcome Offer Modal & Redirect

[decentralauren]

Business Description

In order to begin migrating users from GW1 to GW2, we will make an offer to a select number of users to voluntarily start using the new wallet. The target number of users to migrate is 20k.

1. This offer will be made via a modal that is presented to a segmented number of users. That segmentation will be managed in Post-Hog and will be based on a combination of user behavior (including but not limited to how GW1 is accessed) and location
2. The modal will have a CTA that, when clicked, redirects the user in the same browser tab to the GoodWallet2 URL and begins the login process for GW2. See GW2 Figma screens for reference of what will happen after the user clicks the CTA
3. Users will still be able to access their GoodWallet1 at any point by navigating to the current GoodWallet URL

Detailed Description of Functionality

This ticket covers 3 specific activities:

1. Post-Hog Event Tracking

• [x] event tracking requirements needed in Post-Hog for segmented offers

3. Modal Design & Implementation

• See Figma design link below for modal design

5. Product Tracking (GA / Amplitude)

• Event tracking for CTA clicks
• Event tracking for "do not show again" [ See Comment from @drptiago below]

Technical Implementation

• [x] Create a newCustomDialog and apply design
• [ ] remember in storage 'do not show again'
• [x] add events
  • migration_invited
  • migration_accept
  • migration_denied
• [ ] create a feature-flag show-welcome-offer in posthog
• [ ] trigger modal on dashboard (TBD: either solely based on feature-flag, or feature-flag should be matched with wallet-addresses)

Design Reference

See Figma for full Welcome Rewards flow from GW1 to GW2.

Acceptance Criteria

Specify criteria that will be used to determine if the feature meets the requirements and functions correctly.

• [ ] (Should include a list of testing points for QA how to verify design/functionality) filled out by the development team or can contain suggestions._

Test Cases

Specify the happy path and unhappy path scenarios to test to verify the feature works as expected.