Marketing activity automation implementation method and device, equipment and storage medium

Abstract

The invention discloses a marketing activity automation implementation method and device, equipment and a storage medium, and relates to the technical field of computers, and the method comprises the steps: building a component flow configuration table based on component nodes, component numbers, component types, component sub-nodes and business demands, and determining a target marketing flow through the component flow configuration table; determining component scheduling configuration information corresponding to the target marketing process by using a plurality of process processing interfaces of a pre-configured marketing activity process; wherein the pre-configured flow processing interface comprises a flow execution interface, a flow propulsion interface, a flow termination interface and a data distribution interface; and triggering a corresponding marketing activity execution operation based on the component scheduling configuration information and the target marketing process so as to complete automation of the marketing activity. Therefore, the reliability and efficiency of marketing activity automation are improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and storage medium for automating marketing activities. Background Art

[0002] As consumer finance business is booming, marketing activities are at a critical stage of deep transformation from traditional business models to digital models.

[0003] Most of the existing marketing automation solutions are deeply coupled with various business systems and lack universality. This means that whenever the business system changes or new businesses are expanded, the relevant configuration and development of marketing activities need to be adjusted and rewritten on a large scale, resulting in a long marketing development cycle and difficulty in quickly responding to market changes and business needs. In addition, there is a lack of an effective component scheduling engine to unify and coordinate various key components, resulting in poor process universality and difficulty in adapting to marketing activity needs in different business scenarios.

[0004] Therefore, how to improve the reliability and efficiency of marketing activity automation to enhance user experience is a technical problem that needs to be solved urgently. Summary of the invention

[0005] In view of this, the purpose of the present invention is to provide a method, device, equipment and storage medium for realizing marketing activity automation, which can improve the reliability and efficiency of marketing activity automation. The specific scheme is as follows:

[0006] In a first aspect, the present application provides a method for automating marketing activities, including:

[0007] A component process configuration table is constructed based on component nodes, component numbers, component types, component sub-nodes, and business requirements, and a target marketing process is determined using the component process configuration table; wherein the component nodes are nodes in a multi-branch tree constructed in advance based on the dependency relationship between target components, the target components are components obtained by abstracting various process links in the marketing activity process, different types of components correspond to different types of process links, and the component sub-nodes are leaf nodes of the component nodes;

[0008] Determine the component scheduling configuration information corresponding to the target marketing process by using several process processing interfaces of the pre-configured marketing activity process; wherein the pre-configured process processing interface includes a process execution interface, a process advancement interface, a process termination interface and a data diversion interface;

[0009] The corresponding marketing activity execution operation is triggered based on the component scheduling configuration information and the target marketing process to complete the automation of the marketing activity.

[0010] Optionally, triggering a corresponding marketing activity execution operation based on the component scheduling configuration information and the target marketing process includes:

[0011] When the component type of the component node in the target marketing process is an event component, the events in the event component obtained through various business systems are converted based on preset conversion rules, and the converted events are determined as pending events in the event registration table;

[0012] When the target event is detected, the target event is queried in the event registration table based on the event to be processed, the user identity information and the event identification information to obtain a first query result;

[0013] If the first query result indicates that the target event does not exist in the event registration table, calling the process termination interface to terminate the current process;

[0014] If the first query result indicates that the target event exists in the event registration table, matching the target event in the event registration table based on an event matching rule to obtain a target matching result;

[0015] If the target matching result indicates that the match fails, the process termination interface is called to terminate the current process;

[0016] If the target matching result indicates a successful match, a target matching event matching the target event is obtained from the event registration table, and a logical relationship between the target matching event and the target event is judged based on a preset logical rule to obtain a first judgment result;

[0017] If the first judgment result indicates that the logical relationship between the target matching event and the target event is an AND relationship, querying the target event in the event record table to obtain a second query result;

[0018] If the second query result indicates that the target matching events do not all exist in the event record table, then a table entry record corresponding to the target event is generated in the event record table, and the process termination interface is called to terminate the current process;

[0019] If the second query result indicates that the target matching events all exist in the event record table or the first judgment result indicates that the logical relationship between the target event and the target matching event is an or relationship, then a table entry record corresponding to the target event is generated in the event record table, and the process advancement interface is called to advance the current process.

[0020] Optionally, triggering a corresponding marketing activity execution operation based on the component scheduling configuration information and the target marketing process includes:

[0021] When the component type of the component node in the target marketing process is a user component, acquiring an input state of the process execution interface to complete a state acquisition operation;

[0022] When the input state indicates that no user information is input in the process execution interface, determining a target user file based on a user system, and splitting the target user file into corresponding user data streams based on a user component and the data splitting interface;

[0023] After the processing of the user data flow is completed, calling the process termination interface to terminate the current process;

[0024] When the input state indicates that the user information is input in the process execution interface, the system determines whether the user information satisfies a preset information screening condition based on the user to obtain a second determination result;

[0025] If the second judgment result indicates that it is satisfied, calling the process advancement interface to advance the current process;

[0026] If the second judgment result indicates that it is not satisfied, the process termination interface is called to terminate the current process.

[0027] Optionally, triggering a corresponding marketing activity execution operation based on the component scheduling configuration information and the target marketing process includes:

[0028] When the component type of the component node in the target marketing process is a delayed component, generating a task record corresponding to the delayed task in the delayed task table;

[0029] Determining, based on the delay component, a target task record in the task record whose trigger time is earlier than the current time and whose trigger state is to be triggered;

