Experiment burying point updating method and device

Abstract

The invention discloses an experimental burying point updating method and device, and relates to the technical field of computers. A specific embodiment of the experiment burying point updating method comprises the following steps: in response to a received product experiment request, determining a test entry file associated with the product experiment request, and generating test burying point data according to a test burying point logic corresponding to the test entry file; in response to a received statistical analysis request, performing statistical analysis on the test buried point data, and replacing the test entry file with the formal entry file under the condition that a statistical result meets an online condition; and in response to the received product online request, processing the product online request according to the service logic corresponding to the test entry file, and generating formal burying point data according to the formal burying point logic corresponding to the formal entry file. According to the embodiment, burying point updating can be achieved by replacing the entry file, burying point modification and repackaging and online are not needed, the burying point updating efficiency can be improved, and manpower and material resources are saved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and apparatus for updating experimental data points. Background Technology

[0002] To test the effectiveness of new product features and gather user feedback, developers typically divide business code into multiple groups. For example, they might divide the business code into an experimental group with new code and a control group with existing code. Then, they set up corresponding tracking logic for each group, generating tracking data such as page component interaction counts, method execution counts, and execution results. After the new business code passes testing based on the tracking data, the existing code is replaced with the new code, and the testing tracking logic is modified to match the logic used in the final product.

[0003] In the process of realizing this invention, the inventors discovered that the prior art has at least the following problems:

[0004] During code testing and updates, developers need to frequently modify the tracking logic, which consumes a lot of manpower and resources, is prone to introducing code vulnerabilities, and results in low tracking update efficiency. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a method and apparatus for updating experimental data points, which can improve the efficiency of data point updates and product testing efficiency, and save manpower and material costs.

[0006] To achieve the above objectives, according to a first aspect of the present invention, a method for updating experimental data points is provided, comprising:

[0007] In response to receiving a product experiment request, determine the test entry file associated with the product experiment request, and generate corresponding test data according to the test data entry logic corresponding to the test entry file;

[0008] In response to receiving a statistical analysis request, statistical analysis is performed on the test data. If the statistical results of the test data meet the pre-set launch conditions, the test entry file is replaced with a pre-set official entry file.

[0009] In response to receiving a request from the product line, the request is processed according to the business logic corresponding to the test entry file, and the corresponding formal tracking data is generated according to the formal tracking logic corresponding to the formal entry file.

[0010] Optionally, multiple test entry files are pre-set, and different test entry files are stored on different servers; determining the test entry file associated with the product experiment request includes:

[0011] Based on the pre-configured Nginx configuration information, a corresponding target test entry file is determined from the multiple test entry files. The target test entry file is then used as the test entry file associated with the product experiment request, and the product experiment request is forwarded to the server where the target test entry file is located.

[0012] Optionally, the server where the target test entry file is located is designated as the target server; replacing the test entry file with a pre-configured official entry file includes:

[0013] From the Nginx configuration information, determine the target configuration information corresponding to the target test entry file;

[0014] Based on the official entry file, modify the target configuration information. The modified target configuration information is used to forward the product line requests to the target server.

[0015] Optionally, based on the test tracking logic corresponding to the test entry file, corresponding test tracking data is generated, including:

[0016] Based on the pre-set association relationships, determine the test tracking logic associated with the test entry file;

[0017] Based on the aforementioned test point tracking logic, generate the corresponding initial tracking data;

[0018] Determine the tagging information corresponding to the test entry file;

[0019] According to the marking information, the initial tracking data is marked, and the marked initial tracking data is used as the test tracking data corresponding to the test entry file.

[0020] Optionally, determining the tagging information corresponding to the test entry file includes: obtaining global variables from the test entry file and using the obtained global variables as the tagging information of the test entry file;

[0021] According to the marking information, the initial tracking data is marked, including: concatenating the global variable with the initial tracking data, and using the concatenation result of the global variable and the initial tracking data as the test tracking data corresponding to the test entry file.

[0022] Optionally, before generating the corresponding test tracking data based on the test tracking logic corresponding to the test entry file, the method further includes:

[0023] storing the test entrance file to a preset content distribution network.

[0024] storing the test entrance file to a preset server.

[0025] Optionally, before storing the test entrance file and the resource file required by the test entrance file to the preset content distribution network, the method further comprises: generating a hash value of the test entrance file and the resource file according to a preset hash algorithm; and renaming the test entrance file and the resource file according to the hash value.

[0026] storing the test entrance file and the resource file to the content distribution network after renaming.

[0027] According to a second aspect of the embodiment of the present application, an experimental burying point updating device is provided, comprising:

[0028] a generating module configured to, in response to receiving a product experiment request, determine a test entrance file associated with the product experiment request, and generate corresponding test burying point data according to test burying point logic corresponding to the test entrance file.

[0029] a replacing module configured to, in response to receiving a statistical analysis request, perform statistical analysis on the test burying point data, and replace the test entrance file with a preset formal entrance file in a case where a statistical result of the test burying point data meets a preset online condition.

[0030] a processing module configured to, in response to receiving a product online request, process the formal business request according to business logic corresponding to the test entrance file, and generate corresponding formal burying point data according to formal burying point logic corresponding to the formal entrance file.

[0031] Optionally, a plurality of test entrance files are preset, and different test entrance files are stored in different servers; determining the test entrance file associated with the product experiment request comprises:

[0032] determining, according to preset Nginx configuration information, a target test entrance file corresponding to the plurality of test entrance files, taking the target test entrance file as the test entrance file associated with the product experiment request, and forwarding the product experiment request to a server where the target test entrance file is located.

[0033] Optionally, the server where the target test entry file is located is designated as the target server; replacing the test entry file with a pre-configured official entry file includes:

[0034] From the Nginx configuration information, determine the target configuration information corresponding to the target test entry file;

[0035] Based on the official entry file, modify the target configuration information. The modified target configuration information is used to forward the product line requests to the target server.

[0036] Optionally, based on the test tracking logic corresponding to the test entry file, corresponding test tracking data is generated, including:

[0037] Based on the pre-set association relationships, determine the test tracking logic associated with the test entry file;

[0038] Based on the aforementioned test point tracking logic, generate the corresponding initial tracking data;

[0039] Determine the tagging information corresponding to the test entry file;

