User event indexing method and apparatus, electronic device, and storage medium

Abstract

Embodiments of the present application disclose a user event indexing method and device, electronic equipment and a storage medium. Embodiments of the present application can obtain event data of a user of an application program and at least one user journey, wherein the user journey comprises a mapping relationship between an event identifier, an event indexing structure, audience conditions and an execution event. Based on the event data of the user and the event identifier of the user journey, a target user journey that matches the event data is filtered out from the at least one user journey. Based on the event indexing structure of the target user journey, the audience conditions of the target user journey are obtained. The event data is judged using the audience conditions of the target user journey to obtain a judgment result. Based on the judgment result, the execution event of the target user journey is executed, which can improve the speed of searching for the execution event and thus improve the execution efficiency of the execution event.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically to a user event indexing method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the rapid development of computer technology and information computing, applications are becoming increasingly widespread. An application is a computer program that performs one or more specific functions. It runs in interactive mode, can interact with the user, and has a visual display interface. For example, applications can include software on various terminals, such as mobile phone applications (APPs), tablet applications, laptop applications, personal computer (PC) applications, and so on. In existing technologies, when a user triggers a corresponding event in an application, the computer device needs to search for the event to be executed based on the user's event data. The inventors of this application have discovered through practical application of existing technologies that there is a problem with the low efficiency of indexing and executing events in these technologies. Summary of the Invention

[0003] This application provides a user event indexing method, apparatus, electronic device, and storage medium, which can improve the speed of searching for execution events, thereby improving the execution efficiency of execution events.

[0004] This application provides a user event indexing method, including:

[0005] Acquire event data of the application's users and at least one user journey, wherein the user journey includes an event identifier, an event index structure, audience conditions, and a mapping relationship between the event and the event.

[0006] Based on the user's event data and the event identifier of the user journey, a target user journey that matches the event data is selected from at least one user journey;

[0007] Based on the event index structure of the target user journey, the audience conditions of the target user journey are obtained;

[0008] The event data is processed using the audience conditions of the target user journey to obtain the discrimination result;

[0009] The execution events of the target user journey are executed based on the discrimination result.

[0010] This application embodiment also provides a user event indexing device, including:

[0011] The first acquisition unit is used to acquire event data of the application's users and at least one user journey, wherein the user journey includes an event identifier, an event index structure, audience conditions, and a mapping relationship between execution events;

[0012] A filtering unit is configured to filter out target user journeys that match the event data in at least one user journey based on the user's event data and the event identifier of the user journey.

[0013] The second acquisition unit is used to acquire the audience conditions of the target user journey based on the event index structure of the target user journey;

[0014] The discrimination unit is used to discriminate the event data using the audience conditions of the target user journey to obtain a discrimination result;

[0015] An execution unit is used to execute the execution events of the target user journey based on the discrimination result.

[0016] This application also provides an electronic device, including a memory storing multiple instructions; a processor loads instructions from the memory to execute steps in any of the user event indexing methods provided in this application.

[0017] This application also provides a computer-readable storage medium storing multiple instructions adapted for loading by a processor to execute steps in any of the user event indexing methods provided in this application.

[0018] This application embodiment can obtain user event data and at least one user journey of an application. The user journey includes an event identifier, an event index structure, audience conditions, and a mapping relationship between execution events. Based on the user's event data and the event identifier of the user journey, a target user journey matching the event data is selected from at least one user journey. Based on the event index structure of the target user journey, the audience conditions of the target user journey are obtained. The event data is then processed using the audience conditions of the target user journey to obtain a discrimination result. Based on the discrimination result, the execution events of the target user journey are executed, which can improve the speed of searching for execution events and thus improve the execution efficiency of the execution events. Attached Figure Description

[0019] 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.

[0020] Figure 1a This is a flowchart illustrating the user event indexing method provided in an embodiment of this application;

[0021] Figure 1b This is a schematic diagram of a scenario for the user event indexing method provided in an embodiment of this application;

[0022] Figure 1c This is another scenario illustration of the user event indexing method provided in the embodiments of this application;

[0023] Figure 1d This is another scenario illustration of the user event indexing method provided in the embodiments of this application;