[0030] The process advancement interface is called to advance the current process corresponding to the target task record, and the sleep time is determined based on the current time and the next trigger time, so as to jump again to the step of determining, based on the delay component, in the task record that the trigger time is less than the current time and the trigger status is to be triggered.

[0031] Optionally, triggering a corresponding marketing activity execution operation based on the component scheduling configuration information and the target marketing process includes:

[0032] When the component type of the component node in the target marketing process is a reach component, determining a corresponding scheduled task;

[0033] When the scheduled task is triggered, the corresponding data flow record is determined in the data aggregation record table based on the batch number corresponding to the scheduled task, and the current process is batch-reached based on the data flow record;

[0034] When the process advancement interface is triggered, a current access record is generated in the data aggregation record table, and the amount of data in the current batch is counted based on the serial number information of the current access record to obtain a statistical result;

[0035] If the statistical result shows that the data volume is not less than the preset quantity threshold, the scheduled task is canceled and the current process is batch-reached;

[0036] If the statistical result shows that the data volume is less than the preset quantity threshold, the process termination interface is called to terminate the current process.

[0037] Optionally, the component type of the starting component node in the target component process is a user component or an event component.

[0038] Optionally, the method for automating marketing activities further includes:

[0039] Use the component status query interface to obtain the execution status of the current component node to complete the status acquisition operation;

[0040] When the execution status indicates completion, the process advancement interface is called to execute the component subnode.

[0041] In a second aspect, the present application provides a device for automating marketing activities, including:

[0042] A process determination module is used to construct a component process configuration table based on component nodes, component numbers, component types, component sub-nodes and business requirements, and use the component process configuration table to determine the target marketing process; wherein the component nodes are nodes in a multi-branch tree pre-constructed based on the dependency relationship between target components, the target components are components obtained by abstracting various process links in the marketing activity process, different types of components correspond to different types of process links, and the component sub-nodes are leaf nodes of the component nodes;

[0043] An information determination module, used to determine the component scheduling configuration information corresponding to the target marketing process by using several process processing interfaces of the pre-configured marketing activity process; wherein the pre-configured process processing interface includes a process execution interface, a process advancement interface, a process termination interface and a data diversion interface;

[0044] The marketing execution module is used to trigger corresponding marketing activity execution operations based on the component scheduling configuration information and the target marketing process to complete the automation of the marketing activity.

[0045] In a third aspect, the present application provides an electronic device, including:

[0046] Memory, used to store computer programs;

[0047] The processor is used to execute the computer program to implement the aforementioned method for automating marketing activities.

[0048] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the aforementioned method for automating marketing activities is implemented.

[0049] In the present application, a component process configuration table is constructed based on component nodes, component numbers, component types, component sub-nodes and business requirements, and the target marketing process is determined using the component process configuration table; wherein the component nodes are nodes in a multi-branch tree pre-constructed based on the dependencies between target components, and the target components are components obtained by abstracting various process links in the marketing activity process, different types of components correspond to different types of process links, and the component sub-nodes are leaf nodes of the component nodes; the component scheduling configuration information corresponding to the target marketing process is determined using several process processing interfaces of the pre-configured marketing activity process; wherein the pre-configured process processing interface includes a process execution interface, a process advancement interface, a process termination interface and a data diversion interface; based on the component scheduling configuration information and the target marketing process, the corresponding marketing activity execution operation is triggered to complete the automation of the marketing activity. As can be seen from the above, this application builds a component process configuration table based on component nodes, component numbers, component types, component sub-nodes and business requirements, and determines the target marketing process accordingly, and then uses the process execution interface, process advancement interface, process termination interface and data diversion interface to clarify the component scheduling configuration information, and finally realizes the automation of marketing activities based on the component scheduling configuration information and the target marketing process. In this way, this application can improve the reliability and efficiency of marketing activity automation, thereby enhancing the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0051] Figure 1 A flowchart for automating a marketing activity disclosed in this application;

[0052] Figure 2 A schematic diagram of component scheduling disclosed in this application;

[0053] Figure 3 A schematic diagram of the interaction between a component scheduling engine and internal execution logic of a component disclosed in this application;

[0054] Figure 4 This is a schematic diagram of an event component execution disclosed in this application;

[0055] Figure 5 An event component execution flow chart disclosed in this application;

[0056] Figure 6 A user component execution sequence diagram disclosed in this application;

[0057] Figure 7 A user component execution flow chart disclosed in this application;

[0058] Figure 8 A delay component execution flow chart disclosed in this application;

[0059] Fig. 9 A delay component execution flow chart disclosed in this application;

[0060] Fig.10 A schematic diagram of a component multi-branch tree disclosed in this application;

[0061] Fig.11 A method disclosed in this application Fig.10 The corresponding component configuration is shown schematically;

[0062] Fig.12 This is a schematic diagram of the structure of a device for automating marketing activities disclosed in this application;

[0063] Fig.13 This is a structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION

[0064] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0065] Most existing marketing activity automation solutions are deeply coupled with various business systems and lack universality. This means that whenever the business system changes or new businesses are expanded, the relevant configuration and development of marketing activities need to be adjusted and rewritten on a large scale, resulting in a long marketing activity development cycle and difficulty in quickly responding to market changes and business needs. In addition, there is a lack of an effective component scheduling engine to unify and coordinate various key components, resulting in poor process universality and difficulty in adapting to marketing activity needs in different business scenarios. To this end, this application provides a method for implementing marketing activity automation that can improve the reliability and efficiency of marketing activity automation.

