Use alias and identify methods to keep the identity of your users consistent throughout their interactions in your site or app.
The correct implementation of these methods permits you to use your own user IDs as a distinct_id without altering Mixpanel report functionality.
Manage Identity with Alias and Identify Methods
An ideal integration enables you to track the actions of your users across your application, website or other platform when using Mixpanel.
An example of a user journey follows when a user first engages your site anonymously, signs up for an account, and logs in later.
Mixpanel provides two methods to let you track those actions, and be able to connect the user journey. In short, to implement identity management:
- When a new user signs up, call mixpanel.alias("YOUR_USER_ID") once.
- When a user logs in, call mixpanel.identify("YOUR_USER_ID").
When alias is called, Mixpanel will create a mapping between the Mixpanel generated distinct_id, and your unique identifier.
Subsequently, when identify is called, you pass your identifier and Mixpanel will connect it with the original distinct_id.
Example User Identification Flow
Here’s an example of how alias and identify work together to manage user identity:
- Sally comes to your website for the first time. Mixpanel assigns Sally a randomly generated ID, which is known as a Mixpanel distinct_id.
- Mixpanel assigns Sally the distinct_id “12345”. Now all her actions are connected to that distinct_id.
- After navigating through several pages and performing several events, she successfully signs up for an account.
- The signup confirmation page calls the mixpanel.alias() method and passes Sally’s email address as an argument. For example, mixpanel.alias(“email@example.com").
- The mixpanel.alias(“firstname.lastname@example.org”) method doesn't change her Mixpanel distinct_id. It adds the ID "email@example.com" to a Mixpanel lookup table, and maps it to the original Mixpanel distinct_id “12345”.
- Now Mixpanel calls the mixpanel.identify("firstname.lastname@example.org") method and passes the ID ("email@example.com") to all subsequent pages and logins whenever Mixpanel sees data for "firstname.lastname@example.org”.
- Mixpanel remaps her original distinct_id of “12345”. So all actions Sally takes–whether on your site, in your app, or anonymously before she signed up for her account–maps to her.
The image below illustrates the identity management process.
Only Call Alias Once
An alias can only point to one Mixpanel distinct_id.
If you’re implementing Mixpanel on a site with users who have already signed up, you do not need call alias on those users.
The primary purpose of calling mixpanel.alias() is to connect a user’s anonymous events from before a signup (or other identification) event with the post-signup activity on your site or in your app.
You can simply identify existing users with the Mixpanel identify method.
Existing User Identification Example
If you’ve already mapped your identifier (such as “email@example.com”) to a Mixpanel distinct_id (such as “12345”), any attempt to map your identifier to a different Mixpanel distinct_id fails.
In the previous example, Sally came to your website, not your mobile application. Suppose she decides to download your app on her phone and logs in.
The mixpanel.alias() method does not work the second time. Even though Sally has not used your app on this device before, she is not a new user.
If Mixpanel calls the mixpanel.alias() method, it would attempt to map the email to the random Mixpanel distinct_id from the phone.
To remedy this scenario, use the mixpanel.identify() method to associate the original Mixpanel distinct_id "12345", where all Sally's actions are already stored by calling mixpanel.identify("12345"). This will associate her events moving forward with distinct_id 12345. Events she performed anonymously on her phone will be orphaned.
If an identify or track call arrives to Mixpanel with a new distinct_id too quickly after an alias call, a race condition occurs between the event and the alias call.
Usually there are no issues when your identify and track calls arrive ~1 second after the alias. When the alias queue is backed up, Mixpanel queues events as well, alleviating the race condition.
Split or duplicate profiles can result when events are processed before their corresponding alias.
Developer Documentation Resources to Manage User Identities
The following links direct to the identity management documentation that corresponds to specific SDKs.