User touch method and device, electronic equipment and readable storage medium

Abstract

The invention provides a user touch method and device, electronic equipment and a readable storage medium. The method comprises the following steps: receiving first information of user behavior change acquired based on a user behavior burying point; in response to the first information, obtaining a first behavior feature of the updated user, and dividing the corresponding user into a target arrival list according to the first behavior feature; receiving a touch operation instruction for the target touch list; and in response to the touch operation instruction, executing touch operation on the user in the target touch list. According to the method and the device, when the user behavior is changed, the touch list can be updated in time, so that the timeliness and the accuracy of touch work are improved.

Description

Technical Field

[0001] The present invention relates to the field of information processing technology, and in particular to a user contact method, device, electronic device and readable storage medium. Background Art

[0002] User reach refers to the activity of contacting users through various channels and delivering information to users in a targeted manner after analyzing the users in order to achieve specific goals. In the daily operation of big data, relevant reach information will be sent to users from time to time in combination with various information. The list of users reached and the specific reach behavior are often analyzed in a series of data based on user portraits to draw conclusions. In this process, it is necessary to collect multi-dimensional user behavior data to determine the reach list, reach method and reach time as accurately as possible.

[0003] The common data tracking method is to obtain user behavior characteristics to build user portraits, and use the user behavior characteristics of T-1 timeliness to build user portraits at time T, and then decide on subsequent contact plans. However, this solution of using historical data for contact cannot cope with scenarios where data changes in real time, and cannot update contact based on users' immediate operations, making the contact results inaccurate. Summary of the invention

[0004] In view of this, an embodiment of the present invention provides a user reach method, device, electronic device and readable storage medium to solve the problem that the reach information cannot be updated in real time according to user behavior.

[0005] According to one aspect of the present invention, a user contact method is provided, comprising:

[0006] Receiving first information of a user behavior change obtained based on the user behavior tracking point;

[0007] In response to the first information, obtaining a first behavior feature of the updated user, and classifying the corresponding user into a target reach list according to the first behavior feature;

[0008] Receive contact operation instructions for the target contact list;

[0009] In response to the reach operation instruction, the reach operation is performed on the users in the target reach list.

[0010] Optionally, after performing a reach operation on a user in a target reach list in response to the reach operation instruction, the method further includes:

[0011] After a preset time interval, obtain the task running result corresponding to the touch operation;

[0012] In the case where the user behavior information of the user is not included in the task operation result, a reach failure signal is generated and the reach operation is re-executed;

[0013] And, in the case where the user behavior information of the user is included in the task operation result, a reach success signal is generated.

[0014] Optionally, after receiving the first information on the user behavior change obtained based on user behavior logging, it further includes:

[0015] Receiving historical reach information;

[0016] In response to the historical reach information, in the case where the data source corresponding to the first information has not changed, the target reach list is confirmed according to the historical reach information.

[0017] Optionally, after receiving the reach operation instruction for the target reach list, it further includes:

[0018] Receiving the list of users who have not been reached included in the historical reach information;

[0019] Performing a reach operation on the users who have not been reached in the target reach list.

[0020] Optionally, after receiving the first information on the user behavior change obtained based on user behavior logging, it further includes:

[0021] Performing data cleaning and window calculation processing on the user behavior data corresponding to the first information, and generating a reach operation according to the processing result of the first information.

[0022] Optionally, before receiving the first information on the user behavior change obtained based on user behavior logging, it further includes:

[0023] Receiving the historical behavior characteristics of the user;

[0024] In response to the historical behavior characteristics, performing user behavior logging in several tasks;

[0025] When the information on the user behavior change is generated at the logging point of any task, the first information is generated in a preset manner, and the preset manner includes the message queue, data structure, and reporting time frequency where the first information is located.

[0026] According to the second aspect of the present invention, there is provided a user reach device, including:

[0027] A first receiving module, configured to receive the first information on the user behavior change obtained based on user behavior logging;

[0028] A first processing module, in response to the first information, obtaining the first behavior characteristics of the updated user, and classifying the corresponding users into the target reach list according to the first behavior characteristics;

[0029] A second receiving module, configured to receive a reach operation instruction for a target reach list;