[0040] According to the marking information, the initial tracking data is marked, and the marked initial tracking data is used as the test tracking data corresponding to the test entry file.

[0041] Optionally, determining the tagging information corresponding to the test entry file includes: obtaining global variables from the test entry file and using the obtained global variables as the tagging information of the test entry file;

[0042] According to the marking information, the initial tracking data is marked, including: concatenating the global variable with the initial tracking data, and using the concatenation result of the global variable and the initial tracking data as the test tracking data corresponding to the test entry file.

[0043] Optionally, the device further includes:

[0044] The first storage module is used to store the test tracking file corresponding to the test tracking logic and the resource files required by the test entry file to a pre-set content distribution network;

[0045] The second storage module is used to store the test entry file to a pre-configured server.

[0046] Optionally, the device further includes: a hashing module, used to generate hash values ​​for the test data entry file and the resource file according to a pre-set hashing algorithm; and a renaming module, used to rename the test data entry file and the resource file according to the hash values.

[0047] Storing the test tracking file corresponding to the test tracking logic and the resource files required for the test entry file to a pre-set content distribution network includes: storing the renamed test tracking file and resource files to the content distribution network.

[0048] According to a third aspect of the present invention, an electronic device is provided, comprising:

[0049] One or more processors;

[0050] Storage device for storing one or more programs.

[0051] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

[0052] According to a fourth aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the methods described in any of the above embodiments.

[0053] One embodiment of the above invention has the following advantages or beneficial effects: Based on the entry file, different tracking logics are distinguished, and tracking updates can be achieved simply by replacing the entry file, without modifying the tracking logic or repackaging and deploying. This improves the efficiency of experimental tracking updates, saves manpower and resources, and ensures system stability and high availability. According to the tagging information in the test entry file, tracking data is tagged, enabling flexible and efficient differentiation of tracking data corresponding to different test entry files, thus improving tracking update efficiency. Obtaining global variables from the test entry file, using these global variables as tagging information, and concatenating the tagging information with the tracking data further improves tracking update efficiency. The system offers greater flexibility and efficiency, reducing R&D and maintenance costs. Storing test data entry files and resource files on a CDN while storing test entry files on a server improves the efficiency of file retrieval, optimizes storage space allocation, and saves system resources. Renaming test data entry files and resource files before storing them on the CDN prevents them from being cached in the browser, ensuring accurate file retrieval. Forwarding product experiment requests to the corresponding server based on pre-configured Nginx parameters enhances traffic allocation flexibility, meets diverse product experiment needs, and improves the efficiency and accuracy of product experiments.

[0054] The further effects of the above-described non-conventional optional mode will be described in the following in conjunction with the specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0055] The accompanying drawings are included to provide a further understanding of the application, and are incorporated in and constitute a part of this specification, illustrate embodiments of the application, and together with the description serve to explain the principles of the application. In the drawings:

[0056] Figure 1 is a schematic diagram of the main flow of the updating method of the experimental burying point according to an embodiment of the application;

[0057] Figure 2 is a schematic diagram of the flow distribution according to a reference embodiment of the application;

[0058] Figure 3 is a schematic diagram of the storage device distribution according to a reference embodiment of the application;

[0059] Figure 4 is a schematic diagram of the main flow of the updating method of the experimental burying point according to a reference embodiment of the application;

[0060] Figure 5 is a schematic diagram of the main flow of the updating method of the experimental burying point according to another reference embodiment of the application;

[0061] Figure 6 is a schematic diagram of the main flow of the updating method of the experimental burying point according to yet another reference embodiment of the application;

[0062] Figure 7 is a schematic diagram of the main modules of the updating device of the experimental burying point according to an embodiment of the application;

[0063] Figure 8 is an exemplary system architecture diagram in which embodiments of the application can be applied;

[0064] Figure 9 is a structural schematic diagram of a computer system of a terminal device or a server suitable for implementing embodiments of the application. DETAILED DESCRIPTION

[0065] The exemplary embodiments of the present application will be described hereinafter with reference to the accompanying drawings, in which various specific details are given to provide a thorough understanding of the present application, and the exemplary embodiments should not be construed as limiting the present application. It will be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described or shown herein, embody the principles of the application and, thus, within the scope of the application. To avoid needless obscurity in the following description, well-known functions or constructions are not described in detail.

[0066] It should be noted that the collection, use, storage, sharing and transfer of user personal information involved in the technical solution of the present invention all comply with the provisions of relevant laws and regulations, and require notification to users and obtaining their consent or authorization. When applicable, user personal information is subjected to de-identification and / or anonymization and / or encryption technical processing.

[0067] To test the effectiveness of new product features and gather user feedback, developers typically divide business code into multiple groups. For example, in A / B testing, the business code is divided into an experimental group (new business code) and a control group (existing business code). Then, corresponding event tracking logic is set up for each group. Traffic is allocated to these groups, and event tracking data generated by the logic is obtained. This data includes page component interaction counts, method execution counts, and method execution results. After the new business code passes testing based on the event tracking data, the existing business code is modified to reflect the new code, and the testing event tracking logic is then modified for official testing.

[0068] During code testing and updates, developers need to frequently modify the tracking logic, which consumes a lot of manpower and resources, easily introduces code vulnerabilities, leads to low tracking update efficiency, reduces the stability and high availability of business systems, and increases development and maintenance costs.

[0069] In view of this, according to a first aspect of the present invention, a method for updating experimental data points is provided.

[0070] Figure 1 This is a schematic diagram illustrating the main flow of the experimental data point update method according to an embodiment of the present invention. Figure 1 As shown, the method for updating experimental data points according to an embodiment of the present invention mainly includes the following steps S101 to S103.

[0071] Step S101: In response to receiving a product experiment request, determine the test entry file associated with the product experiment request, and generate corresponding test tracking data according to the test tracking logic corresponding to the test entry file.

[0072] A product experiment request is a request used to conduct comparative experiments on a product before it goes live (such as AB testing). A product experiment request can be a request specifically for product experiments, or it can be a request received and forwarded by a business system in the product's online operating environment.