[0024] Figure 2 This is a schematic diagram of the structure of the user event indexing device provided in the embodiments of this application;

[0025] Figure 3 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0026] 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.

[0027] This application provides a user event indexing method, apparatus, electronic device, and storage medium.

[0028] Specifically, the user event indexing device can be integrated into an electronic device, such as a terminal or server. The terminal can be a mobile phone, tablet, smart Bluetooth device, laptop, or personal computer (PC).

[0029] A server can be an interconnecting server between multiple heterogeneous systems or a backend server. It can also be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, and big data and artificial intelligence platforms, etc.

[0030] In one embodiment, the user event indexing device can be integrated into a computer device such as a terminal or server to implement the user event indexing method proposed in this application. Specifically, the server or terminal can obtain event data of the application's users and at least one user journey, wherein the user journey includes a mapping relationship between event identifiers, event index structures, audience conditions, and execution events; based on the user's event data and the event identifiers of the user journeys, target user journeys that match the event data are filtered out from at least one user journey; based on the event index structure of the target user journey, the audience conditions of the target user journey are obtained; the event data is processed using the audience conditions of the target user journey to obtain a discrimination result; and the execution events of the target user journey are executed based on the discrimination result.

[0031] The following sections provide detailed descriptions of each example. It should be noted that the sequence numbers of the following embodiments are not intended to limit the preferred order of the embodiments.

[0032] In this embodiment, a user event indexing method is provided, such as... Figure 1a The specific process of this user event indexing method can be described as follows:

[0033] 101. Obtain event data of the application's users and at least one user journey, wherein the user journey includes event identifiers, event index structures, audience conditions, and mapping relationships between execution events.

[0034] Applications can include computer programs that perform one or more specific functions. They run in interactive mode, can interact with the user of the application, and have a visual display interface. For example, applications can include application software on various terminals, such as mobile phone applications (APPs), tablet applications, laptop applications, personal computer (PC) applications, and so on.

[0035] For example, applications can include browsers, video playback software, game software, and so on.

[0036] For example, applications can also include mini-programs. A mini-program is an application that can be used without downloading or installing it. To provide users with more diverse business services, developers can create corresponding mini-programs for terminal applications (such as instant messaging applications, shopping applications, email applications, etc.). These mini-programs can be embedded as sub-applications within the terminal application, and by running the sub-application (i.e., the corresponding mini-program) within the application, corresponding business services can be provided to the user.

[0037] User event data can include data generated when a user triggers an event in the application. For example, when a user clicks a functional control in the application, data corresponding to the click event is generated. Similarly, when a user browses content on the application, data corresponding to the browsing event is generated. User event data can include action identifiers, the time the user interacted with the application, and user attribute information. For example, user attribute information can include the user's age and location, etc.

[0038] In this context, the user journey can be a mapping relationship between user event data and execution events defined by developers. For example, ... Figure 1b As shown, this can be a schematic diagram of the user journey. For example, developers can define which user actions towards the application will enter the user journey and what execution events will be triggered.

[0039] In one embodiment, the user journey may include a mapping relationship between event identifiers, an event index structure, audience conditions, and execution events. The event identifier can be used to describe what operation the user performed on the application. The event index structure can be a structure that maps event identifiers to audience conditions. The event index structure can be a fast matching rule object for a specific event, through which the audience conditions corresponding to event data can be quickly indexed. The audience conditions are used to determine whether the event data meets the requirements. If the event data meets the requirements, the user indexing device will trigger an execution event; otherwise, the user indexing device will not trigger an execution event.

[0040] In one embodiment, the developer can configure at least one user journey. For example, the developer can set a corresponding event to be triggered after a user browses content on the application. Or, the developer can set a corresponding event to be triggered after a user in a certain region clicks on a control on the application during a certain time period, and so on.

[0041] Specifically, embodiments of this application may further include:

[0042] Receive user journey creation instructions, create an initial user journey based on the user journey creation instructions, and obtain event rules based on the user journey creation instructions;

[0043] Create an event index structure and construct a structural event mapping relationship between the event index structure and event rules;

[0044] Identify the event rules to obtain the audience conditions corresponding to the event rules;

[0045] Construct a structural condition mapping relationship between audience conditions and event index structure;

