Data burying point management method and device, server and storage medium

Abstract

The invention provides a data burying point management method and device, a server and a storage medium, and the method comprises the steps: obtaining burying point demand information passing the verification, and pushing the burying point demand information to a developer; obtaining a target burying point code written by the developer based on the burying point demand information, and controlling a test client containing the target burying point code to execute a test case associated with the burying point demand information; acquiring a plurality of burying point data reported by the test client; according to the multiple pieces of burying point data and the burying point demand information, the target burying point code is verified, and the target burying point code is stored under the condition that the target burying point code passes verification. According to the method, the accuracy of the burying point codes is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a data point management method, device, server and storage medium. Background Art

[0002] In the era of big data, data plays a vital role in verifying product ideas, finding improvement points for applications, training artificial intelligence algorithms, finding strategic implementation directions, and efficient reporting within the company. For example, data can be buried in financial applications to collect and analyze user behavior data on various insurance products or financial products, so as to help financial companies recommend insurance products or financial products to users, etc., to improve customer stickiness. For another example, data can also be buried in medical applications to collect and analyze the behavior data of medical staff or patients, so as to improve and upgrade medical applications and bring better user experience to medical staff or patients.

[0003] At present, the tracking point operation personnel usually submit the tracking point requirement Excel form to the developer through the internal mailbox of the enterprise, and the developer writes the corresponding tracking point code according to the tracking point requirement Excel form. However, the attribute information of the tracking point fields in the tracking point requirement Excel form is mainly filled in manually by the tracking point operation personnel, which has a high error rate, resulting in the tracking point code written by the developer not meeting the tracking point requirement and unable to guarantee the accuracy of the tracking point code. Therefore, how to improve the accuracy of the tracking point code is an urgent problem to be solved. Summary of the invention

[0004] The embodiments of the present application provide a data tracking management method, device, server and storage medium, aiming to improve the accuracy of tracking codes.

[0005] In a first aspect, an embodiment of the present application provides a data tracking management method, including:

[0006] Acquire the tracking demand information that has passed the review, and push the tracking demand information to the developer, wherein the attribute information of the tracking field in the tracking demand information is selected by the tracking operator through the tracking demand page displayed on the tracking management client;

[0007] Obtaining the target tracking code written by the developer based on the tracking requirement information, and controlling the test client containing the target tracking code to execute the test case associated with the tracking requirement information;

[0008] Acquire multiple tracking data reported by the test client, where the multiple tracking data are reported by the test client based on the target tracking code during execution of the test case;

[0009] The target burying point code is verified according to the multiple burying point data and the burying point requirement information, and if the target burying point code passes the verification, the target burying point code is stored.

[0010] In a second aspect, an embodiment of the present application further provides a data embedding point management device, the data embedding point management device comprising:

[0011] An acquisition module is used to acquire the approved tracking demand information and push the tracking demand information to the developer. The attribute information of the tracking field in the tracking demand information is selected by the tracking operator through the tracking demand page displayed by the tracking management client.

[0012] The acquisition module is also used to acquire the target tracking code written by the developer based on the tracking requirement information;

[0013] A control module, used to control the test client containing the target tracking code to execute the test case associated with the tracking requirement information;

[0014] The acquisition module is further used to acquire a plurality of tracking point data reported by the test client, wherein the plurality of tracking point data is reported by the test client based on the target tracking point code during the execution of the test case;

[0015] A verification module is used to verify the target burying point code according to the multiple burying point data and the burying point requirement information, and store the target burying point code if the target burying point code passes the verification.

[0016] In a third aspect, an embodiment of the present application further provides a server, comprising a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, the data embedding point management method as described in the first aspect is implemented.

[0017] In a fourth aspect, an embodiment of the present application further provides a storage medium, on which a computer program is stored, wherein when the computer program is executed by a processor, the data embedding point management method as described in the second aspect is implemented.

[0018] The embodiments of the present application provide a data burying point management method, device, server and storage medium. Since the attribute information of the burying point field in the burying point requirement information is selected by the burying point operator through the burying point requirement page, it does not need to be filled in manually by the burying point operator, which effectively reduces the error rate and makes the burying point requirement information more accurate. In this way, the developer can write accurate target burying point code based on the accurate burying point requirement information. After writing the target burying point code, the target burying point code is further verified according to multiple burying point data reported by the test client containing the target burying point code and the burying point requirement information. When the target burying point code passes the verification, the target burying point code is stored, which makes the stored target burying point code more accurate, effectively improves the accuracy of the burying point code, and can reduce the occurrence of abnormal situations when using the burying point code. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0020] Figure 1 It is a flow chart of a data point management method provided in an embodiment of the present application;

[0021] Figure 2 It is a schematic diagram of a point-of-sale requirement page in an embodiment of the present application;

[0022] Figure 3 This is a schematic diagram of a page for adding new fields in an embodiment of the present application;

