Data processing method and device, electronic equipment and storage medium

Abstract

The invention provides a data processing method and device, electronic equipment and a storage medium. The invention relates to the technical field of data management, in particular to the technical field of data burying points. The method comprises the following steps: receiving a point burying application; pushing the point burying application to a second processing node, so that a second object performs normative auditing; under the condition that the processing result of the second processing node is approved, pushing the point burying demand to a third processing node, and generating a point burying code by a third object; under the condition that the processing result of the third processing node is that development is completed, pushing the burying point code to a fourth processing node, and testing by a fourth object; under the condition that the processing result of the fourth processing node is that the test is successful, pushing the test data to the first processing node, so that the first object accepts and accepts the test data; and generating a response result under the condition that the processing result of the first processing node is that the acceptance passes. According to the method and the device, platformization and standardization management of the burying point data is realized.

Description

Technical Field

[0001] The present disclosure relates to the field of data management technology, and in particular to the field of data embedding technology, and can be used in application scenarios such as product optimization and iteration, data tracking and statistics, data security and compliance, and specifically relates to a data processing method, device, electronic device and storage medium. Background Art

[0002] In the related technologies, in the management of buried data, there are problems such as chaotic metadata management, non-standard approval process, and time-consuming and labor-intensive acceptance. The data quality cannot be effectively guaranteed, and a unified and systematic management method is urgently needed. Summary of the invention

[0003] The present disclosure provides a data processing method, device, electronic device and storage medium.

[0004] According to one aspect of the present disclosure, there is provided a data processing method, the method comprising:

[0005] receiving a tracking application, where the tracking application is an application submitted by a first object through a first processing node of a tracking management platform, and the tracking application includes a tracking requirement;

[0006] Push the tracking application to the second processing node, so that the second object corresponding to the second processing node can conduct a normative review of the tracking demand according to business requirements and technical specifications;

[0007] If the processing result of the second processing node is approved, the tracking point requirement is pushed to the third processing node, so that the third object corresponding to the third processing node is developed based on the tracking point requirement to generate the tracking point code;

[0008] When the processing result of the third processing node is that the development is completed, the tracking code is pushed to the fourth processing node, so that the fourth object corresponding to the fourth processing node tests the tracking code to obtain test data;

[0009] When the processing result of the fourth processing node is that the test is successful, the test data is pushed to the first processing node so that the first object can accept the test data;

[0010] When the processing result of the first processing node is acceptance passed, a response result of the tracking point application is generated, and the response result includes permission for the tracking point code to go online.

[0011] According to another aspect of the present disclosure, there is provided a data processing device, the device comprising:

[0012] A tracking application module, used to receive a tracking application, where the tracking application is an application submitted by a first object through a first processing node of a tracking management platform, and the tracking application includes a tracking requirement;

[0013] A specification review module, used to push the tracking point application to the second processing node, so that the second object corresponding to the second processing node can conduct a specification review on the tracking point demand according to business requirements and technical specifications;

[0014] A tracking point development module is used to push the tracking point requirement to the third processing node when the processing result of the second processing node is approved, so that the third object corresponding to the third processing node is developed based on the tracking point requirement to generate the tracking point code;

[0015] A code testing module, used for pushing the tracking code to the fourth processing node when the processing result of the third processing node is that the development is completed, so that the tracking code is tested by the fourth object corresponding to the fourth processing node to obtain test data;

[0016] An acceptance confirmation module, configured to push the test data to the first processing node when the processing result of the fourth processing node is that the test is successful, so that the first object can accept the test data;

[0017] The online permission module is used to generate a response result of the tracking point application when the processing result of the first processing node is accepted, and the response result includes permission for the tracking point code to go online.

[0018] According to another aspect of the present disclosure, there is provided an electronic device, comprising:

[0019] at least one processor; and

[0020] a memory communicatively connected to the at least one processor; wherein,

[0021] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute any method in the embodiments of the present disclosure.

[0022] According to another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable the computer to execute any method according to the embodiments of the present disclosure.

[0023] According to another aspect of the present disclosure, a computer program product is provided, including a computer program, which implements any method according to the embodiments of the present disclosure when executed by a processor.

[0024] By adopting the solution disclosed in the present invention, the problems of chaotic tracking point management, non-standard approval and low acceptance efficiency are solved through a unified tracking point management platform, platform-based and standardized management is realized, collaborative efficiency, data accuracy and verification quality are improved, and duplicate tracking points and resource waste are reduced.

[0025] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure.

[0027] Figure 1 is a flowchart of a data processing method according to an embodiment of the present disclosure;

[0028] Figure 2 This is a schematic diagram of the interface of the tracking point management platform according to the embodiment of the present disclosure Figure 1 ;

[0029] Figure 3 This is a schematic diagram of the interface of the tracking point management platform according to the embodiment of the present disclosure Figure 2 ;

[0030] Figure 4 This is a schematic diagram of the interface of the tracking point management platform according to the embodiment of the present disclosure Figure 3 ;

[0031] Figure 5 This is a flowchart of the approval process for the public tracking point;

[0032] Figure 6 is a schematic diagram of the architecture of a tracking point management system according to an embodiment of the present disclosure;

[0033] Figure 7 is a structural schematic diagram of a data processing device according to an embodiment of the present disclosure;

[0034] Figure 8 is a scenario schematic diagram of a data processing method according to an embodiment of the present disclosure;

[0035] Fig. 9 It is a schematic diagram of the structure of an electronic device used to implement the data processing method of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0036] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope of the present disclosure. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0037] The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The term "at least one" in this article means any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C. The terms "first" and "second" in this article refer to multiple similar technical terms and distinguish them. They do not mean to limit the order or to limit them to only two. For example, the first feature and the second feature refer to two types / two features. The first feature can be one or more, and the second feature can also be one or more.

[0038] In addition, in order to better illustrate the present disclosure, numerous specific details are given in the following specific embodiments. It should be understood by those skilled in the art that the present disclosure can also be implemented without certain specific details. In some examples, methods, means, components and circuits well known to those skilled in the art are not described in detail in order to highlight the subject matter of the present disclosure.

[0039] Before introducing the technical solutions of the embodiments of the present disclosure, the technical terms that may be used in the present disclosure are further explained:

[0040] Tracking: Tracking is a technical method that is usually used to record specific data points of user behavior or system operations in applications or websites. Through tracking, developers can track specific events or operations, such as clicks, page visits, etc.

[0041] Tracking point platform: A system used to manage and monitor tracking point data, supporting the entire process of tracking point design, submission, review, development, testing, etc., to ensure accurate and consistent data collection.

[0042] Tracking point management and control system: a system used to comprehensively manage tracking points from demand submission to launch, standardize control of each link, and ensure the accuracy and compliance of tracking point data.

[0043] In the related technologies, due to the lack of unified platforms and the lack of standardized approval processes, the data management of buried points is chaotic, the review efficiency is low, and the acceptance of buried points is time-consuming and laborious. Therefore, there is an urgent need for a solution that can uniformly manage buried point data, standardize the approval process, and improve the acceptance efficiency.

[0044] In order to at least partially solve one or more of the above-mentioned problems and other potential problems, the present disclosure proposes a data processing method, which enhances the whole process management of tracking data from application to launch, and effectively solves the problems of inconsistent platforms, non-standard tracking approval process, low data verification efficiency, etc. in the prior art.

