A method, apparatus, device, and readable storage medium for tracking data points.

Abstract

This invention discloses a method for event tracking management. This method utilizes a Chrome browser extension to embed events, enabling request interception and event selection, without intrusion into production or development environments, significantly improving overall efficiency. Simultaneously, this method performs real-time callback triggering and information collection and storage for message events on target product pages, thus resolving the inconsistency between manually maintained documentation and actual production event tracking, ensuring the comprehensiveness of data in front-end data management. Furthermore, after intercepting asynchronous requests, this method appends production environment tags to the request headers to accurately retrieve production environment logs. Matching and extracting logs based on these tags also ensures the accuracy of information extraction, guaranteeing the authenticity of data in front-end data management. This invention also discloses an event tracking management device, equipment, and readable storage medium, possessing corresponding technical effects.

Description

Technical Field

[0001] This invention relates to the field of data management technology, and in particular to a method, apparatus, device, and readable storage medium for managing data tracking points. Background Technology

[0002] With the development of the Internet, competition among various Internet products is becoming increasingly fierce. Analyzing user behavior data to further optimize products is a very effective approach. Important data sources for user behavior analysis are usually obtained through event tracking. The amount of automated full-event event tracking data collection / reporting is enormous, requiring the filtering of usable data from a large amount of data for data analysis.

[0003] Currently, manual screening and document maintenance are typically required. These documents are scattered, difficult to archive, and hard to find. Updates to tracking points (such as adding, deleting, modifying, and clarifying business implications) require a continuous and significant investment of human resources to update the documents promptly, resulting in substantial human resource costs and low efficiency. For data analysts, delayed document updates can hinder data analysis, and ambiguous notes can lead to additional communication costs. For front-end developers, the scattered and unarchived nature of the documents can lead to repetitive maintenance of the same tracking point during collaborative work, wasting resources and impacting overall maintenance efficiency.

[0004] In conclusion, improving the efficiency of data tracking and reducing resource waste are technical problems that urgently need to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this invention is to provide a method, apparatus, device, and readable storage medium for managing data tracking points, so as to improve the efficiency of data tracking point management and reduce resource waste.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] A method for managing event tracking points, comprising:

[0008] The event tracking management platform is displayed through the Chrome browser, allowing users to identify and preview the product page specified by the user.

[0009] If a message event is detected on an element in the product page, the corresponding event callback is triggered to obtain the tracking information of the element, and the tracking information is transmitted to the tracking management platform for storage and display.

[0010] If an asynchronous request is detected from the product page, a request header is appended to the asynchronous request and sent to the server. The server returns log information corresponding to the request header, and the page is rendered based on the log information. The request header includes a production environment tag.

[0011] Optionally, the step of displaying the event tracking management platform through the Chrome browser, and identifying and previewing the product page specified by the user, includes:

[0012] The event tracking management platform is displayed through the Chrome browser, and user-specified event tracking filtering information is received.

[0013] The corresponding front-end product is obtained based on the aforementioned tracking information.

[0014] Receive user input and determine the version specified by the user in the front-end product;

[0015] The route is mapped to the directory of the front-end product corresponding to the version, in order to display the product page.

[0016] Optionally, the aforementioned tracking point management method further includes:

[0017] Receive routing management requests and determine the management type;

[0018] If the management type is single-page route list management, the current route list is determined according to the route control and view transformation framework, the target page in the route list is output, the updated page is received, and the updated page is merged with the target page.

[0019] Optionally, if a message event is detected on an element in the product page, a corresponding event callback is triggered to obtain the element's tracking information, and the tracking information is transmitted to the tracking management platform for storage and display, including:

[0020] If a mouse triggers a listening event on the product page, the corresponding event tracking information is obtained and transmitted to the event tracking management platform for storage and display.

[0021] If a broadcast message indicating a change in a DOM node is received, the tracking information, routing list, and screenshot data of the changed element are collected and transmitted to the tracking management platform for information storage and display.

