Page operation analysis, embedding method, device, equipment and storage medium

Abstract

The embodiment of the present application provides a page operation analysis, tracking method, device, equipment and storage medium. In the page operation analysis method, after detecting the access operation to the page element, the operation behavior monitoring data corresponding to the access operation is obtained, and after sending a processing request to the server, the response result of the server to the processing request is monitored to obtain the operation result monitoring data; based on the operation behavior monitoring data and the operation result monitoring data, a variety of data generated by the access operation on the page element can be obtained more comprehensively, and the access operation on the page element is monitored at the functional level, which is conducive to more accurate analysis of the access operation on the page element.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a page operation analysis, tracking method, device, equipment and storage medium. Background Art

[0002] In some scenarios, it is necessary to analyze the access operations on the page to mine the user behavior on the page. Based on the mining results of user behavior, the design of the page can be optimized or the business functions carried by the page can be optimized.

[0003] The page analysis method provided by the prior art cannot accurately analyze the access operations on different page elements on the page. Therefore, a new solution is needed. Summary of the invention

[0004] Multiple aspects of the present application provide a page operation analysis, tracking method, device, equipment and storage medium for accurately analyzing access operations on page elements.

[0005] An embodiment of the present application provides a page operation analysis method, including: displaying a page, the page including a first page element; responding to an access operation on the first page element, and obtaining operation behavior monitoring data corresponding to the access operation; sending a processing request to a server based on an event triggered by the access operation, and monitoring the response result of the server to the processing request to obtain operation result monitoring data; analyzing the access operation on the first page element based on the operation behavior monitoring data and the operation result monitoring data.

[0006] An embodiment of the present application also provides a page operation analysis method, including: displaying a page, the page including a first page element; responding to an access operation on the first page element, tracking an event triggered by the access operation according to first tracking point deployment information to obtain operation behavior monitoring data; sending a processing request to a server according to the event triggered by the access operation; tracking the processing request according to second tracking point deployment information to obtain a response result of the server to the processing request as operation result monitoring data; analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

[0007] An embodiment of the present application also provides a tracking point method, including: obtaining an abstract syntax tree corresponding to a page; determining at least one event associated with the page based on the abstract syntax tree; adding first tracking point deployment information and second tracking point deployment information in the event handler corresponding to each of the at least one event; wherein the first tracking point deployment information is used to track the corresponding event when the corresponding event is triggered, and the second tracking point deployment information is used to track the processing request corresponding to the corresponding event.

[0008] An embodiment of the present application also provides a page operation analysis device, including: a display module, used to: display a page, the page including a first page element; a first monitoring module, used to: respond to an access operation on the first page element, and obtain operation behavior monitoring data corresponding to the access operation; a request module, used to: send a processing request to a server according to an event triggered by the access operation; a second monitoring module, used to: monitor the response result of the server to the processing request, and obtain operation result monitoring data; an analysis module, used to: analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

[0009] An embodiment of the present application also provides a page operation analysis device, including: a display module, used to: display a page, the page including a first page element; a first monitoring module, used to: respond to an access operation on the first page element, and track the event triggered by the access operation according to first tracking point deployment information to obtain operation behavior monitoring data; a request module, used to: send a processing request to a server according to the event triggered by the access operation; a second monitoring module, used to: track the processing request according to the second tracking point deployment information to obtain the response result of the server to the processing request as operation result monitoring data; an analysis module, used to: analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

[0010] An embodiment of the present application also provides a tracking device, including: a page analysis module, used to: obtain an abstract syntax tree corresponding to a page; determine at least one event associated with the page based on the abstract syntax tree; a tracking module, used to: add first tracking deployment information and second tracking deployment information in the event handler corresponding to each of the at least one event; wherein the first tracking deployment information is used to track the corresponding event when the corresponding event is triggered, and the second tracking deployment information is used to track the processing request corresponding to the corresponding event.

[0011] An embodiment of the present application also provides an electronic device, including: a memory and a processor; the memory is used to store one or more computer instructions; the processor is used to execute the one or more computer instructions to: execute the page operation analysis method provided by the embodiment of the present application or the tracking method provided by the embodiment of the present application.

[0012] An embodiment of the present application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the page operation analysis method provided by the embodiment of the present application or the tracking method provided by the embodiment of the present application.

[0013] In an embodiment of the present application, after an access operation to a page element is detected, the operation behavior monitoring data corresponding to the access operation is obtained, and after a processing request is sent to the server, the response result of the server to the processing request is monitored to obtain the operation result monitoring data; based on the operation behavior monitoring data and the operation result monitoring data, a variety of data generated by the access operation on the page element can be more comprehensively obtained, and functional-level monitoring of the access operation on the page element is achieved, which is conducive to more accurate analysis of the access operation on the page element. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0015] Figure 1 is a flow chart of a page operation analysis method provided by an exemplary embodiment of the present application;

[0016] Figure 2 is a flow chart of a page operation analysis method provided by another exemplary embodiment of the present application;

[0017] Figure 3 is a schematic diagram showing a page operation analysis result provided by an exemplary embodiment of the present application;

[0018] Figure 4 is a flow chart of a page operation analysis method provided by another exemplary embodiment of the present application;

[0019] Figure 5 is a structural diagram of a page operation analysis device provided by an exemplary embodiment of the present application;

[0020] Figure 6 A schematic diagram of the structure of a point embedding device provided for an exemplary embodiment of the present application;

[0021] Figure 7 It is a schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0023] In some commonly used page operation analysis methods, manual analysis of backend interface logs is usually used to analyze access operations on the page, or exception capture statements (for example, try / catch statements used to capture web page errors) are used on the front end to monitor access operations on page elements. These commonly used page operation analysis methods cannot accurately analyze access operations on different page elements on the page.

[0024] In view of the above technical problems, a solution is provided in some embodiments of the present application. The technical solutions provided by the embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0025] Figure 1 is a flow chart of a page operation analysis method provided by an exemplary embodiment of the present application. Figure 1 As shown, the method includes:

[0026] Step 101: Display a page, which includes a first page element.

