Event-driven marketing campaign collaboration method, device, equipment and storage medium

Abstract

The application provides an event-driven marketing activity collaboration method and device, equipment and storage medium, relates to the technical field of digital service, and includes the following steps: receiving a loading trigger event of a target user for a target marketing activity sent by a first front-end device through an event bus; calling a scheduling layer to respond to the loading trigger event and obtaining strategy configuration information of the target marketing activity; sending the strategy configuration information to the first front-end device; receiving an execution trigger event of the target marketing activity triggered by an activity page through the first front-end device through the event bus; calling an engine layer to respond to the execution trigger event, so that a target logic component corresponding to the target marketing activity is called to execute an execution operation of the target user for the target marketing activity, and an execution result of the target user for the target marketing activity is obtained; and returning the execution result of the target marketing activity to the first front-end device. The application can improve the scalability and operation efficiency of the marketing activity.

Description

Technical Field

[0001] This application relates to the field of digital service technology, and more specifically, to an event-driven marketing campaign collaboration method, apparatus, device, and storage medium. Background Technology

[0002] Currently, enterprise marketing campaigns heavily rely on digital system support. Existing marketing campaign systems mainly fall into two categories: one is general-purpose low-code platforms, which provide basic page building and workflow orchestration capabilities. However, because the component libraries are general-purpose oriented and lack support for marketing scenario-specific functions, a large amount of customized development is required when adapting to specific marketing businesses, resulting in high costs and long cycles. The other is vertical marketing tools, which, although applicable to specific marketing scenarios, have functional boundaries limited to a single stage and cannot cover the entire process of front-end user interaction, back-end business logic, and operational configuration, making it difficult to achieve end-to-end collaboration in marketing campaigns.

[0003] Both types of systems generally suffer from coarse-grained component design, lacking the refined atomic components specific to marketing scenarios. Business personnel need to perform extensive secondary configurations to meet actual needs. Furthermore, most products fail to integrate data between the user end, backend logic, and operations end, leading to reliance on manual intervention for data synchronization and order processing after campaign launch, resulting in low operational efficiency and a high risk of errors. Therefore, achieving flexible orchestration and automated collaboration across the entire marketing campaign chain has become a pressing technical challenge in this field. Summary of the Invention

[0004] This application provides an event-driven marketing campaign collaboration method, apparatus, device, and storage medium, which can improve the scalability and operational efficiency of marketing campaigns.

[0005] In a first aspect, embodiments of this application provide an event-driven marketing campaign collaboration method, the method comprising: Receive loading trigger events for target marketing campaigns from the first front-end device via the event bus; The scheduling layer is invoked to respond to the loading trigger event and obtain the strategy configuration information of the target marketing campaign. The strategy configuration information is sent to the first front-end device, so that the first front-end device renders the target marketing activity based on the strategy configuration information, and generates and displays the activity page of the target marketing activity; The event bus receives the execution trigger event of the target marketing activity triggered by the first front-end device through the activity page; The engine layer responds to the execution trigger event to invoke the target logic component corresponding to the target marketing activity to execute the target user's execution operation for the target marketing activity, and obtains the execution result of the target user for the target marketing activity; The execution results of the target marketing campaign are returned to the first front-end device.

[0006] Optionally, before receiving the execution trigger event of the target marketing activity triggered by the first front-end device through the activity page via the event bus, the method further includes: The first front-end device receives the first entry event of the target user for the target marketing activity via the event bus. The first entry event is an event generated by the first front-end device based on the activity cycle configuration information in the strategy configuration information. The engine layer is invoked to respond to the first entry event of the activity in order to update the activity strategy information of the target logic component corresponding to the target marketing activity for the target user.

[0007] Optionally, before receiving the first entry event of the target user for the target marketing campaign sent by the first front-end device via the event bus, the method further includes: Based on the target user's information, the engine layer is invoked to perform qualification verification on the target user, and the qualification verification result of the target user is obtained. The qualification verification result is returned to the first front-end device.

[0008] Optionally, the call scheduling layer responds to the load trigger event and obtains the strategy configuration information of the target marketing campaign, including: Based on the access address of the target marketing campaign, the scheduling layer is invoked to respond to the loading trigger event, so that the scheduling layer obtains the strategy configuration information of the target marketing campaign based on the access address.

[0009] Optionally, the target logic component includes: an activity count component, an activity execution component, and an activity resource component; the invocation engine layer responds to the execution trigger event to invoke the target logic component to execute the target user's execution operation for the target marketing activity, and obtains the target user's execution result for the target marketing activity, including: The engine layer is invoked to respond to the execution trigger event, thereby calling the activity count component to verify the remaining activity counts for the target user. If the remaining activity count verification passes, the activity execution component is invoked to perform activity condition calculation. If the target user meets the activity conditions, the activity resource component is invoked to distribute the corresponding activity resources to the target user, thereby obtaining the execution result of the target user for the target marketing activity.

[0010] Optionally, the method further includes: Receive configuration trigger operations for the target marketing campaign sent by the second front-end device; Based on the configuration trigger operation, the event component is invoked to configure the event bus for events; Based on the configuration trigger operation, the activity configuration component is invoked to perform activity configuration for the target marketing activity on the target logic component.

[0011] Optionally, the method further includes: The operation is triggered according to the configuration, and the task configuration component is invoked to configure the target marketing campaign.

[0012] Secondly, embodiments of this application also provide an event-driven marketing campaign collaboration device, the device comprising: The receiving module is used to receive loading trigger events for target marketing activities sent by the first front-end device via the event bus; The calling module is used to invoke the scheduling layer to respond to the loading trigger event and obtain the strategy configuration information of the target marketing activity; The sending module is used to send the strategy configuration information to the first front-end device, so that the first front-end device renders the page of the target marketing activity based on the strategy configuration information, and generates and displays the activity page of the target marketing activity. The receiving module is further configured to receive, via the event bus, an execution trigger event of the target marketing activity triggered by the first front-end device through the activity page; The calling module is also used to call the engine layer to respond to the execution trigger event, so as to call the target logic component corresponding to the target marketing activity to execute the target user's execution operation for the target marketing activity, and obtain the execution result of the target user for the target marketing activity; The sending module is also used to return the execution result of the target marketing campaign to the first front-end device.

[0013] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a memory, and a bus, wherein the memory stores program instructions executable by the processor, and when the electronic device is running, the processor communicates with the memory via the bus, and the processor executes the program instructions to perform the steps of the event-driven marketing campaign collaboration method as described in any of the first aspects.

