Using Simplified ID Merge API for Non-Browser ID Linking
kapa.ai We're using the Simplified ID Merge API. On user login, right after calling the standard identify(user_id), we fire an additional custom event from the client. Its sole purpose is to link a server-side identity (a name+phone hash) to the user. For this event, we set $user_id to the logged-in user's ID and $device_id to our custom hash, which is different from the SDK's current browser ID. Is this a valid approach to use the client to trigger a merge for a non-browser-native ID, or are there potential side effects we should be aware of?