[0045] The present disclosure provides a data processing method. Figure 1 : is a flow chart of a data processing method according to an embodiment of the present disclosure, and the data processing method can be applied to a data processing device. The data processing device is located in an electronic device. The electronic device includes but is not limited to a fixed device and / or a mobile device. For example, a fixed device includes but is not limited to a server, and the server can be a cloud server or an ordinary server. For example, a mobile device includes but is not limited to: a mobile phone, a tablet computer. In some possible implementations, the data processing method can also be implemented by a processor calling a computer-readable instruction stored in a memory. Figure 1 As shown, the data processing method includes:

[0046] S101: Receive a tracking application, where the tracking application is an application submitted by a first object through a first processing node of a tracking management platform, and the tracking application includes a tracking requirement;

[0047] S102: Push the tracking application to the second processing node, so that the second object corresponding to the second processing node can conduct a normative review of the tracking demand according to business requirements and technical specifications;

[0048] S103: If the processing result of the second processing node is approved, the tracking requirement is pushed to the third processing node, so that the third object corresponding to the third processing node is developed based on the tracking requirement to generate tracking code;

[0049] S104: When the processing result of the third processing node is that the development is completed, the tracking code is pushed to the fourth processing node, so that the fourth object corresponding to the fourth processing node tests the tracking code to obtain test data;

[0050] S105: When the processing result of the fourth processing node is that the test is successful, push the test data to the first processing node so that the first object can accept the test data;

[0051] S106. When the processing result of the first processing node is acceptance passed, a response result of the tracking point application is generated, and the response result includes permission for the tracking point code to go online.

[0052] In the disclosed embodiment, the first object refers to the role responsible for submitting the tracking application and ultimately accepting the tracking test results, including but not limited to: Product Manager (PM), data manager or the demander of the related project.

[0053] In the embodiment of the present disclosure, the second object refers to the role responsible for conducting business and technical normative reviews of tracking requirements, including but not limited to: business analysts (Business Planner, BP), data reviewers or other relevant roles responsible for requirement specification reviews.

[0054] In the disclosed embodiment, the third object refers to the role responsible for performing development work based on the approved tracking requirements, including but not limited to: R&D personnel (RD), development engineers or other technical personnel responsible for implementing the tracking function.

[0055] In the disclosed embodiment, the fourth object refers to the role responsible for testing the tracking code and outputting the test results, including but not limited to: testers (Quality Assurance, QA), quality assurance engineers or other technical personnel responsible for verifying tracking functions and data.

[0056] In the embodiment of the present disclosure, the first processing node refers to the link of receiving and submitting the tracking application, including but not limited to: submitting the demand application through the tracking management platform and filling in the tracking related information, which is operated by the first object.

[0057] In the disclosed embodiment, the second processing node refers to the link for reviewing the tracking application, including but not limited to: reviewing the rationality and compliance of the tracking application according to business requirements and technical specifications, and operated by the second object.

[0058] In the disclosed embodiment, the third processing node refers to the link for developing tracking code, including but not limited to: R&D personnel write and generate corresponding tracking code according to the approved tracking requirements, which is operated by the third object.

[0059] In the disclosed embodiment, the fourth processing node refers to the link of testing the tracking code, including but not limited to: the tester performs functional verification and quality testing on the generated tracking code, generates test data, and is operated by the fourth object.

[0060] In the disclosed embodiment, the Research Data Center (RDC) is a system for uniformly receiving, processing, and storing tracking data. Accessing the RDC means that the data generated by the tracking points will be directly uploaded to the center for centralized management. After accessing the RDC, the data can be used for real-time analysis, historical log query, and generation of relevant data reports and business analysis, which facilitates subsequent data utilization and monitoring.

[0061] Customized log specifications: Customized log specifications are used to define the log format and structure generated by the tracking data, including the name of the field, data type (such as string, number, Boolean, etc.), and the value range or enumeration value of each field. By customizing the log specifications, the PM can ensure that the logs generated by the tracking data meet the business needs and the requirements of data analysis.

[0062] In some implementations, a schematic diagram of a first object submitting a tracking application through a first processing node of a tracking management platform is shown as follows: Figure 2 As shown in the figure, the first object, as a person with a tracking point demand, needs to design the tracking point specification according to the demand. First, the first object enters the tracking point management platform and fills in the basic information form, including the tracking point title, description, business field (such as log middle platform), product line, tracking point type (such as event or page), person in charge, tracking point scene illustration, etc. This information helps different processing nodes and related objects to understand the business background of the tracking point application more clearly. Next, the first object also needs to define the "peak number of requests per second (Queries Per Second, QPS)" and "estimated traffic" of the tracking point, and describe the expected performance of the tracking point by selecting the corresponding options. This process helps the system evaluate the data load and pressure of the tracking point, and prepare for subsequent processing and resource allocation. Subsequently, the first object needs to choose whether to connect the tracking point to RDC. If "Connect to RDC" is selected, the tracking point data will be uploaded to the RDC system for unified management and storage, ensuring that the tracking point data is centrally processed, effectively managed and tracked.

[0063] like Figure 3As shown, the first object needs to configure a custom log specification, which involves the format and field definition of the tracking log. The first object can select an applicable log format on the platform and specify the scope of application of the log (such as application to all scenarios or specific scenarios). At the same time, the first object can enable the data structure (Schema) mode to ensure that the log meets the specified structural requirements, automatically verify the format and consistency of the tracking data, ensure the integrity of the data, and reduce errors that may occur during the audit and verification process. Finally, the first object defines specific fields in the custom log field settings, including field name, data type, field level, required field, field description, and field value range or enumeration value. The platform supports unlimited levels of field extension, enabling the first object to add more complex tracking fields according to business needs to meet the data collection needs of complex scenarios. For each field, the first object can also set enumeration values ​​and default values ​​to ensure that the tracking data meets business specifications and avoid errors or invalid values ​​in data input. After completing all the above tracking specification designs, the tracking requirements can be pushed to the second processing node for normative review. The Schema mode is a logical structure and feature description of data in the database. Based on the data model, it defines data items, security and integrity rules. It is a description of the logical structure and characteristics of the global data in the database and is a public data view for all users.

[0064] It should be noted that in the above implementation, the process described only involves adding a new tracking point requirement. The present disclosure also includes the function of modifying the tracking point requirement, and only the above part that needs to be modified needs to be edited. The specific process is similar to adding a new one, and will not be repeated here.