[0014] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the event-driven marketing campaign collaboration method as described in any of the first aspects.

[0015] This application provides an event-driven marketing campaign collaboration method, apparatus, device, and storage medium. First, it receives a loading trigger event for a target marketing campaign from a first front-end device via an event bus. Then, it calls the scheduling layer to execute the loading trigger event and obtain the strategy configuration information for the target marketing campaign. Next, it sends the strategy configuration information to the first front-end device, enabling the first front-end device to render the target marketing campaign page based on the strategy configuration information, generating and displaying the campaign page. Then, it receives an execution trigger event for the target marketing campaign triggered by the first front-end device through the campaign page via the event bus. Next, it calls the engine layer to execute the execution trigger event, invoking the target logic component corresponding to the target marketing campaign to execute the target user's operation for the target marketing campaign, obtaining the execution result. Finally, it returns the execution result of the target marketing campaign to the first front-end device. By using the method provided in this application, a complete automated collaborative process for marketing campaigns from front-end triggering to back-end execution can be achieved. Communication is based on an event bus, driving efficient collaboration between the front-end device, scheduling layer, and engine layer, enabling dynamic response in the page rendering and logic execution of marketing campaigns, significantly improving the response speed and processing efficiency of the marketing system. More importantly, by dynamically loading strategy configuration information, the execution logic of marketing campaigns and the front-end display can be separated and reused. Different campaigns can share the same components and configurations. This not only significantly improves the configuration flexibility of marketing campaigns, but more importantly, it enables marketing campaigns to maintain consistent execution logic and user experience across different times and channels. This significantly improves the automation level and collaborative efficiency of marketing campaigns, reduces manual intervention and repetitive configuration work, realizes efficient reuse and intelligent collaboration of marketing resources, and enhances the scalability and operational efficiency of marketing campaigns. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 A flowchart illustrating an event-driven marketing campaign collaboration method provided in this application embodiment; Figure 2 A flowchart illustrating the process of updating campaign strategy information in an event-driven marketing campaign collaboration method provided in this application embodiment; Figure 3 A schematic diagram illustrating the process of receiving the first event of an event in an event-driven marketing campaign collaboration method provided in this application embodiment; Figure 4 A schematic diagram illustrating the process of configuring a target marketing campaign in an event-driven marketing campaign collaboration method provided in this application embodiment; Figure 5 A schematic diagram of an event-driven marketing campaign collaboration device provided for an embodiment of this application; Figure 6 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0019] Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0020] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0021] Before providing a detailed explanation of this application, let's first introduce its application scenarios.

[0022] In actual enterprise marketing operations, various marketing activities (such as lotteries, group buying, and sign-in rewards) often involve the simultaneous display of user front-end pages, the execution of back-end business logic, and the configuration management of the operations back-end. Taking an online lottery activity as an example, after a user enters the activity page through an app or mini-program and clicks the lottery button, the system needs to verify the user's eligibility in real time, deduct lottery attempts, calculate the winning probability, distribute prizes, and simultaneously update the back-end inventory data and activity statistics reports. This process not only involves the collaborative processing of multiple links but also requires real-time linkage between the front-end display and back-end logic to avoid problems such as a user winning a prize but the prize not being distributed, or back-end data being out of sync with the user's end. However, traditional marketing activity systems often isolate the front-end page, back-end logic, and operations configuration. After the activity goes live, the data flow of each link relies on manual intervention or complex interface development, resulting in low operational efficiency, high error rates, and difficulty in meeting the enterprise's needs for rapid iteration and automated collaboration of marketing activities.

[0023] Based on this, this application provides an event-driven marketing campaign collaboration method, apparatus, device, and storage medium. First, it receives a loading trigger event for a target marketing campaign from a first front-end device via an event bus. Then, it calls the scheduling layer to execute the loading trigger event and obtain the strategy configuration information for the target marketing campaign. Next, it sends the strategy configuration information to the first front-end device, enabling the first front-end device to render the target marketing campaign page based on the strategy configuration information, generating and displaying the campaign page. Then, it receives an execution trigger event for the target marketing campaign triggered by the first front-end device through the campaign page via the event bus. Next, it calls the engine layer to execute the execution trigger event, invoking the target logic component corresponding to the target marketing campaign to execute the target user's operation for the target marketing campaign, obtaining the execution result. Finally, it returns the execution result of the target marketing campaign to the first front-end device. This significantly improves the automation level and collaboration efficiency of marketing campaigns, reduces manual intervention and repetitive configuration work, achieves efficient reuse and intelligent collaboration of marketing resources, and enhances the scalability and operational efficiency of marketing campaigns.

[0024] The following description, in conjunction with the accompanying drawings, illustrates several embodiments. The event-driven marketing campaign collaboration method provided in this application can be implemented by a computer device pre-installed with a preset event-driven marketing campaign collaboration algorithm or software, through the execution of the algorithm or software. The computer device can be, for example, a server or a terminal, and the terminal can be a user's computer.

[0025] Figure 1 A flowchart illustrating an event-driven marketing campaign collaboration method provided in this application embodiment is shown below. Figure 1 As shown, this event-driven marketing campaign collaboration method includes: S101 receives the loading trigger event for the target marketing campaign sent by the first front-end device via the event bus.

[0026] First, obtain the loading trigger event triggered by the target user through the first front-end device. The first front-end device is the front-end interaction device for the target user, including but not limited to smartphones, tablets, personal computers, and other terminal devices that can access the network and access marketing activities. The target marketing activity is a marketing activity that requires the display of the activity page and subsequent interaction. It can be any marketing activity instance configured in any business scenario, such as "opening an account for a lucky draw" in the credit business, "group buying for investment" in the wealth management business, "check-in for gifts" in the e-commerce business, or "joint marketing activities" in external businesses.

[0027] It should be noted that this application adopts a layered architecture design, which includes, from top to bottom, a business layer, a gateway layer, a scheduling layer, an engine layer, a basic capability layer, and a data storage layer. The business layer serves as a unified external entry point, connecting to various front-end business scenarios, such as credit business, wealth management business, e-commerce business, and external businesses. The gateway layer deploys gateways, integrating functions such as routing, rate limiting, permission verification, request filtering, and log collection, performing pre-processing on all incoming requests. The scheduling layer, located above the engine layer, is responsible for handling loading events from the event bus and coordinating the dynamic configuration center and data storage layer to complete the acquisition and assembly of strategy configuration information. The engine layer is responsible for the execution of specific business logic, including activity flow, prize management, and rule calculation. The basic capability layer (such as the rule engine, message center, and indicator system) and the data storage layer (such as the prize system, user profile, process engine, and dynamic configuration center) provide basic capabilities and data support for the upper layers. The dynamic configuration center stores structured strategy configuration information for various marketing activities, supporting multi-version management and dynamic activation.

