How can users from different sources be merged into unified users?

I made a website that can be accessed through a browser or through Weibo apps. I hope that requests from different sources of the same user can be merged into one user account, for example, the number of reads. Of course, the simplest way is to ask the user to register before accessing the website. In this way, I made a website that can be accessed directly through a browser, or through apps such as Weibo. I hope that requests from different sources of the same user can be merged into one user account, for example, the number of reads. Of course, the simplest way is to require the user to register before accessing, so that the user is directly under an account. However, the user experience is poor. For example, if the public account supports oauth, the same user can be identified by obtaining the openid no matter on which terminal the user is accessed by using the user's own client, in fact, users do not need to register. Therefore, I would like to see whether there is a basic framework and do not set any obstacles for users to access the website. These operations are only performed when users feel they need to register and log on to the website, then, the customer identities from different sources are gradually determined, and the user data from different sources is eventually unified to a single user account. Is this idea reasonable? Are there mature solutions?

Reply content:

I made a website that can be accessed through a browser or through Weibo apps. I hope that requests from different sources of the same user can be merged into one user account, for example, the number of reads. Of course, the simplest way is to require the user to register before accessing, so that the user is directly under an account. However, the user experience is poor. For example, if the public account supports oauth, the same user can be identified by obtaining the openid no matter on which terminal the user is accessed by using the user's own client, in fact, users do not need to register. Therefore, I would like to see whether there is a basic framework and do not set any obstacles for users to access the website. These operations are only performed when users feel they need to register and log on to the website, then, the customer identities from different sources are gradually determined, and the user data from different sources is eventually unified to a single user account. Is this idea reasonable? Are there mature solutions?

Hello, you need to clarify the basic idea of this problem: Merge users into statistics, so you need to give these users a uid to uniquely identify. Regardless of the channel, establish a one-to-one correspondence between uid.

For example, if you use oauth to log on, you mention that you do not allow user registration, then the system will automatically generate a uid based on the pre-determined policy, and prompt the user that this is his account. At this time, when you log on through other channels, you can use oauth or the generated unique uid to log on to the system.

Effect: This solution solves the problem of tedious user registration. You can add detailed information for further maintenance in the personal center!

Isn't that the problem of multi-terminal login? It must be something that allows users to log on. I have not seen any good solutions at the moment. The possible method is the best. The computer login method is scanning.