Embedded point verification method, embedded point verification device, readable storage medium, electronic device

Abstract

The embodiments of the present disclosure relate to a method for checking buried points, a device for checking buried points, a readable storage medium, and an electronic device, and relate to the field of computer technology. The method for checking buried points includes: receiving buried point reporting information from an application client, and in response to the buried point reporting information including pit position information, matching the pit position information with the pit positions in a target pit position library; and checking the buried point reporting information based on a target verification rule library according to the matching result; wherein the target pit position library and the target verification rule library are determined according to the buried points in the buried point task to be checked. The present disclosure can improve the efficiency and accuracy of buried point verification.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of computer technology. More specifically, the embodiments of the present disclosure relate to a buried point verification method, a buried point verification device, a computer-readable storage medium and an electronic device. Background Art

[0002] This section is intended to provide a background or context to the embodiments of the disclosure that are recited in the claims, and no description herein is admitted to be prior art by inclusion in this section.

[0003] Tracking is the process of collecting some information in a specific process of the application to track the use of the application and provide data support for further product optimization. Verifying tracking can ensure the accuracy of the collected information.

[0004] The tracking verification schemes in the prior art are mainly divided into the following two types: the first is that during the development stage, through real-time uploading of logs, rule matching verification is performed on the server side, or the tracking requirement rules stored on the tracking platform are sent to the client, and the real-time tracking points are verified on the client side; the second is that after the tracking point is released in grayscale or in full, the new and old versions of the tracking points are compared and abnormal fluctuations are monitored to identify whether there are problems with the tracking point data. Summary of the invention

[0005] However, the first solution only focuses on whether the tracking point is correct or not, and cannot verify the over-reporting or under-reporting of the tracking point, so the accuracy of the verification is insufficient. The second solution needs to be launched online to find problems based on the fluctuations of the new and old tracking point data. The problem discovery cycle is long, and it depends on the user coverage of the new version to reach a certain proportion to accurately find problems based on the fluctuations of the new and old data, resulting in low efficiency of tracking point verification. In addition, it can only find problems after the tracking point is launched, which has the defect of delayed problem discovery.

[0006] Therefore, there is a great need for an improved tracking verification method that can improve the accuracy and efficiency of tracking verification, and at the same time, can discover more problems before the tracking goes online, and try to avoid the lag in problem discovery.

[0007] In this context, the embodiments of the present disclosure are intended to provide a method for verifying a buried point, a device for verifying a buried point, a computer-readable storage medium, and an electronic device.

[0008] According to the first aspect of the embodiment of the present disclosure, a method for verifying buried point is provided, comprising: receiving buried point reporting information from an application client, and in response to the buried point reporting information including pit location information, matching the pit location information with the pit locations in a target pit location library; verifying the buried point reporting information based on a target verification rule library according to the matching result; wherein the target pit location library and the target verification rule library are determined according to the buried points in the buried point task to be verified.

[0009] In an optional embodiment, the point-of-sale reporting information is verified according to the matching result based on the target verification rule library, including: in response to a successful match, obtaining the point-of-sale object identifier included in the pit information; for each point-of-sale object identifier, based on the verification rule in the target verification rule library of the first point-of-sale parameter associated with the point-of-sale object identifier, verifying the first point-of-sale parameter in the point-of-sale reporting information.

[0010] In an optional implementation, the tracking point reporting information is verified according to the matching result based on the target verification rule library, including: in response to a matching failure, adding a pit position matching failure label to the tracking point reporting information.

[0011] In an optional embodiment, after receiving the burden reporting information from the application client, the method further includes: determining a second burden parameter associated with the burden reporting event that triggers the burden reporting information, and verifying the second burden parameter in the burden reporting information according to the verification rules of the second burden parameter in the target verification rule library; and / or verifying the public parameters in the burden reporting information according to the verification rules corresponding to the public parameters in the target verification rule library.

[0012] In an optional embodiment, when the tracking point reporting information includes the tracking point reporting information corresponding to the tracking point test task, the tracking point task to be verified includes the first tracking point task in the tracking point test task and the second tracking point task of the application that the tracking point test task targets has been launched.

[0013] In an optional embodiment, the method for determining the tracking task to be verified includes: obtaining the value of a preset field in the tracking reporting information, and determining the tracking task to be verified according to the value of the preset field; wherein the preset field is used to indicate the version of the application client, and the tracking task to be verified includes the online tracking task corresponding to the version of the application client.

[0014] In an optional embodiment, the method also includes: updating the first quantity and the second quantity based on the received burrowing point reporting information; in response to a request to display the verification result of the first verification mode, displaying the first quantity and the second quantity corresponding to the burrowing point reporting events; wherein the first quantity includes the number of burrowing point reporting events indicated by the burrowing point reporting information, and the second quantity includes the number of burrowing point pits corresponding to the burrowing point reporting events indicated by the burrowing point reporting information.

[0015] In an optional embodiment, the method further includes: in response to a request to display the verification results of the first verification mode, sequentially displaying the verification results of the buried point reporting information according to the reporting time of the buried point reporting information.

[0016] In an optional embodiment, when the burying point reporting information includes burying point reporting information corresponding to the burying point test task, the method further includes: determining a target burying point position including burying point parameters of an enumeration type; and determining that the burying point test task test is completed when each enumeration value of each target burying point position is successfully matched.

[0017] In an optional embodiment, the method further includes: for the target burial point parameters in the burial point reporting information that do not pass the verification rule description constraint value range, verifying the target burial point parameters according to a candidate value library pre-associated with the target burial point parameters.

[0018] In an optional embodiment, the method further includes: updating one or more of a third quantity, a fourth quantity, a fifth quantity, a sixth quantity, and a seventh quantity according to the burrowing point attribution parameter value in the burrowing point reporting information; wherein the third quantity is used to characterize the number of burrowing point reporting information with empty burrowing point attribution parameter values, the fourth quantity is used to characterize the number of burrowing point reporting information with illegal burrowing point attribution parameter values, the fifth quantity is used to characterize the number of burrowing point reporting information with unreasonable burrowing point attribution parameter values, the sixth quantity is used to characterize the number of burrowing point reporting information with downgraded burrowing point attribution parameter values, and the seventh quantity is used to characterize the number of burrowing point attribution parameter values ​​of each type of burrowing point reporting event corresponding to the burrowing point reporting information; In the case where the pit position indicated by the pit position information in the burying point attribution parameter value does not belong to the burying point pit position, it is determined that the burying point attribution parameter value is illegal; in the case where the to-be-confirmed pit position indicated by the pit position information in the burying point attribution parameter value belongs to the burying point pit position, but the to-be-confirmed pit position fails to match the pit position information in the candidate burying point attribution parameter value of the burying point reporting event corresponding to the burying point reporting information, it is determined that the burying point attribution parameter value is unreasonable; in the case where the burying point attribution parameter value includes a preset field identifier field identifier, it is determined that the burying point attribution parameter value is downgraded, and the preset field identifier is used to identify the burying point attribution parameter value generated after triggering the pit position without a burying point object in the application client.

[0019] In an optional embodiment, the method also includes: for any application client, recording the burial point reporting information of the application client according to the reporting time sequence of the burial point reporting information; responding to a query request for the target burial point reporting information, obtaining other burial point reporting information whose reporting sequence is within a preset range with the target burial point reporting information, so as to display the target burial point reporting information and the other burial point reporting information.

[0020] In an optional embodiment, the tracking point reporting information includes tracking point reporting information generated by the application client according to the test case of the tracking point test task, wherein the test case is generated based on the tracking point position to be tested of the tracking point test task.

[0021] In an optional embodiment, when the tracking point reporting information includes tracking point reporting information corresponding to the tracking point test task, the method further includes: simulating the test data corresponding to the test link in the tracking point test task through a virtual object, so as to perform integrity verification on the tracking point test task based on the test link.

[0022] According to the second aspect of the embodiment of the present disclosure, there is provided a burying point verification device, including: a burying point information receiving module, configured to receive burying point reporting information of an application client, and in response to the burying point reporting information including pit location information, matching the pit location information with the pit locations in a target pit location library; a verification module, configured to verify the burying point reporting information based on a target verification rule library according to the matching result; wherein the target pit location library and the target verification rule library are determined according to the burying points in the burying point task to be verified.

[0023] In an optional embodiment, the point-of-sale reporting information is verified according to the matching result based on the target verification rule library, including: in response to a successful match, obtaining the point-of-sale object identifier included in the pit information; for each point-of-sale object identifier, based on the verification rule in the target verification rule library of the first point-of-sale parameter associated with the point-of-sale object identifier, verifying the first point-of-sale parameter in the point-of-sale reporting information.

[0024] In an optional implementation, the tracking point reporting information is verified according to the matching result based on the target verification rule library, including: in response to a matching failure, adding a pit position matching failure label to the tracking point reporting information.

[0025] In an optional embodiment, the burying point verification device may also include a second burying point parameter verification module and / or a third burying point parameter verification module, wherein the second burying point parameter verification module is configured to, after receiving the burying point reporting information from the application client, determine the second burying point parameter associated with the burying point reporting event that triggers the burying point reporting information, and verify the second burying point parameter in the burying point reporting information according to the verification rules of the second burying point parameter in the target verification rule library; the third burying point parameter verification module is configured to verify the public parameters in the burying point reporting information according to the verification rules corresponding to the public parameters in the target verification rule library.

[0026] In an optional embodiment, when the tracking point reporting information includes the tracking point reporting information corresponding to the tracking point test task, the tracking point task to be verified includes the first tracking point task in the tracking point test task and the second tracking point task of the application that the tracking point test task targets has been launched.