[0028] As the central hub for event communication between layers and with front-end devices, the event bus is located after the gateway layer. It is responsible for uniformly receiving, routing, and distributing various events from the business layer, and routing them to the scheduling layer or engine layer for appropriate processing according to the event type.

[0029] Specifically, when a target user accesses the entry link of a target marketing campaign or scans the campaign's QR code through a first-end device, the first-end device detects the user's access operation and generates a loading trigger event. This event first passes through the gateway layer for request filtering, permission verification, rate limiting, and routing. After the gateway verification is successful, the event passes through the cluster registry center for service node matching and basic configuration verification by the dynamic configuration center, and is finally transmitted to the event bus. The cluster registry center is responsible for the automatic registration, discovery, and detection of services at each layer, ensuring that the event can be accurately routed to available service nodes. The dynamic configuration center verifies the validity of the basic configuration related to the event. The backend receives this loading trigger event through the event bus. This loading trigger event represents the target user's intent to load and view the target marketing campaign.

[0030] In practice, the loading trigger event carries relevant information for identifying the target marketing campaign and target users, such as the campaign identifier and the user identifier, so that subsequent processing can accurately locate the corresponding campaign instance and user context. Front-end devices in each business scenario only need to interact with the event bus according to a unified event format, without needing to be aware of the differentiated processing logic of the back-end, thus laying the foundation for cross-business line marketing campaign management and collaborative execution.

[0031] S102, invoke the scheduling layer to respond to the loading trigger event and obtain the strategy configuration information of the target marketing campaign.

[0032] Upon receiving a load trigger event, based on the activity identifier, business line identifier, and other information carried in the event, service discovery and node matching are completed through the cluster registry center, and the event is routed to the corresponding processing module in the scheduling layer. The strategy configuration information is the configuration data corresponding to the target marketing campaign. It is the data used to implement the front-end display and business logic execution of the target marketing campaign, and is pre-configured and stored in a specified storage location, uniquely corresponding to the target marketing campaign.

[0033] Specifically, the scheduling layer parses the loading trigger event and extracts the activity identifier of the target marketing campaign. Based on the activity identifier, the scheduling layer initiates a strategy configuration information query request to the dynamic configuration center. The dynamic configuration center stores structured strategy configuration information for each marketing campaign, such as the layout configuration of the campaign page, the configuration of displayed components (e.g., prize components, task components), the configuration of campaign rules (e.g., participation conditions, prize draw distribution rules), and the configuration of winning rules (e.g., winning rate, prize distribution method). In one possible implementation, the strategy configuration information is stored in JSON format in the distributed cache database of the dynamic configuration center.

[0034] In practice, after the scheduling layer obtains the complete policy configuration information, it either temporarily stores it via the event bus or prepares to send it directly to the front-end device. By calling the scheduling layer to uniformly process the loading trigger event and obtain the policy configuration information, the front-end loading request and the back-end policy storage are decoupled. The front-end device does not need to be aware of the storage location, assembly logic, and personalized adaptation process of the policy configuration information; it only needs to initiate a loading request through the event bus to obtain the standardized policy configuration result.

[0035] S103, send strategy configuration information to the first front-end device, so that the first front-end device renders the target marketing activity page based on the strategy configuration information, and generates and displays the activity page of the target marketing activity.

[0036] The policy configuration information returned by the scheduling layer is routed back to the first front-end device. After receiving the policy configuration information, the first front-end device parses it and constructs the user interface of the activity page based on the parsing result.

[0037] Specifically, the strategy configuration information includes a page description of the target marketing campaign, such as the page layout structure, the types of components referenced and their configuration parameters, the style attributes of the components, and the event linkage relationships between components. After reading this information, the first front-end device renders the corresponding component instances on the page according to the configuration requirements. Taking a nine-square grid lottery campaign as an example, if the strategy configuration information specifies that the campaign page must include a nine-square grid lottery component, a prize display component, a task progress component, and a user's remaining attempts component, the rendering engine will render the nine-square grid lottery wheel, prize list, task progress bar, and remaining attempts prompt on the page in the configured order and style requirements, and bind each component to the corresponding data source and event logic.

[0038] In practice, the lifecycle behavior of the page can also be determined based on the activity cycle configuration in the strategy configuration information. For example, if the strategy configuration information defines that the activity is open during specific time periods each day, the rendering engine will display a prompt page indicating that the activity has not started during the non-open periods, and automatically switch to the participateable state during the open periods.

[0039] Once rendering is complete, the first front-end device displays the target marketing campaign's activity page on its display interface, allowing target users to see a complete activity interface containing information such as activity rules, prize details, and participation entry points.

[0040] S104 receives the execution trigger event of the target marketing activity triggered by the first front-end device through the activity page via the event bus.

[0041] Target users browse activity content and interact with it on the activity page, such as clicking the "Draw Now" button in the nine-square lottery wheel, clicking the "Participate in Group Buying" button in the group buying activity, or clicking the "Check In Now" button in the check-in task. When users perform such actions to participate in the activity or perform key steps of the activity, the first front-end device detects the user's interaction behavior and generates a corresponding execution trigger event.

[0042] The execution trigger event represents a target user's request to perform specific business operations on a target marketing campaign. The first front-end device sends the execution trigger event to the gateway layer, where it undergoes request filtering, permission verification, rate limiting verification, and routing forwarding. After the cluster registry center completes service node matching and basic configuration verification with the dynamic configuration center, the event is finally transmitted to the event bus, which then uniformly receives the execution trigger event.

[0043] In one possible implementation, the execution trigger event carries not only the activity identifier and user identifier, but also a specific operation type identifier and the context parameters required for the operation. The operation type identifier is used to distinguish different business operations, while the context parameters vary depending on the operation type. For example, a lottery operation may carry the number of lottery attempts or lottery channel information, a group buying operation may carry the group buying user identifier or group leader identifier, and a task operation may carry the task identifier or completion progress information.

[0044] S105, invoke the engine layer to respond to the execution trigger event, so as to invoke the target logic component corresponding to the target marketing activity to execute the target user's execution operation for the target marketing activity, and obtain the execution result of the target user for the target marketing activity.