[0066] See also Figure 1 As shown, the embodiment of the present invention discloses a method for automating marketing activities, including:

[0067] Step S11, construct a component process configuration table based on component nodes, component numbers, component types, component sub-nodes and business requirements, and use the component process configuration table to determine the target marketing process; wherein, component nodes are nodes in a multi-branch tree pre-constructed based on the dependency relationship between target components, target components are components obtained by abstracting various process links in the marketing activity process, different types of components correspond to different types of process links, and component sub-nodes are leaf nodes of component nodes.

[0068] In this embodiment, it is necessary to first construct a component flow configuration table. The component types in the component flow configuration table include event components, user components, delay components, and reach components. Figure 2 As shown in the figure, the event component is responsible for event reception, rule judgment, logical judgment and event recording. Among them, event reception refers to receiving various event data reported by various systems; rule judgment refers to making rule judgments on the received events and filtering out events that meet the rules; logical judgment refers to making combined judgments on events; event recording refers to recording the events that occurred in the database for data backtracking. The user component is responsible for user filtering and user screening. Among them, user filtering refers to filtering users according to user information and filtering rules to filter out users who do not meet the conditions; user screening refers to filtering out all qualified users according to the rules, and the user screening process needs to rely on the user system. The delay component triggers the delay task through delay task registration and delay task scheduling. In addition, the reach component is responsible for batch reach, single reach, reach means and reach callback. Among them, single reach refers to reaching one user at a time, batch reach refers to reaching through batch aggregation, reach means refers to reaching in multiple scenarios, such as SMS, outbound calls, rights and interests, etc., and reach callback refers to processing the callback data of the reach result.

[0069] It should be noted that the component type of the starting component node in the target component process is a user component or an event component. When the user component is used as the starting point, since the specific users who will become the audience of this marketing activity are determined, the subsequent marketing process has a basis and direction for implementation. In addition, when the event component is used as the starting point, once a specific event is detected, such as customers frequently browsing a certain type of product, the corresponding marketing process can be quickly triggered.

[0070] However, in this embodiment, the reach component is not suitable as the starting component node. Since the focus of the reach component is how to deliver the marketing content when the target user has been determined and the marketing process has been triggered, if the reach component is used as the starting point, without clarifying the target user and the triggering reason, there is no way to talk about who to reach and for what reason, and the entire marketing process lacks the necessary pre-logical foundation. Moreover, the delay component is also not suitable as a starting component node. Similarly, if it is used as the starting component, due to the lack of specific marketing trigger basis and target user indication in the early stage, the simple delay operation has no practical significance and does not meet the logical continuity requirements for the normal marketing process startup.

[0071] In addition, in this embodiment, in order to realize the monitoring and data statistics of each component, it is necessary to maintain a component execution record table. The reason why such a table needs to be maintained is that it can realize comprehensive monitoring and data statistics of each component. By recording the execution status and execution data of each component, the operation status of the entire marketing process can be understood. If the component execution record table is not set, the working status of each component will not be known. When there is a problem in the marketing process, it may take a lot of time and effort to check the components one by one, which is extremely inefficient. Moreover, without the support of data statistics, it is impossible to evaluate the contribution of each component to the marketing effect, and it is impossible to adjust the marketing strategy and optimize the component configuration in time, which in turn affects the effect and efficiency of the entire marketing activity.

[0072] Step S12: Determine the component scheduling configuration information corresponding to the target marketing process using several process processing interfaces of the pre-configured marketing activity process; wherein the pre-configured process processing interface includes a process execution interface, a process advancement interface, a process termination interface and a data diversion interface.

[0073] It can be understood that in this embodiment, see Figure 3 As shown, the component scheduling configuration information is a process processing interface pre-configured according to the marketing activity process, that is, the component scheduling configuration information is the information integrated by the process execution interface, the process advancement interface, the process termination interface and the data diversion interface, and the component scheduling engine can read the component scheduling configuration information, call each interface according to its guidance, and schedule the component operation in an orderly manner.

[0074] Furthermore, by calling the process execution interface of the component scheduling engine, the component can be pulled up to execute the specific component logic. After the execution is completed, the process promotion interface will be called. The component scheduling engine will query the component process configuration table to query the component sub-node list of the current component node, and then call the process execution interface for each component sub-node, thereby realizing the closed loop of the entire link and connecting all components in series. When the process needs to be terminated, the process termination interface of the component scheduling engine needs to be called, and the component scheduling engine will directly block the subsequent process. The data diversion interface of the component scheduling engine is used to undertake the data flow diversion scenario, that is, the activity-level data flow is changed to the user-level data flow. From the overall point of view, when the marketing process activity is released, the process execution interface of the starting component is executed, and the subsequent promotion is promoted by each component calling the process promotion interface, data diversion interface and process termination interface to promote the entire process.

[0075] It should be noted that, in this embodiment, the component status query interface is used to obtain the execution status of the current component node to complete the status acquisition operation. When the execution status indicates that it has been completed, the process advancement interface is called to execute the component subnode. That is, once the status query shows that the current component node has completed the established task, the process advancement interface will respond quickly and activate the next component subnode to be put into operation according to the guidance of the component process configuration table.

[0076] Specifically, a scheduled task is maintained inside the component scheduling engine. It periodically scans execution records that have not been completed for a long time and calls the component status query interface to obtain the execution status. If the status has been completed, the normal advancement process is required. Otherwise, the alarm mechanism will be triggered to notify R&D personnel to troubleshoot the problem, thereby achieving effective monitoring of each component.