[0023] Figure 4 It is a schematic block diagram of a data embedding management device provided in an embodiment of the present application;

[0024] Figure 5 It is a schematic block diagram of the structure of a server provided in an embodiment of the present application.

[0025] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0027] The flowcharts shown in the accompanying drawings are only examples and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may also be decomposed, combined or partially merged, so the actual execution order may change according to actual conditions.

[0028] At present, the tracking point operation personnel usually submit the tracking point requirement Excel form to the developer through the internal mailbox of the enterprise, and the developer writes the corresponding tracking point code according to the tracking point requirement Excel form. However, the attribute information of the tracking point fields in the tracking point requirement Excel form is mainly filled in manually by the tracking point operation personnel, which has a high error rate, resulting in the tracking point code written by the developer not meeting the tracking point requirement and failing to guarantee the accuracy of the tracking point code.

[0029] To solve the above problems, the embodiments of the present application provide a data point management method, device, server and storage medium. In the embodiments of the present application, since the attribute information of the point field in the point demand information is selected by the point operator through the point demand page, it does not need to be filled in manually by the point operator, which effectively reduces the error rate and makes the point demand information more accurate. In this way, the developer can write accurate target point code based on accurate point demand information, and after writing the target point code, the target point code is further verified according to the multiple point data reported by the test client containing the target point code and the point demand information, so that when the target point code passes the verification, the target point code is stored, so that the stored target point code is more accurate, which effectively improves the accuracy of the point code and can reduce the occurrence of abnormal situations when using the point code.

[0030] In addition, the attribute information of the tracking point fields in the tracking point requirements Excel table is mainly filled in manually by the tracking point operators, and the tracking point requirements manually filled in by the tracking point administrators are in various forms, which requires developers to spend more time communicating with the tracking point operators, and the development efficiency of the tracking point code is low. The attribute information of the tracking point fields in the embodiment of the present application is selected by the tracking point operators through the tracking point requirements page, and does not need to be filled in manually by the tracking point operators. The standardization of the attribute information of the tracking point fields can be guaranteed, so that developers can better understand the tracking point requirements, thereby better writing the tracking point code, thereby improving the development efficiency of the tracking point code.

[0031] Among them, the data embedding management method can be applied to servers. The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), as well as big data and artificial intelligence platforms.

[0032] In conjunction with the accompanying drawings, some embodiments of the present application are described in detail below. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0033] See also Figure 1 , Figure 1 The figure is a flow chart of a data point management method provided in an embodiment of the present application. The data point management method can be applied to a server.

[0034] like Figure 1 As shown, the data tracking management method includes steps S101 to S104.

[0035] Step S101, obtain the approved tracking demand information, and push the tracking demand information to the developer. The attribute information of the tracking field in the tracking demand information is selected by the tracking operator through the tracking demand page displayed on the tracking management client.

[0036] In this embodiment, the embedding demand information includes embedding fields and attribute information of the embedding fields. The names of the embedding fields are manually input by the embedding operators through the embedding demand page displayed by the embedding management client, and the attribute information of the embedding fields is selected by the embedding operators through the embedding demand page displayed by the embedding management client. The embedding management client has the functions of submitting embedding demands, reviewing embedding demands, and adding extension fields. The embedding management client can run on a terminal device, which can include a smart phone, a tablet computer, a television, a laptop or a personal computer.

[0037] In some embodiments, the server obtains the reviewed tracking demand information, and pushing the tracking demand information to the developer may include: upon obtaining the tracking demand review request sent by the tracking demand management client, pushing the tracking demand review prompt information to the tracking demand administrator to prompt the tracking demand administrator to review the tracking demand information in the tracking demand review request; obtaining the review result of the tracking demand information sent by the tracking demand management client, which is sent by the tracking demand management client in response to the tracking demand administrator clicking the reject button or the agree button in the displayed tracking demand review page; when the review result is that the tracking demand information has passed the review, pushing the tracking demand information to the developer. Among them, the developer can obtain the pushed tracking demand information through the company's internal chat tool or mailbox, or obtain the pushed tracking demand information through the tracking demand management client.

[0038] In some embodiments, the tracking point management client displays a tracking point demand review page, which includes the tracking point demand information to be reviewed, a reject button and an agree button; in response to the tracking point administrator clicking the reject button, a first review result of the tracking point demand information is sent to the server, and the first review result is that the tracking point demand information has passed the review; in response to the tracking point administrator clicking the agree button, a second review result of the tracking point demand information is sent to the server, and the second review result is that the tracking point demand information has not passed the review.

[0039] In some embodiments, the tracking point management client displays a tracking point demand submission page, which includes a tracking point field input box, an input box for attribute information of the tracking point field, and a submit review button; the tracking point field input box displays the tracking point field input by the tracking point operator; the attribute information input box displays the attribute information selected by the tracking point operator; in response to the tracking point operator clicking the submit review button, a tracking point demand review request is sent to the server based on the tracking point fields and attribute information currently displayed on the tracking point demand submission page.