[0073] Upon receiving a product experiment request, the execution entity of this embodiment assigns the product experiment request to the corresponding test entry file. A test entry file is an entry point for accessing a page. Each test entry file is associated with a piece of business logic, which processes the product experiment requests assigned to the corresponding test entry file and displays the processing results of the product experiment requests in the form of a page. For example, according to the storage order of the test entry files, received product experiment requests are sequentially assigned to the corresponding test entry files, and the product experiment requests are processed according to the business logic corresponding to the test entry file; or, for another example, product experiment requests received at different times are assigned to different test entry files, and the product experiment requests are processed according to the business logic corresponding to the test entry file.

[0074] Each test entry file has corresponding test tracking logic. This logic generates tracking data related to the product experiment request processing. The tracking data is used to evaluate the experimental effectiveness of the test entry file. This data includes: page component interaction counts (e.g., the number of times page links are clicked, page information is viewed, and text boxes are entered), method execution counts (e.g., the number of product queries, order generation, and inventory updates), and method execution results (e.g., whether execution was successful, method execution time, and memory and other resource consumption). For example, after detecting a page link click, the page component interaction count is incremented by 1; after detecting a product query call, the method execution count is incremented by 1.

[0075] It should be noted that the tracking data corresponding to different test entry files have different tagging information. Based on the tagging information, tracking data belonging to different test entry files can be distinguished. For example, tracking data belonging to the same test entry file can be stored in the same tracking dataset, and the tracking datasets corresponding to each test entry file can be distinguished by different tracking dataset names.

[0076] After receiving a product experiment request, a test entry file is selected, and the business test request is processed according to the corresponding business logic. According to the corresponding tracking logic, tracking data is generated, which can provide detailed data support for evaluating the experimental effect of the test entry file. Using tag information to distinguish the tracking data can improve the efficiency and accuracy of tracking classification and avoid confusing tracking data belonging to different test entry files.

[0077] Step S102: In response to receiving a statistical analysis request, perform statistical analysis on the test data. If the statistical results of the test data meet the pre-set launch conditions, replace the test entry file with the pre-set official entry file.

[0078] After receiving the statistical analysis request, the execution subject of the embodiment of the application obtains the test entry file corresponding to the test entry file. The test entry file is compared with the pre-set online condition, for example, the page component interaction frequency is compared with the pre-set interaction frequency threshold, the method execution frequency is compared with the pre-set execution frequency threshold, the success rate of method execution is determined, the average execution time of the method is compared with the pre-set execution time threshold, and the memory resources and CPU resources consumed during the execution of the method are compared with the pre-set resource consumption threshold. In the case where the page component interaction frequency is greater than the interaction frequency threshold, the method execution frequency is greater than the execution frequency threshold, the success rate of method execution is greater than the pre-set success rate threshold, the average execution time of the method is less than the execution time threshold, and the resource consumption during the execution of the method is less than the resource consumption threshold, it is indicated that the user interacts with the front-end page corresponding to the test entry file more frequently, and the efficiency of executing the business method included in the test entry file is higher, the resource consumption is lower, and it is more stable. Therefore, it is determined that the statistical result of the test entry file meets the online condition.

[0079] In the case where there are multiple test entry files, the test entry data corresponding to the multiple test entry files is compared. Specifically, the test entry data of the new entry file referring to the new business logic is compared with the test entry data of the original entry file referring to the original business logic. In the case where the page component interaction frequency of the new entry file is greater than that of the original entry file, the method execution frequency of the new entry file is greater than that of the original entry file, the success rate of the method execution of the new entry file is greater than that of the original entry file, and the method execution time of the new entry file is less than that of the original entry file, it is indicated that the new entry file is more popular with users and can better meet the needs of users and give users a good experience. Therefore, it is determined that the statistical result of the test entry data corresponding to the new entry file meets the online condition.

[0080] In the case where the statistical result meets the online condition, the pre-set formal entry file is used to replace the test entry file meeting the online condition, wherein the formal entry file is an entry file used to process requests on the product line, i.e., the formal entry file is used for actual production of the business system. It should be noted that the difference between the formal entry file and the test entry file is only that the global variables included in the formal entry file are different from the global variables included in the test entry file. After replacement, the business logic corresponding to the test entry file meeting the online condition is used for actual production of the business system. For example, the formal entry file is copied to the storage path of the test entry file, and then the test entry file under the storage path is deleted, i.e., the burying point update is completed. Thereafter, the requests on the product line are processed according to the business logic corresponding to the test entry file, and the formal burying point data is generated according to the formal burying point logic corresponding to the formal entry file, so as to avoid confusion with the test burying point data.

[0081] When the entry file is replaced, the formal entry file corresponding formal burying point logic and the test entry file corresponding test burying point logic are also replaced. It should be noted that in order to evaluate the business execution of the formal entry file, the formal burying point logic corresponding to the formal entry file is set in advance, and the burying point data generated by the formal burying point logic also has corresponding marking information. The burying point logic corresponding to the entry file is decoupled from the business logic corresponding to the entry file, for example, the burying point logic corresponding to the entry file is determined by a configuration file, the burying point logics corresponding to different entry files are stored in different positions, and the burying point logic is replaced by replacing the entry file.

[0082] By replacing the entry file, the burying point updating task can be quickly and accurately completed, without the need to repack and publish, or modify the original entry file or the burying point logic used in formal production, so that manpower and resources can be saved, the code updating efficiency can be improved, code vulnerabilities can be avoided, and the research and development cost and maintenance cost can be reduced.

[0083] In step S103, in response to receiving the product line request, the product line request is processed according to the business logic corresponding to the test entry file, and the corresponding formal burying point data is generated according to the formal burying point logic corresponding to the formal entry file.

[0084] After receiving the product line request, the business logic corresponding to the test entry file is called. The product line request is processed according to the business logic corresponding to the test entry file.

[0085] The formal burying point logic corresponding to the formal entry file is called, that is, the burying point logic in the formal production environment is different from the burying point logic in the test environment, and the burying point logic in the formal production environment needs to be kept unchanged when updating the code package. The corresponding formal burying point data is generated according to the formal burying point logic.

[0086] After the code is updated, the product line request is processed using the business logic corresponding to the test entry file that has passed the product experiment, which can improve the processing efficiency and effect of the product line request, and the corresponding formal burying point data is generated using the formal burying point logic corresponding to the formal entry file, which can accurately generate burying point data while optimizing the business request processing, and ensure the stability and high availability of the business system.

