Event response processing system, method, computer device and storage medium

Abstract

The application relates to the technical field of artificial intelligence, and discloses an event response processing method and system, computer equipment and a storage medium, which are used for improving the pushing efficiency of marketing messages. The method part comprises the following steps: real-time monitoring of a trigger event triggered by a user through a user terminal; when a target event triggered by the user is monitored, the target event is matched with a trigger condition of a preconfigured marketing process, so that a target marketing process is matched out, wherein each preconfigured marketing process is obtained by configuring a process node component corresponding to a marketing strategy type; and the target event is processed in response to a process corresponding to the target marketing process, so that a marketing touch message corresponding to the target marketing process is sent to the user terminal.

Description

Technical Field

[0001] This application relates to the field of artificial intelligence technology, and in particular to an event response processing system, method, computer device, and storage medium. Background Technology

[0002] In the field of marketing applications, companies typically need to develop marketing strategies in order to achieve higher revenue and faster growth at a lower cost. Traditional solutions mainly rely on offline store marketing, or marketing efforts by marketers through apps / websites, media advertising, telephone and SMS marketing, and in-store sales / retailer marketing to implement these strategies.

[0003] The above solutions mainly rely on mobilizing marketing personnel to achieve different marketing goals, which often yields minimal results and results in low efficiency in pushing marketing messages. Summary of the Invention

[0004] This application provides an event response processing system, method, computer device, and storage medium to solve the technical problem of low efficiency in pushing marketing messages.

[0005] Provide an event response handling method for an event response handling engine, the method comprising:

[0006] Real-time monitoring of trigger events initiated by users through the client;

[0007] When a target event triggered by a user is detected, the target event is matched with the triggering conditions of a pre-configured marketing process to identify the target marketing process. Each pre-configured marketing process is configured based on the process node components corresponding to the marketing strategy type.

[0008] In accordance with the process corresponding to the target marketing process, respond to the target event and send the marketing outreach message corresponding to the target marketing process to the user.

[0009] An event response processing system is provided, comprising a client and an event response processing engine, wherein the event response processing engine is used for:

[0010] Real-time monitoring of trigger events initiated by users through the client;

[0011] When a target event is detected, the target event is matched with the triggering conditions of the pre-configured marketing process to match the target marketing process. Each pre-configured marketing process is configured based on the process node component corresponding to the marketing strategy type.

[0012] In accordance with the process corresponding to the target marketing process, respond to the target event and send the marketing outreach message corresponding to the target marketing process to the user.

[0013] A computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of any of the aforementioned event response processing methods, or implements the functions of an event response processing engine in the aforementioned event response processing system.

[0014] A computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements any of the aforementioned event response processing methods, or implements the function of an event response processing engine in the aforementioned event response processing system.

[0015] In the above-described solution, marketing processes are pre-configured through process node components, and user-triggered events are monitored in real time. When a target event that meets the triggering conditions of any marketing process is detected, the event response processing engine executes the corresponding marketing process. Compared with traditional solutions, this embodiment can match and execute corresponding marketing processes by matching user-triggered events. This event-driven approach achieves refined marketing outreach message delivery, and the automated matching and execution of marketing processes greatly improves the efficiency of marketing message delivery. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the 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.

[0017] Figure 1 This is a schematic diagram of an event response processing system according to one embodiment of this application;

[0018] Figure 2 This is another system schematic diagram of the event response processing system in one embodiment of this application;

[0019] Figure 3 This is another system schematic diagram of the event response processing system in one embodiment of this application;

[0020] Figure 4 This is another system schematic diagram of the event response processing system in one embodiment of this application;

[0021] Figure 5This is another system schematic diagram of the event response processing system in one embodiment of this application;

[0022] Figure 6 This is another system schematic diagram of the event response processing system in one embodiment of this application;

[0023] Figure 7 This is another system schematic diagram of the event response processing system in one embodiment of this application;

[0024] Figure 8 This is a flowchart illustrating an event response processing method in one embodiment of this application;

[0025] Figure 9 This is a schematic diagram of the structure of an event response processing device in one embodiment of this application;

[0026] Figure 10 This is a schematic diagram of the structure of a computer device according to one embodiment of this application. Detailed Implementation

[0027] 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, 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.

[0028] This application provides an event response processing scheme, mainly used to achieve refined marketing automation processing and improve the efficiency of marketing message push, including targeted push and multi-channel touchpoint push. It includes several aspects such as event response processing methods, event response processing systems, devices, computer equipment, and storage media. The following describes the above aspects through various embodiments.

[0029] First, an event response processing system provided in an embodiment of this application will be described. For example... Figure 1 As shown, Figure 1 This is a schematic diagram of an event response processing system provided in an embodiment of this application. The system includes a user terminal and an event response processing engine. The user terminal, also known as a client, refers to a program that provides local services to the user, including web services or application services, and can be installed on various personal computers, laptops, smartphones, tablets, and portable wearable devices, including but not limited to. The event response processing engine can be implemented using a standalone server or a server cluster consisting of multiple servers. The event response processing engine is used for:

[0030] Real-time monitoring of trigger events initiated by users through the client;

[0031] When a target event is detected, the target event is matched with the triggering conditions of the pre-configured marketing process to match the target marketing process. Each pre-configured marketing process is configured based on the process node component corresponding to the marketing strategy type.

[0032] In accordance with the process corresponding to the target marketing process, respond to the target event and send the marketing outreach message corresponding to the target marketing process to the user.

[0033] In this embodiment, the marketing process corresponding to each marketing strategy type is configured in advance by building process node components. The marketing process is used to deliver marketing messages according to the process logic and component functions of the configured process node components. The process start node component of each marketing process is configured with the triggering condition corresponding to the marketing strategy type. The triggering condition is the condition for triggering the execution of the marketing process. The triggering conditions for different marketing strategy types can be the same or different, which is not limited here. The marketing strategy type is determined according to the customized marketing strategy. Individual marketing strategies will be illustrated with practical examples later, which is not limited here either.

[0034] These pre-configured marketing processes are executed based on trigger events through an event response processing engine. When the event response processing engine is running, it will listen for trigger events triggered by users through the user's terminal in real time.

[0035] It's important to note that triggering events can vary depending on the application scenario. For example, a triggering event can be generated by a user's actions on an H5 (HTML5) page, such as visiting an H5 page or clicking an element on that page, like a button. There are no specific limitations. Similarly, a triggering event can be generated by a user's actions on an application page, such as visiting an application page or clicking a button on that page. Again, there are no specific limitations. It's worth noting that this application can be a mini-program or a native application, etc. Furthermore, it should be noted that listening to these triggering events can be implemented using event tracking, which is also not limited to this method.

[0036] During real-time monitoring of user-triggered events on the user's device, if the event response processing engine detects a target event triggered by the user, it matches this target event with the triggering conditions of a pre-configured marketing process. The engine selects the marketing process that meets the triggering conditions from the pre-configured processes as the target marketing process; that is, the target marketing process is the marketing process corresponding to the identified target trigger event. After determining the target marketing process, the event response processing engine parses the corresponding process node components to obtain the specific processing flow of the target marketing process. Then, according to the flow of the target marketing process, it responds to the target event and sends the corresponding marketing outreach message to the user's device, achieving the purpose of pushing marketing outreach messages.

[0037] The delivery method for marketing outreach messages is configured through process node components when configuring the marketing process. Generally, the delivery method is related to the marketing strategy type. For example, delivery methods include, but are not limited to, sending official account template messages, official account customer service messages, official account mass messages, mini-program subscription messages, SMS messages, enterprise WeChat messages, and APP push messages (APP Push outreach), etc. There are no specific limitations. More details will be described in detail in the subsequent configuration examples of the marketing process.

[0038] When responding to a target event, the process parser can be used to parse the corresponding process node components of the target marketing process according to the implementation logic of the target marketing process, so as to execute the corresponding processing logic of each process node component until the parsed component is the end component, then the process is completed, and the marketing outreach message corresponding to the target marketing process is sent to the user terminal to realize the push of marketing outreach message.

[0039] As can be seen, this embodiment provides an event response processing system that pre-configures marketing processes through process node components and listens for user-triggered events in real time. When a target event that meets the triggering conditions of any marketing process is detected, the event response processing engine executes the corresponding marketing process. Compared with traditional solutions, this embodiment can match and execute corresponding marketing processes by matching user-triggered events. It achieves refined marketing outreach message push through an event-driven approach, and automatically matches and executes pre-configured componentized processes, greatly improving the efficiency of marketing message push.

[0040] It should be noted that, in the above embodiments, it is mentioned that the marketing process will be built in advance through process node components. To facilitate the building of the marketing process and improve its efficiency, one embodiment provides a configuration scheme for the marketing process, such as... Figure 2 As shown, the event response processing system also includes a process configuration terminal, which is used for:

[0041] Respond to the process node drag operation and select all the process node components required for the marketing strategy type on the canvas;

[0042] The response process node combination operation combines the required process node components to obtain the marketing process corresponding to the marketing strategy type.

[0043] In this embodiment, the process configuration client supports building process node components using a canvas. The client can render the required process node components on the canvas and then configure the marketing process via drag-and-drop. This drag-and-drop method is flexible and can meet most marketing scenarios. As an example, the canvas supports components such as trigger action components, attribute filtering components, event judgment components, A / B testing components, outreach components, grouping components, and tag components. Other process node components can also be selected, but they are not listed here, nor are they limited. Using this example, the implementation functions or logic of each process node component will be introduced.

[0044] The triggering action component is the trigger condition for entering the marketing process. For example, the trigger condition can be an event, a target customer group that matches the required customer group type, or a combination of event and customer group type.

[0045] The attribute filtering component is used to filter target customer groups. For example, only users who meet a certain condition can execute process node A, while users who meet another condition can execute process node B.

[0046] The event judgment component is used to determine whether the user meets a certain event condition. If the condition is met, the yes condition node is executed; otherwise, the no condition node is executed.

