Method, device, computer equipment and storage medium for reporting buried data

Abstract

The present application relates to the field of computers, and specifically to a method, device, computer equipment and storage medium for reporting buried point data. The method includes: collecting the original buried point data that needs to be reported; determining the data recipients of the original buried point data, and the data reporting requirements of each data recipient among the data recipients of the original buried point data, and the number of data recipients of the original buried point data is at least one; processing the original buried point data according to the data reporting requirements of each data recipient among the data recipients of the original buried point data, obtaining the buried point data to be reported of each data recipient, and reporting the buried point data to be reported of each data recipient to each data recipient. The embodiment of the present invention can realize the reporting of the buried point data of the same event to multiple data recipients in order to conduct targeted data analysis.

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a method, device, computer equipment and storage medium for reporting buried point data. Background Art

[0002] Tracking refers to collecting some information in a specific process in an application (APP) to track the usage of the application, which can be used to further optimize the product or provide data support for operations. Tracking can be used to collect information such as the number of visits, number of visitors, length of stay, number of page views, bounce rate, etc.

[0003] Traditional tracking solutions usually just report tracking data to a certain channel, which then performs data analysis. However, with the continuous operation of applications, the number of users is increasing, and the data generated is becoming more and more abundant. In order to better operate applications and provide users with a better user experience, it is necessary to conduct targeted analysis on the collected tracking data, but the current solution cannot meet the needs. Summary of the invention

[0004] In view of the above-mentioned deficiencies or shortcomings, the present invention provides a method, apparatus, computer equipment and storage medium for reporting buried data. The embodiments of the present invention can report the buried data of the same event to multiple data recipients for targeted data analysis.

[0005] According to a first aspect, the present invention provides a method for reporting buried point data. In one embodiment, the method includes:

[0006] Collect the original buried point data that needs to be reported;

[0007] Determine the data recipients of the original buried data and the data reporting requirements of each of the data recipients of the original buried data, where the number of the data recipients of the original buried data is at least one;

[0008] The original buried point data are processed according to the data reporting requirements of each data recipient among the data recipients of the original buried point data, the buried point data to be reported of each data recipient are obtained, and the buried point data to be reported of each data recipient are reported to each data recipient.

[0009] In one embodiment, the step of determining the data recipient of the original buried data includes:

[0010] Determine the type of tracking event corresponding to the original tracking data;

[0011] Determine the data recipient of the original tracking data based on the tracking event type.

[0012] In one embodiment, before the step of determining the data recipient of the original buried data, the following steps are included:

[0013] Receive the mapping relationship information between the tracking event type and the data receiver sent by the configuration server, and store the mapping relationship information locally;

[0014] The steps of determining the data recipient of the original tracking data according to the tracking event type include:

[0015] The data recipient of the original buried point data is determined based on the mapping relationship information between the pre-stored buried point event type and the data recipient.

[0016] In one embodiment, the step of processing the original buried point data according to the data reporting requirement of any data recipient among the data recipients of the original buried point data to obtain the buried point data to be reported by any data recipient includes:

[0017] The original buried point data is converted into a data format so that the data format of the processed original buried point data meets the data reporting requirements of any data recipient, and the processed original buried point data is used as the buried point data to be reported by any data recipient.

[0018] In one embodiment, before the step of collecting the original buried point data to be reported, the following steps are included:

[0019] In response to the triggering of any burying point event, the data reporting program generates the burying point data of the triggered burying point event;

[0020] The steps to collect the original tracking data to be reported include:

[0021] When it is detected that the data reporting program is going to report the buried point data generated by it, the buried point data to be reported by the data reporting program is intercepted by an interceptor, and the intercepted buried point data is used as the original buried point data.

[0022] In one embodiment, the step of reporting the buried data to be reported of each data receiver to each data receiver includes:

[0023] By adopting the single-queue consumption and multi-threaded distribution method, the buried data to be reported by each data receiver is reported to each data receiver through the buried data reporting interface of each data receiver.

