A modular programmed burying point configuration method, related device, equipment and storage medium

Abstract

The application discloses a modular programming method for point-in-time configuration, and belongs to the technical field of computers. The method comprises the following steps: when the system receives a point-in-time configuration request for target data, a block configuration interface containing a block configuration area and a selection area is displayed, the blocks in the interface are code modules encapsulated through a visual programming interface, a user drags a target event block from the selection area to the configuration area, the block encapsulates execution condition judgment logic and can accurately set a point-in-time trigger condition, a first action block is dragged under the target event block as a child node, the first action block encapsulates target behavior code and can obtain target data, and a second action block is dragged under the first action block, the second action block encapsulates data reporting interface code. When the condition is triggered, the system executes behaviors in sequence according to the association relationship, generates and reports target data. The method provided by the application does not need to manually write a large amount of codes, reduces maintenance cost, and improves the efficiency and accuracy of point-in-time configuration.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a modular programming method for configuring embedded points, related devices, equipment, and storage media. Background Technology

[0002] With the widespread application of user-generated content (UGC) in fields such as gaming, education, and application development, data tracking technology has become an important tool for analyzing behavioral information and optimizing product design. Currently, the mainstream data tracking technologies mainly include the following three categories: code-based tracking, visual tracking, and no (full) tracking, but all of them have certain limitations.

[0003] Code-based event tracking requires developers to manually add tracking code. While offering high flexibility and data accuracy, it demands exceptional programming skills from operators and incurs high maintenance costs. Visual event tracking utilizes visual tools to automatically generate code and retrieve data by selecting elements on a page. It boasts high standardization but suffers from a limited scope, low flexibility, and restricted coverage. Event-free (or full) tracking automatically collects data using front-end technologies. Although eliminating the need for manual code addition, it suffers from excessive useless data reporting, poor customization capabilities, large data reporting volumes, and high storage costs, making it difficult to apply effectively in complex business scenarios. Therefore, a new method is urgently needed to address these issues. Summary of the Invention

[0004] This application provides a modular programming method for configuring event tracking points, related devices, equipment, and storage media, which solves the limitations of current code-based event tracking programming, such as high requirements for programming capabilities, high maintenance costs, small scope of visible event tracking, low flexibility, large amount of useless reported data without (full) event tracking, and poor customization capabilities.

[0005] This application provides a modular programming method for configuring event tracking points, including:

[0006] In response to a request for event tracking configuration for target data, the block configuration interface is displayed. The block configuration interface includes a block configuration area and a block selection area. The block selection area contains event blocks and action blocks. Blocks are code modules encapsulated through a visual programming interface. The block configuration area supports logical associations and parameter configurations of blocks.

[0007] In response to a drag operation on the target event block in the block selection area, the target event block is displayed in the block configuration area. The target event block encapsulates a code module that executes condition judgment logic.

[0008] In response to a drag operation on the first action block in the block selection area, the first action block is associated as a child node with the target event block. The first action block encapsulates a code module that executes the target behavior.

[0009] In response to the drag operation of the second action block in the block selection area, the second action block is associated with the first action block as a child node, and the association relationship is displayed in the block configuration area. The second action block encapsulates the code module of the data reporting interface.

[0010] When the execution condition judgment logic is triggered, the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block are executed sequentially according to the association relationship, and the target data is generated and reported.

[0011] Another aspect of this application provides a modular programming-based event tracking configuration device, comprising:

[0012] The response module is used to respond to the data tracking configuration request for the target data and display the block configuration interface. The block configuration interface includes a block configuration area and a block selection area. The block selection area contains event blocks and action blocks. The blocks are code modules encapsulated through a visual programming interface. The block configuration area supports the logical association and parameter configuration of the blocks.

[0013] The response module is also used to respond to drag operations on the target event block in the block selection area, display the target event block in the block configuration area, and the target event block encapsulates a code module that executes condition judgment logic;

[0014] The response module is also used to respond to the drag operation of the first action block in the block selection area, and associate the first action block as a child node with the target event block. The first action block encapsulates the code module that executes the target behavior.

[0015] The response module is also used to respond to the drag operation of the second action block in the block selection area, associate the second action block as a child node with the first action block, display the association relationship in the block configuration area, and the second action block encapsulates the code module of the data reporting interface.

[0016] The reporting module is used to execute the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block in sequence according to the association relationship when the execution condition judgment logic is triggered, so as to generate and report the target data.

[0017] In another aspect, this application provides a computer device including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the methods described above.

[0018] Another aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the methods described above.

[0019] Another aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the methods described above.

[0020] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0021] This application provides a modular programming method for configuring event tracking. When the system receives a request to configure event tracking for target data, it displays a block configuration interface. This interface is divided into a block configuration area and a block selection area. The blocks are code modules encapsulated through a visual programming interface, greatly reducing the programming threshold and allowing operation without professional programming knowledge. Next, the user drags and drops the target event block in the block selection area to display it in the block configuration area. This target event block encapsulates the code module for executing condition judgment logic, allowing for precise setting of the trigger conditions for data tracking, which is more intuitive and flexible than traditional methods. Then, the user drags and drops the first action block, associating it as a child node with the target event block. The first action block encapsulates the code module for executing the target behavior, and when the trigger condition is met, it can execute related behaviors such as obtaining target data. Finally, the user drags and drops the second action block, as a child node, associating it with the first action block and displaying the association. The second action block encapsulates the code module for a data reporting interface, responsible for reporting the target data. When the execution condition judgment logic is triggered, the system sequentially executes the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block, generating and reporting the target data. The visual block operation method reduces the programming skills required of the event tracking operators, allowing ordinary personnel to easily configure event tracking and saving labor costs. The modular design makes the configuration process more flexible, allowing for free combination of different block modules to adjust execution conditions and behaviors according to different business needs, meeting diverse event tracking scenarios and solving the problems of limited tracking range and low flexibility in visual event tracking. Through trigger conditions and execution logic, it avoids excessive reporting of useless data in no (full) event tracking, reducing the amount of data reported and storage costs, and enabling efficient application even in complex business scenarios. Furthermore, compared to code-based event tracking, it eliminates the need to manually write large amounts of code, significantly reducing maintenance costs and improving the efficiency and accuracy of event tracking configuration. Attached Figure Description

[0022] Figures 1 to 3 A schematic diagram illustrating the method for configuring tracking points in modular programming as provided in this application, applied to a game programming scenario.

[0023] Figures 4 to 6 A schematic diagram illustrating the modular programming data entry configuration method provided in this application for implementing product sales scenarios;

[0024] Figure 7 The method for configuring event tracking points in modular programming provided in this application is illustrated in the scenario architecture diagram for implementing game programming.

[0025] Figure 8 A flowchart of the modular programming embedding configuration method provided in the embodiments of this application;

[0026] Figure 9 A schematic diagram illustrating the event tracking configuration request provided in an embodiment of this application;

[0027] Figure 10 A schematic diagram illustrating the drag-and-drop target event block provided in an embodiment of this application;

[0028] Figure 11 A schematic diagram illustrating the dragging of the first action block as provided in an embodiment of this application;

[0029] Figure 12 A schematic diagram illustrating the dragging of a second action block as provided in an embodiment of this application;

[0030] Figure 13 A schematic diagram of the object configuration for the first action block provided in an embodiment of this application;

[0031] Figure 14 A schematic diagram illustrating the data attribute configuration of the first action block provided in an embodiment of this application;

[0032] Figure 15 A schematic diagram illustrating the target value parameter attribute configuration of the first action block provided in this application embodiment;

[0033] Figure 16 A schematic diagram illustrating the variable configuration of the second action block provided in an embodiment of this application;

[0034] Figure 17 This is a configuration interface diagram of the structure provided in the embodiments of this application;

[0035] Figure 18 An interactive diagram of the data reporting process provided in the embodiments of this application;

[0036] Figure 19 A business process diagram provided for an embodiment of this application;

[0037] Figure 20 A structural diagram of the modular programming embedding configuration device provided in the embodiments of this application. Detailed Implementation

[0038] This application provides a modular programming method for configuring event tracking. By displaying a block configuration interface, users can select blocks that encapsulate different functional code modules by dragging and dropping. For example, the target event block sets the trigger conditions, the first action block executes the target behavior, and the second action block is responsible for data reporting. These actions are executed according to their relationships, thereby reducing the programming threshold for event tracking configuration, improving flexibility and accuracy, reducing useless data reporting, lowering storage and maintenance costs, and meeting the needs of diverse event tracking scenarios.

[0039] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0040] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0041] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0042] Before introducing the specific methods of this application, we will first provide an illustrative example of the application scenarios for the modular programming-based event tracking configuration in this application. It should be understood that the following application scenarios are merely illustrative and are not limited to these examples in practice.