[0030] A first execution module, in response to the reach operation instruction, performs a reach operation on the users in the target reach list.

[0031] Optionally, the user reach device further includes:

[0032] A first obtaining module, configured to obtain a task operation result corresponding to the reach operation after a preset time interval;

[0033] A first verification sub-module, configured to generate a reach failure signal and re-perform the reach operation when the user behavior information of the user is not included in the task operation result;

[0034] A second verification sub-module, configured to generate a reach success signal when the user behavior information of the user is included in the task operation result.

[0035] According to a third aspect of the present invention, there is provided an electronic device, including:

[0036] A processor; and

[0037] A memory storing a program,

[0038] wherein the program includes instructions that, when executed by the processor, cause the processor to execute the method according to any one of the first aspects of the present invention.

[0039] According to a fourth aspect of the present invention, there is provided a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to execute the method according to any one of the first aspects of the present invention.

[0040] In one or more technical solutions provided in the embodiments of the present application, by embedding points at each node of the processing task, the first information of the user behavior change is obtained, and the first behavior characteristics of the latest user are analyzed and obtained from the first information, so that the corresponding users are classified into the target reach list according to the first behavior characteristics, achieving the purpose of updating the reach behavior according to the user's instant operation. The present application considers the impact of the user's instant operation on the reach behavior, and performs reach according to the first behavior characteristics of the latest user, avoiding the situation that the reach result is inaccurate due to reaching according to the historical behavior characteristics, and can update the reach list immediately when the user behavior changes, improving the timeliness and accuracy of the reach work. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In the following description of the exemplary embodiments in conjunction with the drawings, more details, features and advantages of the present invention are disclosed. In the drawings:

[0042] Figure 1 Shows a flowchart of a user reach method according to an exemplary embodiment of the present invention;

[0043] Figure 2 Shows a window calculation diagram of a user reach method according to an exemplary embodiment of the present invention;

[0044] Figure 3 Shows an implementation diagram of reach according to an exemplary embodiment of the present invention;

[0045] Figure 4 Shows a data flow diagram of a user reach method according to an exemplary embodiment of the present invention;

[0046] Figure 5 Shows an operation monitoring diagram according to an exemplary embodiment of the present invention;

[0047] Figure 6 Shows an error feedback diagram according to an exemplary embodiment of the present invention;

[0048] Figure 7 Shows a reach information comparison diagram of a user reach method according to an exemplary embodiment of the present invention;

[0049] Figure 8 Shows a buried point flowchart of a user reach method according to an exemplary embodiment of the present invention;

[0050] Figure 9 Shows a schematic block diagram of a user reach device according to an exemplary embodiment of the present invention;

[0051] Figure 10 Shows a structural block diagram of an exemplary electronic device that can be used to implement an embodiment of the present invention. Detailed implementation manners

[0052] The embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present invention. It should be understood that the drawings and embodiments of the present invention are only for exemplary purposes and are not used to limit the protection scope of the present invention.

[0053] It should be understood that the steps recorded in the method embodiments of the present invention can be executed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this regard.

[0054] As used herein, the term "including" and its variations are open-ended, that is, "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description. It should be noted that the concepts such as "first", "second", etc. mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0055] It should be noted that the modifications of "one" and "a plurality of" mentioned in the present invention are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly specified in the context, it should be understood as "one or more".

[0056] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only for illustrative purposes, and are not used to limit the scope of these messages or information.

[0057] The following describes the solution of the present invention with reference to the accompanying drawings, and details the technical solutions provided by the embodiments of the present application through specific embodiments and their application scenarios.

[0058] In the existing user reach methods, the push time of reach information is very important for the reach effect, and it is necessary to grasp user preferences and the living habits of the regular user group, etc. If the instant operation of the user on an application such as an APP cannot get an instant response, the demand scenario is likely to be lost. In addition, for some reach scenarios, feedback is required immediately after the user's action is completed in real time. For example, service notifications based on the user's completion of a certain action, such as order placement reminders, consumption reminders, etc. Therefore, the existing offline processing means used in the user reach method have the defect of poor timeliness. The method often uses the user behavior characteristics with T-1 timeliness to make the reach action decision on the Tth day.