[0045] The engine layer can specifically include modules such as activity flow, prize management, resource management, indicator management, rule engine, component management, task management, and strategy management. After receiving an execution trigger event, the engine layer parses it and determines the target logical component to be called from the component management module based on the activity identifier, operation type identifier, and business line identifier carried in the event.

[0046] The target logic component is a pre-encapsulated component that implements specific marketing business functions, such as a lottery logic component, a group buying logic component, a task completion component, a check-in component, etc. Each logic component encapsulates the algorithm and process of the corresponding business scenario. For example, the lottery logic component encapsulates logic such as probability calculation, inventory deduction, and prize distribution.

[0047] The engine layer calls the target logic component, which then executes specific actions for the target user in relation to the target marketing campaign. During component execution, it may need to interact with the underlying capability layer (such as the rule engine, message center, and metrics system) or the data storage layer (such as the prize system and user profiles) to complete complex business logic. Specifically, the rule engine calculates business rules; the message center handles internal and external message notifications; the metrics system collects data and monitors business metrics; the prize system manages prize-related data such as prize information, inventory quantities, and distribution records; and user profiles store user-dimensional information such as user tags and historical participation data, providing user characteristic data for operations. For example, when the lottery logic component executes, it calls the rule engine to verify if the user meets the winning conditions, calls the prize system to deduct prize inventory, and calls the message center to send a winning notification.

[0048] After the target logic component completes execution, it generates the execution results for the target user's target marketing campaign. The execution results reflect the success or failure of the user's operation and the specific output of the operation. For example, for a lottery operation, the execution result may include "won" or "did not win". If the user won, it may also include specific information about the prize (prize name, prize type, redemption method, etc.). For a group purchase operation, the execution result may include "group successfully formed" or "pending group formation". If the group is successfully formed, it may also include information about the benefits after the group is formed.

[0049] S106, return the execution results of the target marketing campaign to the first front-end device.

[0050] The engine layer returns the execution result to the event bus, which then routes the result back to the first front-end device. Upon receiving the result, the first front-end device parses it and displays real-time feedback to the target user on the activity page.

[0051] Specifically, if the result is a winning lottery, the front-end device will pop up a winning notification box on the page, displaying the image and name of the winning prize, and guiding the user to redeem the prize; if the result is a losing lottery, the front-end device will display "Thank you for participating" on the page, and may update the user's remaining lottery attempts; if the result is a successful group purchase, the front-end device will refresh the group purchase status, displaying a "Group completed" notification and an entry point for claiming subsequent benefits to the user.

[0052] By returning the execution results to the first front-end device and receiving real-time feedback from the front-end device, target users can instantly know the results of their operations and obtain a smooth interactive experience, forming a complete closed loop in the execution process of the entire marketing campaign.

[0053] In this embodiment, a complete automated collaborative process for marketing campaigns, from front-end triggering to back-end execution, can be achieved. Communication is based on an event bus, enabling efficient collaboration between front-end devices, the scheduling layer, and the engine layer. This allows for dynamic responses in page rendering and logic execution of marketing campaigns, significantly improving the response speed and processing efficiency of the marketing system. More importantly, through the dynamic loading of strategy configuration information, the execution logic of marketing campaigns and front-end display are separated and reused. Different campaigns can share the same components and configurations. This not only significantly improves the configuration flexibility of marketing campaigns but, more importantly, ensures that marketing campaigns maintain consistent execution logic and user experience across different times and channels. This significantly improves the automation level and collaborative efficiency of marketing campaigns, reduces manual intervention and repetitive configuration work, achieves efficient reuse and intelligent collaboration of marketing resources, and enhances the scalability and operational efficiency of marketing campaigns.

[0054] In the above Figure 1 Based on the corresponding embodiments, in order to more clearly demonstrate the process of updating activity strategy information, this application also provides a possible implementation of updating activity strategy information in an event-driven marketing activity collaboration method. Figure 2 This is a flowchart illustrating the process of updating activity strategy information in an event-driven marketing campaign collaboration method provided in an embodiment of this application. Figure 2 As shown, before receiving the execution trigger event of the target marketing activity triggered by the first front-end device through the activity page via the event bus in S104 above, the method further includes: S210 receives the first entry event of the target user for the target marketing campaign sent by the first front-end device via the event bus.

[0055] Among them, the first entry event of the activity is an event generated by the first front-end device based on the activity cycle configuration information in the policy configuration information.

[0056] Here, the strategy configuration information includes pre-configured activity cycle configuration information. This activity cycle configuration information is pre-configured through enterprise-side operations and stored in a dynamic configuration center. It defines the full lifecycle operation rules of the target marketing activity, the boundaries of user participation cycles, and the triggering rules for first-entry behavior. It serves as the basis for the first-front-end device to generate the activity's first-entry event. The activity cycle configuration information may include, but is not limited to: the overall effective start and end time of the target marketing activity, daily activity opening hours, user participation cycle reset rules, user first-entry determination rules, the maximum number of user participations within a single cycle, the cycle distribution rules for activity benefits, and the expiration rules for activity participation opportunities—configurations strongly related to the marketing activity's time cycle. The activity's first-entry event is an event command automatically generated by the first-front-end device after determining the user's first-entry behavior based on the activity cycle configuration information when a target user enters the rendered activity page of the target marketing activity. This event triggers the backend to process the target user's activity strategy information.

[0057] Specifically, after the first front-end device completes the rendering of the activity page for the target marketing campaign, it determines the access behavior of the target user based on the activity period configuration information in the acquired strategy configuration information: First, based on the overall start and end time of the activity and the open time period rules, it confirms that the current time is within the effective running period of the activity; then, based on the user first entry determination rules preset in the activity period configuration information, it verifies whether the target user is entering the activity page of the target marketing campaign for the first time in the current effective period; if it is determined to be the first entry in the current period, the first front-end device automatically generates the corresponding first entry event for the target user and the target marketing campaign. After the gateway layer completes request filtering, permission verification and routing forwarding, the cluster registration center completes service node matching and the dynamic configuration center completes basic configuration verification, and then it is transmitted to the event bus. The back-end completes the reception of the first entry event for the activity through the event bus.

[0058] S220, invokes the engine layer to respond to the first entry event of the activity to update the activity strategy information of the target logic component corresponding to the target marketing activity for the target user.

[0059] First, it's important to clarify that activity strategy information refers to personalized strategy data specific to the target user, which the target logic component relies on when executing specific business operations. This differs from the global strategy configuration information obtained in S102. Activity strategy information corresponds to a single user's status data and personalized rules within a specific activity, such as the user's remaining participation count in the current activity period, the user's completed task progress, the user's unique winning probability coefficient, and the temporary benefits the user has already obtained. This information is stored in the user profile within the data storage layer.