[0087] According to a possible embodiment of the present invention, when generating corresponding test tracking data based on the test tracking logic corresponding to the test entry file, a pre-set association relationship is first queried. This association relationship represents the relationship between the test entry file and the test tracking logic. The test tracking file is a code file with tracking logic used to generate the tracking data. Based on the association relationship between the test entry file and the test tracking logic, the test tracking file associated with the test entry file is determined. For example, a first filename of the test entry file is determined in the association relationship, a second filename corresponding to the first filename is queried, and the test tracking file with the second filename is selected as the test tracking file corresponding to the test entry file. This test tracking file has the corresponding test tracking logic.

[0088] Then, based on the test tracking logic included in the test tracking file, the corresponding initial tracking data is generated. The initial tracking data includes: the number of page component interactions, the number of method executions, the method execution success rate, and the method execution duration, among other data.

[0089] Determine the tagging information corresponding to the test entry file. Tagging information is identifiable and unique; different test entry files have different tagging information. For example, the tagging information for test entry files can be pre-stored in a configuration file, associating the tagging information with the filename of the test entry file. After obtaining the initial data tracking data, the associated tagging information is searched in the configuration file based on the filename of the test entry file. For example, a pre-set configuration file might include "{'test1':'A1';'test2':'A2'}", where the tagging information for the test entry file named "test1" is "A1", and the tagging information for the test entry file named "test2" is "A2".

[0090] After obtaining the tagging information, the initial event tracking data is tagged using this information. For example, the tagging information can be used as a prefix or suffix to the initial event tracking data. Alternatively, data structures such as linked lists, arrays, or hash tables can be used to encapsulate the tagging information together with the initial event tracking data. The tagged initial event tracking data is then used as the test event tracking data corresponding to the test entry file. The tagging information in the test event tracking data allows for the determination of the test entry file to which the test event tracking data belongs. This facilitates the differentiation of test event tracking data from different test entry files, improving the accuracy and efficiency of statistical analysis of the test event tracking data.

[0091] According to another possible embodiment of the present invention, when determining the tagging information corresponding to the test entry file, global variables are obtained from the test entry file, and the obtained global variables are used as the tagging information of the test entry file. Specifically, the test entry file can be an HTML (HyperText Markup Language) file, in which global variables are declared in advance. The global variables are different for different test entry files, and the global variables have identifiability and uniqueness.

[0092] The initial tracking data includes a data name and a data value. When marking the initial tracking data according to the marking information, the global variable is concatenated with the data name of the initial tracking data, or the global variable is concatenated with the data value of the initial tracking data. The concatenation result of the global variable and the initial tracking data is used as the test tracking data corresponding to the test entry file.

[0093] For example, the test entry file named "frontPage1" is traversed to obtain the global variable declared in the test entry file, resulting in "global = 'B1_'". Based on the test tracking logic corresponding to the test entry file, the test tracking data is obtained as "testData = C1", where "testData" is the data name of the test tracking data, and "C1" is the data value of the test tracking data. Specifically, "C1" is a hash table containing multiple test tracking data. The global variable is used as a prefix to the data name of the test tracking data, that is, the global variable is concatenated with the data name of the test tracking data to obtain a new data name of the test tracking data as "B1_testData". This concatenated initial tracking data is used as the test tracking data corresponding to the test entry file "frontPage1", specifically, this test tracking data is "B1_testData = C1". By identifying the tag information included in the data name of this test tracking data, the test entry file to which this test tracking data belongs can be determined.

[0094] Global variables read from the test entry file are used as identification information. By concatenating the global variables with the data names or data values ​​of the initial tracking data, the initial tracking data can be quickly and flexibly converted into test tracking data with tagging information, increasing the identification of the test tracking data and facilitating the improvement of the efficiency and accuracy of statistical analysis of the test tracking data.

[0095] According to another possible embodiment of the present invention, before generating the corresponding test tracking data based on the test tracking logic corresponding to the test entry file, the method further includes: storing the test tracking file corresponding to the test tracking logic and the resource files required by the test entry file to a pre-set content delivery network. The test tracking file includes a JS (JavaScript) file, and the resource files required by the test entry file include CSS (Cascading Style Sheets) files, images, documents, etc. A Content Delivery Network (CDN) is an intelligent virtual network built on the existing Internet infrastructure, consisting of node servers placed throughout the network. The CDN can redirect user-sent business requests to the nearest node server in real time based on comprehensive information such as network traffic, the connection and load status of each node server, and the distance and response time between the node server and the user, thereby making the transmission of content related to the business request faster and more stable.

[0096] Preferably, incremental storage is used to store the test event tracking files and the resource files required for the test entry files on the content delivery network (CDN). Specifically, the CDN stores different versions of the test event tracking files and resource files. The corresponding test event tracking files and resource files are removed from the CDN only when the storage time of the test event tracking files and resource files is greater than or equal to a pre-set storage time threshold, or when a content cleanup request is received. Therefore, different test entry files can call different test event tracking files, execute different test event tracking logic, and generate different test event tracking data. Different test entry files can also call different resource files to generate front-end pages with different styles and layouts, providing users with different interactive experiences.

[0097] For example, the official entry file executes the corresponding official tracking logic through the official tracking file D1 in the CDN, and generates the front-end page through the official resource file E1 in the CDN. Developers modify the tracking logic included in the official tracking file D1 to obtain the test tracking file D2, modify the code in the official resource file E1 to obtain the test resource file E2, and modify the official entry file to obtain the test entry file. Then, the test entry file executes new test tracking logic through the test tracking file D2 in the CDN, and generates a new front-end page through the test resource file E2 in the CDN. The tracking data generated by the official tracking file D1 is used as the official tracking data (i.e., the control group), and the tracking data generated by the test tracking file D2 is used as the test tracking data (i.e., the experimental group). The tracking data of different groups are compared, and if the statistical results of the test tracking data meet the deployment conditions, it is determined that the test entry file can replace the official entry file and be deployed.

[0098] Store the test entry file on a pre-configured server. The test entry file includes an HTML file. For example, the test entry file can be stored on a local server. Storing the test entry file and the business logic that processes requests on the same server can also improve the efficiency of page file retrieval and page display.