[0046] The user journey is obtained by associating the structural condition mapping relationship, the structural event mapping relationship, and the initial user journey.

[0047] In one embodiment, when a developer needs to configure a relevant user journey, the user event indexing device can receive a user journey creation instruction. The user event indexing device can then create an initial user journey based on the user journey creation instruction and retrieve event rules based on the user journey creation instruction.

[0048] The event rules can be configuration information provided by developers for the user journey. For example, a user journey could be selected from users who registered for the application in the most recent day. Specifically, coupon 1 could be pushed to male users in Beijing who browsed the application, while coupon 2 could be pushed to female users in Shanghai who also browsed the application.

[0049] In one embodiment, since event rules can be used for user journey configuration information, event rules can include event identifiers, event attributes, and event attribute values. The event identifier in the user journey can also be used to describe what action the user performed on the application. The event attributes and event attribute values ​​can be used to describe audience conditions. For example, the event identifier can be the application the user registered for, and the event attributes can include time, gender, and region. The time attribute value corresponding to the event attribute time can be 1 day. The event attribute value corresponding to the event attribute time can be male or female. The event attribute value corresponding to the event attribute region can be Beijing or Shanghai. By combining event attributes and event attribute values, audience conditions can be formed.

[0050] In one embodiment, since developers may create multiple journey canvases, each journey canvas may have multiple audience conditions, and each audience condition corresponds to different execution events, data chaos can easily occur if this data is not managed. Therefore, in this implementation, an event index structure can be created, and then the data of the canvas journeys can be chained together through the event index structure.

[0051] In one embodiment, an event index structure can be created, and then a structured event mapping relationship can be constructed between the event index structure and event rules. Specifically, a structured event index relationship can be constructed between the event index structure and event identifiers in the event rules. Specifically, the step "constructing the structured event mapping relationship between the event index structure and event rules" may include:

[0052] The event rules are parsed to obtain the event identifier;

[0053] A structured event mapping relationship is constructed between the event index structure and the event identifier by using a pre-defined data structure.

[0054] The preset data structure can include a forward index structure or an inverted index structure, etc. For example, to improve indexing efficiency, the preset data structure can be a hashMap. For example, event rules can be parsed to obtain event identifiers. Then, a hashMap can be used to construct the structural event index relationship between the event index structure and the event identifiers.

[0055] For example, such as Figure 1d As shown, for browsing events, an event index structure 2 can be created, and then a structural event index relationship can be created between the browsing event and the event index structure 2, so that when a user triggers a browsing event, the browsing event can be associated with the event index structure 2.

[0056] For example, such as Figure 1c As shown, for event 1, an event index structure 1 can be created, and then a structural event index relationship can be created between event 1 and event index structure 1. For event 2, an event index structure 2 can be created, and then a structural event index relationship can be created between event structure 2 and event 2.

[0057] In one embodiment, time rules can be identified to obtain audience conditions corresponding to the event rules. For example, event attributes and event attribute values ​​in the event rules can be identified. Then, audience conditions can be generated based on the event attributes and event attribute values.

[0058] Specifically, the step of "identifying event rules and obtaining the audience conditions corresponding to the event rules" may include:

[0059] The event rules are parsed to obtain a list of event attributes;

[0060] Parse the event attribute list to obtain a list of at least one event attribute value;

[0061] Perform calculations on at least one list of event attribute values ​​to obtain the result of the calculation on the list of event attribute values;

[0062] Audience conditions are generated based on the results of calculations on the list of event attribute values.

[0063] In one embodiment, the event rules can be parsed to obtain a list of event attributes, wherein the list of event attributes includes at least one event attribute. Then, the list of event attributes can be parsed to obtain a list of at least one event attribute value. For example, each event attribute in the list of event attributes can be parsed to obtain a list of event attribute values ​​corresponding to each event attribute, wherein each list of event attribute values ​​includes at least one event attribute value.

[0064] For example, the event attribute list includes event attributes such as time, gender, and region. Specifically, the event attribute value list corresponding to the gender attribute includes two event attribute values: male and female.