[0040] In some embodiments, the attribute information of the tracking point field includes the tracking point platform, version number, requirement type, project name, event type, extended field information and functional module. Among them, the attribute information of the tracking point field also includes reporting time, remark information and card link, etc. The extended field information includes the extended field and the attribute information of the extended field. The attribute information of the extended field includes the remark information, English name, Chinese name, field type, field value type and field value format of the extended field.

[0041] For example, Figure 2As shown, the tracking operator can select the tracking platform through the tracking platform check box in the tracking requirement submission page, select the tracking version number through the version number selection box, select the specific requirement type through the requirement type selection box, select the specific project name through the project name selection box, enter the name of the tracking field through the display name input box, and select the specific event type through the event type selection box. Select the specific extension field through the extension field selection box, enter the remark description through the remark description input box, enter the limiting character through the limiting character input box, select the specific value type through the value type selection box, enter the function module name through the function module input box, enter the reporting time through the reporting time input box, enter the remark information through the remark information input box, click the Save Draft button to save the data on the current page as a draft, and click the Submit Review button to send the tracking requirement review request to the server.

[0042] In addition, the point-of-sale operator can add an extended field by clicking the first control 11, or delete the extended field by clicking the second control 12. Among them, the point-of-sale platform is a platform for reporting point-of-sale data, and the demand types include adding new points or iterating points. Event types may include clicks, pages, click_slide down, click_slide up, click_slide left, click_slide right, exposure, exposure_first appearance, timing, and technical reporting. Extended field information refers to the fields and field values ​​carried with the point-of-sale data. Functional module refers to the functional module of the point-of-sale code access client.

[0043] In some embodiments, part of the attribute information of the burying point field is selected by the burying point operator through the burying point requirement page displayed by the burying point management client, and another part of the attribute information of the burying point field is input by the burying point operator through the burying point requirement page displayed by the burying point management client. For example, the burying point platform, version number, requirement type, project name, event type, extension field and value type are selected by the burying point operator through the burying point requirement page displayed by the burying point management client, and the reporting time, remark information, card link, limiting character and function module are input by the burying point operator through the burying point requirement page displayed by the burying point management client.

[0044] In some embodiments, the attribute information of the tracking point field includes extended field information, and the extended field information is selected by the tracking point operator from the extended field database through the tracking point demand page. Among them, each extended field information in the extended field database is pre-established by the tracking point administrator through the field addition page, and the extended field information includes the English name, Chinese name, field type, tracking point demand identifier, field remark information, value remark information, field value type and field value format of the extended field.

[0045] In some embodiments, the server obtains an extension field addition request sent by the burying point management client, and the extension field information in the extension field addition request is input or selected by the burying point administrator through the field addition page displayed by the burying point management client; the extension field information in the extension field addition request is stored in the extension field database. For example, the name of the extension field, the field note information, and the value note information are input by the burying point administrator through the field addition page displayed by the burying point management client, and the field type, burying point requirement identifier, field value type, and field value format are selected by the burying point administrator through the field addition page displayed by the burying point management client. Among them, the burying point requirement identifier is used to indicate whether the extension field can be used for the burying point requirement new field. This embodiment realizes the addition of extension fields, which is convenient for the burying point administrator to pre-add extension fields as needed.

[0046] In some embodiments, the tracking point management client displays a field adding page; displays the extended field information entered or selected by the tracking point administrator on the field adding page; in response to the tracking point administrator clicking the Submit button on the field adding page, sends an extended field adding request to the server according to the currently displayed extended field information. Figure 3 As shown, the embedding administrator can select the field type through the field type check box in the field addition page, select the embedding requirement identifier through the embedding requirement identifier check box, enter the English name of the extended field through the field name input box, enter the Chinese name of the extended field through the Chinese name input box, select the field value type through the field value type selection box, select the field value format through the field value format selection box, enter the business definition of the field through the field note input box, and enter the reporting sample or other instructions through the value note input box. In addition, the embedding administrator can add a field value type and a corresponding field value format by clicking the third control 13, and delete the corresponding field value type and the corresponding field value format by clicking the fourth control 14.

[0047] Step S102: Obtain the target tracking code written by the developer based on the tracking requirement information, and control the test client containing the target tracking code to execute the test case associated with the tracking requirement information.

[0048] In this embodiment, after being assigned with the tracking point requirement information, the developer can write the target tracking point code according to the tracking point requirement information, and upload the target tracking point code to the server through the tracking point management client, and then control the test client containing the target tracking point code to execute the test case associated with the target tracking point code, so that the test client containing the target tracking point code can report the tracking point data to the server based on the target tracking point code during the execution of the test case, so that the server can collect multiple tracking point data reported by the test client. Among them, the test case associated with the tracking point requirement information is written by the developer according to the tracking point requirement information.