[0099] According to another possible embodiment of the present invention, before storing the parameter tracking file and resource files required for the test entry file corresponding to the test tracking logic to a pre-set content distribution network, the method further includes: generating hash values ​​for the test tracking file and resource files according to a pre-set hash algorithm. Specifically, file information such as the generation time, file name, and file size of the test tracking file and resource files are obtained, or a piece of random information is generated. The obtained file information or the generated random information is then converted into hash values ​​using a hash algorithm.

[0100] Then, based on the hash value, the test tracking file and the resource file are renamed. For example, the hash value is added as a name prefix before the filename of the test tracking file and the filename of the resource file; or, for another example, the hash value is added as a name suffix after the filename of the test tracking file and the filename of the resource file.

[0101] After renaming the resource files required by the test burying point file and the test entry file, the renamed test burying point file and the resource files required by the test entry file are stored in the pre-set content distribution network. The file name of the test burying point file and the file name of the resource file stored in the content distribution network have hash information, avoiding the generation of cache of the test burying point file and the resource file, so that each time the test burying point file and the resource file are called, the actual file is obtained instead of the cache in the browser.

[0102] Before being stored in the CDN, the test burying point file and the resource file are renamed, which can avoid the cache of the resource file and the test burying point file in the browser, and ensure the accuracy of file acquisition.

[0103] According to a reference embodiment of the present application, a plurality of test entry files are pre-set, and different test entry files are stored in different servers. When the test entry file associated with the product experiment request is determined, the target test entry file is determined from the plurality of test entry files according to the pre-set Nginx configuration information, the target test entry file is taken as the test entry file associated with the product experiment request, and the product experiment request is forwarded to the server where the target test entry file is located.

[0104] For example, the cumulative request allocation number of the plurality of test entry files is determined first. The Nginx configuration information includes a business request allocation parameter, that is, the number or proportion of product experiment requests that should be allocated to each test entry file. The business request allocation parameter included in the Nginx configuration information is compared with the cumulative request processing number, and according to the comparison result, the target test code package associated with the product experiment request is determined from the plurality of test entry files, and the business test request is sent to the server where the target test code package is located.

[0105] For example, the test entry file F1 has cumulatively processed 6 product experiment requests, the test entry file F2 has cumulatively processed 6 product experiment requests, and the test entry file F3 has cumulatively processed 5 product experiment requests. The pre-set business request allocation parameter is queried to obtain the request allocation proportion of the three test entry files, that is, the number of product experiment requests allocated to the three test entry files should be equal, so that after receiving a new product experiment request, the test entry file F3 is taken as the target test entry file. Since the test entry file F1 is stored in the server G1, the test entry file F2 is stored in the server G2, and the test entry file F3 is stored in the server G3, the newly received product experiment request is forwarded to the server G3.

[0106] By allocating product experiment requests to the corresponding servers based on pre-configured Nginx parameters, the flexibility of traffic allocation can be improved, meeting various product experiment needs and enhancing the efficiency and accuracy of product experiments.

[0107] According to another possible embodiment of the present invention, the server where the target test entry file is located is designated as the target server. When replacing the test entry file with a pre-configured official entry file, the target configuration information corresponding to the target test entry file is first determined from the Nginx configuration information. Then, the target configuration information is modified according to the official entry file. Specifically, the modified target configuration information is used to forward requests from the product line to the target server. The business logic corresponding to the target test entry file processes the requests from the product line, and the official tracking logic corresponding to the official entry file generates the corresponding official tracking data.

[0108] Specifically, the pre-configured Nginx configuration information includes "{'html':'testH1';'js':'js001'}", which indicates that the target test entry file is named "testH1" and the corresponding test tracking file is named "js001". Based on the official entry file, this configuration information is modified to "{'html':'L1';'js':'js100'}", indicating that the official entry file is named "L1" and the corresponding official tracking file is named "js100". After modifying the configuration information, the business logic corresponding to the target test entry file is used to handle online product requests, while the official tracking logic corresponding to the official entry file is used to generate the corresponding official tracking data, avoiding confusion with the test tracking data.

[0109] Figure 2 This is a schematic diagram of traffic allocation according to a possible embodiment of the present invention. Exemplarily, as shown... Figure 2As shown, in the production server cluster, multiple production servers are set up, including Production Server 1, Production Server 2, and Production Server 3. Similarly, in the test server cluster, multiple test servers are set up, including Test Server 1, Test Server 2, and Test Server 3. The production servers receive online product requests. They can process these requests or forward them as product experiment requests to the test servers to monitor the processing of new business logic deployed on the test servers. Specifically, the production servers forward received online product requests as product experiment requests to the test servers according to the Nginx+Lua routing rules. Nginx is a reverse proxy service; the production servers send product experiment requests to Nginx, which contains scripts written in Lua. These Lua scripts include the routing rules for product experiment requests, and Nginx forwards these requests to the test servers according to these rules. For example, with three test servers, the routing rule is: 10% of product experiment requests are forwarded to Test Server 1, 10% to Test Server 2, and 10% to Test Server 3, ensuring that all three test servers receive the same number of product experiment requests.

[0110] Figure 3 This is a schematic diagram of storage device allocation according to a reference embodiment of the present invention. Exemplarily, as shown... Figure 3 As shown, a user sends a product online request to the production server. Upon receiving the request, the production server chooses to process it itself or forward it as a product experiment request to the test server. The test server, upon receiving the product experiment request, references test event files and resource files from the content delivery network (CDN). The CDN then transmits these files to the test server, which generates the front-end page corresponding to the product experiment request and displays it to the user. The configuration module configures traffic allocation, including the proportion of product experiment requests allocated to each test server relative to the total number of product experiment requests. The configuration module also sets the conditions for the statistical results of event data to go live, and configures the event logic for each entry file (e.g., production entry file and test entry file). Different production entry files are stored on different production servers, and different test entry files are stored on different test servers.

[0111] Figure 4 This is a schematic diagram illustrating the main flow of an experimental data tracking update method according to a possible embodiment of the present invention. Figure 4 As shown, the method for updating the experimental data points may include:

[0112] Step S401: In response to receiving a product experiment request, determine the cumulative number of requests to be processed for multiple pre-set alternative test entry files;