[0027] In an optional embodiment, the method for determining the tracking task to be verified includes: obtaining the value of a preset field in the tracking reporting information, and determining the tracking task to be verified according to the value of the preset field; wherein the preset field is used to indicate the version of the application client, and the tracking task to be verified includes the online tracking task corresponding to the version of the application client.

[0028] In an optional embodiment, the buried point verification device also includes: a quantity display module, the quantity display module includes an update unit and a display unit, the update unit is configured to update the first quantity and the second quantity according to the received buried point reporting information; the display unit is configured to respond to the operation of requesting to display the verification result of the first verification mode, and display the first quantity and the second quantity corresponding to the buried point reporting event; wherein, the first quantity includes the number of buried point reporting events indicated by the buried point reporting information, and the second quantity includes the number of buried point pits corresponding to the buried point reporting events indicated by the buried point reporting information.

[0029] In an optional embodiment, the buried point verification device also includes a module for sequentially displaying verification results, and the module for sequentially displaying verification results is configured to respond to an operation requesting to display verification results of a first verification mode, and sequentially display verification results of buried point reporting information according to a reporting time of the buried point reporting information.

[0030] In an optional embodiment, when the burying point reporting information includes burying point reporting information corresponding to the burying point test task, the device also includes a task completion verification module, and the task completion verification module is configured to determine the target burying point positions including burying point parameters of enumeration type; when each enumeration value of each target burying point position is matched successfully, it is determined that the burying point test task test is completed.

[0031] In an optional embodiment, the burial point verification device also includes a candidate verification module, which is configured to: for the target burial point parameters in the burial point reporting information that are not constrained by the verification rule description, verify the target burial point parameters according to a candidate value library pre-associated with the target burial point parameters.

[0032] In an optional embodiment, the burrowing point verification device also includes a quantity update module, and the quantity update module is configured to: update one or more of a third quantity, a fourth quantity, a fifth quantity, a sixth quantity, and a seventh quantity according to the burrowing point attribution parameter value in the burrowing point reporting information; wherein the third quantity is used to characterize the number of burrowing point reporting information with empty burrowing point attribution parameter values, the fourth quantity is used to characterize the number of burrowing point reporting information with illegal burrowing point attribution parameter values, the fifth quantity is used to characterize the number of burrowing point reporting information with unreasonable burrowing point attribution parameter values, the sixth quantity is used to characterize the number of burrowing point reporting information with downgraded burrowing point attribution parameter values, and the seventh quantity is used to characterize the types of burrowing point reporting events corresponding to the burrowing point reporting information. the number of burial point attribution parameter values; wherein, when the pit position indicated by the pit position information in the burial point attribution parameter value does not belong to the burial point pit position, it is determined that the burial point attribution parameter value is illegal; when the to-be-confirmed pit position indicated by the pit position information in the burial point attribution parameter value belongs to the burial point pit position, but the to-be-confirmed pit position fails to match the pit position information in the candidate burial point attribution parameter value of the burial point reporting event corresponding to the burial point reporting information, it is determined that the burial point attribution parameter value is unreasonable; when the burial point attribution parameter value includes a preset field identifier, it is determined that the burial point attribution parameter value is downgraded, and the preset field identifier is used to identify the burial point attribution parameter value generated after triggering the pit position without a burial point object in the application client.

[0033] In an optional embodiment, the buried point verification device also includes a detail display module, which is configured to: for any application client, record the buried point reporting information of the application client according to the reporting time sequence of the buried point reporting information, respond to the query request for the target buried point reporting information, obtain other buried point reporting information whose reporting sequence is within a preset range with the target buried point reporting information, so as to display the target buried point reporting information and the other buried point reporting information.

[0034] In an optional embodiment, the tracking point reporting information includes tracking point reporting information generated by the application client according to the test case of the tracking point test task, wherein the test case is generated based on the tracking point position to be tested of the tracking point test task.

[0035] In an optional embodiment, when the tracking point reporting information includes tracking point reporting information corresponding to the tracking point test task, the tracking point verification device also includes an integrity verification module, and the integrity verification module is configured to: simulate the test data corresponding to the test link in the tracking point test task through a virtual object, so as to perform integrity verification on the tracking point test task based on the test link.

[0036] According to a third aspect of an embodiment of the present disclosure, there is provided a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the method for checking buried points described in the first aspect is implemented.

[0037] According to the fourth aspect of the embodiment of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the buried point verification method described in the first aspect above by executing the executable instructions.

[0038] According to the method for checking the buried point, the device for checking the buried point, the computer-readable storage medium and the electronic device of the embodiment of the present disclosure, in the case of receiving the buried point report information of the application client, in response to the buried point report information including the pit position information, the pit position information is matched with the pit position in the target pit position library; according to the matching result, the buried point report information can be checked based on the target verification rule library; wherein the target pit position library and the target verification rule library are determined according to the buried point in the buried point task to be checked. On the one hand, the present disclosure verifies the buried point information based on the pit position, and can verify the number and omission of buried points, thereby improving the accuracy of the buried point verification; on the other hand, the present disclosure determines the target verification rule library based on the buried point task to be checked, and then can automatically perform buried point verification on the buried point tasks corresponding to the development, integration, grayscale, and release of the buried point in each stage after the online release, thereby improving the efficiency of the buried point verification, and when the buried point task to be checked is a buried point task in the development stage, the buried point can be verified in the development stage to find the buried point problem as early as possible before the buried point goes online. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The above and other objects, features and advantages of the exemplary embodiments of the present disclosure will become readily understood by reading the detailed description below with reference to the accompanying drawings. In the accompanying drawings, several embodiments of the present disclosure are shown in an exemplary and non-limiting manner, in which:

[0040] Figure 1 A schematic diagram of a method for checking buried points according to an embodiment of the present disclosure is shown;

[0041] Figure 2 A flow chart of a method for verifying the reported information of a buried point according to the pit position matching result according to an embodiment of the present disclosure is shown;

[0042] Figure 3 A schematic diagram of a tracking point parameter configuration page according to an embodiment of the present disclosure is shown;

[0043] Figure 4 A schematic diagram of another method for checking buried points according to an embodiment of the present disclosure is shown;

[0044] Figure 5 A flow chart of a method for determining whether a tracking test task is completed according to an embodiment of the present disclosure is shown;

[0045] Figure 6 A schematic diagram of a multi-terminal interaction process when performing a buried point verification according to an embodiment of the present disclosure is shown;

[0046] Figure 7 A flow chart showing another method for real-time verification of an online tracking task according to an embodiment of the present disclosure is shown;

[0047] Figure 8 A flow chart of a method for manual bill of lading follow-up point verification according to an embodiment of the present disclosure is shown;

[0048] Fig. 9 A schematic structural diagram of a buried point verification device according to a disclosed embodiment is shown;

[0049] Fig.10 A structural diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0050] In the drawings, the same or corresponding reference numerals represent the same or corresponding parts. DETAILED DESCRIPTION

[0051] The principles and spirit of the present disclosure will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present disclosure, and are not intended to limit the scope of the present disclosure in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0052] Those skilled in the art will appreciate that the embodiments of the present disclosure may be implemented as a system, device, apparatus, method or computer program product. Therefore, the present disclosure may be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0053] According to an embodiment of the present disclosure, there are provided a method for verifying a buried point, a device for verifying a buried point, a computer-readable storage medium and an electronic device.

[0054] In this document, any number of elements in the drawings is used for illustration rather than limitation, and any naming is used only for distinction and does not have any limiting meaning.

[0055] The principle and spirit of the present disclosure are explained in detail below with reference to several representative embodiments of the present disclosure. SUMMARY OF THE INVENTION

[0056] The inventors of the present disclosure have found that in some existing tracking verification schemes, only the correctness of tracking is concerned, and the over-reporting or under-reporting of tracking cannot be verified, so the accuracy of the verification is insufficient. In other existing tracking verification schemes, problems can only be discovered based on the fluctuations of new and old tracking data after going online. The problem discovery cycle is long, and it depends on the user coverage of the new version to reach a certain proportion to accurately discover problems based on the fluctuations of new and old data, resulting in low efficiency of tracking verification. In addition, problems can only be discovered after the tracking is online, and there is a defect of delayed problem discovery.

[0057] In view of the above content, the basic idea of ​​the present disclosure is to provide a vital sign buried point verification method, a buried point verification device, a computer-readable storage medium and an electronic device. When receiving the buried point reporting information of the application client, in response to the buried point reporting information including the pit position information, the pit position information is matched with the pit position in the target pit position library; according to the matching result, based on the target verification rule library, the buried point reporting information can be verified, wherein the target pit position library and the target verification rule library are determined according to the buried points in the buried point task to be verified. On the one hand, the present invention verifies the tracking information based on the pit position, which can verify the excess and omission of tracking points and improve the accuracy of tracking verification; on the other hand, the present invention determines the target verification rule library based on the tracking task to be verified, and then can automatically perform tracking verification on the tracking tasks corresponding to the various stages of tracking development, integration, grayscale, and release and online, thereby improving the efficiency of tracking verification. Moreover, when the tracking task to be verified is a tracking task in the development stage, the tracking can be verified in the development stage to discover tracking problems as early as possible before the tracking goes online.

[0058] After introducing the basic principles of the present disclosure, various non-limiting embodiments of the present disclosure are described in detail below.

[0059] Application Scenario Overview

[0060] It should be noted that the following application scenarios are only shown to facilitate understanding of the spirit and principle of the present disclosure, and the embodiments of the present disclosure are not limited in this respect. On the contrary, the embodiments of the present disclosure can be applied to any applicable scenario.