[0047] A / B testing components are primarily used for A / B testing. A / B testing refers to creating two (A / B) or more (A / B / n) versions of a web or app interface, and simultaneously allowing different visitor groups (target audiences) with similar or identical compositions to randomly access these different versions. User experience and business data are collected from each visitor group, and finally, the best version is analyzed and evaluated. For example, A / B testing components can be used to test the marketing effectiveness of more than two outreach actions.

[0048] The reach component is mainly used to reach users, including but not limited to SMS reach, WeChat official account template message reach, WeChat official account customer service message reach, WeChat group message reach, APP push reach, and mini program message reach.

[0049] The grouping component is mainly used to add users who enter the marketing process to a group or remove users from a group;

[0050] The tagging component is mainly used to add or remove tags for a specific customer group type from users entering the marketing process.

[0051] In this embodiment, by dragging and dropping any combination and arrangement of the various process node components, the logic and execution actions corresponding to the marketing process to be configured can be strung together through the process node component elements on the canvas, thereby achieving the purpose of customizing the marketing process.

[0052] For example, let's take the "Form-Based Audience Retrieval" marketing process as an example. When configuring this marketing process, firstly, drag the first process component on the canvas as the starting node of the marketing process. The trigger action component of the first process node will be configured with a trigger event for accessing a certain page and set user conditions that meet a certain attribute. Then, add two event judgment components under the trigger component. Event component 1 is configured with an event for submitting the form, and event component 2 is configured with an event for not submitting the form. Then, add group components under each event judgment component. For example, add group component 1 under event component 1 to set the users who submit the form by joining group component 1, and add group component 2 under event component 2 to set the users who do not submit the form by joining group component 2. Under group component 2, add a reach component to configure a WeChat official account template message to remind users who have not submitted the form to fill it out. This completes the "Form-Based Audience Retrieval" process.

[0053] It should be noted that the components for configuring customized marketing processes and the "form-based audience retrieval" marketing process mentioned above are merely illustrative examples. Depending on the actual marketing application scenario, the draggable process node components may include other components or fewer than those mentioned above to customize the required marketing process. For example, in the "form-based audience retrieval" marketing process, other reach methods can be set through the reach component, or the marketing effect can be tested by adding an A / B component in this marketing process. It may also be a marketing process corresponding to other marketing strategy types. Specific embodiments in this application are not limited and will not be illustrated one by one.

[0054] like Figure 3As shown, for ease of understanding, the above component example is used to illustrate the response processing process of the event response processing engine in executing the target marketing process. When the event response processing engine runs, it listens for incoming trigger events. For example, when a user clicks a button on an H5 page, the engine assembles an expression based on the format of the consumed trigger event. This expression is then matched against the trigger conditions configured for all process start node trigger components in the system. If a match is found, the process parser enters the process parser, which parses the first process node component following the matched target marketing process trigger component to execute different logical processing based on the node component type. For example, if it's a conditional component, it will enter the conditional executor's execution flow configuration. The result of the conditional execution is also implemented using rule engine technology based on expression execution. For example, if a user visits an H5 page or clicks a button, and this configured condition matches the user's past actions or future actions, then the condition is met. If the condition is met, the next node component is executed and sent to the flow parser for parsing. If the parsed component is an action node, it will enter the action executor to execute the action configured in the flow, such as sending a public account template message, a public account customer service message, a public account group message, a mini-program subscription message, an SMS message, a WeChat Work message, or an APP message. Actions such as pushing messages, adding groups, and adding tags will be executed. After the action is completed, the next node component will be found and sent to the process parser for parsing. If the parsed component is a delayed node, it will enter the delayed executor to perform a delayed waiting operation. The delay supports absolute and relative time. After the delay is completed, the next node will be found and sent to the process parser for parsing. If the parsed component is an end node, it will enter the end executor. The end executor will perform the process end action and change the current process instance state to the end state. At this point, the target marketing process is completed.

[0055] This embodiment provides a specific implementation method for configuring marketing processes. It supports the construction of various process node components required for marketing processes on the canvas, and the marketing processes and trigger conditions are configured by drag and drop. The drag-and-drop method is flexible and can meet most marketing scenarios. Under the premise of ensuring automated marketing, there are customizable marketing processes that can be saved in the form of components, which expands the marketing application scenarios and the feasibility of automated execution, and ensures the efficient execution of marketing processes.

[0056] It should be noted that, in the foregoing embodiments, it was mentioned that the target event would be matched with the triggering conditions of a pre-configured marketing process to identify the target marketing process. To improve the efficiency and accuracy of marketing process matching, the event response processing system provided in this application also introduces a rule engine approach to achieve efficient execution and accuracy of process matching, such as... Figure 4 As shown, the event response processing system also includes a target rule engine, wherein:

[0057] The event response processing engine is used to send the event data corresponding to the target event to the target rule engine;

[0058] The target rule engine is used to pass event data into the trigger condition rule expression of each pre-configured marketing process for execution, and obtain the execution result;