[0043] In one possible implementation, the method provided in this application embodiment can be applied in a modular programming platform (such as Koding, Programming Cat, etc.). Figures 1 to 3 As shown, Figures 1 to 3This paper illustrates the application of the modular programming tracking configuration method provided in this application in a game programming scenario.

[0044] Modular programming allows for the configuration of event tracking points, enabling the setting of tracking points at key points in the game, such as player login, entry into specific maps, completion of quests, and interaction with NPCs. For example, the target event block can be set to a player entering a specific dungeon. The first action block collects action data such as skill usage frequency and monster kills within the dungeon, which is then reported by the second action block. This allows for understanding the player's gameplay experience, leading to adjustments in dungeon difficulty, skill strength, and other aspects of the game, ultimately optimizing the experience. Specifically:

[0045] When users develop games on a modular programming platform, they may initiate requests to configure event tracking for target data (such as player action data in specific scenarios) in order to understand the player's gaming experience. For example... Figure 1 As shown in (A), after the platform responds to the request, it displays the block configuration interface 10. This interface includes a block configuration area 101 and a block selection area 102, where the blocks are code modules encapsulated through a visual programming interface.

[0046] like Figure 1 As shown in (B) and (C), the user drags the target event block (when the player enters the game) 1021 from the block selection area 102 to the block configuration area 101. Taking the player entering a specific instance as an example, the target event block encapsulates a code module that determines whether the player has entered the instance. For example, it checks whether the player's game character has reached the instance entrance coordinates or whether a specific interactive operation for entering the instance has been triggered. In this way, the reporting conditions for the event tracking data are precisely set.

[0047] like Figure 2 As shown in (A) and (B), the user then drags the first action block (setting custom properties of the object) 1022 under the target event block 1021 as a child node. The first action block encapsulates a code module that executes the target behavior, which is to obtain the player's operation data in the instance. For example, it counts the frequency of the player's skill release, recording the number of times the player uses various skills at different times in the instance; it counts the number of monsters killed, specifying the exact number of various monsters the player eliminates in the instance. This data can reflect the player's game strategy and operating habits in the instance in detail.

[0048] like Figure 3As shown in (A) and (B), the user then drags the second action block 1023 under the first action block 1022 as a child node, and the association relationship 1024 is displayed in the block configuration area. The second action block encapsulates a code module with a data reporting interface, which reports the player operation data obtained by the first action block to a designated data storage space. In this way, the user can centrally acquire and analyze this data.

[0049] When a player enters a specific instance, the execution condition judgment logic of the target event block is triggered. At this time, the system, based on the correlation, first executes the action corresponding to the first action block that retrieves the player's operation data in the instance, and then executes the reporting action corresponding to the second action block, generating and reporting the target data. Based on this data, users can make targeted optimizations to the game, such as adjusting the instance difficulty. If players generally clear the instance easily, the system can appropriately increase the monster's health and attack power; if players fail frequently, the system can decrease the monster's difficulty. The system can also balance skill strength, adjusting skills that are used excessively or insufficiently based on their release frequency, thereby improving the player's gaming experience.

[0050] In another possible implementation, such as Figures 4 to 6 As shown, Figures 4 to 6 This paper illustrates the application of the modular programming-based event tracking configuration method provided in this application in a product marketing scenario. When a game launches a limited-time marketing campaign, such as recharge rebates or new item flash sales, event tracking configuration can be used to understand players' experiences during the campaign.

[0051] The target event building block is set up to allow players to participate in an activity. The first action building block records information such as the player's recharge amount, the type and quantity of items purchased, and the second action building block reports the data. By analyzing this data, the development team can evaluate the effectiveness of the activity and provide a reference for subsequent marketing activities, such as determining more suitable activity times and reward settings. Specifically:

[0052] The user initiates a request to configure event tracking for target data (such as data related to player participation in activities). Figure 4 As shown in (A), the modular programming platform used by the game responds to this request and displays the block configuration interface 40. This interface is divided into a block configuration area 401 and a block selection area 402, where the blocks are code modules encapsulated through a visual programming interface.

[0053] like Figure 4As shown in (B) and (C), the user drags the target event block 4021 from the block selection area to the block configuration area 101. If the marketing campaign is a limited-time recharge rebate, the target event block encapsulates a code module that determines whether a player has participated in the recharge rebate campaign. For example, it checks whether the player made a recharge during the campaign period and whether the recharge amount reached the threshold set by the campaign. Through this setting, data tracking points are accurately determined.

[0054] like Figure 5 As shown in (A) and (B), the user drags the first action block 4022 under the target event block 4021 as a child node. The first action block encapsulates a code module that executes the target behavior, which is to obtain detailed data on the player's participation in the activity. For example, it records the player's recharge amount to clarify how much money the player has invested to participate in the activity; it records the types and quantities of items purchased to understand the player's preference for different items and the quantity they need. This data can reflect the player's consumption behavior and preferences in the activity.

[0055] like Figure 6 As shown in (A) and (B), the user then drags the second action block 4023 under the first action block 4022 as a child node, and displays the association relationship 4024 in the block configuration area. The second action block encapsulates a code module with a data reporting interface, whose function is to report the player's participation data obtained by the first action block to the specified data storage space.

[0056] When a player participates in a recharge rebate activity, the execution condition judgment logic of the target event block is triggered. According to the association relationship, the system first executes the behavior corresponding to the first action block, which is to obtain the player's activity participation data, and then executes the reporting behavior corresponding to the second action block, generating and reporting the target data.

[0057] Users evaluate the effectiveness of marketing campaigns based on the reported data. If it's found that most players' recharge amounts are concentrated in a low range, it indicates that the high recharge rewards are not attractive enough. Reward settings can be adjusted, such as increasing the rebate rate for high recharges or adding rare item rewards. If the purchase quantity of a certain item is extremely low, it may be due to insufficient practicality or appeal; its attributes or appearance can be optimized. By continuously optimizing game marketing campaigns in this way, the return on investment can be improved, increasing player participation and satisfaction.

[0058] In another possible implementation, within social applications (such as instant messaging tools, short video platforms, or social networks), users can automate the collection and analysis of social behavior data through modular programming-based event tracking configuration methods, thereby optimizing product functionality and user experience. For example, a social platform might want to analyze user interactions (such as likes, comments, and shares) on the "Friends' Moments" page to optimize content recommendation algorithms and interface layout. This could include identifying frequently interacting user groups, discovering user preferences for specific types of content, or pinpointing interface lag issues.

[0059] Users initiate a request to configure event tracking for their social behaviors on a modular programming platform (such as the user backend of a social platform). After responding to the request, the platform displays a block configuration interface (including a block configuration area and a block selection area). Users configure the data tracking logic by dragging and dropping blocks, completing the event tracking deployment without writing any code.

[0060] Users drag and drop the target event block from the block selection area to the configuration area to set the trigger conditions. Taking "user enters a friend's activity page" as the target event, a logic judgment module is encapsulated. For example, the tracking can be triggered when the user stays for more than 5 seconds, or dynamically enabled based on user identity (such as a whitelisted user). Users drag the "Enter Activity Page Event Block" to the configuration area and set trigger condition parameters (such as a stay duration threshold) through a visual interface.

[0061] Drag the first action block to become a child node of the event block and configure data tracking. Select the "Record User Operation Trajectory" action block and encapsulate the logic module to implement the following functions: record specific user behaviors (such as click dynamic type, swipe direction, and dwell time) and extract dynamic metadata (such as video playback status, image tags, and content categories). Users associate the "Operation Record Action Block" with the event block and configure the data dimensions to be obtained (such as whether to record click positions) through the parameter panel.

[0062] Drag the second action block as a child node of the first action block and configure the data reporting logic. Select the "Real-time Upload to Data Analysis Backend" action block, encapsulate a standardized reporting interface, and implement the following functions: structured data integration (such as user ID, operation type, timestamp, device information), support for scheduled batch uploads, or real-time triggering of reporting when the user leaves the site. The user associates the "Data Reporting Action Block" with the action block and selects the reporting frequency through configuration options (such as "Report immediately when the page is closed").

[0063] When a user meets the event conditions (such as a dwell time of ≥5 seconds), the system will automatically execute:

[0064] First Action Block: Records behavioral data (e.g., the user scrolls to the 5th post and stays there for 8 seconds);

[0065] The second action block: encrypt the data and upload it to the cloud analysis platform (such as a standardized data package containing user ID, dynamic ID, and dwell time);

[0066] The platform generates behavioral heatmaps based on reported data to identify high-frequency interaction areas (such as the bottom comment section).