[0049] In some embodiments, controlling a test client containing target burying code to execute a test case associated with burying requirement information may include: obtaining a test case associated with burying requirement information, and controlling the test client containing target burying code to execute the test case multiple times; or obtaining multiple test cases associated with burying requirement information, and controlling the test client containing target burying code to execute each of the multiple test cases in sequence. The one or more test cases associated with the burying requirement information are written by developers based on the burying requirement information.

[0050] Step S103: Acquire multiple tracking data reported by the test client, where the multiple tracking data are reported by the test client based on the target tracking code during the execution of the test case.

[0051] In this embodiment, the multiple tracking data reported by the test client may be obtained by the test client executing the same test case multiple times, or may be obtained by the test client executing each test case in multiple different test cases in sequence.

[0052] Step S104: verify the target burying point code according to the multiple burying point data and the burying point requirement information, and store the target burying point code if the target burying point code passes the verification.

[0053] In this embodiment, the buried point data can be user behavior data, such as the user's browsing time, visited pages, click behavior, etc., or it can be conversion behavior data, such as the user's purchase behavior, etc., or it can be other data, which is not specifically limited in this embodiment of the present application. For example, the buried point data is the system performance data of the test client, such as page loading time, etc. Among them, if the target buried point code fails to pass the verification, the buried point error prompt information is pushed to the developer to prompt the developer that the target buried point code does not meet the buried point requirements and the developer needs to modify the buried point code.

[0054] In some embodiments, based on multiple buried point data and buried point requirement information, verifying the target buried point code may include: comparing the buried point field name in the buried point requirement information with the buried point field name in multiple buried point data; comparing the attribute information of the buried point field in the buried point requirement information with the attribute information of the buried point field in multiple buried point data; determining the null value rate of the buried point field based on multiple buried point data; determining that the target buried point code has passed the verification when the null value rate is less than or equal to a preset null value rate, the buried point field name in the buried point requirement information is the same as the buried point field name in the multiple buried point data, and the attribute information of the buried point field in the buried point requirement information is the same as the attribute information of the buried point field in the multiple buried point data; determining that the target buried point code has failed the verification when the null value rate is greater than the preset null value rate, the buried point field name in the buried point requirement information is different from the buried point field name in at least one buried point data, and / or the attribute information of the buried point field in the buried point requirement information is different from the attribute information of the buried point field in at least one buried point data.

[0055] In some embodiments, comparing the attribute information of the buried point field in the buried point demand information with the attribute information of the buried point field in the buried point data may include: determining whether the name of the buried point field in the buried point demand information is consistent with the name of the buried point field in the buried point data; determining whether the number of extended fields in the buried point demand information is consistent with the number of extended fields in the buried point data; determining whether the name of the extended field in the buried point demand information is consistent with the name of the extended field in the buried point data; determining whether the value type of the extended field in the buried point demand information is consistent with the value type of the extended field in the buried point data; determining whether the value format of the extended field in the buried point demand information is consistent with the value format of the extended field in the buried point data; if the name of the buried point field in the buried point demand information is consistent with the name of the buried point field in the buried point data, the number of extended fields in the buried point demand information is consistent with the number of extended fields in the buried point data, and the name of the extended field in the buried point demand information is consistent with the extended field of the buried point data If the name of the segment is consistent, the value type of the extended field in the embedding requirement information is consistent with the value type of the extended field in the embedding data, and the value format of the extended field in the embedding requirement information is consistent with the value format of the extended field in the embedding data, then it is determined that the attribute information of the embedding field in the embedding requirement information is the same as the attribute information of the embedding field in the embedding data; if the name of the embedding field in the embedding requirement information is inconsistent with the name of the embedding field in the embedding data, the number of extended fields in the embedding requirement information is inconsistent with the number of extended fields in the embedding data, the name of the extended field in the embedding requirement information is inconsistent with the name of the extended field in the embedding data, the value type of the extended field in the embedding requirement information is inconsistent with the value type of the extended field in the embedding data and / or the value format of the extended field in the embedding requirement information is inconsistent with the value format of the extended field in the embedding data, then it is determined that the attribute information of the embedding field in the embedding requirement information is different from the attribute information of the embedding field in the embedding data.

[0056] In some embodiments, after step S104, it also includes: obtaining the buried point comparison information and / or the field null value rate at a first interval time, the buried point comparison information is used to indicate whether the buried point data of the same buried point field reported by the clients of different platforms are consistent, and the buried point comparison information and the field null value rate are determined according to the buried point data reported by the clients containing the target buried point code in the production environment; when the buried point comparison information indicates that the buried point data of the same buried point field reported by the clients of different platforms are inconsistent and / or the field null value rate is greater than the preset null value rate threshold, output the buried point abnormality prompt information. Among them, outputting the buried point abnormality prompt information may include: sending the buried point abnormality prompt information to a preset mailbox. This embodiment outputs the buried point abnormality prompt information when the buried point data of the same buried point field reported by the clients of different platforms are inconsistent and / or the field null value rate is high, so that the user can know that the buried point is abnormal, which is convenient for the user to handle in time.