[0027] Step 102: respond to the access operation on the first page element and obtain operation behavior monitoring data corresponding to the access operation.

[0028] Step 103: Send a processing request to the server according to the event triggered by the access operation, and monitor the response result of the server to the processing request to obtain operation result monitoring data.

[0029] Step 104: Analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

[0030] The execution subject of this embodiment may be a terminal device, which may be implemented as a computer, a mobile phone, a tablet computer, etc., which is not limited in this embodiment. Among them, the page may include any page provided by the terminal device for displaying information, for example, a web page provided by a browser installed on a computer, an application page provided by an application of a mobile terminal, etc., which is not limited in this embodiment.

[0031] A page may contain one or more page elements, such as control elements such as buttons and edit boxes, and hyperlink elements such as text hyperlinks and image hyperlinks. Page elements can provide users with a variety of different operation entrances, so that users can access and use the functions provided by the page based on different operation entrances. For example, when a page element is implemented as a button control such as "Edit", "Delete", and "Save", the user can access and use the functions of editing data, deleting data, and saving data provided by the page based on the above button controls. For another example, when a page element is implemented as a text hyperlink element or an image hyperlink element, the user can access other pages pointed to by the link based on the above hyperlink element, which will not be repeated.

[0032] The user who initiates the access operation to the page element is usually the service object of the page information. For example, it may include a user who uses a terminal device to access an application page, and a user who uses a browser to access a web page. In some other scenarios, the user may also be a user for testing the page development effect or a computer program for simulating page testing, which is not limited in this embodiment.

[0033] An access operation on a page element refers to a detectable operation initiated by a user on a page element. The access operation can be implemented as a variety of different types of operations, for example, it can be implemented as a click operation, input operation, drag operation, long press operation, etc. on a page element, which is not limited in this embodiment. Among them, the first page element refers to any page element on the page; the term "first" is used here to limit it, which is only used for the convenience of description and distinction.

[0034] When an access operation on the first page element is detected, a series of data generated by the access operation behavior can be monitored to obtain operation behavior monitoring data. The operation behavior monitoring data may include a variety of data for recording user behavior and accessed information content, such as user attribute data and page element attribute data, so as to analyze the user's access operation behavior.

[0035] Each page element can be bound to one or more events, and each event has an event listener and an event handler. The event listener is used to listen to the access operation on the page element to detect whether the event is triggered by the access operation on the page element. The event handler is used to perform the corresponding event processing operation when the event is triggered.

[0036] In some scenarios, the event handler needs to complete the event processing operation with the support of the server. For example, the server needs to provide data support and computing power support. When an access operation occurs on the first page element, an event bound to the first page element is triggered. If the processing of the event requires interaction with the server, the event handler corresponding to the event can send a processing request corresponding to the event to the server. For example, the user clicks the "Delete" button on the page, triggering a deletion event for specific data, and the specific data is stored on the server. Then, the event handler of the deletion event can send a data deletion request to the server to implement the data deletion function bound to the button.

[0037] After sending a processing request to the server, the terminal device can monitor the server's response to the processing request and obtain operation result monitoring data based on the response result. The operation result monitoring data is used to record whether the event triggered by the access operation is successfully processed, that is, whether the user's access operation to the page element is successfully responded to.

[0038] The above process of obtaining operation behavior monitoring data and operation result monitoring data realizes monitoring of access operations on page elements from different links, and more completely captures various data generated by access operations. Based on the operation behavior monitoring data and operation result monitoring data, the access operations on page elements can be analyzed.

[0039] In this embodiment, after an access operation to a page element is detected, the operation behavior monitoring data corresponding to the access operation is obtained, and after a processing request is sent to the server, the response result of the server to the processing request is monitored to obtain the operation result monitoring data; based on the operation behavior monitoring data and the operation result monitoring data, a variety of data generated by the access operation on the page element can be more comprehensively obtained, and functional-level monitoring of the access operation on the page element is realized, which is conducive to more accurate analysis of the access operation on the page element.

[0040] It is worth noting that in the above and below embodiments of the present application, the operation behavior monitoring data and operation result monitoring data generated by the access operations on the page elements can be obtained by performing multiple tracking operations on the access operations on the page.

[0041] Among them, tracking, also known as event tracking, refers to adding information monitoring points in a specific processing link, which can capture specified information under the trigger of a specific event or a specific operation. The following will further explain the page operation analysis method provided in the embodiment of the present application in combination with the tracking operation.

[0042] Figure 2is a flow chart of a page operation analysis method provided by another exemplary embodiment of the present application. Figure 2 As shown, the method includes:

[0043] Step 201: Obtain the abstract syntax tree corresponding to the page.

[0044] Step 202: Determine at least one event associated with the page according to the abstract syntax tree; wherein each event may be triggered by an access operation on a page element to which it is bound.

[0045] Step 203: Add the first burying point deployment information and the second burying point deployment information to the event processor corresponding to each of the at least one event.

[0046] Step 204: display the page, and display at least one page element on the page.

[0047] Step 205: respond to the access operation on the first page element, and track the event triggered by the access operation according to the first tracking point deployment information to obtain operation behavior monitoring data.

[0048] Step 206: Send a processing request to the server according to the event triggered by the access operation.

[0049] Step 207: Track the processing request according to the second tracking point deployment information to obtain operation result monitoring data.

[0050] Step 208: Analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

[0051] In step 201, an Abstract Syntax Tree (AST) is an abstract representation of the syntax structure of the source code. It represents the syntax structure of the source code in a tree structure, and a node on the tree structure represents a structure in the source code.

[0052] Optionally, if the page is developed in JavaScript (a programming language, referred to as JS), the Babel tool can be used to obtain the abstract syntax tree of the page. The Babel tool is a JS editor that can convert source languages. For example, the Babel tool can convert the JS source code corresponding to the page into AST based on the babylon library, which will not be described in detail.

[0053] In step 202, based on the grammatical structure expressed by the abstract syntax tree, one or more events associated with the page can be determined. The one or more events are bound to page elements, and each event can be triggered by an access operation on the page element to which it is bound. One page element can be bound to one or more events.

