Solved

Interchanged values for “DistinctID” and “Distinct ID Before Identity”

  • 21 July 2021
  • 1 reply
  • 28 views

I’m finding that about half the time, ‘Distinct ID’ is not updated by my Identify calls and that all subsequent events show ‘Distinct ID Before Identity” as my intended id and ‘Distinct ID’ as the original id. It’s as if Distinct ID is being changed to my intended value, and then change back to its original value. 

I’m calling Identify(username) when a user creates an account and when a user logs in, so this means that upon creating an account, Identify gets called twice back to back. Any chance this is the source of the problem?

I’m using Mixpanel version 2.2.3 with Unity.

icon

Best answer by donna 23 July 2021, 19:40

Hi! I replied through the Support Ticket that you have opened with us, but for anyone else coming across this thread:

With ID Merge, there is a Canonical Distinct ID, it is the main id for a user in Mixpanel: https://help.mixpanel.com/hc/en-us/articles/360041039771#individual-users 

 

Mixpanel’s ID Merge system determines which identifier within a user’s identity cluster will be the canonical id.

You can’t control what will be the canonical id for users noted here: https://help.mixpanel.com/hc/en-us/articles/360039133851#changes-after-enabling-id-merge

 

In the case where the Distinct ID was the “original id”, and Distinct ID before Identity had the “intended id”:

Both identifiers are in the same identity cluster, Mixpanel ID Merge system had chosen the “original id” as the canonical id.

View original

1 reply

Hi! I replied through the Support Ticket that you have opened with us, but for anyone else coming across this thread:

With ID Merge, there is a Canonical Distinct ID, it is the main id for a user in Mixpanel: https://help.mixpanel.com/hc/en-us/articles/360041039771#individual-users 

 

Mixpanel’s ID Merge system determines which identifier within a user’s identity cluster will be the canonical id.

You can’t control what will be the canonical id for users noted here: https://help.mixpanel.com/hc/en-us/articles/360039133851#changes-after-enabling-id-merge

 

In the case where the Distinct ID was the “original id”, and Distinct ID before Identity had the “intended id”:

Both identifiers are in the same identity cluster, Mixpanel ID Merge system had chosen the “original id” as the canonical id.

Reply


Mixpanel