Data reporting method and device, computer device, and storage medium

Abstract

The application discloses a data reporting method and device, computer equipment and a storage medium. The method comprises: analyzing an intercepted burying point event to obtain network data; determining first network data and second network data in the network data based on a first data table; generating a target task based on the second network data and storing the target task to a processing queue; executing the target task based on the monitored network request data to obtain second response data of the second network data; updating the network data based on the first response data and the second response data, and reporting the updated network data. The application stores the second network data that is not matched to the response data as the target task and stores the target task to the processing queue. After the network request is monitored, the target task in the processing queue is executed according to the monitored network request data, so that the reported network data can carry the network request data, the integrity of the network data is ensured, and the accuracy of data analysis is improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to a data reporting method, apparatus, computer equipment, and storage medium. Background Technology

[0002] Currently, during the data reporting process, the management backend configures corresponding event tracking and attributes for different elements on the client-side page. These attributes contain the data to be reported. Furthermore, the completed server-side data is stored globally. Finally, when reporting event data, the required data can be retrieved from this global storage and reported. Summary of the Invention

[0003] This application provides a data reporting method, apparatus, computer device, and storage medium.

[0004] In a first aspect, embodiments of this application provide a data reporting method, including:

[0005] The intercepted event tracking data is analyzed to obtain the network data to be reported for the event tracking data.

[0006] The first network data and the second network data in the network data are determined based on the first data table; the first network data matches the first response data in the first data table, and the second network data does not match the response data in the first data table;

[0007] The target task is generated based on the second network data and stored in the processing queue;

[0008] Based on the monitored network request data, the target task in the processing queue is executed to obtain the second response data of the second network data;

[0009] The network data is updated based on the first response data and the second response data, and the updated network data is reported.

[0010] Secondly, embodiments of this application provide a data reporting device, including:

[0011] The analysis module is used to analyze the intercepted event tracking data to obtain the network data to be reported for the event tracking data.

[0012] A matching module is used to determine first network data and second network data in the network data based on a first data table; the first network data matches the first response data in the first data table, and the second network data does not match the response data in the first data table;

[0013] The storage module is used to generate target tasks based on the second network data and store them in the processing queue;

[0014] The execution module is used to execute the target task in the processing queue based on the monitored network request data, and obtain the second response data of the second network data;

[0015] The data reporting module is used to update the network data based on the first response data and the second response data, and to report the updated network data.

[0016] Thirdly, embodiments of this application also provide a computer device, including a memory storing multiple computer programs; a processor loads the computer programs from the memory to execute any of the data reporting methods provided in embodiments of this application.

[0017] Fourthly, embodiments of this application also provide a computer-readable storage medium storing multiple computer programs adapted for loading by a processor to execute any of the data reporting methods provided in embodiments of this application.

[0018] Fifthly, embodiments of this application also provide a computer program product, including a computer program or computer program that, when executed by a processor, implements any of the data reporting methods provided in embodiments of this application.

[0019] The solution adopted in the application embodiment can determine the target task based on the second network data for which no response data was matched and store it in the processing queue. After listening to the network request, the target task in the processing queue is executed according to the listened network request data. This allows the second network data in the target task to be matched with the network request data, and the second response data of the second network data is matched from the network request data. Then, the network data is updated and reported according to the first response data and the second response data. Therefore, during the data reporting process, the reported network data can carry the network request data, ensuring the integrity of the reported network data and improving the accuracy of subsequent data analysis. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0021] Figure 1 This is a schematic diagram of the application environment for the data reporting method provided in the embodiments of this application;

[0022] Figure 2 This is a flowchart illustrating the data reporting method provided in the embodiments of this application;

[0023] Figure 3 This is a schematic diagram of the embedded data table provided in the embodiments of this application;

[0024] Figure 4 This is a schematic diagram of the first data table provided in an embodiment of this application;

[0025] Figure 5 This is a schematic diagram of the processing queue provided in an embodiment of this application;

[0026] Figure 6 This is a schematic diagram of the process for consuming the processing queue provided in an embodiment of this application;

[0027] Figure 7 This is a schematic diagram of the overall scheme flow of the data reporting method provided in the embodiments of this application;