[0059] The setting of offline processing of historical user behavior data with T-1 timeliness will result in a situation where the reach time is delayed due to offline latency in the scenario of a large amount of users plus complex reach processing logic. The user portrait has changed, while the offline data can only obtain the user portrait before the change, and such reach effect is greatly reduced.

[0060] In view of this, the present invention provides a user reach method, device, electronic device and readable storage medium. Among them, the user reach method is applied to any electronic device with user reach function, and the electronic device includes but is not limited to: personal mobile terminal devices, computers or server devices, etc.

[0061] As shown in Figure 1 the figure, Figure 1 FIG. 1 is a schematic flowchart of a user reach method provided by an embodiment of the present application. The method may include the following steps S101 to S104:

[0062] S101, receiving first information on the change of the user behavior obtained based on user behavior logging.

[0063] As an implementation manner, by presetting user behavior logging in different tasks, user behavior data generated by the user in real time in different tasks can be obtained, and when the user behavior data changes, first information on the change of the user behavior is generated.

[0064] As a specific implementation manner, the user reach method is applied to an APP in the field of credit risk control. Different tasks may be other APPs in the same device as the APP in the field of credit risk control. By logging at each node of other APPs, the APP in the field of credit risk control can instantaneously obtain user behavior data from different data sources, establish a user profile based on the user behavior data, and perform analysis.

[0065] In the APP in the field of credit risk control, user behaviors include different behaviors such as pulling new users, returning of old users, and performing financial operations generated by different data sources. When the behavior data of user A is financial operation data, if the behavior data of pulling new users appears, it indicates that user A has a change in user behavior, and first information for user A will be generated. When the behavior data of user B is old user return data, if the behavior data of performing financial operations appears, it indicates that user B has a change in user behavior, and first information for user B will be generated.

[0066] As a specific implementation manner, as shown in Figure 2 the figure, a window assigner Window Assigner is used to divide the user behavior data obtained in real time into multiple time windows according to time. The main function of the Window Assigner is to divide the data stream into continuous time windows so that the data in each window can be processed and calculated separately. Whenever first information is generated in any time window, the first information is output downstream.

[0067] S102, in response to the first information, obtaining the first behavior characteristics of the updated user, and classifying the corresponding user into the target reach list according to the first behavior characteristics.

[0068] As an implementation, according to the first information changed by the user behavior, update the historical behavior characteristics of the user to obtain the updated first behavior characteristics, and classify the user into the target reach list according to the first behavior characteristics. Among them, when the historical behavior characteristics are updated to the first behavior characteristics, the user portrait obtained from the historical behavior characteristics is also updated.

[0069] As a specific implementation, in the APP in the field of credit risk control, after the user behavior changes, the historical behavior characteristics of the user will be obtained at the time of change, and the historical behavior characteristics will be updated to obtain the updated first behavior characteristics of the user. User portraits are created based on the first behavior characteristics, enabling users to be accurately classified into the target reach list.

[0070] Specifically, if the historical behavior data of user A is financial operation data, then the historical behavior characteristics of user A are financial operation characteristics. After user A shows the behavior data of pulling in new users, the historical behavior characteristics are updated to the first behavior characteristics, and the first behavior characteristics include financial operation characteristics and the characteristics of pulling in new people. Creating user portraits based on these two characteristics will classify user A into the target reach list for financial information reach and pulling in new people reach, achieving more accurate reach for user A and avoiding the situation of inaccurate reach results caused by missing user updates.

[0071] At the same time, the method of updating historical behavior characteristics according to the first information only needs to obtain historical behavior characteristics when receiving the first information, which can avoid obtaining historical behavior characteristics multiple times and the problem of high data processing pressure caused by multiple acquisitions.

[0072] S103, receive a reach operation instruction for the target reach list.

[0073] As an implementation, when generating reach operation instructions for different target reach lists in the APP in the field of credit risk control, reach information is transmitted to users in different target reach lists.

[0074] S104, in response to the reach operation instruction, perform a reach operation on the users in the target reach list.

[0075] As an implementation, users in different target reach lists receive reach information and perform their respective reach operations.