[0065] In one embodiment, at least one list of event attribute values ​​can be processed to obtain the result of the operation. Then, audience conditions can be generated based on the result of the operation. For example, a Cadillac product operation can be performed on groups of event attributes from different event attribute value lists, and then the results can be combined to form audience conditions. Alternatively, event attribute values ​​from different event attribute value lists can be combined to obtain audience conditions.

[0066] In one embodiment, after identifying the audience conditions, a structural condition mapping relationship between the audience conditions and the event index structure can be constructed. This can be achieved by generating edge identifiers for the audience conditions. Then, the structural condition mapping relationship between the audience conditions and the event index structure is constructed using these edge identifiers. Specifically, the step of "constructing the structural condition mapping relationship between the audience conditions and the event index structure" may include:

[0067] Generate edge identifiers for audience conditions;

[0068] Add edge identifiers to the event index structure to build a structural condition mapping relationship between the audience condition and the event index structure.

[0069] For example, for audience condition 1, an edge identifier named id1 can be constructed. For audience condition 2, an edge identifier named id2 can be constructed. Then, the edge identifiers can be added to the event index structure to establish a structural condition mapping relationship between the audience conditions and the event index structure.

[0070] In one embodiment, the structural condition mapping relationship, structural event mapping relationship, and initial user journey can be associated to obtain the user journey.

[0071] 102. Based on user event data and event identifiers of user journeys, filter out target user journeys that match the event data in at least one user journey.

[0072] In one embodiment, after acquiring the user's event data, in order to determine whether the user's operation on the application triggered certain execution events, it is possible to determine whether there is a target user journey that matches the event data within the user journey. Therefore, based on the user's event data and the event identifier of the user journey, a target user journey that matches the event data can be filtered out from at least one user journey.

[0073] Specifically, the step "based on user event data and event identifiers of user journeys, filter out target user journeys that match the event data in at least one user journey" may include:

[0074] Identify user event data to obtain the operation identifier of the event data;

[0075] The operation identifier of the event data is matched with the event identifier of at least one user journey to obtain the matching result;

[0076] Based on the matching results, target user journeys that match the event data are selected from at least one user journey.

[0077] In one embodiment, user event data can be identified to obtain operation identifiers from the event data. For example, the user event data can be traversed to read the operation identifiers from the event data. The operation identifier indicates what operation the user performed on the application. For example, the operation identifier can be the name of the user's operation. Alternatively, the operation identifier can be presented in numerical form. For example, when the operation identifier is "11100", it indicates that the user clicked control A. And when the operation identifier is "11101", it indicates that the user clicked control B.

[0078] In one embodiment, the operation identifier of the event data can be matched with the event identifier of at least one user journey to determine whether it is necessary to enter the user journey. The event identifier of the user journey can also be used to describe what operation the user performed on the application. When the operation identifier and the event identifier are the same, it can be indicated that the user journey corresponding to that event identifier is the target user journey.

[0079] In one embodiment, if there is no event identifier that is the same as the operation identifier, the user's event data can be left unprocessed and the user journey can be skipped.

[0080] 103. Based on the event index structure of the target user journey, obtain the audience conditions of the target user journey.

[0081] In one embodiment, audience conditions for the target user journey can be obtained based on the event index structure of the target user journey. Specifically, the step "obtaining audience conditions for the target user journey based on the event index structure of the target user journey" may include:

[0082] Parse the event index structure to obtain the list of event attributes corresponding to the event index structure;

[0083] The operation identifier and event attribute list of the event data are matched to obtain the event attribute value list;

[0084] Based on the list of event attribute values, the audience conditions of the user journey are obtained through a preset structured condition mapping logic.

[0085] In one embodiment, the event index structure can be parsed to obtain a list of event attributes corresponding to the event index structure. Then, the operation identifiers of the event data and the list of event attributes can be matched to obtain a list of event attribute values. For example, the event name is obtained from user event data (denoted as EventRecord), and the event index structure (denoted as FastFilterPattern) is obtained. Then, the list of event attribute values ​​can be obtained based on the list of event attributes in FastFilterPattern and the attributes in EventRecord. Then, the set of edge identifiers can be obtained from the preset structural condition mapping relationship based on the list of event attribute values ​​obtained in the previous step. If the set of edge identifiers is empty, the processing result is... Then, the audience conditions of the user journey can be obtained based on the edge identifiers in the set of edge identifiers obtained in the previous step.

