Question about merging anonymous events across browsers after identify() Hi all, I just ran a test with the Mixpanel JavaScript SDK and encountered a behavior I didn’t fully expect. Here’s what I did: 1. In Google Chrome, I opened the site and Mixpanel created an anonymous profile with a random device_id / distinct_id. 2. The user did 4–5 page views anonymously. 3. Then I called identify() with a known user ID (e.g., user_123), and continued browsing. 4. Mixpanel correctly merged the anonymous and identified events into one profile ✅ So far, all good. Then I tried this in Opera (completely different browser): 1. Again, Mixpanel created an anonymous user when I landed on the site. 2. I did a few anonymous events (e.g., page views) - PROBLEM 3. Then I logged in and called identify("user_123") Now the issue: The anonymous events in Opera stayed under a separate profile and were not merged. Expected: Every time an anonymous user browse around in any browser/device as soon as they are identified all those anonymous events should be assigned to their profile Question: Why doesn’t Mixpanel merge the anonymous events from the second browser session to the existing profile once identify() is called with the same user ID? Is this expected behavior? Thanks in advance!
I see that the event where opera went from anonymous to identified is called "User Signed Up" rather than "user signed in"... is it possible you're clearing local storage/session information when a user signs up or when log out? this could be happening automatically (some browsers do this when you close the window) or manually (for example, if you're calling mixpanel.reset()
you can actually look at the device id of all the events and make sure it's the same for all events sent by opera... if it is, then it's a mixpanel bug and you need to reach to CS... if it's not, then you're probably clearing local storage before you're calling identify