[0060] Specifically, upon receiving the first entry event of an activity via the event bus, the cluster registry center matches service nodes based on the target marketing activity identifier, target user identifier, and business line identifier carried in the event. This triggers a call to the engine layer, which then parses and processes the first entry event. Based on the parsed identifier information, the engine layer retrieves the target logic component corresponding to the target marketing activity from the component management module. Simultaneously, it obtains the basic strategy template for the activity from the dynamic configuration center. Combining this with the target user's profile, historical participation data, and other information, the engine executes the preset first entry strategy rules in the activity cycle configuration information through the rule engine. This initializes and updates the activity strategy information for the target user in the target logic component, including but not limited to configuring the number of participations within the current activity cycle, initializing the user's task progress, and binding rules for distributing exclusive user benefits. The updated activity strategy information is then synchronized to the data storage layer for caching.

[0061] In this embodiment, the activity first-entry event mechanism can automatically trigger dynamic adjustments to the activity strategy information when a user enters the activity page for the first time, ensuring that the user's state and the activity rules are always consistent, avoiding logical execution errors caused by uninitialized state, and realizing refined strategy management for different users and different time dimensions, which significantly improves the user experience and the accuracy of activity execution.

[0062] In the above Figure 2 Based on the corresponding embodiments, in order to more clearly demonstrate the process of receiving the first entry event of an activity, this application also provides a possible implementation of receiving the first entry event of an activity in an event-driven marketing activity collaboration method. Figure 3 This is a schematic diagram illustrating the process of receiving the first event in an event-driven marketing campaign collaboration method provided in an embodiment of this application. Figure 3 As shown, before receiving the first entry event of the target user for the target marketing campaign sent by the first front-end device via the event bus in S210 above, the method further includes: S310: Based on the target user's information, call the engine layer to perform qualification verification on the target user and obtain the qualification verification result of the target user.

[0063] Specifically, before the first front-end device generates the first entry event of the activity, an eligibility verification request is generated based on the user identifier of the target user and the activity identifier of the target marketing activity. This request first passes through the gateway layer for request filtering, permission verification, rate limiting verification, and routing forwarding. After the gateway verification is successful, the cluster registry center completes service node matching and basic configuration verification with the dynamic configuration center, and finally transmits the request to the event bus. The event bus routes the request to the engine layer for processing based on the request type.

[0064] After receiving the eligibility verification request, the engine layer parses it and, based on the target user information and target marketing activity identifier carried in the request, calls the rule engine, loads the preset participation eligibility rules for the target marketing activity in the dynamic configuration center, and performs multi-dimensional verification of the target user in conjunction with the user profile. The verification content may include, but is not limited to: verifying whether the target user meets the participation conditions set by the activity (such as user level, user tags, historical behavior, etc.), verifying whether the target user has reached the participation limit in the current activity period, and verifying whether the business line to which the target user belongs has the right to participate in the activity, etc.

[0065] After the qualification verification is completed, the engine layer generates a qualification verification result, which may include "verification passed" or "verification failed". If the verification fails, it may also include the reason code and prompt information for the failure. The engine layer returns the qualification verification result to the event bus.

[0066] S320 returns the qualification verification result to the first front-end device.

[0067] Specifically, the engine layer transmits the generated qualification verification result to the event bus, which then forwards the result to the first front-end device that initiated the verification request via the gateway layer according to preset routing rules. After receiving and parsing the qualification verification result, the first front-end device will perform the corresponding operation based on the result. If the verification passes, it will continue to determine the user's first entry behavior and generate an activity first entry event; if the verification fails, it will display the corresponding no participation qualification prompt on the activity page.

[0068] In this embodiment, by performing pre-qualification verification before the first entry event of the activity is triggered, subsequent operations of unqualified users can be intercepted during the user's first entry, thus avoiding invalid initialization of activity strategy information, reducing backend resource consumption, and ensuring the implementation of marketing activity participation rules.

[0069] Optionally, in the above Figure 1 Based on the corresponding embodiment, in step S102 above, the scheduling layer responds to the loading trigger event and obtains the strategy configuration information for the target marketing activity, including: S410, based on the access address of the target marketing campaign, calls the scheduling layer to respond to the loading trigger event, so that the scheduling layer can obtain the strategy configuration information of the target marketing campaign based on the access address.

[0070] The access address for a target marketing campaign is the network address used by the target user when accessing the campaign, and it is bound to the target marketing campaign individually.

[0071] Specifically, the loading trigger event carries the activity access address accessed by the target user. Upon receiving this event, a call to the scheduling layer is directly triggered based on this access address. The scheduling layer first verifies the validity of the access address to check if it is a configured and legitimate marketing activity access address. If the address verification is valid, the scheduling layer further parses the activity feature information in the address and searches in the dynamic configuration center based on this information to directly match and obtain the strategy configuration information of the target marketing activity uniquely corresponding to the access address. If the address verification is invalid, such as the address not existing, the address being invalid, or the address not matching the business line, the scheduling layer determines that it cannot obtain valid strategy configuration information, triggers a 404 page display instruction, and no longer executes subsequent configuration information retrieval operations.

[0072] In this embodiment, policy configuration information is obtained based on the access address, and the 404 error scenario is triggered through address validity pre-check, which avoids invalid configuration retrieval consuming resources, while ensuring timely feedback of front-end access errors and guaranteeing the integrity and rationality of the marketing activity access link.

[0073] In the above Figure 1 Based on the corresponding embodiments, the target logic component may optionally include: an activity count component, an activity execution component, and an activity resource component.

[0074] The activity count component manages the logic of how many times a user can participate in an activity, including querying, deducting, and verifying the remaining counts; the activity execution component calculates and determines the conditions for executing an activity, such as calculating the probability of a lottery or determining the conditions for forming a group in a group-buying activity; and the activity resource component manages the logic of distributing activity resources, including the distribution of prizes, the granting of benefits, and the issuance of coupons.

[0075] Based on this, in step S105 above, the engine layer responds to the execution trigger event, thereby invoking the target logic component corresponding to the target marketing activity to execute the target user's operation on the target marketing activity. The execution result of the target user on the target marketing activity includes: S510 calls the engine layer to respond to the trigger event, calls the activity count component to check the remaining activity counts for the target user. If the remaining activity counts check passes, the activity execution component is called to calculate the activity conditions. If the target user meets the activity conditions, the activity resource component is called to distribute the corresponding activity resources to the target user, and the execution result of the target user for the target marketing activity is obtained.