[0086] 104. Use the audience conditions of the target user journey to perform discrimination processing on the event data and obtain the discrimination results.

[0087] In one embodiment, the event data can be processed using the audience conditions of the target user journey to obtain the discrimination result.

[0088] For example, a user journey could select users who registered for the application in the most recent day to enter the journey. Specifically, coupon 1 could be pushed to male users in Beijing who had browsed the application, while coupon 2 could be pushed to female users in Shanghai who had browsed the application. When creating a user journey, event rules can be created as follows: Figure 1d The event index structure shown.

[0089] For example, consider User 1, who registered for the application one year ago. User 1 is male, from Beijing, and has a browsing event. The user event indexing device can find edge ID1 based on User 1's event data. However, since User 1 registered for the application one year ago, User 1 did not trigger an execution event, and the user event processing ends.

[0090] For example, consider user 2, who registered for the application today, is male, is from Beijing, and immediately after registering, a browsing event occurred. The user event indexing device can find edge id1 based on the browsing event, and since user 2 fits the user journey, an execution event will be triggered.

[0091] 105. Execute the target user journey execution events based on the discrimination results.

[0092] For example, a user journey could involve selecting users who registered for the application in the most recent day. Specifically, coupon 1 could be pushed to male users in Beijing who had browsed the application, while coupon 2 could be pushed to female users in Shanghai who had browsed the application.

[0093] If a male user in Beijing registers for the application and then browses it within the last day, he will receive coupon 1. Conversely, if a female user registers for the application and then browses it within the last day, she will receive coupon 2.

[0094] As described above, the embodiments of this application can obtain user event data and at least one user journey of an application. The user journey includes an event identifier, an event index structure, audience conditions, and a mapping relationship between execution events. Based on the user's event data and the event identifier of the user journey, a target user journey matching the event data is selected from at least one user journey. Based on the event index structure of the target user journey, the audience conditions of the target user journey are obtained. The event data is then processed using the audience conditions of the target user journey to obtain a discrimination result. Based on the discrimination result, the execution event of the target user journey is executed. In the embodiments of this application, by constructing user journeys based on the event index structure, it is possible to quickly map user event data to corresponding execution events, thereby improving the speed of searching for execution events and thus improving the execution efficiency of execution events.

[0095] To better implement the above methods, this application also provides a user event indexing device, which can be integrated into an electronic device, such as a terminal or server. The terminal can be a mobile phone, tablet computer, smart Bluetooth device, laptop computer, or personal computer; the server can be a single server or a server cluster composed of multiple servers.

[0096] For example, in this embodiment, the method of this application embodiment will be described in detail by taking the user event indexing device specifically integrated into an electronic device as an example.

[0097] For example, such as Figure 2 As shown, the user event indexing device may include a first acquisition unit 201, a filtering unit 202, a second acquisition unit 203, a discrimination unit 204, and an execution unit 205, as follows:

[0098] The first acquisition unit 201 is used to acquire event data of the user of the application and at least one user journey, wherein the user journey includes an event identifier, an event index structure, audience conditions and a mapping relationship between execution events;

[0099] The filtering unit 202 is used to filter out target user journeys that match the event data in at least one user journey based on the user's event data and the event identifier of the user journey;

[0100] The second acquisition unit 203 is used to acquire the audience conditions of the target user journey based on the event index structure of the target user journey;

[0101] The discrimination unit 204 is used to discriminate the event data using the audience conditions of the target user journey to obtain a discrimination result;

[0102] The execution unit 205 is used to execute the execution events of the target user journey based on the discrimination result.

[0103] In one embodiment, the filtering unit 202 may include:

[0104] The identification subunit is used to identify the user's event data and obtain the operation identifier of the event data;

[0105] The first matching subunit is used to match the operation identifier of the event data with the event identifier of the at least one user journey to obtain a matching result;

[0106] A filtering subunit is used to filter out target user journeys that match the event data in at least one user journey based on the matching results.

[0107] In one embodiment, the second acquisition unit 203 may include:

[0108] The first parsing subunit is used to parse the event index structure to obtain the event attribute list corresponding to the event index structure;

[0109] The second matching subunit is used to match the operation identifier and event attribute list of the event data to obtain a list of event attribute values.

[0110] The acquisition sub-unit is used to obtain the audience conditions of the user journey based on the event attribute value list and through a preset structure condition mapping logic.

[0111] In one embodiment, the user event indexing device may include:

[0112] A receiving unit is configured to receive a user journey creation instruction, create an initial user journey based on the user journey creation instruction, and obtain event rules based on the user journey creation instruction.

[0113] A creation unit is used to create an event index structure and construct a structured event mapping relationship between the event index structure and the event rules;

[0114] The identification unit is used to identify the event rules and obtain the audience conditions corresponding to the event rules.

[0115] The construction unit is used to construct the structural condition mapping relationship between the audience conditions and the event index structure;

[0116] The association unit is used to associate the structural condition mapping relationship, the structural event mapping relationship, and the initial user journey to obtain the user journey.

[0117] In one embodiment, the creation unit may include:

[0118] The second parsing subunit is used to parse the event rules to obtain event identifiers;

[0119] The first construction subunit is used to construct the structural event mapping relationship between the event index structure and the event identifier through a preset data structure.

[0120] In one embodiment, the identification unit may include:

[0121] The third parsing subunit is used to parse the event rules to obtain a list of event attributes;

[0122] The fourth parsing subunit is used to parse the event attribute list to obtain at least one event attribute value list;

[0123] The operation subunit is used to perform operations on the at least one list of event attribute values ​​to obtain the operation result of the list of event attribute values.

[0124] A sub-unit is generated to generate the audience conditions based on the calculation results of the event attribute value list.

[0125] In one embodiment, the building unit may include:

[0126] An identifier generation subunit is used to generate edge identifiers for the audience conditions;

[0127] The second construction subunit is used to add the edge identifier to the event index structure to construct a structural condition mapping relationship between the audience condition and the event index structure.

[0128] 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.

[0129] As can be seen from the above, the user event indexing device of this embodiment obtains the event data of the application user and at least one user journey by the first acquisition unit. The user journey includes the mapping relationship between event identifier, event index structure, audience conditions and execution events. The filtering unit filters out the target user journey that matches the event data in the at least one user journey based on the user's event data and the event identifier of the user journey. The second acquisition unit obtains the audience conditions of the target user journey based on the event index structure of the target user journey. The discrimination unit uses the audience conditions of the target user journey to perform discrimination processing on the event data to obtain the discrimination result. The execution unit executes the execution event of the target user journey based on the discrimination result, which can improve the speed of searching for execution events and thus improve the execution efficiency of execution events.

[0130] Therefore, the embodiments of this application can improve the speed of searching for execution events, thereby improving the execution efficiency of execution events.

[0131] Accordingly, this application also provides an electronic device, which can be a terminal or a server. The terminal can be a smartphone, tablet computer, laptop computer, touch screen, game console, personal computer, personal digital assistant (PDA) and other terminal devices.

[0132] like Figure 3 As shown, Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device 300 includes a processor 310 with one or more processing cores, a memory 320 with one or more computer-readable storage media, and a computer program stored in the memory 320 and executable on the processor. The processor 310 and the memory 320 are electrically connected. Those skilled in the art will understand that the electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0133] The processor 310 is the control center of the electronic device 300. It connects various parts of the electronic device 300 through various interfaces and lines. By running or loading software programs and / or modules stored in the memory 320, and calling data stored in the memory 320, it performs various functions of the electronic device 300 and processes data, thereby monitoring the electronic device 300 as a whole.

[0134] In this embodiment, the processor 310 in the electronic device 300 loads the instructions corresponding to the processes of one or more applications into the memory 320 according to the following steps, and the processor 310 runs the applications stored in the memory 320 to achieve various functions:

[0135] Acquire event data of the application's users and at least one user journey, wherein the user journey includes an event identifier, an event index structure, audience conditions, and a mapping relationship between the event and the execution event;

[0136] Based on the user's event data and the event identifier of the user journey, a target user journey that matches the event data is selected from at least one user journey;