[0061] The present disclosure can be applied to scenarios where data is collected. For example, the tracking point verification method provided by the present disclosure can be used to verify the tracking points in the development stage. After the verification is passed, the tracking points are put online to collect application usage data (such as the number of visits, the number of visitors, the length of stay, the number of page views, etc.), so as to track the use of the application and provide data support for further optimization of the application. In the information recommendation scenario, the tracking point verification method provided by the present disclosure can be used to verify the collected historical data related to the user's behavior to determine whether the collected historical data related to the user's behavior is accurate, and then accurately portray the user portrait to recommend information to the user.

[0062] The present disclosure can also be applied to scenarios for optimizing application clients. For example, after the tracking point is launched, the tracking point information reported by the application client can be verified according to the tracking point verification method of the present disclosure, and the verification results can be counted and then analyzed to determine which pages or controls in the application client need to be optimized, thereby improving the user's interactive experience.

[0063] Exemplary Methods

[0064] The tracking verification scheme in the related technology only focuses on whether the tracking is correct or not, and cannot verify the over-reporting or under-reporting of the tracking, resulting in insufficient accuracy of the tracking verification. In addition, in other tracking verification schemes, problems can only be discovered based on the fluctuations of the new and old tracking data after going online. The problem discovery cycle is long, and it depends on the user coverage of the new version to reach a certain proportion to accurately discover problems based on the fluctuations of the new and old data, resulting in low efficiency of tracking verification. In addition, it can only discover problems after the tracking is online, and there is a defect of delayed detection of tracking problems.

[0065] The exemplary embodiments of the present disclosure first provide a buried point verification method to at least overcome all or part of the above-mentioned defects existing in the related art.

[0066] Figure 1 A method for checking buried points in an exemplary embodiment of the present disclosure is shown, which may include:

[0067] Step S110, receiving the tracking point reporting information from the application client, and in response to the tracking point reporting information including the pit location information, matching the pit location information with the pit location in the target pit location library;

[0068] Step S120, verifying the buried point reporting information based on the matching result and the target verification rule library;

[0069] Among them, the target pit location library and the target verification rule library are determined according to the buried points in the buried point tasks to be verified.

[0070] The following are Figure 1 Provide detailed instructions for each step.

[0071] Step S110, receiving the tracking point reporting information from the application client, and in response to the tracking point reporting information including the pit location information, matching the pit location information with the pit location in the target pit location library.

[0072] In an exemplary implementation, the application client in step S110 may include a tracking point test task application client, wherein the tracking point test task application client may be understood as an application client used by developers when testing the developed tracking point tasks.

[0073] When the tracking point developer tests the tracking point task, the application client used is the client corresponding to the application to be tested. For example, the tracking point developer modified the tracking point of the 1.0 version of the application to complete the development of the new tracking point task. After completion, the new tracking point task can be merged with the tracking point task of the 1.0 version of the application to generate the application to be tested, and then the generated application to be tested can be installed in any terminal device to obtain the client of the application to be tested.

[0074] In the case where the application client in step S110 includes an application client used by a developer when testing a developed tracking task, the tracking reporting information in step S110 may include tracking reporting information corresponding to the tracking test task.

[0075] Testing and verifying the tracking points during the tracking point testing phase can, to a large extent, ensure the accuracy and completeness of the newly added tracking points during the tracking point task development process. However, considering that the tracking point test is often on the required development code branch, that is, each developer is responsible for testing the tracking point task branch developed by him, it may still be modified after the test is completed, and in the process of merging the newly added tracking points of other branches into the main release branch, there may also be other conflicts, resulting in modifications to the tracking points after the test is completed. In other words, the tracking point task branch after the test is completed is still a certain distance away from the code for synthesis, grayscale, and full launch, and there is still a possibility of change. Therefore, after the tracking point test is completed, the tracking point verification method disclosed in the present invention can be used to verify the status of tracking point task integration, grayscale, and post-launch status.

[0076] Grayscale release refers to a release method that can smoothly transition between black and white. A / B testing can be performed on it, that is, some users continue to use product feature A, and some users start using product feature B. If users have no objection to B, then gradually expand the scope and migrate all users to B. Grayscale release can ensure the stability of the overall system. Problems can be discovered and adjusted during the initial grayscale to ensure their impact, that is, control some users to use the latest release version. Full release means that after clicking on the release, all users will use the current latest release version when accessing the program.

[0077] Based on this, in another exemplary embodiment, the application client of step S110 may include any application client corresponding to the synthesis, grayscale, or full release of the tracking task. For an application, different versions will be generated with continuous optimization and upgrading. Therefore, different users may use different versions of the application, and the application client in step S110 may include any version of the application client.

[0078] In other words, the tracking point verification method provided by the exemplary embodiment of the present disclosure can verify the tracking points during the tracking point testing phase, and can also continue to verify the tracking point information reported by the application client after the tracking point task is synthesized or launched, so as to promptly check for problems that were not discovered during the tracking point task testing, thereby verifying the tracking points in all aspects and improving the accuracy of the tracking point reported information.

[0079] In an exemplary application scenario, when a trigger operation occurs in an application client, the application client can report the burying point information corresponding to the trigger operation. Then, the burying point information reported by the application client can be verified.

[0080] Exemplarily, it is possible to determine whether the location information is included in the location reporting information, and verify the location reporting information based on the determination result.

[0081] For example, if the tracking point reporting information contains the field identifier corresponding to the pit location information, it can be determined that the tracking point reporting information contains the pit location information. Otherwise, it can be determined that the tracking point reporting information does not contain the pit location information, that is, the currently reported tracking point information may be an event tracking point, etc. Taking the use of the field identifier spm (Super Content Model, which refers to the parameter field that expresses the pit location in the tracking point reporting information) to identify the tracking point pit location information as an example, when the spm field is included in the tracking point reporting information, it can be determined that the tracking point reporting information includes the pit location information.

[0082] When it is determined that the tracking point reporting information contains pit location information, the pit location information in the tracking point reporting information can be matched with the pit locations in the target pit location library to verify the tracking point reporting information.

[0083] Among them, the target pit location library is determined according to the buried points in the buried point task to be verified. That is, the target pit location library is determined according to the pit locations corresponding to the buried points in the buried point task to be verified.

[0084] In an exemplary embodiment, when the tracking point reporting information in step S110 includes the tracking point reporting information corresponding to the tracking point test task, the tracking point tasks to be verified include the first tracking point task in the tracking point test task and the second tracking point task for which the application targeted by the tracking point test task has been launched.

[0085] For example, the tracking point verification method disclosed in the present invention can perform real-time tracking point testing and verification based on tracking point task requirements. Developers can perform real-time testing and verification on the tracking point tasks they are responsible for developing, that is, when performing tracking point testing, they can select specific tracking point tasks. For tracking point test tasks, when verifying them, the target tracking point library can be determined based on all the tracking points that have been released and launched by the application and the tracking points in the tracking point tasks to be tested (not released and launched).

[0086] For developers, each time they develop a new tracking task, they can add, modify, delete, and perform one or more operations based on the tracking tasks corresponding to a certain version of the application (already launched). Usually, one or more operations such as adding, modifying, and deleting are performed on the basis of the tracking tasks corresponding to the latest version of the application to complete the development of the new tracking task. The tracking tasks in the latest version of the application have been released and launched, so when the tracking reporting information includes the tracking reporting information corresponding to the tracking test task, the tracking tasks to be verified include the first tracking task in the tracking test task and the second tracking task of the application that the tracking test task targets, which has been launched.

[0087] Of course, developers can also develop new tracking tasks based on any historical version of the application as needed, and this exemplary embodiment does not specifically limit this. When developers develop new tracking tasks based on any historical version of the application, the tracking tasks to be verified can include the current tracking tasks to be tested and the tracking tasks corresponding to the historical version of the application.

[0088] In an exemplary application scenario, after the developer completes the development of a new tracking task on the tracking management platform, he can select the new tracking task on the tracking management platform, and then use the client corresponding to the historical version of the application corresponding to the new tracking task that has been launched (such as the current latest version) to scan the code to log in to the tracking management platform. Since the developer scans the code to log in, the version of the application client used by the developer can be obtained when scanning the code to log in. According to all the tracking tasks that have been launched corresponding to the version of the application client used by the developer and the tracking tasks to be tested manually selected by the developer (that is, the new tracking tasks completed by the developer), the tracking tasks to be verified can be determined, so as to determine the target pit library and the target verification rule library according to the tracking tasks to be verified, so as to perform verification tests on the tracking tasks to be tested.

[0089] In the present disclosure, when conducting tracking task testing, since the tracking tasks to be verified include both the currently newly developed tracking tasks and the historical tracking tasks that have been launched, the new and old tracking points can be verified at the same time to test whether the new tracking tasks affect the correctness of the old tracking tasks, avoiding changing the correct old tracking points into incorrect tracking points during the development of the new tracking tasks, thereby further improving the accuracy of the tracking verification.

[0090] In another exemplary embodiment, the method for determining the tracking task to be verified in step S110 may include: obtaining the value of a preset field in the tracking report information, and determining the tracking task to be verified according to the value of the preset field. The preset field is used to indicate the version of the application client, and the tracking task to be verified includes the tracking task that has been launched corresponding to the version of the application client.

[0091] As mentioned above, in order to ensure the comprehensiveness of tracking verification, tracking can be verified at various stages after code integration, grayscale release, and full release, so as to find tracking problems as early as possible and correct them in time. However, for code integration, grayscale release, and full release, it is not possible to determine the tracking tasks to be verified through the tracking tasks to be tested selected by the developer and the active scanning code login method as in the testing phase.

[0092] Based on this, in order to ensure that the tracking points can be automatically verified in each stage of tracking task testing, integration, grayscale release, and full release, it is also possible to carry preset fields in the tracking point reporting information and determine the version of the application client corresponding to the currently reported tracking point information through the value of the preset field.