[0028] Figure 8 This is a schematic diagram of the structure of the data reporting device provided in the embodiments of this application;

[0029] Figure 9 This is a schematic diagram of the internal structure of the computer device provided in the embodiments of this application. Detailed Implementation

[0030] 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 a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. At the same time, in the description of the embodiments of this application, the terms "first," "second," etc., are only used to distinguish descriptions and should not be construed as indicating or implying relative importance. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0031] In one embodiment of this application, the data reporting method can run on a local terminal device or a server. When the data reporting method runs on a server, the method can be implemented and executed based on a cloud interaction system, wherein the cloud interaction system includes a server and client devices.

[0032] To better understand the data reporting method, apparatus, computer equipment, and storage medium provided in the embodiments of this application, the application environment applicable to the embodiments of this application is described below.

[0033] Please see Figure 1 , Figure 1 This diagram illustrates an application environment for a data reporting method provided in an embodiment of this application. As one implementation, the data reporting method provided in this embodiment can be applied to an electronic device, wherein the electronic device can be as follows: Figure 1 The server 110 shown can be connected to the terminal device 120 via a network. The network serves as a medium for providing a communication link between the server 110 and the terminal device 120. The network can include various connection types, such as wired communication links, wireless communication links, etc., and this embodiment is not limited thereto. Optionally, in other embodiments, the electronic device can also be a smartphone, laptop, etc.

[0034] It should be understood that Figure 1 The server 110, network, and terminal device 120 shown are merely illustrative. Depending on the implementation requirements, any number of servers, networks, and terminal devices can be included. For example, server 110 can be a physical server or a server cluster consisting of multiple servers, and terminal device 120 can be a mobile phone, tablet, desktop computer, laptop computer, etc. It is understood that embodiments of this application can also allow multiple terminal devices 120 to access server 110 simultaneously.

[0035] In some embodiments, the terminal device 120 can record the user's voice to obtain the user's audio data. Further, the terminal device 120 sends the user's audio data to the server 110 via a network. After receiving the user's audio data, the server 110 can process this audio data using the data reporting method described in this application embodiment.

[0036] The following detailed description is provided in conjunction with the accompanying drawings. In this embodiment, the execution subject is a terminal device as an example. It should be noted that the order of description in the following embodiments is not intended to limit the preferred order of the embodiments. Although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be performed in a different order than that shown in the accompanying drawings.

[0037] The data reporting method in this embodiment can be applied to event tracking scenarios, which may include, for example, page access path scenarios and element click scenarios. In event tracking scenarios, it is necessary to report the data collected by the event tracking; however, current event tracking data reporting cannot include network request data.

[0038] To address the aforementioned technical issues, the inventors proposed a data reporting method based on a processing queue. Specifically, second network data that has not yet matched with response data is taken as the target task and stored in the processing queue. Upon detecting a network request, the target task in the processing queue is executed based on the detected network request data. This allows the second network data in the target task to be matched against the network request data, and the second response data of the second network data is extracted from the network request data. Then, the network data is updated and reported based on the first and second response data. This ensures that the reported network data can carry the network request data during the data reporting process, guaranteeing the integrity of the reported network data and improving the accuracy of subsequent data analysis.

[0039] In some embodiments, the terminal device 120 can respond to user operations, collect embedded events, generate a data reporting trigger request, and perform data reporting through the data reporting method of this application embodiment.

[0040] In other embodiments, the terminal device 120 can respond to user operations, collect embedded events, generate a data reporting trigger request, and then send the trigger request to the server 110 via the network. When the server 110 receives the trigger request, it can perform data reporting using the data reporting method of this application embodiment.

[0041] Definitions:

[0042] "Event tracking" is a term in the field of data collection. It is a commonly used data collection method in website analytics, mainly used to collect user behavior data for data analysis.

[0043] Visual tracking, also known as selection-based tracking, is a data tracking mechanism built upon full tracking technology. Developers do not need to add any code to the data tracking points; they only need to connect to the management backend and select the elements on the page that need tracking to add interface tracking points that take effect immediately.

[0044] Data reporting typically refers to communication between the client and the server. When a data tracking point is triggered, a data request is sent to a remote server over the network, and the data carried is then transmitted to the server.