[0065] In some embodiments, the second object conducts a normative review of the tracking point requirements according to business requirements and technical specifications, including: the second object checks the rationality of the field definition in the tracking point application to ensure that the field naming, data type and format meet the business requirements. At the same time, the second object will confirm whether the tracking point design can accurately collect the data required in the business scenario to ensure that the tracking point settings can meet the business logic requirements. In addition, the review also involves checking whether the tracking point meets the technical specifications to ensure that the data collection method, timing and frequency are reasonable and will not have an adverse impact on system performance or user experience. In order to improve data processing efficiency, the second object also needs to review whether there is redundancy in the tracking point, avoid repeated tracking point design, and reduce the burden on the system. The enumeration values ​​and ranges of the fields in the tracking point also need to be reviewed to ensure that non-compliant inputs will not appear in the subsequent development and data processing process. Finally, the second object also needs to evaluate the security and privacy compliance of the tracking point data to ensure that the processing of sensitive data complies with the requirements of relevant laws and regulations and the company's data protection policy. If the processing result of the second processing node is approved, a tracking point identifier (Identifier, ID) is generated. If the audit result of the second processing node is not passed, the system will return the tracking application to the first processing node with the specific reason for the failure. Figure 4 As shown, the first subject modifies the tracking point requirements based on the feedback, including adjusting the field definition, data type, tracking point design or collection method, etc., to ensure that the requirements meet the business and technical specifications. After the modification is completed, the first subject can resubmit the tracking point application and enter a new round of review process. The reviewer can only view the changed line, and the relevant information before or after the change.

[0066] In some embodiments, the third object is developed based on the tracking point requirements and generates tracking point code, including: first, the third object analyzes the tracking point requirements that have passed the review to ensure that the business logic, field definition and data type meet the requirements. Subsequently, the tracking point code is embedded in the key processes of the system, such as the trigger points of the front-end user operations or the back-end services, to ensure that the tracking point data is accurately captured. During development, the third object needs to ensure that the tracking point is triggered at the appropriate time and frequency to avoid frequent triggering affecting performance. At the same time, a log format that conforms to the Schema is generated according to the custom log specification, and the serialization, transmission and compression of the log are processed to ensure that the data is accurately uploaded to the RDC. After the development is completed, the third object conducts a preliminary self-test and uses a packet capture tool or a log analysis tool to verify the accuracy of the tracking point data. If necessary, debug and optimize the problem to ensure that the tracking point runs stably in different scenarios, and finally generate optimized tracking point code for subsequent testing.

[0067] In some embodiments, the fourth object corresponding to the fourth processing node tests the tracking code to obtain test data, including: the fourth object will use automation tools and log analysis tools to simulate the triggering scenario of the tracking, and verify whether the tracking code captures the correct data as expected. During the test, the fourth object will check whether the triggering timing of the tracking, the integrity and accuracy of the data, and the frequency of reporting meet the business and technical requirements. The test scenario usually includes different user operation paths, system environments, and boundary conditions to ensure that the tracking can work properly in various usage scenarios. The fourth object will also check the transmission process of the tracking data through the packet capture tool to ensure that the data can be accurately sent to the RDC or other specified storage system, and verify the matching of the log format with the custom log specification. After the test data is generated, the fourth object will analyze and verify the generated data in detail to ensure that it is consistent with the expected results. If the test data meets the business requirements and technical specifications, the fourth object will submit the test results to the first processing node, and the first object will accept it. If there is a problem with the test data, the fourth object will feedback the test results to the third object, and the third object needs to correct the tracking code based on the feedback and resubmit the code for testing. This cycle continues until all tests pass and meet the requirements.

[0068] In some embodiments, the first object accepts the test data, including: first, the first object will verify the integrity, accuracy and compliance of the test data with business logic according to business needs and expected indicators. The first object will check whether the data correctly captures the predetermined user behavior or system events to ensure that the trigger conditions and data content of the tracking point meet business expectations. In addition, the first object will also verify the reporting frequency and timing of the tracking point data to confirm whether the timeliness of the data meets the requirements. If the test data performs normally in all scenarios and meets the requirements in the tracking point application, the first object will pass the acceptance. If the data is found to be abnormal or does not meet business requirements, the first object will pass the feedback to the fourth object for further adjustment, and return it to the third object for code correction if necessary until the data meets the acceptance criteria.

[0069] In some embodiments, generating a response result of a tracking application includes: first, after the first object accepts and passes the test data, the system will generate a response result of the tracking application, indicating that the tracking process has been completed. The response result includes the online permission of the tracking code, which means that the tracking can be officially put into the production environment and start collecting and reporting data. In addition, the response result may also include a detailed record of the tracking status, such as the online time, the system modules involved, the estimated traffic impact and other information, for subsequent tracking and maintenance. If a problem is found during the acceptance process, a modification feedback or a failed response result will be generated, and returned to the corresponding processing node for correction until the problem is resolved.

[0070] For example, suppose an e-commerce platform needs to track the user's operation behavior on the shopping cart page. The first object (PM) submits a tracking application through the tracking management platform and defines the operation behaviors that need to be tracked, such as "add to shopping cart", "remove product", "view product details", etc. PM also configures a custom log specification to ensure that the field name, data type (such as string, number) and value range of these operations match the business requirements, and chooses to connect to RDC for centralized data management and analysis. The second object (BP) reviews these tracking requirements based on business logic, ensures that the field definition is reasonable, the frequency and timing of data collection meet the technical specifications, and checks whether there are duplicate or redundant tracking points. After the review is passed, the third object (RD) embeds the tracking code in the system according to the requirements, integrates the tracking into the front-end user operation and back-end service, and ensures that each operation behavior can be accurately recorded. After the development is completed, the fourth object (QA) tests the code, using simulated user operation scenarios to verify the trigger timing of the tracking and the accuracy of the data, and ensures that all operations can be successfully uploaded to RDC. After the test data is generated, QA confirms that it meets expectations and submits the test results to PM for acceptance. The PM verifies the data, confirms that all operational behaviors are correctly tracked and reported, and finally approves the tracking point to go online and enter the formal production environment.

[0071] The technical solution of the disclosed embodiment ensures standardized management of the entire process from demand submission, code development to test verification. By accessing RDC for centralized data management, the real-time and accuracy of the tracking data is ensured, redundant tracking and data inconsistency problems are avoided, and the efficiency and quality of data collection are improved. Ultimately, tracking can accurately track user behavior and provide reliable data support for business analysis and optimization.

[0072] In some embodiments, when the processing result of the first processing node is acceptance passed, generating a response result of the tracking point application further includes:

[0073] If the processing result of the first processing node is acceptance passed, the test data is pushed to the second processing node so that the second object can accept the test data;

[0074] When the processing result of the second processing node is acceptance passed, a response result is generated.

[0075] In some embodiments, the second object accepts the test data, including: if the processing result of the first processing node is accepted, the test data is pushed to the second processing node, and the second object verifies the integrity and accuracy of the test data to ensure that the data complies with the business logic and technical specifications. The second object will verify whether the data collection meets the tracking requirements, check whether the timing and frequency of the tracking trigger are reasonable, and confirm whether the expected user behavior or system events are captured in accordance with regulations. In addition, the quality of the data must be evaluated to ensure that there are no lost or duplicate records. If the test data does not meet the requirements, the second object will submit feedback to the relevant developers for correction until the test data meets the acceptance criteria.

[0076] For example, suppose a financial platform needs to track users' transfer operations. The first object (PM) submits a tracking point application through the tracking point management platform, defining key operations such as "transfer initiation", "transfer confirmation", and "transfer completion". After development and preliminary acceptance, the test data is pushed to the second object (BP) for acceptance. BP verifies the integrity and accuracy of the tracking point data, verifies whether the data correctly reflects the user's transfer behavior, and confirms whether the timing and frequency of data triggering meet business requirements. After inspection, BP found that some transfer operations were not captured as expected, resulting in data loss. BP fed back the problem to the development team for correction, and after the correction was completed, it was accepted again. Finally, the test data passed, and the final response result of the tracking point application was generated, allowing the tracking point to be officially launched for business analysis and optimization.