[0113] Step S402: Compare the cumulative number of requests processed with the Nginx configuration parameters, and determine the test entry file associated with the product experiment request from multiple candidate test entry files based on the comparison results;

[0114] Step S403: Generate the corresponding test tracking data according to the test tracking logic corresponding to the test entry file;

[0115] Step S404: In response to receiving the statistical analysis request, perform statistical analysis on the test data points and obtain the corresponding statistical results;

[0116] Step S405: Determine whether the statistical results meet the upper limit conditions. If yes, proceed to step S406; otherwise, proceed to step S404.

[0117] Step S406: Replace the test entry file with the pre-configured official entry file;

[0118] Step S407: In response to receiving a product online request, process the product online request according to the business logic corresponding to the test entry file;

[0119] Step S408: Generate the corresponding formal tracking data based on the formal tracking logic corresponding to the formal entry file.

[0120] The specific implementation details of the experimental data point update method of the present invention, which can be referred to in the above embodiment, have been described in detail in the above-described experimental data point update method, so the details will not be repeated here.

[0121] Figure 5 This is a schematic diagram of the main flow of an experimental data tracking update method according to another applicable embodiment of the present invention. Figure 5 As shown, the method for updating the experimental data points may include:

[0122] Step S501: In response to receiving a product experiment request, determine the test entry file associated with the product experiment request;

[0123] Step S502: Determine the test tracking logic associated with the test entry file based on the pre-set configuration information;

[0124] Step S503: Generate the corresponding initial data points according to the test data point logic;

[0125] Step S504: Obtain global variables from the test entry file and use the obtained global variables as the tagging information of the test entry file;

[0126] Step S505: Concatenate the global variables and the initial data points, and use the concatenation result as the test data points corresponding to the test entry file.

[0127] Step S506: In response to receiving the statistical analysis request, perform statistical analysis on the test data points and obtain the corresponding statistical results;

[0128] Step S507: Determine whether the statistical results meet the upper limit conditions. If yes, proceed to step S508; otherwise, proceed to step S506.

[0129] Step S508: Replace the test entry file with the pre-configured official entry file;

[0130] Step S509: In response to receiving a product online request, process the product online request according to the business logic corresponding to the test entry file;

[0131] Step S510: Generate the corresponding formal tracking data based on the formal tracking logic corresponding to the formal entry file.

[0132] The specific implementation details of the experimental data point update method of another applicable embodiment of the present invention have been described in detail in the above-described experimental data point update method, so the details will not be repeated here.

[0133] Figure 6 This is a schematic diagram of the main flow of an experimental data tracking update method according to another possible embodiment of the present invention. Figure 6 As shown, the method for updating the experimental data points may include:

[0134] Step S601: Store the test entry file to the target server;

[0135] Step S602: Store the test entry file corresponding to the test entry file and the resource files required by the test entry file in the content delivery network;

[0136] Step S603: In response to receiving the product experiment request, forward the product experiment request to the target server;

[0137] Step S604: Generate the corresponding initial data points based on the test data point logic included in the test data point file corresponding to the test entry file in the content delivery network.

[0138] Step S605: Obtain the tagging information from the test entry file;

[0139] Step S606: Concatenate the initial tracking data set and the tagging information into test tracking data;

[0140] Step S607: In response to receiving the statistical analysis request, perform statistical analysis on the test data points and obtain the corresponding statistical results;

[0141] Step S608: Determine whether the statistical results meet the upper limit conditions. If yes, proceed to step S609; otherwise, proceed to step S607.

[0142] Step S609: Replace the test entry file with the pre-configured official entry file;

[0143] Step S610: In response to receiving a product online request, process the product online request according to the business logic corresponding to the test entry file;

[0144] Step S611: Generate the corresponding formal tracking data based on the formal tracking logic corresponding to the formal entry file.

[0145] The specific implementation details of the experimental data point update method of another possible embodiment of the present invention have been described in detail in the above-described experimental data point update method, so the details will not be repeated here.

[0146] According to a second aspect of the present invention, an apparatus for updating experimental embedded points is provided.

[0147] Figure 7 This is a schematic diagram of the main modules of the experimental data point updating device according to an embodiment of the present invention, as shown below. Figure 7 As shown, the experimental embedding point updating device 700 mainly includes:

[0148] The generation module 701 is used to respond to receiving a product experiment request, determine the test entry file associated with the product experiment request, and generate corresponding test data according to the test data entry logic corresponding to the test entry file.

[0149] Replacement module 702 is used to respond to a received statistical analysis request, perform statistical analysis on the test data, and replace the test entry file with a pre-set official entry file if the statistical results of the test data meet the pre-set online conditions.

[0150] The processing module 703 is used to respond to a request received from the product line, process the formal business request according to the business logic corresponding to the test entry file, and generate corresponding formal tracking data according to the formal tracking logic corresponding to the formal entry file.

[0151] According to a possible embodiment of the present invention, multiple test entry files are pre-set, and different test entry files are stored on different servers; determining the test entry file associated with the product experiment request includes:

[0152] Based on the pre-configured Nginx configuration information, a corresponding target test entry file is determined from the multiple test entry files. The target test entry file is then used as the test entry file associated with the product experiment request, and the product experiment request is forwarded to the server where the target test entry file is located.

[0153] According to another possible embodiment of the present invention, the server where the target test entry file is located is designated as the target server; replacing the test entry file with a pre-set official entry file includes:

[0154] From the Nginx configuration information, determine the target configuration information corresponding to the target test entry file;

[0155] Based on the official entry file, modify the target configuration information. The modified target configuration information is used to forward the product line requests to the target server.

[0156] According to another possible embodiment of the present invention, based on the test tracking logic corresponding to the test entry file, corresponding test tracking data is generated, including:

[0157] Based on the pre-set association relationships, determine the test tracking logic associated with the test entry file;

[0158] Based on the aforementioned test point tracking logic, generate the corresponding initial tracking data;

[0159] Determine the tagging information corresponding to the test entry file;

[0160] According to the marking information, the initial tracking data is marked, and the marked initial tracking data is used as the test tracking data corresponding to the test entry file.

[0161] According to another possible embodiment of the present invention, determining the tagging information corresponding to the test entry file includes: obtaining global variables from the test entry file, and using the obtained global variables as the tagging information of the test entry file;