[0093] For example, when packaging the tracking point reporting information, the unique UUID (Universally Unique Identifier) ​​corresponding to the application client version can be embedded in the tracking point reporting information according to the version of the application client. At the same time, the mapping relationship between each UUID and the corresponding application client version is saved in the tracking point management platform. In this way, when the tracking point management platform (i.e., the server) receives the tracking point reporting information, it can find the application client version corresponding to the UUID according to the UUID in the tracking point reporting information, and then determine the tracking point tasks to be verified according to the tracking point tasks that have been launched for the application client version.

[0094] For the tracking test phase, the tracking tasks to be verified are the online tracking tasks corresponding to the determined application version and the tracking tasks to be tested selected by the developer. For the stages of tracking task integration, grayscale release, and full release, the tracking tasks to be verified are all the online tracking tasks corresponding to the determined application client version.

[0095] Through the method disclosed in the present invention, the tasks to be verified in each stage of the buried point test, integration, grayscale, and release can be accurately determined, so that the benchmark for buried point verification (i.e., the target pit library and the target verification rule library) can be accurately determined based on the buried point tasks to be verified, and the buried points can be automatically verified at each stage, thereby improving the efficiency of the buried point verification.

[0096] Exemplarily, after determining the burying point task to be verified, the target pit location library can be determined based on the pit locations in the burying point task to be verified. When the burying point information to be reported includes pit location information, the pit location information in the burying point information to be reported can be matched with the pit locations in the target pit location library to determine the verification result of the burying point reporting information based on the matching result.

[0097] Continue to refer Figure 1 In step S120, according to the matching result, based on the target verification rule library, the buried point reporting information is verified.

[0098] Among them, the target verification rule base is determined according to the embedded points in the embedded point task to be verified. In other words, the target verification rule base includes parameter configuration rules corresponding to the embedded points in the embedded point task to be verified. The method for determining the embedded point task to be verified has been described in detail in the above-mentioned step S110, which can be referred to and will not be repeated here.

[0099] For example, Figure 2 The following is a flow chart showing a method for verifying the reported information of a buried point according to the pit position matching result according to an embodiment of the present disclosure. Figure 2, the method may include steps S210 to S240.

[0100] In step S210, the pit location information in the burial point reporting information is matched with the pit location in the target pit location library. In response to a successful match, the process proceeds to step S220. In response to a failed match, the process proceeds to step S240.

[0101] In step S220, the burial point object identifier included in the pit location information is obtained.

[0102] In an exemplary embodiment, a pit location can be understood as a unique location that can be described in a client application.

[0103] A page can be understood as an entire area that is exclusively displayed at a certain user interface level, such as a newly opened underlying page, a TAB (tab bar / tab), a channel, etc.; a page is generally used to organize a lot of content for distribution or as the actual function carrier of a single content. Information such as page flow exposure and dwell time is of great significance for application analysis. An element can be understood as a UI (User Interface) component and / or unit that can be interacted with by users on a page, such as a list unit, a button, a slidable content module, etc. Lists and modules are generally used to carry content distribution, and their click-through rate has analytical significance for the content distribution effect. Buttons are generally used to carry user interaction, and buttons are usually mounted on the underlying page of a content unit or content function.

[0104] Both pages and elements can be used as tracking objects. A page can include subpages and elements. For a page, the page itself, the subpages and elements in the page can be used as tracking objects in the page. Users can customize the settings according to their needs.

[0105] Exemplarily, in response to a trigger operation on an application client, a page node tree of a target display page exposed by the trigger operation may be determined, and then a buried point object tree may be generated based on the attribute information of the nodes in the page node tree. For example, a buried point object tree may be generated based on nodes in the page node tree that are configured with buried point object identifiers.

[0106] After generating the burying point object tree, the burying point object identification chain from the burying point object to the root object in the burying point object tree can be determined based on the parent-child relationship in the burying point object tree and the burying point object identification pre-configured for the burying point object in the burying point object tree, and the location attribute information of the burying point object can be added to the burying point object identification chain to obtain the pit information of the burying point object.

[0107] The Object Id (OID) is the client-side identifier of the page or element being tracked. The same OID can be used to represent the same UI style, the same content unit, the same interactive form, or a specific UI location on the client. When developing tracking, developers can configure the Object Id for each tracking object.

[0108] Considering that there are some repeated types of elements with the same level in the page, for example, the object identifier of each list element in the list reuse unit is the same and belongs to the same level, that is, the object identifier of each list element in the list reuse unit is the object identifier of the list unit, and the level of each list element is the level of the list unit. In this case, if only the embedding object identifier chain is used to represent the pit position information of the embedding object, it is impossible to distinguish which element in the list unit is currently exposed, which will affect the accuracy of the embedding information reporting.

[0109] In order to solve this problem, in an optional implementation, the location attribute information of the burial point object can be added to the burial point object identification chain to obtain the pit location information in the burial point reporting information.

[0110] For example, the currently exposed burying point object is _oid1, the burying point object identifier of its parent node in the burying point object tree is oid2, the parent node of its parent node is the root node, and the burying point object identifier of the root node is oid3, where the position attribute information of oid2 is pos2, then the pit position information in the burying point reporting information corresponding to the burying point object can be expressed as oid1|oid2:pos2|oid3. Then, the current value of the burying point parameter associated with each burying point object identifier in the pit position information can be reported.

[0111] When verifying the buried point reporting information, the buried point parameters associated with the buried point object indicated by the buried point object identifier in the pit information can be verified. Therefore, the buried point object identifier included in the pit information can be obtained.

[0112] In step S230, for each burying point object identifier, based on the verification rule of the first burying point parameter associated with the burying point object identifier in the target verification rule library, the first burying point parameter in the burying point reporting information is verified.

[0113] Among them, the first burying point parameter associated with the burying point object identifier can be understood as a private parameter of the burying point object indicated by the burying point object identifier.

[0114] For example, Figure 3 A schematic diagram of a point tracking parameter configuration page according to an embodiment of the present disclosure is shown. Figure 3It can be seen that for the tracking point object, it can be configured with private parameters (that is, the first tracking point parameter mentioned above), and can also be configured with event parameters and global public parameters.

[0115] Among them, private parameters can be understood as parameters that only belong to a certain embedding object indicated by a certain embedding object identifier. Event parameters can be understood as parameters that need to be reported when a corresponding event occurs on the client. For example, in the embedding management platform, the page exposure event is configured as a embedding reporting event, and the page exposure event is associated with event parameter 1. The page exposure event is configured for embedding object 1. Then, when embedding object 1 is exposed, event parameter 1 corresponding to the page exposure event needs to be reported. Figure 3 In the example, the page exposure start event and page exposure end event are configured for page1, which means that when page1 starts or ends exposure, the event parameter 1 associated with the corresponding page exposure start event or page exposure end event needs to be reported. Global public parameters can be understood as parameters that can be configured for any tracking object in the entire application client, that is, they are not parameters that can only belong to a specific tracking object indicated by a tracking object identifier. Figure 3 The global public parameter V1 in .

[0116] For example, tracking point developers can pre-configure corresponding tracking point parameters for each tracking point object in the tracking point management platform, such as Figure 3 In the page shown, the corresponding tracking point parameters are configured for each tracking point object, and the corresponding value rules are configured for each tracking point parameter. The value rules can be used as the verification rules for the tracking point parameters.

[0117] Exemplarily, for each burying point object identifier included in the pit information, the current value of the first burying point parameter associated with the burying point object identifier can be matched with the value rule of the first burying point parameter in the target verification rule library. If the match fails, the first burying point parameter verification fails. For example, if the value rule of a first burying point parameter is 0 or 1, and in the current burying point reporting information, when the value of the first burying point parameter is any value of 0 or 1, the current verification of the first burying point verification parameter is successful, but if the value of the first burying point parameter is other than 0 or 1, such as 5, the current verification of the first burying point verification parameter fails.

[0118] In other words, it can be determined whether the value of each first burial point parameter with a value-taking rule in the current burial point reporting information is within the range constrained by the corresponding value-taking rule. If so, the current verification of the first burial point parameter is successful; if not, the current verification of the first burial point parameter fails.

[0119] In step S240, a label indicating that the pit location matching failed is added to the tracking point reporting information.

[0120] For example, in response to receiving the tracking point reporting information, it can be determined whether the tracking point reporting information contains the pit location information. If the tracking point reporting information contains the pit location information, the pit location contained in the tracking point reporting information can be matched with the pit location in the target pit location library. If the match is successful, it means that the tracking point information to be reported is the reporting information generated by the pit location in the tracking point task. If the match fails, it means that the tracking point information to be reported is not the reporting information generated by the pit location in the tracking point task, and a pit location matching failure label can be added to the tracking point reporting information.

[0121] Exemplarily, when the pit information is matched successfully, a label of successful pit match can also be added to the successfully matched buried point reporting information. In this way, through pit matching and the added labels of successful pit match or failed pit match, it is possible to check whether there are too many or too few buried points. For example, the pits that have not been successfully matched are the buried point pits that are not needed in the buried point task, that is, the over-buried pits. If after all the test operations of the buried point task to be tested are completed, there is no pit in the buried point task to be tested in the successfully matched pits, then the pit is the under-buried pit.

[0122] As mentioned above, the parameters of the burying point object can also include one or more event parameters or public parameters. Based on this, after receiving the burying point reporting information from the application client, it is also possible to determine the second burying point parameter associated with the burying point reporting event that triggers the burying point reporting information, and verify the second burying point parameter in the burying point reporting information according to the verification rules of the second burying point parameter in the target verification rule library; and / or verify the public parameters in the burying point reporting information according to the verification rules corresponding to the public parameters in the target verification rule library. Among them, the second burying point parameter can be understood as the above-mentioned event parameter.

