Thank you for your question about user identification in Mixpanel using the Unity SDK. I understand you're experiencing issues with merging user identities after calling Mixpanel.Identify(). Let me address your concerns based on the information available.
Unfortunately, the Unity SDK for Mixpanel does not currently support Simplified ID Merge. According to the Mixpanel documentation, "All Mixpanel Client-Side SDKs support Simplified ID Merge except for Unity SDK."
This explains why you're not seeing the expected behavior of merging the anonymous user (with the random distinct ID) and the identified user (with ID 1234) after calling Mixpanel.Identify().
To resolve this issue, you have a few options:
1. Use a different SDK: If possible, consider using a different Mixpanel SDK that supports Simplified ID Merge.
2. Implement server-side tracking: You could implement server-side tracking where you have more control over the identity management process.
3. Use the Original ID Merge system: If you need to stick with the Unity SDK, you might need to use the Original ID Merge system instead of Simplified ID Merge. However, this would require creating a new project with Original ID Merge enabled.
4. Contact Mixpanel Support: Given that this seems to be a limitation of the Unity SDK, you might want to reach out to Mixpanel's support team for further guidance or to inquire about future support for Simplified ID Merge in the Unity SDK.
For the Unity SDK, the current recommendation for managing user identity involves using Mixpanel.Identify() and Mixpanel.Reset() as described in the Mixpanel Unity SDK documentation. However, these methods may not provide the same functionality as Simplified ID Merge in terms of automatically linking anonymous and identified users.
I apologize that I don't have a more direct solution for your issue. The limitation of the Unity SDK in supporting Simplified ID Merge is the root cause of the behavior you're experiencing.