[0059] The event response processing engine receives the execution results of each trigger condition rule expression from the target rule engine and determines the target marketing process based on the execution results of each trigger condition rule expression.

[0060] In this embodiment, the target rule engine will concatenate the trigger conditions configured in the trigger components of each marketing process to generate corresponding trigger condition rule expressions. The rule expression is a logical formula for string manipulation, which is to use some predefined characters and combinations of these specific characters to form a "rule string". The "rule string" is used to express a filtering logic for the string. The execution result of the expression is only yes or no. If the result is yes, it means that it is matched; if the result is no, it means that it is not matched.

[0061] In this embodiment, when constructing the corresponding trigger condition rule expression, for example, a user may perform many actions on an H5 page, such as accessing a page or clicking a button. These events are reported to a message queue through the event tracking SDK. Each message in the message queue is an event, and each event has a corresponding event format, such as the event type (access event or click event), and the event also has an object body containing a title and related metadata. For example, in this embodiment, the corresponding trigger condition rule expression is constructed based on the event format.

[0062] After detecting a target event, the event response processing engine parses the corresponding event data and passes it to the target rule engine. This event data includes event information such as event type and customer group type. The target rule engine then feeds the event data into the trigger condition rule expressions for each pre-configured marketing process, executes them, and passes the execution results to the event response processing engine. Based on the execution results of each trigger condition rule expression, the event response processing engine determines the target marketing process. For example, if the result of the trigger condition rule expression for marketing process 1 is yes, then marketing process 1 is selected as the target marketing process. In this embodiment, feeding the event data into each rule expression for parallel matching improves event matching efficiency, thereby enhancing the overall efficiency of automated execution.

[0063] For example, if the trigger condition configured in the process component node is that a user visits a certain work and the gender of the visiting user is female, then the trigger condition rule expression is (event=='VIEW'&&contentId=='95fef5a9-6dd8-4bee-822e-2ae54fbe0444'&&sex=0), where event, contentId, and sex are placeholders for the input parameters, representing the event, work, and gender, respectively. If the input parameters are passed into the trigger condition expression and match the value of the equal sign on the right, a result can be calculated.

[0064] It should be noted that, as another example, in addition to the matching method described above, the target rule engine can also sequentially feed event data into each trigger condition rule expression until a result of "yes" is obtained, at which point the expression matching process ends. The specific method is not limited. In this example, compared to the aforementioned embodiments, the processing load can be reduced in most cases.

[0065] For example, the target rule engine in this application embodiment can be the Aviator rule engine, or a rule engine such as JRuby, and there is no specific limitation. It is worth noting that the Aviator rule engine is more lightweight, making it easier to deploy and reducing system space usage.

[0066] As can be seen, the embodiments of this application provide a marketing process matching and execution based on event-driven and expression engines. It can be understood that the target rule engine can be embedded in the event response processing engine as an intermediate component, realizing the separation of business decisions from the event response processing engine code. Expression rules are written using the predefined semantic modules of the selected rule engine. It can accept event data input, interpret expression rules, and make corresponding decisions based on expression rules. That is, the target rule engine only handles the invocation and execution of rules. In this way, when the marketing process changes, the expression rules in the rule engine can be changed directly, reducing the complexity of components that implement complex business logic, reducing the maintenance cost and scalability cost of automated marketing process execution, and facilitating subsequent expansion, optimization, or updates to the automated execution process of the marketing process.

[0067] It should be noted that the aforementioned embodiments clearly defined the matching method used to match the marketing process with the target event triggered by the user. In this embodiment, the specific triggering method is specified as follows:

[0068] In one embodiment, the event response processing engine is used to parse out the event type corresponding to the target event; match the event type with the triggering conditions of a pre-configured marketing process, so as to use the marketing process that matches the event type as the target marketing process; or; parse out the customer group type corresponding to the target event; match the customer group type with the triggering conditions of a pre-configured marketing process, so as to use the marketing process that matches the customer group type as the target marketing process.

[0069] In this embodiment, as mentioned in the previous embodiments, when configuring the first process node of the marketing process using the triggering component, the configured triggering condition can be an event or a customer group type. Therefore, in this embodiment, the corresponding marketing process can be matched as the target marketing process by interpreting the event type corresponding to the target event or the customer group type of the user who triggered the target event. Here, the event type refers to the triggering event type, such as opening an H5 page, clicking certain page elements on an H5 page, or clicking certain page elements on an application page; the specific type is not limited. The customer group type is pre-determined based on user data and profiling technology; the customer group type of the triggering user can be determined through the user data of the triggering user.