[0024] In one embodiment, when reporting the burial point data to be reported by each data receiver to each data receiver, the burial point data to be reported by each data receiver is compressed, and the compressed burial point data to be reported by each data receiver is reported to each data receiver.

[0025] According to the second aspect, the present invention provides a buried point data reporting device. In one embodiment, the device includes:

[0026] The buried point data acquisition module is used to collect the original buried point data that needs to be reported;

[0027] A receiver information determination module, used to determine the data receiver of the original buried point data and the data reporting requirements of each of the data receivers of the original buried point data, wherein the number of the data receivers of the original buried point data is at least one;

[0028] The buried point data reporting module is used to process the original buried point data according to the data reporting requirements of each data recipient among the data recipients of the original buried point data, obtain the buried point data to be reported by each data recipient, and report the buried point data to be reported by each data recipient to each data recipient.

[0029] According to a third aspect, the present invention provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any of the above method embodiments when executing the computer program.

[0030] According to a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of any of the above method embodiments are implemented.

[0031] In an embodiment of the present invention, by collecting the original buried point data that needs to be reported, the data recipients of the original buried point data and the data reporting requirements of each data recipient among the data recipients of the original buried point data are determined, and the number of data recipients of the original buried point data is at least one; the original buried point data is processed according to the data reporting requirements of each data recipient among the data recipients of the original buried point data, and the buried point data to be reported of each data recipient is obtained, and the buried point data to be reported of each data recipient is reported to each data recipient, so that the buried point data can be reported to multiple data recipients, so that each data recipient can perform targeted analysis on the buried point data from the client. In addition, when meeting the above business needs, it will not affect the normal use of the client by users, and reduce the workload required for developers to implement the above functions. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 This is an application environment diagram of a method for reporting buried point data in an embodiment;

[0033] Figure 2 A schematic diagram of a flow chart of a method for reporting buried point data in an embodiment;

[0034] Figure 3A schematic diagram of a process for determining a data recipient in one embodiment;

[0035] Figure 4 It is a structural block diagram of a buried point data reporting device in one embodiment;

[0036] Figure 5 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0038] The present invention provides a method for reporting buried point data. In this embodiment, the method for reporting buried point data can be applied to Figure 1 In the application environment shown in the figure, the user terminal 10 is installed with an application, in which an SDK (Software Development Kit) for reporting point data can be integrated, through which some behaviors of the user in the application (hereinafter referred to as the target application) can be recorded and reported to the data receiver (such as Figure 1 21-23, of course, the number of data recipients can be adjusted based on different application scenarios, and this embodiment does not limit it), the data recipient is used to receive the buried data of the application program so as to perform data analysis on the buried data of the user terminal, wherein the data recipient can be the application developer's own server, or the server of the service provider that provides data analysis services to it, such as AppsFlyer (a mobile attribution and marketing analysis platform that can provide users with mobile advertising analysis and other services), Firebase (a mobile platform that can help users quickly develop high-quality applications).

[0039] The various terminals of the user terminal 10 may include but are not limited to various personal computers, laptops, smart phones, tablet computers and desktop computers, etc. The data receiver may be implemented with an independent server or a server cluster consisting of multiple servers.

[0040] A method for reporting buried point data provided in this embodiment includes: Figure 2 The steps shown below are applied to Figure 1 The user terminal in is taken as an example for explanation.

[0041] S110: Collecting the original buried point data that needs to be reported;

[0042] S120: Determine a data recipient of the original buried point data and a data reporting requirement of each of the data recipients of the original buried point data, wherein the number of the data recipients of the original buried point data is at least one;

[0043] S130: Process the original burial point data according to the data reporting requirements of each data receiver among the data receivers of the original burial point data, obtain the burial point data to be reported of each data receiver, and report the burial point data to be reported of each data receiver to each data receiver.

[0044] Among them, the developer of the target application can use Transform and bytecode operation frameworks such as ASM and Javassist to perform bytecode instrumentation in the compilation phase when developing the target application to achieve automatic tracking. Developers can define corresponding tracking events based on actual needs and set corresponding tracking points for each tracking event to collect tracking data for each tracking event.

