setting distinctid after session already started, create another session and new visitor

[Vikaskumargd]

Describe the Bug

User Journey:

1. User go to landing page anonymously. (session started and visible in Umami Session page)
2. User now login/signup. (I am setting distinctid as userid using umami.identify(unique_id: string). Now new session started)

Now I have 2 different session visible on Session page with different visitors.

It should not be the case.

Database

PostgreSQL

Relevant log output

Which Umami version are you using? (if relevant)

v2.19.0

Which browser are you using? (if relevant)

Edge

How are you deploying your application? (if relevant)

Dokploy

[DDushkin]

Hello, we have the same issue. Users go to the Landing page or to the Register page with some promo code, then they sign up, and we call identify with user_id from the DB. Then, if we wanna see the reporting or User journeys or Funnels all end at the sign up step, cause after identify, a new session gets created. It would be great if we could link those sessions, because this is critical for analytics, and we end up with 2 sessions

[franciscao633]

Closing this out since we have a proposed solution in #3820 with an enhancement tag.