[0076] As a specific implementation, as Figure 3 shown, in the field of financial risk control, several confirmed target reach lists are written into the downstream database MYSQL to facilitate the acquisition of parallel reach logics for multiple users and multiple tasks in the database MYSQL.

[0077] According to the input structured query language (SQL), simple aggregation and interaction are performed to obtain the marketing list that is reached according to the reach operation instructions. In the aggregation process, only simple logical screening is required to obtain the latest results, which improves the efficiency and effect of reaching, greatly shortens the update and iteration time, and can achieve instant reach.

[0078] In one embodiment of the present application, S104, in response to the reach operation instruction, after performing the reach operation on the user in the target reach list, further includes:

[0079] S105, after a preset time interval, obtaining a task running result corresponding to the reaching operation;

[0080] S106, when the task execution result does not include the user behavior information of the user, generating a reach failure signal and re-executing the reach operation;

[0081] S107, and, when the task execution result includes the user behavior information of the user, generating a successful reach signal.

[0082] As an implementation method, the existing contact solutions lack a verification mechanism for the output of contact results. The accuracy of the user contact system's actions cannot be guaranteed, which can easily lead to a reduced user experience. The framework and distributed processing engine Flink itself does not provide such a result calibration solution, and the running status of the built-in tasks has performance bottlenecks, and the delay in indicator collection gradually increases.

[0083] Therefore, after reaching out to the user, the task running results corresponding to the reaching operation are obtained at preset intervals to verify the reaching effect. By verifying the association between the task running results and the user, it is determined whether the reaching has failed, and the user is reached again after failure. By means of verification after reaching out, the integrity of the reaching system can be guaranteed, the implementation of the reaching operation can be ensured, and the reaching effect and success rate can be improved.

[0084] As a specific implementation method, after user A is classified into the target reach list for financial consumption reach, user A is reached to consume in the APP in the field of credit risk control, and then the task running result of the APP in the field of credit risk control is obtained to determine whether the result contains the consumption behavior information of user A. If it does, it means that the reach method successfully allows user A to consume, and the reach result is successful. If the result does not contain the consumption behavior information of user A, the reach fails, and the reach operation needs to be performed again for user A.

[0085] As a specific implementation method, after user B is classified into the target reach list for pulling new user reach from other data sources, user B is reached for registration in the APP in the field of credit risk control, and then the task operation result of the APP in the field of credit risk control is obtained to determine whether the result contains the registration behavior information of user B. If it contains, it means that the reach method has successfully enabled user B to register, and the reach result is successful. If the result does not contain the registration behavior information of user B, the reach fails and the reach operation needs to be performed on user B again.

[0086] In an implementation manner of the present application, as Figure 4 shown, user reach needs to obtain APP buried point data and real-time change logs from multiple APPs, that is, obtain the user behavior data of the user in multiple APPs and the first information of the user behavior changes in multiple APPs, and transmit the user behavior data and the first information using the distributed publish-subscribe message system Kafka as the message queue. The framework and the distributed processing engine Flink read and process the information transmitted by Kafka, and write the processed result into the downstream adapted database. Connect to different relational databases through Java Database Connectivity (JDBC) to facilitate the monitoring of features in the user dimension and variable dimension in different databases. Through the monitoring of features in the user dimension and variable dimension, it is used to verify whether the user reach is successful.

[0087] As a specific implementation method, as Figure 5 shown, after performing the reach operation on the user in the target reach list, monitoring and verification in the user dimension and variable dimension are carried out. That is, the result produced by the real-time task is verified to ensure the accuracy of user reach. The time granularity of the monitoring system is customized. After customization, the monitoring system runs regularly, supporting minute-level result verification and alarm. For the verification in the user dimension, verify the association between the task operation result and the user to know whether the reach behavior has been implemented according to the reach list, and then judge whether the reach fails, and re-perform user reach after failure.

[0088] For the verification in the variable dimension, as Figure 6 shown, the reach operation performed on the user in the target reach list will be reconciled with the offline historical reach information to ensure the accuracy of the variable output result of the real-time task.