[0070] This embodiment provides two specific triggering conditions for driving the execution of the marketing process: events or customer group types. In some embodiments, both event types and customer group types may be considered. When an event type triggers, a corresponding marketing process is executed for each event type, matching the marketing process to the event itself. This allows for marketing targeting different event types, achieving broad marketing goals. When a customer group type triggers, a corresponding marketing process is executed for each customer group type, matching the marketing process to the customer group's attributes. This allows for targeted marketing to different customer groups, achieving personalized marketing. When both event type and customer group type are considered, a corresponding marketing process can be executed for the target group that triggered a specific event. For example, continuing with the "form-based audience retrieval" marketing process, the triggering condition is configured as a page visit, with user conditions meeting certain attributes set as the final triggering condition. It can be seen that by comprehensively setting triggering conditions, a more refined marketing reach can be achieved, further improving the effectiveness of refined marketing.

[0071] In conjunction with the above examples, it is also worth emphasizing that when selecting a customer group type at the trigger node, you can also select a trigger event, choosing one of the two. If you only select a trigger event, then you don't need to use a customer group type. Using customer group type as a trigger condition is an optional implementation.

[0072] In conjunction with the above embodiments, in order to ensure the implementation of the trigger condition matching process to achieve the purpose of refined marketing, such as Figure 5 As shown, the event response and processing system also includes a big data platform, in which:

[0073] The event response processing engine is also used to process target events according to the corresponding process of the target marketing process, collect marketing response data after processing the target event, and send the marketing response data to the big data platform.

[0074] The big data platform is used to integrate the received marketing response data and generate user profile tag data based on the integrated data;

[0075] The event response processing engine is also used to receive user profile tag data from the big data platform and to establish customer group types based on the received user profile tag data.

[0076] In this embodiment, after the marketing trigger message reaches the user's end, in order to analyze the marketing effect and realize the construction of customer groups, the event response processing engine will collect the marketing response data after the target event response processing, and push it to the big data platform for big data analysis to obtain marketing effect and user tag data.

[0077] As an example, in the marketing outreach message configured in the target marketing process, a link containing content can be pushed. This link's page is configured with a data tracking SDK (Software Development Kit). After receiving the marketing outreach message, the user only needs to open the link on their device to trigger a data reporting activity. Any user actions on the page are collected, and this data ultimately enters a big data platform, such as a Hadoop cluster, for data cleaning, transformation, processing, storage, and analysis. The specific big data platform used is not limited. After the marketing response data is stored on the big data platform, it undergoes preprocessing and analysis based on various statistical data points related to marketing effectiveness, such as the number of participants, participants, reach, clicks, shares, form submissions, and participant information. This data is then further processed to generate user profile tag data. The event response processing engine can then collect this user profile tag data from the big data platform to establish customer segmentation and feed it back into the marketing process.

[0078] It's important to note that to achieve truly personalized marketing for different user groups, it's essential to first establish customer segmentation. User profile tags include demographic tags, customer behavior preference tags, customer interaction information tags, and transaction information tags. Customer segmentation is achieved through multi-dimensional criteria. Demographic tags include attributes such as gender, age, and region. Customer interaction information tags include attributes such as customer social relationships, communication records, and attitudes and opinions. For example, this can be calculated by combining user basic attributes, interests, and behavioral data. For instance, a male user with a movie-watching preference is categorized as a "male movie enthusiast" customer segment. Ultimately, target customer data is stored in storage systems like Elasticsearch for use in marketing campaigns. This combined calculation can be achieved by concatenating conditions and expressions into an SQL query that Elasticsearch can recognize, which is then used to retrieve the data from Elasticsearch.

[0079] Based on the stored target customer data, the customer groups to be filtered are configured in the trigger action component of the marketing process. The customer group filtering conditions can be user basic information, behavior records, tags, etc. Any or no combination of these conditions can be used as the filtering conditions. When the marketing process starts, it will filter out the corresponding users from Elasticsearch based on the configured filtering conditions and execute the corresponding marketing process.

[0080] In this embodiment, after achieving the goal of refined marketing, the marketing effect can be further evaluated based on the feedback response data after marketing, which facilitates the adjustment of marketing strategy types and is used to establish customer group types to ensure the implementation of refined marketing, thus having high practicality.

[0081] In one embodiment, such as Figure 6 As shown, the event response processing system also includes a message queue system, wherein:

[0082] The message queue system is used to receive event messages for each triggering event uploaded by the user from the client.

[0083] An event response processing engine is used to establish polling channels with the target message queue of the message queuing system;

[0084] The event messages in the target message queue are polled through a polling channel to monitor user-triggered events in real time.

[0085] This embodiment provides a specific implementation method for the event response processing engine to listen to user-triggered events. For example, when a user triggers an event through the user terminal, such as clicking a button event on an H5 page, this click event is reported to the target message queue of the message queue system. Since the event response processing engine has established a subscription-consumption relationship with the target message queue, the events uploaded to the target message queue will be consumed by the event response processing engine, thereby listening to the user-triggered event. Specifically, the event response processing engine polls the event messages in the target message queue through a polling channel to listen to user-triggered events in real time. For example, the message queue system can be a Kafka message queue system or a queue system such as KubeMQ, and the specific system is not limited.

[0086] In this embodiment, using a message queue to handle the listening of triggered events helps to control and optimize the speed of the event response processing engine through which the data stream passes, resolving the inconsistency between the processing speed of producing and consuming messages. Moreover, in the event of a surge in triggered events, using a message queue enables critical components to withstand the sudden surge in pressure without crashing due to sudden overload requests.

