Solved

$user_id is 'undefined' after implementing alias to track registration funnel

  • 11 March 2019
  • 1 reply
  • 229 views

Userlevel 4
Badge

We recently implemented alias at signup and then call identify upon login so that we can track a single user pre and post signup auth. It appears that we're now doing that correctly as the distinct_id for a user pre and post auth are now the same value. However, since we've put this into place, the Mixpanel default $user_id property that gets tracked with default events like $ae_session is now coming back as 'undefined' for newly registered users. Is there an additional step that needs to happen in order for $user_id to be populated with the user's distinct_id or our internal ID?


Thanks!


icon

Best answer by cherise 29 March 2019, 22:20

@rmelville -

You do not need to do anything additional here! The $user_id value is the unique ID that mixpanel.identify() sets, so until the newly registered users come back to login and trigger mixpanel.identify(), it will remain undefined.

Here is a link to all default properties that we track with our client-side SDKs.

I hope this helps!

- Cherise


View original

1 reply

Userlevel 4
Badge +3

@rmelville -

You do not need to do anything additional here! The $user_id value is the unique ID that mixpanel.identify() sets, so until the newly registered users come back to login and trigger mixpanel.identify(), it will remain undefined.

Here is a link to all default properties that we track with our client-side SDKs.

I hope this helps!

- Cherise


Reply