[0089] If the executed reach operation combined with the first information is inconsistent with the result of the historical reach information and the inconsistency ratio exceeds the threshold, save the consumption progress, record the checkpoint address of the task operation snapshot, pause the task and perform attribution analysis on the problem, and quickly stop the loss of reach mistakes.

[0090] In an embodiment of the present application, after receiving the first information on the change of the user behavior obtained based on the user behavior buried points in S101, it further includes:

[0091] S101a, receiving historical reach information;

[0092] S101b, in response to the historical reach information, when the data source corresponding to the first information has not changed, confirming the target reach list according to the historical reach information.

[0093] As an implementation method, in order to reduce the data congestion caused by obtaining historical behavior characteristics, historical reach information with a T-1 time limit can be obtained. If the data source corresponding to the first information has not changed, the target reach list can be confirmed according to the reach list in the historical reach information, thereby reducing the data processing process and accelerating the reach progress.

[0094] As a specific implementation method, after pre-burying points in different data source APPs and obtaining the user behavior data of user A in the first APP, user A uninstalled the first APP and then generated user behavior data in the second APP. Then, the first information on the change of user A's behavior was generated, and the target reach list was changed according to the first behavior characteristics of user A. In this case, the data source of user A has changed, and the corresponding target reach list needs to be re-determined.

[0095] However, if the behavior data of user B in the APP in the field of credit risk control changes from registration behavior data to the behavior data of pulling new users, and then the first information on the change of user behavior is generated. Since the data source has not changed, the target reach list can be confirmed according to the historical reach information. That is, user B can still be classified into the target reach list for pulling new users or the target reach list for consumption reach, without the need to additionally obtain the first behavior characteristics and divide the target reach list.

[0096] As a specific implementation method, as Figure 7 shown, obtain the historical reach information with a T-1 time limit, and judge whether the user corresponding to the first information on the change of the user behavior is in the historical reach list with a T-1 time limit. If not in the historical reach list, it means that the user is not within the previous reach range, and the user is not processed, reducing the marketing cost. If in the historical reach list, then judge whether the user has updated behavior characteristics. If so, use Flink to perform real-time processing on the updated first information. If not, the original reach mode is not changed, and there is no need to additionally obtain the first behavior characteristics and divide the target reach list.

[0097] In an embodiment of the present application, after receiving the reach operation instruction for the target reach list in S103, it further includes:

[0098] S103a, receiving the list of users who have not been reached included in the historical reach information;

[0099] S103b, performing a reach operation on the users who have not been reached in the target reach list.

[0100] As an implementation method, in order to avoid omitting some users in the historical reach work and avoid omitting the users who failed to be reached in the historical reach work, it is necessary to obtain the list of users who have not been reached included in the historical reach information and divide the corresponding target reach list for the users who have not been reached. This is convenient for reaching these users who have not been reached when reaching the target reach list.

[0101] As a specific implementation method, in the historical reach work, after obtaining the list of users who have not been reached included in the historical reach information and knowing that user A has been omitted and not reached, the corresponding target reach list of user A is determined, and after receiving the reach operation instruction for the target reach list, user A who has been omitted is reached at the same time.

[0102] As a specific implementation method, in the historical reach work, after obtaining the list of users who have not been reached included in the historical reach information and knowing that the reach of user B failed, the corresponding target reach list of user B is determined, and after receiving the reach operation instruction for the target reach list, user B who failed to be reached is reached again at the same time.

[0103] In an embodiment of the present application, after receiving the first information on the change of the user behavior obtained based on user behavior buried points in S101, it further includes:

[0104] S101c, performing data cleaning and window calculation processing on the user behavior data corresponding to the first information, and generating a reach operation according to the processing result of the first information.

[0105] As an implementation method, data cleaning is performed on the user behavior data corresponding to the first information. The process of data cleaning includes identifying and correcting errors, missing values, invalid values, and inconsistencies in the data to ensure the accuracy, integrity, and consistency of the data.

[0106] Then, the window calculation is triggered by the user behavior change driving the window, and a reach operation is generated according to the first information after the user behavior change, which can accurately reach the user and avoid the delay of the reach time. It realizes the effect of transferring the data processing work of the data aggregated in one window to any time period triggered in real time and reducing the instantaneous pressure of the processing.