[0087] In one embodiment, such as Figure 7 As shown, in order to facilitate real-time recording of the execution status of the configured marketing processes, the event response processing system also includes a target database;

[0088] The event response processing engine is also used to extract operation record data for each step executed by the event response processing engine and save the operation record data in the target database. When an instruction to query the historical execution steps of the event response processing engine is received, the response engine reads the operation record data corresponding to the historical execution steps from the target database and renders and displays the read operation record data.

[0089] In this embodiment, the execution of each step of the event response processing engine will transfer the execution operation record as operation record data to the target database. For example, the execution path of each step will also be recorded. The execution path refers to the execution path of the process from node A to node B. When viewing the process on the process canvas, the number of executions can be seen on the line connecting node A to node B. When viewing the marketing process, the execution data of the current process can be displayed on the canvas, which is convenient for monitoring and maintaining the execution status of the marketing process.

[0090] In summary, this application provides an event response processing system. Based on an event response processing engine, it combines event-driven, big data analysis and processing, and customer tagging and profiling technologies to achieve refined marketing objectives. The event response processing engine acts as an execution hub, receiving external user-triggered events, analyzing and executing different marketing processes based on different trigger events and / or customer groups, and pushing different marketing outreach messages to achieve personalized marketing goals. The executed data is then collected and aggregated on a big data platform, and finally, the marketing effectiveness of the entire marketing process is evaluated based on the big data platform. Further details and technical effects can be found in the foregoing embodiments, and will not be repeated here.

[0091] The above embodiments describe the event response processing system provided in this application. The following describes the event response processing method based on this system.

[0092] In one embodiment, such as Figure 8 As shown, an event response handling method is provided. Taking the application of this method in the event response handling engine of an event response handling system as an example, the method includes the following steps:

[0093] S10: Real-time monitoring of trigger events initiated by users through the client;

[0094] S20: When a target event triggered by a user is detected, the target event is matched with the triggering conditions of a pre-configured marketing process to match the target marketing process. Each pre-configured marketing process is configured based on the process node component corresponding to the marketing strategy type.

[0095] S30: Respond to the target event according to the process corresponding to the target marketing process, so as to send the marketing outreach message corresponding to the target marketing process to the user.

[0096] As can be seen, this embodiment provides an event response processing method. Marketing processes are pre-configured through process node components, and user-triggered events are monitored in real time. When a target event that meets the triggering conditions of any marketing process is detected, the event response processing engine executes the corresponding marketing process. Compared with traditional solutions, this embodiment can match and execute corresponding marketing processes by matching user-triggered events. This event-driven approach achieves refined marketing outreach message delivery, and the automated matching and execution of marketing processes significantly improves the efficiency of marketing message delivery.

[0097] In one embodiment, the pre-configured marketing process is obtained by: responding to the process node drag operation, selecting all process node components required for the marketing strategy type on the canvas; responding to the process node combination operation, combining the required process node components to obtain the marketing process corresponding to the marketing strategy type. The canvas method supports the construction of process node components. The process configuration end can render the required process node components on the canvas, and then configure the marketing process by dragging and dropping. The drag-and-drop method is flexible and can meet most marketing scenarios. As an example, the canvas supports components such as trigger action components, attribute filtering components, event judgment components, A / B testing components, reach components, grouping components, and tag components, and may also include other process node components for selection.

[0098] In one embodiment, step S20, which involves matching the target event with the triggering conditions of a pre-configured marketing process to identify the target marketing process, includes the following:

[0099] S201A: Parse out the event type corresponding to the target event;

[0100] S202A: Match event types with the trigger conditions of pre-configured marketing processes to target marketing processes that match the event type.

[0101] or;

[0102] S203A: Parse out the customer group type corresponding to the target event;

[0103] S204A: Match customer segment types with pre-configured marketing process trigger conditions to target marketing processes that match the customer segment type.

[0104] In this embodiment, when an event type triggers, a corresponding marketing process is executed for each event type. Matching the marketing process to the event itself allows for targeted marketing across different event types, achieving broad marketing goals. When a customer group type triggers, a corresponding marketing process is executed for each customer group type. Matching the marketing process to the customer group attributes allows for targeted marketing to different customer groups, achieving a personalized experience. When both event type and customer group type are considered, a corresponding marketing process can be executed for the target group that triggered a specific event. For example, continuing with the "form-based audience retrieval" marketing process, the trigger condition is configured as a page visit event, and user conditions meeting a certain attribute are set as the final trigger condition. It can be seen that by comprehensively setting trigger conditions, a more refined marketing reach can be achieved, further improving the effectiveness of refined marketing.

[0105] In one embodiment, after responding to the target event according to the process corresponding to the target marketing process, the method further includes the following:

[0106] S40: Collect marketing response data after responding to and processing the target event;

[0107] S50: Send marketing response data to the big data platform so that the big data platform can integrate the received marketing response data and generate user profile tag data based on the integrated data;