[0057] Among them, the first interval time and the preset null value rate threshold can be set by the user, and the embodiments of the present application do not specifically limit this. For example, the first interval time is 1 day, that is, the point-of-sale comparison information and / or the field null value rate is determined based on the point-of-sale data reported by the client containing the target point-of-sale code in the production environment on the previous day, that is, the point-of-sale comparison information and / or the field null value rate is obtained in a T+1 manner.

[0058] In some embodiments, after step S104, it also includes: obtaining the value of a preset key indicator and / or the value change information of the preset key indicator at a second interval, the value of the preset key indicator and the value change information of the preset key indicator are determined according to the tracking data reported by the client containing the target tracking code in the production environment; when the value of the preset key indicator is greater than the preset threshold and / or the value change information of the preset key indicator meets the preset change condition, output indicator abnormality prompt information. This embodiment outputs indicator abnormality prompt information when an abnormality occurs in a key indicator, so that the user can know that the indicator is abnormal, which is convenient for the user to handle in time.

[0059] Among them, the second interval time, the preset threshold value and the preset key indicator can be set by the user based on the actual situation, and the embodiment of the present application does not specifically limit this. For example, the second interval time is 1 day, that is, the value of the preset key indicator and / or the value change information of the preset key indicator is determined based on the previous day's tracking data reported by the client containing the target tracking code in the production environment, that is, the value of the preset key indicator and / or the value change information of the preset key indicator is obtained in a T+1 manner. The preset key indicator may include at least one of the utilization rate, usage duration and usage frequency.

[0060] In some embodiments, the value change information of the preset key indicator includes at least one of the value decrease amount, value increase amount, value decrease ratio, value increase ratio and continuous decrease days of the preset key indicator; the value change information of the preset key indicator satisfies the preset change condition including at least one of the value decrease amount of the preset key indicator is greater than the preset decrease amount, the value increase amount of the preset key indicator is greater than the preset increase amount, the value decrease ratio of the preset key indicator is greater than the first preset ratio, the value increase ratio of the preset key indicator is greater than the second preset ratio and the continuous decrease days of the preset key indicator are greater than the preset days. Among them, the preset decrease amount, the preset increase amount, the first preset ratio, the second preset ratio and the preset days can be set based on actual conditions, and the embodiments of the present application do not make specific limitations on this.

[0061] It should be noted that the value decrease of the preset key indicator is obtained by subtracting the value of the preset key indicator on the Tth day (the previous day) from the value of the preset key indicator on the T+1th day (the current day). The value increase of the preset key indicator is obtained by subtracting the value of the preset key indicator on the T+1th day (the current day) from the value of the preset key indicator on the Tth day (the previous day). The value decrease ratio of the preset key indicator is the ratio of the difference between the value of the preset key indicator on the Tth day (the previous day) and the value of the preset key indicator on the T+1th day (the current day) to the value of the preset key indicator on the Tth day (the previous day). The value increase ratio of the preset key indicator is the ratio of the difference between the value of the preset key indicator on the T+1th day (the current day) and the value of the preset key indicator on the Tth day (the previous day) to the value of the preset key indicator on the Tth day (the previous day). The number of consecutive days of decrease of the preset key indicator refers to the number of days on which the value line of the preset key indicator decreases.

[0062] In some embodiments, when the tracking point requirement information is obtained, the tracking point change record table is updated according to the tracking point requirement information. The tracking point change record table stores a record of each tracking point change, which may include the tracking point requirement type, tracking point version number, H5 production time, Native grayscale time, Native production time, tracking point number, tracking point Chinese name, demand proposer, tracking point technical person in charge, and tracking point changer. This embodiment updates the tracking point change record table to facilitate the query of causes and accountability in the event of subsequent tracking point anomalies.

[0063] See also Figure 4 , Figure 4 It is a schematic block diagram of a data point management device provided in an embodiment of the present application.

[0064] like Figure 4 As shown, the data embedding management device 100 includes:

[0065] The acquisition module 110 is used to acquire the approved tracking demand information and push the tracking demand information to the developer. The attribute information of the tracking field in the tracking demand information is selected by the tracking operator through the tracking demand page displayed by the tracking management client.

[0066] The acquisition module 110 is also used to acquire the target tracking code written by the developer based on the tracking requirement information;

[0067] The control module 120 is used to control the test client containing the target tracking code to execute the test case associated with the tracking requirement information;

[0068] The acquisition module 110 is further used to acquire a plurality of tracking data reported by the test client, wherein the plurality of tracking data are reported by the test client based on the target tracking code during the execution of the test case;

[0069] The verification module 130 is used to verify the target burying point code according to the multiple burying point data and the burying point requirement information, and store the target burying point code if the target burying point code passes the verification.

