Hi, I’m a new user for Amplitude.
I have a case, that when I tracked my funnel registration, my visitor in web browser identified as difference device id and session from their device id and session before register. I tested this journey in Google Chrome, but some how when I tested this flow in Mobile Web, the device ID was consistence before and after join.
Based on this article https://help.amplitude.com/hc/en-us/articles/115003135607-Tracking-Unique-Users
I assume, my journey would be consider as difference amplitude id right, and it would implicated if I wanna create funnel conversion cause my journey don’t consider as same person.
So is this case caused by $identify or what should I do to solve this issue?
Kindly for your advice in my cases. Thank you
Best answer by jarren.patao
This kind of behavior can happen depending on your organization’s has set up user identification within your events. I did notice that the device_id that shows up in your screenshot ends with an “R” which signifies it was a randomly generated UUID set by our SDK.
If you are not setting custom device_id values, then it could be the case that you are regenerating your device_id somewhere within the users’ event flow. One thing that is interesting here is that these don't look like the device_id's that the JS SDK creates so it could be good to look into how your team is setting this value.
You could potentially be sending events from multiple pages. Since we rely on initializing our SDK on each page for cross-domain tracking, it could be the case that the SDK is being initialized on the second page without passing the device_id as we mention here: https://help.amplitude.com/hc/en-us/articles/115003135607#h_f717e48c-460c-4a17-abd7-102327673798
If you are using an SDK v6.x.x— we’ve also made some changes to our infrastructure since then which addressed reusing device_id's from cookies
Hope this helps!