[0045] Remote network data typically refers to data (attributes + attribute values) obtained through server-side interface requests.

[0046] An interface refers to an API (Application Programming Interface), such as a method provided by the server when a client interacts with the server via the HTTP protocol. The server implements specific functions through the API, and the caller does not need to understand its internal implementation details. An API can also be understood as a wrapper around a specific service, providing it to others for use.

[0047] refer to Figure 2 , Figure 2 This is a flowchart illustrating the data reporting method provided in this application embodiment. The specific flow of the data reporting method can be as follows: steps 10 to 50, wherein:

[0048] Step 10: Analyze the intercepted event tracking data to obtain the network data to be reported for the event tracking data.

[0049] It should be noted that when users access page paths or click on elements in the operation page of the terminal device, the terminal device will respond to the user's operation and intercept the event tracking based on the operation.

[0050] In this application embodiment, the embedded event is also the data acquisition event.

[0051] Furthermore, the terminal device analyzes the intercepted event tracking information to obtain the network data to be reported for the event tracking information, as described in steps 101 to 103. The network data is the data that the terminal device needs to send to the server, and at this time, the network data only carries attribute information.

[0052] Further, steps 101 to 103 are described as follows:

[0053] Step 101: Analyze the embedded events to obtain event identifiers;

[0054] Step 102: Match the event identifier in the event tracking data table to obtain event tracking data;

[0055] Step 103: Perform data analysis on the embedded data to obtain the network data.

[0056] It should be noted that before performing data reporting, the terminal device needs to download the corresponding event tracking data table from the server. Each item in the event tracking data table contains at least three parameters, including the event identifier (Identity Document, ID) that triggered the reporting, the event name, and the reporting attribute configuration. Each item in the event tracking data table can be understood as event tracking data.

[0057] Optionally, after the terminal device intercepts the triggered event, it analyzes the event to obtain the event element. In the web domain, the event element refers to what is displayed within the user's browser window; it can be the entire page, or a single image, text, button, or independent functional module. For example, for a page exposure event, the event element is the page itself; for a button click event, the event element is the button. The process is similar in other terminal device scenarios, and will not be elaborated further here.

[0058] Furthermore, the terminal device obtains the event identifier of the event element. Since the event identifier can uniquely identify a time, it can be matched against the event tracking data table. That is, it checks whether the event element has a matching relationship in the event tracking data table based on the event identifier. If a matching relationship is found, the terminal device obtains the tracking data for that event.

[0059] Furthermore, the terminal device performs attribute configuration analysis on the reported embedded data to check whether the embedded data is required to carry network data. In other words, it performs data analysis on the embedded data to determine whether the embedded data carries network data.

[0060] Furthermore, if it is determined that the embedded data does not contain network data, the terminal device will directly report the embedded data. If it is determined that the embedded data contains network data, the terminal device will retrieve the network data from the embedded data.

[0061] In one embodiment, reference is made to Figure 3 , Figure 3 This is a schematic diagram of the embedded data table provided in an embodiment of this application. According to... Figure 3 It can be seen that the event tracking data table includes multiple event tracking data, such as event tracking data 1, event tracking data 2, ..., event tracking data n. Each event tracking data includes an event identifier, an event name, and a reporting attribute configuration. The reporting attribute configuration includes multiple network data, namely network data 1, network data 2, ..., network data m. Network data 1 includes requestKey1 and its corresponding responseKey1-1 and responseKey1-2. Network data 2 includes requestKey2 and its corresponding responseKey2-1 and responseKey2-2. Network data m includes requestKeym and its corresponding responseKeym-1 and responseKeym-2.

[0062] Step 20: Determine the first network data and the second network data in the network data based on the first data table.

[0063] It should be noted that the embodiments of this application require pre-configuration of a first data table, which can be understood as a global network data storage object (networkCacheMap), as shown below. Figure 4 , Figure 4 This is a schematic diagram of the first data table provided in an embodiment of this application. According to... Figure 4 As can be seen, the first data table is an object Map. The first data table includes at least two attributes: the unique identifier of the API request requestKey (request data) and the specific response data returned by the API request responseKey (response data).