[0070] In some embodiments, the verification module 130 is further used to:

[0071] Comparing the burying point field name in the burying point demand information with the burying point field names in the multiple burying point data;

[0072] Comparing the attribute information of the burying point field in the burying point demand information with the attribute information of the burying point field in the plurality of burying point data;

[0073] Determine the null value rate of the buried point field according to the multiple buried point data;

[0074] In the case where the null value rate is less than or equal to the preset null value rate, the name of the burying point field in the burying point requirement information is the same as the name of the burying point field in the multiple burying point data, and the attribute information of the burying point field in the burying point requirement information is the same as the attribute information of the burying point field in the multiple burying point data, it is determined that the target burying point code passes the verification;

[0075] When the null value rate is greater than the preset null value rate, the name of the burying point field in the burying point requirement information is different from the name of the burying point field in at least one of the burying point data, and / or the attribute information of the burying point field in the burying point requirement information is different from the attribute information of the burying point field in at least one of the burying point data, it is determined that the target burying point code has failed the verification.

[0076] In some embodiments, the attribute information of the tracking point field includes extended field information, and the extended field information is selected by the tracking point operator from an extended field database through the tracking point demand page.

[0077] In some embodiments, the acquisition module 110 is also used to obtain an extended field addition request sent by the tracking point management client, wherein the extended field information in the extended field addition request is input or selected by the tracking point administrator through the field addition page displayed by the tracking point management client; and to store the extended field information in the extended field addition request in the extended field database.

[0078] In some embodiments, the data embedding management device 100 further includes:

[0079] The acquisition module 110 is further used to acquire the burying point comparison information and / or the field null value rate at a first interval time, the burying point comparison information is used to indicate whether the burying point data of the same burying point field reported by the clients of different platforms are consistent, and the burying point comparison information and the field null value rate are determined according to the burying point data reported by the client containing the target burying point code in the production environment;

[0080] A prompt output module is used to output abnormal burial point prompt information when the burial point comparison information indicates that the burial point data reported by clients of different platforms for the same burial point field are inconsistent and / or the field null value rate is greater than a preset null value rate threshold.

[0081] In some embodiments, the data embedding management device 100 further includes:

[0082] The acquisition module 110 is further configured to acquire a value of a preset key indicator and / or value change information of a preset key indicator at a second interval, wherein the value of the preset key indicator and the value change information of the preset key indicator are determined based on the tracking data reported by a client containing the target tracking code in a production environment;

[0083] The prompt output module is used to output indicator abnormality prompt information when the value of the preset key indicator is greater than the preset threshold and / or the value change information of the preset key indicator meets the preset change condition.

[0084] In some embodiments, the value change information of the preset key indicator includes at least one of a value decrease amount, a value increase amount, a value decrease ratio, a value increase ratio, and a number of consecutive decrease days of the preset key indicator;

[0085] The value change information of the preset key indicator satisfies the preset change conditions, including at least one of the following: the decrease in the value of the preset key indicator is greater than the preset decrease, the increase in the value of the preset key indicator is greater than the preset increase, the decrease ratio of the value of the preset key indicator is greater than the first preset ratio, the increase ratio of the value of the preset key indicator is greater than the second preset ratio, and the consecutive decrease days of the preset key indicator is greater than the preset number of days.

[0086] It should be noted that technical personnel in the relevant field can clearly understand that, for the convenience and conciseness of description, the specific working processes of the above-described devices and modules and units can refer to the corresponding processes in the aforementioned data embedding management method embodiment, and will not be repeated here.

[0087] The apparatus provided in the above embodiment may be implemented in the form of a computer program. The computer program may be Figure 5 Run on the server shown.

[0088] See also Figure 5 , Figure 5 It is a schematic block diagram of the structure of a server provided in an embodiment of the present application.

[0089] like Figure 5 As shown, the server includes a processor, a memory, and a network interface connected via a system bus, wherein the memory may include a storage medium and an internal memory.

[0090] The storage medium can store an operating system and a computer program. The computer program includes program instructions, and when the program instructions are executed, the processor can execute any data embedding management method.

[0091] The processor is used to provide computing and control capabilities to support the operation of the entire server.

[0092] The network interface is used for network communication, such as sending assigned tasks, etc. Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied. The specific server may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0093] It should be understood that the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0094] In one embodiment, the processor is used to run a computer program stored in the memory to implement the following steps:

[0095] Acquire the tracking demand information that has passed the review, and push the tracking demand information to the developer, wherein the attribute information of the tracking field in the tracking demand information is selected by the tracking operator through the tracking demand page displayed on the tracking management client;

[0096] Obtaining the target tracking code written by the developer based on the tracking requirement information, and controlling the test client containing the target tracking code to execute the test case associated with the tracking requirement information;