[0054] For example, a page button can be bound to a single click event and a long press event; the single click event can be triggered by a single click on the page button, and the long press event can be triggered by a long press on the page button. For another example, a page image can be bound to a double click event and a drag event; the double click event can be triggered by a double click on the page image, and the drag event can be triggered by a drag on the page image.

[0055] In step 203, the event processor is used to execute a set event processing operation when the event bound to the page element is triggered by an access operation on the page element, so as to realize the business function carried by the page element.

[0056] In order to improve the monitoring process of access operations, two tracking points can be performed in the event processor to form two information monitoring points in the event processor. Optionally, the first tracking point deployment information and the second tracking point deployment information can be added in each event processor. Among them, the first tracking point deployment information is used to track the event to which it belongs when the event to which it belongs is triggered; the second tracking point deployment information is used to track the processing request corresponding to the event to which it belongs.

[0057] The following will take any event in the at least one event as an example to exemplify the two tracking operations. For the convenience of description, the any event is described as the first event.

[0058] Optionally, the code corresponding to the event handler of the first event can be determined in the source code corresponding to the page. Then, the target code can be determined in the code corresponding to the event handler, and the target code is used to send a corresponding processing request to the server when the first event is triggered. Then, the code corresponding to the first embedding point deployment information can be added before the target code, and the code corresponding to the second embedding point deployment information can be added after the target code. Based on the above operations, two information monitoring points are formed in the event handler, the first information monitoring point is before sending the processing request, and the second information monitoring point is after sending the processing request.

[0059] Optionally, the above steps 201 to 203 can be implemented by a browser plug-in or application plug-in developed based on the Babel tool. When the page is opened in a browser or application, the plug-in can automatically analyze the AST corresponding to the page, and automatically perform two tracking points for each event in the code that can be triggered by the operation according to the AST. In addition, the automatic tracking operation based on the browser or application is realized, reducing the labor cost.

[0060] In step 204, optionally, the page may be displayed when the user accesses the page through a terminal device, or the page may be displayed when triggered by a specific system event.

[0061] In step 205, the first page element can be any page element of the at least one page element, and this embodiment does not impose any limitation. The access operation on the first page element can trigger an event bound to the first page element. Based on the record of the aforementioned embedding step, the event processor corresponding to the triggered event includes two information monitoring points, namely: an information monitoring point corresponding to the first embedding deployment information, and an information monitoring point corresponding to the second embedding deployment information.

[0062] The information monitoring point corresponding to the first tracking point deployment information can track the event triggered by the access operation when the access operation occurs on the first page element, and use the tracked data associated with the event as the operation behavior monitoring data. Optionally, the operation behavior monitoring data may include: at least one of action attribute data, user attribute data, operation object attribute data, and operation verification data.

[0063] Among them, the action attribute data may include the operation frequency and operation type of the access operation that triggered the event. The user attribute data may include the identifier of the user who initiated the access operation (such as the user account, etc.). The operation object data may include relevant information of the page element being accessed, such as the identifier of the page element, the type of page element, the business function corresponding to the page element, etc. The operation verification data may include configuration information verification data, interface verification data, JS form verification data, etc. I will not go into details.

[0064] It should be understood that the first tracking point deployment information can be configured in a personalized manner to indicate which operation behavior monitoring data the information monitoring point obtains during the event tracking process. The above-listed data are only for exemplary description, and this embodiment includes but is not limited to this.

[0065] In step 206, a corresponding processing request may be sent to the server according to the event triggered by the access operation. In some scenarios, the first page element is bound to multiple events. When the type of event triggered by the access operation is different, the processing request sent to the server is also different.

[0066] For example, a button on the page is bound to a single-click event and a double-click event. The single-click event is used to implement function M, and the double-click event is used to implement function N. If the access operation on the button is a single-click operation, and the single-click operation triggers the single-click event, a processing request corresponding to function M can be sent to the server; if the access operation is a double-click operation, and the double-click operation can trigger the double-click event, a processing request corresponding to function N can be sent to the server.

[0067] In step 207, after sending the processing request to the server, the information monitoring point corresponding to the second burying point deployment information is activated, and the processing request can be tracked according to the second burying point deployment information. In the process of tracking the processing request, the information monitoring point can capture the server's response result to the processing request and obtain the operation result monitoring data.

[0068] Optionally, the operation result monitoring data includes at least one of interface status data, response content data, and response failure type data.

[0069] The interface includes the interface between the event processor and the communication component on the terminal device, and the interface used for communication between the terminal device and the server. Interface status data is data obtained by monitoring the working status of the interface, and may include interface abnormality data, interface normal data, etc. Based on the interface status data, the cause of the failure of the access operation can be analyzed. For example, in some scenarios, the communication interface between the terminal device and the server is abnormal, and the server cannot receive the processing request, which leads to the failure to successfully respond to the access operation on the page element.

[0070] The response content refers to the actual content returned by the server based on the processing request. By analyzing the response content, it can be identified whether the failure to successfully respond to the access operation on the page element is due to reasons on the server side. For example, in some scenarios, there is no abnormality in the interface, and the server successfully receives the processing request, but an abnormality occurs on the server side, causing the processing to fail. Although the server successfully returns the response content, the response content indicates that the processing request was not successfully processed. In this scenario, the terminal device cannot successfully respond to the access operation on the page element. By analyzing the monitored response content, it is possible to accurately analyze whether the reason for the failure to respond to the access operation comes from the server side.

[0071] Among them, the response failure type may include an interface abnormal failure type, a server abnormal failure type, or a failure type caused by other reasons on the terminal device side or the server side, which is not limited in this embodiment.

[0072] Based on the above two information monitoring points, a series of processes after the access operation occurs on the first page element can be relatively completely monitored. After obtaining the operation behavior monitoring data and the operation result monitoring data, step 208 can be executed to analyze the operation on the first page element.

[0073] Optionally, data generated by access operations on page elements within a specific period can be counted to analyze according to the statistical period. The specific period can be one day, three days or one week. Alternatively, the specific period can be flexibly adjusted according to the information content published on the page, which is not limited in this embodiment.