[0064] Optionally, this embodiment of the application also configures a processing queue (reportQueue), wherein the processing queue (reportQueue) is of type array. See reference... Figure 5 , Figure 5 This is a schematic diagram of the processing queue provided in an embodiment of this application. According to... Figure 5 It can be seen that each item in the array includes at least four attributes: the reported execution function `callblak` (corresponding information: `Function`); the timeout period `timeout` (corresponding information: `Number`); the creation time `creatAt` (corresponding information: `Number`); and the dependent remote network data `DependencyRequestList` (corresponding information: `Array`). <networkcachemap>The reporting execution function is used to execute the reporting task, and the waiting timeout time and the dependent remote network data are used to confirm whether the preconditions for allowing reporting are met during each check.

[0065] Optionally, embodiments of this application set preconditions for allowing reporting. These preconditions include the requirement that all network data required by the target task can be retrieved from the first data table `networkCacheMap` using its corresponding unique identifier `requestKey`. Alternatively, the target task in the `reportQueue` may time out.

[0066] Optionally, the terminal device matches the unique identifier requestKey of each piece of network data in the first data table networkCacheMap to determine whether it can obtain the response data responseKey of each piece of network data.

[0067] Furthermore, if it is determined that each piece of data in the network data matches the corresponding response data in the first data table networkCacheMap, the terminal device updates the network data according to the response data of each piece of data in the network data, and reports the updated network data.

[0068] Furthermore, if it is determined that some data in the network data matches the corresponding response data in the first data table networkCacheMap, while some data does not match the corresponding response data in the first data table networkCacheMap, the terminal device obtains the first network data and the second network data in the network data. The first network data matches the first response data in the first data table, while the second network data does not match the response data in the first data table.

[0069] Step 30: Generate a target task based on the second network data and store it in the processing queue.

[0070] Optionally, the terminal device generates a target task based on the request data of the second network data and stores the target task in a processing queue. Therefore, a processing queue may include multiple target tasks. Specifically, the terminal device analyzes the second network data to obtain the second request data of the second network data, which is the requestKey of the second network data.

[0071] Furthermore, the terminal device assembles the second request data and the second network data according to the data format of the processing queue to generate the target task corresponding to the second network data. That is, it assembles the reporting execution function, the second network data, and the second request data to obtain the target task of the second network data in the processing queue reportQueue.

[0072] Furthermore, the terminal device stores the target task in the processing queue reportQueue.

[0073] Therefore, in this embodiment, the second network data that does not match the response data pair is stored in the processing queue and reported after subsequent conditions are met, thus avoiding the loss of network data in the data tracking table.

[0074] Step 40: Execute the target task in the processing queue based on the monitored network request data to obtain the second response data of the second network data.

[0075] It should be noted that the terminal device in this embodiment needs to monitor network requests initiated by the terminal device to the server in real time. Network requests typically refer to API interfaces, which are mostly written by the backend and invoked by frontend developers. That is, the terminal device initiates an HTTP request to the server, and the backend returns remote resources or performs some action, such as obtaining remote resource data from the server.

[0076] Optionally, after each network request is completed, the terminal device obtains the network request data for that network request. Further, based on the network request data, the terminal device executes the target task in the processing queue to obtain the second response data of the second network data, as described in steps 401 to 403.

[0077] Step 50: Update the network data based on the first response data and the second response data, and report the updated network data.

[0078] Optionally, the terminal device updates the network data based on the first response data and the second response data. Specifically, it updates the first network data using the first response data as an attribute value and updates the second network data using the second response data as an attribute value, thus obtaining the updated network data. Further, the terminal device reports the updated network data.

[0079] In this embodiment, the second network data that does not match the response data can be used as the target task and stored in the processing queue. After a network request is detected, the target task in the processing queue is executed according to the detected network request data, that is, the second response data of the second network data is obtained from the network request data, and the network data is updated and reported according to the first response data and the second response data. Therefore, the network data reported during the data reporting process can carry the network request data.

[0080] Further, steps 401 to 403 are described as follows:

[0081] Step 401: Based on the first request data and the response data of the first request data in the network request data, update the first data table to obtain the second data table;

[0082] Step 402: Execute the target task and match the second request data in the target task with the first request data in the second data table;

[0083] Step 403: If the second request data matches the corresponding first request data in the second data table, then the response data corresponding to the matched first request data is determined as the second response data.

