We are migrating from an old identify system to a new one. How can we effectively migrate existing users to the new system? Is it possible to update the distinct_id for these existing users to align with the new system?
Hi Amal N., 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> đź‘‹
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
Based on the information provided in the knowledge sources, I can offer some guidance on migrating from an old identification system to a new one in Mixpanel. However, it's important to note that the process depends on which ID management system you're currently using and which one you're migrating to.Mixpanel supports two versions of the ID Merge API: Simplified ID Merge and Original ID Merge. If you're considering migrating to the Simplified ID Merge system, here are some key points to consider: 1. Migration to Simplified ID Merge requires setting up a new empty Mixpanel project. It's not possible to automatically convert an existing project with data from Legacy or Original ID Merge to Simplified ID Merge Deciding to Migrate.2. For backfilling historical data, you have several options:
- Use Mixpanel's HTTP API
- Use the Mixpanel Warehouse Connector
- Use a Customer Data Platform (CDP) Backfilling Historical Data3. When migrating, you need to ensure that your historical data is properly formatted for the Simplified ID Merge system. This may involve transforming your data to include both $device_id and $user_id properties, which are essential for identity merging in the new system Understanding Simplified ID Merge.Regarding updating the distinct_id for existing users: In the Simplified ID Merge system, the distinct_id is automatically set by Mixpanel based on the $user_id and $device_id properties. The $user_id is always set as the distinct_id for the user when present. If only $device_id is present, it will be used as the distinct_id with a "$device:" prefix Understanding Simplified ID Merge.It's important to note that once there is data in your project, you cannot change the Identity Merge API version Identity Merge APIs.Given the complexity of this migration process, it's recommended to carefully plan your migration strategy and consider reaching out to Mixpanel's support team for guidance specific to your implementation.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ 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'm sorry, but it seems like your question was not fully submitted. Could you please provide more details or clarify what you need help with?
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Is it possible to link two identified users together in Mixpanel? If so, what is the best way to merge or associate their data?
Let me check the knowledge base for you again. One moment! đź“š
Yes, it is possible to link two identified users together in Mixpanel, but the method depends on the ID management system you're using.1. Original ID Merge: You can use the $merge API event to merge any two ID clusters, as long as it does not exceed 500 total IDs. This event can only be processed when sent via the /import API directly. Here's an example of a merge event payload: LBKS{ "event": "$merge", "properties": { "$distinct_ids": [ "user_id_1", "user_id_2" ] } }LBKSOriginal ID Merge2. Simplified ID Merge: In this system, it's not possible to merge two $user_ids together. 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. When a $user_id and a $device_id is detected in the same event for the first time, it triggers a merge of the 2 IDs.```<?php
// import dependencies
require 'vendor/autoload.php';
// create an instance of the Mixpanel class $mp = Mixpanel::::getInstance("YOUR_PROJECT_TOKEN");
// when a device_id pair is detected in the same event for the first time, // a merge is triggered to map the 2 IDs together. device_id' => "ANON_ID", '$user_id' => "USER_ID" ));
?> ```Simplified ID MergePlease note that the best method to merge or associate user data depends on your specific use case and the ID management system you're using.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ 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, it is possible to re-identify a user in Mixpanel, but the method depends on the ID management system you're using.1. Original ID Merge: You can use the alias method to create a new alias for a user. This can be useful if you want to change the identified user ID. However, once you've aliased two IDs, you can't change the alias later. Here's an example of how to use the alias method: LBKSmixpanel.alias("NEW_ID", "EXISTING_ID");LBKSOriginal ID Merge2. Simplified ID Merge: In this system, you can use the identify method to set a new $user_id for a user. This will link the new $user_id with the existing $device_id for that user. Here's an example of how to use the identify method: LBKSmixpanel.identify("NEW_ID");LBKSSimplified ID MergePlease note that the best method to re-identify a user or change an identified user ID depends on your specific use case and the ID management system you're using.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ 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! đź“š
In Mixpanel, the concept of "alias" is used to link two non-anonymous Distinct IDs. It creates an "alias" to another Distinct ID already present in the identity cluster and adds the same alias ID into the same cluster. This is triggered when calling .alias using the client-side SDKs. The $create_alias event is used to link two non-anonymous Distinct IDs. It creates an “alias” to another Distinct ID already present in the identity cluster and adds the same alias ID into the same cluster. Multiple alias ID can point to the same Distinct ID, aliases can be daisy-chained; but the same alias ID cannot point to multiple different Distinct IDs. Not all server-side SDKs support alias() method. This is a legacy function for projects not using ID Merge. Here is a technical definition of the $create_alias event in our API reference.In the Original ID Merge system, the alias method was the only way to connect users together prior to March 2020. This method was very limited and was not retroactive, meaning that if a user used two devices and then logged in, you would lose activity for the user from one of the devices. If you set up Mixpanel prior to 2020, you may have implemented using the .alias() method. Alias is still supported in its original state and we have preserved its documentation here, but if you want to revisit your identity management strategy, we recommend setting up a new Mixpanel project and using the best practices outlined in this guide.In the API, the $create_alias event payload is only useful for projects using the Original ID Merge system and the Legacy ID Management System; it has no functionality in the Simplified ID Merge system. You can also use the import endpoint: https://api.mixpanel.com/import/ Create AliasIn the API, the alias property is used to track the alias passed into the $create_alias event. Reserved Event Properties
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