[0074] Optionally, the data sending method and the data receiving end address may be configured in the first burying point deployment information to instruct the information monitoring point to send the acquired operation behavior monitoring data to the target data receiving end in a specified manner. Also, the data sending method and the data receiving end address may be configured in the second burying point deployment information to instruct the information monitoring point to send the acquired operation result monitoring data to the target data receiving end in a specified manner.

[0075] For example, by configuring the first burying point deployment information, the information monitoring point can be instructed to send the operation behavior monitoring data to the storage space with address B1 through the A1 interface. At the same time, by configuring the second burying point deployment information, the monitoring point can be instructed to send the operation behavior monitoring data to the storage space with address B2 through the A2 interface. Among them, address B1 and address B2 can be the same address or different addresses, which is not limited in this embodiment.

[0076] Optionally, when tracking each event, a unique identification (such as logID) can be set for the event. The operation behavior monitoring data and operation result monitoring data generated after each event is triggered by an access operation carry the unique identification of the event. Based on the unique identification of the event, the operation behavior monitoring data and operation result monitoring data corresponding to the event can be associated.

[0077] Based on the above, when analyzing the access operation on the first page element, the event bound to the first page element can be determined, and then the operation behavior monitoring data and operation result monitoring data corresponding to the event can be obtained from the target data receiving end according to the unique identification identifier of the event. Next, the access operation on the first page element can be analyzed according to the obtained operation behavior monitoring data and operation result monitoring data.

[0078] Optionally, analyzing the access operations on the first page element may include: analyzing the number of access operations on the first page element, the number of access users, the number of processed requests, the response success rate of the access operations, the response failure rate of the access operations, the failure reasons of the access operations and / or the distribution characteristics of the failure reasons.

[0079] The number of access operations refers to the frequency of access operations on the first page, which can be obtained based on the action attribute data in the operation behavior monitoring data. Each time an access operation is detected, the operation frequency can be recorded plus one. If the access operations on the page element include multiple different types, the frequency of each type of access operation can be counted separately, which will not be repeated here.

[0080] The number of access users refers to the number of users who initiate access operations on the first page element, which can be obtained by monitoring the number of user attributes in the operation behavior monitoring data. For example, the number of access users can be counted based on the number of user accounts that initiate access operations, which will not be repeated here.

[0081] The number of processing requests can be counted according to the number of times the operation result monitoring data is obtained. The operation result monitoring data is obtained by tracking the processing requests. Therefore, it can be considered that the frequency of sending the processing requests is the same as or similar to the frequency of obtaining the operation result monitoring data.

[0082] The response success rate can be calculated by combining the frequency of successful responses and the number of access operations, and the response failure rate can be calculated by combining the frequency of failed responses and the number of access operations. The frequency of successful responses and the frequency of failed responses can be determined based on the interface status data and the response content data in the operation result monitoring data, which will not be described in detail.

[0083] Among them, the failure reason of the access operation can be obtained based on the operation verification data in the operation behavior monitoring data and the response failure type data in the operation result monitoring data.

[0084] The distribution characteristics of the failure reasons can be obtained by counting the frequency of each type of failure reason. For example, the number of operation failures due to failure of front-end operation verification data and the number of operation failures due to server-side abnormalities can be counted.

[0085] It is worth noting that if the first page element is bound to multiple events, the access operation that triggers each event can be analyzed separately, which will not be repeated here.

[0086] In this embodiment, based on the abstract syntax tree of the page, an automated page tracking operation is implemented. Based on two tracking operations, various data generated by access operations on page elements can be monitored automatically and in a process-based manner, which is conducive to more accurate analysis of access operations on page elements.

[0087] It should be noted that, based on the above steps, Figure 2 As shown, the method also includes:

[0088] Step 209: In response to the viewing operation on the first page element, obtain the result of analyzing the access operation on the first page element.

[0089] Step 210: Visually display on the page the result of analyzing the access operation on the first page element.

[0090] The user who initiates the viewing operation may be the developer of the page or the optimizer of the page. When the execution subject is a terminal device, the terminal device may determine the user's viewing authority based on the user account accessing the page. If the terminal device determines that the user accessing the page has the authority to view the analysis results based on the user account, the analysis results of the access operation on the page element may be displayed to the user based on the user's viewing operation.

[0091] Optionally, the viewing operation may be implemented as a box selection operation on a page element, or a pointer hovering operation on a page element, or a selection operation on a check button bound to a page element, etc., which is not limited in this embodiment.

[0092] In some scenarios, in order to improve the display effect, the viewing operation can be implemented as a hover operation of the mouse pointer on the page element. For example, for a browser, the page element on which the mouse pointer is hovering can be selected based on the hover selector. When the mouse pointer hovers over a certain page element, it can be considered that the user wants to view the analysis result corresponding to the page element. Next, the result of the analysis of the access operation on the page element can be obtained according to the identifier of the page element and displayed.

[0093] Optionally, the analysis results of the access operations on the page elements can be displayed in a floating window or pop-up window on the page to be more intuitive to the user. For example, after detecting a hover operation on the first page element, a floating window can be displayed on the page near the first page element, and the analysis results of the access operations on the first page element can be displayed in the floating window.

[0094] Optionally, the analysis results can be displayed in the form of charts. The charts may include but are not limited to: column charts (histograms), line charts, pie charts, bar charts, radar charts, word clouds, funnel charts, data maps, waterfall charts, etc. For example, the access success rate, failure rate, and proportion of various error types corresponding to the first page element can be displayed based on a column chart, which will not be repeated here.

[0095] A typical display effect can be as follows Figure 3 As shown. Figure 3 In the example, page element 1, page element 2, and page element 3 are displayed on the page. When the mouse pointer is placed on page element 2, a floating window may pop up on the page, and the analysis results of the access operations on page element 2 are displayed in the floating window through a bar chart.