[0067] The method provided in this application enables social platforms to accurately collect and analyze behavioral data in a modular and visual manner, significantly reducing development costs and accelerating feature iteration cycles, ultimately enhancing user activity and product competitiveness.

[0068] Please see Figure 7 , Figure 7 The diagram illustrates a scenario architecture diagram of the modular programming data entry configuration method provided in this application for implementing game programming. This scenario includes a user terminal 710, a network 720, a server 730, and a database 740.

[0069] Terminal 710 includes a human-computer interaction screen, a processor, and a memory. The human-computer interaction screen displays the block configuration interface and provides a human-computer interaction interface to receive user drag-and-drop operations, etc. The processor generates interaction commands in response to the above human-computer interaction operations and sends these commands to the server. The memory stores the reported data points (target data).

[0070] The terminal 710 involved in this application includes, but is not limited to, mobile phones, tablets, laptops, desktop computers, intelligent voice interaction devices, virtual reality devices, smart home appliances, vehicle terminals, aircraft, etc.

[0071] Run client 711 on terminal 710. Taking a modular programming client as an example, client 711 is deployed on terminal 710. Client 711 can run on terminal 710 through a browser, or as a standalone application (APP) or applet, etc.

[0072] Network 720 uses standard communication technologies and / or protocols, typically the Internet, but can also be any network, including but not limited to Bluetooth, local area network (LAN), metropolitan area network (MAN), wide area network (WAN), mobile, private network, or any combination of virtual private network. In some embodiments, custom or dedicated data communication technologies may be used to replace or supplement the aforementioned data communication technologies.

[0073] Server 730 includes a processor. Server 740 in this application can be a standalone physical server, a server cluster or distributed system consisting of at least one physical server, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence (AI) platforms.

[0074] Database 740 is used to store the reported data points.

[0075] After entering the modular programming client 711 in terminal 710, the user configures the event tracking. The user initiates a data tracking configuration request for the target data, as in step S701. In response to the request, terminal 710 displays a block configuration interface, which includes a block configuration area and a block selection area. The block selection area contains event blocks and action blocks, where each block is a code module encapsulated through a visual programming interface. The block configuration area supports logical associations and parameter configurations of the blocks.

[0076] The user drags the target event block from the block selection area to the configuration area. As in step S702, the terminal 710 responds to the drag operation of the target event block in the block selection area by displaying the target event block in the block configuration area. The target event block encapsulates a code module that executes condition judgment logic.

[0077] The user drags the first action block as a child node of the target event block, as in step S703. In response to the drag operation of the first action block in the block selection area, the first action block is associated with the target event block as a child node. The first action block encapsulates a code module that performs the target behavior.

[0078] The user drags the second action block as a child node of the first action block. As in step S704, the terminal responds to the drag operation of the second action block in the block selection area, associates the second action block as a child node with the first action block, and displays the association relationship in the block configuration area. The second action block encapsulates the code module of the data reporting interface.

[0079] When a player triggers the execution condition, such as in step S705, the terminal automatically executes the behavior of the first action block and generates data. Then, it calls the second action block to complete the reporting process. The user optimizes the game difficulty or skill balance strategy based on the received data, such as adjusting the attributes of dungeon monsters or the strength parameters of skills.

[0080] The method provided in this application allows users to quickly build data acquisition logic chains through visual drag-and-drop without writing code, significantly reducing the development threshold and time cost; at the same time, it supports flexible expansion of event triggering conditions and action types to adapt to multiple scenario needs.

[0081] Please see Figure 8 , Figure 8 A flowchart illustrating a modular programming-based event tracking configuration method is provided. It should be noted that the live streaming interaction method provided in this application embodiment can be applied to a terminal, and this application embodiment does not impose any limitations. The method includes:

[0082] S810: In response to a request for event tracking configuration for target data, display the block configuration interface.

[0083] The block configuration interface includes a block configuration area and a block selection area. Blocks are code modules encapsulated through a visual programming interface.

[0084] Understandably, target data refers to the behavioral or business data to be collected (such as clicks, dwell time, and operation paths). A data tracking configuration request refers to a configuration command initiated by the user through the terminal, used to define data tracking rules. The block configuration interface is an interface integrating visual programming, containing a block configuration area (logic chain display area) and a block selection area (pre-built module library). The visual programming interface refers to the underlying technology framework (such as WebGL or React components) that encapsulates code logic into graphical blocks.

[0085] like Figure 9 As shown, Figure 9 This diagram illustrates a data entry configuration request. (For example...) Figure 9 In step (A), the user clicks the Tools Cube button 911 in the top left menu bar, and then clicks the Modular Programming button 912. Modular programming, through visual programming capabilities, can realize a variety of complex gameplay content, such as adding highly interactive designs like games, music, and videos to the map.

[0086] When the terminal receives a request for event tracking configuration for the target data, it immediately executes a response action, displaying the block configuration interface to the user, such as... Figure 9 As shown in (B) in the diagram. The block configuration interface 920 is based on the concept of visual programming, aiming to reduce the technical threshold for users to configure event tracking points.

[0087] The block configuration interface 920 includes a block configuration area 921 and a block selection area 922. The block configuration area 921 (also called the canvas) is the core area for users to build tracking logic, acting like a virtual workbench. Users can combine and arrange blocks with different functions within this area to construct tracking configuration logic that meets their needs. The block selection area 922 stores various code modules, i.e., blocks, encapsulated through a visual programming interface. These blocks encapsulate complex programming code according to different functions, transforming it into intuitive graphical modules. Users do not need to delve into the code details; they can use these blocks to complete tracking configuration through simple operations.

[0088] Building blocks are code modules encapsulated through a visual programming interface. They hide the complex underlying programming logic and present it to the user in an intuitive graphical form. Each building block represents a specific function, providing the basic components for subsequent event tracking configuration operations.

[0089] This step serves as the entry point for the entire process. Its core function is to transform complex event tracking configurations into intuitive graphical operations through a user-friendly interface that responds to requests. No manual coding is required; configuration can be completed solely through interface interaction. All functional modules (events, actions) are pre-packaged for rapid reuse.

[0090] S820, in response to a drag operation on the target event block in the block selection area, displays the target event block in the block configuration area.

[0091] The target event block encapsulates a code module containing the logic for executing conditional judgments.

[0092] Understandably, the target event block represents the trigger condition for data tracking and reporting (such as "player enters the game" or "player leaves the game"). The execution condition judgment logic is used to verify whether the trigger condition is met. The drag-and-drop operation is an interactive action where the user moves the block from the selection area to the configuration area using the mouse or touch.

[0093] Users can select a target event block by dragging and dropping it into the block configuration area. This operation is intuitive and convenient, aligning with users' habits of visual operation. The target event block encapsulates code modules for execution condition judgment logic. Its main function is to define the trigger conditions for data tracking. For example, the target event block can be set to the event of a player entering the game. When the user performs this action, the corresponding execution condition judgment logic is triggered, thereby initiating the subsequent data acquisition and reporting process. By dynamically binding event trigger logic, the timing of data acquisition can be precisely determined, ensuring that data is collected only when key events occur, improving the effectiveness and targeting of data tracking.

[0094] like Figure 10 As shown, Figure 10 This illustrates a diagram of dragging and dropping a target event block. (For example...) Figure 10 In step (A), the user clicks on event block 1012 in block selection area 1011, then displays event block list 1013. The user clicks on player 1014 in event block list 1013, displaying player event block list 1015. The user then drags the "When player enters game" target event block 1016 from player event block list 1015 to the block configuration area, as shown below. Figure 10 In (B), in the block configuration area 1017, the target event block 1016 is displayed.

[0095] S830, In response to a drag operation on the first action block in the block selection area, associate the first action block as a child node with the target event block.

[0096] The first action block encapsulates a code module that performs the target behavior.

[0097] Understandably, the first action block is used to encapsulate the logic for collecting specific behavioral data. Child node association: A logical chain (event → action) is established through parent-child relationships, representing "execute the action after the trigger condition is met." Target behavior code module: An executable function library, such as actions like data parsing, local caching, and API calls.

[0098] After the user places the target event block, the first action block is dragged out from the block selection area and associated with it as a child node. This association clarifies the logical order of operations. The first action block encapsulates the code module that executes the target behavior. When the triggering condition defined by the target event block is met, the target behavior corresponding to the first action block will be executed. For example, in the e-commerce application mentioned above, when the user enters the game and triggers the target event, the first action block can execute actions such as obtaining the coordinate information of the virtual object controlled by the user lock in the game, and the event of the user entering the game. This information will be used as part of the target data to provide a basis for subsequent analysis and decision-making.