[0077] Step S13: triggering corresponding marketing activity execution operations based on the component scheduling configuration information and the target marketing process to complete the automation of the marketing activity.

[0078] In a specific embodiment, see Figure 4 and Figure 5As shown, when the component type of the component node in the target marketing process is an event component, the events obtained through each business system in the event component are converted based on the preset conversion rules, and the converted events obtained are determined as pending events in the event registry. It should be noted that each business system may include a front-end system, a user system, an accounting system, an accounting system, a risk control system, and a post-loan system. In addition, the events reported by each business system can reflect the corresponding business scenarios. For example, in the financial field scenario, the reported events include but are not limited to login, card binding, credit, repayment, increase, adjustment, credit certification, activity browsing, activity clicks, face recognition, and contract signing. And each event has its own unique business attributes. For example, the event of borrowing has business attributes such as product number, loan amount, and loan interest rate.

[0079] When the target event is detected, the target event is queried in the event registry based on the pending event, user identity information, and event identification information to obtain the first query result. If the first query result shows that the target event does not exist in the event registry, the process termination interface is called to terminate the current process; if the first query result shows that the target event exists in the event registry, the target event is matched in the event registry based on the event matching rules to obtain the target matching result. It should be noted that after the external event is converted into an internal event, all event matching rules can be expressed by a unified rule expression, and the event can be matched through the internal event information and the rule expression, thereby filtering out events that meet the conditions. For example, the event expression for a loan greater than 10,000 can be written as eventCode=`loanSubmit` && loanAmt>10000.

[0080] Specifically, if the target matching result indicates that the match fails, the process termination interface is called to terminate the current process; if the target matching result indicates that the match succeeds, the target matching event that matches the target event is obtained from the event registration table, and the logical relationship between the target matching event and the target event is judged based on the preset logical rules to obtain a first judgment result. If the first judgment result indicates that the logical relationship between the target matching event and the target event is an AND relationship, the target event is queried in the event record table to obtain a second query result;

[0081] It can be understood that in this embodiment, if the second query result shows that the target matching events do not all exist in the event record table, then a table entry record corresponding to the target event is generated in the event record table, and the process termination interface is called to terminate the current process; if the second query result shows that the target matching events all exist in the event record table or the first judgment result shows that the logical relationship between the target event and the target matching event is an or relationship, then a table entry record corresponding to the target event is generated in the event record table, and the process advancement interface is called to advance the current process.

[0082] In a specific embodiment, see Figure 6 and Figure 7 As shown, when the component type of the component node in the target marketing process is a user component, the input status of the process execution interface is obtained to complete the status acquisition operation. When the input status indicates that there is no user information input in the process execution interface, the target user file is determined based on the user system, and the target user file is split into corresponding user data streams based on the user component and the data diversion interface. After the processing of the user data stream is completed, the process termination interface is called to terminate the current process.

[0083] On the contrary, when the input status indicates that there is user information input in the process execution interface, the user system determines whether the user information meets the preset information screening condition based on the user information to obtain a second judgment result. If the second judgment result shows that it meets the condition, the process advancement interface is called to advance the current process; if the second judgment result shows that it does not meet the condition, the process termination interface is called to terminate the current process.

[0084] In a specific embodiment, see Figure 8 As shown, when the component type of the component node in the target marketing process is a delayed component, a task record corresponding to the delayed task is generated in the delayed task table. Based on the delayed component, a target task record whose trigger time is earlier than the current time and whose trigger state is to be triggered is determined in the task record.

[0085] In this embodiment, the process advancement interface is called to advance the current process corresponding to the target task record, and the sleep time is determined based on the current time and the next trigger time, so as to jump again to the step of determining in the task record based on the delay component that the trigger time is less than the current time and the trigger status is to be triggered.

[0086] In a specific embodiment, see Fig. 9As shown, when the component type of the component node in the target marketing process is a reach component, the corresponding scheduled task is determined; when the scheduled task is triggered, the corresponding data flow record is determined in the data aggregation record table based on the batch number corresponding to the scheduled task, and the current process is batch reached based on the data flow record; when the process advancement interface is triggered, the current reach record is generated in the data aggregation record table, and the data volume of the current batch is counted based on the number information of the current reach record to obtain the statistical result;

[0087] It should be noted that if the statistical results show that the data volume is not less than the preset threshold, the scheduled task will be canceled and the current process will be batch-reached; if the statistical results show that the data volume is less than the preset threshold, the process termination interface will be called to terminate the current process.

[0088] As can be seen from the above, this application builds a component process configuration table based on component nodes, component numbers, component types, component sub-nodes and business requirements, and determines the target marketing process accordingly, and then uses the process execution interface, process advancement interface, process termination interface and data diversion interface to clarify the component scheduling configuration information, and finally realizes the automation of marketing activities based on the component scheduling configuration information and the target marketing process. In this way, this application can improve the reliability and efficiency of marketing activity automation, thereby enhancing the user experience.

[0089] Combine the following Fig.10 and Fig.11 The schematic diagram shown specifically illustrates the technical solution of the embodiment of the present application.