[0096] Optionally, step 209 and step 210 can be implemented by a browser plug-in or an application plug-in with the assistance of a chart rendering tool. The browser plug-in or application plug-in can obtain the analysis results of the access operation on the viewed page element when it is determined that the user accessing the page has the authority to view the analysis results, call the chart rendering tool to draw the analysis results, and display the analysis results on the page where the page element is located. Optionally, the rendering tool can be a Bizcharts tool (an open source software that provides a tool for rendering multiple types of charts) or other optional chart rendering tools, which is not limited in this embodiment.

[0097] In this embodiment, according to the viewing operation of the user on the page element, the analysis result of the access operation on the page element is displayed in a visual manner on the page, which is more intuitive and convenient for the user to view.

[0098] Figure 4 is a flow chart of a page operation analysis method provided by another exemplary embodiment of the present application. Figure 4 As shown, the method includes:

[0099] Step 401: display a page, which includes a first page element.

[0100] Step 402: respond to the access operation on the first page element, and track the event triggered by the access operation according to the first tracking point deployment information to obtain operation behavior monitoring data.

[0101] Step 403: Send a processing request to the server according to the event triggered by the access operation.

[0102] Step 404: Track the processing request according to the second tracking point deployment information to obtain the server's response result to the processing request as operation result monitoring data.

[0103] Step 405: Analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

[0104] The optional implementation methods of the above steps can refer to the records of the above embodiments and will not be described in detail here.

[0105] In this embodiment, after an access operation on a page element is detected, various data generated by the access operation can be automatically and process-based monitored in multiple links based on the first tracking point deployment information and the second tracking point deployment information, which is conducive to more accurate analysis of the access operations on the page elements.

[0106] In addition to the page operation analysis methods provided in the aforementioned embodiments, an embodiment of the present application also provides a tracking method, which includes: obtaining an abstract syntax tree corresponding to the page. According to the abstract syntax tree, at least one event associated with the page is determined. In the event handler corresponding to each of the at least one event, first tracking deployment information and second tracking deployment information are added; wherein the first tracking deployment information is used to track the event when the event is triggered, and the second tracking deployment information is used to track the processing request corresponding to the event.

[0107] This method can be implemented based on a browser plug-in or an application plug-in. When a page is opened in a browser or an application, the plug-in in the browser or application can automatically analyze the AST corresponding to the page, and automatically perform two tracking points for each event in the code that can be triggered by an operation based on the AST.

[0108] Among them, the first burial point deployment information and the second burial point deployment information can be configured according to actual needs, and this embodiment does not limit it.

[0109] In this embodiment, based on the abstract syntax tree of the page, automated page tracking operations are implemented, reducing labor costs; based on two tracking operations, various data generated by access operations on page elements can be monitored automatically and in a process-based manner, which is conducive to more accurate analysis of access operations on page elements.

[0110] It should be noted that the execution subject of each step of the method provided in the above embodiment can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 201 to 204 can be device A; for another example, the execution subject of steps 201 and 202 can be device A, and the execution subject of step 203 can be device B; and so on.

[0111] In addition, in some of the processes described in the above embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this article or executed in parallel, and the sequence numbers of the operations, such as 201, 202, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., do not represent the order of precedence, and do not limit the "first" and "second" to be different types.

[0112] The above and following embodiments of the present application can be applied to page operation analysis in various application scenarios.

[0113] In some scenarios, the web page provided by the browser can be analyzed based on the page operation analysis method provided in the embodiment of the present application. Among them, the web page can be implemented as an e-commerce web page, a web page provided by a cloud computing platform, a game web page, a news portal web page, a video web page, a music web page, an education web page, etc., which is not limited in this embodiment. By performing operation analysis on the web page, the design rationality and functional perfection of the web page can be analyzed; or, the content of interest to the user can be mined, and the information displayed on the web page can be adjusted according to the content of interest to the user. Taking an e-commerce web page as an example, the page elements on the e-commerce web page may include multiple category tags corresponding to multiple commodity categories. By counting the number of visits to multiple category tags and calculating the proportion of the number of visits to each category tag, the user's interest in multiple commodity categories can be analyzed.

[0114] Taking an education webpage as an example, the page elements on the education webpage can be implemented as links to various courses. The link may point to the course resources provided by this website or to the course resources provided by other websites. After each link is clicked, the click result is tracked and the error reason for the failure to successfully respond to the click operation is obtained. The fault of this website or other websites can be located and analyzed to further optimize the webpage function.

[0115] In other scenarios, an operation analysis can be performed on the application page provided by the application based on the page operation analysis method provided in the embodiment of the present application. Among them, the application can be implemented as an application running on a computer, or as an application running on a smart terminal. Among them, the smart terminal may include a smart phone, a smart wearable device, a smart home device, etc., which is not limited in this embodiment. By performing an operation analysis on the application page, the design rationality and functional perfection of the application page can be analyzed; or, the content of interest to the user can be mined, and the information displayed on the application page can be adjusted according to the content of interest to the user.

[0116] The above application can be a client software provided by multiple different fields that can interact with users and provide set services to users. The different fields include but are not limited to: e-commerce field, cloud computing field, game field, news field, video field, music field, education field, live broadcast field, etc. Taking the application implemented as a mobile phone news client as an example, the page elements on the news client may include multiple news field tags. In the process of users using the news client, the number of clicks on multiple news field tags and the number of click results successfully returned are counted, and the success rate of the news client successfully displaying news content in different fields can be calculated, and then the access stability of the news client can be analyzed.

[0117] The following will take the web page provided by the website as an example to further illustrate the page analysis method provided by this application. Website developers can develop a browser plug-in based on the babel tool. The browser plug-in can be based on the AST of the web page, and perform two tracking points for each event on the web page that can be triggered by an access operation, that is, tracking points before the request and tracking points after the request, and set a logID for each event.

[0118] When a user initiates an access operation to a page element while browsing a web page, the pre-request embedding point can perform operation statistics or capture exceptions (such as incomplete user information, inability to operate due to dependency issues on the previous interface, etc.). After sending the processing request, the post-request embedding point can obtain the interface return information. Based on the data obtained by the pre-request embedding point and the post-request embedding point and the logID, the response success rate, failure rate, and proportion of various error types of access operations on page elements can be counted. Website developers can also develop a dynamic display plug-in based on the interface provided by the browser. When developing or maintaining related user access pages for a website, you can log in to the access account and move the mouse pointer to the target page element you want to view. When the dynamic display plug-in determines that the visitor has the authority to view the analysis results based on the access account, it can obtain the results of the analysis of the access operation on the target page element, render the result through the icon rendering tool, and display the rendered result through a floating window on the web page.