[0099] like Figure 11 As shown, Figure 11 This diagram illustrates the dragging and dropping of the first action block. Figure 11 In step (A), the user clicks on action block 1102 in block selection area 1101, then displays action block list 1103. The user clicks on assignment 1104 in action block list 1103, explicitly assigning values ​​to action block list 1105. The user then drags the first action block 1106 of "Set Object Custom Attributes" in assignment block list 1105 to the block configuration area, as shown below. Figure 11In (B), in the block configuration area 1107, the target event block 1108 and the first action block 1106 are displayed, and the first action block 1106 is a child node of the target event block 1108.

[0100] S840, In response to a drag operation on the second action block in the block selection area, associate the second action block as a child node with the first action block, and display the association relationship in the block configuration area.

[0101] The second action block encapsulates the code module for the data reporting interface.

[0102] Understandably, the second action block encapsulates the data transmission logic (such as encryption algorithms or API call interfaces). The data reporting interface refers to a standardized data transmission channel (such as a RESTful API or WebSocket protocol). The association is used to graphically display the logical chain hierarchy (event → action 1 → action 2).

[0103] The user continues to drag and drop the second action block from the block selection area, associating it as a child node with the first action block. The relationships between them are clearly displayed in the block configuration area. The second action block encapsulates a code module for a data reporting interface. Its main responsibility is to send the data obtained after the first action block completes the target action, to a designated location, such as a server database or data analysis platform, via the data reporting interface. This completes the crucial steps from data acquisition to data transmission, ensuring that the data is stored and analyzed in a timely and accurate manner.

[0104] like Figure 12 As shown, Figure 12 A diagram illustrating the dragging of the second action block is shown. Figure 12 In step (A), the user clicks on action block 1202 in block selection area 1201, then displays action block list 1203. The user clicks on user 1204 in action block list 1203, displaying user action block list 1205. The user then drags the second action block 1206, "Report Tracking Data," from user block list 1205 to the block configuration area, as shown below. Figure 12 In (B), in the block configuration area 1207, the target event block 1208, the first action block 1209, and the second action block 1206 are displayed. The first action block 1209 is a child node of the target event block 1208, and the second action block 1206 is a child node of the first action block 1209. The relationship 1210 is formed by the target event block 1208 → the first action block 1209 → the second action block 1206.

[0105] S850. When the execution condition judgment logic is triggered, the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block are executed sequentially according to the association relationship to generate and report the target data.

[0106] Understandably, the execution condition judgment logic is used to verify whether the behavior meets the preset trigger conditions during code execution. The association relationship refers to the execution order defined based on parent and child nodes (Event → Action 1 → Action 2). Generating and reporting target data involves converting the raw data processed by the action blocks into a structured format (such as JSON) and transmitting it to the server.

[0107] When the execution condition judgment logic in the target event block is triggered, the entire event tracking configuration process enters the execution phase. The system will strictly follow the previously established relationships, sequentially executing the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block. First, the first action block performs the operation of acquiring target data, generating target data containing various key information; then, the second action block sends this target data out through its encapsulated data reporting interface, completing the data reporting process. For example, in a game application, when a player reaches a specific level and triggers a target event, the first action block acquires information such as the player's game equipment and skills at that level, and the second action block reports this information to the game operation server so that operators can analyze the player's game progress and behavior habits, thereby optimizing game content and operational strategies.

[0108] The method provided in this application embodiment realizes a simple, intuitive and efficient data tracking configuration method, which can meet the data collection and analysis needs in different application scenarios and has broad application prospects and practical value.

[0109] In an optional embodiment of the modular programming embedding configuration method provided in the above embodiments of this application, in response to a drag operation on a first action block in the block selection area, the method further includes:

[0110] In response to the attribute configuration operation of the first action block, the first action block configuration interface, which includes object configuration slot, attribute configuration slot and target value configuration slot, is displayed in the block configuration area;

[0111] The first action block is generated by receiving object selection instructions, attribute type selection instructions, and numerical input instructions through the first action block configuration interface.

[0112] Understandably, after a user drags and drops the first action block and associates it with the target event block, an attribute configuration operation is performed on that first action block. At this point, the system responds by displaying the first action block configuration interface in the block configuration area, which includes object configuration slots, attribute configuration slots, and target value configuration slots. This configuration interface is designed to allow users to flexibly parameterize the target behavior performed by the first action block to meet the data collection needs of different scenarios.

[0113] like Figure 13 As shown, Figure 13 A schematic diagram of the object configuration for the first action block is shown. (Example) Figure 13 As shown in (A), the first action block 1301 includes an object configuration slot 1302, an attribute configuration slot, and a target value configuration slot. Figure 13 As shown in (B), the user clicks on the variable block 1306 in the block selection area 1305, then the variable block list 1307 is displayed. The user clicks on the structure 1308 in the variable block list 1307, then the structure list 1309 is displayed. The user clicks on the tracking data block 1310 in the structure list 1309 and drags the tracking data block 1310 to the object configuration slot 1302, as shown. Figure 13 As shown in (C), the embedded data block 1310 is displayed in the object configuration slot of the first action block 1301 to configure the object attributes in the first action block.

[0114] like Figure 14 As shown, Figure 14 A schematic diagram illustrating the data attribute configuration of the first action block is shown. For example... Figure 14 As shown in (A), the first action block 1401 includes an object configuration slot, an attribute configuration slot 1402, and a target value configuration slot. Figure 14 As shown in (B), when the user clicks on attribute configuration slot 1402, attribute configuration list 1403 is displayed. The user then clicks on the numeric data type 1404 in attribute configuration list 1403. Figure 14 As shown in (C), the attribute configuration slot in the first action block 1401 is filled with numeric data type 1404.

[0115] like Figure 15 As shown, Figure 15 This diagram illustrates the configuration of the target value parameter attributes for the first action block. (For example...) Figure 15 As shown in (A), the first action block 1501 includes an object configuration slot, an attribute configuration slot, and a target value configuration slot 1502. Figure 15 As shown in (B), when the user clicks the target value configuration slot 1502, a virtual keyboard 1503 is displayed, and the user enters the target value 1504 using the virtual keyboard. Figure 15 As shown in (C), the target value configuration slot in the first action block 1501 is filled with a numeric data type 1504.

[0116] After receiving object selection instructions, attribute type selection instructions, and numerical input instructions through the configuration interface described above, the system generates a parameterized first action block. Thus, when the target event is triggered, the first action block will accurately acquire the target data according to the configured parameters. This parameterized data is more accurate and targeted than the unconfigured data, providing more valuable information for subsequent data analysis and business decisions.

[0117] The method provided in this application embodiment is intuitive and easy to operate in practical applications. Users can complete the parameterized configuration of the first action block simply by clicking, selecting, and inputting in the visual configuration interface, without writing complex code. This further reduces the technical threshold for event tracking configuration, improves configuration efficiency, and meets the diverse data collection needs of different business scenarios.

[0118] In an optional embodiment of the modular programming tracking configuration method provided in the above embodiments of this application, the response to the attribute configuration operation of the first action block includes:

[0119] In response to a drag operation on a variable block in the block selection area, the variable block is embedded into the object configuration slot of the first action block. The variable block encapsulates a code module with an object identifier.

[0120] In response to a click on the attribute configuration slot, a selection list containing basic data types and custom data types is displayed;

[0121] In response to a click on a target data type in the selection list, display the identifier of the selected data type in the attribute configuration slot;

[0122] In response to an input operation to the target value configuration slot, perform at least one of the following: directly input a numerical parameter, or drag and drop a variable block into the target value configuration slot.

[0123] Understandably, after dragging and dropping the first action block and associating it with the target event block, the specific implementation process for configuring the properties of the first action block is as follows:

[0124] 1. Respond to variable block drag-and-drop operations and embed object configuration slots. When a user needs to configure the object properties of the first action block, they will drag the variable block in the block selection area. The variable block encapsulates the object identifier code module (such as objectId:"user"), which is used to dynamically bind business objects (such as user, product).

[0125] 2. Clicking the attribute configuration slot displays a list of data type selections. After the user completes the object configuration, they can click the attribute configuration slot of the first action block. The system will then respond to this action, displaying a selection list containing basic data types (such as integers, strings, booleans, etc.) and custom data types.

[0126] 3. Click the target data type identifier. The user clicks the target data type from the displayed selection list. The system will then display the identifier of the selected data type in the attribute configuration slot.

[0127] When a user enters a target value in the configuration slot, there are several options available, and the system will perform at least one of the following operations:

[0128] 1) Direct input of numerical parameters: Users can directly enter numerical parameters in the target value configuration slot through input devices such as virtual keyboards.