[0084] Optionally, the terminal device parses the network request data to obtain the first request data and the response data corresponding to the first request data.

[0085] Furthermore, the terminal device assembles the first request data and the corresponding response data according to the data format of the first data table to obtain the assembled data.

[0086] Furthermore, the terminal device stores the assembled data into the first data table, that is, it updates the first data table with the assembled data to obtain the updated second data table.

[0087] Furthermore, the terminal device executes the target task in the processing queue according to the updated second data table, and matches the second response data corresponding to the second network data. Specifically, the terminal device matches the second request data with the first request data in the second data table to determine whether there is first request data in the second data table that matches the second request data.

[0088] Furthermore, if it is determined that there is first request data in the second data table that matches the second request data, that is, the second request data matches the corresponding response data in the second data table, the terminal device will determine the response data corresponding to the matched first request data as the second response data corresponding to the second network data.

[0089] Reference Figure 6 , Figure 6 This is a schematic diagram of the processing queue consumption provided in an embodiment of this application. According to... Figure 6 It can be seen that the processing queue includes target task 1, target task 2, target task 3, ..., target task n. For target task 1, when executing target task 1, the second request data corresponding to target task 1 is obtained, and the second request data corresponding to target task 1 is matched against the second data table. If the second response data corresponding to target task 1 is matched against the second data table, then the data reporting corresponding to target task 1 is executed. The same logic applies to target task 2, target task 3, ..., target task n, which will not be elaborated here.

[0090] Furthermore, if it is determined that the second request data does not match the corresponding response data in the second data table, the terminal device will continue to match the second request data in the second data table after the next network request data to obtain the second response data corresponding to the second network data.

[0091] In this embodiment, second network data that has not been matched with response data can be used as a target task and stored in a processing queue. After a network request is detected, the target task in the processing queue is executed according to the detected network request data. This allows the second network data in the target task to be matched with the network request data, and the second response data of the second network data is matched from the network request data. Then, the network data is updated and reported according to the first and second response data. Therefore, during the data reporting process, the reported network data can carry the network request data, ensuring the integrity of the reported network data and improving the accuracy of subsequent data analysis.

[0092] Furthermore, after storing the target task in the processing queue, the process also includes:

[0093] Step 60: Determine the duration and status information of the target task stored in the processing queue;

[0094] Step 70: If the duration is greater than or equal to the duration threshold and the status information is in an incomplete state, then the network data is updated based on the first response data to obtain the third updated network data; wherein, the incomplete state is used to indicate that the target task has not been processed, that is, so that there is no response data in the second data table that matches the second network data.

[0095] Step 80: Report the third updated network data.

[0096] Optionally, the terminal device starts a timer to poll and traverse each target task in the processing queue reportQueue according to the time interval timeInterval, and obtain the duration and status information of each target task.

[0097] Furthermore, the terminal device compares the duration with a preset duration threshold, which is set according to actual conditions, such as 5 seconds, 10 seconds, etc.

[0098] Furthermore, if the duration is determined to be greater than or equal to the duration threshold and the status information is in an incomplete state, the terminal device updates the network data corresponding to each target task through the first response data corresponding to each target task. The incomplete state is used to indicate that the target task has not been processed, that is, so that there is no response data matching the second network data in the second data table.

[0099] Furthermore, the terminal device reports the updated network data for each target task.

[0100] Optional, refer to Figure 6 , Figure 6 This is a schematic diagram of the processing queue consumption provided in an embodiment of this application. According to... Figure 6 As can be seen, the processing queue includes target task 1, target task 2, target task 3, ..., target task n. Target task 1 can be obtained from the processing queue, or any target task can be obtained from the processing queue. Furthermore, if the duration of target task 1 exceeds the duration threshold, the network data corresponding to target task 1 is updated using the first response data corresponding to target task 1, and the updated network data of target task 1 is reported. The same logic applies to target tasks 2, 3, ..., n, which will not be elaborated further here.

[0101] This application embodiment uses a timer polling mechanism to ensure that the event tracking points will be reported, thus avoiding the loss of network data.

[0102] Furthermore, after reporting the updated network data, it also includes:

[0103] Step 90: Execute each target task in the processing queue based on the detected close event;

[0104] Step 100: If each target task matches the third response data in the second data table, then based on the first response data and the third response data of each target task, update the network data corresponding to each target task, and report the updated network data of each target task.

[0105] Step 110: If no third response data is matched in the second data table for each target task, then the network data corresponding to each target task is updated based on the first response data of each target task, and the updated network data of each target task is reported.

[0106] Optionally, the terminal device listens for the device's close event in real time. The close event varies depending on the terminal device. For example, on a web application, the close event refers to the page closing; in a native app, it refers to the app closing; and so on for other clients. The close event can be understood as the lifecycle of a single session. On a web application, it typically refers to the lifecycle from page opening to closing; in a native app, it typically refers to the lifecycle from app startup to shutdown.

[0107] After the terminal device detects the shutdown event, it executes each target task in the processing queue.

[0108] Furthermore, if each target task matches third response data in the second data table, the terminal device updates the network data corresponding to each target task using the first and third response data, and reports the updated network data for each target task. If each target task does not match third response data in the second data table, the terminal device updates the network data corresponding to each target task using the first response data, and reports the updated network data for each target task.

[0109] This application embodiment ensures that the event tracking will be reported by disabling the event listening mechanism, thus avoiding the loss of network data.

[0110] Furthermore, referring to Figure 7 , Figure 7 This is a schematic diagram of the overall scheme flow of the data reporting method provided in the embodiments of this application, and the specific analysis is as follows:

[0111] Step 1: Download the event tracking data table from the server. Specifically, send a request to the server to retrieve the event tracking data table and store the retrieved event tracking data table globally.

[0112] Step 2: When the terminal device intercepts the triggering of the tracking event, it checks whether the triggering element of the tracking event has a matching relationship in the tracking data table. If a matching relationship is found, the tracking data is read, and it is checked whether the tracking data is required to carry network data. Specifically, when the tracking event is triggered, the corresponding tracking data is found in the server tracking data table obtained in Step 1 based on the unique identifier of the triggering element, and it is checked whether the tracking data is required to carry network data.

[0113] Step 3: If the data tracking data does not need to include network data, then directly report the data and the process ends.

[0114] Step 4: If the event tracking data needs to carry network data, then check whether all network data has met the conditions in the first data table (network data global storage object networkCacheMap) using the event tracking data.

[0115] Step 5: If all conditions are met, the data for the event is reported directly, and the process ends.

[0116] Step 6: If the conditions are not met, the second network data in the reporting function and network data that does not meet the conditions, along with its corresponding request data, are stored as target tasks in the processing queue. That is, after assembling the data according to the data format of the processing queue reportQueue, it is stored in the processing queue reportQueue.

[0117] Step 7: Intercept network requests from terminal devices. Whenever a network request ends, execute the following two steps: Store the unique identifier `requestKey` and the returned result `responseKey` into the global network data storage object `networkCacheMap`. Poll the target tasks in the processing queue `reportQueue`, execute the corresponding data reporting, and remove the corresponding target task from the processing queue.

[0118] Step 8: The terminal device starts a timer. The timer polls and checks the target tasks in the processing queue reportQueue at regular intervals, consumes the target tasks that have timed out, that is, executes the corresponding data reporting, and deletes the corresponding target task from the processing queue.

[0119] Step 9: When a terminal device shutdown event is detected, immediately consume all target tasks in the reportQueue, that is, execute the corresponding data reporting.

[0120] Therefore, the second network data that has not matched the response data can be used as the target task and stored in the processing queue. After listening to the network request data, the target task in the processing queue is executed to obtain the second response data of the second network data from the network request data. Then, the network data is updated and reported according to the first response data and the second response data. Therefore, during the data reporting process, the reported network data can carry the network request data.

[0121] It should be understood that although each step in the flowcharts of the above embodiments is shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.

[0122] Based on the same inventive concept, this application also provides a data reporting device for implementing the above-described data reporting method. The solution provided by this device is similar to the solution described in the above-described method. Therefore, the specific limitations of one or more data reporting devices and embodiments of the data reporting device provided below can be found in the above-described limitations of the data reporting method and data reporting method, and will not be repeated here.