[0123] For example, after receiving the tracking point reporting information from the application client, the parameter identification field in the tracking point reporting information can be matched with the event parameter identification field and the global parameter identification field in the target verification rule library to determine the event parameters and global parameters in the tracking point reporting information. Then, the current value of the event parameter or global parameter determined in the tracking point reporting information is matched with the value taking rule of the event parameter or global parameter in the target verification rule library to determine whether the current value is within the value range constrained by the corresponding value taking rule, so as to verify the event parameter and global parameter in the tracking point reporting information. At the same time, in the case where the tracking point reporting information includes pit information, the private parameters associated with each tracking point object in the pit information can also be verified according to the above-mentioned steps S210 to S240.

[0124] For example, Figure 4 FIG. 2 is a flow chart showing another method for checking buried points according to an embodiment of the present disclosure. Figure 4 , the method may include steps S401 to S412. Wherein:

[0125] In step S401, receive the buried point report information; in step S402, determine whether there is pit location information in the buried point report information, if yes, go to step S403, otherwise go to step S411; in step S403, match the pit location information in the buried point report information with the pit location in the target pit location library; in step S404, determine whether the pit location information is matched successfully, if the match is successful, go to step S405, otherwise go to step S412; in step S405, determine the buried point object list corresponding to the buried point object contained in the pit location information of the buried point report information; in step S406, determine whether the buried point object list is empty, if yes, go to step S411, otherwise, go to step S407 to step S410; in step S407, obtain the buried point The first burial point object in the object list; in step S408, determine whether the first burial point object is configured with private parameter rules, if so, go to step S409, otherwise, go to step S411; in step S409, traverse the private parameter rules of the first burial point object to verify the private parameters of the first burial point object in the burial point reporting information; in step S410, after the private parameter verification of the first burial point object is completed, delete the first burial point object from the burial point object list, and continue to go to step S406; in step S411, traverse the event parameters and public parameters, and verify the values ​​of the traversed event parameters and public parameters according to the target verification rule library; in step S412, add a label of pit position matching failure to the current burial point reporting information.

[0126] For example, after receiving the burying point report information, it can be determined whether there is pit information in the burying point report information. If there is no pit information, the event parameters and / or public parameters in the burying point report information are directly verified. If there is pit information, the pit information in the burying point report information is matched with the pit in the target pit library (the target pit library is determined based on the burying point pit in the burying point task to be verified). If the match fails, a pit match failure mark is added to the burying point report information; if the match is successful, the burying point object list corresponding to the burying point object contained in the pit information is determined, and each burying point object in the burying point object list is traversed. For the traversed burying point objects, it is determined whether the burying point object is configured with private parameters. If so, the private parameters are verified. If not, the public parameters or event parameters configured for the burying point object are verified. After traversing the burying point object list, other event parameters or public parameters in the burying point report information can also be verified.

[0127] Of course, after receiving the buried point reporting information, it is also possible not to determine whether there is pit position information in the buried point reporting information, but to directly verify the public parameters and / or event parameters in the buried point reporting information according to the public parameters and / or event parameters in the target verification rule library. After the verification of the public parameters and / or event parameters is completed, it is determined whether there is pit position information in the buried point reporting information. If there is no pit position information, the verification of the buried point reporting information is terminated. If there is pit position information, the pit position information is matched with the pit position in the target pit position library. For the pit position information that is successfully matched, the buried point object in the pit position information is obtained, and the value of each private parameter of each buried point object in the pit position information in the current buried point reporting information is verified according to the verification rules of the private parameters of the buried point object in the target verification rule library. For the pit position information that fails to match, a label of pit position matching failure is directly added to it. This exemplary embodiment does not make special limitations on this.

[0128] In an exemplary embodiment, when performing a tracking point test, the tester can manually operate to trigger the tracking point report, thereby obtaining the tracking point report information. In order to further improve the accuracy of the tracking point test, during the tracking point test phase, the number of each type of tracking point report event occurring on the client and the number of pits corresponding to the tracking point report event can be counted, so that the tester can find out the excess and omission of tracking point report information.

[0129] Based on this, the buried point verification method in the present invention may also include: updating the first quantity and the second quantity according to the received buried point reporting information; responding to the operation requesting to display the verification result of the first verification mode, displaying the first quantity and the second quantity corresponding to the buried point reporting event; wherein, the first quantity includes the number of buried point reporting events indicated by the buried point reporting information, and the second quantity includes the number of buried point pit positions corresponding to the buried point reporting events indicated by the buried point reporting information.

[0130] For example, when receiving the buried point reporting information, the buried point reporting event indicated by the buried point reporting information can be determined, and then the number of the buried point reporting events can be updated, that is, 1 is added to the number previously counted. The buried point reporting event indicated by the buried point reporting information can be understood as the event that causes the current buried point information to be reported. For example, if a page exposure event occurs currently, resulting in the reporting of this buried point information, the number of page exposure events is added by 1. It is also possible to determine whether the buried point reporting information contains a pit position. If so, it is determined whether the buried point reporting information has been generated in the current pit position during this test. If so, no processing is performed. If not, the number of buried point pit positions corresponding to the buried point reporting event indicated by the buried point reporting information can be updated, that is, 1 is added to the number of buried point pit positions corresponding to the buried point reporting event previously counted.

[0131] By updating the first and second numbers of statistics, the tester can analyze the accuracy of the timing of the embedding and the accuracy of the number of embeddings. For example, in a certain embedding task, embedding is performed in 7 pits for the page exposure event, and the tester performs 16 operations during the test. After completing the test operation, the tester can trigger the first verification mode verification result display control, and then the first and second numbers corresponding to the embedding reporting events during the test can be displayed. If the first number is 16 and the second number is 7, the tester can determine that the embedding timing and the number of embedding pits of the embedding task are correctly developed.

[0132] In an exemplary embodiment, in response to a request to display the verification results of the first verification mode, the verification results of the buried point reporting information are displayed sequentially according to the reporting time of the buried point reporting information.

[0133] For example, after completing the test operation, the tester can trigger the first verification mode verification result display control, and then display the verification results of the buried point reporting information according to the order of the reporting time of the buried point reporting information. The latest buried point reporting information can be displayed at the front, or the latest buried point reporting information can be displayed at the end, and this exemplary embodiment does not specifically limit this. The verification results may include results such as verification passed, verification failed, and the pit location information was not matched and could not be verified. Among them, the pit location information was not matched, which can be understood as the pit location information is included in the buried point reporting information, but the pit location information is not successfully matched with the pit location in the target pit location library.

[0134] In other words, in the verification result display page of the first verification mode, one or more of the first quantity, the second quantity, and the display list of the verification results of the buried point reporting information displayed in sequence can be displayed. In the case where the verification result display page of the first verification mode includes a display list of the verification results of the buried point reporting information displayed in sequence, in response to the user's triggering operation on the verification result record of any buried point reporting information, the verification details of the buried point reporting information can be displayed. Among them, for the buried point reporting information that fails the verification, an error message prompt can be given near the parameters that failed the verification in its verification details to remind the tester of the error, so that the tester can find the problem as soon as possible and make corrections, thereby improving the test efficiency.

[0135] Exemplarily, when the tracking point reporting information includes the tracking point reporting information corresponding to the tracking point test task, Figure 5 A flowchart of a method for determining whether a tracking test task is completed according to an embodiment of the present disclosure is shown. Figure 5The method may include steps S510 to S520. In step S510, a target burying point position including burying point parameters of an enumerated type is determined; in step S520, when each enumerated value of each target burying point position is successfully matched, it is determined that the burying point test task test is completed.

[0136] For example, when verifying the tracking report information during the tracking test phase, in addition to the need to count the accuracy of the number of tracking positions to avoid the number of tracking positions being too many or too few, it is necessary to successfully match each enumeration value of each tracking parameter of each enumeration type in each tracking position before the tracking test task is determined to be completed and the tracking task is allowed to go online. This can more completely ensure the accuracy of the tracking of each tracking task branch.

[0137] In an exemplary scenario, when performing tracking verification, not all tracking parameters can be accurately constrained by describing rules to have a value range. For example, the value of a parameter can only be constrained by a rule to ensure that it cannot be empty, but its value range cannot be constrained by a rule.

[0138] Based on this, in an exemplary embodiment, the burial point verification method in the present disclosure may also include: for the target burial point parameters in the burial point reporting information that do not pass the constraint value range description of the verification rule, the target burial point parameters are verified according to a candidate value library pre-associated with the target burial point parameters.

[0139] For example, for parameters whose value range cannot be described by simple rules, the correctness of the value of the tracking parameter can be verified by associating it with the correct value pseudo table of the tracking parameter stored on the server (that is, the candidate value library mentioned above), and verifying the correctness of the value of the tracking parameter by inclusion judgment. That is, the parameter is verified by judging whether the value of the parameter successfully matches a value in the correct value pseudo table.

[0140] Taking the NetEase Cloud Music client as an example, for example, the value of the song name parameter cannot be constrained by simple rules, but it is known which songs are included in the NetEase Cloud Music playlist library. Then, for the reported song name parameter, it can be determined whether the corresponding song name is in the playlist library. If so, the verification passes, otherwise, the parameter verification fails.

[0141] Furthermore, in the present disclosure, in each stage of tracking point development and testing, tracking point integration, grayscale release, and full release, in addition to performing value rule verification and statistical verification on the values ​​of tracking point parameters (such as the verification of the first quantity, the second quantity, and the enumeration type parameters mentioned above), tracking point attribution verification can also be performed, that is, it can be verified whether the values ​​of the attribution parameters in the tracking point reporting information are correct.