[0077] In this way, the integrity and accuracy of the tracking data are ensured through a multi-level acceptance process and data verification mechanism. The second object's review of the test data further improves the data quality and avoids data loss, duplication, or non-compliance with business logic.

[0078] In some embodiments, the data processing method may also include: when the processing result of the second processing node is that the review fails, the tracking application is returned to the first processing node, together with the specific reason for the review failure, so that the first object can modify the tracking requirement according to the feedback and resubmit it; when the processing result of the fourth processing node is that the test fails, the specific reason for the test failure is returned to the third processing node, so that the third object can repair it according to the test feedback, and resubmit it to the fourth processing node for testing after the repair; when the processing result of the first processing node is that the acceptance fails, if it is a problem with the function implementation or the code itself, it will be returned to the third processing node, so that the third object can repair it according to the acceptance feedback.

[0079] In some embodiments, the specific reasons for failure of the incidental audit may include: the specific feedback content may involve field definition issues, for example: the field naming is not standardized or the data type does not meet the technical specifications, which may lead to data processing errors. At the same time, the feedback may point out that there is redundancy in the tracking point design, causing the system to repeatedly collect data and increase unnecessary system burden. In addition, the timing or frequency of the tracking point trigger may be unreasonable. For example, too frequent triggering affects system performance, or the data does not conform to the business logic, resulting in the inability to support accurate business decisions. Format issues in custom log specifications may also lead to incompatibility with the RDC system and affect the accuracy of data storage and transmission. After receiving these feedbacks, the first object needs to make corresponding modifications to the tracking point requirements, readjust the field definition, optimize the trigger conditions and frequency, ensure that the requirements meet the technical and business specifications, and then submit them for review again.

[0080] In some embodiments, the specific reasons for the test failure are returned to the third processing node, including: detailed error information and technical feedback. For example, feedback may involve the failure of the tracking code to correctly capture the expected user behavior or system events, resulting in inaccurate or incomplete data collection. Feedback may also point out that the timing of data reporting is inappropriate, the trigger conditions or frequency do not meet business requirements, or there are problems such as data loss and duplicate records. In addition, the log format does not match the custom log specification, resulting in data anomalies during transmission or storage, which may also be the reason for the test failure. The third object needs to analyze and correct the tracking code based on these feedbacks, adjust the technical details such as trigger conditions, frequency and log format to ensure that the code complies with business logic and technical specifications, and then resubmit the code for testing.

[0081] In some embodiments, if it is a problem with the function implementation or the code itself, it will be returned to the third processing node, including: detailed feedback on the code implementation. The feedback may involve code logic errors, which result in the failure of the tracking point to trigger or execute correctly and to capture the expected data. Specific problems may include: the code fails to correctly handle boundary conditions, resulting in the failure of the tracking point function in some cases; the reporting of the tracking point data does not meet expectations, which may be due to incorrect variable assignment, data type error or interface call failure. In addition, there may be compatibility issues between the tracking point code and other system modules, resulting in the tracking point failing to work properly in the actual production environment. Based on these feedbacks, the third object corrects the functional logic and re-optimizes the code implementation to ensure that the tracking point function meets the design requirements and meets technical and business specifications, and then resubmits it for testing and acceptance.

[0082] For example, suppose a social media platform needs to track the user's "like" and "cancel like" operations. The first subject (PM) submitted the tracking application, but the review found that the field naming was not standardized, such as the field type of the like operation was incorrectly set to string instead of Boolean, and there were redundant tracking points, causing the system to repeatedly collect the same data. After failing the review, the PM modified the field definition and optimized the tracking design based on the feedback, and resubmitted the application. Subsequently, the third subject (RD) completed the development of the tracking code, but during testing, the fourth subject found that the "cancel like" operation was not correctly captured. The problem was fed back to the third processing node, and the RD fixed the code logic to ensure that the "like" and "cancel like" operations could be accurately triggered respectively, and resubmitted the code for testing. During the acceptance stage, the first subject found that the system failed to correctly handle the user's rapid and repeated "like" and "cancel like" operations under certain boundary conditions, and the data collection was inaccurate. The problem was returned to the third subject, and the RD further fixed the code based on the feedback to ensure that the tracking data could also be captured normally in this case. After testing and acceptance, the tracking point was finally put online and successfully tracked user behavior.

[0083] In this way, the accuracy and completeness of data collection are ensured through multiple audits and feedback mechanisms. After multiple levels of feedback corrections such as audit, testing, and acceptance, problems such as irregular field definition, logical errors in data collection, and improper boundary condition handling were solved, ensuring that data collection can work normally in complex operation scenarios.

[0084] In some embodiments, when the processing result of the third processing node is that the development is completed, the burying point code is pushed to the fourth processing node, and also includes: when the processing result of the third processing node is that the development is completed, verifying whether the burying point code meets the technical specifications and business requirements; after the verification is passed, pushing the burying point code to the fourth processing node.

[0085] In some implementations, verifying whether the tracking code meets technical specifications and business requirements includes: after the tracking code is reviewed and approved by BP, the RD will develop the code. After the development is completed, the code will enter the QA stage, and the QA team will conduct a comprehensive test on the tracking code. The test content includes verifying whether the triggering timing of the tracking, the accuracy of the data, the reporting frequency, etc. meet the business requirements. If the QA test fails, QA will feedback the specific reasons for the test failure, such as incomplete data capture, wrong timing, mismatched log format, etc. RD will make repairs based on the feedback, adjust the tracking logic and code implementation, ensure that the data can be accurately and timely delivered to the tracking online service, and resubmit it for testing.

[0086] For example, an e-commerce platform needs to track the user's "add product to shopping cart" operation. BP reviewed and approved the tracking requirement, and RD developed the tracking code according to business needs to ensure that every time the user clicks the "Add to Cart" button, the tracking can be accurately triggered and record the operation. After the development is completed, the code enters the QA stage for verification. The QA team checks whether the tracking is correctly triggered when the user clicks and whether the data can be accurately reported. During the test, it was found that there was a delay in the timing of reporting data, resulting in the failure to feedback the data to the server in time. QA fed back this problem to RD, who then fixed the code, optimized the logic and triggering timing of data reporting, and resubmitted the test. Finally, the code passed the QA verification and was pushed to the fourth processing node for further testing and acceptance.

[0087] In this way, we ensure that each stage of tracking point development complies with technical specifications and business requirements, avoiding analysis errors caused by inaccurate data or untimely tracking point triggering. Through multiple verifications and repairs, we ultimately ensure that the tracking point code can efficiently and accurately record user behavior after it goes online, providing reliable support for platform operations and data analysis.

[0088] In some embodiments, when the processing result of the fourth processing node is that the test is successful, the test data is pushed to the first processing node, and it also includes: when the processing result of the fourth processing node is that the test is successful, verifying whether the test data conforms to the expected behavior of the tracking code and whether the test data conforms to the data specifications and quality standards; after the verification is passed, the test data is pushed to the first processing node for acceptance.