[0022] Optionally, after transmitting the tracking information to the tracking management platform for information storage and display, the method further includes:

[0023] The data tracking management platform receives the data tracking information;

[0024] Identify the event points in the stored event point list that match the event point information, and use them as target event points;

[0025] Create the association between the embedded information and the target embedded point, update the information, and display the output.

[0026] If the target tracking point does not exist, a new tracking point is created in the tracking point list, and the information is stored and displayed.

[0027] Optionally, determining the tracking points in the stored tracking point list that match the tracking point information includes:

[0028] The keys of the embedded information are decomposed into arrays to obtain the first array; the keys of each embedded information in the stored embedded list are decomposed into arrays to obtain the array set.

[0029] Calculate the minimum edit distance between the first array and each array in the array set;

[0030] If the minimum edit distance is less than a preset ratio of the key length of the embedded information, a match is determined.

[0031] Optionally, the aforementioned tracking point management method further includes:

[0032] Receive a tag management request and determine the management category; wherein, the management category includes: create, update, delete, and create;

[0033] If the management category is "created", then receive tag information; wherein, the tag information includes: tag name, interface, and fields.

[0034] A device for managing embedded data points, comprising:

[0035] The product identification unit is used to display the event tracking management platform through the Chrome browser, identify and preview the product page specified by the user;

[0036] The first management unit is used to trigger the corresponding event callback to obtain the tracking information of the element if a message event is detected on the element in the product page, and to transmit the tracking information to the tracking management platform for information storage and display.

[0037] The second management unit is used to, if it detects that the product page has issued an asynchronous request, append request header information to the asynchronous request and send it to the server, receive the log information corresponding to the request header information returned by the server, and complete the page rendering based on the log information; wherein, the request header information includes: production environment tag.

[0038] A computer device, comprising:

[0039] Memory, used to store computer programs;

[0040] A processor is used to implement the steps of the data tracking management method when executing the computer program.

[0041] A readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the data tracking management method.

[0042] The method provided in this invention achieves request interception and event tracking management through Chrome browser's own extension embedding method. It is completely non-intrusive to production and development environments, solves the problem of archiving event tracking documents, significantly improves the overall efficiency of event tracking management, and is compatible with all Vue projects. New projects can deploy the product immediately, making it convenient and quick. Simultaneously, this method monitors both message events and asynchronous requests, triggering real-time callbacks and collecting and storing information for message events on the target product page. This solves the problem of inconsistencies between manually maintained documentation and actual online event tracking, enabling automatic real-time updates of the latest status information based on event tracking settings, ensuring the comprehensiveness of data in front-end data management. Furthermore, in monitoring asynchronous requests, after intercepting the asynchronous request, this method appends a production environment tag to the request header information to accurately retrieve production environment logs. Obtaining logs as response data for the front-end interface ensures that the page is a true reflection of the online environment, and matching and extracting logs based on the production environment tag also ensures the accuracy of information extraction, guaranteeing the authenticity and accuracy of data in front-end data management.

[0043] Accordingly, embodiments of the present invention also provide a tracking point management device, equipment, and readable storage medium corresponding to the above-described tracking point management method, which have the above-described technical effects, and will not be described in detail here. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of the present invention or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a flowchart illustrating the implementation of a data tracking management method in an embodiment of the present invention.

[0046] Figure 2 This is a schematic diagram of a data tracking management platform according to an embodiment of the present invention;

[0047] Figure 3This is a schematic diagram of a tag management page according to an embodiment of the present invention;

[0048] Figure 4 This is a schematic diagram of a data list page according to an embodiment of the present invention;

[0049] Figure 5 This is a schematic diagram of a version management page according to an embodiment of the present invention;

[0050] Figure 6 This is a schematic diagram of a version management process in an embodiment of the present invention;

[0051] Figure 7 This is a schematic diagram of a routing management page in an embodiment of the present invention;

[0052] Figure 8 This is a schematic diagram of a routing management process in an embodiment of the present invention;

[0053] Figure 9 This is a schematic diagram of the structure of a data point management device according to an embodiment of the present invention;