[0076] Specifically, after the engine layer parses and executes the triggered event, it first calls the activity count component. This component retrieves the remaining participation count data of the target user within the current activity period from the data storage layer and performs a verification of the remaining activity count based on the activity period configuration information. If the verification passes, the engine layer immediately calls the activity execution component. This component loads the preset activity participation conditions in the rule engine and performs multi-dimensional condition calculations and judgments based on the target user's user profile, business-related data, etc. If it is determined that the target user meets the activity conditions, the engine layer further calls the activity resource component. This component connects to the prize system and resource management module to complete the activity resource inventory verification. After the verification passes, the corresponding activity resources are distributed to the target user, and the resource distribution records and user rights data are updated synchronously. Finally, the processing results of each component are integrated to generate a complete execution result for the target user for the target marketing activity.

[0077] If the calculation result of the activity execution component shows that the target user does not meet the activity conditions (such as not winning the prize or not forming a group yet), the corresponding execution result (such as "Thank you for participating" or "Pending group formation") will be generated directly without calling the activity resource component.

[0078] In this embodiment, the division of labor and sequential execution of business logic are achieved through the activity count component, activity execution component, and activity resource component. Each component has a clear responsibility and can be reused independently. At the same time, the sequential triggering and condition judgment between components ensure the implementation of activity execution rules, avoid invalid resource allocation, and improve the maintainability and scalability of activity execution logic, making it easier to upgrade components or adjust rules for individual stages in the future.

[0079] In the above Figure 1 Based on the corresponding embodiments, in order to more clearly demonstrate the process of configuring target marketing campaigns, this application also provides a possible implementation of configuring target marketing campaigns in an event-driven marketing campaign collaboration method. Figure 4 This is a schematic diagram illustrating the process of configuring a target marketing campaign in an event-driven marketing campaign collaboration method provided in an embodiment of this application. Figure 4 As shown, based on the above S101-S106, the method further includes: S610 receives configuration trigger operations for the target marketing campaign sent by the second front-end device.

[0080] Among them, the second front-end device is a marketing activity configuration terminal for enterprise-side operations personnel. It is a device that enables visual configuration on the enterprise side, allowing operations personnel to complete the entire process configuration of marketing activities through drag-and-drop, check-in, parameter entry, and other methods. The configuration trigger operation is the expression of the operations personnel's intent to create or edit the target marketing activity, which may include interactive behaviors such as selecting activity templates from the template library, dragging and dropping components to the canvas, filling in configuration forms, and setting business rules.

[0081] Specifically, based on the visual orchestration engine interface of the second front-end device, the operators perform configuration operations such as page layout, component selection, and rule setting for the target marketing campaign. Each operation generates a corresponding configuration trigger operation instruction, which is transmitted to the backend after being verified by the gateway layer. The backend receives the configuration trigger operation and provides an operational basis for subsequent event configuration and activity configuration.

[0082] S620 triggers an operation based on the configuration and calls the event component to configure the event bus.

[0083] Among them, the event component is a pre-packaged marketing scenario component, which is responsible for the event bus's event rule configuration, event trigger setting, event routing management and other functions, and is the configuration core for realizing event-driven collaboration.

[0084] Specifically, when operators define the event types required for the target marketing campaign in the preset configuration interface, such as defining "lottery button click event", "group purchase success event", "task completion event", etc., the event component is triggered based on these configurations. The event component is then configured to specifically configure the event bus based on the configuration requirements, configuring the triggering and processing rules for various events such as loading, first entry, and execution required for the entire chain of the target marketing campaign. This ensures that the event bus can identify and route various events of the target marketing campaign, realizing event linkage between the front end and the back end and at all levels.

[0085] S630 triggers an operation based on the configuration, calls the activity configuration component, and performs activity configuration for the target marketing activity on the target logic component.

[0086] The activity configuration component includes functional modules such as page configuration, component configuration, rule configuration, and resource configuration; the target logic component includes functional components such as activity count, execution, and resources to implement the target marketing activity.

[0087] Specifically, operations personnel configure the target marketing campaign within the preset configuration interface. This includes selecting the activity frequency component, activity execution component, and activity resource component from the component library, and setting the required parameters for each component: configuring the daily delivery count and cumulative limit for the activity frequency component; configuring the winning rate and prize distribution method for the activity execution component; and configuring the prize type, inventory quantity, and redemption rules for the activity resource component. Based on these configurations, the system triggers operations to call the activity configuration component, which then instantiates and configures the target logic component, binding the parameters set by the operations personnel to the component and establishing the calling relationships and data flow rules between components.

[0088] After all configuration operations are completed, the activity configuration component will encapsulate the configuration results of the operations personnel in a structured manner, generate the strategy configuration information corresponding to the target marketing activity, and store it in the dynamic configuration center in JSON format. It fully describes the page display format, business rules, event flow, component instances and their parameters, and the calling relationship between components of the target marketing activity, and establishes a unique correspondence with the activity identifier for dynamic loading and execution when users access it later.

[0089] It should be noted that, in the configuration process of S610 to S630 above, this application embodiment also provides a template reuse mechanism. After the operators complete the component assembly and parameter configuration of the target marketing activity, the activity configuration component not only generates the strategy configuration information of the activity, but also saves the current configuration as a reusable activity template according to the operator's instructions. This template is a standardized encapsulation of the general structure and process of a type of marketing activity, such as a nine-square grid lottery template, a group buying activity template, a sign-in gift template, etc. Each template predefines the component set, page layout skeleton, default event flow, and configurable parameter items required for this type of activity. When it is necessary to create a similar marketing activity in the future, the operators can directly select the corresponding template from the template library and personalize the predefined parameter items in the template in the visual configuration interface, such as replacing prize images, adjusting the winning rate value, modifying the start and end time of the activity, and changing the task reward rules. The activity configuration component automatically instantiates the template into new strategy configuration information according to the template structure and the parameters filled in by the operators, generating a personalized target marketing activity that uniquely corresponds to the current configuration. This mechanism, combining template reuse with parameterized configuration, allows marketing campaigns across different business scenarios to quickly generate multiple personalized campaign instances based on the same template. For example, the credit business can create an "Account Opening Lottery" campaign based on the nine-square grid lottery template, the wealth management business can create an "Investment Lottery" campaign based on the same template, and the e-commerce business can create a "Group Buying" campaign based on the group buying activity template. This mechanism greatly improves the efficiency of creating marketing campaigns. Operations personnel do not need to configure from scratch; they only need to adjust the parameters based on the template to quickly launch new campaigns, significantly reducing the cost of repetitive development and enabling efficient reuse of marketing resources across business lines and scenarios.