[0107] As a specific implementation, user A's user behavior changed at 10:00, and the system generated a log and recorded the generation time of the log as 10:00. Next, this data was sent to the distributed publish-subscribe messaging system Kafka, and then processed using the framework and the distributed processing engine Flink. When the data arrived at Flink, the system time of Flink was 10:02. At this time, 10:02 refers to the processing time, while 10:00 is the event time. If you want to accurately obtain information about the user behavior change, you need to use the time when the data was generated (i.e., the event time), rather than the processing time of Flink.

[0108] Therefore, it is necessary to clean the data for errors, missing values, invalid values, and inconsistencies, and then perform window calculation processing to generate reach operations corresponding to the event time of the user behavior change, ensuring the accuracy of subsequent reach work.

[0109] In an implementation manner of the present application, before S101, receiving the first information of the user behavior change obtained based on user behavior tracing, it further includes:

[0110] S101d, receiving the historical behavior characteristics of the user;

[0111] S101e, in response to the historical behavior characteristics, performing user behavior tracing in several tasks;

[0112] S101f, when generating the information of the user behavior change at the tracing point of any one of the tasks, generating the first information in a preset manner, and the preset manner includes the message queue, data structure, and reporting time frequency where the first information is located.

[0113] As an implementation manner, by analyzing the historical behavior characteristics of the user, tracing is performed at places where the user may generate behavior data. The tracing data monitors whether the user behavior has changed. If it has changed, the data structure of the first information is adjusted in a preset manner, and the first information is sent to the preset message queue according to the reporting time frequency. The setting of the reporting time frequency is to prevent the blocking of multiple messages. Therefore, in the case of a large number of messages, the first information is reported in an orderly manner.

[0114] As a specific implementation, as Figure 8 shown, performing user behavior tracing in several tasks includes analyzing and confirming the activities to be collected by tracing (i.e., confirming the tracing event) according to the historical behavior characteristics of the user, and then confirming the tracing trigger mechanism. The tracing trigger mechanism includes a page stay time mechanism, a page view count mechanism, or a page click mechanism, etc.

[0115] When the event triggering mechanism for data logging is the page dwell time mechanism, record the dwell time of the user on a certain page. The user dwell time = the time t2 when the user leaves the page - the time t1 when the user enters the page. When the user dwell time reaches the expectation, message reporting is performed. When the event triggering mechanism for data logging is the page view count mechanism, the reporting mechanism is to record once when the user successfully enters a page, and also record once when the page is refreshed. When the recorded count reaches the expectation, message reporting is performed. When the event triggering mechanism for data logging is the page click mechanism, record the event triggered by the user clicking on an object on the page, and report the click behavior as a message.

[0116] In the user reach method provided in the embodiments of the present application, by logging data at each node of the processing task, the first information of the user behavior change is obtained, and the latest first behavior characteristics of the user are analyzed from the first information. Then, according to the first behavior characteristics, the corresponding users are divided into the target reach list, so as to achieve the purpose of updating the reach behavior according to the user's immediate operations. The present application takes into account the impact of the user's immediate operations on the reach behavior, and performs the reach according to the latest first behavior characteristics of the user, avoiding the situation where the reach result is inaccurate due to reaching according to the historical behavior characteristics. It can update the reach list immediately when the user behavior changes, improving the timeliness and accuracy of the reach work.

[0117] Corresponding to the above embodiments, refer to Figure 9 , the embodiments of the present application also provide a user reach device 900, including:

[0118] A first receiving module 901, configured to receive the first information of the user behavior change obtained based on user behavior logging;

[0119] A first processing module 902, in response to the first information, obtains the updated first behavior characteristics of the user, and divides the corresponding users into the target reach list according to the first behavior characteristics;

[0120] A second receiving module 903, configured to receive a reach operation instruction for the target reach list;

[0121] A first execution module 904, in response to the reach operation instruction, performs a reach operation on the users in the target reach list.

[0122] Optionally, the user reach device 900 further includes:

[0123] A first obtaining module 905, configured to obtain the task running result corresponding to the reach operation after a preset time interval;