[0142] Based on this, the burrowing point verification method in the present disclosure may also include: updating one or more of the third quantity, the fourth quantity, the fifth quantity, the sixth quantity, and the seventh quantity according to the burrowing point attribution parameter value in the burrowing point reporting information, wherein the third quantity is used to characterize the number of burrowing point reporting information with empty burrowing point attribution parameter values, the fourth quantity is used to characterize the number of burrowing point reporting information with illegal burrowing point attribution parameter values, the fifth quantity is used to characterize the number of burrowing point reporting information with unreasonable burrowing point attribution parameter values, the sixth quantity is used to characterize the number of burrowing point reporting information with downgraded burrowing point attribution parameter values, and the seventh quantity is used to characterize the number of burrowing point attribution parameter values ​​of each type of burrowing point reporting events corresponding to the burrowing point reporting information.

[0143] In an exemplary embodiment, when the pit location indicated by the pit location information in the burial point attribution parameter value does not belong to the burial point pit location, the burial point attribution parameter value is determined to be illegal; when the pit location to be confirmed indicated by the pit location information in the burial point attribution parameter value belongs to the burial point pit location, but the burial point to be confirmed fails to match the pit location information in the candidate burial point attribution parameter value of the burial point reporting event corresponding to the burial point reporting information, the burial point attribution parameter value is determined to be unreasonable; when the burial point attribution parameter value includes a preset field identifier, it is determined that the burial point attribution parameter value is downgraded, and the preset field identifier is used to identify the burial point attribution parameter value generated after triggering the pit location without a burial point object in the application client.

[0144] For example, statistics can be summarized for situations such as empty attribution, illegal attribution slot, unreasonable attribution slot, attribution degradation, and attribution type distribution to verify the embedding points, and then the problems existing in the current embedding points can be analyzed based on the summary results to optimize the embedding points.

[0145] For example, based on the seventh quantity mentioned above, the distribution of the attribution parameter values ​​of each type of buried point reporting events can be determined. Taking the song playing event in the NetEase Cloud Music client as an example, after the new buried point task is fully launched, the number of different types of buried point attribution parameter values ​​corresponding to the song playing event is counted for each version of the buried point task, such as the number of buried point attribution parameter values ​​for search types, the number of buried point attribution parameter values ​​for automatic play types, etc., and then the proportion of each type of buried point attribution parameter value is analyzed. Compare the current proportion with the proportion of the previous version to analyze the fluctuation of the song playing event buried point, and determine whether the buried point needs to be optimized or whether there is a problem with the buried point based on the fluctuation. For example, when the fluctuation exceeds a certain range, it is determined that there is a problem with the song playing event buried point, and then analyze the cause of the problem and optimize and correct it.

[0146] By verifying the attribution parameters of tracking points, it is possible to verify attribution errors caused by unreasonable business interactions and processing logic, as well as missed tracking points, thereby further improving the comprehensiveness of tracking point verification and helping to improve the accuracy of subsequent tracking points.

[0147] In an exemplary scenario, during any of the integration phase, grayscale release, and full release, when a problem occurs, the relevant site no longer exists, and it is often difficult to directly reproduce the problem (when it is not in the testing phase, developers can test locally with test packages and reproduce it), so the troubleshooting and confirmation of tracking point problems is often a pain point and requires a huge workload. Based on this, in the present disclosure, during the tracking point verification process, the tracking point before and after the problem occurs can be used as anchor points to provide users with the ability to query detailed tracking point log details in order to quickly locate the problem.

[0148] In an exemplary implementation, the tracking point verification method in the present disclosure may also include: for any application client, according to the reporting time sequence of the tracking point reporting information, recording the tracking point reporting information of the application client; responding to a query request for the target tracking point reporting information, obtaining other tracking point reporting information whose reporting sequence is within a preset range with the target tracking point reporting information, so as to display the target tracking point reporting information and other tracking point reporting information. Among them, the preset range can be customized according to the needs, such as the two tracking point reporting information before and after.

[0149] For example, the target tracking point reporting information can include tracking point reporting information that failed verification. For example, if the verification result of the 120th tracking point reporting information in the tracking point reporting information is verification failure, when the user log detail control associated with the 120th tracking point reporting information is clicked, the tracking point reporting information from 118 to 122 can be displayed. In this way, the user's operation path at the time can be automatically restored to assist R&D personnel in analyzing the cause of the error and improve the efficiency of tracking point problem troubleshooting.

[0150] In an exemplary application scenario, the tracking point reporting information in the present disclosure may include tracking point reporting information automatically generated based on a user's manual triggering operation on an application client.

[0151] In another exemplary application scenario, the tracking point reporting information in the present disclosure may also include tracking point reporting information generated by the application client according to the test case of the tracking point test task, wherein the test case is generated based on the tracking point position to be tested of the tracking point test task.

[0152] For example, in the present disclosure, the location of the buried point is determined based on the buried point object tree, which can accurately describe the location of each buried point. Therefore, in the buried point test task, test cases can be written according to the locations of all the buried point tasks to be verified, so as to send the covered user operation paths to the application test client, and implement comprehensive coverage testing before the buried point task goes online through the full traversal mode, so as to avoid the problem of incomplete buried point coverage caused by manual operation, improve the accuracy of the buried point test, and improve the test efficiency before the buried point task goes online. During the traversal process, the relevant buried points will be automatically diverted to the buried point management platform for verification, so as to output the verification results and realize the full automation of the buried point test verification.

[0153] At the same time, in the process of testing based on manual operations, if the existence of parameter values, whether they comply with the value rules, and whether they are in the candidate value library are all correct, it is impossible to further automatically and accurately verify the logic of "is it that?" For example, for the relevant playlist recommendation cards in the playlist details page of NetEase Cloud Music, even if their content values ​​can be verified by the playlist library (i.e., the candidate value library) in NetEase Cloud Music, if both playlist 1 and playlist 2 are in the playlist library, it is impossible to verify whether the current playlist is really "playlist 1" instead of "playlist 2". By writing test cases, the absolute correctness of the values ​​of the tracking point parameters can be verified based on the test cases. For example, if the test case writes that playlist 1 is triggered, the playlist reported in the tracking point reporting information can be compared with the playlist in the test case, so as to automatically verify the absolute correctness of the playlist content.

[0154] In an exemplary embodiment, when the tracking point reporting information includes the tracking point reporting information corresponding to the tracking point test task, the tracking point verification method in the present disclosure may also include: simulating the test data corresponding to the test link in the tracking point test task through a virtual object, so as to perform integrity verification on the tracking point test task based on the test link.

[0155] For example, although the user's usage data is personalized and its tracking results may be non-fixed and non-exhaustive, the pages, pits and logic that generate tracking in the corresponding client are limited and can be maintained. Based on this, for some more important scenarios, specific data can be issued through MOCK (simulation, during the test process, for some objects that are difficult to construct or difficult to obtain, a test method of buying simulation tests by creating virtual objects) to obtain the tracking results of each pit in the scene, thereby building a corresponding complete verification link to ensure the absolute accuracy of the indicator caliber of the core scenario. Of course, the integrity of the link can be verified based on MOCK for any scenario, and this exemplary embodiment does not make any special limitations on this.

[0156] Next, Figure 6 The following is a schematic diagram of a multi-terminal interaction process when performing a point-of-use verification according to an embodiment of the present disclosure. First, the client packaging process is as follows: Figure 6 As shown, in step S611, when the client is packaging the tracking point reporting information, a unique UUID is generated according to the client version; in step S612, the UUID is added to the package; in step S613, the package UUID, package information, and tracking point tasks to be verified are uploaded to the package information database of the server.

[0157] The second is the client log reporting process. For example, in step S621, the client obtains the UUID in the package; in step S622, the point reporting information and the UUID are reported to the server.

[0158] After the server receives the buried point reporting information, it can start the buried point verification process of the server. For the server buried point verification process, in step S631, the server can determine the buried point task to be verified corresponding to the buried point reporting information from the package information database according to the package UUID in the buried point reporting information, so as to determine the target verification rule library and the target pit location library according to the buried point task to be verified; in step S632, the buried point reporting information is subjected to rule verification according to the target verification rule library and the target pit location library, and statistical verification, attribution verification, and parameter value coverage verification can also be performed. After the verification is completed, the server can store the package UUID, buried point reporting information and verification results together in the log database.

[0159] The log database and the aforementioned package information database can assist the server in querying logs and reports. For example, complex conditions can be converted into a package list based on the package filtering conditions, which can avoid a large amount of complex package information being entered into the client package. Based on the query statement including the package UUID, filtering queries can be performed in the log database, so that logs that meet the auxiliary package filtering conditions can be obtained.

[0160] Figure 7 A flowchart of another method for real-time verification of an online tracking task according to an embodiment of the present disclosure is shown. Figure 7In step S701, the log format of the received tracking point reporting information is parsed; in step S702, the package UUID in the tracking point reporting information is extracted; in step S703, the local cache of the verification rules is obtained according to the package UUID; in step S704, the verification results are calculated, including rule verification, attribution verification, statistical verification (such as the first number, second number, third number, fourth number, fifth number, sixth number, and seventh number mentioned above), and parameter value coverage verification (such as the enumeration type parameters mentioned above are enumerated value coverage verification); in step S In step S705, the verification result is submitted to the queue; in step S706, the single-threaded processing flow obtains the verification result and submits it to the queue; in step S707, the private list to be submitted in the thread is written; in step S708, it is determined whether the number in the list to be submitted is greater than the preset value or whether the last write time occurs before the preset time length, if so, go to step S709, otherwise go to step S710; in step S709, the data in the list to be submitted is written to the database in batches, and the list to be submitted is cleared; in step S710, no processing is performed.