[0090] Specifically, first, the components can be connected in order in the form of a multi-branch tree to determine the target marketing process. That is, the dependency relationship between the components can be abstracted into a multi-branch tree, and each node of the multi-branch tree is a specific component. The form of the multi-branch tree can be as follows: Fig.10As shown in the figure. As can be seen from the figure, the marketing process starts with user component 1, through which users aged over 30 and under 50 who do not follow a specific public account are screened out. Then multiple branch operations are launched. On the one hand, in order to guide users to follow the public account, the contact component 1 will send a text message to the screened users to follow the public account, and then the user component 2 will filter out users in Hunan Province based on certain filtering rules. After filtering the users in Hunan Province, enter the timeout component 1 for a 30-minute delay operation, then the user component 3 filters out male users, and finally the contact component 2 issues coupons to attract the remaining users after the screening operation. On the other hand, the user component 4 filters new customer users, and then enters the event component 1. When the loan occurs, the contact component 3 will intelligently call out to remind the user that the loan is successful. After passing through the contact component 3, on the one hand, then after the 3-day delay of the timeout component 2, after 3 days, in order to help users understand their financial status in a timely manner, the contact component 5 will send a text message to check the bill. On the other hand, the contact component 4 will send new customer loan coupons to attract users.

[0091] In addition, in order to realize the above-mentioned multi-branch tree structure of each component, it is necessary to determine the component process configuration table. The core fields of the component process configuration table include the entry serial number, component number, component type, and component child node. The component process configuration table corresponding to the above-mentioned multi-branch tree can be as follows: Fig.11 As shown in the figure, cust represents the user component, reach represents the reach component, dealy represents the delay component, and event represents the event component.

[0092] Each component is the basic unit of the target marketing activity process, and each interface is a bridge connecting each component. It should be noted that the process execution interface input parameters include the entry serial number, component id (i.e. identity document, ID card identification number), and user id. The serial number refers to the number of entering the marketing activity. Each time the activity is executed, there will be a new serial number, which is the activity-level data; the user id can be a null value, because there is no user information when the activity starts to execute, which is the activity-level data flow. The process advancement interface input parameters include the serial number, user id and component id, and the input parameter data is the same as the process execution interface input parameters. The process termination interface input parameters include the serial number, user id and component id, and the input parameter data is the same as the process execution interface input parameters. The data diversion interface input parameters include the entry serial number, user id and component id. The user id is the user id after diversion. Often an activity-level data flow can be diverted into a series of user-level data flows.

[0093] It can be understood that, taking the above multi-branch tree as an example, the first component node is user component 1, then the process execution interface will be called for user component 1 to filter users. At this time, there is no user id in the input parameter, so the user component can obtain the full amount of user data, and then the activity level data stream needs to be diverted into the user level data stream. For example, if 100 users are filtered out through user component 1, the data diversion interface will be called 100 times. After processing, the process termination interface will be called. At this time, the serial number of the input parameter is consistent with the input parameter of the process execution interface, and the user id is empty.

[0094] In addition, the component execution record table is used to monitor and collect data of each component. The core fields of the component execution record table include entry serial number, user id, component number, component type, execution status, start execution time and end execution time. The user id can be a null value, and the execution status enumeration includes in progress, completed, and terminated. When calling the component process execution interface, the record status of the component execution record table is in progress. When the component completes the call to the process advancement interface, the status is ended. When the component terminates the call to the process termination interface, the status is terminated.

[0095] Furthermore, when the component type of the component node is an event component, in this embodiment, an event component configuration table, an event registration table, and an event record table are configured in the event component. Specifically, the event component configuration table records the event information that each event component needs to process, and the core fields include component id, event id, and event rule; the event registration table is responsible for recording all events that need to be processed, and the core fields include event id, event rule, user id, and occurrence time; the event record table is responsible for recording all event reporting records, and the core fields include event id, component id, occurrence time, and user id.

[0096] When the event component starts to execute, it first writes the current pending event into the event registry, and then starts waiting for the event to come. Among them, the pending event comes from the event component configuration table. When the current event (i.e., the target event) is detected, the event registry is queried according to the user id and event id. If the current event exists, the subsequent process is executed, otherwise it is directly blocked. Then, the current event is matched according to the rule expression (i.e., the event matching rule). If the match is successful, the next process is entered, otherwise the current process is directly blocked. Then, according to the preset logical rules, the current event and the event that matches the current event (i.e., the target matching event) are logically judged. If the two are in an AND relationship, the event record table needs to be queried. If all the associated events exist in the event record table, the current event is inserted into the event record table, and the process advancement interface is called. Otherwise, the current event is inserted into the event record table, and the process termination interface is called; if it is an OR relationship, the current event is inserted into the event record table, and the process advancement interface is called.

[0097] In this embodiment, when the component type of the component node is a user component, the user component contains a user component configuration table. The user component configuration table records the user information that each user component needs to filter, and the core fields include component id, event id and user filtering conditions (that is, preset information filtering conditions). It should be noted that the user component needs to interact with the user system. When there is no user information in the input parameter of the process execution interface, it means that the current process needs to filter out all user lists, and then call the user system to query the user list that meets the user filtering conditions. At this time, the input parameter is the user filtering condition. The user system cannot immediately return the full user list. The user system will start an asynchronous thread to filter users that meet the user filtering conditions. The filtered user data will be sent to the user component in the form of a file. After receiving the user data, the user component starts to process the user file, calls the data diversion interface to split it into user streams, and after all user data streams are processed, finally calls the process termination interface to end the current process.

[0098] On the contrary, when the input parameter of the component process execution interface contains user information, the user system is called to query the user information that meets the user screening conditions. The input parameter is the user ID. The user system will return the queried user information, and then the user component will make a user information judgment. For user information that meets the user screening conditions, the process promotion interface is called to normally promote the execution of subsequent processes; and for user information that does not meet the user screening conditions, the process termination interface is called to end the current process.