[0108] S60: Receives user profile tag data from the big data platform and establishes customer group types based on the received user profile tag data.

[0109] In this embodiment, after achieving the goal of refined marketing, the marketing effect can be further evaluated based on the feedback response data after marketing, which is convenient for adjusting the type of marketing strategy and for establishing customer group types to ensure the implementation of refined marketing. It also makes full use of the feedback data in the marketing process and has high practicality.

[0110] In one embodiment, step S20, which involves matching the target event with the triggering conditions of a pre-configured marketing process to identify the target marketing process, includes the following:

[0111] S201B: Send the event data corresponding to the target event to the target rule engine so that the target rule engine can pass the event data into the trigger condition rule expression of each pre-configured marketing process for execution;

[0112] S202B: Receives the execution result of each triggering condition rule expression fed back by the target rule engine;

[0113] S203B: Determine the target marketing process based on the execution result of each trigger condition rule expression.

[0114] In this embodiment, the present application provides a marketing process matching and execution based on event-driven and expression engine. The target rule engine can be embedded in the event response processing engine as an intermediate component, realizing the separation of business decisions from the event response processing engine code. Expression rules are written using the predefined semantic modules of the selected rule engine, which can accept event data input, interpret expression rules, and make corresponding decisions based on expression rules. That is, the target rule engine only handles the invocation and execution of rules. In this way, when the marketing process changes, the expression rules in the rule engine can be changed directly, reducing the complexity of components that implement complex business logic, reducing the maintenance cost and scalability cost of automated marketing process execution, and facilitating subsequent expansion, optimization, or updates to the automated execution process of the marketing process.

[0115] In one embodiment, step S10, namely, real-time monitoring of user-triggered events, includes the following:

[0116] S11: Establish a polling channel with the target message queue of the message queue system. The target message queue is used to receive the event message corresponding to each triggered event uploaded by the user.

[0117] S12: Poll the event messages in the target message queue through the polling channel to listen for user-triggered events in real time.

[0118] In this embodiment, using a message queue to handle the listening of triggered events helps to control and optimize the speed of the event response processing engine through which the data stream passes, resolving the inconsistency between the processing speed of producing and consuming messages. Moreover, in the event of a surge in triggered events, using a message queue enables critical components to withstand the sudden surge in pressure without crashing due to sudden overload requests.

[0119] In one embodiment, the method further includes the following:

[0120] S101: Extract the operation record data of each step executed by the event response processing engine and save the operation record data in the target database;

[0121] S102: When receiving an instruction from the query event response processing engine to retrieve the historical execution steps, the response query reads the operation record data corresponding to the historical execution steps from the target database and renders and displays the read operation record data.

[0122] In this embodiment, the execution of each step of the event response processing engine will transfer the execution operation record as operation record data to the target database. For example, the execution path of each step will also be recorded. The execution path refers to the execution path of the process from node A to node B. When viewing the process on the process canvas, the number of executions can be seen on the line connecting node A to node B. When viewing the marketing process, the execution data of the current process can be displayed on the canvas, which is convenient for monitoring and maintaining the execution status of the marketing process.

[0123] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0124] It should also be noted that for more details about the event response processing method provided in the embodiments of this application and the resulting technical effects, please refer to the description of the event response processing system in the foregoing embodiments. To avoid redundancy, the description will not be repeated here.

[0125] In one embodiment, an event response processing apparatus is provided, which corresponds one-to-one with the event response processing engine in the event response processing method described above. For example... Figure 9 As shown, the event response processing device 10 includes a listening module 101, a matching module 102, and a response module 103. Detailed descriptions of each functional module are as follows:

[0126] The listening module 101 is used to listen in real time to trigger events initiated by the user through the user terminal;

[0127] The matching module 102 is used to match the target event with the triggering conditions of the pre-configured marketing process when the target event triggered by the user is detected, so as to match the target marketing process. Each pre-configured marketing process is configured according to the process node component corresponding to the marketing strategy type.

[0128] The response module 103 is used to respond to the target event according to the process corresponding to the target marketing process, so as to send the marketing outreach message corresponding to the target marketing process to the user terminal.

[0129] As can be seen, this embodiment provides an event response processing device that pre-configures marketing processes through process node components and monitors user-triggered events in real time. When a target event that meets the triggering conditions of any marketing process is detected, the event response processing engine executes the corresponding marketing process. Compared with traditional solutions, this embodiment can match and execute corresponding marketing processes by matching user-triggered events. It achieves refined marketing outreach message delivery through an event-driven approach, and the automated matching and execution of marketing processes greatly improves the efficiency of marketing message delivery.

[0130] For specific limitations regarding the event response processing device, please refer to the limitations concerning the event response processing engine in the event response processing system described above. The resulting technical effects can also be found in the aforementioned embodiments, and will not be repeated here. Each module in the aforementioned event response processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0131] In one embodiment, a computer device is provided, which may be an event response processing engine, and its internal structure diagram may be as follows: Figure 10As shown. The computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface is used for communication with external devices such as user terminals, target databases, or process configuration terminals via a network connection. When the computer program is executed by the processor, it implements the various steps of an event response processing method, for example... Figure 8 S10-S30 shown will not be described again here to avoid repetition.

