Nameer

Muhammad U. FYI.

Ansh A. We are getting another issue where device id (mixpanel properties) of our domain 1 is different from device id of domain 2 due to which different events are being dropped for the same user. Can you please help with this issue?

The reset part works fine for the app but the website still stays linked to that user and upon the second sign up it gives the following error while merging the website and the new user id: errAnonDistinctIdAssignedAlready

Because of this for some user accounts we are unable to track their website journey as it is already linked to the first user merged

No like a lot of our current user's are doing this.

Ansh A. It shouldn't but can happen if the user uses different emails for the sign up.

Ansh A. We are experiencing an issue related to cross-domain identity resolution. Currently, we pass the anonymous Distinct ID from our website (Domain 1) to our web application (Domain 2). When the user signs up, this anonymous Distinct ID from the website is bound to the User ID using Mixpanel's simplified ID merge. Consequently, the events tracked from the website (Domain 1) are correctly attributed to the User ID. The core issue is that this binding process is permanent and manual, leading to data attribution errors for repeat sign-ups. Due to this ID merge, if the same individual revisits the website (Domain 1), is redirected to the app (Domain 2), and signs up as a new user (creating a second User ID), the website events tracked during this new session remain permanently bound to the first User ID this individual signed up with. As a result, all subsequent sign-ups that originate from a redirection from the website incorrectly merge their anonymous website events into the first user's Mixpanel event history.