[0129] 2) Drag and drop variable blocks into target value configuration slots: Users can also drag and drop variable blocks from the block selection area into target value configuration slots. For example, in some cases, the target value may be related to another variable. Users can drag and drop the variable block that encapsulates the target value object identifier into the target value configuration slot. In this way, when the first action block is executed, it will determine the target value based on the object information represented by the variable block.

[0130] The method provided in this application, through a series of operations, completes the attribute configuration of the first action block, generating a more parameterized first action block. When the execution condition judgment logic of the target event block is triggered, the first action block will accurately acquire target data according to the configured parameters such as object, attribute, and target value. The second action block then reports this data, thereby providing a more accurate and targeted basis for subsequent data analysis and business decisions. This configuration method is intuitive and flexible. Users do not need to write complex code; they can complete the fine-grained configuration of the first action block simply through drag-and-drop, clicking, and input operations. This further reduces the technical threshold for event tracking configuration, improves the efficiency and quality of data collection, and meets the diverse event tracking needs in different business scenarios.

[0131] In an optional embodiment of the modular programming embedding configuration method provided in the above embodiments of this application, in response to a drag operation on a second action block in the block selection area, the method further includes:

[0132] In response to a variable configuration operation on the second action block, the configuration interface for the second action block, which includes a report data selection slot, is displayed;

[0133] Associate the variable block with the second action block by dragging and dropping the configured variable block from the first action block to the report data selection slot.

[0134] It is understandable that after the drag operation of the second action block is completed, that is, after the second action block is associated with the first action block as a child node and the association relationship is displayed in the block configuration area, variable configuration operations for the second action block are also involved.

[0135] After the user completes the drag-and-drop association of the second action block, a variable configuration operation is performed on that second action block. At this time, the system responds by displaying the second action block configuration interface, which includes a data selection slot for reporting, in the block configuration area. This configuration interface is specifically designed to facilitate users in selecting the data to be reported, making the data reporting configuration process more intuitive and convenient. The configuration interface includes the following core components: Data selection slot for reporting: used to bind the data variables to be reported; Variable list panel: displays the variable blocks already configured in the first action block.

[0136] In the displayed second action block configuration interface, the user drags and drops the variable blocks already configured in the first action block to the report data selection slot. The system establishes a cross-action reference relationship, injecting the variable identifier into the code module of the second action block. Variable references are resolved through the scope chain, supporting multi-level nesting. In this way, the goal of associating the variable blocks with the second action block is achieved.

[0137] Preferably, users can rename fields or add comments to bound variables. This maps the original variable name to the reported field name, or allows users to fill in field descriptions.

[0138] like Figure 16 As shown, Figure 16 A schematic diagram of the variable configuration for the second action block is shown. (For example...) Figure 16 In (A), the second action block 1601 includes a data reporting selection slot 1602. For example... Figure 16 In step (B), the user clicks on variable block 1604 in block selection area 1603, then displays variable block list 1605. The user clicks on structure 1606 in variable block list 1605, then displays structure list 1607. The user clicks on tracking data block 1608 in structure list 1607, and drags tracking data block 1310 to object configuration slot 1602, as shown. Figure 16 As shown in (C), the embedded data block 1608 is displayed in the data selection slot of the second action block 1601 to configure the reported data in the first action block.

[0139] The method provided in this application further improves the modular programming data entry configuration process. Through intuitive visual operation, users can flexibly select the data to be reported, which improves the relevance and effectiveness of data reporting. At the same time, it reduces the difficulty of data entry configuration and meets the diverse needs of data collection and reporting in different business scenarios.

[0140] In an optional embodiment of the modular programming data entry configuration method provided in the above embodiments of this application, the variable configuration operation in response to the second action block includes:

[0141] In response to a click on the data selection slot, display a list of configured variables;

[0142] In response to the selection operation of the target variable in the variable list, the target variable is associated with the reporting interface parameter of the second action block.

[0143] Understandably, after completing the variable configuration for the second action block and displaying the configuration interface for the second action block, which includes the report data selection slot, the user clicks on the report data selection slot. At this point, the system responds by displaying a list of configured variables. The user then selects a target variable from this list. The system then associates this target variable with the report interface parameters of the second action block.

[0144] When a user clicks the data selection slot in the second action block, the system automatically pops up a panel displaying a list of configured variables. The variable list contains two types of data sources: global variables (system-predefined public data) and local variables (dynamic variables generated through attribute configuration in the first action block).

[0145] Users can perform one of the following operations in the variable list: single selection: directly click the target variable; multiple selection: hold down the Ctrl / Command key to select multiple variables; the system will highlight the selected variables and display a preview of the field type (such as "string" or "numeric") on the right.

[0146] Users drag and drop selected variables into the reporting interface parameter area. The system automatically performs the following operations: Field naming rules: Variable identifiers are used by default, but can be manually modified to business field names; Data type adaptation: Data format is automatically converted according to the reporting interface definition (e.g., date type is converted to ISO string); Interface parameter requirements are validated using JSON Schema (e.g., field required fields, enumeration value restrictions); If the variable type does not match the interface requirements (e.g., text is passed as a numeric type), a red warning icon is displayed in real time.

[0147] In practice, all these operations are completed within a visual interface, eliminating the need for users to write complex code. Clicking on data selection slots and choosing target variables is as intuitive and convenient as ordering food from a menu. This approach not only improves the accuracy and flexibility of data reporting but also lowers the technical barrier to data tracking configuration, allowing even non-technical personnel to easily configure data reporting. Furthermore, this configuration method allows for flexible selection of reported data based on different business needs, meeting the diverse requirements of social applications for behavioral data collection and analysis in various scenarios, such as analyzing user activity levels and content preferences, providing strong data support for application optimization and operation.

[0148] In summary, the method provided in this application embodiment, through intuitive operation steps, effectively associates the configured target variable with the reporting interface parameters of the second action block, further improves the instrumentation configuration process of modular programming, and enhances the efficiency and quality of data reporting.

[0149] In an optional embodiment of the modular programming instrumentation configuration method provided in the above embodiments of this application, the method further includes:

[0150] In response to configuration operations on the data structure of the tracking points, a custom structure variable is generated.

[0151] Understandably, after completing the basic event tracking configuration process—that is, responding to event tracking configuration requests for target data and performing operations such as dragging, associating, and configuring parameters of various building blocks—it also involves configuring the event tracking data structure to generate custom structure variables to meet more complex data collection needs. When a user needs a custom event tracking data structure, a configuration operation will be performed on the event tracking data structure. At this time, the system responds to this operation and enters the process of generating custom structure variables. The specific implementation process is as follows:

[0152] In data tracking scenarios, data can be organized by defining structure variables.

[0153] First, define a structure containing three nodes: "User Answer," a string representing the user's answer; "Number of Answers," an integer representing the number of times the user answered; and "Success Flag," a boolean indicating whether the answer was successful. Next, declare a structure variable and populate it with data. Assign values ​​to the structure variable; for example, assign "Number of Answers" the value 2 and "Success Flag" the value "true". Finally, report the populated structure variable as event tracking data.

[0154] The method provided in this application embodiment allows users to flexibly construct multi-dimensional data structures without manually writing complex data model definitions. Users can also directly drag and drop and reuse the structure variables to bind reporting interface parameters in other building blocks (such as reporting action building blocks), thereby realizing the ability to create complex data models from scratch. This breaks through the limitation of traditional data collection points that can only collect flat data, significantly improves data modeling efficiency, and ensures data consistency.

[0155] In an optional embodiment of the modular programming-based event tracking configuration method provided in the above embodiments of this application, in response to a configuration operation on the event tracking data structure, a custom structure variable is generated, including:

[0156] In response to dragging structural blocks in the selected area, the structure configuration interface is displayed;

[0157] The structure configuration interface receives input of structure identifiers and adds at least one field.

[0158] Configure a data type identifier and default value parameter for each field.

[0159] Understandably, in response to configuration operations on the data tracking structure, a custom structure variable is generated. The specific implementation process is as follows: Please refer to [link / reference]. Figure 17 , Figure 17 This is the configuration interface for the struct. When a user drags a struct block from the block selection area to the block configuration area, the system displays a configuration interface containing a struct identifier input box, a field list area, and a data type selection control. The user enters a custom name (e.g., UserBehavior) in the identifier input box, and the system automatically generates a unique identifier and saves it to the global variable library. Then, by clicking the "Add Field" button, a new row is generated, and the user selects a basic type (e.g., String, Number) or a nested struct (e.g., Array) in the data type selection control. <user>The system sets default values ​​for each field (numerical types support calculator controls, and date types are automatically filled with ISO format templates); after the field configuration is completed, the system verifies the validity and generates standardized structure code modules (such as JavaScript classes), and adds the structure variables to the block selection area for subsequent reference.