[0137] Based on the event index structure of the target user journey, the audience conditions of the target user journey are obtained;

[0138] The event data is processed using the audience conditions of the target user journey to obtain the discrimination result;

[0139] The execution events of the target user journey are executed based on the discrimination result.

[0140] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0141] Optional, such as Figure 3 As shown, the electronic device 300 also includes: a touch display screen 330, a radio frequency circuit 340, an audio circuit 350, an input unit 360, and a power supply 370. The processor 310 is electrically connected to the touch display screen 330, the radio frequency circuit 340, the audio circuit 350, the input unit 360, and the power supply 370. Those skilled in the art will understand that... Figure 3 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0142] The touch display screen 330 can be used to display a graphical user interface (GUI) and receive operation commands generated by the user interacting with the GUI. The touch display screen 330 may include a display panel and a touch panel. The display panel can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of the electronic device. These graphical user interfaces can be composed of graphics, text, icons, video, and any combination thereof. Optionally, the display panel can be configured using a liquid crystal display (LCD), organic light-emitting diode (OLED), or other similar technologies. The touch panel can be used to collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel), generate corresponding operation commands, and execute the corresponding program according to the operation commands. Optionally, the touch panel may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch location and the signal generated by the touch operation, transmitting the signal to the touch controller. The touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 310. It can also receive and execute commands from the processor 310. The touch panel can cover the display panel. When the touch panel detects a touch operation on or near it, it transmits the information to the processor 310 to determine the type of touch event. Subsequently, the processor 310 provides corresponding visual output on the display panel based on the type of touch event. In this embodiment, the touch panel and the display panel can be integrated into the touch display screen 330 to achieve input and output functions. However, in some embodiments, the touch panel and the touch display screen 330 can be implemented as two independent components to achieve input and output functions. That is, the touch display screen 330 can also be used as part of the input unit 360 to achieve input functions.

[0143] The radio frequency circuit 340 can be used to transmit and receive radio frequency signals to establish wireless communication with network devices or other electronic devices, and to transmit and receive signals with network devices or other electronic devices.

[0144] Audio circuitry 350 can be used to provide an audio interface between a user and an electronic device via a speaker and a microphone. Audio circuitry 350 can convert received audio data into electrical signals and transmit them to the speaker, where the speaker converts them into sound signals for output. Conversely, the microphone converts collected sound signals into electrical signals, which are then received by audio circuitry 350, converted back into audio data, and then processed by processor 310 before being transmitted via radio frequency circuitry 340 to, for example, another electronic device, or output to memory 320 for further processing. Audio circuitry 350 may also include an earphone jack to provide communication between peripheral headphones and electronic devices.

[0145] The input unit 360 can be used to receive input numbers, characters, or user characteristic information (such as fingerprints, iris, facial information, etc.), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.

[0146] Power supply 370 is used to supply power to various components of electronic device 300. Optionally, power supply 370 can be logically connected to processor 310 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Power supply 370 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0147] although Figure 3 As not shown in the diagram, the electronic device 300 may also include a camera, sensor, wireless fidelity module, Bluetooth module, etc., which will not be described in detail here.

[0148] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0149] As can be seen from the above, the electronic device provided in this embodiment can simultaneously track the user's operation progress in different operation events, which is convenient for marketing companies' products.

[0150] 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.

[0151] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of computer programs that can be loaded by a processor to execute steps in any of the user event indexing methods provided in embodiments of this application. For example, the computer program can execute the following steps:

[0152] Acquire event data of the application's users and at least one user journey, wherein the user journey includes an event identifier, an event index structure, audience conditions, and a mapping relationship between the event and the event.

[0153] Based on the user's event data and the event identifier of the user journey, a target user journey that matches the event data is selected from at least one user journey;

[0154] Based on the event index structure of the target user journey, the audience conditions of the target user journey are obtained;

[0155] The event data is processed using the audience conditions of the target user journey to obtain the discrimination result;

[0156] The execution events of the target user journey are executed based on the discrimination result.