[0119] Figure 5 is a schematic diagram of the structure of a page operation analysis device provided by an exemplary embodiment of the present application. Figure 5 As shown, the device includes: a display module 501, a first monitoring module 502, a request module 503, a second monitoring module 504 and an analysis module 505.

[0120] The display module 501 is used to display a page, wherein the page includes a first page element.

[0121] The first monitoring module 502 is used to: respond to an access operation on the first page element and obtain operation behavior monitoring data corresponding to the access operation.

[0122] The request module 503 is used to send a processing request to the server according to the event triggered by the access operation.

[0123] The second monitoring module 504 is used to monitor the response result of the server to the processing request and obtain operation result monitoring data.

[0124] The analysis module 505 is used to analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

[0125] Further optionally, the display module 501 is also used to: respond to a viewing operation on the first page element, obtain a result of analyzing an access operation on the first page element; and visually display the result of analyzing the access operation on the first page element on the page.

[0126] Further optionally, when obtaining the operation behavior monitoring data corresponding to the access operation, the first monitoring module 502 is specifically used to: track the event triggered by the access operation according to the first tracking point deployment information; and obtain the tracked data associated with the event as the operation behavior monitoring data.

[0127] Further optionally, when the second monitoring module 504 monitors the response result of the server to the processing request and obtains the operation result monitoring data, it is specifically used to: track the processing request according to the second tracking point deployment information; obtain the tracked response result of the server to the processing request as the operation result monitoring data.

[0128] Further optionally, the device also includes a burying point module 506.

[0129] Among them, the tracking point module 506 is used to: obtain the abstract syntax tree corresponding to the page; determine at least one event associated with the page according to the abstract syntax tree; wherein each event can be triggered by an access operation on the page element to which it is bound; in the event handler corresponding to each of the at least one event, add the first tracking point deployment information and the second tracking point deployment information.

[0130] Further optionally, when the tracking point module 506 adds the first tracking point deployment information and the second tracking point deployment information in the event processor corresponding to the at least one event, it is specifically used to: determine a target code in the event processor corresponding to the first event in the at least one event; the target code is used to send a corresponding processing request to the server when the first event is triggered; add the code corresponding to the first tracking point deployment information before the target code, and add the code corresponding to the second tracking point deployment information after the target code.

[0131] Further optionally, the operation behavior monitoring data includes: at least one of action attribute data, user attribute data, operation object attribute data and operation verification data; the operation result monitoring data includes: at least one of interface status data, response content data and response failure type data.

[0132] Further optionally, when analyzing the access operations on the first page element, the analysis module 505 is specifically used to: analyze the number of access operations, the number of access users, the number of processed requests, the response success rate of the access operations, the response failure rate of the access operations, the failure reasons of the access operations and / or the distribution characteristics of the failure reasons.

[0133] In this embodiment, after an access operation on a page element is detected, the operation behavior monitoring data corresponding to the access operation is obtained, and after a processing request is sent to the server, the response result of the server to the processing request is monitored to obtain the operation result monitoring data; based on the operation behavior monitoring data and the operation result monitoring data, a variety of data generated by the access operation on the page element can be more comprehensively obtained, and functional-level monitoring of the access operation on the page element is realized, which is conducive to more accurate analysis of the access operation on the page element.

[0134] Figure 5 Each module in the page operation analysis device shown can also execute the page operation analysis method according to the following logic:

[0135] The display module 501 is used to: display a page, and the page includes a first page element. The first monitoring module 502 is used to: respond to the access operation on the first page element, and track the event triggered by the access operation according to the first tracking point deployment information to obtain operation behavior monitoring data. The request module 503 is used to: send a processing request to the server according to the event triggered by the access operation. The second monitoring module 504 is used to: track the processing request according to the second tracking point deployment information to obtain the response result of the server to the processing request as operation result monitoring data. The analysis module 505 is used to: analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

[0136] In this embodiment, after an access operation on a page element is detected, various data generated by the access operation can be automatically and process-based monitored in multiple links based on the first tracking point deployment information and the second tracking point deployment information, which is conducive to more accurate analysis of the access operations on the page elements.

[0137] Figure 6 A schematic diagram of a structure of a point embedding device provided by an exemplary embodiment of the present application is shown in FIG. Figure 6 The device shown includes: a page analysis module 601 and a tracking point module 602.

[0138] The page analysis module 601 is used to: obtain an abstract syntax tree corresponding to a page; and determine at least one event associated with the page according to the abstract syntax tree.

[0139] The tracking point module 602 is used to: add first tracking point deployment information and second tracking point deployment information in the event processor corresponding to each of the at least one event; wherein the first tracking point deployment information is used to track the corresponding event when the corresponding event is triggered, and the second tracking point deployment information is used to track the processing request corresponding to the corresponding event.

[0140] The tracking device provided in this embodiment can be packaged as an automated tracking tool and provided to third-party users for use, which will not be described in detail.

[0141] In this embodiment, based on the abstract syntax tree of the page, automated page tracking operations are implemented, reducing labor costs; based on two tracking operations, various data generated by access operations on page elements can be monitored automatically and in a process-based manner, which is conducive to more accurate analysis of access operations on page elements.

[0142] Figure 7 is a schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present application, such as Figure 7 As shown, the electronic device includes: a memory 701 and a processor 702.

[0143] The memory 701 is used to store computer programs and can be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phone book data, messages, pictures, videos, etc.

[0144] Among them, the memory 701 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0145] When the electronic device is applied to the page analysis operation, it may also include: a communication component 703 and a display component 704.

