I'm having an issue where some users aren't tracked between events and a new user is created. This is because sign-up is a two stage process, and users need to click a link in their emails between the two sign-up events, which opens a new window and often creates a new user in Mixpanel. How can I join the two and increase the match rate of users at this stage?
Hi James S., 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
It sounds like you're experiencing an identity management issue in Mixpanel where users are being tracked as separate entities when they complete a two-stage sign-up process. This is a common challenge when users navigate between different browser sessions or devices during authentication flows.
Solution: Implement ID Merge
Mixpanel's ID Merge feature is designed specifically to solve this problem by connecting events from the same user across different sessions and devices.
How to implement ID Merge:
1. Use .identify() at the right moments: Call the .identify() method when users complete registration or login to link their pre and post-login events.LBKS// When user starts the signup process, track with current ID mixpanel.track('sign up started');LBKS// When user completes signup after email verification, identify them mixpanel.identify('user_123'); // Use their actual user ID hereLBKS2. Call .reset() appropriately:
- For Simplified ID Merge: Call .reset() upon logout to generate a new device ID for new users on the same device
- For Original ID Merge: Only call .reset() when there's an explicit intent to change to a new userLearn to Use Mixpanel: ID Merge Implementation provides a detailed walkthrough of this implementation.
Best Practices:
- Track user identifiers as properties: Store the user's unique identifier as both a super property and user property to help with troubleshooting - Avoid creating profiles for anonymous users: Wait until users are fully identified before creating profiles - QA your implementation: Ensure cross-platform and pre/post-registration events are properly linked to the same user - Document your implementation: Keep a record of how you've implemented ID management for future referenceLearn to Use Mixpanel: Basic concepts in ID Merge explains the fundamental concepts behind this feature.For detailed implementation guidance, check the Identifying Users documentation which provides comprehensive best practices.
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 you've already implemented the ID Merge suggestions I mentioned earlier but are still experiencing issues with matching users across your two-stage signup process. Let's explore some additional approaches you can take to improve your user matching rate.
Additional Strategies for Improving User Matching
1. Pass identifiers between sessions: Consider passing a unique identifier in the email verification link that can connect the two sessions. For example:
```LBKS Then in the verification page, read this parameter and use it to link the sessions.LBKS2. **Check your ID Merge system version**: Ensure you're using the Simplified ID Merge system, which is more straightforward and robust than Legacy or Original ID Merge.
[Migrating to Simplified ID Merge](https://docs.mixpanel.com/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system#overview) explains the differences between these systems.LBKS3. **Server-side tracking for critical events**: For the email verification step, consider implementing server-side tracking with the same user ID to ensure continuity.LBKS4. **Consistent user identification across platforms**: If you're tracking across web and mobile, ensure you're using the same user ID consistently.LBKS5. **QA your implementation**: Double-check that your implementation is correctly setting `$device_id` and `$user_id` properties on events. Review the [Example User Flows](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-simplified#example-user-flows) to ensure your implementation matches the expected behavior.LBKS6. **Create a new project with Simplified ID Merge**: If you're using an older ID management system, consider creating a new Mixpanel project with Simplified ID Merge enabled from the start, as this cannot be changed after data is ingested.LBKS [Setting Up Mixpanel](https://docs.mixpanel.com/guides/plan/setup) provides guidance on configuring a new project with Simplified ID Merge.LBKSIf you've already implemented all these suggestions and are still experiencing issues, it might be worth reaching out to Mixpanel Support for a more tailored solution based on your specific implementation details.LBKSWould you like me to elaborate on any of these approaches?
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.