Method, device, equipment and storage medium for prompting users to log in to a platform
By analyzing user behavior logs and account data, dormant users can be identified and reactivated in a personalized way, solving the problem of low success rate in waking up dormant users and achieving more efficient user reactivation and data protection.
Patent Information
- Application Number
- CN202011021787.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-09-25
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-09-25
AI Technical Summary
In existing technologies, the success rate of waking up dormant users is low, which easily leads to user complaints, as well as problems such as loss of user data, loss of accounts, or invalid passwords.
By analyzing users' historical behavior logs and account data, dormant users are identified, and different resources and prompts are allocated based on activity levels, employing a personalized wake-up mechanism.
It improved the success rate of waking up dormant users, reduced user data loss and account invalidation issues, and enhanced the user experience.
Smart Images

Figure CN112288460B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to the field of Internet technology, and in particular, to a method, device, equipment and storage medium for prompting a user to log in to a platform. Background Art
[0002] With the development of mobile Internet, the cost of acquiring users for various service platforms is increasing. After a service platform has been operating for a long time, it is inevitable that a large number of dormant users will appear who have not used the service platform for a long time.
[0003] However, if users do not log in to the platform for a long time, it may cause problems such as loss of user data, loss of user account, and invalid user password. Summary of the invention
[0004] The embodiments of the present invention provide a method, device, equipment and storage medium for prompting a user to log in to a platform, so as to solve the problems of user data loss, user account loss, user password invalidation, etc. caused by long-term non-login of the user.
[0005] On the one hand, an embodiment of the present invention provides a method for prompting a user to log in to a platform, comprising:
[0006] Determine the user's registration duration and active behavior records based on the user's historical behavior logs and account data;
[0007] If the user's registration duration and active behavior records meet preset conditions, the user is determined to be a target user;
[0008] Determine the activity level information of the target user based on the historical behavior log and account data of the target user;
[0009] According to the activity level information of the target user, corresponding user resources are allocated to the target user and prompt information is pushed, wherein the prompt information is used to prompt the user to use the user resources after logging in, wherein different user resources are allocated to target users with different activity levels.
[0010] On the other hand, an embodiment of the present invention provides a device for prompting a user to log in to a platform, including:
[0011] A data processing module, used to determine the user's registration duration and active behavior records based on the user's historical behavior log and account data;
[0012] An identification processing module, configured to determine that the user is a target user if the registration duration and active behavior record of the user meet preset conditions;
[0013] The data processing module is also used to: determine the activity level information of the target user according to the historical behavior log and account data of the target user;
[0014] The wake-up processing module is used to allocate corresponding user resources to the target user and push prompt information according to the activity level information of the target user, wherein the prompt information is used to prompt the user to use the user resources after logging in, wherein different user resources are allocated to target users with different activity levels.
[0015] On the other hand, an embodiment of the present invention provides a device for prompting a user to log in to a platform, including:
[0016] A processor, a memory, and a computer program stored on the memory and executable on the processor;
[0017] Wherein, when the processor runs the computer program, the method of prompting the user to log in to the platform is implemented as described above.
[0018] On the other hand, an embodiment of the present invention provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method of prompting a user to log in to the platform as described above is implemented.
[0019] The method, apparatus, device and storage medium for prompting a user to log in to a platform provided by an embodiment of the present invention determine the registration duration and active behavior record of the user according to the user's historical behavior log and account data; if the registration duration and active behavior record of the user meet the preset conditions, the user is determined to be a target user, and dormant users can be identified more accurately; further, the activity level information of the target user is determined according to the historical behavior log and account data of the target user; according to the activity level information of the target user, corresponding user resources are allocated to the target user, and different user resources are allocated to target users with different activity levels, and prompt information is pushed to the user to prompt the user to use the user resources after logging in, so that different levels of incentives can be used for dormant users with different activity levels in a targeted manner, thereby realizing a more diversified and flexible awakening mechanism for dormant users, and improving the awakening success rate of dormant users, so as to encourage dormant users to log in to the platform as soon as possible, and avoid problems such as user data loss, user account loss or password expiration due to long-term non-login to the platform. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 A schematic diagram of the system architecture of the service platform provided by an embodiment of the present invention;
[0021] Figure 2 A flow chart of a method for prompting a user to log in to a platform provided in Embodiment 1 of the present invention;
[0022] Figure 3 A flow chart of a method for prompting a user to log into a platform provided in Embodiment 2 of the present invention;
[0023] Figure 4 A schematic diagram of summarizing dormant user indicators provided in the second embodiment of the present invention;
[0024] Figure 5 A schematic diagram of the structure of a device for prompting a user to log in to a platform provided in Embodiment 3 of the present invention;
[0025] Figure 6 This is a schematic diagram of the structure of a device for prompting a user to log in to a platform provided in Embodiment 5 of the present invention.
[0026] The above drawings have shown clear embodiments of the present invention, which will be described in more detail below. These drawings and text descriptions are not intended to limit the scope of the present invention in any way, but to illustrate the concept of the present invention for those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0027] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.
[0028] The terms "first", "second", etc. involved in the embodiments of the present invention are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. In the description of the following embodiments, the meaning of "multiple" is more than two, unless otherwise clearly and specifically defined.
[0029] The embodiment of the present invention is specifically applied to a service platform, such as an online shopping platform, etc. The system architecture of the service platform is as follows: Figure 1 As shown, it includes a server and a user terminal. Users can register as users of the service platform through the user terminal and enjoy the services provided by the service platform, such as shopping through the service platform.
[0030] After the service platform has been operating for a long time, it is inevitable that a large number of dormant users who have not used the service platform for a long time will appear. At present, each service platform uses the last login time as an indicator to determine dormant users, pushes reminder information to all dormant users, and wakes up all dormant users uniformly. In the process of implementing the present invention, the inventor found that at least there is a problem in the prior art that the success rate of waking up dormant users is very low, which easily leads to user complaints.
[0031] The method for prompting a user to log in to a platform provided in an embodiment of the present invention is intended to solve the above technical problems.
[0032] The following specific embodiments are used to describe in detail the technical solutions of the present invention and how the technical solutions of the present application solve the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present invention will be described below in conjunction with the accompanying drawings.
[0033] Figure 2 This is a flow chart of a method for prompting a user to log in to a platform provided in Embodiment 1 of the present invention. The method in this embodiment is applied to a server of a service platform. In other embodiments, the method can also be applied to other devices. This embodiment takes a server as an example for schematic illustration. Figure 2 As shown, the specific steps of this method are as follows:
[0034] Step S101: Determine the user's registration duration and active behavior records based on the user's historical behavior log and account data.
[0035] The user's historical behavior log may include record information of all the user's behaviors in using the service platform.
[0036] The user's account data includes the user's account information, identity information, attribute information, asset information, financial information, identity information, business authority information, etc.
[0037] In this embodiment, the server can obtain detailed data of the user behavior log as comprehensive as possible, as well as all account data of the user on the service platform.
[0038] Furthermore, the registration duration of the user may be determined according to the registration time of the user.
[0039] Optionally, the active behavior records may be all active behavior records since the user registered, or active behavior records within a preset period of time.
[0040] The preset time period can be set and adjusted according to the actual application scenario, and this embodiment does not specifically limit it. For example, the preset time period can be the last year, the last several months, or the last several days, etc.
[0041] Depending on the user's business identity, the user's active behavior records may be different. For individual users, the user's active behavior records may include the following aspects: page browsing and click records through various channels (such as application APP, fixed terminals, mobile browsers, instant messaging software, etc.); login records; order records; coupon collection and use records; gift card purchase, card binding, and card use records; account balance recharge, use, and withdrawal records; virtual currency (such as points, Jingdou, gold coins, etc.) collection and use records; customer service consultation and after-sales records; financial card binding, payment, real-name, white slips, wallets, financial management, and crowdfunding records; cloud platform trial, consumption, and after-sales records; insurance sub-platform insurance and accident records; logistics sub-platform shipment and points records; and so on.
[0042] For corporate users, it usually includes active behavior records of corporate users as individuals, and on this basis, it also includes active behavior records as companies. For example, warehousing and return records; product shelf and shelf records; promotion creation and manual deletion records; coupon issuance records; virtual currency (such as points, Jingdou, gold coins, etc.) reward issuance records; delivery records; merchant customer service software online records; after-sales return and exchange, compensation records; rebate records; logistics carrier records; bidding records; contract signing records; financial settlement completion records; etc.
[0043] For example, taking JD.com as the service platform, the active behavior records of individual users of JD.com may include: page browsing and click records of users through various channels; login records; order records; coupon collection and use records; gift card purchase, binding and card use records; account balance recharge, use and withdrawal records; Jingdou collection and use records; customer service consultation and after-sales records; financial card binding, payment, real name, Baitiao, wallet, financial management and crowdfunding records; JD Cloud trial, consumption and after-sales records; JD Allianz insurance and accident records; JD Logistics delivery and points records. For corporate users of JD.com, in addition to the above-mentioned active behavior records of individual users, the active behavior records of corporate users may also include: storage and return records; product shelf and shelf records; promotion creation and manual deletion records; coupon issuance records; Jingdou reward issuance records; delivery records; merchant Dongdong online records; after-sales return and exchange, compensation records; rebate records; logistics carrier records; bidding records; contract signing records; financial settlement completion records; etc.
[0044] Step S102: If the user's registration duration and active behavior record meet preset conditions, the user is determined to be a target user.
[0045] Among them, target users refer to dormant users on the platform who have been inactive recently, have not logged in for a long time or have logged in less frequently, and need to be awakened and motivated. The "sleeping users" mentioned in the embodiments of the present invention refer to target users whose registration duration and active behavior records meet preset conditions.
[0046] In this embodiment, whether each user is a dormant user is determined based on the registration duration and active behavior records of each user.
[0047] For example, based on the user's registration duration and active behavior records, if a user has been registered for a long time but has no active behavior records in the recent period, or has very few active behavior records, the user can be determined to be a dormant user.
[0048] The user's registration duration and active behavior records must meet at least one of the following pre-conditions:
[0049] The registration duration is greater than the preset threshold, and there is no active behavior record less than the preset number of times during the preset period.
[0050] The preset threshold and the preset number of times may be set according to actual application scenarios, and are not specifically limited in this embodiment.
[0051] Step S103: Determine the activity level information of the target user based on the historical behavior log and account data of the target user.
[0052] In actual applications, different dormant users have different levels of activity. For dormant users with different levels of activity, the possibility and value of waking up the users are different.
[0053] In order to wake up sleeping users more flexibly and specifically, in this embodiment, after determining the target user, the activity level information of the target user is first determined based on the target user's historical behavior log and account data, and then different wake-up processes are performed on target users with different activity levels based on the target user's activity level information.
[0054] The activity level information may be information that can be used to measure the activity level, activity level, or likelihood of being awakened of different users. The more active the user, the greater the likelihood of being awakened and the easier it is to be awakened, while the less active the user, the less likely to be awakened and the less likely it is to be awakened.
[0055] For example, the activity level information can be the user's sleepiness level or activity level divided according to pre-set rules; or, it can be the length of time since the last use of the service platform; or, it can be the user's business authority information, asset information, historical order information, etc., which can reflect the user's activity level or the possibility of the user being awakened to a certain extent; or, it can be a score calculated based on the user's relevant data to reflect the user's activity level or the possibility of being awakened, and so on.
[0056] Step S104: allocate corresponding user resources to the target user according to the activity level information of the target user and push prompt information, where the prompt information is used to prompt the user to use the user resources after logging in, wherein different user resources are allocated to target users with different activity levels.
[0057] In this embodiment, after determining the activity level information of the target user, different wake-up processes are used to wake up users with different activity levels, so as to improve the efficiency and success rate of waking up the user to log in to the platform.
[0058] In addition, by pushing prompt information to the target user, the user is promptly reminded that the user can use the user resources allocated to him / her after logging in, thereby encouraging the target user to log in to the platform as soon as possible. For example, the prompt information can be pushed to the user through a communication method reserved by the user, such as text messages and instant messaging software. The method of pushing information to the target user is not specifically limited in this embodiment.
[0059] For example, for dormant users with higher levels of activity, that is, users who are easier to awaken, relatively stronger awakening incentives can be implemented. For example, large coupons or virtual resources (such as experience points, points, virtual currency, etc.) can be issued to awaken as many of these more active users as possible and improve the success rate of awakening dormant users.
[0060] For dormant users with very low activity levels, that is, users who are difficult to wake up, relatively small wake-up incentives can be used. For example, push promotional information to users, etc., to test user reactions and avoid wasting more resources.
[0061] In this embodiment, the specific wake-up processing adopted for different activity levels can be set and adjusted according to the actual application scenario and the needs of the service platform, and this embodiment does not make any specific limitations here.
[0062] The embodiment of the present invention determines the user's registration duration and active behavior record based on the user's historical behavior log and account data; if the user's registration duration and active behavior record meet the preset conditions, the user is determined to be a target user, and dormant users can be identified more accurately; further, the target user's activity level information is determined based on the target user's historical behavior log and account data; according to the target user's activity level information, corresponding user resources are allocated to the target user, and different user resources are allocated to target users with different activity levels, and prompt information is pushed to the user to prompt the user to use the user resources after logging in, so that different levels of incentives can be used for dormant users with different activity levels in a targeted manner, realizing a more diversified and flexible dormant user awakening mechanism, improving the dormant user awakening success rate, and thus encouraging dormant users to log in to the platform as soon as possible, avoiding problems such as user data loss, user account loss or password expiration due to long-term non-login to the platform.
[0063] Figure 3 A flow chart of the method for prompting a user to log into a platform provided in the second embodiment of the present invention. Based on the above-mentioned first embodiment, in this embodiment, multiple user categories are determined according to the business identity in the user's account data, and the business identity includes at least individual users and corporate users; for each user category, the target user in the user category is identified according to the historical behavior log and account data of the user in the user category, and the activity level information of the target user in the user category is determined; according to the activity level information of the target user in the user category, the user resources corresponding to the user category are allocated to the target user in the user category and prompt information is pushed. Figure 3 As shown, the specific steps of this method are as follows:
[0064] Step S201: Obtain the user's historical behavior log and account data.
[0065] The user's historical behavior log may include record information of all the user's behaviors in using the service platform.
[0066] The user's account data includes the user's account information, identity information, attribute information, asset information, financial information, identity information, business authority information, etc.
[0067] In this embodiment, the server can obtain detailed data of user behavior logs as comprehensive as possible, as well as all account data of users on the service platform. For example, based on the active behavior of users in the service platform system, all possible active data inside and outside the station (including sub-platforms, cooperative platforms, etc.) can be counted.
[0068] In this step, after obtaining the user's historical behavior log and account data, it is necessary to preprocess the user's historical behavior log and account data, including planning the processing of the account format in the data, the format of the log data, etc., so that the account format in the data is unified and the log data is standardized.
[0069] Step S202: Determine multiple user categories based on the business identity in the user's account data. The business identity includes at least individual users and corporate users. Perform subsequent steps for each user category.
[0070] In this embodiment, considering that there are differences in the behavior information, effective identity information, virtual resources and other information of users with different business identities, users are classified according to their business identities to obtain multiple user classifications, each of which contains users with the same business identity. Then, for each user classification, data of users with the business depth are used to analyze statistical data according to different logics to determine the user's active behavior records, identify dormant users, and determine the activity level information of dormant users, which can improve the accuracy of dormant user identification and the accuracy of activity level information.
[0071] For example, all users of the service platform are divided into individual users and corporate users according to their business identities. The activity levels of individual users are divided into first-level dormant users (CS1), second-level dormant users (CS2), and third-level dormant users (CS3); the activity levels of corporate users are divided into first-level dormant users (BS1), second-level dormant users (BS2), and third-level dormant users (BS3).
[0072] Among them, the awakening processing corresponding to sleeping users with the same activity level in different user categories is different, and the awakening processing corresponding to sleeping users with different activity levels in the same user category is different.
[0073] Step S203: Eliminate users with accounts of a specified type based on the user's account data.
[0074] The designated account type includes at least one of the following:
[0075] Whitelist accounts, accounts that cannot be awakened for login authentication, and accounts that are not registered by actual users.
[0076] Among them, the whitelist account refers to the account included in the whitelist pre-set on the service platform.
[0077] The account that cannot be awakened for login authentication may include accounts of various sub-platforms of the service platform, third-party merchant main accounts, third-party merchant sub-accounts, and corporate major customers. For example, for the JD.com service platform, the authentication method of the authentication cube is adopted, so the account that cannot be awakened for login authentication may be an account that cannot be awakened for authentication cube, which may include: Yixun.com account, No. 1 store account, POP merchant (JD.com third-party merchant) main account, POP merchant sub-account, JD.com medicine city account, corporate major customer account, etc. When the sub-platforms or user structures included in the service platform change, the account that cannot be awakened for login authentication may change, which is not specifically limited in this embodiment.
[0078] Accounts not registered by actual users may include test accounts, customer service accounts, operation accounts, etc.
[0079] In this embodiment, by eliminating accounts of a specified type, special accounts of non-valid users can be excluded to reduce unnecessary data processing and improve efficiency.
[0080] In addition, the execution order of this step and other steps can be adjusted locally, for example, it can be executed before step S202, after step S205, after step S207, etc., which is not specifically limited in this embodiment.
[0081] Step S204: Determine the user's registration duration and active behavior records within a preset period of time based on the user's historical behavior log and account data.
[0082] Among them, the registration duration can be determined according to the user's registration time.
[0083] The preset time period can be set and adjusted according to the actual application scenario, and this embodiment does not specifically limit it. For example, the preset time period can be the last year, the last several months, or the last several days, etc.
[0084] Depending on the user's business identity, the user's active behavior records may be different. For individual users, the user's active behavior records may include the following aspects: page browsing and click records through various channels (such as application APP, fixed terminals, mobile browsers, instant messaging software, etc.); login records; order records; coupon collection and use records; gift card purchase, card binding, and card use records; account balance recharge, use, and withdrawal records; virtual currency (such as points, Jingdou, gold coins, etc.) collection and use records; customer service consultation and after-sales records; financial card binding, payment, real-name, white slips, wallets, financial management, and crowdfunding records; cloud platform trial, consumption, and after-sales records; insurance sub-platform insurance and accident records; logistics sub-platform shipment and points records; and so on.
[0085] For corporate users, it usually includes active behavior records of corporate users as individuals, and on this basis, it also includes active behavior records as companies. For example, warehousing and return records; product shelf and shelf records; promotion creation and manual deletion records; coupon issuance records; virtual currency (such as points, Jingdou, gold coins, etc.) reward issuance records; delivery records; merchant customer service software online records; after-sales return and exchange, compensation records; rebate records; logistics carrier records; bidding records; contract signing records; financial settlement completion records; etc.
[0086] For example, taking JD.com as the service platform, the active behavior records of individual users of JD.com may include: page browsing and click records of users through various channels; login records; order records; coupon collection and use records; gift card purchase, binding and card use records; account balance recharge, use and withdrawal records; Jingdou collection and use records; customer service consultation and after-sales records; financial card binding, payment, real name, Baitiao, wallet, financial management and crowdfunding records; JD Cloud trial, consumption and after-sales records; JD Allianz insurance and accident records; JD Logistics delivery and points records. For corporate users of JD.com, in addition to the above-mentioned active behavior records of individual users, the active behavior records of corporate users may also include: storage and return records; product shelf and shelf records; promotion creation and manual deletion records; coupon issuance records; Jingdou reward issuance records; delivery records; merchant Dongdong online records; after-sales return and exchange, compensation records; rebate records; logistics carrier records; bidding records; contract signing records; financial settlement completion records; etc.
[0087] Step S205: If the user's registration duration and active behavior record meet preset conditions, the user is determined to be a target user.
[0088] In this embodiment, whether each user is a dormant user is determined based on the registration duration and active behavior records of each user.
[0089] For example, based on the user's registration duration and active behavior records, if a user has been registered for a long time but has no active behavior records in the recent period, or has very few active behavior records, the user can be determined to be a dormant user.
[0090] The user's registration duration and active behavior records must meet at least one of the following pre-conditions:
[0091] The registration duration is greater than the preset threshold, and there is no active behavior record less than the preset number of times during the preset period.
[0092] The preset number of times can be set according to the actual application scenario, and is not specifically limited in this embodiment.
[0093] For example, if the preset number of times is 1, this step can be implemented in the following manner:
[0094] If the registration duration of a user is greater than a preset threshold and there is no active behavior record within the preset period, the user is determined to be a target user.
[0095] Specifically, if the registration duration of a user is greater than a preset threshold, and the user does not have any active behavior record within a preset period of time, then it can be determined that the user is a dormant user.
[0096] If the user's registration duration is less than or equal to a preset threshold, or the user has at least one active behavior record within a preset period of time, it can be determined that the user is not a dormant user.
[0097] The preset threshold and the preset period can be set and adjusted according to the actual application scenario, and this embodiment does not specifically limit it. For example, the preset threshold can be one year, the preset period can be the most recent year, etc. The length of the preset threshold and the preset period can be the same or different.
[0098] For example, the preset threshold may be 365 days, and the preset period may be nearly one year. If the user's registration duration is greater than 365 days, and the user has no active behavior record in the past year, the user may be determined to be a dormant user.
[0099] Step S206: Determine the target user's valid identity information, business authority information, virtual resource information, and historical order information based on the dormant user's historical behavior log and account data.
[0100] In actual applications, different dormant users have different levels of activity. For dormant users with different levels of activity, the possibility and value of waking up the users are different.
[0101] In order to wake up sleeping users more flexibly and specifically, in this embodiment, after determining the target user, the activity level information of the target user is first determined based on the target user's historical behavior log and account data, and then different wake-up processes are performed on target users with different activity levels based on the target user's activity level information.
[0102] The activity level information may include the user's valid identity information, business authority information, virtual resource information, and historical order information.
[0103] The valid identity information includes information that can be used to identify the user. For example, the valid identity information may include: associated mobile phone number, bound email address, bound bank card, financial real-name authentication information, set security questions, etc.
[0104] Business authority information refers to information about business authority that the service platform can provide. Exemplarily, business authority information may include: membership, sub-platform membership, rights and interests within the validity period of the business contract, rights and interests within the validity period of the financial system contract, etc.
[0105] Virtual resource information refers to the virtual resources provided by the service platform owned by the user. Exemplarily, the user's virtual resource information may include: the amount of available coupons (including shipping coupons), the balance of available gift cards, the balance of virtual currencies (such as points, Jingdou, gold coins, etc.), the balance of accounts, the balance of wallets, the balance of financial management, the balance of steel coins, and the balance of IOUs. In addition, the virtual resource information of corporate users may also include the total amount to be settled, etc. Among them, the total amount to be settled = the total amount payable by the service platform - the total amount payable by the merchant.
[0106] Historical order information includes orders that record the purchase of physical goods and orders that record the use of virtual services (such as mobile phone recharge services and ticket purchase services provided by the service platform).
[0107] As a possible implementation manner, according to the activity level information of the target user, different wake-up processes are performed on target users with different activity levels, which can be specifically implemented in the following steps S207-S208.
[0108] In another possible implementation, different degrees of wake-up processing can be performed directly according to the valid identity information, business authority information, virtual resource information and historical order information of the target user. The specific implementation can be as follows:
[0109] If the target user has valid identity information, a first user electronic certificate and / or a first amount of virtual resources are issued to the target user, and a first message is pushed to the target user, the first message being used to prompt the target user to use the first type of preferential rights and / or the first amount of virtual resources after logging in. If the target user does not have valid identity information, and the target user has business authority, virtual resources or historical orders, a second user electronic certificate and / or a second amount of virtual resources are issued to the target user, and a second message is pushed to the target user, the second message being used to prompt the target user to use the second type of preferential rights and / or the second amount of virtual resources after logging in; wherein the preferential degree of the second user electronic certificate is less than that of the first user electronic certificate, and the second amount is less than the first amount. If the target user does not have valid identity information, business authority, virtual resources and historical orders, a third type of preferential rights and interests are allocated to the target user, and shared resources are pushed to the target user, the third message being used to prompt the target user to use shared resources after logging in.
[0110] The user electronic certificate refers to the certificate corresponding to the preferential rights and interests issued to the current user and can only be used by the current user after logging in. For example, coupons, discount coupons, cash coupons, etc. issued to users. The preferential degree of the user electronic certificate is the preferential degree of the preferential rights and interests corresponding to the user electronic certificate.
[0111] The first user electronic certificate and the second user electronic certificate may both include one or more different types of user electronic certificates. The first user electronic certificate and the second user electronic certificate have different preferential levels, and the preferential level of the second user electronic certificate is less than that of the first user electronic certificate. Which user electronic certificates the first user electronic certificate and the second user electronic certificate specifically include may be configured and adjusted according to the actual application scenario, and this embodiment does not specifically limit this.
[0112] Shared resources refer to the preferential rights and benefits that are available to all users of the platform or to designated user groups that meet the conditions. For example, all users of the platform can use preferential activities, such as discounts for purchases above a certain amount, prizes for participating in activities, etc.
[0113] In addition, the type and quantity of virtual resources allocated to the target user in this step can be configured and adjusted according to the actual application scenario, and this embodiment does not make any specific restrictions here.
[0114] By pushing prompt information such as the first information, the second information, and the third information to the target user, the user is promptly prompted to use the user resources after logging in, thereby encouraging the target user to log in to the platform as soon as possible. For example, the prompt information can be pushed to the user through a communication method reserved by the user, such as text messages and instant messaging software. This embodiment does not specifically limit the method of pushing information to the target user.
[0115] Among them, the specific push method and specific content of the first information, the second information and the third information can be configured and adjusted according to the actual application scenario, and this embodiment does not make specific limitations here.
[0116] A user with valid identity information refers to a user with at least one valid identity information. A user with business permissions refers to a user with at least one business permission. A user with virtual resources refers to a user whose balance of at least one virtual resource is not 0. A user with historical orders refers to a user with at least one historical order.
[0117] Step S207: determining the activity level information of the target user according to the valid identity information, business authority information, virtual resource information and historical order information of the target user.
[0118] In this embodiment, this step can be implemented in the following manner:
[0119] Based on the target user's valid identity information, business authority information, virtual resource information and historical order information, the activity level of the target user with valid identity information is determined as the first level; the activity level of the target user with business authority, virtual resources or historical orders but without valid identity information is determined as the second level; the activity level of the target user with no business authority, no virtual resources, no historical orders and no valid identity information is determined as the third level.
[0120] For example, the hierarchical identification rules of target users (sleeping users) may be as shown in Table 1 below:
[0121] Table 1
[0122]
[0123] As shown in Table 1, CS1, CS2 and CS3 are the first, second and third levels for dormant users among individual users, respectively; BS1, BS2 and BS3 are the first, second and third levels for dormant users among enterprise users, respectively. As shown in Table 1, whether it is an individual user or an enterprise user, a dormant user satisfies both conditions of "registration time exceeds 365 days" and "no active behavior record in the past year". The identification rules for first-level dormant users may include: the account registration time exceeds 365 days, there is no active behavior record in the past year, there is valid identity information, and there is no requirement for whether there are virtual resources, business permissions and historical orders; and special accounts are excluded. The identification rules for second-level dormant users may include: the account registration time exceeds 365 days, there is no active behavior record in the past year, there is no valid identity information, there are virtual resources or business permissions or there are historical orders, and special accounts are excluded. The identification rules for third-level dormant users may include: the registration time exceeds 365 days, there is no active behavior record in the past year, there is no valid identity information, there are no virtual resources, no business permissions, no historical orders, and special accounts are excluded.
[0124] Optionally, in this step, users can be first divided into two levels according to whether they have valid identity information; for each divided user level, further divided into two levels according to whether they have business authority information, to obtain four user levels; for each of the four divided user levels, further divided into two levels according to whether they have virtual resource information, to obtain eight user levels, and so on.
[0125] Optionally, in this step, at least one of valid identity information, business authority information, virtual resource information and historical order information can be used to divide user levels. Various different user level division methods can be generated according to different arrangements and combinations, which will not be repeated here in this embodiment.
[0126] Step S208: Allocate different user resources to target users of different activity levels and push prompt information.
[0127] In this embodiment, after the activity level of the target user is determined, different wake-up processes are used to wake up users with different activity levels to improve the wake-up success rate.
[0128] Exemplarily, for dormant users with higher activity levels (e.g., the first level in step S207), that is, users who are easier to be awakened, relatively stronger awakening incentives can be implemented. For example, large coupons or virtual resources (e.g., experience points, points, virtual currency, etc.) can be issued to awaken as many of these more active users as possible and improve the success rate of awakening dormant users.
[0129] For dormant users with a low activity level (e.g., the third level in step S207), that is, users who are difficult to wake up, relatively weaker wake-up incentives can be used, such as pushing promotional information to users, which can be issued to test user reactions to avoid wasting more resources.
[0130] In this embodiment, the specific wake-up processing adopted for different activity levels can be set and adjusted according to the actual application scenario and the needs of the service platform, and this embodiment does not make any specific limitations here.
[0131] In addition, by pushing prompt information to the target user, the user is promptly reminded that the user can use user resources after logging in, thereby encouraging the target user to log in to the platform as soon as possible. For example, the prompt information can be pushed to the user through a communication method reserved by the user, such as text messages and instant messaging software. This embodiment does not specifically limit the method of pushing information to the target user.
[0132] Step S209: If the target user does not have valid identity information, the target user is prompted to add valid identity information when logging in.
[0133] In this embodiment, when a dormant user logs in, if the dormant user does not have valid identity information, a prompt message may be displayed to require the dormant user to add valid identity information, thereby improving user quality.
[0134] Exemplarily, in this embodiment, data analysis and aggregation can be performed based on the user's historical behavior log and account data to obtain a summary of user active behavior records within a preset time period, a summary of user valid identity information, a summary of user business permissions, a summary of user virtual resources, and a summary of special accounts; according to the dimension of the user account, each user account contains only one data record in each type of summary data, wherein each type of summary information can be stored in the form of a data table. Then, based on the summary data of all accounts and each dimension, a dormant user index table is determined, including a dormant user index summary and an identity identifier. Based on the dormant user index table and dormant account identification rules (as shown in Table 1), an identification result table is generated to obtain a final model of dormant users. The final model of dormant users fully stores the user's activity level, number of sleep days, and other specified important indicators. For example, taking the service platform as JD.com as an example, the dormant user index summary may include the following: Figure 4 The information shown in .
[0135] The embodiment of the present invention distinguishes between individual users and corporate users, and for each user classification, determines the user's registration duration and active behavior record according to the user's historical behavior log and account data; if the user's registration duration and active behavior record meet the preset conditions, the user is determined to be a target user, and the dormant user can be identified more accurately; further, the activity level information of the target user is determined according to the historical behavior log and account data of the target user; according to the activity level information of the target user, user resources are allocated to the target user, and different user resources are allocated to target users with different activity levels, and prompt information is pushed to the user to prompt the user to use the user resources after logging in, so that different levels of incentives can be used for dormant users with different activity levels in a targeted manner, realizing a more diversified and flexible dormant user awakening mechanism, improving the awakening success rate of dormant users, and thus encouraging dormant users to log in to the platform as soon as possible, avoiding problems such as user data loss, user account loss or password expiration due to long-term non-login to the platform; further, for dormant users who do not have valid identity information, when the user logs in, the user is required to complete the valid identity information, which can improve user quality.
[0136] Figure 5 This is a schematic diagram of the structure of the device for prompting a user to log in to the platform provided in the third embodiment of the present invention. The device for prompting a user to log in to the platform provided in the embodiment of the present invention can execute the processing flow provided in the method embodiment for prompting a user to log in to the platform. Figure 5 As shown, the device 30 for prompting a user to log in to a platform includes: a data processing module 301 , an identification processing module 302 and a wake-up processing module 303 .
[0137] Specifically, the data processing module 301 is used to determine the user's registration duration and active behavior records based on the user's historical behavior log and account data.
[0138] The identification processing module 302 is used to determine that the user is a target user if the user's registration duration and active behavior record meet preset conditions.
[0139] The data processing module 301 is also used to determine the activity level information of the target user according to the historical behavior log and account data of the target user.
[0140] The wake-up processing module 303 is used to allocate corresponding user resources to the target user and push prompt information according to the activity level information of the target user, where the prompt information is used to prompt the user to use the user resources after logging in, wherein different user resources are allocated to target users with different activity levels.
[0141] The device provided in the embodiment of the present invention can be specifically used to execute the method embodiment provided in the above-mentioned embodiment 1, and the specific functions will not be repeated here.
[0142] The embodiment of the present invention determines the user's registration duration and active behavior record based on the user's historical behavior log and account data; if the user's registration duration and active behavior record meet the preset conditions, the user is determined to be a target user, and dormant users can be identified more accurately; further, the target user's activity level information is determined based on the target user's historical behavior log and account data; according to the target user's activity level information, corresponding user resources are allocated to the target user, and different user resources are allocated to target users with different activity levels, and prompt information is pushed to the user to prompt the user to use the user resources after logging in, so that different levels of incentives can be used for dormant users with different activity levels in a targeted manner, realizing a more diversified and flexible dormant user awakening mechanism, improving the dormant user awakening success rate, and thus encouraging dormant users to log in to the platform as soon as possible, avoiding problems such as user data loss, user account loss or password expiration due to long-term non-login to the platform.
[0143] On the basis of the above-mentioned embodiment 3, in this embodiment, the data processing module is further used for:
[0144] Based on the target user's historical behavior logs and account data, determine the target user's valid identity information, business authority information, virtual resource information and historical order information.
[0145] In a possible implementation manner, the wake-up processing module is further configured to:
[0146] If the target user has valid identity information, a first user electronic certificate and / or a first amount of virtual resources are issued to the target user, and a first message is pushed to the target user, the first message being used to prompt the target user to use the first user electronic certificate and / or the first amount of virtual resources after logging in.
[0147] In a possible implementation manner, the wake-up processing module is further configured to:
[0148] If the target user does not have valid identity information, and the target user has business permissions, virtual resources or historical orders, a second user electronic certificate and / or a second quantity of virtual resources will be issued to the target user, and a second message will be pushed to the target user, where the second message is used to prompt the target user to use the second user electronic certificate and / or the second quantity of virtual resources after logging in; wherein the preferential treatment of the second user electronic certificate is less than that of the first user electronic certificate, and the second quantity is less than the first quantity.
[0149] In a possible implementation manner, the wake-up processing module is further configured to:
[0150] If the target user does not have valid identity information, business authority, virtual resources and historical orders, shared resources are allocated to the target user, and third information is pushed to the target user, where the third information is used to prompt the target user to use the shared resources after logging in.
[0151] In a possible implementation manner, the wake-up processing module is further configured to:
[0152] The activity level information of the target user is determined based on the target user's valid identity information, business authority information, virtual resource information and historical order information; different user resources are allocated to target users of different activity levels and prompt information is pushed.
[0153] In a possible implementation manner, the identification processing module is further used for:
[0154] If the user's registration duration is greater than a preset threshold and there is no active behavior record within the preset period, the user is determined to be a target user.
[0155] In a possible implementation manner, the wake-up processing module is further configured to:
[0156] If the target user does not have valid identity information, the target user is prompted to add valid identity information when logging in.
[0157] In a possible implementation manner, the data processing module is further used for:
[0158] According to the user's account data, users with accounts of specified types are eliminated. The specified accounts include at least one of the following:
[0159] Whitelist accounts, accounts that cannot be awakened for login authentication, and accounts that are not registered by actual users.
[0160] In a possible implementation, the data processing module is further used to: determine multiple user categories according to the business identities in the user's account data, where the business identities include at least individual users and corporate users.
[0161] The identification processing module is also used to: for each user category, determine the target user in the user category according to the historical behavior log and account data of the users in the user category, and determine the activity level information of the target user in the user category.
[0162] The wake-up processing module is further used to: allocate user resources corresponding to the user category to the target user in the user category and push prompt information according to the activity level information of the target user in the user category.
[0163] The device provided in the embodiment of the present invention can be specifically used to execute the method embodiment provided in the above-mentioned embodiment 2, and the specific functions will not be repeated here.
[0164] The embodiment of the present invention determines the user's registration duration and active behavior record based on the user's historical behavior log and account data; if the user's registration duration and active behavior record meet the preset conditions, the user is determined to be a target user, and dormant users can be identified more accurately; further, the target user's activity level information is determined based on the target user's historical behavior log and account data; according to the target user's activity level information, corresponding user resources are allocated to the target user, and different user resources are allocated to target users with different activity levels, and prompt information is pushed to the user to prompt the user to use the user resources after logging in, so that different levels of incentives can be used for dormant users with different activity levels in a targeted manner, realizing a more diversified and flexible dormant user awakening mechanism, improving the dormant user awakening success rate, and thus encouraging dormant users to log in to the platform as soon as possible, avoiding problems such as user data loss, user account loss or password expiration due to long-term non-login to the platform.
[0165] Figure 6 This is a schematic diagram of the structure of a device for prompting a user to log in to a platform provided in Embodiment 5 of the present invention. Figure 6 As shown, the device 100 for prompting a user to log in to a platform includes: a processor 1001 , a memory 1002 , and a computer program stored in the memory 1002 and executable on the processor 1001 .
[0166] Among them, when the processor 1001 runs the computer program, it implements the method of prompting the user to log in to the platform provided by any of the above method embodiments.
[0167] The embodiment of the present invention determines the user's registration duration and active behavior record based on the user's historical behavior log and account data; if the user's registration duration and active behavior record meet the preset conditions, the user is determined to be a target user, and dormant users can be identified more accurately; further, the target user's activity level information is determined based on the target user's historical behavior log and account data; according to the target user's activity level information, corresponding user resources are allocated to the target user, and different user resources are allocated to target users with different activity levels, and prompt information is pushed to the user to prompt the user to use the user resources after logging in, so that different levels of incentives can be used for dormant users with different activity levels in a targeted manner, realizing a more diversified and flexible dormant user awakening mechanism, improving the dormant user awakening success rate, and thus encouraging dormant users to log in to the platform as soon as possible, avoiding problems such as user data loss, user account loss or password expiration due to long-term non-login to the platform.
[0168] In addition, an embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method of prompting a user to log in to the platform provided by any of the above method embodiments is implemented.
[0169] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example for illustration. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.
[0170] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art that are not disclosed by the present invention. The description and examples are to be considered exemplary only, and the true scope and spirit of the present invention is indicated by the following claims.
[0171] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.
Claims
1. A method for prompting a user to log in to a platform, characterized in that: include: Determine the user's registration duration and active behavior records based on the user's historical behavior logs and account data; If the user's registration duration and active behavior records meet preset conditions, the user is determined to be a target user; The preset conditions include: the registration duration is greater than a preset threshold, and the number of active behavior records within a preset period is less than a preset number; Determine the valid identity information, business authority information, virtual resource information and historical order information of the target user based on the historical behavior log and account data of the target user; determine the activity level information of the target user based on the valid identity information, the business authority information, the virtual resource information and the historical order information; Different user resources are allocated to target users of different activity levels respectively, and prompt information is pushed to wake up the target users, wherein the prompt information is used to prompt the users to use the user resources after logging in, wherein different user resources are allocated to target users of different activity levels.
2. The method according to claim 1, characterized in that The method of respectively allocating different user resources to target users of different activity levels and pushing prompt information to wake up the target users includes: If the target user has valid identity information, a first user electronic credential and / or a first amount of virtual resources are issued to the target user, and a first message is pushed to the target user to wake up the target user, wherein the first message is used to prompt the target user to use the first user electronic credential and / or the first amount of virtual resources after logging in.
3. The method according to claim 2, characterized in that The method of respectively allocating different user resources to target users of different activity levels and pushing prompt information to wake up the target users includes: If the target user does not have valid identity information, and the target user has business permissions, virtual resources or historical orders, a second user electronic certificate and / or a second amount of virtual resources are issued to the target user, and a second message is pushed to the target user to wake up the target user, where the second message is used to prompt the target user to use the second user electronic certificate and / or the second amount of virtual resources after logging in; The preferential degree of the second user electronic certificate is less than that of the first user electronic certificate, and the second amount is less than the first amount.
4. The method according to claim 3, characterized in that The method of respectively allocating different user resources to target users of different activity levels and pushing prompt information to wake up the target users includes: If the target user does not have valid identity information, business authority, virtual resources and historical orders, shared resources are allocated to the target user, and a third message is pushed to the target user to wake up the target user, wherein the third message is used to prompt the target user to use the shared resources after logging in.
5. The method according to claim 1, characterized in that If the registration duration and active behavior record of the user meet the preset conditions, determining the user as a target user includes: If the registration duration of the user is greater than a preset threshold and there is no active behavior record within a preset period of time, the user is determined to be a target user.
6. The method according to claim 1, characterized in that Also includes: If the target user does not have valid identity information, the target user is prompted to add valid identity information when the target user logs in.
7. The method according to any one of claims 1 to 6, characterized in that Also includes: According to the account data of the user, users with accounts of a specified type are eliminated, where the accounts of the specified type include at least one of the following: Whitelist accounts, accounts that cannot be awakened for login authentication, and accounts that are not registered by actual users.
8. The method according to any one of claims 1 to 6, characterized in that Also includes: Determining multiple user categories according to the business identity in the user's account data, the business identity including at least an individual user and an enterprise user; For each of the user categories, determine the target user in the user category according to the historical behavior logs and account data of the users in the user category, and determine the activity level information of the target user in the user category; According to the activity level information of the target user in the user category, user resources corresponding to the user category are allocated to the target user in the user category, and prompt information is pushed.
9. A device for prompting a user to log in to a platform, characterized in that: include: A data processing module, used to determine the user's registration duration and active behavior records based on the user's historical behavior log and account data; An identification processing module, configured to determine that the user is a target user if the registration duration and active behavior record of the user meet preset conditions; The preset conditions include: the registration duration is greater than a preset threshold, and the number of active behavior records within a preset period is less than a preset number; The data processing module is further used to determine the valid identity information, business authority information, virtual resource information and historical order information of the target user based on the historical behavior log and account data of the target user; determine the activity level information of the target user based on the valid identity information, the business authority information, the virtual resource information and the historical order information; The wake-up processing module is used to allocate different user resources to target users of different activity levels and push prompt information to wake up the target users, wherein the prompt information is used to prompt the users to use the user resources after logging in, wherein the user resources allocated to target users of different activity levels are different.
10. A device for prompting a user to log in to a platform, characterized in that: include: A processor, a memory, and a computer program stored on the memory and executable on the processor; Wherein, when the processor runs the computer program, the method according to any one of claims 1 to 8 is implemented.
11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.
12. A computer program product comprising: A computer program, characterized in that when the computer program is executed by a processor, it is used to implement the method according to any one of claims 1 to 8.
