Skip to main content

Hey,

There is my, pretty usual, use case :

  • Leads fill a form, so we can contact them by email.
  • After a will, some of them convert to user by creating an account on our platform.
  • Right now, we use our platform generated ID as user_id in Amplitude. So at the lead step we don’t have it.

I’m not sure how can I easily follow all the journey in Amplitude.

I’m used to Braze and Mixpanel where you can have aliases to handle this kind of cases, once the user creates an account you just merge all his alias to it. But this system is not available in Amplitude.

 

What’s the best way to identify ‘not yet’ users in Amplitude (but we can have a temporal unique identifier as the email) and then identify them to their final user_id ?

Let me know if my explanation is not clear ;)


Thanks and have a great day !

Matthias

Hi @tthias 

The general best practice is to not assign any explicit user ID for anonymous users.

These users will still have Amplitude IDs and device IDs. Users will later be merged when Amplitude recognizes the different user IDs belong to the same user. In your case, this will occur usually when the user creates the account and gets the user_id field. The lead form submission event will be merged and attributed to this user_id in the event stream.

Hope this helps.

Reply


Terms & ConditionsCookie settings