The Merge Flow empowers merchants to seamlessly manage multiple registration and update sources, providing enhanced control over user merging.

📚 In this article...
Common Use Cases

Merge Flow Configuration

Common Use Cases:

• A user is registered from two sources with different unique identifiers, such as a phone number and an email address, resulting in an error when attempting to update their details.
• A user is registered as an email subscriber and also as a member with a phone number, resulting in an error when attempting to update their details.

For example, if a member registers through a Wi-Fi integration using only their email and later registers at the POS with a phone number, the system flags the duplicate identifier when the user updates their details in the customer portal. The system then verifies the user via 2FA on the existing identifier. Once verified, the Merge Flow combines the profiles into a single user, migrates all associated assets, and ensures that any updated member details are transferred to the merged profile, keeping the most recent information intact for a seamless and cohesive experience.

Note: The new Merge Flow is available exclusively in the customer portal with full registration mode enabled.

Merge Flow Configuration

1. Enable Merge Duplicates

   • Go to the Registration Screen in the Advanced Settings section.
   • Enable the Merge Duplicates flag.
   • (Optional) Customize the prompt messages that will be displayed to users when the Merge Flow is triggered.
     
     
     
     

2. Check Full Registration Mode

   • Open the Customer Profile Screen.
   • Ensure that Full Registration Mode is turned on.
   • If it is not enabled, activate it.
   • Save the settings in the Customer Portal.

3: Configure Member Already Exists Event

When the system detects that a member already exists with the same identifier during an updateMember request, it now captures this as an event. A new trigger is available: Member Already Exists, with the condition: Conflicting Identifier.
(Conflicting Identifier = when two profiles use the same email or phone number.)

• Create a new HUB rule
  • Select the trigger Member Already Exists.
    
    
• Define Rule Cases
  • Handle different identifiers separately (for example, phone number vs. email).

     

  • Add the Conflicting Identifier condition.

    • For email conflicts, set up an SMS action.

    • For phone number conflicts, set up an email action.
      
      

  • Exclude Customer Portal Source

    • Add an additional condition: Source Name is not CustomerPortal.

    • This ensures conflicts triggered directly from the Customer Portal are ignored, since those cases are already handled natively within the Merge Flow.
      
      

  • Prompt Members to Merge Profiles
    • Automatically notify members when a conflict is detected.

    • Include the mention MemberUpdateLinkUrl in each communication (SMS and Email).

      • This will send members a secure update form where they can review and update their details.