[0090] In this embodiment, by receiving the configuration trigger operation of the second front-end device, the event component and the activity configuration component are called respectively to complete the configuration of the event bus and the instantiation configuration of the target logic component. This realizes the full-process visual configuration of marketing activities from event definition to component assembly, which significantly reduces the technical threshold for activity creation and improves configuration efficiency. The final generated strategy configuration information provides a data foundation for the dynamic rendering of the user-end page and the automated execution of business logic, realizing the collaborative effect of configuration reuse.

[0091] In the above Figure 6Optionally, based on the corresponding embodiments, the method further includes: S710 triggers an operation based on configuration, calls the task configuration component, and configures the target marketing campaign.

[0092] The task configuration component is responsible for the visual configuration of task types, task rules, task rewards, and the relationship between task frequency and activity frequency involved in the target marketing campaign.

[0093] Specifically, during the process of configuring activities through the second front-end device, operators can select the "Task Configuration" tab in the preset configuration interface to configure task dimensions for the target marketing activity. Configuration content may include, but is not limited to: selecting task types (such as check-in tasks, sharing tasks, inviting friends tasks, browsing tasks, etc.), setting task completion conditions (such as consecutive check-in days, number of successful shares, number of invited users, etc.), configuring task reward rules (such as receiving extra lottery chances for each completed task, issuing coupons after task completion, etc.), establishing the association between tasks and activity count components (such as calling the activity count component to increase the user's remaining counts after task completion), and setting task periodic rules (such as daily reset, weekly reset, and only one completion allowed during the activity period, etc.).

[0094] Based on the operator's configuration, the task configuration component is invoked. This component instantiates and encapsulates the configuration content, binding task-related rules and parameters to the target marketing campaign. It also establishes the calling relationships and data flow rules between the task component, the activity count component, and the activity resource component. For example, it can be configured to "when a user checks in for the first time each day, the activity count component is invoked to give the user one extra chance to win a prize, and the activity resource component is invoked to distribute check-in points to the user."

[0095] After task configuration is complete, the task configuration component encapsulates the configuration results in a structured manner and incorporates them into the strategy configuration information of the target marketing campaign, storing it in JSON format in the dynamic configuration center. The updated strategy configuration information fully describes the rule definitions of the target marketing campaign at the task level, task component instances and their parameters, the calling relationship between the task and other components, etc., establishing a unique correspondence with the campaign identifier, so that it can be dynamically loaded and executed when accessed by users later.

[0096] In this embodiment, by calling the task configuration component to configure the target marketing campaign, support for marketing campaigns with different tasks is achieved, enriching the content format of marketing campaigns and further improving the collaborative efficiency and operational flexibility of marketing campaigns.

[0097] Based on the above embodiments, the event-driven marketing campaign collaboration method provided in this application will be further explained below in conjunction with a specific application scenario.

[0098] Taking the "Nine-Square Grid Lottery" activity in the e-commerce business as an example, the target user accesses the activity entry link through the first front-end device (such as the H5 activity page in the e-commerce APP). After the first front-end device verifies the access address, it generates a loading trigger event. This event is transmitted to the event bus after being rate-limited and verified by the gateway layer, discovered by the cluster registration center service, and basic verified by the dynamic configuration center. The event bus routes it to the scheduling layer. The scheduling layer obtains the pre-configured strategy configuration information (including the nine-square grid component layout, prize list, winning rate of 80%, and rules such as 3 lottery chances given out daily) from the dynamic configuration center based on the activity identifier, and returns it to the event bus, which then sends it to the first front-end device. The first front-end device renders the nine-square grid lottery page based on the strategy configuration information and displays it to the user. At the same time, based on the activity period configuration in the strategy configuration information, it determines that the user is entering for the first time on the day and automatically generates the first entry event, which is again routed to the engine layer via the event bus. The engine layer calls the rule engine to verify the user's eligibility (such as whether the user level meets the requirements) based on the user profile. After the verification is passed, the bonus number policy is executed. The system initializes the user's remaining 3 draw attempts for the day using the activity count component and updates the cache. When the user clicks the "Draw Now" button in the grid, the first front-end device generates an execution trigger event, which is routed to the engine layer via the event bus. The engine layer calls the draw logic component from the component management module. This component first calls the activity count component to verify the user's remaining attempts (currently 3). If the verification is successful, 1 remaining attempt is deducted. Then, the activity execution component loads the rule engine to perform probability calculations. Based on an 80% winning rate and the current prize inventory, it determines that the user has won the third prize. Next, the activity resource component is called to connect with the prize system to deduct the third prize inventory and send a winning notification through the message center. Finally, an execution result containing the "winning" status and third prize information is generated. The execution result is returned to the first front-end device via the event bus. The page pops up a winning prompt box in real time, displaying the prize image and the prize redemption entry. The user gets a complete draw experience. The entire process is driven by the event bus to coordinate the scheduling layer, engine layer, and various logic components, realizing full-link automation of the marketing activity from loading and initialization to execution feedback.

[0099] The following describes an event-driven marketing campaign collaboration device and electronic device provided in this application, which are used to perform the application. The specific implementation process and technical effects are described above and will not be repeated below.

[0100] Figure 5 A schematic diagram of an event-driven marketing campaign collaboration device provided in an embodiment of this application is shown below. Figure 5 As shown, this event-driven marketing campaign collaboration device includes: The receiving module 1000 is used to receive the loading trigger event for the target marketing activity sent by the first front-end device via the event bus.

[0101] Call module 2000 to invoke the scheduling layer response to the loading trigger event and obtain the strategy configuration information of the target marketing campaign.

[0102] The sending module 3000 is used to send strategy configuration information to the first front-end device, so that the first front-end device can render the target marketing activity page based on the strategy configuration information, and generate and display the activity page of the target marketing activity.

[0103] The receiving module 1000 is also used to receive the execution trigger event of the target marketing activity triggered by the first front-end device through the activity page via the event bus.

[0104] Module 2000 is also used to call the engine layer to respond to the execution trigger event, so as to call the target logic component corresponding to the target marketing activity to execute the target user's execution operation for the target marketing activity, and obtain the execution result of the target user for the target marketing activity.

[0105] The sending module 3000 is also used to return the execution results of the target marketing campaign to the first front-end device.

[0106] Optionally, the receiving module 1000 is also configured to receive, via the event bus, the first entry event of the target user for the target marketing campaign sent by the first front-end device.

[0107] Optionally, module 2000 can also be used to invoke the engine layer to respond to the first entry event of the activity in order to update the activity strategy information of the target logic component corresponding to the target marketing activity for the target user.

[0108] Optionally, module 2000 can also be used to call the engine layer to perform qualification verification on the target user based on the target user's information, and obtain the qualification verification result of the target user.

[0109] Optionally, the sending module 3000 is also used to return the qualification verification result to the first front-end device.

[0110] Optionally, module 2000 is invoked, specifically to invoke the scheduling layer to respond to the loading trigger event based on the access address of the target marketing activity, so that the scheduling layer can obtain the strategy configuration information of the target marketing activity based on the access address.

[0111] Optionally, module 2000 is invoked, specifically for the target logic components including: activity count component, activity execution component, and activity resource component; the engine layer responds to the execution trigger event, invokes the activity count component to verify the remaining activity counts for the target user, if the remaining activity counts verification passes, invokes the activity execution component to perform activity condition calculation, if the target user meets the activity conditions, invokes the activity resource component to distribute the corresponding activity resources to the target user, and obtains the execution result of the target user for the target marketing activity.

[0112] Optionally, the receiving module 1000 is also used to receive configuration trigger operations for the target marketing campaign sent by the second front-end device.

[0113] Optionally, module 2000 is also used to, based on configuration trigger operations, call the event component to configure the event bus; based on configuration trigger operations, call the activity configuration component to configure the target logic component for the target marketing activity; and based on configuration trigger operations, call the task configuration component to configure the target marketing activity.

[0114] These modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together as a system-on-a-chip (SOC).

[0115] Figure 6 This is a schematic diagram of an electronic device provided in an embodiment of this application. The device may be a computing device or a server with computing processing capabilities.

[0116] The electronic device 10 includes a processor 11, a storage medium 12, and a bus 13. The storage medium 12 stores program instructions executable by the processor 11. When the electronic device 10 is executed, the processor 11 communicates with the storage medium 12 via the bus 13, and the processor 11 executes the program instructions to perform the above-described method embodiment. The specific implementation and technical effects are similar and will not be described in detail here.

[0117] Optionally, this application also provides a program product, such as a computer-readable storage medium, including a program that, when executed by a processor, performs the above-described method embodiments.

[0118] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0119] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0120] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0121] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0122] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A collaborative method for event-driven marketing campaigns, characterized in that, The method includes: Receive loading trigger events for target marketing campaigns from the first front-end device via the event bus; The scheduling layer is invoked to respond to the loading trigger event and obtain the strategy configuration information of the target marketing campaign. The strategy configuration information is sent to the first front-end device, so that the first front-end device renders the target marketing activity based on the strategy configuration information, and generates and displays the activity page of the target marketing activity; The event bus receives the execution trigger event of the target marketing activity triggered by the first front-end device through the activity page; The engine layer responds to the execution trigger event to invoke the target logic component corresponding to the target marketing activity to execute the target user's execution operation for the target marketing activity, and obtains the execution result of the target user for the target marketing activity; The execution results of the target marketing campaign are returned to the first front-end device.