[0045] Exemplarily, tracking events may include event types such as click events, exposure events, and page dwell time events. Each event type may correspond to multiple specific tracking events. For example, a click event may be a user clicking a button in a target application. Regardless of whether there is any result after the click, it can be counted as a click event. For example, click events may include order submission events, order cancellation events, payment initiation events, payment cancellation events, etc.; page dwell time events can be used to indicate the length of time a user stays on a certain page of the target application; exposure events refer to a user successfully opening a page, refreshing a page, loading the next page and / or loading a page, etc.

[0046] During the operation of the target application, the original buried data to be reported can be generated through the integrated SDK, and then the data recipients of the original buried data and the data reporting requirements of each data recipient among the data recipients of the original buried data can be determined, and then the original buried data can be processed according to the data reporting requirements of each data recipient among the data recipients of the original buried data to obtain the buried data to be reported by each data recipient, and finally the buried data to be reported by each data recipient is reported to each data recipient, so as to realize the reporting of the buried data of the same event to multiple data recipients, so that each data recipient can conduct targeted analysis on the buried data from the client. In addition, when meeting the above business needs, it will not affect the normal use of the client by users, and reduce the workload required for developers to implement the above functions.

[0047] In one embodiment, the above step of determining the data recipient of the original buried data is as follows: Figure 3 As shown, including:

[0048] S121: Determine the type of buried point event corresponding to the original buried point data;

[0049] S122: Determine the data receiver of the original burying point data according to the burying point event type.

[0050] In this embodiment, the buried data required by different data receivers may be different. For example, data receiver A needs the buried data of the target application reported by the user terminal to be the buried data of the three buried events a, b, and c, while data receiver B needs the buried data of the target application reported by the user terminal to be the buried data of the three buried events b, c, and d. If the original buried data currently acquired is the buried data of the buried event a, then it can be determined that the data receiver of the original buried data is A. Similarly, if the original buried data currently acquired is the buried data of the buried event b or c, then it can be determined that the data receiver of the original buried data is A and B. Therefore, when determining the data receiver of the original buried data, it is possible to first determine the buried event type corresponding to the original buried data currently acquired, and then determine the data receiver of the original buried data based on the buried data type.

[0051] Among them, before the step of determining the data recipient of the original buried point data, it includes: receiving the mapping relationship information between the buried point event type and the data recipient sent by the configuration server, and storing the mapping relationship information locally (referring to the local of the user terminal). Correspondingly, the step of determining the data recipient of the original buried point data according to the buried point event type includes: determining the data recipient of the original buried point data according to the pre-stored mapping relationship information between the buried point event type and the data recipient.

[0052] The mapping relationship information between the tracking event type and the data recipient can be adjusted by the developer (or operator, etc.) based on actual needs, and after adjustment, it can be sent to the user terminal through the configuration server so that the user terminal can determine the data recipient of the original tracking data based on the mapping relationship information.

[0053] The above-mentioned buried point event type may refer to the unique identifier of the buried point event. For example, there are currently three buried point events, and their corresponding unique identifiers are a, b, and c. If the original buried point data currently obtained is the buried point data of buried point event a, then the buried point event type corresponding to the original buried point data at this time refers to a. At this time, when determining the data recipient of the original buried point data according to the buried point event type, the data recipient corresponding to the unique identifier of the buried point event is determined as the data recipient of the original buried point data.

[0054] When there is an event type corresponding to a buried point event, the above buried point event type may refer to the event type of the buried point event (the event type may be defined according to actual needs). For example, there are currently 6 buried point events, and their corresponding unique identifiers are a1, b1, c1 and a2, b2, c2, among which the event types corresponding to a1 and a2 are both A, the event types corresponding to b1 and b2 are both B, and the event types corresponding to c1 and c2 are both C. If the original buried point data currently acquired is the buried point data of buried point event a, then the buried point event type corresponding to the original buried point data at this time refers to A. At this time, when determining the data recipient of the original buried point data according to the buried point event type, the data recipient corresponding to the event type of the buried point event is determined as the data recipient of the original buried point data.