[0054] Figure 10 This is a schematic diagram of the structure of a computer device according to an embodiment of the present invention. Detailed Implementation

[0055] The core of this invention is to provide a tracking point management method that can improve the efficiency of tracking point data management and reduce resource waste.

[0056] To enable those skilled in the art to better understand the present invention, the invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0057] Please refer to Figure 1 , Figure 1 This is a flowchart of a data tracking management method according to an embodiment of the present invention. The method includes the following steps:

[0058] S101. Display the event tracking management platform through the Chrome browser, and identify and preview the product page specified by the user;

[0059] Open the Chrome browser, such as Figure 2 The image shows a schematic diagram of a data tracking management platform, demonstrating how the platform receives product page information specified by the user (such as product, version, route, etc., which can be used to match product pages). The Chrome browser previews the product page using an iframe.

[0060] This application utilizes the Chrome browser and implements event tracking management through Chrome's own extensions. This includes plugin request interception and event selection, ensuring complete non-intrusion into production / development environments without affecting production stability. Furthermore, the plugin is compatible with all Vue projects, allowing new projects to deploy and use it immediately.

[0061] The product page specified by the user can be determined by the user's direct input, or it can be determined by further analysis based on information such as the product version entered by the user. This embodiment does not limit this and can be set according to actual usage needs.

[0062] S102. If a message event is detected on an element in the product page, the corresponding event callback is triggered to obtain the element's tracking information, and the tracking information is transmitted to the tracking management platform for storage and display.

[0063] The system monitors message events on the product page specified by the user for preview. If a message event occurs, the corresponding event callback mechanism is triggered (different callback mechanisms can be set according to different message events). The system collects the corresponding data according to the event callback mechanism, generates event tracking information, and then synchronizes the collected event tracking information to the event tracking management platform to realize the listening and data storage of event tracking, ensuring that the event tracking information is updated and stored in real time.

[0064] The monitoring of message events mainly includes the monitoring of messages and the monitoring of events. The specific monitoring and collection mechanism is not limited in this embodiment. It can be set according to different actual monitoring and collection needs. It will not be elaborated in this embodiment. Please refer to the following embodiment for details.

[0065] The browser's monitoring of message events injected into the product page specified by the user can be achieved by injecting scripts into the HTML file.

[0066] S103. If an asynchronous request is detected from the product page, append request header information to the asynchronous request and send it to the server. Receive the log information corresponding to the request header information returned by the server and complete the page rendering based on the log information.

[0067] You can run asynchronous request monitoring by opening the Chrome browser. It runs concurrently with the Chrome browser. Specifically, you can use the API chrome.webRequest.onBeforeSendHeaders.addListener provided by the Chrome Extension to intercept requests for a specified service (preview service) and a specified request type ('xmlhttprequest', 'main_frame', 'sub_frame') before the request headers are sent. After interception, you append request header information and then send the request to the server. When the server receives the newly added request parameters, it will retrieve the server data and return it to the client to render the page.

[0068] This feature allows you to intercept and process all asynchronous requests, or only asynchronous requests of a specified type or for a specific service. The specific settings can be configured according to the actual monitoring needs, and are not limited here.

[0069] The front-end page is driven by server-side data. However, the user status in the production environment is extremely complex. To view the pages corresponding to various data statuses, tags (i.e., production environment tags) can be used for quick and accurate matching. In this application, for specific asynchronous requests, a request body containing tags is added to accurately search for the log information corresponding to that tag for page rendering, thus solving the problem of real user accounts. In addition, this application can also set various preset tags, i.e., the key and value of the interface, to accurately match the logs in the production environment. The logs are used as the response data of the front-end interface. Since the logs are real data of all real users online, this ensures that the page is a true reflection of the online environment and guarantees the authenticity of the output data.

[0070] It should be noted that the execution order of steps S102 and S103 is not limited. They can be executed in parallel or sequentially, depending on the actual deployment needs. This will not be elaborated further here.

