Hello everyone, we made a mistake when we used wrong userId (different one) for identifying users. Then we fixed it but now we have duplicate user entries in mixpanel. We also log e-mails, that are unique. Is there any possibility to tell mixpanel to join those accounts with same e-mail address? Or how would you approach solving this issue? Thank you very much in advance for any help, Filip
Hi Filip O., 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
Hello Filip, I understand your concern about duplicate user entries in Mixpanel due to using incorrect user IDs. Unfortunately, based on the provided knowledge sources, there isn't a straightforward way to merge accounts with the same email address in Mixpanel. However, I can offer some insights and potential approaches to address this issue: 1. For projects using the Original ID Merge system, it is possible to merge two identified IDs using the [$merge API event](https://developer.mixpanel.com/reference/identity-merge). This allows merging of any 2 ID clusters as long as it does not exceed 500 total IDs [Identifying Users (Original) FAQ](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-original#faq). 2. If you're using the Simplified ID Merge system, it's important to note that it doesn't support merging multiple identified IDs (i.e., User IDs) per ID cluster [Migrating to Simplified ID Merge](https://docs.mixpanel.com/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system#on-original-id-merge). 3. As a best practice, Mixpanel recommends using an ID that is unique to each user and does not change, such as a database ID. While using an identifier like email may be more convenient, keep in mind that you cannot merge 2 $user_ids or change a $user_id in the Simplified ID Merge system [Identifying Users (Simplified) FAQ](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-simplified#faq). To approach solving this issue: 1. First, review your implementation to ensure you're correctly identifying users moving forward. Make sure to call .identify() with the correct user ID at appropriate points in the user journey, such as upon registration/login or when an app is re-opened in a logged-in state [Identifying Users (Original) Best Practices](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-original#best-practices). 2. For existing duplicate entries, if you're using the Original ID Merge system, you could potentially use the $merge API event to combine the duplicate accounts. However, this would need to be done carefully and may require custom scripting to match and merge accounts based on email addresses. 3. If you're using the Simplified ID Merge system or if merging is not feasible, you might need to consider starting fresh with a new Mixpanel project using the correct user IDs. This would ensure accurate data moving forward, although you would lose historical data. 4. As an alternative, you could keep the email addresses as a separate user property and use this for analysis within Mixpanel, even though the underlying user IDs remain separate. Remember, it's crucial to document your ID management implementation for future reference and troubleshooting [Identifying Users (Original) Best Practices](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-original#best-practices).
For more detailed assistance with your specific setup, I recommend reaching out to Mixpanel's support team as they may be able to provide more tailored advice for your situation.
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 understand your concern about losing data when starting fresh with a new Mixpanel project. You're right that this approach would result in data loss, which is not ideal. Let me provide some alternative options based on the available knowledge sources: 1. Data Migration: Instead of starting completely fresh, you could consider migrating your existing data to a new project. Mixpanel offers several methods for backfilling historical data: - If you have a data warehouse: You can use the [Mixpanel Warehouse Connector](https://docs.mixpanel.com/docs/tracking-methods/warehouse-connectors) or the [Import API](https://developer.mixpanel.com/reference/import-events) to import your data into Mixpanel [Migrating to Mixpanel](https://docs.mixpanel.com/docs/migration#loading-historical-data). - If you don't have a data warehouse: You can export your data from your current Mixpanel project and use a helper function provided by Mixpanel to move it into a new project [Migrating to Mixpanel](https://docs.mixpanel.com/docs/migration#loading-historical-data). 2. Partial Historical Data: If migrating all historical data is too complex or time-consuming, you could consider importing only a portion of your historical data. Mixpanel recommends "loading a year's worth (or less) of historical data during your migration. This will allow your team to review year-over-year trends easily and do historical analysis as needed" [Migrating to Mixpanel](https://docs.mixpanel.com/docs/migration#loading-historical-data). 3. Data Transformation: During the migration process, you could potentially transform your data to correct the user ID issues. This would involve mapping the incorrect user IDs to the correct ones based on email addresses or other unique identifiers [Send Your Data: Implement Your Tracking Plan](https://docs.mixpanel.com/guides/implement/send-your-data#backfilling-historical-data). 4. Test Project: Before fully committing to a data migration, Mixpanel recommends "Load a limited subset of the data into a test project (for example, a single day or data or a sample of the entire dataset) to get started. This will help you identify any errors in the end to end process before you do a full historical data load" [Migrating to Mixpanel](https://docs.mixpanel.com/docs/migration#loading-historical-data). Remember, the process of importing old data with a different format can have potential issues with identity management and data discrepancies. It's essential to carefully plan and execute the migration to ensure data integrity [Send Your Data: Implement Your Tracking Plan](https://docs.mixpanel.com/guides/implement/send-your-data#backfilling-historical-data). For a more detailed guide on project migration, including steps for migrating reports and non-data entities, you can refer to Mixpanel's [project migration playbook](https://docs.mixpanel.com/guides/playbooks/project-migration).
Given the complexity of your situation, I strongly recommend reaching out to Mixpanel's support team for personalized assistance. They can provide more specific guidance based on your exact setup and requirements.
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! đź“š
To contact Mixpanel support regarding your issue with duplicate user entries and data migration, you have several options:1. If you're logged into Mixpanel, you can click on "Contact Support" in the Help Menu Contacting Mixpanel Support.2. If you're not logged in, you can access the support form directly by going to mixpanel.com/get-support Contacting Mixpanel Support.3. You can also email the Customer Success team at <success@​mixpanel.com> Not sure where to start or need help?.When contacting support, be sure to provide details about your current setup, the issue you're facing with duplicate user entries, and any steps you've already taken to address the problem. This will help the support team provide more targeted assistance.Remember that response times may vary depending on your Mixpanel plan. You can check the expected response times for different plans in the Support Offerings & First Response Times table.For complex migration issues like yours, reaching out to support is definitely recommended as they can provide personalized guidance based on your specific situation.
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.