[0055] In one embodiment, the step of processing the original buried point data according to the data reporting requirement of any data recipient among the data recipients of the original buried point data to obtain the buried point data to be reported by any data recipient includes:

[0056] The original buried point data is converted into a data format so that the data format of the processed original buried point data meets the data reporting requirements of any data recipient, and the processed original buried point data is used as the buried point data to be reported by any data recipient.

[0057] In this embodiment, different data receivers may have different data reporting requirements for the buried data reported by the user terminal, wherein the data reporting requirements may be data format requirements, for example, data receiver A requires the buried data to be in JSON (JavaScript Object Notation) format, while data receiver A requires the buried data to be in a non-JSON format, such as log, xml, etc. Therefore, when the original buried data is processed according to the data reporting requirements of the data receiver, it is formatted so that the processed data can meet the data reporting requirements of the data receiver.

[0058] Furthermore, in some application scenarios, the data reporting requirements of the data receiver may include requirements for the upload timing of the buried point data in addition to the data format requirements. For example, the data receiver may require that the upload timing of the buried point data of the first buried point event be reported immediately, and require that the upload timing of the buried point data of the second buried point event be reported regularly (for example, once every 1 minute, 3 minutes, etc.), that is, after the user terminal obtains the buried point data belonging to the first buried point event, it immediately reports it to the data receiver, and after obtaining the buried point data of the second buried point event, it first stores it in a file for recording the buried point data, and then reports the buried point data in the file to the data receiver when the current time reaches the reporting time. Among them, the first buried point event (or second buried point event) of each data receiver may be different, for example, the first buried point event corresponding to the data receiver A is a, b, and the first buried point event corresponding to the data receiver B is b, c. In addition, the mapping relationship between each data receiver and its first buried point event and the second buried point event pre-stored in the user terminal can be dynamically configured by configuring the server.

[0059] In one embodiment, before the step of collecting the original buried point data to be reported, the following steps are included:

[0060] In response to the triggering of any burying point event, the data reporting program generates the burying point data of the triggered burying point event.

[0061] Accordingly, the steps for collecting the original tracking data to be reported include:

[0062] When it is detected that the data reporting program is going to report the buried point data generated by it, the buried point data to be reported by the data reporting program is intercepted by an interceptor, and the intercepted buried point data is used as the original buried point data.

[0063] In this embodiment, the data reporting program is used to generate the buried point data of any buried point event when the buried point event is triggered, and then report the generated buried point data to a specified data recipient through the data reporting interface. If the buried point data required by each data recipient is consistent, then the buried point data to be reported by the data reporting program can be intercepted by an interceptor, and the intercepted buried point data can be used as the original buried point data, and subsequent steps can be performed, such as processing the original buried point data to obtain the buried point data to be reported to each data recipient. In this way, there is no need to integrate multiple data reporting programs in the target application, which can reduce the workload of developers.

[0064] Among them, the above interceptor can be implemented based on the characteristics of AOP aspect programming of the program.

[0065] In one embodiment, the step of reporting the burial point data to be reported by each data receiver to each data receiver includes: adopting a single queue consumption and multi-thread distribution method to report the burial point data to be reported by each data receiver to each data receiver through the burial point data reporting interface of each data receiver.

[0066] This embodiment does not use the main thread to report the buried data. By adopting a single queue consumption and multi-thread distribution method to report the buried data to be reported by each data receiver to each data receiver, the reporting speed can be accelerated and the impact on the normal use of users can be reduced.

[0067] Furthermore, when reporting the buried point data to be reported by each data receiver to each data receiver, the buried point data to be reported by each data receiver is compressed, and the compressed buried point data to be reported by each data receiver is reported to each data receiver. Compressing the buried point data before reporting can reduce the amount of data that needs to be uploaded, speed up the reporting speed, reduce the occupancy of the upload bandwidth, and reduce the impact on the normal use of users.