[0071] In addition to the steps mentioned above, to facilitate the addition, modification, and deletion of tags, further unified tag management settings can be implemented. Optionally, one specific implementation step is as follows:

[0072] Step S104: Receive tag management request and determine management category; wherein, management category includes: create, update, delete, and create;

[0073] Step S105: If the management category is "Create", receive tag information; wherein, the tag information includes: tag name, interface and field.

[0074] like Figure 3The diagram shows a tag management page where tags can be created, updated, and deleted. Tag creation requires a tag name and tag content; the tag content includes the interface and fields. This tag management method can comprehensively cover different tag management needs, and precise matching can be achieved based on this tag information format. This embodiment only uses the above tag management method as an example; other implementation methods can refer to the description in this embodiment and will not be elaborated further. Of course, tag management settings can also be omitted, and this is not a limitation.

[0075] Based on the above introduction, the technical solution provided by this invention achieves request interception and event tracking management through the Chrome browser's own extension embedding method. It is completely non-intrusive to production and development environments, solves the problem of archiving event tracking documents, significantly improves the overall efficiency of event tracking management, and is compatible with all Vue projects. New projects can deploy the product immediately, making it convenient and quick. Simultaneously, this method monitors both message events and asynchronous requests, triggering real-time callbacks and collecting and storing information for message events on the target product page. This solves the problem of inconsistencies between manually maintained documents and actual online event tracking, achieving automatic real-time updates of the latest status information based on event tracking settings, ensuring the comprehensiveness of data in front-end data management. Furthermore, in monitoring asynchronous requests, after intercepting the asynchronous request, this method appends a production environment tag to the request header information to accurately retrieve production environment logs. Obtaining logs as response data for the front-end interface ensures that the page is a true reflection of the online environment, and matching and extracting logs based on the production environment tag also ensures the accuracy of information extraction, guaranteeing the authenticity and accuracy of data in front-end data management.

[0076] It should be noted that, based on the above embodiments, the present invention also provides corresponding improvements. In the preferred / improved embodiments, steps that are the same as or corresponding to those in the above embodiments can be referred to each other, and the corresponding beneficial effects can also be referred to each other; however, these will not be elaborated upon in the preferred / improved embodiments herein.

[0077] The above embodiments do not limit the method for determining the product page specified by the user. This embodiment mainly describes this method, which can be performed according to the following steps:

[0078] Step S11: Display the event tracking management platform through the Chrome browser and receive the event tracking filtering information specified by the user;

[0079] like Figure 4The image shows a schematic diagram of a data list page. The data list page can consist of filter conditions and a filter list. The filter conditions mainly include product, version, page, tracking key, remarks, creation time and creator, etc. Users can manage tracking points by searching, updating and deleting.

[0080] Step S12: Obtain the corresponding front-end product based on the tracking information;

[0081] Step S13: Receive user operation and determine the version specified by the user in the front-end product;

[0082] like Figure 5 The image shows a schematic diagram of a version management page. The filter criteria on the version management page can mainly consist of product, code repository, and version number. These version filter criteria can be set for different versions of products, and different versions can correspond to different usage requirements. The version to be output is displayed according to the user's specification, which can solve the preview problem when there are multiple products, multiple code repositories, and multiple branches of development in collaboration with multiple people.

[0083] like Figure 6 The diagram shows a version management process. After selecting or entering the corresponding filter conditions, users can obtain the corresponding front-end products (js, css, img, and html) and check whether the product has been deployed on the server. Users can also further deploy / delete / update the product.

[0084] Step S14: Map the route to the directory of the front-end product corresponding to the version to display the product page.

[0085] The selected product, version, and route are passed to the URL. The server finds the specific version of the product in the product directory based on the request parameters, maps the route to that product directory, and outputs the corresponding HTML to complete the preview of the product page.

[0086] To facilitate the mapping and display of the product catalog, route management can be further configured for each product. Optionally, one route management method is as follows:

[0087] Step S15: Receive a routing management request and determine the management type;