[0099] When the component type of the component node is a delay component, the delay component contains a delay component configuration table. The delay component configuration table records the timeout information that each delay component needs to filter. The core fields include component id, event id and timeout time. The timeout time is the time that needs to be delayed, that is, the sleep time. It can be understood that the delay component has the ability of delayed triggering. Therefore, the delay component needs to maintain a delay task table. Its core fields include task id, component id, user id, trigger time, and trigger status. Among them, the task id represents the unique identifier of the current task, the trigger time is the next wake-up time of the task, and the trigger status includes triggered and pending triggering. When the delay component is called to start execution, a task record will first be inserted into the delay task table, and then wait for the task to be called up. The trigger time of the delay task is the current time plus the timeout time of the delay component configuration table.

[0100] Furthermore, the delay component will start a real-time running thread, which will periodically query tasks that meet certain conditions. Since marketing activities are not very sensitive to time, the period of scheduled scanning can be set to 1 minute. When the thread is awakened, it will query all task records whose trigger time is earlier than the current time and whose trigger status is to be triggered from the delay task table, and then call the process advancement interface according to the component id, user id, and serial number. When all task records are processed, the next wake-up time will be calculated. For example, if the current time is 12:00:00 and the next trigger time is 12:00:30, then the current thread will directly execute the operation of sleeping for 30 seconds.

[0101] When the component type of the component node is a reach component, the reach component contains a reach component configuration table. The reach component configuration table records the information that each reach component needs to reach. The core fields include component id, event id, reach channel, and reach content.

[0102] In the marketing automation process, the real-time requirements for reach are often not high, so data stream aggregation can be used. Currently, window aggregation and upper limit aggregation are supported. Window aggregation refers to setting a time window and aggregating all data streams within the time window into one data stream, while upper limit aggregation refers to counting the number of data streams and aggregating the data after reaching a certain upper limit (that is, the preset number threshold). In addition, by maintaining the data aggregation record table, all data that needs to be aggregated can be easily stored. The core fields of the data aggregation record table include user id, component id, serial number, reach channel, reach content, batch number and occurrence time. The batch number is stored in Redis (i.e. RemoteDictionary Server, remote dictionary service). Every time a batch of data is aggregated, the batch number is incremented by 1.

[0103] For window aggregation, a scheduled task will be set, which will be executed once every 10 minutes on average. After the scheduled task starts to execute, the data flow records filtered out by the record table will be aggregated according to the statistical data of the current batch number, and batches will be reached. After the batch is reached, a new scheduled task will be registered and executed 10 minutes later. For upper limit aggregation, when the reach component starts to execute, the content related to the current reach will first be written into the data aggregation record table, and then the data volume of the current batch in the record table will be aggregated according to the statistical data of the current batch number. If the aggregation limit is exceeded, data aggregation will be performed directly for batch reach. At the same time, the scheduled task of the current time window will be canceled, and a new scheduled task will be registered and executed 10 minutes later.

[0104] In addition, it should be emphasized that in many contact scenarios, it is impossible to obtain contact results in real time, such as SMS contact, which relies on data callbacks from various operators. Therefore, the specific execution of the component is to query the data aggregation record table according to the user ID after receiving the callback result, obtain the user ID, component ID and serial number, and call the process promotion interface to promote the subsequent process.

[0105] Accordingly, see Fig.12 As shown, the embodiment of the present application also provides a device for automating marketing activities, including:

[0106] The process determination module 11 is used to construct a component process configuration table based on component nodes, component numbers, component types, component sub-nodes and business requirements, and use the component process configuration table to determine the target marketing process; wherein the component nodes are nodes in a multi-branch tree pre-constructed based on the dependency relationship between target components, the target components are components obtained by abstracting various process links in the marketing activity process, different types of components correspond to different types of process links, and the component sub-nodes are leaf nodes of the component nodes;

[0107] The information determination module 12 is used to determine the component scheduling configuration information corresponding to the target marketing process by using several process processing interfaces of the pre-configured marketing activity process; wherein the pre-configured process processing interface includes a process execution interface, a process advancement interface, a process termination interface and a data diversion interface;

[0108] The marketing execution module 13 is used to trigger corresponding marketing activity execution operations based on the component scheduling configuration information and the target marketing process to complete the automation of the marketing activity.

[0109] As can be seen from the above, this application builds a component process configuration table based on component nodes, component numbers, component types, component sub-nodes and business requirements, and determines the target marketing process accordingly, and then uses the process execution interface, process advancement interface, process termination interface and data diversion interface to clarify the component scheduling configuration information, and finally realizes the automation of marketing activities based on the component scheduling configuration information and the target marketing process. In this way, this application can improve the reliability and efficiency of marketing activity automation, thereby enhancing the user experience.

[0110] In a specific implementation, the marketing execution module 13 includes:

[0111] An event determination unit, configured to, when the component type of the component node in the target marketing process is an event component, transform the events in the event component obtained through each business system based on a preset transformation rule, and determine the obtained transformed events as pending events in an event registration table;

[0112] A first event query unit is used to query the target event in the event registration table based on the event to be processed, the user identity information and the event identification information when the target event is detected to obtain a first query result;

[0113] A first process termination unit, configured to call the process termination interface to terminate the current process if the first query result indicates that the target event does not exist in the event registration table;

[0114] an event matching unit, configured to match the target event in the event registration table based on an event matching rule to obtain a target matching result if the first query result indicates that the target event exists in the event registration table;