[0161] Among them, the above steps S701 to S705 can be processed by computing threads, each computing thread corresponds to a partition (part) of a message queue, so that multiple message queues or multiple partitions of a single thread can be processed simultaneously by multiple threads. In step S703, the verification rules can be cached in the local public storage area with the package UUID as the keyword and the rule as the value corresponding to the keyword. The verification result in step S705 can be stored in the public memory area, and then, in step S706, the single thread obtains the verification result from the queue in the public memory area.

[0162] By accumulating multiple verification results and writing them into the log database in batches, the number of concurrent writes can be reduced and the stability of writes can be improved.

[0163] As mentioned above, the present disclosure can realize the tracking point verification from different stages such as the tracking point task development stage, the tracking point task integration stage, the tracking point task gray stage, and the tracking point task online stage to ensure the comprehensiveness of the tracking point verification. Among them, in the demand development stage, the tracking point management platform can provide real-time upload and automatic verification capabilities of logs through webscoket (a protocol for full-duplex communication on a single TCP (Transmission Control Protocol) connection), and provide timely verification tests for demand-oriented incremental and historical stock tracking points; in the demand integration stage, by establishing an accurate association between the integrated product and the merged branches and tasks, clarifying the tasks to be verified, and using the internal manual use of the integrated product and the machine automatic traversal to realize the automatic verification of related tracking points; in the demand gray and online stages, the tracking points are further verified by diverting the online log identifier (i.e., UUID), and the fluctuation of the tracking points is counted, and the fluctuation is accurately verified. However, this may still not guarantee that all problems can be discovered 100% before going online.

[0164] Based on this, a closed-loop manual bill of lading and follow-up process can be established for the buried problems that cannot be discovered through automatic verification. Figure 8 As shown, in step S801, the business party and the algorithm party can first analyze whether there are problems with the reported data table based on their own experience; in step S802, if it is clear that there are problems with the data table, a list of data problems can be listed; in step S803, the R&D personnel of the data warehouse can analyze the causes of the problems in the problem list, such as analyzing whether it is a task abnormality, a point abnormality, a version problem, etc. For data problems that are determined to be point abnormalities, a list of point problems corresponding to the gray version and the full online version can be sorted out. In step S804, the problem can be confirmed and developed and repaired, and new and old points can be self-tested.

[0165] pass Figure 8 The process shown can promptly confirm and repair tracking problems that are discovered after going online, further ensuring the accuracy of tracking.

[0166] The data point verification method disclosed in the present invention can effectively realize the forward guarantee of data point quality, so as to discover data point problems as early as possible, and form effective problem discovery and interception in various stages such as demand development, integrated regression, grayscale launch, and full launch, which can reduce data point problems, speed up problem discovery, and improve problem location and resolution speed.

[0167] Furthermore, the tracking point verification method disclosed in the present invention is to perform verification on tracking point objects, which has good scalability and versatility and is applicable to any business and large front-end platform framework.

[0168] At the same time, the buried point verification method disclosed in the present invention can verify the buried points at various stages to comprehensively ensure the accuracy of the buried point data.

[0169] Exemplary Devices

[0170] The exemplary embodiment of the present disclosure also provides a buried point verification device. Fig. 9 As shown, the buried point verification device 900 may include: a buried point information receiving module 910 and a verification module 920. Among them:

[0171] The tracking point information receiving module 910 is configured to receive tracking point reporting information from the application client, and in response to the tracking point reporting information including pit location information, match the pit location information with the pit location in the target pit location library;

[0172] The verification module 920 is configured to verify the tracking point reporting information according to the matching result and based on the target verification rule library.

[0173] In an optional implementation, based on the aforementioned embodiment, the target pit location library and the target verification rule library are determined according to the burying points in the burying point task to be verified.

[0174] In an optional implementation, based on the aforementioned embodiment, the verification module 920 may be specifically configured as follows: in response to a successful match, obtaining the burial point object identifier included in the pit location information; for each burial point object identifier, verifying the first burial point parameter in the burial point reporting information based on the verification rule in the target verification rule base of the first burial point parameter associated with the burial point object identifier.

[0175] In an optional implementation, based on the foregoing embodiment, the verification module 920 may be specifically configured to: in response to a matching failure, add a label indicating a pit position matching failure to the tracking point reporting information.

[0176] In an optional embodiment, the burying point verification device 900 may also include a second burying point parameter verification module and / or a third burying point parameter verification module, wherein the second burying point parameter verification module is configured to, after receiving the burying point reporting information of the application client, determine the second burying point parameter associated with the burying point reporting event that triggers the burying point reporting information, and verify the second burying point parameter in the burying point reporting information according to the verification rules of the second burying point parameter in the target verification rule library; the third burying point parameter verification module is configured to verify the public parameters in the burying point reporting information according to the verification rules corresponding to the public parameters in the target verification rule library.

[0177] In an optional embodiment, when the tracking point reporting information includes the tracking point reporting information corresponding to the tracking point test task, the tracking point task to be verified includes the first tracking point task in the tracking point test task and the second tracking point task of the application that the tracking point test task targets has been launched.

[0178] In an optional embodiment, the method for determining the tracking task to be verified includes: obtaining the value of a preset field in the tracking reporting information, and determining the tracking task to be verified according to the value of the preset field; wherein, the preset field is used to indicate the version of the application client, and the tracking task to be verified includes the online tracking task corresponding to the version of the application client.

[0179] In an optional embodiment, the buried point verification device 900 may also include: a quantity display module, the quantity display module includes an update unit and a display unit, the update unit is configured to update the first quantity and the second quantity according to the received buried point reporting information; the display unit is configured to respond to the operation of requesting to display the verification result of the first verification mode, and display the first quantity and the second quantity corresponding to the buried point reporting event; wherein, the first quantity includes the number of buried point reporting events indicated by the buried point reporting information, and the second quantity includes the number of buried point pits corresponding to the buried point reporting events indicated by the buried point reporting information.

[0180] In an optional embodiment, the buried point verification device 900 may also include a sequential display verification result module, which is configured to respond to a request to display the verification result of the first verification mode, and sequentially display the verification results of the buried point reporting information according to the reporting time of the buried point reporting information.

[0181] In an optional embodiment, when the burying point reporting information includes burying point reporting information corresponding to the burying point test task, the device 900 may further include a task completion verification module, and the task completion verification module is configured to determine the target burying point positions including burying point parameters of enumerated type; when each enumerated value of each target burying point position is matched successfully, it is determined that the burying point test task test is completed.

[0182] In an optional embodiment, the burial point verification device may further include a candidate verification module, which is configured to: for the target burial point parameters in the burial point reporting information that do not pass the constraint value range description of the verification rule, verify the target burial point parameters according to a candidate value library pre-associated with the target burial point parameters.

[0183] In an optional embodiment, the burrowing point verification device may further include a quantity update module, and the quantity update module is configured to: update one or more of a third quantity, a fourth quantity, a fifth quantity, a sixth quantity, and a seventh quantity according to the burrowing point attribution parameter value in the burrowing point reporting information; wherein the third quantity is used to characterize the number of burrowing point reporting information with empty burrowing point attribution parameter values, the fourth quantity is used to characterize the number of burrowing point reporting information with illegal burrowing point attribution parameter values, the fifth quantity is used to characterize the number of burrowing point reporting information with unreasonable burrowing point attribution parameter values, the sixth quantity is used to characterize the number of burrowing point reporting information with downgraded burrowing point attribution parameter values, and the seventh quantity is used to characterize various types of burrowing point reporting events corresponding to the burrowing point reporting information. type of burying point attribution parameter values; wherein, when the pit position indicated by the pit position information in the burying point attribution parameter value does not belong to the burying point pit position, it is determined that the burying point attribution parameter value is illegal; when the to-be-confirmed pit position indicated by the pit position information in the burying point attribution parameter value belongs to the burying point pit position, but the to-be-confirmed pit position fails to match the pit position information in the candidate burying point attribution parameter value of the burying point reporting event corresponding to the burying point reporting information, it is determined that the burying point attribution parameter value is unreasonable; when the burying point attribution parameter value includes a preset field identifier, it is determined that the burying point attribution parameter value is downgraded, and the preset field identifier is used to identify the burying point attribution parameter value generated after triggering the pit position without a burying point object in the application client.

[0184] In an optional embodiment, the buried point verification device may further include a details display module, which is configured to: for any application client, record the buried point reporting information of the application client according to the reporting time sequence of the buried point reporting information, respond to a query request for the target buried point reporting information, obtain other buried point reporting information whose reporting sequence is within a preset range with the target buried point reporting information, so as to display the target buried point reporting information and the other buried point reporting information.

[0185] In an optional embodiment, the tracking point reporting information includes tracking point reporting information generated by the application client according to the test case of the tracking point test task, wherein the test case is generated based on the tracking point position to be tested of the tracking point test task.

[0186] In an optional embodiment, when the tracking point reporting information includes tracking point reporting information corresponding to the tracking point test task, the tracking point verification device may further include an integrity verification module, and the integrity verification module is configured to: simulate the test link correspondence in the tracking point test task through a virtual object.

[0187] In addition, other specific details of the embodiments of the present disclosure have been described in detail in the inventive implementation of the above method and will not be repeated here.

[0188] Exemplary Storage Media

[0189] The storage medium according to the exemplary embodiment of the present disclosure is described below.