[0160] The method provided in this application allows users to flexibly construct multi-dimensional data structures without manually writing complex data model definitions. Users can also directly drag and drop and reuse the structure variables to bind reporting interface parameters in other blocks (such as reporting action blocks), which significantly improves data modeling efficiency and ensures data consistency.

[0161] In an optional embodiment of the modular programming-based event tracking configuration method provided in the above embodiments of this application, the response to the configuration operation of the event tracking data structure includes:

[0162] Structure identifier input box, field list area and data type selection control;

[0163] Adding fields includes:

[0164] In response to a field addition command, a new field configuration row is generated in the field list area;

[0165] In response to a click on the data type selection control of the new field configuration row, display the data type options;

[0166] In response to the data type selection operation, the identifier of the selected data type is written to the field configuration line.

[0167] Understandably, the structure identifier input box is used by users to enter the name of a custom structure. This identifier is a unique identifier for the structure, facilitating its reference and identification during subsequent data tracking configuration. The structure identifier input box provides an intuitive and easy-to-manage way to distinguish different custom structures, enhancing the readability and maintainability of the configuration. The field list area serves as the area for displaying and managing the various fields within the structure. Users can add, delete, or modify fields in this area, making it the core area for constructing the structure's specific content. The field list area centrally manages the structure's field information, allowing users to clearly see the structure's components and facilitating unified operations and adjustments to the fields. The data type selection control allows users to choose the appropriate data type for each field. It provides multiple data type options, including basic data types (such as integers, strings, booleans, etc.) and possible custom data types to meet the storage needs of different fields. The data type selection control ensures that the data type of each field conforms to actual business requirements, guaranteeing data accuracy and consistency, and laying the foundation for subsequent data processing and analysis.

[0168] When a user issues a field addition command (e.g., by clicking the "Add Field" button), the system generates a new field configuration row in the field list area. This new row contains data type selection controls and other possible configuration items, awaiting further user configuration. This step provides users with a convenient way to dynamically add fields, making the structure definition flexible. Users can expand the structure's content at any time according to actual business changes.

[0169] When a user clicks the data type selection control in the new field configuration row, the system displays a list of available data type options. This list includes predefined basic data types and possible custom data types. This step provides users with a clear selection interface, allowing them to choose the appropriate data type based on the field's actual purpose and avoiding potential errors from manually entering data types.

[0170] After a user selects a data type from the displayed options, the system writes an identifier for that data type into the field configuration row. For example, if the user selects the "Integer" type, the identifier "Integer" will be displayed in the field configuration row. This step clarifies the data type of each field, enabling the system to correctly process and store the data in that field. Furthermore, this visual approach allows users to intuitively see the results of the field's data type settings.

[0171] The method provided in this application has strong visualization and interactivity. Through reasonable component design and clear operation steps, it allows users to easily create and customize the data structure of data tracking points. It lowers the technical threshold for data tracking point configuration, improves configuration efficiency, and can adapt to diverse data collection needs in different business scenarios, providing strong support for analysis and decision-making based on data tracking points.

[0172] In an optional embodiment of the modular programming data entry configuration method provided in the above embodiments of this application, when the execution condition judgment logic is triggered, the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block are executed sequentially according to the association relationship, and the target data is generated and reported, including:

[0173] Load the logical relationships generated by the block configuration area in the virtual runtime environment;

[0174] When the execution conditions of the target event block are met, the first action block is triggered to execute the target behavior and generate intermediate data containing object attribute values.

[0175] The intermediate data is input into the second action block, and the intermediate data is converted into the target data format and reported to the server through the data reporting interface.

[0176] Understandably, loading the logical relationships generated by the block configuration area in the virtual runtime environment provides a simulated runtime space for the execution of the tracking logic. This ensures that the logical relationships between different blocks can run in an independent and controllable environment, avoiding interference with the actual system. Simultaneously, this decouples the tracking configuration logic from other parts of the actual application, improving system stability and maintainability. The logical relationships generated by the block configuration area are the core of the entire tracking operation; they define when data collection is triggered (through the target event block) and what data is collected (through the action block). Loading these logical relationships into the virtual runtime environment is like building a "stage" for the tracking operation, on which subsequent operations will proceed in an orderly manner.

[0177] The target event block encapsulates the execution condition judgment logic. Subsequent operations are only triggered when the actual behavior or system event meets this preset condition. This ensures the targeting of data collection, ensuring that data is collected only when critical events occur, thus avoiding the generation of invalid data. Once the target event is triggered, the first action block begins to execute its encapsulated target behavior. These behaviors may include obtaining information related to user operations, such as obtaining information about purchased goods in an e-commerce application or obtaining the player's character status in a game. By executing these behaviors, intermediate data containing object attribute values ​​is generated. This intermediate data is a preliminary acquisition of relevant information when the target event occurs, preparing for subsequent data reporting. This mechanism guarantees the accuracy and timeliness of data collection, accurately capturing detailed information related to the target event, and providing a rich and valuable data foundation for subsequent data analysis.

[0178] The intermediate data generated by the first action block is passed to the second action block to ensure data continuity and integrity. The second action block acts as a data "transporter," responsible for further processing and sending this data out. Through its encapsulated data reporting interface, the second action block converts the intermediate data into the target data format. This step ensures that the data can be correctly received and processed by the server; different servers may have specific requirements for data formats, such as JSON and XML. After format conversion, the data is reported to the server, ultimately realizing the data transmission process from client to server. The second action block ensures that data can be transmitted in a format acceptable to the server, enabling the server to perform data analysis and storage smoothly, which is a crucial step in realizing the value of data.

[0179] The method provided in this application constitutes a complete and rigorous data processing flow for event tracking. From logic loading, condition triggering, data generation to final format conversion and reporting, each step is closely linked, ensuring that event tracking configuration can accurately and efficiently acquire and transmit data, providing reliable data support for business analysis and product optimization based on event tracking data.

[0180] In an optional embodiment of the modular programming instrumentation configuration method provided in the above embodiments of this application, the method further includes:

[0181] Receive target data analysis requests;

[0182] Extract raw data that matches the target data from the data storage space;

[0183] The raw data is parsed and visualized to generate data analysis charts.

[0184] Understandably, after responding to a target event and completing data reporting, the system further supports data analysis and visualization functions. The specific implementation process is as follows: When a user initiates a target data analysis request through the front-end interface, the system extracts raw data from the data storage space (such as a distributed database or log service) that matches the target data defined in the event tracking configuration. The extracted raw data may contain unstructured or semi-structured data such as timestamps of actions, operation types, and associated product information. The system parses and cleans the raw data, including: data filtering (based on the field mapping relationship in the event tracking configuration (e.g., retaining only the user_id and action_type fields)), data transformation (converting timestamps to ISO format), and aggregation statistics (statistically analyzing high-frequency operation behaviors by user ID (e.g., Top 10 click counts)).

[0185] After parsing, the system generates interactive data analysis charts through a visualization engine, such as:

[0186] 1) Behavior distribution chart: Displays the frequency curve of user operations in different time periods (using a line chart from ECharts);

[0187] 2) Profile Card: Generates an attribute tag cloud based on aggregated data;

[0188] 3) Funnel Analysis Chart: Visualize the conversion path of users from browsing products to completing payment (using a Sankey chart).

[0189] Users can view detailed data through the floating boxes on the charts and can dynamically adjust the analysis dimensions through filters.

[0190] like Figure 18 As shown, Figure 18 An interactive diagram illustrating the data reporting process is provided. Modular programming software: provides a block configuration interface, supporting user-defined data reporting logic; Backend service: receives and processes data, including data storage, parsing, analysis, and visualization modules; Third-party teaching platform: displays analysis results, supporting user-defined fields and interactive chart generation.

[0191] When a player starts the game and loads the specified map, the client initializes player data (including user_id and edu_use_id) and binds the data reporting logic through the visual configuration interface. When a player completes a quiz, clears a level, or performs other target actions, a reporting event is triggered, sending structured data containing map_id, event_id, and operation details to the backend server.

[0192] After receiving the data, the backend service stores it in relational databases (such as MySQL) and time-series databases (such as InfluxDB), filtering out invalid data through validation rules. Subsequently, the system extracts key fields (such as map_id, event_id, and user_answer), cleans and transforms the raw data (such as timestamp standardization and nested data deconstruction), and generates teaching analysis indicators (such as accuracy and participation). Finally, the analysis results are synchronized to a third-party teaching platform via API. The platform renders interactive charts based on field mapping relationships (such as comparisons of answer accuracy across different maps), allowing users to view detailed data and customize dimension filtering (such as segmentation by device type or time period) via a floating window.

