jinny B.

Commented on Understanding Event Merging and Reporting in Mixpa...·Posted inMixpanel Bot

kapa.ai We've merged our user IDs after a user logs in. We understand that Mixpanel's identity merge system should retroactively link all events from the anonymous device:id to the new user's distinct_id. However, we're finding that when we query for a user's events using their merged ID, we cannot see the very first "Initial Referring Domain" value.

Commented on Understanding Event Merging and Reporting in Mixpa...·Posted inMixpanel Bot

jinny B.

kapa.ai And how can I find out a user's Initial Referring Domain using a user property that is updated after they sign up

Posted in Mixpanel Bot·

jinny B.

Understanding Event Merging and Reporting in Mixpanel

kapa.ai I have a question regarding how events are merged after a user logs in. From my understanding, when a user logs in and we set their distinct ID using mixpanel.identify(our_distinct_id), the new distinct ID is merged with the previous anonymous distinct ID (the one starting with device:). This combines all the events from the anonymous session with the newly identified user's events. However, I've noticed a specific issue. Events that were logged with the property "Initial Referring Domain" during the anonymous session do not appear to be merged or linked to the user's new distinct ID after they log in. Can you please explain why this is happening? Additionally, could you provide detailed instructions on how to create an Insights report to see these events? What specific conditions or filters should I use to view the anonymous events that were logged with the "Initial Referring Domain" property and are now linked to a user's identified distinct ID?

8Comments