[0190] In this exemplary embodiment, the above method can be implemented by a program product, such as a portable compact disk read-only memory (CD-ROM) and including program code, and can be run on a device, such as a personal computer. However, the program product of the present disclosure is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, apparatus, or device.

[0191] The program product may adopt any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0192] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0193] The program code contained on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RE, etc., or any suitable combination of the foregoing.

[0194] Program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user computing device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0195] Exemplary Electronic Devices

[0196] refer to Fig.10 An electronic device according to an exemplary embodiment of the present disclosure is described. The electronic device may be a client or a server.

[0197] Fig.10 The electronic device 1000 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0198] like Fig.10 As shown, the electronic device 1000 is in the form of a general computing device. The components of the electronic device 1000 may include, but are not limited to: at least one processing unit 1010, at least one storage unit 1020, a bus 1030 connecting different system components (including the storage unit 1020 and the processing unit 1010), and a display unit 1040.

[0199] The storage unit stores program codes, which can be executed by the processing unit 1010, so that the processing unit 1010 performs the steps according to various exemplary embodiments of the present disclosure described in the above “Exemplary Method” section of this specification. For example, the processing unit 1010 can perform the following steps: Figure 1 The method steps shown, etc.

[0200] The storage unit 1020 may include a volatile storage unit, such as a random access storage unit (RAM) 1021 and / or a cache storage unit 1022 , and may further include a read-only storage unit (ROM) 1023 .

[0201] The storage unit 1020 may also include a program / utility 1024 having a set (at least one) of program modules 1025, such program modules 1025 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0202] The bus 1030 may include a data bus, an address bus, and a control bus.

[0203] The electronic device 1000 may also communicate with one or more external devices 1100 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), and such communication may be performed through an input / output (I / O) interface 1050. The electronic device 1000 also includes a display unit 1040, which is connected to the input / output (I / O) interface 1050 for display. In addition, the electronic device 1000 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) through a network adapter 1060. As shown, the network adapter 1060 communicates with other modules of the electronic device 1000 through a bus 1030. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1000, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0204] It should be noted that, although several modules or submodules of the device are mentioned in the above detailed description, such division is merely exemplary and not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided into multiple units / modules to be embodied.

[0205] In addition, although the operations of the disclosed method are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0206] Although the spirit and principle of the present disclosure have been described with reference to several specific embodiments, it should be understood that the present disclosure is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present disclosure is intended to cover various modifications and equivalent arrangements included in the spirit and scope of the attached claims.

Claims

1. A method for burying point verification, characterized in that: include: Receiving the tracking point reporting information from the application client, and in response to the tracking point reporting information including the pit location information, matching the pit location information with the pit location in the target pit location library; According to the matching result, based on the target verification rule library, the tracking point reporting information is verified; The target pit location library and the target verification rule library are determined according to the buried points in the buried point task to be verified; Update one or more of the third quantity, the fourth quantity, the fifth quantity, the sixth quantity, and the seventh quantity according to the burying point attribution parameter value in the burying point reporting information; Among them, the third number is used to characterize the number of burying point reporting information with empty burying point attribution parameter values, the fourth number is used to characterize the number of burying point reporting information with illegal burying point attribution parameter values, the fifth number is used to characterize the number of burying point reporting information with unreasonable burying point attribution parameter values, the sixth number is used to characterize the number of burying point reporting information with downgraded burying point attribution parameter values, and the seventh number is used to characterize the number of each type of burying point reporting event corresponding to the burying point reporting information; Wherein, when the pit location indicated by the pit location information in the burying point attribution parameter value does not belong to the burying point pit location, it is determined that the burying point attribution parameter value is illegal; When the pit location to be confirmed indicated by the pit location information in the burying point attribution parameter value belongs to the burying point pit location, but the pit location to be confirmed fails to match the pit location information in the candidate burying point attribution parameter value of the burying point reporting event corresponding to the burying point reporting information, it is determined that the burying point attribution parameter value is unreasonable; In a case where the burying point attribution parameter value includes a preset field identifier, determining that the burying point attribution parameter value is downgraded, the preset field identifier being used to identify the burying point attribution parameter value generated after triggering a pit position without a burying point object in the application client; Among them, the pit position is the only location that can be described in the client application.

2. The method for burying point verification according to claim 1, characterized in that: According to the matching result, based on the target verification rule library, verifying the tracking point reporting information includes: In response to a successful match, obtaining a burying point object identifier included in the pit location information; For each burying point object identifier, based on the verification rule of the first burying point parameter associated with the burying point object identifier in the target verification rule library, the first burying point parameter in the burying point reporting information is verified.

3. The method for burying point verification according to claim 1, characterized in that: According to the matching result, based on the target verification rule library, verifying the tracking point reporting information includes: In response to a matching failure, a label indicating that the pit position matching failed is added to the tracking point reporting information.

4. The method for burying point verification according to claim 1, characterized in that: After receiving the tracking point reporting information from the application client, the method further includes: Determine a second burying point parameter associated with the burying point reporting event that triggers the burying point reporting information, and verify the second burying point parameter in the burying point reporting information according to the verification rule of the second burying point parameter in the target verification rule library; and / or The public parameters in the tracking point reporting information are verified according to the verification rules corresponding to the public parameters in the target verification rule library.

5. The method for burying point verification according to claim 1, characterized in that: In the case where the tracking point reporting information includes the tracking point reporting information corresponding to the tracking point test task, the tracking point task to be verified includes the first tracking point task in the tracking point test task and the second tracking point task for the application that has been launched by the tracking point test task.

6. The method for burying point verification according to claim 1, characterized in that: The method for determining the task to be verified includes: Obtaining the value of a preset field in the tracking point reporting information, and determining the tracking point task to be verified according to the value of the preset field; Among them, the preset field is used to indicate the version of the application client, and the tracking task to be verified includes the online tracking task corresponding to the version of the application client.

7. The method for burying point verification according to claim 1, characterized in that: The method further comprises: Update the first quantity and the second quantity according to the received tracking point reporting information; In response to the request to display the verification result of the first verification mode, the first number and the second number corresponding to the buried point reporting events are displayed; Among them, the first number includes the number of burrowing point reporting events indicated by the burrowing point reporting information, and the second number includes the number of burrowing point pits corresponding to the burrowing point reporting events indicated by the burrowing point reporting information.

8. The method for burying point verification according to claim 1, characterized in that: The method further comprises: In response to the request to display the verification results of the first verification mode, the verification results of the buried point reporting information are displayed sequentially according to the reporting time of the buried point reporting information.

9. The method for burying point verification according to claim 1, characterized in that: In a case where the tracking point reporting information includes tracking point reporting information corresponding to the tracking point test task, the method further includes: Determine the target burying point location including the burying point parameters of the enumeration type; When each enumerated value of each target burying point position is matched successfully, it is determined that the burying point test task is completed.

10. The method for burying point verification according to any one of claims 1 to 9, characterized in that: The method further comprises: For the target burying point parameters in the burying point reporting information that do not pass the verification rule description constraint value range, the target burying point parameters are verified according to a candidate value library pre-associated with the target burying point parameters.

11. The method for burying point verification according to claim 1, characterized in that: The method further comprises: For any application client, record the tracking point reporting information of the application client according to the reporting time sequence of the tracking point reporting information; In response to a query request for target burying point reporting information, other burying point reporting information whose reporting order with the target burying point reporting information is within a preset range is obtained to display the target burying point reporting information and the other burying point reporting information.

12. The method for burying point verification according to claim 1, characterized in that: The tracking point reporting information includes tracking point reporting information generated by the application client triggered by the test case of the tracking point test task, wherein the test case is generated based on the tracking point position to be tested of the tracking point test task.

13. The method for burying point verification according to claim 1, characterized in that: In a case where the tracking point reporting information includes tracking point reporting information corresponding to the tracking point test task, the method further includes: The test data corresponding to the test link in the embedded test task is simulated by a virtual object, so as to perform integrity verification on the embedded test task based on the test link.

14. A buried point verification device, characterized in that: include: A tracking point information receiving module is configured to receive tracking point reporting information from an application client, and in response to the tracking point reporting information including pit location information, match the pit location information with the pit location in a target pit location library; A verification module is configured to verify the tracking point reporting information according to the matching result and based on the target verification rule library; The target pit location library and the target verification rule library are determined according to the buried points in the buried point task to be verified; Update one or more of the third quantity, the fourth quantity, the fifth quantity, the sixth quantity, and the seventh quantity according to the burying point attribution parameter value in the burying point reporting information; Among them, the third number is used to characterize the number of burying point reporting information with empty burying point attribution parameter values, the fourth number is used to characterize the number of burying point reporting information with illegal burying point attribution parameter values, the fifth number is used to characterize the number of burying point reporting information with unreasonable burying point attribution parameter values, the sixth number is used to characterize the number of burying point reporting information with downgraded burying point attribution parameter values, and the seventh number is used to characterize the number of each type of burying point reporting event corresponding to the burying point reporting information; Wherein, when the pit location indicated by the pit location information in the burying point attribution parameter value does not belong to the burying point pit location, it is determined that the burying point attribution parameter value is illegal; When the pit location to be confirmed indicated by the pit location information in the burying point attribution parameter value belongs to the burying point pit location, but the pit location to be confirmed fails to match the pit location information in the candidate burying point attribution parameter value of the burying point reporting event corresponding to the burying point reporting information, it is determined that the burying point attribution parameter value is unreasonable; In a case where the burying point attribution parameter value includes a preset field identifier, determining that the burying point attribution parameter value is downgraded, the preset field identifier being used to identify the burying point attribution parameter value generated after triggering a pit position without a burying point object in the application client; Among them, the pit position is the only location that can be described in the client application.

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

16. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the method according to any one of claims 1 to 13.

Images