[0088] Step S16: If the management type is single-page route list management, determine the current route list according to the route control and view transformation framework, output the target page in the route list, receive the updated page, and merge the updated page with the target page.

[0089] like Figure 7 The image shows a schematic diagram of a route management page. Route management types mainly include single-page route list management and individual route management. For example... Figure 8The diagram illustrates a route management process. In this process, updating the single-page route list relies on a Chrome extension. When updating routes, the event tracking platform loads the current SPA (Single Page Application) as an iframe. The extension retrieves the current route list using `root.__vue__._routerRoot.$options.router.options.routes` (Vue 2.x) or `root.__vue_app__._context.config.globalProperties.$router.getRoutes` (Vue 3.x) and sends the route list (using `postMessage`) to the main page. The main page then merges the old and new route lists, completing the route list update. Updates for individual routes can be found in the relevant technical documentation and will not be elaborated upon here.

[0090] This route management method can ensure the continuous and stable updating of the route list.

[0091] Based on the above introduction, this embodiment creates different directories and deploys different products according to product and version information. One service corresponds to N products, and a preview service returns the products in the corresponding directory according to product and version information, thereby satisfying the preview needs of multiple environments, both online and offline.

[0092] In addition, the above embodiments do not limit the mechanism for tracking and monitoring message events on the product page. This embodiment introduces a specific implementation of one mechanism. Other implementation methods can refer to the introduction of this embodiment, and will not be repeated here.

[0093] Monitoring message events can specifically include monitoring messages and monitoring mouse events.

[0094] Step S21: If a mouse event is detected on the product page, obtain the corresponding event tracking information and transmit it to the event tracking management platform for storage and display.

[0095] Event monitoring can be achieved by obtaining the document object of the product page, registering mouse events (including mouseover, mouseout, mouseleave, etc.), and adding corresponding event listeners. This embodiment does not limit the event monitoring settings, nor does it limit the specific types of mouse events registered. The settings can be made according to the actual needs of use.

[0096] When the mouse triggers a corresponding event on the product page, a corresponding callback will be triggered. The callback function retrieves the event tracking information and can broadcast it to the parent page via postMessage to achieve event listening.

[0097] Step S22: If a broadcast message indicating a change in a DOM node is received, collect the tracking information, route list, and screenshot data of the changed element, and transmit them to the tracking management platform for information storage and display.

[0098] Listening to message communication can be achieved by broadcasting messages using `postMessage`. The parent page listens for message events, and when a broadcast message is received, it processes the transmitted data. Specifically, the data transmission involved in the plugin mainly includes: tracking information (tracking information corresponding to elements selected by mouse hover / hover / double-click, and tracking information of changed elements collected when the product page generates DOM node changes), route lists, and screenshot data. Data items can also be added or deleted as needed; this embodiment does not impose any restrictions on this.

[0099] After completing the message listening settings for the product page, if the mouse clicks / hoveres / hovers / double-clicks an element (e.g., element 1) on the subpage, the registered event callback will be triggered. The callback function retrieves the event tracking information for element 1 and posts a message to the main page. The main page's event listener callback will then be triggered, and it will begin processing and displaying the event tracking information for element 1. When annotation information is entered on the main page and saved, the main page will post a message to the subpage to retrieve a screenshot. The screenshot, event tracking information, and the listening information set for the product, version, and page will then be saved for subsequent data processing and management.

[0100] Furthermore, the above embodiments do not limit the storage and display methods of the updated tracking information received by the tracking management platform. This embodiment introduces a data processing method for the platform, in which, after the tracking information is transmitted to the tracking management platform for storage and display, the following steps can be further performed:

[0101] Step S106: The event tracking management platform receives event tracking information;

[0102] Step S107: Determine the tracking points that match the tracking information in the stored tracking point list and use them as target tracking points;

[0103] Step S108: Create the association between the tracking information and the target tracking point, update the information and display the output;

[0104] Step S109: If the target tracking point does not exist, create a new tracking point in the tracking point list, and store and display the information.