[0123] This embodiment also provides a data reporting device, which can be integrated into a terminal device. For example, such as... Figure 8 As shown, the data reporting device may include:

[0124] Analysis module 801 is used to analyze the intercepted event tracking data to obtain the network data to be reported for the event tracking data.

[0125] The matching module 802 is used to determine the first network data and the second network data in the network data based on the first data table; the first network data matches the first response data in the first data table, and the second network data does not match the response data in the first data table;

[0126] Storage module 803 is used to generate a target task based on the second network data and store it in the processing queue;

[0127] Execution module 804 is used to execute the target task in the processing queue based on the monitored network request data, and obtain the second response data of the second network data;

[0128] The data reporting module 805 is used to update network data based on the first response data and the second response data, and to report the updated network data.

[0129] The aforementioned data reporting device can take the second network data that has not matched the response data as the target task and store it in the processing queue. After listening to the network request data, it executes the target task in the processing queue, obtains the second response data of the second network data from the network request data, and then updates the network data according to the first response data and the second response data and reports it. Therefore, during the data reporting process, the reported network data can carry the network request data.

[0130] In some embodiments, the data reporting module 805 is further configured to:

[0131] The first data table is updated based on the first request data and the response data of the first request data in the network request data;

[0132] Based on the updated second data table, the target task in the processing queue is executed, and the second response data corresponding to the second network data is matched.

[0133] In some embodiments, the data reporting module 805 is further configured to:

[0134] Traverse the processing tasks in the processing queue to obtain the second request data corresponding to the target task;

[0135] The second request data is matched with the first request data in the second data table;

[0136] If the second request data matches the corresponding first request data in the second data table, then the response data corresponding to the matched first request data is determined as the second response data corresponding to the second network data.

[0137] In some embodiments, the analysis module 801 is further configured to:

[0138] The event tracking points are analyzed to obtain event identifiers;

[0139] Based on the event identifier, the event data is obtained by matching it in the event tracking data table;

[0140] The network data is obtained by performing data analysis on the embedded data points.

[0141] In some embodiments, the data reporting device is further configured to:

[0142] Iterate through each target task in the processing queue to obtain the duration of each target task;

[0143] If the duration is greater than or equal to the duration threshold, then the network data corresponding to each target task is updated based on the first response data corresponding to each target task;

[0144] The updated network data for each of the aforementioned target tasks will be reported.

[0145] In some embodiments, the data reporting device is further configured to:

[0146] Execute each target task in the processing queue based on the detected close event;

[0147] If each target task matches the third response data in the second data table, then based on the first response data and the third response data of each target task, the network data corresponding to each target task is updated, and the updated network data of each target task is reported.

[0148] If no third response data is matched in the second data table for each target task, the network data corresponding to each target task is updated based on the first response data of each target task, and the updated network data of each target task is reported.

[0149] Based on the same inventive concept, this application also provides a computer device, which can be a server or a terminal device. The computer device includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps of the above-described data reporting method. This enables various functions, such as:

[0150] The intercepted event tracking data is analyzed to obtain the network data to be reported for the event tracking data.

[0151] The first network data and the second network data in the network data are determined based on the first data table; the first network data matches the first response data in the first data table, and the second network data does not match the response data in the first data table;

[0152] The target task is generated based on the second network data and stored in the processing queue;

[0153] Based on the monitored network request data, the target task in the processing queue is executed to obtain the second response data of the second network data;

[0154] The network data is updated based on the first response data and the second response data, and the updated network data is reported.

[0155] Beneficial effect: Second network data that does not match response data can be used as the target task and stored in the processing queue. After listening to the network request, the target task in the processing queue is executed according to the listened network request data, that is, the second response data of the second network data is obtained from the network request data, and then the network data is updated and reported according to the first response data and the second response data. Therefore, the network data reported during the data reporting process can carry the network request data.

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

[0157] In one embodiment, taking a terminal device as an example, its internal structure diagram can be as follows: Figure 9 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When executed by the processor, the computer program implements a data reporting method. The display unit of the computer device is used to form a visually visible image. It can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0158] Those skilled in the art will understand that Figure 9 The structure shown is only a block diagram of a part of the structure related to the present application and does not constitute a limitation on the computer device on which the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0159] Based on the same inventive concept, embodiments of this application also provide a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc.