[0132] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When executed by a processor, the computer program implements the various steps of the event response processing method described above, for example... Figure 8 S10-S30, as shown, will not be described again here to avoid repetition. Alternatively, when the computer program is executed by the processor, it implements the functions of each module / unit in this embodiment of the event response processing apparatus, for example... Figure 9 The functions of each module shown are not described again here to avoid repetition. The computer-readable storage medium may be non-volatile or volatile.

[0133] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0134] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0135] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. An event response processing system, characterized in that, The system includes a user terminal, an event response processing engine, a big data platform, a target rule engine, and a message queue system, wherein the event response processing engine is used for: Real-time monitoring of trigger events triggered by the user through the user terminal includes: establishing a polling channel with a target message queue of the message queue system, wherein the target message queue is used to receive event messages of each trigger event uploaded by the user terminal, and polling the event messages in the target message queue through the polling channel to monitor the trigger events in real time; When a target event is detected, the event data corresponding to the target event is sent to the target rule engine. The target rule engine is used to pass the event data into the trigger condition rule expression of each pre-configured marketing process for execution and return the execution result. The event response processing engine receives the execution result and matches the target marketing process according to the execution result. Each pre-configured marketing process is configured based on the process node components corresponding to the marketing strategy type. The process node components include trigger action components, attribute filtering components, event judgment components, and reach components. According to the process corresponding to the target marketing process, the target event is responded to and processed so as to send the marketing outreach message corresponding to the target marketing process to the user terminal; The system collects marketing response data after processing the target event and sends the marketing response data to the big data platform. The big data platform integrates the marketing response data and generates user profile tag data based on the integrated data. The user profile tag data is then fed back to the event response processing engine. The event response processing engine receives external user-triggered events, analyzes and judges different trigger events and / or customer groups to execute different marketing processes, and pushes different marketing outreach messages.

2. The event response processing system as described in claim 1, characterized in that, The event response processing engine is also used for: Parse the event type corresponding to the target event; The event type is matched with the triggering conditions of a pre-configured marketing process, so that the marketing process that matches the event type is used as the target marketing process; or; The target event's corresponding customer group type was analyzed. The customer group type is matched with the triggering conditions of a pre-configured marketing process, so that the marketing process that matches the customer group type is used as the target marketing process.

3. The event response processing system as described in claim 1, characterized in that, The event response processing system also includes a target database; The event response processing engine is also used to extract operation record data for each step executed by the event response processing engine, and save the operation record data in the target database; When an instruction is received to query the historical execution steps of the event response processing engine, the response query reads the operation record data corresponding to the historical execution steps from the target database and renders and displays the read operation record data.

4. An event response processing method based on the event response processing system of claim 1, characterized in that, For an event response processing engine, the method includes: Real-time monitoring of trigger events initiated by users through the user terminal includes: establishing a polling channel with a target message queue of a message queue system, wherein the target message queue is used to receive event messages for each trigger event uploaded by the user terminal, and polling the event messages in the target message queue through the polling channel to monitor the trigger events in real time; When a target event triggered by the user is detected, the event data corresponding to the target event is sent to the target rule engine. The target rule engine is used to pass the event data into the trigger condition rule expression of each pre-configured marketing process for execution and return the execution result. The event response processing engine receives the execution result and matches the target marketing process according to the execution result. Each pre-configured marketing process is configured based on the process node components corresponding to the marketing strategy type. The process node components include trigger action components, attribute filtering components, event judgment components, and reach components. According to the process corresponding to the target marketing process, the target event is responded to and processed so as to send the marketing outreach message corresponding to the target marketing process to the user terminal; The system collects marketing response data after processing the target event and sends the marketing response data to a big data platform. The big data platform integrates the marketing response data and generates user profile tag data based on the integrated data. The user profile tag data is then fed back to the event response processing engine. The event response processing engine receives external user-triggered events, analyzes and judges different trigger events and / or customer groups to execute different marketing processes, and pushes different marketing outreach messages.

5. The event response processing method as described in claim 4, characterized in that, The step of matching the target event with the triggering conditions of a pre-configured marketing process to identify the target marketing process includes: Parse the event type corresponding to the target event; The event type is matched with the triggering conditions of a pre-configured marketing process, so that the marketing process that matches the event type is used as the target marketing process; or; The target event's corresponding customer group type was analyzed. The customer group type is matched with the triggering conditions of a pre-configured marketing process, so that the marketing process that matches the customer group type is used as the target marketing process.

6. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the event response processing method as described in any one of claims 4 to 5, or implements the function of the event response processing engine in the event response processing system as described in any one of claims 1 to 3.

7. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the event response processing method as described in any one of claims 4 to 5, or implements the function of the event response processing engine in the event response processing system as described in any one of claims 1 to 3.

Images