[0105] like Figure 2As shown on the middle page, after the main page receives the event tracking information, annotations can be added to the page and saved. When updating the stored event tracking information, users can select associated information to determine the matching event tracking information. Selecting associated information means that these two similar event tracking points are considered to be data with the same business meaning, thus ensuring that the data processing rules remain unchanged when event tracking is updated due to requirement iteration.

[0106] Optionally, the matching mechanism for the embedded points in step S107 can be executed according to the following steps:

[0107] Step S71: Decompose the keys of the tracking information into arrays to obtain the first array; decompose the keys of each tracking information in the stored tracking list into arrays to obtain the array set;

[0108] Step S72: Calculate the minimum edit distance between the first array and each array in the array set;

[0109] Step S73: If the minimum edit distance is less than the preset ratio of the key length of the embedded information, a match is determined.

[0110] The keys of the tracking information are decomposed into arrays to obtain the first array; the keys of each tracking information in the stored tracking information list are decomposed into arrays to obtain the array set; the minimum edit distance is calculated for each array in the first array and the array set; if the minimum edit distance is less than the preset ratio of the key length of the tracking information, a match is determined.

[0111] To save the data, diff it with the saved event tracking list. First, split the keys of the new and old event tracking points into arrays as strings. Then, calculate the minimum edit distance of the arrays (for example, by calling a diff algorithm). When the edit distance is less than a preset proportion (e.g., 1 / 2) of the length of the event tracking information key, the two event tracking key keys can be considered similar. The new event tracking point is then diffed with each item in the old event tracking list in turn. After diffing, the event tracking information with the minimum edit distance is updated, stored, and displayed in a pop-up window.

[0112] It should be noted that this embodiment only uses the above two methods of determining matching points as examples. Other implementation methods can refer to the description in this embodiment, and will not be repeated here.

[0113] Corresponding to the above method embodiments, this invention also provides a tracking point management device, which can be referred to in conjunction with the tracking point management method described above.

[0114] See Figure 9 As shown, the device includes the following modules: a product determination unit 110, a first management unit 120, and a second management unit 130.

[0115] Among them, the product determination unit 110 is mainly used to display the tracking management platform through the Chrome browser, determine and preview the product page specified by the user;

[0116] The first management unit 120 is mainly used to trigger the corresponding event callback to obtain the element's tracking information if a message event is detected on an element in the product page, and then transmit the tracking information to the tracking management platform for information storage and display.

[0117] The second management unit 130 is mainly used to add request header information to the asynchronous request and send it to the server if it detects that the product page has issued an asynchronous request. It also receives the log information corresponding to the request header information returned by the server and completes the page rendering based on the log information. The request header information includes a production environment tag.

[0118] For details on the addition of other module units, please refer to the above method embodiments; they will not be repeated here.

[0119] Corresponding to the above method embodiments, this invention also provides a computer device. The computer device described below and the tracking point management method described above can be referred to each other.

[0120] The computer device includes:

[0121] Memory, used to store computer programs;

[0122] A processor is used to implement the steps of the tracking point management method in the above method embodiments when executing a computer program.

[0123] For details, please refer to Figure 10 This is a schematic diagram illustrating the specific structure of a computer device provided in this embodiment. The computer device can vary significantly due to differences in configuration or performance. It may include one or more central processing units (CPUs) 322 (e.g., one or more processors) and a memory 332. The memory 332 stores one or more computer application programs 342 or data 344. The memory 332 can be temporary or persistent storage. The program stored in the memory 332 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the data processing device. Furthermore, the central processing unit 322 may be configured to communicate with the memory 332 and execute the series of instruction operations stored in the memory 332 on the computer device 301.

[0124] Computer device 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input / output interfaces 358, and / or one or more operating systems 341.

[0125] The steps in the tracking point management method described above can be implemented using the structure of computer equipment.

[0126] Corresponding to the above method embodiments, this invention also provides a readable storage medium. The readable storage medium described below can be referred to in conjunction with the tracking point management method described above.

