Thang D.

kapa.ai When an identified user named A123 logs in, the event has a distinct_id equal to user ID A123. Later, an event appears with the same distinct_id (A123) but a different user_id—let’s say B123. Could this happen if user A123 logged out and then logged in with another account (user B123)? If so, why does the distinct_id still remain as A123?

kapa.ai Why do many events have a user_id that is null? For example, the event answer_attempt_submission always has a null user_id. Can you explain why this happens and let me know which other events have the same issue?

kapa.ai In a user flow, the distinct_id is initially set to the device_id, and the user_id is null. Later, in some events, the user_id becomes not null, but the distinct_id stays the same. Can you explain why this happens?

kapa.ai Why does a user have more than one distinct_id in Legacy ID Management?

kapa.ai In the data, I see 4 types of distinct_id values: The distinct_id is the same as the user_id. The distinct_id is a device_id. The distinct_id has a $device: prefix. The distinct_id is neither a user_id nor a device_id. Can you help why this happen in Legacy ID Management?