[0146] Among them, the processor 702 is coupled with the memory 701, and is used to execute the computer program in the memory 701, so as to: display a page through the display component 704, and the page includes a first page element; respond to an access operation on the first page element, and obtain operation behavior monitoring data corresponding to the access operation; according to the event triggered by the access operation, send a processing request to the server through the communication component 703; monitor the response result of the server to the processing request to obtain operation result monitoring data; analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

[0147] Further optionally, the processor 702 is also used to: respond to a viewing operation on the first page element, obtain a result of analyzing an access operation on the first page element; and visually display the result of analyzing the access operation on the first page element on the page through the display component 704.

[0148] Further optionally, when the processor 702 obtains the operation behavior monitoring data corresponding to the access operation, it is specifically used to: track the event triggered by the access operation according to the first tracking point deployment information; and obtain the tracked data associated with the event as the operation behavior monitoring data.

[0149] Further optionally, when the processor 702 monitors the response result of the server to the processing request and obtains the operation result monitoring data, it is specifically used to: track the processing request according to the second tracking point deployment information; obtain the tracked response result of the server to the processing request as the operation result monitoring data.

[0150] Further optionally, the processor 702 is also used to: obtain an abstract syntax tree corresponding to the page; determine at least one event associated with the page based on the abstract syntax tree; wherein each event can be triggered by an access operation on the page element to which it is bound; and add the first burying point deployment information and the second burying point deployment information to the event handler corresponding to each of the at least one event.

[0151] Further optionally, when the processor 702 adds the first burying point deployment information and the second burying point deployment information in the event processor corresponding to the at least one event, it is specifically used to: determine a target code in the event processor corresponding to the first event in the at least one event; the target code is used to send a corresponding processing request to the server when the first event is triggered; add the code corresponding to the first burying point deployment information before the target code, and add the code corresponding to the second burying point deployment information after the target code.

[0152] Further optionally, the operation behavior monitoring data includes: at least one of action attribute data, user attribute data, operation object attribute data and operation verification data; the operation result monitoring data includes: at least one of interface status data, response content data and response failure type data.

[0153] Further optionally, when analyzing the access operations on the first page element, the processor 702 is specifically used to: analyze the number of access operations, the number of access users, the number of processed requests, the response success rate of the access operations, the response failure rate of the access operations, the failure reasons of the access operations and / or the distribution characteristics of the failure reasons.

[0154] Further, if Figure 7 As shown, the electronic device also includes: a power supply component 705 and other components. Figure 7 Only some components are shown schematically, which does not mean that the electronic device only includes Figure 7 Components shown.

[0155] Among them, the communication component 703 is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G or 5G, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component can be implemented based on near field communication (NFC) technology, radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0156] The display component 704 includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0157] The power supply component 705 provides power to various components of the device where the power supply component is located. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device where the power supply component is located.

[0158] In this embodiment, after an access operation on a page element is detected, the operation behavior monitoring data corresponding to the access operation is obtained, and after a processing request is sent to the server, the response result of the server to the processing request is monitored to obtain the operation result monitoring data; based on the operation behavior monitoring data and the operation result monitoring data, a variety of data generated by the access operation on the page element can be more comprehensively obtained, and functional-level monitoring of the access operation on the page element is realized, which is conducive to more accurate analysis of the access operation on the page element.

[0159] In addition to the execution logic described in the above embodiments, Figure 7 The electronic device shown can also execute the page analysis method according to the following logic: the processor 702 displays a page through the display component 704, and the page includes a first page element; in response to an access operation on the first page element, the event triggered by the access operation is tracked according to the first embedding point deployment information to obtain operation behavior monitoring data; according to the event triggered by the access operation, a processing request is sent to the server through the communication component 703; according to the second embedding point deployment information, the processing request is tracked to obtain the response result of the server to the processing request as the operation result monitoring data; according to the operation behavior monitoring data and the operation result monitoring data, the access operation on the first page element is analyzed.

[0160] In addition to the execution logic recorded in the aforementioned embodiments, an electronic device including a memory and a processor may also execute a page tracking method according to the following logic: the processor obtains an abstract syntax tree corresponding to the page; based on the abstract syntax tree, determines at least one event associated with the page; in the event handler corresponding to each of the at least one event, adds first tracking deployment information and second tracking deployment information; wherein, the first tracking deployment information is used to track the event when the event is triggered, and the second tracking deployment information is used to track the processing request corresponding to the event.

[0161] Accordingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, which, when executed, can implement each step that can be performed by an electronic device in the above method embodiment.

[0162] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0163] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0164] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0165] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0166] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0167] Memory may include non-permanent storage in a computer-readable medium, in the form of random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0168] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0169] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0170] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A page operation analysis method, characterized in that: include: Displaying a page, the page including a first page element; In response to an access operation on the first page element, obtaining operation behavior monitoring data corresponding to the access operation, the operation behavior monitoring data including action attribute data, the action attribute data including an operation frequency of the access operation that triggers an event corresponding to the access operation; Sending a processing request to a server according to an event triggered by the access operation, and monitoring a response result of the server to the processing request to obtain operation result monitoring data, wherein the operation result monitoring data includes response content data indicating whether the server successfully processes the processing request; Analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data; Among them, analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data includes: analyzing the response success rate and / or response failure rate of the access operation on the first page element.

2. The method according to claim 1, characterized in that Also includes: In response to a viewing operation on the first page element, obtaining a result of analyzing the access operation on the first page element; The result of analyzing the access operation on the first page element is visually displayed on the page.

3. The method according to claim 1, characterized in that Obtaining operation behavior monitoring data corresponding to the access operation, including: Tracking the event triggered by the access operation according to the first tracking point deployment information; The tracked data associated with the event is obtained as the operation behavior monitoring data.

4. The method according to claim 3, characterized in that Monitoring the response result of the server to the processing request to obtain operation result monitoring data includes: Tracking the processing request according to the second tracking point deployment information; The tracked response result of the server to the processing request is obtained as the operation result monitoring data.

5. The method according to claim 4, characterized in that Also includes: Obtaining an abstract syntax tree corresponding to the page; Determine at least one event associated with the page according to the abstract syntax tree; wherein each event may be triggered by an access operation on a page element to which it is bound; In the event handler corresponding to each of the at least one event, add the first burying point deployment information and the second burying point deployment information.