[0162] According to the marking information, the initial tracking data is marked, including: concatenating the global variable with the initial tracking data, and using the concatenation result of the global variable and the initial tracking data as the test tracking data corresponding to the test entry file.

[0163] According to another embodiment of the present application, the experimental point-in-time update device 700 further comprises:

[0164] The first storage module is configured to store the test point-in-time file corresponding to the test point-in-time logic and the resource file required by the test entry file to a pre-set content distribution network.

[0165] The second storage module is configured to store the test entry file to a pre-set server.

[0166] According to an embodiment of the present application, the experimental point-in-time update device 700 further comprises a hash module configured to generate hash values of the test point-in-time file and the resource file according to a pre-set hash algorithm; and a renaming module configured to rename the test point-in-time file and the resource file according to the hash values.

[0167] The first storage module is configured to store the test point-in-time file corresponding to the test point-in-time logic and the resource file required by the test entry file to a pre-set content distribution network.

[0168] It should be noted that the specific implementation of the experimental point-in-time update device in the embodiments of the present application has been described in detail in the experimental point-in-time update method described above, and therefore the repeated content will not be described here.

[0169] According to the technical scheme of the embodiments of the present application, different point-in-time logics are distinguished based on entry files, and point-in-time update can be realized by replacing the entry file, without the need to modify the point-in-time logic, repackage and go online, which can improve the efficiency of experimental point-in-time update, save manpower and resources, and ensure system stability and high availability; the point-in-time data is marked according to the marking information of the test entry file, which can flexibly and efficiently distinguish the point-in-time data corresponding to different test entry file code packages, improving the efficiency of point-in-time update; the global variable is obtained from the test entry file, the global variable is taken as the marking information, and the marking information is spliced with the point-in-time data, which can further improve the flexibility and efficiency of point-in-time update, and reduce the research and development cost and maintenance cost; the test point-in-time file and the resource file are stored to a CDN, and the test entry file is stored to a server, which can improve the search efficiency of various files, reasonably allocate storage space, and save system resources; the test point-in-time file and the resource file are renamed before being stored to the CDN, which can avoid the caching of the resource file and the test point-in-time file in the browser, and ensure the accuracy of file acquisition; the product experiment request is forwarded to the corresponding server according to the pre-set Nginx configuration parameter, which can improve the flexibility of traffic distribution, meet various product experiment demands, improve the efficiency and accuracy of product experiments.

[0170] According to a third aspect of the embodiments of the present application, an electronic device is provided, comprising: one or more processors; a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method according to the first aspect of the embodiments of the present application.

[0171] According to a fourth aspect of the embodiments of the present application, a computer readable medium is provided, having stored thereon a computer program, when the program is executed by a processor, the method according to the first aspect of the embodiments of the present application is implemented.

[0172] Figure 8 An exemplary system architecture 800 to which the experimental A / B testing update method or the experimental A / B testing update device according to the embodiments of the present application can be applied is shown.

[0173] As shown in Figure 8 The system architecture 800 can include terminal devices 801, 802, 803, a network 804 and a server 805. The network 804 is a medium for providing a communication link between the terminal devices 801, 802, 803 and the server 805. The network 804 can include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0174] A user can use the terminal devices 801, 802, 803 to interact with the server 805 through the network 804 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 801, 802, 803, such as product experiment applications, project update applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0175] The terminal devices 801, 802, 803 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers and desktop computers, etc.

[0176] The server 805 can be a server providing various services, for example, a background management server (only an example) providing support for an update request of an experiment burying point sent by the upstream terminal device 801, 802, 803. The background management server can determine a test entry file associated with a product experiment request in response to receiving the product experiment request, generate corresponding test burying point data according to test burying point logic corresponding to the test entry file, perform statistical analysis on the test burying point data in response to receiving a statistical analysis request, replace the test entry file with a pre-set formal entry file in a case where a statistical result of the test burying point data meets a pre-set online condition, process the product online request according to business logic corresponding to the test entry file in response to receiving a product online request, generate corresponding formal burying point data according to formal burying point logic corresponding to the formal entry file, and feed back an update situation of the experiment burying point (only an example) to the terminal device.

[0177] It should be noted that the experiment burying point update method provided by the embodiment of the present application is generally executed by the server 805, and accordingly, the experiment burying point update device is generally arranged in the server 805. The experiment burying point update method provided by the embodiment of the present application can also be executed by the terminal device 801, 802, 803, and accordingly, the experiment burying point update device can be arranged in the terminal device 801, 802, 803.

[0178] It should be understood that Figure 8 The number of terminal devices, networks and servers in the above-mentioned system is only illustrative. Any number of terminal devices, networks and servers can be provided according to the needs of implementation.

[0179] Reference will be made to Figure 9 which shows a structural schematic diagram of a computer system 900 suitable for implementing the terminal device of the embodiment of the present application. Figure 9 The terminal device shown is only an example and should not bring any limitation to the function and use range of the embodiment of the present application.

[0180] As shown in Figure 9 , the computer system 900 includes a central processing unit (CPU) 901 which can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 902 or programs loaded from a storage portion 908 into a random access memory (RAM) 903. Various programs and data required for the operation of the system 900 are also stored in the RAM 903. The CPU 901, the ROM 902 and the RAM 903 are connected to each other through a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0181] The following components are connected to the I / O interface 905: an input part 906 including a keyboard, a mouse, etc.; an output part 907 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage part 908 including a hard disk, etc.; and a communication part 909 including a network interface card such as a LAN card, a modem, etc. The communication part 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 910 as necessary, so that a computer program read out therefrom is installed in the storage part 908 as necessary.

[0182] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program in accordance with embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program comprising a computer program carried on a computer readable medium, the computer program containing program code for executing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network by the communication part 909, and / or installed from the removable medium 911. When the computer program is executed by the central processing unit (CPU) 901, the above-described functions defined in the system of the embodiments of the present disclosure are executed.

[0183] It should be noted that the computer-readable medium in the embodiments of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. More specific examples of the computer-readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the embodiments of the present application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In the embodiments of the present application, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, transmit, propagate or transport a program for use by or in conjunction with an instruction execution system, device or apparatus. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wireline, optical cable, RF, etc., or any suitable combination thereof.