[0068] Figure 2 , Figure 3 FIG. 1 is a flow chart of a method for reporting buried point data in an embodiment. It should be understood that although Figure 2 , Figure 3 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 , Figure 3 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0069] Based on the same inventive concept, the present invention also provides a device for reporting buried point data. Figure 4 As shown, the buried point data reporting device includes the following modules:

[0070] The buried point data acquisition module 110 is used to collect the original buried point data that needs to be reported;

[0071] A receiver information determination module 120, used to determine the data receiver of the original buried point data and the data reporting requirements of each of the data receivers of the original buried point data, wherein the number of the data receivers of the original buried point data is at least one;

[0072] The buried point data reporting module 130 is used to process the original buried point data according to the data reporting requirements of each data recipient among the data recipients of the original buried point data, obtain the buried point data to be reported of each data recipient, and report the buried point data to be reported of each data recipient to each data recipient.

[0073] In one embodiment, the receiving party information determination module includes:

[0074] The type determination submodule is used to determine the type of the buried point event corresponding to the original buried point data;

[0075] The receiver determination submodule is used to determine the data receiver of the original tracking data according to the tracking event type.

[0076] In one embodiment, the buried point data reporting device further includes a mapping relationship maintenance module. The mapping relationship maintenance module is used to receive the mapping relationship information between the buried point event type and the data recipient sent by the configuration server before determining the data recipient of the original buried point data, and store the mapping relationship information locally.

[0077] Correspondingly, the receiver determination submodule is used to determine the data receiver of the original burying point data according to the mapping relationship information between the pre-stored burying point event type and the data receiver.

[0078] In one embodiment, the buried point data reporting module is used to process the original buried point data according to the data reporting requirements of any data recipient of the original buried point data to obtain the buried point data to be reported by any data recipient. The module is specifically used to convert the data format of the original buried point data so that the data format of the processed original buried point data meets the data reporting requirements of any data recipient, and the processed original buried point data is used as the buried point data to be reported by any data recipient.

[0079] In one embodiment, the buried point data reporting device further includes a buried point data generating module. The buried point data generating module is used to generate the buried point data of the triggered buried point event in response to the triggering of any buried point event through a data reporting program before collecting the original buried point data to be reported.

[0080] Correspondingly, the buried point data acquisition module is used to intercept the buried point data to be reported by the data reporting program through an interceptor when it detects that the data reporting program is going to report the buried point data it generated, and use the intercepted buried point data as the original buried point data.

[0081] In one embodiment, when the burial point data reporting module is used to report the burial point data to be reported by each data receiver to each data receiver, it is specifically used to adopt a single queue consumption and multi-thread distribution method to report the burial point data to be reported by each data receiver to each data receiver through the burial point data reporting interface of each data receiver.

[0082] In one embodiment, when the burial point data reporting module is used to report the burial point data to be reported by each data receiver to each data receiver, it is specifically used to compress the burial point data to be reported by each data receiver, and report the compressed burial point data to be reported by each data receiver to each data receiver.

[0083] For the specific limitations of the buried data reporting device, please refer to the limitations of the buried data reporting method above, which will not be repeated here. Each module in the above-mentioned buried data reporting device can be implemented in whole or in part through software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0084] In one embodiment, a computer device is provided, whose internal structure diagram can be as follows: Figure 5 shown.

[0085] The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as buried point data and mapping relationship information. The specific stored data can also refer to the definition in the above method embodiment. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for reporting buried point data is implemented.

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

[0087] This embodiment further provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented:

[0088] Collect the original buried point data that needs to be reported; determine the data recipients of the original buried point data, and the data reporting requirements of each data recipient among the data recipients of the original buried point data, and the number of data recipients of the original buried point data is at least one; process the original buried point data according to the data reporting requirements of each data recipient among the data recipients of the original buried point data, obtain the buried point data to be reported of each data recipient, and report the buried point data to be reported of each data recipient to each data recipient.

[0089] In one embodiment, when the processor executes the computer program to determine the data recipient of the original buried data, the processor further implements the following steps:

[0090] Determine the type of buried point event corresponding to the original buried point data; determine the data recipient of the original buried point data based on the buried point event type.