[0124] The first parity check sub-module 906 is configured to generate a reach failure signal and re-execute the reach operation when the user behavior information of the user is not included in the task operation result;

[0125] The second parity check sub-module 907 is configured to generate a reach success signal when the user behavior information of the user is included in the task operation result.

[0126] Optionally, the user reach device 900 further includes:

[0127] The third receiving module 908 is configured to receive historical reach information;

[0128] The first confirmation module 909, in response to the historical reach information, when the data source corresponding to the first information has not changed, confirms the target reach list according to the historical reach information.

[0129] Optionally, the user reach device 900 further includes:

[0130] The third receiving module 910 is configured to receive the list of users who have not been reached included in the historical reach information;

[0131] The second execution module 911 is configured to perform a reach operation on the users who have not been reached in the target reach list.

[0132] Optionally, the user reach device 900 further includes:

[0133] The second processing module 912 is configured to perform data cleaning and window calculation processing on the user behavior data corresponding to the first information, and generate a reach operation according to the processing result of the first information.

[0134] Optionally, the user reach device 900 further includes:

[0135] The fourth receiving module 913 is configured to receive the historical behavior characteristics of the user;

[0136] The third processing module 914, in response to the historical behavior characteristics, performs user behavior logging in several tasks;

[0137] The fourth processing module 915 is configured to generate the first information in a preset manner when information on the change of the user behavior is generated at the logging point of any one of the tasks, and the preset manner includes the message queue, data structure, and reporting time frequency where the first information is located.

[0138] In the embodiment of the present application, the user reach device provided obtains the first information of the user behavior change by embedding points at each node of the processing task, analyzes and obtains the first behavior characteristics of the latest user from the first information, and thus divides the corresponding user into the target reach list according to the first behavior characteristics, achieving the purpose of updating the reach behavior according to the user's immediate operation. The present application considers the impact of the user's immediate operation on the reach behavior, and performs the reach according to the first behavior characteristics of the latest user, avoiding the inaccurate reach result caused by reaching according to the historical behavior characteristics. It can update the reach list immediately when the user behavior changes, improving the timeliness and accuracy of the reach work.

[0139] An exemplary embodiment of the present invention further provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program executable by the at least one processor, and the computer program, when executed by the at least one processor, is used to cause the electronic device to execute the method according to the embodiment of the present invention.

[0140] An exemplary embodiment of the present invention further provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to execute the method according to the embodiment of the present invention.

[0141] An exemplary embodiment of the present invention further provides a computer program product, including a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to execute the method according to the embodiment of the present invention.

[0142] Reference Figure 10 , the structural block diagram of the electronic device 1000 that can be used as the server or client of the present invention will now be described. It is an example of a hardware device that can be applied to various aspects of the present invention. The electronic device is intended to represent various forms of digital electronic computer devices, such as, laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as, personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or claimed herein.

[0143] As Figure 10As shown, the electronic device 1000 includes a computing unit 1001, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 1002 or a computer program loaded from a storage unit 1008 into a random access memory (RAM) 1003. In the RAM 1003, various programs and data required for the operation of the device 1000 can also be stored. The computing unit 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0144] A plurality of components in the electronic device 1000 are connected to the I / O interface 1005, including: an input unit 1006, an output unit 1007, a storage unit 1008, and a communication unit 1009. The input unit 1006 can be any type of device capable of inputting information into the electronic device 1000. The input unit 1006 can receive input numerical or character information, and generate key signal inputs related to user settings and / or function controls of the electronic device. The output unit 1007 can be any type of device capable of presenting information, and can include but is not limited to a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The storage unit 1008 can include but is not limited to a magnetic disk, an optical disk. The communication unit 1009 allows the electronic device 1000 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks, and can include but is not limited to a modem, a network card, an infrared communication device, a wireless communication transceiver, and / or a chipset, such as a BluetoothTM device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.

