Im using Mixpanels unified identity function. I can see that users have both deviceIDs and a userID. How can I create a funnel that shows me anonymous user -> signed in user conversion?
Hi Daniel 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> đź‘‹
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
To create a funnel that shows anonymous user to signed-in user conversion in Mixpanel, you'll need to leverage Mixpanel's ID Merge functionality, which you're already using. Here's how to approach this:
Creating an Anonymous to Signed-in User Conversion Funnel
Mixpanel's ID Merge system automatically connects pre-login (anonymous) and post-login (identified) user behavior when implemented correctly. This allows you to create funnels that span across the anonymous to authenticated user journey.
Step 1: Ensure Proper Implementation
First, make sure your implementation is correctly tracking both anonymous and identified states: 1. For anonymous users: Events should include a $device_id property
2. Upon sign-in/registration: Call .identify(user_id) or include both $device_id and $user_id in the same event
3. Upon logout: Call .reset() to generate a new $device_idThis implementation creates an identity cluster that connects anonymous activity with identified activity How Mixpanel Marketing Analytics unlocks full user journey analysis.
Step 2: Create Your Funnel
To build the funnel: 1. Select events that represent the anonymous user journey (e.g., "Page View", "Product View") 2. Include the sign-up or login event as a step in your funnel (e.g., "Sign Up", "Login") 3. Optionally add post-login events to track further conversionSince Mixpanel automatically stitches pre-login and post-login behavior with ID Merge, your funnel will correctly show the conversion from anonymous to signed-in users.
Example Funnel Steps
Step 2: "Product View" (anonymous event with $device_id)
Step 3: "Sign Up" (event with both $device_id and $user_id)
Step 4: "Complete Profile" (identified event with $user_id)LBKS```LBKSLBKSWith proper ID Merge implementation, Mixpanel will automatically connect these events even though they started as anonymous and converted to identified users.LBKSIf you need more detailed guidance on implementing ID management for this specific use case, refer to the [Identifying Users documentation](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-simplified).
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.
Does mixpanel retroactivelly add the userID to events that occured before they signed up?
Let me check the knowledge base for you again. One moment! đź“š
Yes, Mixpanel does retroactively add the userID to events that occurred before a user signed up when you're using the Simplified ID Merge system.When a user starts as anonymous and later signs up or logs in, Mixpanel will retroactively update the distinct_id on their previous anonymous events from $device:D1 to their $user_id value. This happens automatically when you properly implement ID Merge by including both the $device_id and $user_id in the same event (typically at login or signup).This is clearly shown in the example user flows from Mixpanel's documentation: LBKS| Event | $device_id | $user_id | distinct_id (set by Mixpanel) | Notes | | --- | --- | --- | --- | --- | | 1 | D1 | | ~~**$device:D1**~~ ⇒ **U1** | Retroactively updated | | 2 | D1 | | ~~**$device:D1**~~ ⇒ **U1** | Retroactively updated | | 3 | D1 | U1 | U1 | Links D1 ⇒ U1, D1 and U1 are inside one ID cluster |LBKSAs shown above, Events 1 and 2 were initially tracked with only a $device_id, but after Event 3 (which contains both $device_id and $user_id), Mixpanel retroactively updates the distinct_id of the previous events Identifying Users (Simplified).This retroactive updating is what allows you to create funnels that span from anonymous to authenticated states and analyze the complete user journey.It's worth noting that while the identity mapping happens immediately, it may take up to 24 hours for this mapping to fully propagate throughout all parts of the Mixpanel system, though the Activity Feed view updates in near real-time (less than 1 minute) Identifying Users (Simplified).
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.