[0160] Since the computer program stored in the computer-readable storage medium can execute any of the data reporting methods provided in the embodiments of this application, the beneficial effects that any of the data reporting methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0161] Based on the same inventive concept, embodiments of this application also provide a computer program product or computer program, which includes a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform the methods provided in the various optional implementations of the above embodiments.

[0162] It should be noted that the object data (including but not limited to user device information, user personal information, etc.) and dialogue data involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of relevant countries and regions. Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program and related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods.

[0163] Any reference to memory, database, or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0164] The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0165] In the above embodiments of the data reporting device, computer-readable storage medium, computer device, and computer program product, the description of each embodiment has its own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process and beneficial effects of the data reporting device, computer-readable storage medium, computer program product, computer device, and their corresponding units described above can be referred to the description of the data reporting method in the above embodiments, and will not be repeated here.

[0166] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of each technical feature in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0167] The foregoing has provided a detailed description of a data reporting method, apparatus, computer device, computer-readable storage medium, and computer program product provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.< / networkcachemap>

Claims

1. A data reporting method, characterized in that, The method includes: The intercepted event tracking data is analyzed to obtain the network data to be reported for the event tracking data. The first network data and the second network data in the network data are determined based on the first data table; the first network data matches the first response data in the first data table, and the second network data does not match the response data in the first data table; The target task is generated based on the second network data and stored in the processing queue; Based on the monitored network request data, the target task in the processing queue is executed to obtain the second response data of the second network data; The network data is updated based on the first response data and the second response data, and the updated network data is reported.

2. The data reporting method as described in claim 1, characterized in that, The step of executing the target task in the processing queue based on the monitored network request data to obtain the second response data of the second network data includes: Based on the first request data and the response data of the first request data in the network request data, the first data table is updated to obtain the second data table; Execute the target task in the processing queue, and match the second request data in the target task with the first request data in the second data table; If the second request data matches the corresponding first request data in the second data table, then the response data corresponding to the matched first request data is determined as the second response data.

3. The data reporting method as described in claim 1, characterized in that, The process of analyzing the intercepted event tracking data to obtain the network data to be reported includes: The event tracking points are analyzed to obtain event identifiers; Based on the event identifier, the event data is obtained by matching it in the event tracking data table; The network data in the event tracking data is determined as the network data to be reported for the event tracking.

4. The data reporting method according to any one of claims 1 to 3, characterized in that, The data reporting method also includes: Determine the duration and status information of the target task stored in the processing queue; If the duration is greater than or equal to the duration threshold and the status information is in an incomplete state, then the network data is updated based on the first response data to obtain the third network data; The third network data is reported.

5. The data reporting method according to any one of claims 1 to 3, characterized in that, The data reporting method also includes: Based on the detected shutdown event, execute the target task; If the second request data in the target task matches the corresponding third response data in the second data table, the network data is updated based on the first response data and the third response data to obtain the fourth network data. The fourth network data is reported.

6. The data reporting method as described in claim 5, characterized in that, The data reporting method also includes: If the second request data in the target task does not match the corresponding third response data in the second data table, the network data is updated based on the first response data to obtain the fifth network data. The fifth network data is reported.

7. A data reporting device, characterized in that, The device includes: The analysis module is used to analyze the intercepted event tracking data to obtain the network data to be reported for the event tracking data. A matching module is used to determine first network data and second network data in the network data based on a first data table; the first network data matches the first response data in the first data table, and the second network data does not match the response data in the first data table; The storage module is used to generate a target task based on the second network data and store it in the processing queue; The execution module is used to execute the target task in the processing queue based on the monitored network request data, and obtain the second response data of the second network data; The data reporting module is used to update the network data based on the first response data and the second response data, and to report the updated network data.

8. A computer device, characterized in that, It includes a processor and a memory, the memory storing multiple computer programs; the processor loads the computer programs from the memory to execute the data reporting method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores multiple computer programs adapted for loading by a processor to execute the data reporting method as described in any one of claims 1 to 6.

10. A computer software, characterized in that, The computer software includes a computer program, which is executed by a processor using the data reporting method as described in any one of claims 1 to 6.

Images