[0089] In some embodiments, verifying whether the test data conforms to the expected behavior of the buried point code and whether the test data conforms to the data specification and quality standards includes: checking whether the buried point code is triggered at the right time by simulating the expected user behavior or system events. For example, when the user clicks a button or completes a specific operation, the system verifies whether the buried point can accurately capture these events and successfully reports the corresponding log data. It is also necessary to check whether the reported test data is complete, including all key fields such as event ID, user ID and timestamp, etc., to ensure that it is accurately recorded and conforms to business logic. In addition, the test data must also conform to the defined Schema format to ensure that the naming, data type and format of the field are consistent with the Schema requirements. For example, if the field is expected to be a Boolean type, it will be ensured during verification that it is not incorrectly filled as a string or numeric type. The data quality is further tested through automated tools to ensure that the data is not lost or reported repeatedly, and to check whether the timestamp and reporting frequency are in line with expectations to avoid excessive or delayed reporting that affects system performance. If the verification fails, the QA will retest or conduct in-depth analysis at the fourth processing node to find the root cause of the problem. QA may debug and analyze the tracking code in more detail to find out why the data does not meet expectations, and feedback the problem to the third party (RD) for repair. After the repair, RD resubmits the test until the test data meets the expected requirements and meets all quality standards.

[0090] For example, an online education platform needs to track the user's "course completion" operation. RD developed the tracking code to ensure that whenever a user completes a course, the tracking will be accurately triggered and record the behavior. QA tests by simulating the user's behavior of completing the course to check whether the tracking is accurately triggered and verify whether the reported log data contains the correct key fields such as event ID, user ID and timestamp. In addition, QA also verifies whether the log data conforms to the predefined Schema format to ensure that the field naming and data types meet the specifications. During the test, QA found that the frequency of data reporting did not meet the requirements, resulting in delays in some log data. QA analyzed the problem in depth and fed back to RD. RD fixed the code based on the feedback and adjusted the data reporting logic. After retesting, the tracking code was successfully verified, all data was accurate and met technical and business specifications, and the test data was pushed to the first processing node for acceptance.

[0091] Figure 5 The following is a flow chart of the approval process of the tracking point: Figure 5As shown, PM adds or modifies the tracking requirement at the first processing node and submits it to the second processing node, so that BP can conduct a normative review of the tracking requirement according to business requirements and technical specifications; after BP passes the review, the tracking requirement is pushed to the third processing node, so that RQ can develop based on the tracking requirement and generate the tracking code; after RQ development is completed, the tracking code is pushed to the fourth processing node, so that QA can test the tracking code and obtain test data; after the QA test is successful, the test data is pushed to the first processing node, so that PM can accept the test data; if PM passes the acceptance, the acceptance result is pushed to the second processing node, so that BP can accept it; after BP passes the acceptance, the response result of the tracking application is generated, and the tracking code is allowed to go online. If the BP or QA fails to pass the review result of the tracking requirement, it returns to PM, so that PM can modify the tracking requirement and resubmit it. If the PM or BP fails to pass the acceptance result of the tracking requirement, it returns to QA, so that QA can retest and resubmit it.

[0092] In this way, through a rigorous multi-stage verification process, we can ensure that the tracking data is accurate and meets business requirements and technical specifications. Problems during the testing process can be discovered and fixed in a timely manner, ensuring that the tracking code can efficiently and stably record user behavior after it goes online, providing reliable data support for subsequent business analysis.

[0093] In some embodiments, after the tracking code is put online, it may also include: sampling the running data corresponding to the tracking code from the data storage area to obtain sampled data; based on the sampled data, determining the compliance rate of the tracking, the compliance rate is an indicator for measuring the quality of the tracking; if the compliance rate is lower than a preset threshold, notifying the second object corresponding to the second processing node in the form of a work order so that it can analyze whether the tracking is compliant; if the analysis result shows that the data structure is not compliant, notifying the first object of the first processing node to correct the data structure definition of the tracking; if the analysis result shows that the log record is not compliant, notifying the third object of the third processing node to repair the tracking code.

[0094] In the disclosed embodiment, the real-time data collection module (tcbox) is a module for collecting data from client devices or systems in real time, which is responsible for capturing user behaviors or system events and transmitting these data to the server or data processing platform for processing and analysis. It ensures the timeliness and accuracy of data collection and can perform preliminary processing or filtering on the client side.

[0095] In some embodiments, sampling data acquisition includes: when the tracking code is online, the system will sample the tracking operation data from the data storage area of ​​the tracking online service. The sampling receives the tracking data from the tcbox or other client devices through the interface, and then transmits it to the "point status" for inspection.

[0096] In some implementations, determining the compliance rate of a buried point can be divided into two calculation methods.

[0097] The first method is to calculate the UV compliance rate, the formula is UV = 100% - (UE / UT*100%), where UE represents the number of abnormal points, and UT represents the total number of points. If a certain point has an abnormal log, UE will be increased by 1, and this method is used to measure the overall compliance of the point.

[0098] The second method is to calculate the PV compliance rate, the formula is PV = PS / PT * 100%, where PS is the total number of normal logs, PT is the total number of logs. Every time a normal log appears, PS increases by 1. This method is used to evaluate the accuracy of log records and the quality stability of data.

[0099] In some implementations, the second object corresponding to the second processing node is notified in the form of a work order, including: if the compliance rate is lower than a preset threshold, the system will generate a work order and notify the second object (usually a BP or a relevant auditor) to analyze the compliance issue. The notification will be issued in the form of a work order and synchronized to the BP to ensure that the problem is tracked and handled in a timely manner.

[0100] In some embodiments, correcting the tracking point database structure or log includes: if the analysis result shows that the data structure is not compliant (such as field, data type mismatch), notifying the first object (such as PM) to correct the database structure.

[0101] In some implementations, if the log record is not compliant, including: incomplete data, field errors, the system will notify a third party (such as RD) to repair the tracking code to make the log record comply with business and technical specifications.

[0102] For example, an e-commerce platform launched a set of tracking code to track users' payment operations. After going online, the system sampled the operating data from the data storage area of ​​the tracking online service and calculated the compliance rate of the tracking. When using the UV compliance rate calculation, it was found that there were anomalies in the logs of some users' payment operations, resulting in an increase in UE and a compliance rate lower than the preset threshold. The system generated a work order and notified the BP for analysis, and found that the anomaly originated from the mismatch of field definitions in the database structure. Subsequently, the PM received the notification and corrected the database structure. On the other hand, some log records were incomplete, and the system notified the RD to repair the tracking code so that the log records met technical and business specifications. After repair and retesting, the compliance rate was improved to the normal range, and the system was able to accurately track user payment behavior.

[0103] In this way, data sampling and compliance rate calculation can be used to timely discover and resolve data anomalies or log non-compliance issues, ensuring the accuracy and consistency of data collection. Through the automated work order process, problems can be promptly fed back and fixed, thereby improving the reliability of the tracking system and ensuring the quality of business data.

[0104] In some embodiments, the data processing method may also include: recording the operation object, operation time, related requirements and modification records of each processing node, so that other processing nodes can view or trace the detailed information of the buried points.