2. The method according to claim 1, characterized in that, Before receiving the execution trigger event of the target marketing activity triggered by the first front-end device through the activity page via the event bus, the method further includes: The first front-end device receives the first entry event of the target user for the target marketing activity via the event bus. The first entry event is an event generated by the first front-end device based on the activity cycle configuration information in the strategy configuration information. The engine layer is invoked to respond to the first entry event of the activity in order to update the activity strategy information of the target logic component corresponding to the target marketing activity for the target user.

3. The method according to claim 2, characterized in that, Before receiving the first entry event of the target user for the target marketing campaign sent by the first front-end device via the event bus, the method further includes: Based on the target user's information, the engine layer is invoked to perform qualification verification on the target user, and the qualification verification result of the target user is obtained. The qualification verification result is returned to the first front-end device.

4. The method according to claim 1, characterized in that, The call scheduling layer responds to the loading trigger event and obtains the strategy configuration information of the target marketing campaign, including: Based on the access address of the target marketing campaign, the scheduling layer is invoked to respond to the loading trigger event, so that the scheduling layer obtains the strategy configuration information of the target marketing campaign based on the access address.

5. The method according to claim 1, characterized in that, The target logic component includes: an activity count component, an activity execution component, and an activity resource component; the invocation engine layer responds to the execution trigger event to invoke the target logic component to execute the target user's execution operation for the target marketing activity, and obtains the target user's execution result for the target marketing activity, including: The engine layer is invoked to respond to the execution trigger event, thereby calling the activity count component to verify the remaining activity counts for the target user. If the remaining activity count verification passes, the activity execution component is invoked to perform activity condition calculation. If the target user meets the activity conditions, the activity resource component is invoked to distribute the corresponding activity resources to the target user, thereby obtaining the execution result of the target user for the target marketing activity.

6. The method according to claim 1, characterized in that, The method further includes: Receive configuration trigger operations for the target marketing campaign sent by the second front-end device; Based on the configuration trigger operation, the event component is invoked to configure the event bus for events; Based on the configuration trigger operation, the activity configuration component is invoked to perform activity configuration for the target marketing activity on the target logic component.

7. The method according to claim 6, characterized in that, The method further includes: The operation is triggered according to the configuration, and the task configuration component is invoked to configure the target marketing campaign.

8. An event-driven marketing campaign collaboration device, characterized in that, The device includes: The receiving module is used to receive loading trigger events for target marketing activities sent by the first front-end device via the event bus; The calling module is used to invoke the scheduling layer to respond to the loading trigger event and obtain the strategy configuration information of the target marketing activity; The sending module is used to send the strategy configuration information to the first front-end device, so that the first front-end device renders the page of the target marketing activity based on the strategy configuration information, and generates and displays the activity page of the target marketing activity. The receiving module is further configured to receive, via the event bus, an execution trigger event of the target marketing activity triggered by the first front-end device through the activity page; The calling module is also used to call the engine layer to respond to the execution trigger event, so as to call the target logic component corresponding to the target marketing activity to execute the target user's execution operation for the target marketing activity, and obtain the execution result of the target user for the target marketing activity; The sending module is also used to return the execution result of the target marketing campaign to the first front-end device.

9. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus. The memory stores program instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus, and the processor executes the program instructions to perform the steps of the event-driven marketing campaign collaboration method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, performs the event-driven marketing campaign collaboration method as described in any one of claims 1-7.

Images