[0097] Acquire multiple tracking data reported by the test client, where the multiple tracking data are reported by the test client based on the target tracking code during execution of the test case;

[0098] The target burying point code is verified according to the multiple burying point data and the burying point requirement information, and if the target burying point code passes the verification, the target burying point code is stored.

[0099] In some embodiments, when the processor verifies the target burying point code according to the multiple burying point data and the burying point requirement information, it is used to implement:

[0100] Comparing the burying point field name in the burying point demand information with the burying point field names in the multiple burying point data;

[0101] Comparing the attribute information of the burying point field in the burying point demand information with the attribute information of the burying point field in the plurality of burying point data;

[0102] Determine the null value rate of the buried point field according to the multiple buried point data;

[0103] In the case where the null value rate is less than or equal to the preset null value rate, the name of the burying point field in the burying point requirement information is the same as the name of the burying point field in the multiple burying point data, and the attribute information of the burying point field in the burying point requirement information is the same as the attribute information of the burying point field in the multiple burying point data, it is determined that the target burying point code passes the verification;

[0104] When the null value rate is greater than the preset null value rate, the name of the burying point field in the burying point requirement information is different from the name of the burying point field in at least one of the burying point data, and / or the attribute information of the burying point field in the burying point requirement information is different from the attribute information of the burying point field in at least one of the burying point data, it is determined that the target burying point code has failed the verification.

[0105] In some embodiments, the attribute information of the tracking point field includes extended field information, and the extended field information is selected by the tracking point operator from an extended field database through the tracking point demand page.

[0106] In some embodiments, the processor is further configured to implement the following steps:

[0107] Obtaining an extension field adding request sent by the embedding point management client, where the extension field information in the extension field adding request is input or selected by the embedding point administrator through the field adding page displayed by the embedding point management client;

[0108] The extended field information in the extended field adding request is stored in the extended field database.

[0109] In some embodiments, after implementing the storage of the target embedding code, the processor is further configured to implement:

[0110] Acquire burying point comparison information and / or field null value rate at a first interval, wherein the burying point comparison information is used to indicate whether the burying point data of the same burying point field reported by clients of different platforms are consistent, and the burying point comparison information and the field null value rate are determined based on the burying point data reported by the client containing the target burying point code in the production environment;

[0111] When the burial point comparison information indicates that the burial point data reported by clients of different platforms for the same burial point field are inconsistent and / or the field null value rate is greater than a preset null value rate threshold, output burial point abnormality prompt information.

[0112] In some embodiments, after implementing the storage of the target embedding code, the processor is further configured to implement:

[0113] Acquire the value of a preset key indicator and / or the value change information of the preset key indicator at a second interval, wherein the value of the preset key indicator and the value change information of the preset key indicator are determined according to the tracking data reported by the client containing the target tracking code in the production environment;

[0114] When the value of the preset key indicator is greater than a preset threshold and / or the value change information of the preset key indicator meets the preset change condition, indicator abnormality prompt information is output.

[0115] In some embodiments, the value change information of the preset key indicator includes at least one of a value decrease amount, a value increase amount, a value decrease ratio, a value increase ratio, and a number of consecutive decrease days of the preset key indicator;

[0116] The value change information of the preset key indicator satisfies the preset change conditions, including at least one of the following: the decrease in the value of the preset key indicator is greater than the preset decrease, the increase in the value of the preset key indicator is greater than the preset increase, the decrease ratio of the value of the preset key indicator is greater than the first preset ratio, the increase ratio of the value of the preset key indicator is greater than the second preset ratio, and the consecutive decrease days of the preset key indicator is greater than the preset number of days.

[0117] It should be noted that technical personnel in the relevant field can clearly understand that, for the convenience and conciseness of description, the specific working process of the server described above can refer to the corresponding process in the aforementioned data embedding management method embodiment, and will not be repeated here.

[0118] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., including several instructions for enabling a server (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.

[0119] An embodiment of the present application also provides a storage medium, on which a computer program is stored. The computer program includes program instructions. The method implemented when the program instructions are executed can refer to the various embodiments of the data tracking point management method of the present application.

[0120] The storage medium may be volatile or non-volatile. The storage medium may be an internal storage unit of the server described in the foregoing embodiment, such as a hard disk or memory of the server. The storage medium may also be an external storage device of the server, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc., equipped on the server.

[0121] Furthermore, the storage medium may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function, etc.; the data storage area may store data created according to the use of the blockchain node, etc.

[0122] The blockchain referred to in this application is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.

[0123] It should be understood that the terms used in this application specification are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in this application specification and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0124] It should also be understood that the term "and / or" used in the specification of this application and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, including these combinations. It should be noted that, in this article, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "including a..." does not exclude the presence of other identical elements in the process, method, article or system including the element.