[0193] Editor data retrieval interface: Interface name: GetAppReportData. Request parameters are shown in Table 1; response parameters are shown in Table 2; data structure is shown in Table 3; AppDataReportItem structure is shown in Table 4.

[0194] Table 1

[0195] Parameter name type Required describe map_id uint64_t yes Map ID event_id string no Event names of tracking points start_time uint64_t yes The start point of the time interval (millisecond timestamp) end_time uint64_t yes End point of the time interval (millisecond timestamp)

[0196] Table 2

[0197] Parameter name type describe code int Status code, 0 indicates the request was successful. msg string Response Information data json string Data content

[0198] Table 3

[0199] Parameter name type describe data_list array of AppDataReportItem Data list last_data_time uint64_t Data timestamp (page turning parameter)

[0200] Table 4

[0201]

[0202]

[0203] The method provided in this application embodiment realizes a closed loop from game behavior triggering to teaching analysis through a customized data reporting process, which solves the technical pain points of poor flexibility in traditional data tracking configuration and low analysis efficiency. It is particularly suitable for the personalized data collection and visualization needs of educational games.

[0204] In an optional embodiment of the modular programming-based event tracking configuration method provided in the above embodiments of this application, before responding to the event tracking configuration request for target data, the method further includes:

[0205] Analyze the target data analysis requirements list and extract the fields to be collected;

[0206] A data tracking configuration template is generated based on the data fields to be collected. The template includes the relationship between event types, action types, and reporting parameters.

[0207] Understandably, the target data analysis requirements list describes the user's expectations for the final data analysis results, encompassing various business goals and questions. Analyzing this list allows for a deeper understanding of what information the user wants to extract from the data. Extracting the data fields to be collected from the requirements list clarifies the specific content of subsequent data collection. These fields are crucial for building the data foundation, directly impacting whether the data analysis needs can be met.

[0208] Data tracking configuration templates provide a standardized definition for tracking operations, associating data fields to be collected with event types, action types, and reporting parameters. This makes the tracking configuration process more standardized and orderly, reducing errors and inconsistencies caused by human intervention. Template generation avoids the tedious process of redefining events, actions, and reporting parameters every time tracking is configured. Developers can directly configure based on templates, greatly improving configuration efficiency, especially in large-scale data collection scenarios. Templates clearly define the relationships between event types, action types, and reporting parameters, ensuring the consistency and coherence of the collected data. For example, when a specific event is triggered, the corresponding action and reporting parameters are fixed, ensuring that the collected data accurately reflects the business logic.

[0209] Please see Figure 19 , Figure 19 The business process diagram is shown. In map game-related projects, the requesting party (such as game operation teams, educational institutions, etc.) first clarifies the data effects to be analyzed. For example, game operation teams want to understand the time players spend in different map areas and the frequency of interaction to optimize map design and game experience; educational institutions using map games for teaching want to know students' knowledge acquisition and operational habits during gameplay to adjust teaching strategies. The requesting party organizes and records these expected analytical effects, forming a requirement document. After obtaining the requesting party's requirement document, the third-party data analysis platform conducts in-depth analysis of the data effects to be analyzed. For example, to analyze the time players spend in map areas, it is necessary to determine data collection points such as the time points when players enter and leave the area; if the focus is on knowledge acquisition, it is necessary to clarify the data collection content such as in-game behaviors related to knowledge points. Based on the analysis results, the third-party data analysis platform outputs a detailed data tracking document. The document clearly specifies the data fields to be collected (such as player ID, map area ID, entry time, exit time, operation type, etc.), the events that trigger data collection (such as players entering a specific area, completing a specific task, etc.), and the relevant parameters for data reporting. Users obtain data tracking documentation from third-party data analytics platforms and carefully understand the requirements. Then, they utilize modular programming's building block tools to implement data tracking. For example, in a game development environment, users select appropriate event blocks (such as "player enters area" or "complete task" event blocks) from the block selection area, place them in the block configuration area, and configure the corresponding conditional logic according to their needs. Next, they select action blocks (such as those for obtaining the player's current location or recording timestamps) and associate them as child nodes with the corresponding event blocks, completing the data collection logic. Simultaneously, they configure action blocks for data reporting (such as blocks for sending collected data to the backend server), ensuring that the data is reported according to the specified parameters and format. After completing the data tracking configuration, users publish the map containing the data tracking functionality to the modular programming environment, making it available to map game players. Map game players open the specified map and start the game in the modular programming environment. During gameplay, when a player's actions trigger pre-set data collection events (such as entering a specific map area or performing a specific operation), the game client automatically collects relevant data according to the user-configured data tracking logic and reports the data to the backend server. For example, when a player enters a specific area on the map, the game client records data such as the player ID, entry time, and area ID, and sends this data to the backend server. The backend server receives the data reported by the player and stores it.The server employs a suitable database system (such as relational databases or NoSQL databases) to store data according to certain rules and structures, ensuring data security and retrievability. The third-party data analysis platform reads the stored data from the backend server. Then, it uses data analysis algorithms and tools to process and analyze the data. For example, it calculates the average time players spend in different map areas and statistically analyzes the frequency of specific actions. Finally, the third-party data analysis platform displays the analysis results in a visual format, such as generating bar charts, line charts, and heatmaps. Clients can intuitively view these visualizations and make data-driven decisions, such as optimizing map design or adjusting teaching plans, thereby achieving a closed loop in the entire business process.

[0210] The method provided in this application, by parsing the target data analysis requirements list, can accurately understand the business's expectations and priorities for data analysis; the operation of extracting the data fields to be collected further clarifies the specific scope of data collection; a data tracking configuration template is generated based on the data fields to be collected, associating event types, action types, and reporting parameters to form a standardized configuration pattern; the clearly defined associations between event types, action types, and reporting parameters in the template ensure the continuity of each step in the data collection process. During data reporting and processing, it can proceed according to the expected logic, ensuring the consistency and integrity of the collected data, providing a reliable data source for subsequent data analysis.

[0211] Please see Figure 20 , Figure 20 This application provides a modular programming-based event tracking device, such as... Figure 20 In (A), the embedded point configuration device 200 includes:

[0212] The response module 2001 is used to respond to the data tracking configuration request for the target data and display the block configuration interface. The block configuration interface includes a block configuration area and a block selection area. The block selection area contains event blocks and action blocks. The blocks are code modules encapsulated through a visual programming interface. The block configuration area supports the logical association and parameter configuration of the blocks.

[0213] The response module 2001 is also used to respond to the drag operation of the target event block in the block selection area, display the target event block in the block configuration area, and the target event block encapsulates a code module that executes condition judgment logic;

[0214] The response module 2001 is also used to respond to the drag operation of the first action block in the block selection area, and associate the first action block as a child node with the target event block. The first action block encapsulates a code module that executes the target behavior.

[0215] The response module 2001 is also used to respond to the drag operation of the second action block in the block selection area, associate the second action block as a child node with the first action block, display the association relationship in the block configuration area, and the second action block encapsulates the code module of the data reporting interface.

[0216] The reporting module 2002 is used to generate and report target data by sequentially executing the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block according to the association relationship when the execution condition judgment logic is triggered.

[0217] In a specific embodiment of the modular programming embedding configuration device provided in the above embodiments of this application, such as Figure 20 In section (B), the embedded point configuration device 200 further includes:

[0218] The response module 2001 is also used to respond to the attribute configuration operation of the first action block and display the first action block configuration interface, which includes object configuration slot, attribute configuration slot and target value configuration slot, in the block configuration area.

[0219] The generation module 2003 is used to receive object selection instructions, attribute type selection instructions and numerical input instructions through the first action block configuration interface, and generate parameterized first action blocks.

[0220] In a specific embodiment of the modular programming embedding configuration device provided in the above embodiments of this application,

[0221] The response module 2001 is also used to respond to the drag operation of the variable block in the block selection area by embedding the variable block into the object configuration slot of the first action block. The variable block encapsulates a code module with an object identifier.

[0222] The response module 2001 is also used to respond to click operations on the attribute configuration slot by displaying a selection list containing basic data types and custom data types;

[0223] The response module 2001 is also used to display the identifier of the selected data type in the attribute configuration slot in response to a click operation on the target data type in the selection list;

[0224] The response module 2001 is also configured to, in response to an input operation to the target value configuration slot, perform at least one of the following: directly inputting a numerical parameter, or dragging and dropping a variable block into the target value configuration slot.

[0225] In a specific embodiment of the modular programming embedding configuration device provided in the above embodiments of this application, such as Figure 20 In section (C), the embedded point configuration device 200 also includes:

[0226] The response module 2001 is also used to display the second action block configuration interface, which includes the report data selection slot, in response to the variable configuration operation of the second action block;