[0091] In one embodiment, before the processor executes the computer program to determine the data recipient of the original buried data, the processor further implements the following steps:

[0092] Receive the mapping relationship information between the tracking event type and the data recipient sent by the configuration server, and store the mapping relationship information locally.

[0093] Accordingly, when the processor executes the computer program to determine the data recipient of the original buried point data according to the buried point event type, the following steps are also implemented:

[0094] The data recipient of the original buried point data is determined based on the mapping relationship information between the pre-stored buried point event type and the data recipient.

[0095] In one embodiment, the processor executes a computer program to process the original buried point data according to the data reporting requirements of any data recipient of the original buried point data, and when obtaining the buried point data to be reported of any data recipient, the following steps are further implemented:

[0096] The original buried point data is converted into a data format so that the data format of the processed original buried point data meets the data reporting requirements of any data recipient, and the processed original buried point data is used as the buried point data to be reported by any data recipient.

[0097] In one embodiment, before the processor executes the computer program to collect the original buried point data to be reported, the processor further implements the following steps:

[0098] In response to the triggering of any burying point event, the data reporting program generates the burying point data of the triggered burying point event.

[0099] Accordingly, when the processor executes the computer program to collect the original buried point data to be reported, the following steps are also implemented:

[0100] When it is detected that the data reporting program is going to report the buried point data generated by it, the buried point data to be reported by the data reporting program is intercepted by an interceptor, and the intercepted buried point data is used as the original buried point data.

[0101] In one embodiment, when the processor executes the computer program to report the buried data to be reported of each data receiver to each data receiver, the processor also implements the following steps:

[0102] By adopting the single-queue consumption and multi-threaded distribution method, the buried data to be reported by each data receiver is reported to each data receiver through the buried data reporting interface of each data receiver.

[0103] In one embodiment, the processor executes a computer program to compress the burial point data to be reported by each data recipient when reporting it to each data recipient, and reports the compressed burial point data to be reported by each data recipient to each data recipient.

[0104] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0105] Collect the original buried point data that needs to be reported; determine the data recipients of the original buried point data, and the data reporting requirements of each data recipient among the data recipients of the original buried point data, and the number of data recipients of the original buried point data is at least one; process the original buried point data according to the data reporting requirements of each data recipient among the data recipients of the original buried point data, obtain the buried point data to be reported of each data recipient, and report the buried point data to be reported of each data recipient to each data recipient.

[0106] In one embodiment, the computer program is executed by a processor to further implement the following steps when determining the data recipient of the original buried data:

[0107] Determine the type of buried point event corresponding to the original buried point data; determine the data recipient of the original buried point data based on the buried point event type.

[0108] In one embodiment, the computer program is executed by a processor, and before determining the data recipient of the original buried data, the computer program further implements the following steps:

[0109] Receive the mapping relationship information between the tracking event type and the data recipient sent by the configuration server, and store the mapping relationship information locally.

[0110] Accordingly, when the computer program is executed by the processor and the data recipient of the original buried point data is determined according to the buried point event type, the following steps are also implemented:

[0111] The data recipient of the original buried point data is determined based on the mapping relationship information between the pre-stored buried point event type and the data recipient.

[0112] In one embodiment, the computer program is executed by a processor, and when the original buried point data is processed according to the data reporting requirements of any data recipient of the original buried point data, and the buried point data to be reported of any data recipient is obtained, the following steps are further implemented:

[0113] The original buried point data is converted into a data format so that the data format of the processed original buried point data meets the data reporting requirements of any data recipient, and the processed original buried point data is used as the buried point data to be reported by any data recipient.

[0114] In one embodiment, the computer program is executed by a processor, and before the step of collecting the original buried point data to be reported, the following steps are further implemented:

[0115] In response to the triggering of any burying point event, the data reporting program generates the burying point data of the triggered burying point event.

[0116] Accordingly, the computer program is executed by the processor, and when collecting the original buried point data to be reported, the following steps are also implemented:

[0117] When it is detected that the data reporting program is going to report the buried point data generated by it, the buried point data to be reported by the data reporting program is intercepted by an interceptor, and the intercepted buried point data is used as the original buried point data.

[0118] In one embodiment, the computer program is executed by a processor, and when reporting the buried data to be reported of each data recipient to each data recipient, the following steps are also implemented:

[0119] By adopting the single-queue consumption and multi-threaded distribution method, the buried data to be reported by each data receiver is reported to each data receiver through the buried data reporting interface of each data receiver.

[0120] In one embodiment, the computer program is executed by a processor, and when reporting the buried point data to be reported of each data recipient to each data recipient, the buried point data to be reported of each data recipient is compressed, and the compressed buried point data to be reported of each data recipient is reported to each data recipient.

[0121] Those skilled in the art can understand that all or part of the processes in the above method embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0122] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features 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.

[0123] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for reporting buried point data, characterized in that: The method is applied to a user terminal, the user terminal is connected to multiple data receivers, and the data receivers are used to receive the buried data of the application program so as to perform data analysis on the buried data of the user terminal; The user terminal is installed with a target application integrated with an SDK, and the method is implemented based on the SDK, and the method includes: Collect the original buried point data that needs to be reported; Determine a data recipient of the original buried point data and a data reporting requirement of each of the data recipients of the original buried point data, wherein the number of the data recipients of the original buried point data is at least one; Processing the original buried point data according to the data reporting requirements of each data recipient among the data recipients of the original buried point data, obtaining the buried point data to be reported of each data recipient, and reporting the buried point data to be reported of each data recipient to each data recipient; Before the step of determining the data recipient of the original burying point data, the method includes: receiving mapping relationship information between the burying point event type and the data recipient sent by the configuration server, and storing the mapping relationship information locally; The step of determining the data recipient of the original buried data includes: Determine the type of buried point event corresponding to the original buried point data; Determine the data recipient of the original burying point data according to the pre-stored mapping relationship information between the burying point event type and the data recipient; Before the step of collecting the original buried point data to be reported, the method includes: generating buried point data of the triggered buried point event in response to the triggering of any buried point event through a data reporting program; The step of collecting the original buried point data that needs to be reported includes: when it is detected that the data reporting program is going to report the buried point data it generates, the buried point data to be reported by the data reporting program is intercepted by an interceptor, and the intercepted buried point data is used as the original buried point data.

2. The method according to claim 1, characterized in that The step of processing the original buried point data according to the data reporting requirement of any data recipient of the original buried point data to obtain the buried point data to be reported by any data recipient includes: The original burial point data is subjected to data format conversion processing so that the data format of the processed original burial point data meets the data reporting requirements of any data recipient, and the processed original burial point data is used as the burial point data to be reported by any data recipient.

3. The method according to claim 1, characterized in that The step of reporting the buried data to be reported of each data receiver to each data receiver includes: By adopting the single-queue consumption and multi-threaded distribution method, the buried data to be reported by each data receiver is reported to each data receiver through the buried data reporting interface of each data receiver.

4. The method according to claim 1 or 3, characterized in that When reporting the buried point data to be reported of each data receiver to each data receiver, the buried point data to be reported of each data receiver is compressed, and the compressed buried point data to be reported of each data receiver is reported to each data receiver.

5. A device for implementing the method for reporting buried point data according to claim 1, characterized in that: The device is applied to a user terminal, the user terminal is connected to multiple data receivers, and the data receivers are used to receive the buried data of the application program so as to perform data analysis on the buried data of the user terminal; the device includes: The buried point data acquisition module is used to collect the original buried point data that needs to be reported; A receiver information determination module, used to determine the data receiver of the original buried point data and the data reporting requirements of each of the data receivers of the original buried point data, wherein the number of the data receivers of the original buried point data is at least one; The buried point data reporting module is used to process the original buried point data according to the data reporting requirements of each data recipient among the data recipients of the original buried point data, obtain the buried point data to be reported by each data recipient, and report the buried point data to be reported by each data recipient to each data recipient.

6. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images