[0105] In some implementations, when each processing node performs an operation, the system automatically records the identity of the operator of the node (such as PM, RD, BP, etc.), the specific time of the operation, and the requirements or changes performed. In addition, any modification of requirements, code repairs, or adjustments to log formats will be recorded in detail in the system. This information can be viewed by other processing nodes through the system interface to ensure the transparency and traceability of the tracking process, which is convenient for subsequent analysis, troubleshooting, or improvement.

[0106] For example, when a data analysis platform was developing a tracking system, the PM submitted a tracking requirement for tracking user login operations. The system automatically recorded the PM's identity, submission time, and requirement content. Later, the RD completed the tracking development and submitted it, and the system also recorded the developer's identity, development time, and code modification records. QA discovered problems during the test and provided feedback, and the system recorded the feedback content and corresponding modifications in detail. Each operation node in the entire process is fully recorded to facilitate subsequent queries and backtracking, ensuring that each modification and change in requirements is transparent and traceable.

[0107] In this way, by automatically recording and tracing the operation information of the processing nodes, the transparency and traceability of the tracking process are ensured, which facilitates the rapid discovery and resolution of problems and improves the efficiency and accuracy of tracking management.

[0108] In some embodiments, the data processing method may also include: receiving tracking point operation records from various types of equipment; analyzing and determining the current status of each tracking point based on the tracking point operation records; and performing differentiated processing on the corresponding tracking point operation records according to the different status of the tracking points.

[0109] In some embodiments, receiving the tracking point operation records from various devices includes: different devices such as the client, personal computer (PC) and server report the tracking point information they collect to tcbox, which serves as the core service end for receiving log data. The tracking point data of each device is transmitted to tcbox via the network to ensure that the tracking point data of all terminals are uniformly collected and processed.

[0110] In some embodiments, when analyzing and determining the current status of each tracking point based on the tracking point operation record, it includes: tcbox will process the tracking point differently according to its status. For example, if the tracking point has been abandoned or offline, tcbox will directly discard the data of these tracking points to avoid unnecessary waste of storage and processing resources. If the tracking point is not online, that is, it has not passed the tracking point approval process, tcbox will store the data normally in the log verification queue, and store the data in the data, and then transfer it to the distributed search and analysis engine (Elasticsearch, ES) storage service. These data are only used for testing and verification of the platform and will not be used in formal data reports. For the tracking points that have been put online, tcbox will store the data in all-flash storage (All-Flash Storage, AFS), and then transfer it to the universal data warehouse (Universal Data Warehouse, UDW) for use by downstream data processors, or forward these data to other systems or business parties in need.

[0111] In some embodiments, according to the different status of the burial point, the specific method of performing differentiated processing on the corresponding burial point operation records includes: the abandoned burial point data will be discarded, the burial point data that is not online will be stored and used for testing and verification, and the burial point data that is online will enter the formal data processing process to ensure that the data of each burial point is processed and managed most appropriately according to its status.

[0112] For example, an e-commerce platform has launched a new tracking system to track users' product browsing behavior. The client, PC, and server report the tracking data to tcbox, and the platform receives the tracking operation records of these devices in real time. The system analyzes the status of different tracking points based on these operation records. For old tracking points that have been offline, the system directly discards the relevant data; for test tracking points that have not yet passed approval, tcbox stores the data in the ES storage service for testing; and for the tracking data that has been officially launched, tcbox stores it in AFS and transfers it to UDW for business analysis and report generation.

[0113] In this way, by performing differentiated processing on tracking data in different states, unnecessary data storage and processing burdens are effectively reduced, and system performance and efficiency are improved. The data from online tracking points can be accurately captured and managed, providing high-quality data support for downstream data analysis.

[0114] In some embodiments, according to the different states of the burial point, the corresponding burial point operation records are processed differentially, and also include: if the state of the burial point is abandoned, its operation record is directly discarded; if the state of the burial point is offline, its operation record is stored according to the preset first storage strategy; if the state of the burial point is online, its operation record is stored according to the preset second storage strategy.

[0115] In some embodiments, if the state of the tracking point is abandoned, its operation record is directly discarded, including: when the system detects that the tracking point has been marked as abandoned or offline, tcbox will immediately discard the data after receiving the operation data of the tracking point to avoid unnecessary waste of storage and processing resources. The data will not be transmitted to any log storage or analysis system, thereby reducing the burden on the system.

[0116] In some implementations, if the status of the tracking point is offline, its operation record is stored according to the preset first storage strategy, including: when tcbox receives the offline tracking point data, it will be stored normally in the log verification queue, and the data will be further transmitted to the storage service for testing and verification purposes. These data will not be used for formal reports and business analysis, but only for testing tools within the platform so that developers and testers can verify and debug them.

[0117] In some implementations, if the status of the tracking point is online, its operation records are stored according to the preset second storage strategy, including: tcbox will store the data of the online tracking point in the fast storage service to ensure that the data can be quickly accessed, and further transferred to the persistent storage service to provide support for downstream data processing and business needs. These data can be used for formal data reporting, analysis and decision-making processes, and can be called by other systems or business parties.

[0118] In this way, by performing differentiated processing according to the status of the tracking point, the utilization of system resources is effectively optimized. Abandoned tracking point data is discarded in a timely manner to avoid unnecessary storage and processing burdens; the tracking point data that has not been put online is properly stored for testing and verification according to the first storage strategy, which does not affect the formal data flow; the tracking point data that has been put online is efficiently stored through the second storage strategy to ensure that the data can be used for formal analysis and report generation.

[0119] Figure 6 The schematic diagram of the architecture of the tracking point management system is shown in FIG. Figure 6As shown, the tracking point management system includes two parts: tracking point management platform and tracking point online service. The tracking point management platform is responsible for the whole process management from tracking point application to online launch, and the tracking point online service is responsible for receiving tracking point operation records from each end; based on the tracking point operation records, analyze and determine the current status of each tracking point; according to the different status of the tracking point, the corresponding tracking point operation records are processed differently. After the tracking point code is launched, the operation data corresponding to the tracking point code is sampled from the data storage area to obtain the sampled data; based on the sampled data, the compliance rate of the tracking point is determined; if the compliance rate is lower than the preset threshold, the BP is notified in the form of a work order so that it can analyze whether the tracking point is compliant; if the analysis result shows that the data structure is not compliant, the PM is notified to correct the data structure definition of the tracking point; if the analysis result shows that the log record is not compliant, the RQ is notified to repair the tracking point code.

[0120] The present disclosure provides a data processing device, such as Figure 7 As shown, the data processing device may include: a tracking application module 701, which is used to receive a tracking application, where the tracking application is an application submitted by a first object through a first processing node of a tracking management platform, and the tracking application includes a tracking requirement; a specification review module 702, which is used to push the tracking application to a second processing node, so that a second object corresponding to the second processing node can conduct a specification review on the tracking requirement according to business requirements and technical specifications; a tracking development module 703, which is used to push the tracking requirement to a third processing node if the processing result of the second processing node is approved, so that a third object corresponding to the third processing node can develop based on the tracking requirement , generating tracking code; code testing module 704, used for, when the processing result of the third processing node is development completion, pushing the tracking code to the fourth processing node, so that the fourth object corresponding to the fourth processing node tests the tracking code and obtains test data; acceptance confirmation module 705, used for, when the processing result of the fourth processing node is test success, pushing the test data to the first processing node, so that the first object accepts the test data; online permission module 706, used for, when the processing result of the first processing node is acceptance passed, generating a response result of the tracking application, the response result including permission for the tracking code to go online.