[0145] The computing unit 1001 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 1001 include but are not limited to a central processing module (CPU), a graphics processing module (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The computing unit 1001 executes the various methods and processes described above. For example, in some embodiments, the user reach method can be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 1008. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 1000 via the ROM 1002 and / or the communication unit 1009. In some embodiments, the computing unit 1001 can be configured to execute the user reach method in any other appropriate manner (e.g., by means of firmware).

[0146] The program code for implementing the method of the present invention can be written in any combination of one or more programming languages. These program codes can be provided to the processor or controller of a general-purpose computer, a special-purpose computer, or other programmable user-accessible devices, such that when the program codes are executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program codes can be executed entirely on the machine, partially on the machine, partially on the machine as an independent software package and partially on a remote machine, or entirely on a remote machine or server.

[0147] In the context of the present invention, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0148] As used in the present invention, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., a disk, an optical disk, a memory, a programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0149] In order to provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0150] The systems and techniques described herein can be implemented in a computing system including backend components (e.g., as a data server), or a computing system including middleware components (e.g., an application server), or a computing system including frontend components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described herein), or a computing system including any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include: local area network (LAN), wide area network (WAN), and the Internet.

[0151] A computer system can include clients and servers. Clients and servers are generally far apart from each other and typically interact through a communication network. The client - server relationship is created by computer programs running on the respective computers and having a client - server relationship with each other.

Claims

1. A user contact method, characterized in that: include: Receiving first information about the user behavior change obtained based on the user behavior tracking point; In response to the first information, obtaining the updated first behavior feature of the user, and classifying the corresponding user into a target reach list according to the first behavior feature; Receiving a reach operation instruction for the target reach list; In response to the reach operation instruction, a reach operation is performed on the user in the target reach list.

2. The user contact method according to claim 1, characterized in that: After performing the reaching operation on the user in the target reaching list in response to the reaching operation instruction, the method further includes: After a preset time interval, obtaining the task running result corresponding to the reaching operation; If the task execution result does not include the user behavior information of the user, generating a reach failure signal and re-executing the reach operation; And, when the task execution result includes the user behavior information of the user, a successful reach signal is generated.

3. The user contact method according to claim 1, characterized in that: After receiving the first information of the user behavior change obtained based on the user behavior tracking point, the method further includes: Receive historical contact information; In response to the historical reach information, when the data source corresponding to the first information has not changed, the target reach list is confirmed according to the historical reach information.

4. The user contact method according to claim 1, characterized in that: After receiving the reaching operation instruction for the target reaching list, the method further includes: Receiving a list of unreached users included in the historical reach information; Perform a reaching operation on the unreached users in the target reaching list.

5. The user contact method according to claim 1, characterized in that: After receiving the first information of the user behavior change obtained based on the user behavior tracking point, the method further includes: Perform data cleaning and window calculation processing on the user behavior data corresponding to the first information, and generate a reach operation based on the processing result of the first information.

6. The user contact method according to claim 1, characterized in that: Before receiving the first information of the user behavior change obtained based on the user behavior tracking point, the method further includes: Receiving historical behavior characteristics of the user; In response to the historical behavior characteristics, user behavior tracking is performed in a plurality of tasks; When the information about the change in user behavior is generated at any of the task's tracking points, the first information is generated in a preset manner, which includes the message queue, data structure, and reporting time frequency where the first information is located.

7. A user contact device, characterized in that: include: A first receiving module, used to receive first information of the user behavior change obtained based on the user behavior tracking point; A first processing module, in response to the first information, obtains the updated first behavior feature of the user, and classifies the corresponding user into a target reach list according to the first behavior feature; A second receiving module is used to receive a reach operation instruction for the target reach list; The first execution module performs a reach operation on the user in the target reach list in response to the reach operation instruction.

8. The user access device according to claim 7, characterized in that: The user access device further includes: A first acquisition module, used to acquire the task running result corresponding to the reaching operation after a preset time interval; A first verification submodule, configured to generate a reach failure signal and re-execute the reach operation when the task execution result does not contain the user behavior information of the user; The second verification submodule is used to generate a successful reach signal when the task execution result includes the user behavior information of the user.

9. An electronic device, comprising: processor; as well as Memory for storing programs, The program includes instructions, which, when executed by the processor, cause the processor to perform the method according to any one of claims 1 to 6.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to make a computer execute the method according to any one of claims 1-6.

Images