How to Merge Two Distinct User Profiles Effectively

Hi William D., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋

Based on the information provided in the knowledge sources, I can answer your question about merging two distinct user profiles in Mixpanel.Unfortunately, Mixpanel does not provide a direct way to merge two distinct user profiles. According to the Identifying Users (Simplified) FAQ, it is not possible to merge two $user_ids together using the Simplified API. Mixpanel recommends against doing this in general, as it adds complexity to the identity resolution strategy.Instead, Mixpanel recommends having a single, unchanging $user_id for each user and pointing all other IDs for that user to that single $user_id. This approach helps maintain a cleaner and more straightforward identity management system.If you're using an older version of Mixpanel's identity management system (Original ID Merge), there is a $merge API event that allows merging of any 2 ID clusters, but this is limited to a maximum of 500 total IDs.For projects using the newer Simplified ID Merge system, the recommendation is to avoid merging distinct user profiles and instead focus on maintaining a consistent $user_id for each unique user from the beginning.If you need to consolidate data from multiple profiles, you may want to consider exporting the data, merging it manually according to your specific needs, and then reimporting it as a single user profile. However, this process would require careful planning and execution to ensure data integrity.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

Yes, if you're using an older version of Mixpanel's identity management system, specifically the Original ID Merge system, you can indeed use the merge event allows you to merge any two identifiers together. This event is only useful for projects using the Original ID Merge system and has no functionality in other ID management systems.Here's what you need to know about using the merge event can only be sent via the https://api.mixpanel.com/import endpoint, which is protected by your project's API secret.3. The merge will be successful as long as it doesn't result in an ID cluster exceeding 500 total IDs.4. The merge event payload::LBKSLBKS```LBKS{ "event":: "distinct_ids": [ "user_id_1", "user_id_2" ] } }```Remember that this method is only available for projects using the Original ID Merge system. If you're unsure about your current ID management version, you can check it in your Project Settings.Also, keep in mind that Mixpanel recommends using the newer Simplified ID Merge system for new projects, as it provides a more straightforward approach to identity management. However, if you're working with an existing project on the Original ID Merge system, the $merge API is available for your use.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

Based on the information you've provided, it appears that you are using the oldest version of Mixpanel's identity management system, which is referred to as Legacy ID Management.According to the Identity Management Overview, Mixpanel has three versions of ID management:1. Legacy ID Management (prior to March 2020) 2. Original ID Merge (released in March 2020) 3. Simplified ID Merge (released in March 2023)When you see the message "This project does not have ID Merge enabled," it indicates that your project is using the Legacy ID Management system. This is confirmed in the Migrating to Simplified ID Merge documentation, which discusses the limitations of Legacy ID Management.With Legacy ID Management:1. You can only alias a User ID to an Anonymous ID once, typically on the first device where they started using your product. 2. Subsequent attempts to alias the same User ID to a different Anonymous ID (generated from a different platform or device) will fail. 3. There's no retroactive identity merging feature, which can lead to orphaned users when users interact across multiple sessions, devices, and platforms.It's important to note that this system is quite limited compared to the newer ID Merge systems. If you're only tracking authenticated users (i.e., not tracking events while users are anonymous), you might not need the more advanced features of the newer systems.If you're considering updating your identity management approach, you might want to look into setting up a new Mixpanel project with either the Original or Simplified ID Merge system, as described in the migration guide.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

I apologize for the confusion in my previous responses. Based on the information you've provided about your project stating "This project does not have ID Merge enabled," I need to correct my earlier statements.According to the Identity Management Overview, your project is using the Legacy ID Management system, which is the oldest version of Mixpanel's identity management.In this case, you cannot use the merge event is only available for projects using the Original ID Merge system, which your project does not have enabled.For projects on Legacy ID Management, the options for managing user identity are more limited. As stated in the documentation for Legacy ID Management, you can only alias a User ID to an Anonymous ID once, typically on the first device where they started using your product.If you need more advanced identity management features, including the ability to merge user profiles, you would need to consider migrating to a new Mixpanel project with either the Original or Simplified ID Merge system enabled. This process is described in the migration guide.I apologize again for any confusion my previous responses may have caused. Thank you for providing the additional information about your project's settings, which helped clarify the situation.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.