[0121] In some embodiments, the online permission module 706 is used to: when the processing result of the first processing node is accepted, push the test data to the second processing node so that the second object can accept the test data; when the processing result of the second processing node is accepted, generate a response result.

[0122] In some embodiments, the device further includes: a return processing module ( Figure 7(not shown), used for: when the processing result of the second processing node is that the review fails, returning the tracking application to the first processing node, together with the specific reason for the review failure, so that the first object can modify the tracking requirement according to the feedback and resubmit it; when the processing result of the fourth processing node is that the test fails, returning the specific reason for the test failure to the third processing node, so that the third object can repair it according to the test feedback, and resubmit it to the fourth processing node for testing after the repair; when the processing result of the first processing node is that the acceptance fails, if it is a problem with the function implementation or the code itself, it will be returned to the third processing node, so that the third object can repair it according to the acceptance feedback.

[0123] In some embodiments, the code testing module 704 is used to: when the processing result of the third processing node is that the development is completed, verify whether the tracking code meets the technical specifications and business requirements; after the verification is passed, push the tracking code to the fourth processing node.

[0124] In some embodiments, the acceptance confirmation module 705 is used to: when the processing result of the fourth processing node is a successful test, verify whether the test data conforms to the expected behavior of the tracking code and whether the test data conforms to the data specification and quality standards; after the verification is passed, push the test data to the first processing node for acceptance.

[0125] In some embodiments, the device further comprises: a sampling module ( Figure 7 (not shown), used to sample the running data corresponding to the embedded code from the data storage area to obtain the sampled data; determine the module ( Figure 7 Not shown), used to determine the compliance rate of the tracking point based on the sampling data, and the compliance rate is an indicator for measuring the quality of the tracking point; notification module ( Figure 7 (not shown), if the compliance rate is lower than a preset threshold, then the second object corresponding to the second processing node is notified in the form of a work order so that it can analyze whether the tracking point is compliant; if the analysis result shows that the data structure is not compliant, then the first object of the first processing node is notified to correct the data structure definition of the tracking point; if the analysis result shows that the log record is not compliant, then the third object of the third processing node is notified to repair the tracking point code.

[0126] In some embodiments, the device further includes: a recording module ( Figure 7 (not shown) is used to record the operation object, operation time, related requirements and modification records of each processing node, so that other processing nodes can view or trace the detailed information of the buried point.

[0127] In some embodiments, the device further includes: a receiving module ( Figure 7 (not shown) for receiving the point operation records from various devices; a status analysis module ( Figure 7(not shown), used to analyze and determine the current state of each tracking point based on the tracking point operation record; Differentiation processing module ( Figure 7 (not shown) is used to perform differentiated processing on corresponding burying point operation records according to different states of the burying points.

[0128] In some embodiments, the differential processing module is used to: if the status of the burial point is abandoned, directly discard its operation record; if the status of the burial point is offline, store its operation record according to a preset first storage strategy; if the status of the burial point is online, store its operation record according to a preset second storage strategy.

[0129] For the description of specific functions and examples of each module and submodule of the device in the embodiment of the present disclosure, reference can be made to the relevant description of the corresponding steps in the above method embodiment, which will not be repeated here.

[0130] The data processing device of the disclosed embodiment solves the problems of chaotic tracking point management, non-standard approval, and low acceptance efficiency through a unified online tracking point management system, realizes platform-based and standardized management, improves collaborative efficiency, data accuracy and verification quality, and reduces duplicate tracking points and waste of resources.

[0131] The present disclosure provides a scenario diagram of a data processing method, such as Figure 8 shown.

[0132] As mentioned above, the data processing method provided by the embodiment of the present disclosure is applied to electronic devices. Electronic devices are intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices, and other similar computing devices.

[0133] Specifically, the electronic device can perform the following operations:

[0134] receiving a tracking application, where the tracking application is an application submitted by the first object through the first processing node of the tracking management platform, and the tracking application includes a tracking requirement;

[0135] Push the tracking application to the second processing node, so that the second object corresponding to the second processing node can conduct a normative review of the tracking demand according to business requirements and technical specifications;

[0136] If the processing result of the second processing node is approved, the tracking point requirement is pushed to the third processing node, so that the third object corresponding to the third processing node is developed based on the tracking point requirement to generate the tracking point code;

[0137] When the processing result of the third processing node is that the development is completed, the tracking code is pushed to the fourth processing node, so that the fourth object corresponding to the fourth processing node tests the tracking code to obtain test data;

[0138] When the processing result of the fourth processing node is that the test is successful, the test data is pushed to the first processing node so that the first object can accept the test data;

[0139] When the processing result of the first processing node is acceptance passed, a response result of the tracking point application is generated, and the response result includes permission for the tracking point code to go online.

[0140] It should be understood that Figure 8 The scene diagram shown is only illustrative and not restrictive. Those skilled in the art can Figure 8 Various obvious changes and / or substitutions can be made to the examples, and the resulting technical solutions still fall within the scope of the disclosure of the embodiments of the present disclosure.

[0141] In the technical solution disclosed herein, the acquisition, storage and application of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0142] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

[0143] Fig. 9 A schematic block diagram of an example electronic device 900 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.

[0144] like Fig. 9As shown, the device 900 includes a computing unit 901, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 902 or a computer program loaded from a storage unit 908 to a random access memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the device 900 can also be stored. The computing unit 901, the ROM 902, and the RAM 903 are connected to each other via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0145] A number of components in the device 900 are connected to the I / O interface 905, including: an input unit 906, such as a keyboard, a mouse, etc.; an output unit 907, such as various types of displays, speakers, etc.; a storage unit 908, such as a disk, an optical disk, etc.; and a communication unit 909, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 909 allows the device 900 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0146] The computing unit 901 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a CPU, a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSP), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 901 performs the various methods and processes described above, such as data processing methods. For example, in some embodiments, the data processing method may be implemented as a computer software program, which is tangibly included in a machine-readable medium, such as a storage unit 908. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 900 via the ROM 902 and / or the communication unit 909. When the computer program is loaded into the RAM 903 and executed by the computing unit 901, one or more steps of the data processing method described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to execute the data processing method in any other appropriate manner (eg, by means of firmware).

[0147] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0148] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0149] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory (EPROM), a 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 of the foregoing.

[0150] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0151] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: Local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

[0152] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0153] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0154] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the principles of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A data processing method, comprising: receiving a tracking application, where the tracking application is an application submitted by a first object through a first processing node of a tracking management platform, and the tracking application includes a tracking requirement; Pushing the tracking point application to a second processing node, so that a second object corresponding to the second processing node can conduct a normative review of the tracking point requirement according to business requirements and technical specifications; If the processing result of the second processing node is approved, the tracking point requirement is pushed to the third processing node, so that the third object corresponding to the third processing node is developed based on the tracking point requirement to generate tracking point code; When the processing result of the third processing node is that the development is completed, the tracking code is pushed to a fourth processing node, so that a fourth object corresponding to the fourth processing node tests the tracking code to obtain test data; When the processing result of the fourth processing node is that the test is successful, the test data is pushed to the first processing node so that the first object can accept the test data; When the processing result of the first processing node is acceptance passed, a response result of the tracking point application is generated, and the response result includes permission for the tracking point code to go online.

