User event processing method and apparatus, electronic device, and readable storage medium
By establishing a user behavior event tree, the problem of isolated user behavior events is solved, enabling deeper data analysis and behavior prediction, and improving application performance.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SF TECH CO LTD
- Filing Date
- 2021-09-10
- Publication Date
- 2026-06-16
AI Technical Summary
In existing methods of collecting user behavior data, user behavior events are relatively isolated, making it difficult to analyze user behavior data in depth.
By obtaining the identifiers of target sub-user events, the target functional events are identified, and a user behavior event tree is established to record the correlation between each user event, including the correlation between sub-events of the same user and different users.
It enhances the correlation of user behavior events, enabling deeper analysis of user behavior data and improving future behavior prediction and application performance.
Smart Images
Figure CN115795100B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, specifically to a user event processing method, apparatus, electronic device, and computer-readable storage medium. Background Technology
[0002] With the rapid development of internet technology, various software applications, such as client applications and web applications, have emerged in an endless stream. In order for applications to better meet users' needs, they often collect user behavior events in various functional modules of the application with the user's consent, analyze user behavior preferences, and so on, in order to improve the performance of each functional module of the application.
[0003] It is evident that user behavior events have significant guiding value for improving application performance. Current technologies primarily collect user behavior events from various functional modules through event tracking. However, these collected user behavior events are relatively isolated, with weak correlations between any two events. Therefore, these collected user behavior events are typically only suitable for simple data analysis such as total pageviews and visitor counts, and are insufficient for in-depth analysis of user behavior data. Summary of the Invention
[0004] This application provides a user event processing method, apparatus, electronic device, and computer-readable storage medium, aiming to solve the problem that existing user behavior data collection methods collect relatively isolated user behavior events, making it difficult to conduct in-depth analysis of user behavior data.
[0005] Firstly, this application provides a user event handling method, the method comprising:
[0006] When a sub-user event is triggered for the target application, obtain the target sub-event identifier of the triggered target sub-user event;
[0007] Based on the target sub-event identifier, the target functional event corresponding to the target sub-user event is determined, wherein the target functional event includes multiple sub-user events;
[0008] Obtain the target maintenance event tree corresponding to the target function event;
[0009] Based on the target sub-event identifier, the node count of the target maintenance event tree is updated to obtain the user behavior event tree of the target functional event, wherein the user behavior event tree is used to establish the association between various user events related to the target functional event.
[0010] In some embodiments of this application, the node count includes the number of sub-event triggers recorded by the target node corresponding to the target sub-event identifier;
[0011] The step of updating the node count of the target maintained event tree based on the target sub-event identifier to obtain the user behavior event tree of the target functional event includes:
[0012] From each tree node of the target maintenance event tree, determine the target node corresponding to the target sub-event identifier;
[0013] Update the sub-event trigger counts recorded in the target node to obtain the user behavior event tree of the target function event.
[0014] In some embodiments of this application, the node count includes the number of sub-event triggers recorded by the target node corresponding to the target sub-event identifier;
[0015] The step of updating the node count of the target maintained event tree based on the target sub-event identifier to obtain the user behavior event tree of the target functional event includes:
[0016] Detect whether there is a target node corresponding to the target sub-event identifier in each tree node of the target maintenance event tree;
[0017] If there is no target node corresponding to the target sub-event identifier in any of the tree nodes of the target maintenance event tree, then the sub-event decomposition relationship of the target functional event is obtained;
[0018] Based on the sub-event decomposition relationship, add the target node to the target maintenance event tree;
[0019] Update the sub-event trigger counts recorded in the target node to obtain the user behavior event tree of the target function event.
[0020] In some embodiments of this application, the target node in the user behavior event tree corresponding to the target sub-event identifier also records the user identifier of the target sub-user event, and the method further includes:
[0021] Obtain the target user identifier of the user to be analyzed;
[0022] Obtain the target behavior structured data corresponding to the target user identifier from the user behavior event tree;
[0023] Based on the target behavior structure data, predict the future behavior or target matching content of the user to be analyzed.
[0024] In some embodiments of this application, after predicting the target matching content of the user to be analyzed based on the target behavior structure data, the method further includes:
[0025] The target matching content is pushed to the target application interface corresponding to the user to be analyzed.
[0026] In some embodiments of this application, the user behavior event tree is an event tree in the user behavior event tree set of the target application, and the method further includes:
[0027] Based on the user behavior event tree set, target events or user needs in the target application are determined, wherein the target events include at least one of the target application's abnormal events, popular events, and high conversion rate events.
[0028] In some embodiments of this application, obtaining the target maintenance event tree corresponding to the target functional event includes:
[0029] Check if there is an event tree in the preset maintenance event tree that corresponds to the target function event;
[0030] If there is an event tree corresponding to the target function event in the preset maintenance event tree, then the target maintenance event tree corresponding to the target function event is obtained from the preset maintenance event tree.
[0031] In some embodiments of this application, after detecting whether there is an event tree corresponding to the target function event in the preset maintenance event tree, the method further includes:
[0032] If there is no event tree corresponding to the target function event in the preset maintenance event tree, then the sub-event decomposition relationship of the target function event is obtained;
[0033] Based on the sub-event decomposition relationship, a target maintenance event tree corresponding to the target function event is established.
[0034] In some embodiments of this application, the method further includes:
[0035] Displays a user behavior event tree of the target function events.
[0036] Secondly, this application provides a user event processing device, the user event processing device comprising:
[0037] The first acquisition unit is used to acquire the target sub-event identifier of the triggered target sub-user event when there is a sub-user event triggered for the target application.
[0038] The determining unit is configured to determine the target functional event corresponding to the target sub-user event based on the target sub-event identifier, wherein the target functional event includes multiple sub-user events;
[0039] The second acquisition unit is used to acquire the target maintenance event tree corresponding to the target functional event;
[0040] An update unit is used to update the node count of the target maintenance event tree based on the target sub-event identifier to obtain the user behavior event tree of the target functional event, wherein the user behavior event tree is used to establish the association between various user events related to the target functional event.
[0041] In some embodiments of this application, the node count includes the number of sub-event triggers recorded by the target node corresponding to the target sub-event identifier, and the update unit is specifically used for:
[0042] From each tree node of the target maintenance event tree, determine the target node corresponding to the target sub-event identifier;
[0043] Update the sub-event trigger counts recorded in the target node to obtain the user behavior event tree of the target function event.
[0044] In some embodiments of this application, the node count includes the number of sub-event triggers recorded by the target node corresponding to the target sub-event identifier, and the update unit is specifically used for:
[0045] Detect whether there is a target node corresponding to the target sub-event identifier in each tree node of the target maintenance event tree;
[0046] If there is no target node corresponding to the target sub-event identifier in any of the tree nodes of the target maintenance event tree, then the sub-event decomposition relationship of the target functional event is obtained;
[0047] Based on the sub-event decomposition relationship, add the target node to the target maintenance event tree;
[0048] Update the sub-event trigger counts recorded in the target node to obtain the user behavior event tree of the target function event.
[0049] In some embodiments of this application, the target node in the user behavior event tree corresponding to the target sub-event identifier also records the user identifier of the target sub-user event. The user event processing device further includes a prediction unit, which is specifically used for:
[0050] Obtain the target user identifier of the user to be analyzed;
[0051] Obtain the target behavior structured data corresponding to the target user identifier from the user behavior event tree;
[0052] Based on the target behavior structure data, predict the future behavior or target matching content of the user to be analyzed.
[0053] In some embodiments of this application, after the step of predicting the target matching content of the user to be analyzed based on the target behavior structure data, the prediction unit is specifically used for:
[0054] The target matching content is pushed to the target application interface corresponding to the user to be analyzed.
[0055] In some embodiments of this application, the user behavior event tree is an event tree in the user behavior event tree set of the target application, and the user event processing device further includes an analysis unit, which is specifically used for:
[0056] Based on the user behavior event tree set, target events or user needs in the target application are determined, wherein the target events include at least one of the target application's abnormal events, popular events, and high conversion rate events.
[0057] In some embodiments of this application, the second acquisition unit is specifically used for:
[0058] Check if there is an event tree in the preset maintenance event tree that corresponds to the target function event;
[0059] If there is an event tree corresponding to the target function event in the preset maintenance event tree, then the target maintenance event tree corresponding to the target function event is obtained from the preset maintenance event tree.
[0060] In some embodiments of this application, after the step of detecting whether there is an event tree corresponding to the target function event in the preset maintenance event tree, the second acquisition unit is specifically used for:
[0061] If there is no event tree corresponding to the target function event in the preset maintenance event tree, then the sub-event decomposition relationship of the target function event is obtained;
[0062] Based on the sub-event decomposition relationship, a target maintenance event tree corresponding to the target function event is established.
[0063] In some embodiments of this application, the user event processing device further includes a display unit, which is specifically used for:
[0064] Displays a user behavior event tree of the target function events.
[0065] Thirdly, this application also provides an electronic device, which includes a processor and a memory, wherein the memory stores a computer program, and when the processor invokes the computer program in the memory, it executes the steps in any of the user event handling methods provided in this application.
[0066] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, the computer program being loaded by a processor to execute the steps in the user event handling method.
[0067] When a sub-user event triggered by a target application exists, this application determines the target functional event corresponding to the sub-user event by obtaining the target sub-event identifier of the triggered target sub-user event and, based on the target sub-event identifier, obtains the target maintenance event tree corresponding to the target functional event; and updates the node count of the target maintenance event tree based on the target sub-event identifier to obtain the user behavior event tree of the target functional event. On the one hand, since the target functional event is split into multiple sub-user events and recorded in the form of an event tree, the correlation of the behavioral events within the target functional event itself is enhanced. On the other hand, since the sub-user events triggered by each user are recorded in an event tree, a certain correlation can also be established between the various user behavioral events. As can be seen, this application can establish the correlation between various user behavior events related to functional events (including the correlation between various sub-events of the same user, and the correlation between various sub-events or functional events of different users), avoiding the relative isolation between user behavior events. This allows for a deeper analysis of user behavior data, improving the accuracy of analyzing future user behavior or target matching content, abnormal events of the target application, popular events, and high conversion rate events, thereby further contributing to the improvement of target application performance. Attached Figure Description
[0068] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0069] Figure 1 This is a schematic diagram of a user event processing system provided in an embodiment of this application;
[0070] Figure 2 This is a flowchart illustrating a user event handling method provided in an embodiment of this application;
[0071] Figure 3 This is a schematic diagram illustrating the association between functional events and sub-user events provided in the embodiments of this application;
[0072] Figure 4 This is a schematic diagram of an embodiment of the event tree provided in this application.
[0073] Figure 5This is an illustrative diagram illustrating the node count of the update target maintenance event tree in an embodiment of this application;
[0074] Figure 6 This is a schematic diagram of an embodiment of the user event processing device provided in this application.
[0075] Figure 7 This is a schematic diagram of an embodiment of the electronic device provided in this application. Detailed Implementation
[0076] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0077] In the description of the embodiments of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, features defined with "first" and "second" may explicitly or implicitly include one or more of the stated features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly specified.
[0078] To enable any person skilled in the art to implement and use this application, the following description is provided. In this description, details are set forth for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be implemented without using these specific details. In other instances, well-known processes will not be described in detail to avoid obscuring the description of the embodiments of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in the embodiments of this application.
[0079] The execution entity of the user event processing method in this application embodiment can be the user event processing device provided in this application embodiment, or a distributed processing system integrating the user event processing device; wherein, the distributed processing system includes a message middleware (e.g., Kafka message middleware) for sending and receiving user events from various clients and a real-time computing node (e.g., Flink real-time computing node) for processing user events. Alternatively, it can be a server device, physical host, or user equipment (UE) or other different types of electronic devices that integrate the user event processing device; wherein, the user event processing device can be implemented in hardware or software, and the UE can specifically be a smartphone, tablet computer, laptop computer, handheld computer, desktop computer, or personal digital assistant (PDA) or other terminal device.
[0080] The electronic device can operate independently or in a cluster. By applying the user event processing method provided in this application, the correlation between various user behavior events related to functional events can be established, avoiding the relative isolation between user behavior events, thereby enabling a deeper analysis of user behavior data.
[0081] See Figure 1 , Figure 1 This is a schematic diagram of a user event processing system provided in an embodiment of this application. The user event processing system may include an electronic device 100, which integrates a user event processing unit. For example, when a sub-user event triggered for a target application exists, the electronic device can: obtain the target sub-event identifier of the triggered target sub-user event; determine the target functional event corresponding to the target sub-user event based on the target sub-event identifier, wherein the target functional event includes multiple sub-user events; obtain a target maintenance event tree corresponding to the target functional event; and update the node count of the target maintenance event tree based on the target sub-event identifier to obtain a user behavior event tree for the target functional event, wherein the user behavior event tree is used to establish associations between various user events related to the target functional event.
[0082] In addition, such as Figure 1 As shown, the user event processing system may also include a memory 200 for storing data, such as user events.
[0083] It should be noted that, Figure 1The schematic diagram of the user event processing system shown is merely an example. The user event processing system and scenario described in this application embodiment are for the purpose of more clearly illustrating the technical solutions of this application embodiment and do not constitute a limitation on the technical solutions provided in this application embodiment. As those skilled in the art will know, with the evolution of user event processing systems and the emergence of new business scenarios, the technical solutions provided in the embodiments of this invention are also applicable to similar technical problems.
[0084] The following describes the user event processing method provided in the embodiments of this application. In this embodiment, an electronic device is used as the execution subject. For simplicity and ease of description, the execution subject will be omitted in the subsequent method embodiments. The user event processing method includes: when there is a sub-user event triggered for a target application, obtaining the target sub-event identifier of the triggered target sub-user event; determining the target functional event corresponding to the target sub-user event based on the target sub-event identifier, wherein the target functional event includes multiple sub-user events; obtaining the target maintenance event tree corresponding to the target functional event; updating the node count of the target maintenance event tree based on the target sub-event identifier to obtain the user behavior event tree of the target functional event, wherein the user behavior event tree is used to establish the association between various user events related to the target functional event.
[0085] Reference Figure 2 , Figure 2 This is a flowchart illustrating a user event handling method provided in an embodiment of this application. It should be noted that although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here. The user event handling method includes steps 201-204, wherein:
[0086] 201. When there is a sub-user event triggered for the target application, obtain the target sub-event identifier of the triggered target sub-user event.
[0087] The target application can be any type of client-side app, such as a shopping service app or a logistics service app. The target application can also be any type of web application, such as a third-party shopping service mini-program or a browser-based shopping service application.
[0088] User events refer to user actions within a target application, such as clicking or typing.
[0089] The user event-related data involved in this application embodiment is obtained, stored and used with the consent of the user, the parties involved or related parties, provided that relevant information protection laws and regulations are complied with.
[0090] To better understand the embodiments of this application, the relationship between functional events, sub-user events, and event trees in the embodiments of this application will be introduced below.
[0091] 1. Functional events.
[0092] A functional event refers to a series of actions performed by a user in response to a function provided by a target application. For example, ... Figure 3 As shown, the user's actions in sending a package through the target application, such as selecting the sender's address, selecting the recipient's address, selecting the shipping method, signing the terms and conditions, selecting coupons, and paying the shipping fee, can be considered as a single functional event.
[0093] 2. Sub-user events.
[0094] A sub-user event refers to a specific action within a series of actions corresponding to a functional event. For example, ... Figure 3 As shown, for the parcel sending function provided by the target application, any one of the following actions can be regarded as a sub-user event: selecting the sender's address, selecting the recipient's address, selecting the sending method, signing the terms, selecting coupons, and paying the shipping fee.
[0095] Among them, target sub-user events refer to detected and triggered sub-user events.
[0096] As can be seen, a function event contains multiple sub-user events.
[0097] 3. Event tree.
[0098] An event tree can be a relational database or a tree diagram used to record the relationships between user events.
[0099] In this embodiment, an event tree is established for each functional event based on the relationships between its sub-user events. This tree serves as the maintenance event tree for that functional event, used to maintain the relationships between user events related to that functional event. Each node in the maintenance event tree represents a sub-user event, such as... Figure 4 As shown, Figure 4 Two maintenance event trees are shown in the figure. Figure 4 Each circle in the event tree maintains a node in the event tree, and each letter represents a sub-user event.
[0100] The maintenance event tree of multiple functional events of the target application can form an event forest.
[0101] 4. Sub-event identifier.
[0102] To facilitate the differentiation and recording of each sub-user event, different identifiers are assigned to different sub-user events in this embodiment of the application to clarify different user behaviors. A sub-event identifier refers to the identifier of a sub-user event. A target sub-event identifier refers to the identifier of a target sub-user event.
[0103] For example, before step 201, the method further includes: detecting whether there are sub-user events triggered for the target application. The target application may include multiple functional events, and each functional event may include multiple sub-user events. The existence of any one sub-user event confirms the presence of a sub-user event triggered for the target application. Since the target application may be deployed on multiple clients, in some embodiments, "detecting whether there are sub-user events triggered for the target application" may specifically include: detecting whether each client hosting the target application has a sub-user event triggered for the target application.
[0104] Specifically, in step 201, there are multiple ways to obtain the target sub-event identifier of the target sub-user event, including, for example:
[0105] (1) When a sub-user event triggered against a target application is detected, the currently triggered sub-user event can be obtained in real time as the target sub-user event. In steps 203 to 204, the node count of the event tree is updated for the sub-user event triggered in real time. At this time, the step of "obtaining the target sub-event identifier of the triggered target sub-user event" may specifically include: obtaining the sub-event identifier of the currently triggered sub-user event in real time as the target sub-event identifier of the target sub-user event.
[0106] (2) Obtain all sub-user events triggered for the target application within a certain period of time as the target sub-user event. In steps 203 to 204, update the node count of the event tree for the sub-user events triggered within a certain period of time. At this time, the step of "obtaining the target sub-event identifier of the triggered target sub-user event" may specifically include: obtaining the sub-event identifier of all sub-user events triggered for the target application within a certain period of time as the target sub-event identifier of the target sub-user event.
[0107] 202. Based on the target sub-event identifier, determine the target functional event corresponding to the target sub-user event.
[0108] From the description of "the relationship between functional events, sub-user events and the event tree" in step 201 above, it can be seen that a functional event contains multiple sub-user events, that is, the target functional event includes multiple sub-user events.
[0109] A target function event is a function event that includes target sub-user events.
[0110] In step 202, there are multiple ways to determine the target functional event corresponding to the target sub-user event. For example, the association between each sub-user event and each functional event is pre-stored in a preset database. "Determining the target functional event corresponding to the target sub-user event based on the target sub-event identifier" may specifically include: based on the association between each sub-user event and each functional event stored in the preset database, querying the target functional event that has an association with the target sub-user event corresponding to the target sub-event identifier.
[0111] For example, there are relationships between each sub-user event and each functional event as shown in Table 1 below. If the target sub-event of the target sub-user event is identified as "B1", then the target functional event "Event 1" that is associated with the target sub-user event identified as "B1" can be found from the pre-stored relationships in the database.
[0112] Table 1
[0113] Functional events Sub-user events Event 1 Sub-event A1, sub-event A2, ... Event 2 Sub-event B1, sub-event B2, sub-event B3, ... … … Event n Sub-event n1, sub-event n2, sub-event n3, ...
[0114] 203. Obtain the target maintenance event tree corresponding to the target function event, and use it as the target maintenance event tree for the target sub-user event.
[0115] The target maintenance event tree is an event tree used to record the relationships between various user events related to the target function events.
[0116] The target maintenance event tree is a maintenance event tree used to record target sub-user events, that is, the target maintenance event tree corresponding to the target function events corresponding to the target sub-user events.
[0117] In step 203, there are multiple ways to obtain the target maintenance event tree corresponding to the target function event, including, for example:
[0118] (1) Establish the target maintenance event tree in real time. At this time, step 203 may specifically include: obtaining the sub-event decomposition relationship of the target function event; and establishing the target maintenance event tree corresponding to the target function event based on the sub-event decomposition relationship.
[0119] The sub-event decomposition relationship refers to the hierarchical relationship between the various sub-user events of the target function event, such as the order of operations. For example, Figure 3 The hierarchical relationship between the various operations in the express delivery function shown is the sub-event decomposition relationship of the express delivery function.
[0120] (2) Obtain the target maintenance event tree corresponding to the target functional event from the maintenance event tree of each functional event that has been pre-established in the target application. At this time, step 203 may specifically include: obtaining the target maintenance event tree corresponding to the target functional event from the preset maintenance event tree.
[0121] The preset maintenance event tree refers to the maintenance event tree of each functional event that has been pre-established in the target application.
[0122] For example, such as Figure 4 As shown, the preset maintenance event tree includes maintenance event tree A and maintenance event tree P. Figure 4 (a) in the text represents the maintenance event tree P of functional event 1. Functional event 1 includes sub-events P to Z. Tree nodes P to Z in the maintenance event tree P are used to record sub-events P to Z respectively. Figure 4 In the diagram, (b) represents the maintenance event tree A of functional event 2. Functional event 2 includes sub-events A to O. Tree nodes A to O in the maintenance event tree A are used to record sub-events A to O, respectively.
[0123] If the target sub-user event is detected as "sub-event W", then in step 202, the target function event corresponding to the target sub-user event (sub-event W) can be determined as "function event 1". In step 203, the target maintenance event tree "maintenance event tree P" set corresponding to the target function event "function event 1" can be obtained as the target maintenance event tree used to record the target sub-user event.
[0124] If the target sub-user event is detected as "sub-event G", then in step 202, the target function event corresponding to the target sub-user event (sub-event G) can be determined as "function event 2". In step 203, the target maintenance event tree "maintenance event tree A" set corresponding to the target function event "function event 2" can be obtained as the target maintenance event tree used to record the target sub-user event.
[0125] (3) Detect whether a target maintenance event tree exists in the pre-established maintenance event trees of each functional event of the target application. If it exists, directly obtain the target maintenance event tree corresponding to the target functional event from the pre-established maintenance event trees of each functional event of the target application. If it does not exist, establish the target maintenance event tree in real time based on the sub-event decomposition relationship of the target functional event. In this case, step 203 may specifically include: detecting whether an event tree corresponding to the target functional event exists in the preset maintenance event tree; if an event tree corresponding to the target functional event exists in the preset maintenance event tree, obtain the target maintenance event tree corresponding to the target functional event from the preset maintenance event tree. If an event tree corresponding to the target functional event does not exist in the preset maintenance event tree, obtain the sub-event decomposition relationship of the target functional event; establish the target maintenance event tree corresponding to the target functional event based on the sub-event decomposition relationship.
[0126] 204. Based on the target sub-event identifier, update the node count of the target maintained event tree to obtain the user behavior event tree of the target functional event.
[0127] The user behavior event tree is used to establish the association between various user behavior data related to the target function event.
[0128] Among them, the node count is the number of sub-events triggered by each node in the event tree.
[0129] The node count of the target event tree includes the node count of the target node corresponding to the target sub-event identifier, specifically including the number of sub-event triggers recorded by the target node corresponding to the target sub-event identifier.
[0130] In step 204, there are several ways to update the node count of the target maintained event tree, including, for example:
[0131] (1) If a target node corresponding to the target sub-event identifier exists in the target maintenance event tree, directly update the node count of the target node in the target maintenance event tree. In this case, step 204 may specifically include the following steps 2041A to 2042A:
[0132] 2041A. From each tree node of the target maintenance event tree, determine the target node corresponding to the target sub-event identifier.
[0133] Among them, the target node refers to the tree node in the target maintained event tree that is used to record the sub-user events corresponding to the target sub-event identifier.
[0134] like Figure 5As shown, for example, if step 203 determines that the target maintenance event tree is "maintenance event tree A" and the sub-user event corresponding to the target sub-event identifier "G" is "sub-event G", then in step 2041, the tree node "G" used to record the sub-user event "sub-event G" corresponding to the target sub-event identifier "G" can be determined from each tree node of the target maintenance event tree "maintenance event tree A" as the target node corresponding to the target sub-event identifier "G".
[0135] 2042A. Update the sub-event trigger count recorded in the target node to obtain the user behavior event tree of the target function event.
[0136] For example, taking the above target sub-user event as a single target sub-user event, the number of sub-event triggers recorded before the target node is increased by 1 to obtain the target maintenance event tree after the node count of the target node is updated, which serves as the user behavior event tree for the target function event.
[0137] To make it easier to understand, let's continue with the example from step 2041, such as... Figure 5 As shown, the target node corresponding to the target sub-event identifier "G" is "G", and the current sub-event trigger count recorded by the target node "G" is "1". Figure 5 As shown in (a); based on the sub-event trigger quantity "1" recorded before the target node "G", 1 is added to obtain the target maintenance event tree after the node count of the target node is updated to "2", which serves as the user behavior event tree for the target functional event, as shown in (a). Figure 5 As shown in (b) of the diagram.
[0138] (2) The target maintenance event tree may not necessarily contain a target node corresponding to the target sub-event identifier. It is necessary to first check whether a target node exists in the target maintenance event tree. If it exists, the node count of the target node in the target maintenance event tree can be updated directly. If it does not exist, the target node needs to be added to the target maintenance event tree first, and then the node count of the target node in the target maintenance event tree needs to be updated. In this case, step 204 may specifically include the following steps 2041B to 2044B, wherein:
[0139] 2041B. Detect whether there is a target node corresponding to the target sub-event identifier in each tree node of the target maintenance event tree.
[0140] For example, it can be detected whether there is a node in the target maintenance event tree with the same identifier as the target sub-event identifier; if there is a node in the target maintenance event tree with the same identifier as the target sub-event identifier, it is determined that there is a target node in the target maintenance event tree corresponding to the target sub-event identifier; if there is no node in the target maintenance event tree with the same identifier as the target sub-event identifier, it is determined that there is no target node in the target maintenance event tree corresponding to the target sub-event identifier.
[0141] like Figure 5 As shown, for example, if the target sub-event is identified as "H", and there is no node in the target maintenance event tree with the same identifier as the target sub-event, then it is determined that there is no target node in the target maintenance event tree corresponding to the target sub-event identifier. Similarly, if the target sub-event is identified as "E", and there is a node in the target maintenance event tree with the same identifier as the target sub-event, then it is determined that there is a target node in the target maintenance event tree corresponding to the target sub-event identifier.
[0142] 2042B. If there is no target node corresponding to the target sub-event identifier in any of the tree nodes of the target maintenance event tree, then obtain the sub-event decomposition relationship of the target functional event.
[0143] The sub-event decomposition relationship refers to the hierarchical relationship between the various sub-user events of the target function event, such as the order of operations. For example, Figure 3 The hierarchical relationship between the various operations in the express delivery function shown is the sub-event decomposition relationship of the express delivery function.
[0144] If there is a target node in each tree node of the target maintenance event tree that corresponds to the target sub-event identifier, then the sub-event trigger quantity recorded by the target node can be directly updated in the target node of the target maintenance event tree to obtain the user behavior event tree of the target function event.
[0145] 2043B. Based on the sub-event decomposition relationship, add the target node to the target maintenance event tree.
[0146] For example, based on the sub-event decomposition relationship of the target functional event, the relationship tree node that has a hierarchical relationship with the target sub-user event is determined from the target maintenance event tree; a new node is connected to the relationship tree node as the target node, thereby realizing the addition of the target node in the target maintenance event tree.
[0147] 2044B. Update the sub-event trigger count recorded in the target node to obtain the user behavior event tree of the target function event.
[0148] The implementation of step 2044B is similar to that of step 2042A. For details, please refer to the description of step 2044B above. For the sake of simplicity, it will not be repeated here.
[0149] As can be seen from the above, in this embodiment, when a sub-user event triggered for the target application exists, the target sub-event identifier of the triggered target sub-user event is obtained. Based on the target sub-event identifier, the target functional event corresponding to the target sub-user event is determined; the target maintenance event tree corresponding to the target functional event is obtained; and based on the target sub-event identifier, the node count of the target maintenance event tree is updated to obtain the user behavior event tree of the target functional event. On the one hand, since the target functional event is split into multiple sub-user events and recorded in the form of an event tree, the correlation of the behavioral events of the target functional event itself is enhanced. On the other hand, since the sub-user events triggered by each user are recorded in an event tree, a certain correlation can also be established between the various user behavioral events. As can be seen, the embodiments of this application can establish the correlation between various user behavior events related to functional events (including the correlation between various sub-events of the same user, and the correlation between various sub-events or functional events of different users), avoiding the relative isolation between user behavior events. This allows for a deeper analysis of user behavior data, improving the accuracy of analysis of future user behavior or target matching content, abnormal events of the target application, popular events, and high conversion rate events, thereby further contributing to the improvement of target application performance.
[0150] Furthermore, to facilitate the visualization of user behavior data, in some embodiments, after obtaining the user behavior event tree of the target function event, the user behavior event tree of the target function event can be further displayed. Specifically, the user behavior event tree of the target function event can be displayed through the execution entity electronic device of this application embodiment; alternatively, the user behavior event tree of the target function event can be sent to other terminals, such as mobile phones, computers, etc., and displayed through other terminals.
[0151] For each functional event of the target application, a user behavior event tree can be determined. For each functional module provided in the target application, multiple functional events can be triggered, thus allowing for the determination of multiple user behavior event trees. These multiple user behavior event trees of the target application can constitute an event forest, reflecting the overall user events of the target application. In other words, the user behavior event tree of the target functional event is one event tree in the set of user behavior event trees of the target application.
[0152] Furthermore, after determining the user behavior event tree set of the target application, analysis can be performed based on the user behavior event tree set to determine target events (such as abnormal events, popular events, high conversion rate events, etc.) or user needs in the target application. That is, the user event processing method can further include: determining the target events or user needs in the target application based on the user behavior event tree set, wherein the target events include at least one of abnormal events, popular events, and high conversion rate events of the target application.
[0153] Among these, abnormal events can be user events involving abnormal access. Popular events can be user events involving high traffic. High conversion rate events can be user events involving click-through rates exceeding a preset click-through rate.
[0154] The abnormal events, popular events, and high conversion rate events listed here are just examples. The specific examples can be adjusted according to the actual business scenario requirements and are not limited to this.
[0155] In this embodiment of the application, a structured user behavior event tree is used to determine target events or user needs in the target application. Since the structured user behavior event tree can reflect the relationship between various user events, it can mine deeper user behavior data, thereby improving the accuracy of determining target events or user needs.
[0156] Furthermore, to analyze individual users, behavioral data for each user can be extracted from the user behavior event tree. The target node in the user behavior event tree corresponding to the target sub-event identifier also records the user identifier of the target sub-user event. This user event processing method can further include: obtaining the target user identifier of the user to be analyzed; obtaining structured target behavior data corresponding to the target user identifier from the user behavior event tree; and predicting the future behavior or target matching content of the user to be analyzed based on the target behavior structured data.
[0157] Among them, the target behavior structured data refers to the collection of sub-user events that have been triggered by the user to be analyzed and have connections (such as hierarchical relationships).
[0158] Here, "future behavior" can refer to actions the user to be analyzed is likely to take in the future. "Target matching content" can be content that the user to be analyzed is interested in. The future behavior and target matching content listed here are merely examples and can be adjusted according to the actual business scenario requirements; they are not limited to this.
[0159] In this embodiment, by obtaining structured target behavior data corresponding to the target user identifier from the structured user behavior event tree, structured user behavior data can be extracted to predict the future behavior of the user to be analyzed or the target matching content. Since the structured user behavior data establishes the correlation between various user behavior data, deeper levels of user behavior data can be mined, making the predicted future behavior of the user to be analyzed or the target matching content more realistic.
[0160] Furthermore, to improve the performance of the target application and thus enhance the user experience, after determining the target matching content for the user to be analyzed, the target matching content can be pushed to the target application interface corresponding to the user. Here, the target application interface refers to the application interface of the target application used by the user to be analyzed.
[0161] To better understand the embodiments of this application, a specific example is given below. For instance, taking the user event processing device integrated into a Flink real-time computing node and sending and receiving user events from various clients through the Kafka message middleware as an example, the specific implementation of the user event processing method can be as follows:
[0162] 1) Obtain triggered target sub-user events from each client through the Kafka message middleware.
[0163] 2) For each target sub-user event obtained from the Kafka message middleware, group them according to the user identifier to facilitate subsequent recording of target sub-user events triggered by different users.
[0164] 3) Determine the target function event corresponding to the target sub-event based on the target sub-event identifier.
[0165] 4) Determine if a target maintenance relationship tree corresponding to the target functional event exists in the preset maintenance event tree. If not, obtain and generate the target maintenance relationship tree corresponding to the target functional event based on the sub-event decomposition relationship of the target functional event; use the target maintenance event tree as the target maintenance event tree for the target sub-user event, update the node count of the target maintenance event tree, and obtain the user behavior event tree for the target functional event. If it exists, obtain the target maintenance event tree corresponding to the target functional event from the preset maintenance event tree, update the node count of the target maintenance event tree, and obtain the user behavior event tree for the target functional event.
[0166] 5) Through steps 1)-4) above, all sub-user events triggered by the target application over a period of time can be structurally recorded, forming a user behavior event tree for each target function event in the target application. This results in an event forest for the target application.
[0167] 6) Use the user behavior event tree in the event forest of the target application to identify target events or user needs in the target application; or, predict future user behavior or target matching content. Alternatively, visualize the user behavior event tree in the event forest of the target application for analysis by relevant personnel.
[0168] To better implement the user event handling method in the embodiments of this application, based on the user event handling method, the embodiments of this application also provide a user event handling device, such as... Figure 6 The diagram shown is a structural schematic of one embodiment of the user event processing device in this application. The user event processing device 600 includes:
[0169] The first acquisition unit 601 is used to acquire the target sub-event identifier of the triggered target sub-user event when there is a sub-user event triggered for the target application.
[0170] The determining unit 602 is configured to determine the target functional event corresponding to the target sub-user event based on the target sub-event identifier, wherein the target functional event includes multiple sub-user events;
[0171] The second acquisition unit 603 is used to acquire the target maintenance event tree corresponding to the target function event;
[0172] The update unit 604 is used to update the node count of the target maintenance event tree based on the target sub-event identifier to obtain the user behavior event tree of the target functional event, wherein the user behavior event tree is used to establish the association between various user events related to the target functional event.
[0173] In some embodiments of this application, the node count includes the number of sub-event triggers recorded by the target node corresponding to the target sub-event identifier, and the update unit 604 is specifically used for:
[0174] From each tree node of the target maintenance event tree, determine the target node corresponding to the target sub-event identifier;
[0175] Update the sub-event trigger counts recorded in the target node to obtain the user behavior event tree of the target function event.
[0176] In some embodiments of this application, the node count includes the number of sub-event triggers recorded by the target node corresponding to the target sub-event identifier, and the update unit 604 is specifically used for:
[0177] Detect whether there is a target node corresponding to the target sub-event identifier in each tree node of the target maintenance event tree;
[0178] If there is no target node corresponding to the target sub-event identifier in any of the tree nodes of the target maintenance event tree, then the sub-event decomposition relationship of the target functional event is obtained;
[0179] Based on the sub-event decomposition relationship, add the target node to the target maintenance event tree;
[0180] Update the sub-event trigger counts recorded in the target node to obtain the user behavior event tree of the target function event.
[0181] In some embodiments of this application, the target node in the user behavior event tree corresponding to the target sub-event identifier also records the user identifier of the target sub-user event. The user event processing device 600 further includes a prediction unit (not shown in the figure), which is specifically used for:
[0182] Obtain the target user identifier of the user to be analyzed;
[0183] Obtain the target behavior structured data corresponding to the target user identifier from the user behavior event tree;
[0184] Based on the target behavior structure data, predict the future behavior or target matching content of the user to be analyzed.
[0185] In some embodiments of this application, after the step of predicting the target matching content of the user to be analyzed based on the target behavior structure data, the prediction unit is specifically used for:
[0186] The target matching content is pushed to the target application interface corresponding to the user to be analyzed.
[0187] In some embodiments of this application, the user behavior event tree is an event tree in the user behavior event tree set of the target application, and the user event processing device 600 further includes an analysis unit (not shown in the figure), the analysis unit being specifically used for:
[0188] Based on the user behavior event tree set, target events or user needs in the target application are determined, wherein the target events include at least one of the target application's abnormal events, popular events, and high conversion rate events.
[0189] In some embodiments of this application, the second acquisition unit 603 is specifically used for:
[0190] Check if there is an event tree in the preset maintenance event tree that corresponds to the target function event;
[0191] If there is an event tree corresponding to the target function event in the preset maintenance event tree, then the target maintenance event tree corresponding to the target function event is obtained from the preset maintenance event tree.
[0192] In some embodiments of this application, after the step of detecting whether there is an event tree corresponding to the target function event in the preset maintenance event tree, the second acquisition unit 603 is specifically used for:
[0193] If there is no event tree corresponding to the target function event in the preset maintenance event tree, then the sub-event decomposition relationship of the target function event is obtained;
[0194] Based on the sub-event decomposition relationship, a target maintenance event tree corresponding to the target function event is established.
[0195] In some embodiments of this application, the user event processing device 600 further includes a display unit (not shown in the figure), the display unit being specifically used for:
[0196] Displays a user behavior event tree of the target function events.
[0197] In practice, each of the above units can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units, please refer to the previous method embodiments, which will not be repeated here.
[0198] Because this user event handling device can execute the application, such as Figures 1 to 5 Corresponding to the steps in the user event handling method in any embodiment, this application can be implemented as described above. Figures 1 to 5 For details on the beneficial effects that the user event handling method can achieve in any embodiment, please refer to the preceding description, which will not be repeated here.
[0199] Furthermore, to better implement the user event handling method in the embodiments of this application, based on the user event handling method, the embodiments of this application also provide an electronic device, see below. Figure 7 , Figure 7 This illustration shows a structural diagram of an electronic device according to an embodiment of this application. Specifically, the electronic device provided in this embodiment includes a processor 701, which executes a computer program stored in a memory 702 to implement, for example... Figures 1 to 5 Corresponding to each step of the user event handling method in any embodiment; or, when the processor 701 executes the computer program stored in the memory 702, it implements as follows: Figure 6 The functions of each unit in the corresponding embodiment.
[0200] For example, a computer program can be divided into one or more modules / units, one or more of which are stored in memory 702 and executed by processor 701 to complete the embodiments of this application. One or more modules / units can be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in a computer device.
[0201] The electronic device may include, but is not limited to, processor 701 and memory 702. Those skilled in the art will understand that the illustrations are merely examples of an electronic device and do not constitute a limitation on the electronic device. It may include more or fewer components than illustrated, or combine certain components, or different components. For example, the electronic device may also include input / output devices, network access devices, buses, etc., and processor 701, memory 702, input / output devices, and network access devices are connected via a bus.
[0202] The processor 701 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor. The processor is the control center of the electronic device, connecting various parts of the electronic device through various interfaces and lines.
[0203] The memory 702 can be used to store computer programs and / or modules. The processor 701 implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory 702 and by calling data stored in the memory 702. The memory 702 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device (such as audio data, video data, etc.). In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, RAM, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.
[0204] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the user event processing device, electronic equipment, and their corresponding units described above can be referred to as follows: Figures 1 to 5 The description of the user event handling method corresponding to any embodiment will not be repeated here.
[0205] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.
[0206] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to execute the present application. Figures 1 to 5 For the steps in the user event handling method corresponding to any embodiment, please refer to the following for specific operations: Figures 1 to 5 The descriptions of the user event handling methods corresponding to any embodiment will not be repeated here.
[0207] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.
[0208] Because of the instructions stored in the computer-readable storage medium, the present application can be executed as described above. Figures 1 to 5 Corresponding to the steps in the user event handling method in any embodiment, this application can be implemented as described above. Figures 1 to 5For details on the beneficial effects that the user event handling method can achieve in any embodiment, please refer to the preceding description, which will not be repeated here.
[0209] The foregoing has provided a detailed description of a user event processing method, apparatus, electronic device, and computer-readable storage medium provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A user event handling method, characterized in that, The method includes: When a sub-user event is triggered for the target application, obtain the target sub-event identifier of the triggered target sub-user event; Based on the target sub-event identifier, the target functional event corresponding to the target sub-user event is determined, wherein the target functional event includes multiple sub-user events; Obtain the target maintenance event tree corresponding to the target function event; Based on the target sub-event identifier, the node count of the target maintenance event tree is updated to obtain the user behavior event tree of the target functional event. The user behavior event tree is used to establish the association between various user events related to the target functional event. The node count includes the sub-event triggering quantity recorded by the target node corresponding to the target sub-event identifier. If the target node does not exist in any of the tree nodes of the target maintenance event tree, the sub-event decomposition relationship of the target functional event is obtained. According to the sub-event decomposition relationship, the target node is added to the target maintenance event tree, and the sub-event triggering quantity recorded by the target node is updated.
2. The user event handling method according to claim 1, characterized in that, The step of updating the node count of the target maintained event tree based on the target sub-event identifier to obtain the user behavior event tree of the target functional event includes: From each tree node of the target maintenance event tree, determine the target node corresponding to the target sub-event identifier; Update the sub-event trigger counts recorded in the target node to obtain the user behavior event tree of the target function event.
3. The user event handling method according to claim 1, characterized in that, Before obtaining the sub-event decomposition relationship of the target functional event if the target node does not exist in any of the tree nodes of the target maintenance event tree, the method further includes: Detect whether there is a target node corresponding to the target sub-event identifier in each tree node of the target maintenance event tree.
4. The user event handling method according to claim 1, characterized in that, The target node in the user behavior event tree corresponding to the target sub-event identifier also records the user identifier of the target sub-user event, and the method further includes: Obtain the target user identifier of the user to be analyzed; Obtain the target behavior structured data corresponding to the target user identifier from the user behavior event tree; Based on the target behavior structure data, predict the future behavior or target matching content of the user to be analyzed.
5. The user event handling method according to claim 4, characterized in that, After predicting the target matching content for the user to be analyzed based on the target behavior structure data, the method further includes: The target matching content is pushed to the target application interface corresponding to the user to be analyzed.
6. The user event handling method according to claim 1, characterized in that, The user behavior event tree is one of the event trees in the user behavior event tree set of the target application, and the method further includes: Based on the user behavior event tree set, target events or user needs in the target application are determined, wherein the target events include at least one of the target application's abnormal events, popular events, and high conversion rate events.
7. The user event handling method according to claim 1, characterized in that, The step of obtaining the target maintenance event tree corresponding to the target function event includes: Check if there is an event tree in the preset maintenance event tree that corresponds to the target function event; If there is an event tree corresponding to the target function event in the preset maintenance event tree, then the target maintenance event tree corresponding to the target function event is obtained from the preset maintenance event tree.
8. The user event handling method according to claim 7, characterized in that, After detecting whether a pre-defined maintenance event tree exists that corresponds to the target function event, the method further includes: If there is no event tree corresponding to the target function event in the preset maintenance event tree, then the sub-event decomposition relationship of the target function event is obtained; Based on the sub-event decomposition relationship, a target maintenance event tree corresponding to the target function event is established.
9. The user event handling method according to any one of claims 1-8, characterized in that, The method further includes: Displays a user behavior event tree of the target function events.
10. A user event processing device, characterized in that, The user event processing device includes: The first acquisition unit is used to acquire the target sub-event identifier of the triggered target sub-user event when there is a sub-user event triggered for the target application. The determining unit is configured to determine the target functional event corresponding to the target sub-user event based on the target sub-event identifier, wherein the target functional event includes multiple sub-user events; The second acquisition unit is used to acquire the target maintenance event tree corresponding to the target functional event; An update unit is configured to update the node count of the target maintenance event tree based on the target sub-event identifier to obtain the user behavior event tree of the target functional event. The user behavior event tree is used to establish the association between various user events related to the target functional event. The node count includes the sub-event triggering quantity recorded by the target node corresponding to the target sub-event identifier. If the target node does not exist in any of the tree nodes of the target maintenance event tree, the sub-event decomposition relationship of the target functional event is obtained. Based on the sub-event decomposition relationship, the target node is added to the target maintenance event tree, and the sub-event triggering quantity recorded by the target node is updated.
11. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the user event handling method as described in any one of claims 1 to 9 when it invokes the computer program in the memory.
12. A computer-readable storage medium, characterized in that, It stores a computer program, which is loaded by a processor to perform the steps of the user event handling method according to any one of claims 1 to 9.