[0227] The association module 2004 is used to associate a variable block with a second action block by dragging and dropping a configured variable block from the first action block to the report data selection slot.

[0228] In a specific embodiment of the modular programming embedding configuration device provided in the above embodiments of this application, the response module 2001 is further configured to display a list of configured variables in response to a click operation on the reporting data selection slot;

[0229] The response module 2001 is also used to respond to the selection operation of the target variable in the variable list and associate the target variable with the reporting interface parameters of the second action block.

[0230] In a specific embodiment of the modular programming-based event tracking configuration device provided in the above embodiments of this application, the response module 2001 is further configured to generate a custom structure variable in response to the configuration operation of the event tracking data structure.

[0231] In a specific embodiment of the modular programming embedding configuration device provided in the above embodiments of this application,

[0232] The response module 2001 is also used to respond to drag operations on structural blocks in the block selection area and display the structure configuration interface;

[0233] The response module 2001 is also used to receive input operations of structure identifiers through the structure configuration interface and add at least one field;

[0234] The response module 2001 is also used to configure data type identifiers and default value parameters for each field.

[0235] In a specific embodiment of the modular programming embedding configuration device provided in the above embodiments of this application,

[0236] Response module 2001 is also used to generate a new field configuration line in the field list area in response to a field addition command;

[0237] The response module 2001 is also used to display the data type options in response to a click operation on the data type selection control of the new field configuration row;

[0238] Response module 2001 is also used to write the identifier of the selected data type to the field configuration line in response to a data type selection operation.

[0239] In a specific embodiment of the modular programming embedding configuration device provided in the above embodiments of this application, such as Figure 20 In (D), the embedding point configuration device 200 also includes:

[0240] Run Module 2005 is used to load the logical relationships generated by the block configuration area in the virtual runtime environment;

[0241] The generation module 2003 is also used to trigger the first action block to execute the target behavior and generate intermediate data containing object attribute values ​​when the execution conditions of the target event block are detected to be met.

[0242] The reporting module 2002 is also used to input intermediate data into the second action block, convert the intermediate data into the target data format through the data reporting interface, and report it to the server.

[0243] In a specific embodiment of the modular programming embedding configuration device provided in the above embodiments of this application, such as Figure 20 In (E), the embedded point configuration device 200 also includes:

[0244] Receiver module 2007 is used to receive target data analysis requests;

[0245] Extraction module 2008 is used to extract raw data that matches the target data from the data storage space;

[0246] The generation module 2003 is also used to parse and visualize raw data, generating data analysis charts.

[0247] In a specific embodiment of the modular programming embedding configuration device provided in the above embodiments of this application, such as Figure 20 In (F), the embedded point configuration device 200 also includes:

[0248] Parsing module 2009 is used to parse the target data analysis requirements list and extract the fields of the data to be collected;

[0249] The generation module 2003 is also used to generate a data tracking configuration template based on the fields of the data to be collected. The template includes the relationship between event type, action type and reporting parameters.

[0250] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0251] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0252] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, 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, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

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

[0254] 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 as a software functional unit.

[0255] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a server or terminal device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing computer programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A modular programming method for configuring event tracking points, characterized in that, include: In response to a request for event tracking configuration for target data, a block configuration interface is displayed. The block configuration interface includes a block configuration area and a block selection area. The block selection area includes event blocks and action blocks. The blocks are code modules encapsulated through a visual programming interface. The block configuration area supports logical association and parameter configuration of the blocks. In response to a drag operation on a target event block in the block selection area, the target event block is displayed in the block configuration area, and the target event block encapsulates a code module that performs condition judgment logic. In response to a drag operation on the first action block in the block selection area, the first action block is associated as a child node with the target event block, and the first action block encapsulates a code module that performs the target behavior. In response to a drag operation on the second action block in the block selection area, the second action block is associated with the first action block as a child node, and the association relationship is displayed in the block configuration area. The second action block encapsulates a code module for a data reporting interface. When the execution condition judgment logic is triggered, the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block are executed sequentially according to the association relationship to generate and report target data.

2. The embedding point configuration method as described in claim 1, characterized in that, The response to the drag operation of the first action block in the block selection area further includes: In response to the attribute configuration operation of the first action block, a first action block configuration interface including an object configuration slot, an attribute configuration slot, and a target value configuration slot is displayed in the block configuration area; The first action block is generated by receiving object selection instructions, attribute type selection instructions, and numerical input instructions through the first action block configuration interface.

3. The embedding point configuration method as described in claim 2, characterized in that, The response to the attribute configuration operation of the first action block includes: In response to a drag operation on a variable block in the block selection area, the variable block is embedded into the object configuration slot of the first action block, and the variable block encapsulates a code module with an object identifier. In response to a click on the attribute configuration slot, a selection list containing basic data types and custom data types is displayed; In response to a click operation on a target data type in the selection list, an identifier of the selected data type is displayed in the attribute configuration slot; In response to an input operation to the target value configuration slot, perform at least one of the following: directly input a numerical parameter, or drag and drop a variable block into the target value configuration slot.

4. The embedding point configuration method as described in claim 1, characterized in that, The response to the drag operation of the second action block in the block selection area further includes: In response to a variable configuration operation on the second action block, a configuration interface for the second action block, including a report data selection slot, is displayed; By dragging and dropping the configured variable block from the first action block to the report data selection slot, the variable block is associated with the second action block.

5. The embedding point configuration method as described in claim 4, characterized in that, The variable configuration operation in response to the second action block includes: In response to a click on the reported data selection slot, a list of configured variables is displayed; In response to the selection operation of the target variable in the variable list, the target variable is associated with the reporting interface parameters of the second action block.

6. The embedding point configuration method as described in claim 1, characterized in that, The method further includes: In response to configuration operations on the data structure of the embedded points, a custom structure variable is generated.

7. The embedding point configuration method as described in claim 6, characterized in that, The process of generating custom structure variables in response to configuration operations on the embedded data structure includes: In response to a drag operation on a structural block in the block selection area, the structure configuration interface is displayed; The structure configuration interface receives input of structure identifiers and adds at least one field. Configure a data type identifier and default value parameter for each field.

8. The embedding point configuration method as described in claim 6, characterized in that, The response to the configuration operation of the embedded data structure includes: In response to a field addition instruction, a new field configuration row is generated in the field list area; In response to a click on the data type selection control of the new field configuration row, the data type options are displayed; In response to the data type selection operation, the identifier of the selected data type is written to the field configuration line.

9. The embedding point configuration method as described in claim 1, characterized in that, When the execution condition judgment logic is triggered, the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block are executed sequentially according to the association relationship to generate and report target data, including: Load the logical relationships generated by the block configuration area in the virtual runtime environment; When the execution condition of the target event block is met, the first action block is triggered to execute the target behavior and generate intermediate data containing object attribute values. The intermediate data is input into the second action block, and the intermediate data is converted into the target data format and reported to the server through the data reporting interface.

10. The embedding point configuration method as described in claim 9, characterized in that, The method further includes: Receive target data analysis requests; Extract raw data that matches the target data from the data storage space; The raw data is parsed and visualized to generate data analysis charts.

11. The embedding point configuration method as described in claim 1, characterized in that, The response to the event tracking configuration request for the target data also includes: Analyze the target data analysis requirements list and extract the fields to be collected; A data tracking configuration template is generated based on the data fields to be collected. The template includes the relationship between event types, action types, and reporting parameters.

12. A modular programming-based embedding configuration device, characterized in that, include: The response module is used to respond to the data tracking configuration request for the target data and display the block configuration interface. The block configuration interface includes a block configuration area and a block selection area. The block selection area includes event blocks and action blocks. The blocks are code modules encapsulated through a visual programming interface. The block configuration area supports the logical association and parameter configuration of the blocks. The response module is also used to respond to a drag operation on a target event block in the block selection area, display the target event block in the block configuration area, and the target event block encapsulates a code module that performs condition judgment logic; The response module is also used to respond to a drag operation on the first action block in the block selection area, and associate the first action block as a child node with the target event block. The first action block encapsulates a code module that executes the target behavior. The response module is also used to respond to the drag operation of the second action block in the block selection area, associate the second action block as a child node with the first action block, display the association relationship in the block configuration area, and the second action block encapsulates the code module of the data reporting interface. The reporting module is used to, when the execution condition judgment logic is triggered, execute the target behavior corresponding to the first action block and the reporting behavior corresponding to the second action block in sequence according to the association relationship, and generate and report the target data.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the modular programming embedding configuration method according to any one of claims 1 to 11.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the modular programming embedding configuration method according to any one of claims 1 to 11.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the modular programming embedding configuration method according to any one of claims 1 to 11.

Images