When users use the product for the first time, they usually do not understand the product and worry about finding that the product functions do not match their expectations after registration. It may also be that the registration process is too cumbersome and is unwilling to spend time on it. Out of concern for personal privacy, they are reluctant to easily hand Buy email list over personal information to a product that is not yet understood.
However, if these unregistered users are directly allowed to use the product without any identification of the user's identity, not only will a lot of user behavior data be lost, but there will also be a problem that the functions cannot be used because they do not meet the conditions of use.
Without identification, it is impossible to identify which unregistered user did the operation, and it is impossible to analyze the behavior data before user registration, so as to continuously optimize the product and obtain more new user registrations. Without identity, functions based on identity cannot be used, such as sending messages, comments, etc.
The contradiction is obvious: we not only want to meet the needs of users to use the product without registration and login, but also want to identify users and obtain operational data.
How to resolve this contradiction? The answer is guest mode: tourists without registered accounts are automatically assigned guest accounts to mark their identities, allowing users to use all functions as "guests" except for "registered users only".
2. How to design the tourist mode?
When designing the tourist mode, we should focus on 4 user scenarios: tourists use the product for the first time, guide tourists to register and log in, tourists register accounts, and tourists log in to existing accounts.
1. Tourists use the product for the first time
When the user uses the product for the first time, according to the user's hardware information, a visitor ID is assigned to the user, that is, a UserID whose status is "unregistered", and the visitor's behavior data is recorded under this UserID.