[0115] A second process termination unit, configured to call the process termination interface to terminate the current process if the target matching result indicates that the match fails;

[0116] An event judgment unit, configured to obtain a target matching event that matches the target event from the event registration table if the target matching result indicates that the match is successful, and to judge the logical relationship between the target matching event and the target event based on a preset logical rule to obtain a first judgment result;

[0117] A second event query unit, configured to query the target event in an event record table to obtain a second query result if the first judgment result indicates that the logical relationship between the target matching event and the target event is an AND relationship;

[0118] A third process termination unit is used to generate a table entry record corresponding to the target event in the event record table if the second query result shows that the target matching event does not all exist in the event record table, and call the process termination interface to terminate the current process;

[0119] The first process advancement unit is used to generate a table entry record corresponding to the target event in the event record table if the second query result shows that the target matching events all exist in the event record table or the first judgment result shows that the logical relationship between the target event and the target matching event is an or relationship, and call the process advancement interface to advance the current process.

[0120] In a specific implementation, the marketing execution module 13 includes:

[0121] a first state acquisition unit, configured to acquire an input state of the process execution interface when the component type of the component node in the target marketing process is a user component, so as to complete a state acquisition operation;

[0122] a file splitting unit, configured to determine a target user file based on a user system when the input state indicates that no user information is input in the process execution interface, and split the target user file into corresponding user data streams based on a user component and the data splitting interface;

[0123] A fourth process termination unit, configured to call the process termination interface to terminate the current process after the processing of the user data flow is completed;

[0124] an information screening unit, configured to determine, based on the user system, whether the user information satisfies a preset information screening condition when the input status indicates that the user information is input in the process execution interface, so as to obtain a second determination result;

[0125] A second process advancement unit, configured to call the process advancement interface to advance the current process if the second judgment result indicates that the current process is satisfied;

[0126] The fifth process termination unit is used to call the process termination interface to terminate the current process if the second judgment result indicates that it is not satisfied.

[0127] In a specific implementation, the marketing execution module 13 includes:

[0128] a record generating unit, configured to generate a task record corresponding to a delayed task in a delayed task table when the component type of the component node in the target marketing process is a delayed component;

[0129] A record determination unit, configured to determine, based on the delay component, in the task record a target task record whose trigger time is earlier than the current time and whose trigger state is to be triggered;

[0130] The third process advancement unit is used to call the process advancement interface to advance the current process corresponding to the target task record, and determine the sleep time based on the current time and the next trigger time, so as to jump again to the step of determining, based on the delay component, in the task record that the trigger time is less than the current time and the trigger state is to be triggered.

[0131] In a specific implementation, the marketing execution module 13 includes:

[0132] A task determination unit, configured to determine a corresponding scheduled task when the component type of the component node in the target marketing process is a reach component;

[0133] A first process access unit, configured to determine, in a data aggregation record table, a corresponding data flow record based on a batch number corresponding to the scheduled task when the scheduled task is triggered, and perform batch access to the current process based on the data flow record;

[0134] A data volume statistics unit, used for generating a current access record in the data aggregation record table when the process advancement interface is triggered, and counting the data volume of the current batch based on the serial number information of the current access record to obtain a statistical result;

[0135] A second process access unit is used to cancel the scheduled task and perform batch access on the current process if the statistical result shows that the data volume is not less than a preset quantity threshold;

[0136] The sixth process termination unit is used to call the process termination interface to terminate the current process if the statistical result shows that the data volume is less than the preset quantity threshold.

[0137] In a specific implementation, the component type of the starting component node in the target component process is a user component or an event component.

[0138] In a specific implementation, the marketing execution module 13 further includes:

[0139] A second state acquisition unit, used to acquire the execution state of the current component node by using the component state query interface to complete the state acquisition operation;

[0140] The node execution unit is used to call the process advancement interface to execute the component sub-node when the execution status indicates completion.

[0141] Furthermore, the present application also discloses an electronic device. Fig.13 This is a structural diagram of an electronic device 20 according to an exemplary embodiment, and the content in the figure cannot be regarded as any limitation on the scope of use of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the method for automating marketing activities disclosed in any of the aforementioned embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0142] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0143] In addition, the memory 22 as a carrier for resource storage may be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon may include an operating system 221, a computer program 222, etc., and the storage method may be temporary storage or permanent storage.

[0144] The operating system 221 is used to manage and control the hardware devices and computer programs 222 on the electronic device 20, which can be Windows Server, Netware, Unix, Linux, etc. In addition to including computer programs that can be used to complete the marketing activity automation implementation method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include computer programs that can be used to complete other specific tasks.

[0145] Furthermore, the present application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the aforementioned disclosed method for automating marketing activities is implemented. The specific steps of the method can be referred to the corresponding contents disclosed in the aforementioned embodiments, and will not be repeated here.

[0146] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0147] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0148] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0149] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0150] The technical solution provided by the present application is introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for general technicians in this field, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for automating marketing activities, characterized in that: include: A component process configuration table is constructed based on component nodes, component numbers, component types, component sub-nodes, and business requirements, and a target marketing process is determined using the component process configuration table; wherein the component nodes are nodes in a multi-branch tree constructed in advance based on the dependency relationship between target components, the target components are components obtained by abstracting various process links in the marketing activity process, different types of components correspond to different types of process links, and the component sub-nodes are leaf nodes of the component nodes; Determine the component scheduling configuration information corresponding to the target marketing process by using several process processing interfaces of the pre-configured marketing activity process; wherein the pre-configured process processing interface includes a process execution interface, a process advancement interface, a process termination interface and a data diversion interface; The corresponding marketing activity execution operation is triggered based on the component scheduling configuration information and the target marketing process to complete the automation of the marketing activity.