[0125] The serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments. The above description is only a specific implementation mode of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A data point management method, characterized in that: include: Acquire the tracking demand information that has passed the review, and push the tracking demand information to the developer, wherein the attribute information of the tracking field in the tracking demand information is selected by the tracking operator through the tracking demand page displayed on the tracking management client; Obtaining the target tracking code written by the developer based on the tracking requirement information, and controlling the test client containing the target tracking code to execute the test case associated with the tracking requirement information; Acquire multiple tracking data reported by the test client, where the multiple tracking data are reported by the test client based on the target tracking code during execution of the test case; The target burying point code is verified according to the multiple burying point data and the burying point requirement information, and if the target burying point code passes the verification, the target burying point code is stored.

2. The data point management method according to claim 1 is characterized in that: The verifying the target burying point code according to the plurality of burying point data and the burying point requirement information includes: Comparing the burying point field name in the burying point demand information with the burying point field names in the multiple burying point data; Comparing the attribute information of the burying point field in the burying point demand information with the attribute information of the burying point field in the plurality of burying point data; Determine the null value rate of the buried point field according to the multiple buried point data; In the case where the null value rate is less than or equal to the preset null value rate, the name of the burying point field in the burying point requirement information is the same as the name of the burying point field in the multiple burying point data, and the attribute information of the burying point field in the burying point requirement information is the same as the attribute information of the burying point field in the multiple burying point data, it is determined that the target burying point code passes the verification; When the null value rate is greater than the preset null value rate, the name of the burying point field in the burying point requirement information is different from the name of the burying point field in at least one of the burying point data, and / or the attribute information of the burying point field in the burying point requirement information is different from the attribute information of the burying point field in at least one of the burying point data, it is determined that the target burying point code has failed the verification.

3. The data point management method according to claim 1 is characterized in that: The attribute information of the tracking point field includes extended field information, and the extended field information is selected by the tracking point operator from an extended field database through the tracking point demand page.

4. The data point management method according to claim 3 is characterized in that: The method further comprises: Obtaining an extension field adding request sent by the embedding point management client, where the extension field information in the extension field adding request is input or selected by the embedding point administrator through a field adding page displayed by the embedding point management client; The extended field information in the extended field adding request is stored in the extended field database.

5. The data embedding management method according to claim 1, characterized in that: After storing the target embedding code, the method further includes: Acquire burying point comparison information and / or field null value rate at a first interval, wherein the burying point comparison information is used to indicate whether the burying point data of the same burying point field reported by clients of different platforms are consistent, and the burying point comparison information and the field null value rate are determined based on the burying point data reported by the client containing the target burying point code in the production environment; When the burial point comparison information indicates that the burial point data reported by clients of different platforms for the same burial point field are inconsistent and / or the field null value rate is greater than a preset null value rate threshold, output burial point abnormality prompt information.

6. The data point management method according to any one of claims 1 to 5, characterized in that: After storing the target embedding code, the method further includes: Acquire the value of a preset key indicator and / or the value change information of the preset key indicator at a second interval, wherein the value of the preset key indicator and the value change information of the preset key indicator are determined based on the tracking data reported by the client containing the target tracking code in the production environment; When the value of the preset key indicator is greater than a preset threshold and / or the value change information of the preset key indicator meets the preset change condition, indicator abnormality prompt information is output.

7. The data point management method according to claim 6, characterized in that: The value change information of the preset key indicator includes at least one of the value decrease amount, value increase amount, value decrease ratio, value increase ratio and number of consecutive decrease days of the preset key indicator; The value change information of the preset key indicator satisfies the preset change conditions, including at least one of the following: the decrease in the value of the preset key indicator is greater than the preset decrease, the increase in the value of the preset key indicator is greater than the preset increase, the decrease ratio of the value of the preset key indicator is greater than the first preset ratio, the increase ratio of the value of the preset key indicator is greater than the second preset ratio, and the consecutive decrease days of the preset key indicator is greater than the preset number of days.

8. A data point management device, characterized in that: The data embedding point management device comprises: An acquisition module is used to acquire the approved tracking demand information and push the tracking demand information to the developer. The attribute information of the tracking field in the tracking demand information is selected by the tracking operator through the tracking demand page displayed by the tracking management client. The acquisition module is also used to acquire the target tracking code written by the developer based on the tracking requirement information; A control module, used to control the test client containing the target tracking code to execute the test case associated with the tracking requirement information; The acquisition module is further used to acquire a plurality of tracking point data reported by the test client, wherein the plurality of tracking point data is reported by the test client based on the target tracking point code during the execution of the test case; A verification module is used to verify the target burying point code according to the multiple burying point data and the burying point requirement information, and store the target burying point code if the target burying point code passes the verification.

9. A server, characterized in that: The server includes a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, the data burial point management method as described in any one of claims 1 to 7 is implemented.

10. A storage medium for computer-readable storage, characterized in that: The storage medium stores a computer program, wherein when the computer program is executed by a processor, the data burial point management method as described in any one of claims 1 to 7 is implemented.

Images