6. The method according to claim 5, characterized in that In the event processor corresponding to the at least one event, adding the first burying point deployment information and the second burying point deployment information includes: For a first event among the at least one event, determining a target code in an event processor corresponding to the first event; the target code is used to send a corresponding processing request to the server when the first event is triggered; Add the code corresponding to the first burying point deployment information before the target code, and add the code corresponding to the second burying point deployment information after the target code.

7. The method according to any one of claims 1 to 6, characterized in that: The operation behavior monitoring data also includes: at least one of user attribute data, operation object attribute data and operation verification data; The operation result monitoring data also includes at least one of interface status data and response failure type data.

8. The method according to claim 7, characterized in that Analyzing the access operation on the first page element also includes: Analyze the number of access operations, the number of access users, the number of processed requests, the failure reasons of the access operations and / or the distribution characteristics of the failure reasons on the first page element.

9. A page operation analysis method, characterized in that: include: Displaying a page, the page including a first page element; In response to an access operation on the first page element, an event triggered by the access operation is tracked according to the first tracking point deployment information to obtain operation behavior monitoring data, wherein the operation behavior monitoring data includes action attribute data, and the action attribute data includes an operation frequency of the access operation that triggers the event corresponding to the access operation; Sending a processing request to a server according to an event triggered by the access operation; According to the second tracking point deployment information, the processing request is tracked to obtain a response result of the server to the processing request as operation result monitoring data, wherein the operation result monitoring data includes response content data indicating whether the server successfully processes the processing request; Analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data; Among them, analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data includes: analyzing the response success rate and / or the response failure rate of the access operation on the first page element.

10. A method for embedding a point, characterized in that: include: Get the abstract syntax tree corresponding to the page; Determining at least one event associated with the page according to the abstract syntax tree; In the event processor corresponding to each of the at least one event, add the first burying point deployment information and the second burying point deployment information; The first tracking point deployment information is used to track the corresponding event when the corresponding event is triggered, so as to obtain the tracked data associated with the corresponding event as the operation behavior monitoring data, wherein the operation behavior monitoring data includes action attribute data, and the action attribute data includes the operation frequency of the access operation that triggers the corresponding event of the access operation; The second tracking point deployment information is used to track the processing request corresponding to the event to which it belongs, so as to obtain the response result of the tracked server to the processing request as operation result monitoring data. The operation result monitoring data includes response content data indicating whether the server has successfully processed the processing request, so as to analyze the response success rate and / or response failure rate of the access operation on the page element according to the operation result monitoring data.

11. A page operation analysis device, characterized in that: include: A display module, used to: display a page, wherein the page includes a first page element; A first monitoring module is used to: respond to an access operation on the first page element, obtain operation behavior monitoring data corresponding to the access operation, the operation behavior monitoring data includes action attribute data, and the action attribute data includes an operation frequency of the access operation that triggers an event corresponding to the access operation; A request module, used to: send a processing request to a server according to an event triggered by the access operation; A second monitoring module is used to: monitor the response result of the server to the processing request to obtain operation result monitoring data, wherein the operation result monitoring data includes response content data indicating whether the server successfully processes the processing request; An analysis module, configured to analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data; Among them, analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data includes: analyzing the response success rate and / or the response failure rate of the access operation on the first page element.

12. The device according to claim 11, characterized in that Also includes: A tracking point module is used to: obtain an abstract syntax tree corresponding to the page; determine at least one event associated with the page based on the abstract syntax tree; wherein each event can be triggered by an access operation on the page element to which it is bound; and add first tracking point deployment information and second tracking point deployment information to the event handler corresponding to each of the at least one event.

13. The device according to claim 11 or 12, characterized in that The display module is also used to: respond to the viewing operation on the first page element, obtain the result of analyzing the access operation on the first page element; and visually display the result of analyzing the access operation on the first page element on the page.

14. A page operation analysis device, characterized in that: include: A display module, used to: display a page, wherein the page includes a first page element; A first monitoring module is used to: respond to an access operation on the first page element, and track an event triggered by the access operation according to the first tracking point deployment information to obtain operation behavior monitoring data, wherein the operation behavior monitoring data includes action attribute data, and the action attribute data includes an operation frequency of the access operation that triggers the event corresponding to the access operation; A request module, used to: send a processing request to a server according to an event triggered by the access operation; A second monitoring module is used to: track the processing request according to the second tracking point deployment information to obtain a response result of the server to the processing request as operation result monitoring data, wherein the operation result monitoring data includes response content data indicating whether the server successfully processes the processing request; An analysis module, configured to analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data; Among them, analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data includes: analyzing the response success rate and / or the response failure rate of the access operation on the first page element.

15. A point embedding device, characterized in that: include: The page analysis module is used to: obtain the abstract syntax tree corresponding to the page; Determining at least one event associated with the page according to the abstract syntax tree; A tracking point module, used to: add first tracking point deployment information and second tracking point deployment information in the event processor corresponding to each of the at least one event; wherein the first tracking point deployment information is used to track the corresponding event when the corresponding event is triggered, so as to obtain the tracked data associated with the event as operation behavior monitoring data, the operation behavior monitoring data includes action attribute data, and the action attribute data includes the operation frequency of the access operation that triggers the event corresponding to the access operation; The second tracking point deployment information is used to track the processing request corresponding to the event to which it belongs, so as to obtain the response result of the tracked server to the processing request as operation result monitoring data. The operation result monitoring data includes response content data indicating whether the server successfully processes the processing request, so as to analyze the response success rate and / or response failure rate of the access operation on the page element according to the operation result monitoring data.

16. An electronic device, characterized in that: include: Memory and processor; The memory is used to store one or more computer instructions; The processor is used to execute the one or more computer instructions to: execute the page operation analysis method described in any one of claims 1-9 or the tracking method described in claim 10.

17. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, it can implement the page operation analysis method described in any one of claims 1 to 10 or the tracking method described in claim 10.

Images