[0157] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0158] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0159] Since the computer program stored in the storage medium can execute the steps in any of the user event indexing methods provided in the embodiments of this application, the beneficial effects that any of the user event indexing methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0160] The foregoing has provided a detailed description of a user event indexing method, apparatus, electronic device, and 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 indexing method, characterized in that, include: Acquire event data of the application's users and at least one user journey, wherein the user journey includes an event identifier, an event index structure, audience conditions, and a mapping relationship between the event and the execution event; Based on the user's event data and the event identifier of the user journey, a target user journey that matches the event data is selected from at least one user journey; Based on the event index structure of the target user journey, the audience conditions of the target user journey are obtained; The event data is processed using the audience conditions of the target user journey to obtain the discrimination result; Execute the execution events of the target user's journey based on the discrimination result; Prior to acquiring user event data and at least one user journey for the application, the method further includes: Receive a user journey creation instruction, create an initial user journey based on the user journey creation instruction, and obtain event rules based on the user journey creation instruction; Create an event index structure and construct a structured event mapping relationship between the event index structure and the event rules; The event rules are identified to obtain the audience conditions corresponding to the event rules; Construct a structural condition mapping relationship between the audience conditions and the event index structure; The user journey is obtained by associating the structural condition mapping relationship, the structural event mapping relationship, and the initial user journey.

2. The method according to claim 1, characterized in that, The step of filtering out target user journeys that match the event data in at least one user journey, based on the user's event data and the event identifiers of the user journey, includes: The user's event data is identified to obtain the operation identifier of the event data; The operation identifier of the event data is matched with the event identifier of the at least one user journey to obtain a matching result; Based on the matching results, target user journeys that match the event data are selected from at least one user journey.

3. The method according to claim 1, characterized in that, The method of obtaining the audience conditions of the target user journey based on the event index structure of the target user journey includes: The event index structure is parsed to obtain the event attribute list corresponding to the event index structure; The operation identifier and the event attribute list of the event data are matched to obtain a list of event attribute values. Based on the list of event attribute values, the audience conditions of the user journey are obtained through a preset structured condition mapping logic.

4. The method according to claim 3, characterized in that, The construction of the structural event mapping relationship between the event index structure and the event rules includes: The event rules are parsed to obtain event identifiers; A structured event mapping relationship is constructed between the event index structure and the event identifier through a preset data structure.

5. The method according to claim 3, characterized in that, The process of identifying the event rules to obtain the audience conditions corresponding to the event rules includes: The event rules are parsed to obtain a list of event attributes; The event attribute list is parsed to obtain at least one event attribute value list; The at least one list of event attribute values ​​is processed to obtain the result of the operation on the list of event attribute values; The audience conditions are generated based on the calculation results of the event attribute value list.

6. The method according to claim 3, characterized in that, The construction of the structural condition mapping relationship between the audience conditions and the event index structure includes: Generate edge identifiers for the audience conditions; The edge identifier is added to the event index structure to construct a structural condition mapping relationship between the audience condition and the event index structure.

7. A user event indexing device, characterized in that, include: The first acquisition unit is used to acquire event data of the application's users and at least one user journey, wherein the user journey includes an event identifier, an event index structure, audience conditions, and a mapping relationship between execution events; A filtering unit is configured to filter out target user journeys that match the event data in at least one user journey based on the user's event data and the event identifier of the user journey. The second acquisition unit is used to acquire the audience conditions of the target user journey based on the event index structure of the target user journey; The discrimination unit is used to discriminate the event data using the audience conditions of the target user journey to obtain a discrimination result; An execution unit is configured to execute the execution events of the target user journey based on the discrimination result; The user event indexing device is also used for: Receive a user journey creation instruction, create an initial user journey based on the user journey creation instruction, and obtain event rules based on the user journey creation instruction; Create an event index structure and construct a structured event mapping relationship between the event index structure and the event rules; The event rules are identified to obtain the audience conditions corresponding to the event rules; Construct a structural condition mapping relationship between the audience conditions and the event index structure; The user journey is obtained by associating the structural condition mapping relationship, the structural event mapping relationship, and the initial user journey.

8. An electronic device, characterized in that, It includes a processor and a memory, the memory storing multiple instructions; the processor loads instructions from the memory to perform the steps in the user event indexing method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted for loading by a processor to perform the steps of the user event indexing method according to any one of claims 1 to 6.

Images