[0184] The flowcharts and block diagrams in the drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module, a segment, or a portion of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks noted in succession can in fact be executed substantially concurrently or in the reverse order, depending on the functionality involved. It will also be noted that each block in the flowcharts or block diagrams and combinations of blocks in the flowcharts or block diagrams can be implemented by special-purpose hardware-based systems that perform the specified functions or operations, or combinations of special-purpose hardware and computer instructions.

[0185] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including a generation module, a replacement module, and a processing module. The names of these modules do not necessarily limit the module itself; for example, the generation module can also be described as a "module for generating test data points."

[0186] In another aspect, embodiments of the present invention also provide a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the device, the device implements the following method: in response to receiving a product experiment request, determining a test entry file associated with the product experiment request, and generating corresponding test tracking data according to the test tracking logic corresponding to the test entry file; in response to receiving a statistical analysis request, performing statistical analysis on the test tracking data, and replacing the test entry file with a pre-set formal entry file if the statistical results of the test tracking data meet pre-set online conditions; in response to receiving a product online request, processing the product online request according to the business logic corresponding to the test entry file, and generating corresponding formal tracking data according to the formal tracking logic corresponding to the formal entry file.

[0187] According to the technical solution of this invention, different tracking logics are distinguished based on the entry file. Tracking updates can be achieved by replacing the entry file without modifying the tracking logic or repackaging and deploying it online. This improves the efficiency of experimental tracking updates, saves manpower and resources, and ensures system stability and high availability. Tracking data is marked according to the marking information of the test entry file, enabling flexible and efficient differentiation of tracking data corresponding to different test entry files, thus improving tracking update efficiency. Global variables are obtained from the test entry file, and these global variables are used as marking information. The marking information is then concatenated with the tracking data, further enhancing the flexibility of tracking updates. This improves efficiency and reduces R&D and maintenance costs. Storing test data entry files and resource files on a CDN and test entry files on a server improves the efficiency of finding various files, allocates storage space reasonably, and saves system resources. Renaming test data entry files and resource files before storing them on the CDN avoids caching in the browser, ensuring accurate file retrieval. Forwarding product experiment requests to the corresponding server based on pre-set Nginx configuration parameters improves the flexibility of traffic allocation, meets various product experiment needs, and improves the efficiency and accuracy of product experiments.

[0188] The above detailed description does not limit the scope of the embodiments of the application. Various modifications, combinations, sub-combinations and alternatives can occur to one skilled in the art without departing from the spirit and scope of the embodiments of the application. Any modification, equivalent replacement or improvement made within the spirit and principle of the embodiments of the application should be included within the scope of the embodiments of the application.

Claims

1. A method for updating experimental data points, characterized in that, include: In response to receiving a product experiment request, determine the test entry file associated with the product experiment request, and generate corresponding test data according to the test data entry logic corresponding to the test entry file; In response to receiving a statistical analysis request, statistical analysis is performed on the test data. If the statistical results of the test data meet the pre-set launch conditions, the test entry file is replaced with a pre-set official entry file. In response to receiving a request from the product line, the request is processed according to the business logic corresponding to the test entry file, and the corresponding formal tracking data is generated according to the formal tracking logic corresponding to the formal entry file.

2. The method according to claim 1, characterized in that, Multiple test entry files are pre-configured, and different test entry files are stored on different servers; Determine the test entry file associated with the product experiment request, including: Based on the pre-configured Nginx configuration information, a corresponding target test entry file is determined from the multiple test entry files. The target test entry file is then used as the test entry file associated with the product experiment request, and the product experiment request is forwarded to the server where the target test entry file is located.

3. The method according to claim 2, characterized in that, The server containing the target test entry file is designated as the target server. Replace the test entry file with a pre-configured official entry file, including: From the Nginx configuration information, determine the target configuration information corresponding to the target test entry file; Based on the official entry file, modify the target configuration information. The modified target configuration information is used to forward the product line requests to the target server.

4. The method according to claim 1, characterized in that, Based on the test tracking logic corresponding to the test entry file, generate the corresponding test tracking data, including: Based on the pre-set association relationships, determine the test tracking logic associated with the test entry file; Based on the aforementioned test point tracking logic, generate the corresponding initial tracking data; Determine the tagging information corresponding to the test entry file; According to the marking information, the initial tracking data is marked, and the marked initial tracking data is used as the test tracking data corresponding to the test entry file.

5. The method according to claim 4, characterized in that, Determining the tagging information corresponding to the test entry file includes: obtaining global variables from the test entry file and using the obtained global variables as the tagging information of the test entry file; According to the marking information, the initial tracking data is marked, including: concatenating the global variable with the initial tracking data, and using the concatenation result of the global variable and the initial tracking data as the test tracking data corresponding to the test entry file.

6. The method according to claim 5, characterized in that, Before generating the corresponding test tracking data based on the test tracking logic corresponding to the test entry file, the method further includes: Store the test tracking file corresponding to the test tracking logic and the resource files required for the test entry file in a pre-set content distribution network; The test entry file is stored on a pre-configured server.

7. The method according to claim 6, characterized in that, Before storing the test tracking file corresponding to the test tracking logic and the resource file required for the test entry file to a pre-set content distribution network, the method further includes: generating hash values ​​for the test tracking file and the resource file according to a pre-set hash algorithm; and renaming the test tracking file and the resource file according to the hash values. Storing the test tracking file corresponding to the test tracking logic and the resource files required for the test entry file to a pre-set content distribution network includes: storing the renamed test tracking file and resource files to the content distribution network.

8. A device for updating experimental embedded points, characterized in that, include: The generation module is used to respond to a received product experiment request, determine the test entry file associated with the product experiment request, and generate corresponding test data according to the test data entry logic corresponding to the test entry file. The replacement module is used to respond to a received statistical analysis request, perform statistical analysis on the test data, and replace the test entry file with a pre-set official entry file if the statistical results of the test data meet the pre-set launch conditions. The processing module is used to respond to a request received from the product line, process the formal business request according to the business logic corresponding to the test entry file, and generate the corresponding formal tracking data according to the formal tracking logic corresponding to the formal entry file.

9. An electronic device, characterized in that, include: One or more processors; Storage device, used to store one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-7.

10. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-7.

Images