[0127] A readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the tracking point management method described in the above method embodiments.

[0128] Specifically, the readable storage medium can be a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, or any other readable storage medium capable of storing program code.

[0129] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of the invention.

Claims

1. A method for managing data collection points, characterized in that, include: The event tracking management platform is displayed via Chrome browser extension embedding, allowing users to identify and preview the product pages specified by the user. If a message event is detected on an element in the product page, the corresponding event callback is triggered to obtain the tracking information of the element, and the tracking information is transmitted to the tracking management platform for storage and display. If an asynchronous request is detected from the product page, a request header is appended to the asynchronous request and sent to the server. The server then receives the log information corresponding to the request header and renders the page based on the log information. The request header includes a production environment tag, which is used by the server to match logs from the production environment.

2. The method for managing embedded data points according to claim 1, characterized in that, The process of displaying the event tracking management platform via a Chrome browser extension, and identifying and previewing the user-specified product page, includes: The event tracking management platform is displayed via Chrome browser extension embedding and receives event tracking filtering information specified by the user. The corresponding front-end product is obtained based on the aforementioned tracking information. Receive user input and determine the version specified by the user in the front-end product; The route is mapped to the directory of the front-end product corresponding to the version, in order to display the product page.

3. The embedding point management method according to claim 2, characterized in that, Also includes: Receive routing management requests and determine the management type; If the management type is single-page route list management, the current route list is determined according to the route control and view transformation framework, the target page in the route list is output, the updated page is received, and the updated page is merged with the target page.

4. The method for managing embedded data points according to claim 1, characterized in that, If a message event is detected on an element in the product page, a corresponding event callback is triggered to obtain the element's tracking information. This tracking information is then transmitted to the tracking management platform for storage and display, including: If a mouse triggers a listening event on the product page, the corresponding event tracking information is obtained and transmitted to the event tracking management platform for storage and display. If a broadcast message indicating a change in a DOM node is received, the tracking information, routing list, and screenshot data of the changed element are collected and transmitted to the tracking management platform for information storage and display.

5. The method for managing embedded data points according to claim 1, characterized in that, After transmitting the tracking information to the tracking management platform for storage and display, the method further includes: The data tracking management platform receives the data tracking information; Identify the event points in the stored event point list that match the event point information, and use them as target event points; Create the association between the embedded information and the target embedded point, update the information, and display the output. If the target tracking point does not exist, a new tracking point is created in the tracking point list, and the information is stored and displayed.

6. The method for managing embedded data points according to claim 5, characterized in that, The step of determining the tracking points that match the tracking point information in the stored tracking point list includes: The keys of the embedded information are decomposed into arrays to obtain the first array; the keys of each embedded information in the stored embedded list are decomposed into arrays to obtain the array set. Calculate the minimum edit distance between the first array and each array in the array set; If the minimum edit distance is less than a preset ratio of the key length of the embedded information, a match is determined.

7. The method for managing embedded data points according to claim 1, characterized in that, Also includes: Receive a tag management request and determine the management category; wherein, the management category includes: update, delete, and create; If the management category is "created", then receive tag information; wherein, the tag information includes: tag name, interface, and fields.

8. A device for managing embedded points, characterized in that, The steps for implementing the data tracking management method as described in any one of claims 1 to 7 include: The product identification unit is used to display the event tracking management platform via Chrome browser extension embedding, and to identify and preview the product page specified by the user; The first management unit is used to trigger the corresponding event callback to obtain the tracking information of the element if a message event is detected on the element in the product page, and to transmit the tracking information to the tracking management platform for information storage and display. The second management unit is used to, if it detects that the product page has issued an asynchronous request, append request header information to the asynchronous request and send it to the server, receive the log information corresponding to the request header information returned by the server, and complete the page rendering based on the log information; wherein, the request header information includes: production environment tag.

9. A computer device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the tracking point management method as described in any one of claims 1 to 7 when executing the computer program.

10. A readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the data entry management method as described in any one of claims 1 to 7.

Images