2. The method for automating marketing activities according to claim 1, characterized in that: The triggering of corresponding marketing activity execution operations based on the component scheduling configuration information and the target marketing process includes: When the component type of the component node in the target marketing process is an event component, the events in the event component obtained through various business systems are converted based on preset conversion rules, and the converted events are determined as pending events in the event registration table; When the target event is detected, the target event is queried in the event registration table based on the event to be processed, the user identity information and the event identification information to obtain a first query result; If the first query result indicates that the target event does not exist in the event registration table, calling the process termination interface to terminate the current process; If the first query result indicates that the target event exists in the event registration table, matching the target event in the event registration table based on an event matching rule to obtain a target matching result; If the target matching result indicates that the match fails, the process termination interface is called to terminate the current process; If the target matching result indicates a successful match, a target matching event matching the target event is obtained from the event registration table, and a logical relationship between the target matching event and the target event is judged based on a preset logical rule to obtain a first judgment result; If the first judgment result indicates that the logical relationship between the target matching event and the target event is an AND relationship, querying the target event in the event record table to obtain a second query result; If the second query result indicates that the target matching events do not all exist in the event record table, then a table entry record corresponding to the target event is generated in the event record table, and the process termination interface is called to terminate the current process; If the second query result indicates that the target matching events all exist in the event record table or the first judgment result indicates that the logical relationship between the target event and the target matching event is an or relationship, then a table entry record corresponding to the target event is generated in the event record table, and the process advancement interface is called to advance the current process.

3. The method for automating marketing activities according to claim 1, characterized in that: The triggering of corresponding marketing activity execution operations based on the component scheduling configuration information and the target marketing process includes: When the component type of the component node in the target marketing process is a user component, acquiring an input state of the process execution interface to complete a state acquisition operation; When the input state indicates that no user information is input in the process execution interface, determining a target user file based on a user system, and splitting the target user file into corresponding user data streams based on a user component and the data splitting interface; After the processing of the user data flow is completed, calling the process termination interface to terminate the current process; When the input state indicates that the user information is input in the process execution interface, the system determines whether the user information satisfies a preset information screening condition based on the user to obtain a second determination result; If the second judgment result indicates that it is satisfied, calling the process advancement interface to advance the current process; If the second judgment result indicates that it is not satisfied, the process termination interface is called to terminate the current process.

4. The method for automating marketing activities according to claim 1, characterized in that: The triggering of corresponding marketing activity execution operations based on the component scheduling configuration information and the target marketing process includes: When the component type of the component node in the target marketing process is a delayed component, generating a task record corresponding to the delayed task in the delayed task table; Determining, based on the delay component, a target task record in the task record whose trigger time is earlier than the current time and whose trigger state is to be triggered; The process advancement interface is called to advance the current process corresponding to the target task record, and the sleep time is determined based on the current time and the next trigger time, so as to jump again to the step of determining, based on the delay component, in the task record that the trigger time is less than the current time and the trigger status is to be triggered.

5. The method for automating marketing activities according to any one of claims 1 to 4, characterized in that: The triggering of corresponding marketing activity execution operations based on the component scheduling configuration information and the target marketing process includes: When the component type of the component node in the target marketing process is a reach component, determining a corresponding scheduled task; When the scheduled task is triggered, the corresponding data flow record is determined in the data aggregation record table based on the batch number corresponding to the scheduled task, and the current process is batch-reached based on the data flow record; When the process advancement interface is triggered, a current access record is generated in the data aggregation record table, and the amount of data in the current batch is counted based on the serial number information of the current access record to obtain a statistical result; If the statistical result shows that the data volume is not less than the preset quantity threshold, the scheduled task is canceled and the current process is batch-reached; If the statistical result shows that the data volume is less than the preset quantity threshold, the process termination interface is called to terminate the current process.

6. The method for automating marketing activities according to claim 1, characterized in that: The component type of the starting component node in the target component process is a user component or an event component.

7. The method for automating marketing activities according to claim 1, characterized in that: Also includes: Use the component status query interface to obtain the execution status of the current component node to complete the status acquisition operation; When the execution status indicates completion, the process advancement interface is called to execute the component subnode.

8. A device for automating marketing activities, characterized in that: include: A process determination module is used to construct a component process configuration table based on component nodes, component numbers, component types, component sub-nodes and business requirements, and use the component process configuration table to determine the target marketing process; wherein the component nodes are nodes in a multi-branch tree pre-constructed based on the dependency relationship between target components, the target components are components obtained by abstracting various process links in the marketing activity process, different types of components correspond to different types of process links, and the component sub-nodes are leaf nodes of the component nodes; An information determination module, used to determine the component scheduling configuration information corresponding to the target marketing process by using several process processing interfaces of the pre-configured marketing activity process; wherein the pre-configured process processing interface includes a process execution interface, a process advancement interface, a process termination interface and a data diversion interface; The marketing execution module is used to trigger corresponding marketing activity execution operations based on the component scheduling configuration information and the target marketing process to complete the automation of the marketing activity.

9. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the method for automating marketing activities as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Used to store a computer program; wherein, when the computer program is executed by a processor, the method for automating marketing activities as described in any one of claims 1 to 7 is implemented.

Images