2. The method according to claim 1, wherein: When the processing result of the first processing node is acceptance passed, generating a response result of the tracking point application includes: If the processing result of the first processing node is acceptance passed, pushing the test data to the second processing node so that the second object can accept the test data; When the processing result of the second processing node is acceptance passed, the response result is generated.

3. The method according to claim 1, further comprising: If the processing result of the second processing node is that the review fails, the tracking application is returned to the first processing node with the specific reason for the review failure, so that the first object can modify the tracking requirement according to the feedback and resubmit it; If the processing result of the fourth processing node is that the test is unsuccessful, the specific reason for the test failure is returned to the third processing node, so that the third object can repair it according to the test feedback and resubmit it to the fourth processing node for testing after the repair; When the processing result of the first processing node is that the acceptance is unsuccessful, if it is a problem with the function implementation or the code itself, it will be returned to the third processing node so that the third object can repair it according to the acceptance feedback.

4. The method according to claim 1, wherein: When the processing result of the third processing node is that the development is completed, pushing the tracking code to the fourth processing node includes: When the processing result of the third processing node is that the development is completed, verify whether the embedding code complies with the technical specifications and the business requirements; after the verification is passed, push the embedding code to the fourth processing node.

5. The method according to claim 1, wherein: When the processing result of the fourth processing node is that the test is successful, pushing the test data to the first processing node includes: When the processing result of the fourth processing node is that the test is successful, verify whether the test data conforms to the expected behavior of the embedding code and whether the test data conforms to the data specification and quality standards; after the verification is passed, push the test data to the first processing node for acceptance.

6. The method according to claim 1, wherein: After the tracking code is launched, it also includes: Sampling the operation data corresponding to the embedding code from the data storage area to obtain sampled data; Based on the sampling data, determine the compliance rate of the buried point; If the compliance rate is lower than a preset threshold, the second object of the second processing node is notified in the form of a work order so that the second object can analyze whether the tracking point is compliant; If the analysis result shows that the data structure is not compliant, notifying the first object of the first processing node to correct the data structure definition of the tracking point; If the analysis result shows that the log record is not compliant, the third object of the third processing node is notified to repair the embedded code.

7. The method according to any one of claims 1 to 6, further comprising: Record the operation object, operation time, related requirements and modification records of each processing node so that other processing nodes can view or trace the detailed information of the buried point.

8. The method according to claim 7, further comprising: Receive tracking point operation records from various equipment; Based on the tracking point operation record, analyze and determine the current status of each tracking point; According to the different states of the tracking points, the corresponding tracking point operation records are processed differently.

9. The method according to claim 8, wherein: According to different states of the tracking points, the corresponding tracking point operation records are processed differently, including: If the status of the tracking point is abandoned, its operation record is directly discarded; If the tracking point is not online, its operation record is stored according to the preset first storage strategy; If the status of the tracking point is online, its operation record is stored according to the preset second storage strategy.

10. A data processing device, comprising: A tracking point application module, configured to receive a tracking point application, wherein the tracking point application is an application submitted by a first object through a first processing node of a tracking point management platform, and the tracking point application includes a tracking point requirement; A specification review module, used for pushing the tracking point application to the second processing node, so that the second object corresponding to the second processing node can conduct a specification review on the tracking point requirement according to business requirements and technical specifications; A tracking point development module, used for pushing the tracking point requirement to a third processing node when the processing result of the second processing node is approved, so that a third object corresponding to the third processing node is developed based on the tracking point requirement to generate tracking point code; A code testing module, configured to push the embedding code to a fourth processing node when the processing result of the third processing node is that the development is completed, so that the embedding code is tested by a fourth object corresponding to the fourth processing node to obtain test data; An acceptance confirmation module, configured to push the test data to the first processing node when the processing result of the fourth processing node is that the test is successful, so that the first object can accept the test data; The online permission module is used to generate a response result of the tracking point application when the processing result of the first processing node is accepted, and the response result includes permission for the tracking point code to go online.

11. The device according to claim 10, wherein: The online permission module is used to: If the processing result of the first processing node is acceptance passed, pushing the test data to the second processing node so that the second object can accept the test data; When the processing result of the second processing node is acceptance passed, the response result is generated.

12. The apparatus according to claim 10, further comprising: Return processing module, used to: If the processing result of the second processing node is that the review fails, the tracking application is returned to the first processing node with the specific reason for the review failure, so that the first object can modify the tracking requirement according to the feedback and resubmit it; If the processing result of the fourth processing node is that the test is unsuccessful, the specific reason for the test failure is returned to the third processing node, so that the third object can repair it according to the test feedback and resubmit it to the fourth processing node for testing after the repair; When the processing result of the first processing node is that the acceptance is unsuccessful, if it is a problem with the function implementation or the code itself, it will be returned to the third processing node so that the third object can repair it according to the acceptance feedback.

13. The device according to claim 10, wherein: The code testing module is used to: When the processing result of the third processing node is that the development is completed, verify whether the embedding code complies with the technical specifications and the business requirements; after the verification is passed, push the embedding code to the fourth processing node.

14. The device according to claim 10, wherein: The acceptance confirmation module is used to: When the processing result of the fourth processing node is that the test is successful, verify whether the test data conforms to the expected behavior of the embedding code and whether the test data conforms to the data specification and quality standards; after the verification is passed, push the test data to the first processing node for acceptance.

15. The apparatus according to claim 10, further comprising: A sampling module, used for sampling the operation data corresponding to the embedding code from the data storage area to obtain sampled data; A determination module, used to determine the compliance rate of the buried point based on the sampling data; a notification module, configured to notify the second object of the second processing node in the form of a work order if the compliance rate is lower than a preset threshold, so that the second object can analyze whether the tracking point is compliant; If the analysis result shows that the data structure is not compliant, notifying the first object of the first processing node to correct the data structure definition of the tracking point; If the analysis result shows that the log record is not compliant, the third object of the third processing node is notified to repair the embedded code.

16. The device according to any one of claims 10 to 15, further comprising: The recording module is used to record the operation object, operation time, related requirements and modification records of each processing node so that other processing nodes can view or trace the detailed information of the buried point.

17. The apparatus according to claim 16, further comprising: The receiving module is used to receive the tracking point operation records from various devices; A status analysis module, used to analyze and determine the current status of each tracking point based on the tracking point operation record; The differential processing module is used to perform differential processing on the corresponding tracking point operation records according to the different states of the tracking points.

18. The device according to claim 17, wherein: The differentiation processing module is used for: If the status of the tracking point is abandoned, its operation record is directly discarded; If the tracking point is not online, its operation record is stored according to the preset first storage strategy; If the status of the tracking point is online, its operation record is stored according to the preset second storage strategy.

19. An electronic device comprising: at least one processor; as well as a memory communicatively connected to at least one processor; wherein, The memory stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 9.

20. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are for causing a computer to execute a method according to any one of claims 1-9.

21. A computer program product comprising a computer program stored on a storage medium, the computer program implementing the method according to any one of claims 1 to 9 when executed by a processor.

Images