CN113378036A

CN113378036A - Page operation analysis and point burying method, device, equipment and storage medium

Info

Publication number: CN113378036A
Application number: CN202010163123.2A
Authority: CN
Inventors: 郭婧瑶
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2020-03-10
Filing date: 2020-03-10
Publication date: 2021-09-10

Abstract

The embodiment of the application provides a page operation analysis method, a page operation analysis device, a page operation point burying method, a page operation point burying device and a storage medium. In the page operation analysis method, after detecting access operation aiming at page elements, acquiring operation behavior monitoring data corresponding to the access operation, and after sending a processing request to a server, monitoring a response result of the server to the processing request to obtain operation result monitoring data; based on the operation behavior monitoring data and the operation result monitoring data, various data generated by the access operation on the page element can be acquired more comprehensively, the function level monitoring of the access operation on the page element is realized, and the analysis of the access operation on the page element is facilitated more accurately.

Description

Page operation analysis and point burying method, device, equipment and storage medium

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method, an apparatus, a device, and a storage medium for page operation analysis and point burying.

Background

In some scenarios, it is desirable to analyze access operations on a page to mine user behavior on the page. Based on the mining result of the user behavior, the design of the page can be optimized or the business function borne by the page can be optimized.

The page analysis method provided by the prior art cannot accurately analyze access operations on different page elements on a page. Therefore, a new solution is yet to be proposed.

Disclosure of Invention

Aspects of the present disclosure provide a page operation analysis method, a page operation embedding method, a page operation analysis device, a page operation embedding device, and a storage medium, which are used to accurately analyze an access operation on a page element.

The embodiment of the application provides a page operation analysis method, which comprises the following steps: displaying a page, wherein the page comprises a first page element; responding to the access operation on the first page element, and acquiring operation behavior monitoring data corresponding to the access operation; sending a processing request to a server according to the event triggered by the access operation, and monitoring the response result of the server to the processing request to obtain operation result monitoring data; and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

The embodiment of the present application further provides a page operation analysis method, including: displaying a page, wherein the page comprises a first page element; responding to the access operation on the first page element, and tracking an event triggered by the access operation according to first embedded point deployment information to acquire 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 buried point deployment information to obtain a response result of the server to the processing request as operation result monitoring data; and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

The embodiment of the present application further provides a point burying method, including: acquiring an abstract syntax tree corresponding to a page; determining at least one event associated with the page according to the abstract syntax tree; adding first buried point deployment information and second buried point deployment information in an event processor corresponding to each event; the first buried point deployment information is used for tracking the event when the event is triggered, and the second buried point deployment information is used for tracking the processing request corresponding to the event.

An embodiment of the present application further provides a page operation analysis device, including: a display module for: displaying a page, wherein the page comprises a first page element; a first monitoring module to: responding to the access operation on the first page element, and acquiring operation behavior monitoring data corresponding to the access operation; a request module to: sending a processing request to a server according to the event triggered by the access operation; a second monitoring module to: monitoring a response result of the server to the processing request to obtain operation result monitoring data; an analysis module to: and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

An embodiment of the present application further provides a page operation analysis device, including: a display module for: displaying a page, wherein the page comprises a first page element; a first monitoring module to: responding to the access operation on the first page element, and tracking an event triggered by the access operation according to first embedded point deployment information to acquire operation behavior monitoring data; a request module to: sending a processing request to a server according to the event triggered by the access operation; a second monitoring module to: tracking the processing request according to second buried point deployment information to obtain a response result of the server to the processing request as operation result monitoring data; an analysis module to: and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

The embodiment of the present application further provides a buried point device, including: a page analysis module to: acquiring an abstract syntax tree corresponding to a page; determining at least one event associated with the page according to the abstract syntax tree; a buried point module for: adding first buried point deployment information and second buried point deployment information in an event processor corresponding to each event; the first buried point deployment information is used for tracking the event when the event is triggered, and the second buried point deployment information is used for tracking the processing request corresponding to the event.

An embodiment of the present application further provides an electronic device, including: a memory and a processor; the memory is to store one or more computer instructions; the processor is to execute the one or more computer instructions to: and executing the page operation analysis method provided by the embodiment of the application or the point burying method provided by the embodiment of the application.

The embodiment of the present application further provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the page operation analysis method provided in the embodiment of the present application or the embedding method provided in the embodiment of the present application can be implemented.

In the embodiment of the application, after the access operation aiming at the page element is detected, the operation behavior monitoring data corresponding to the access operation is obtained, and after the 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, various data generated by the access operation on the page element can be acquired more comprehensively, the function level monitoring of the access operation on the page element is realized, and the analysis of the access operation on the page element is facilitated more accurately.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

FIG. 1 is a flowchart illustrating a method for analyzing page operations according to an exemplary embodiment of the present application;

FIG. 2 is a schematic flowchart of a page operation analysis method according to another exemplary embodiment of the present application;

FIG. 3 is a schematic illustration showing a result of a page operation analysis provided by an exemplary embodiment of the present application;

FIG. 4 is a flowchart illustrating a method for analyzing page operations according to another exemplary embodiment of the present application;

FIG. 5 is a schematic structural diagram of a page operation analysis apparatus according to an exemplary embodiment of the present application;

FIG. 6 is a schematic structural diagram of a buried point device provided in an exemplary embodiment of the present application;

fig. 7 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In some common page operation analysis methods, access operations on a page are usually analyzed by manually analyzing a backend interface log, or an exception capture statement (e.g., try/catch statement for capturing a web page error) is used in a front end to monitor the access operations on page elements. These conventional page operation analysis methods cannot accurately analyze access operations on different page elements on a page.

In view of the above technical problems, in some embodiments of the present application, a solution is provided, and the technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

Fig. 1 is a schematic flowchart of a page operation analysis method according to an exemplary embodiment of the present application, and as shown in fig. 1, the method includes:

step 101, displaying a page, wherein the page comprises a first page element.

And 102, responding to the access operation on the first page element, and acquiring operation behavior monitoring data corresponding to the access operation.

Step 103, sending a processing request to the server according to the event triggered by the access operation, and monitoring a response result of the server to the processing request to obtain operation result monitoring data.

And 104, analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

The execution main body of this embodiment may be a terminal device, and the terminal device may be implemented as a computer, a mobile phone, a tablet computer, and the like, which is not limited in this embodiment. The page may include any page provided by the terminal device and used for displaying information, for example, a web page provided by a browser installed on a computer, an application page provided by an application of the mobile phone terminal, and the like, which is not limited in this embodiment.

The page may include one or more page elements, such as control elements, e.g., buttons, edit boxes, and hyperlink elements, e.g., text hyperlinks, picture hyperlinks, and the like. The page element may provide a variety of different operational portals to the user to facilitate the user accessing and using the functionality provided by the page based on the different operational portals. For example, when the page elements are implemented as button controls such as "edit," "delete," "save," and the like, the user can access and use the functions of editing data, deleting data, and saving data provided by the page based on the button controls. For another example, when the page element is implemented as a text hyperlink element or an image hyperlink element, the user may access other pages pointed by the link based on the hyperlink element, and the description is omitted.

The user who initiates the access operation on the page element is usually a service object of the page information. For example, a user who makes the terminal device access an application page, a user who accesses a web page using a browser, and the like may be included. In some other scenarios, the user may also be implemented as a user for testing the page development effect or a computer program for simulating page testing, which is not limited in this embodiment.

An access operation on a page element refers to some detectable operation initiated by a user on the page element. The access operation may be implemented as various different types of operations, for example, a click operation, an input operation, a drag operation, a long-press operation, and the like for a page element, which is not limited in this embodiment. The first page element refers to any page element on the page; it is defined herein as "first" only for convenience of description and distinction.

When the 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 operational 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, to facilitate analysis of the user's access operational behavior.

Wherein each page element can bind one or more events, and each event corresponds to an event listener and an event handler (event handler). The event listener is used for monitoring the access operation on the page element to detect whether the event is triggered by the access operation on the page element. The event processor is used for executing corresponding event processing operation when the event is triggered.

In some scenarios, the event handler needs to complete the event handling operations with the support of the server, e.g., the server is required to provide data support and computing power support. When the access operation occurs on the first page element, a certain event bound by the first page element is triggered. If the processing procedure of the event needs to interact with the server, the event processor corresponding to the event can send a processing request corresponding to the event to the server. For example, a user clicking on a "delete" button on a page triggers a delete event for particular data that is stored on the server. Then the event handler for the delete event may send a data delete request to the server to implement the button-bound data delete function.

After sending the processing request to the server, the terminal device may monitor a response result of the server to the processing request, and obtain operation result monitoring data according to the response result. The operation result monitoring data is used for recording whether the event triggered by the access operation is successfully processed, that is, whether the access operation of the user on the page element is successfully responded.

The process of acquiring the operation behavior monitoring data and the operation result monitoring data realizes monitoring of the access operation on the page elements from different links, and more completely captures various data generated by the access operation. Based on the operation behavior monitoring data and the operation result monitoring data, the access operation on the page element can be analyzed.

In this embodiment, after an access operation for a page element is detected, operation behavior monitoring data corresponding to the access operation is acquired, and after a processing request is sent to a server, a response result of the server to the processing request is monitored to obtain operation result monitoring data; based on the operation behavior monitoring data and the operation result monitoring data, various data generated by the access operation on the page element can be acquired more comprehensively, the function level monitoring of the access operation on the page element is realized, and the analysis of the access operation on the page element is facilitated more accurately.

It is worth noting that in the above and below embodiments of the present application, the operation behavior monitoring data and the operation result monitoring data generated by the access operation on the page element can be obtained by performing multiple times of embedding on the access operation on the page.

The buried point, also called event tracing (event tracing), is to add an information monitoring point in a specific processing link, and the information monitoring point can capture specified information under the triggering of a specific event or a specific operation. The page operation analysis method provided in the embodiment of the present application will be further described below with reference to a buried point operation.

Fig. 2 is a schematic flowchart of a page operation analysis method according to another exemplary embodiment of the present application, and as shown in fig. 2, the method includes:

step 201, obtaining an abstract syntax tree corresponding to the page.

Step 202, determining at least one event associated with the page according to the abstract syntax tree; where each event may be triggered by an access operation on the page element to which it is bound.

Step 203, adding the first buried point deployment information and the second buried point deployment information in the event processor corresponding to each of the at least one event.

And step 204, displaying the page, and displaying at least one page element on the page.

Step 205, responding to the access operation on the first page element, and tracking an event triggered by the access operation according to the first buried point deployment information to obtain operation behavior monitoring data.

And step 206, sending a processing request to the server according to the event triggered by the access operation.

And step 207, tracking the processing request according to the second buried point deployment information to acquire operation result monitoring data.

And 208, analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

In step 201, an Abstract Syntax Tree (AST) is an Abstract representation of the source code Syntax structure. It expresses the grammar structure of the source code by a tree structure, and one node on the tree structure expresses one structure in the source code.

Alternatively, if the page is developed by using JavaScript (JS), a Babel tool may be used to obtain the abstract syntax tree of the page. The Babel tool is a JS editor and can convert a source language. For example, the Babel tool may convert the JS source code corresponding to the page into the AST according to the babylon library, which is not described again.

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

For example, a page button may bind a single click event as well as a long press event; wherein, the single-click event can be triggered by single-click operation on the page button, and the long-press event can be triggered by long-press operation on the page button. For another example, a page picture may bind a double-click event and a drag event; the double-click event can be triggered by double-click operation on the page picture, and the drag event can be triggered by drag operation on the page picture.

In step 203, the event handler is configured to execute a set event processing operation when an event bound to the page element is triggered by an access operation on the page element, so as to implement a service function carried by the page element.

To complete the monitoring flow of the access operation, two times of embedding can be carried out in the event processor so as to form two information monitoring points in the event processor. Alternatively, first and second buried point deployment information may be added in each event handler. The first embedded point deployment information is used for tracking the events when the events to which the first embedded point deployment information belongs are triggered; the second buried point deployment information is used for tracking the processing request corresponding to the event to which the second buried point deployment information belongs.

The two-time burial point operation will be exemplified below by taking any one of the at least one event as an example. For convenience of description, any one event is described as a first event.

Optionally, the code corresponding to the event handler of the first event may be determined in the source code corresponding to the page. Next, object code may be determined in the corresponding code of the event handler, the object code being used to send a corresponding processing request to the server when the first event is triggered. Then, a code corresponding to the first buried point deployment information may be added before the object code, and a code corresponding to the second buried point deployment information may be added after the object code. Based on the above operation, 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.

Alternatively, the above steps 201 to 203 can be implemented by a browser plug-in or an application plug-in developed based on a Babel tool. When the page is opened in the browser or the application program, the plug-in can automatically analyze AST corresponding to the page and automatically perform two times of embedding points for each event which can be triggered by operation in the code according to the AST. Furthermore, automatic point burying operation based on a browser or an application program is achieved, and labor cost is reduced.

In step 204, the page may optionally be presented when the user accesses the page through the terminal device. Alternatively, the page is presented upon the triggering of a particular system event.

In step 205, the first page element may be any page element in the at least one page element, which is not limited in this embodiment. An access operation on a first page element may trigger an event to which the first page element is bound. Based on the description of the embedding step, the event processor corresponding to the triggered event comprises two information monitoring points, namely: the information monitoring points correspond to the first buried point deployment information, and the information monitoring points correspond to the second buried point deployment information.

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

The action attribute data may include the operation frequency and the operation type of the access operation that triggered the event. The user attribute data may include an identification of the user (e.g., user account, etc.) that initiated the access operation. The operation object data may include related information of the accessed page element, such as an identifier of the page element, a type of the page element, a business function corresponding to the page element, and the like. The operation verification data can comprise configuration information verification data, interface verification data, JS form verification data and the like. And will not be described in detail.

It should be appreciated that the information monitoring site can be instructed by personalizing the first site deployment information to obtain which operational behavior monitoring data to obtain during the course of the trace event. The above listed data are for illustrative purposes only, and the present embodiment includes but is not limited thereto.

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 with a plurality of events. When the types of the events triggered by the access operation are different, the processing requests sent to the server are also different.

For example, a button on the page binds a single click event and a double click event. Wherein, the single-click event is used for realizing the M function, and the double-click event is used for realizing the N function. If the access operation on the button is a click operation, and the click operation triggers a click event, a processing request corresponding to the M function can be sent to the server; if the access operation is a double-click operation which can trigger a double-click event, a processing request corresponding to the N function can be sent to the server.

In step 207, after the processing request is sent to the server, the information monitoring point corresponding to the second embedded point deployment information is activated, and the processing request can be tracked according to the second embedded point deployment information. In the process of tracking and processing the request, the information monitoring point can capture the response result of the server to the processing request to obtain the operation result monitoring data.

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

The interface comprises an interface between the event processor and a communication component on the terminal equipment, an interface adopted for communication between the terminal equipment and the server and the like. The interface state data is data obtained by monitoring the working state of the interface, and may include interface abnormal data, interface normal data, and the like. Based on the interface status data, the reason for the failure of the access operation may be analyzed. For example, in some scenarios, an abnormality occurs in a communication interface between the terminal device and the server, and the server cannot receive the processing request, thereby failing to successfully respond to the access operation on the page element.

The response content refers to the actual content returned by the server according to the processing request. The response content is analyzed, and whether the access operation on the page element cannot be successfully responded due to the server side can be identified. For example, in some scenarios, the interface is not abnormal, the server successfully receives the processing request, but the server side is abnormal, resulting in processing failure, and 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, whether the reason of response failure of the access operation comes from the server side or not can be accurately analyzed.

The response failure type may include an interface abnormal failure type, a server abnormal failure type, or a type of failure caused by other reasons of the terminal device side or the server side, which is not limited in this embodiment.

Based on the two information monitoring points, a series of processes after the access operation occurs on the first page element can be monitored completely. After the operation behavior monitoring data and the operation result monitoring data are obtained, step 208 may be executed to analyze the operation on the first page element.

Alternatively, the data generated by the access operation on the page element within a certain period may be counted to perform the analysis according to the statistical period. The specific period may be one day, three days, or one week. Or, the specific period may be flexibly adjusted according to the content of the information published on the page, which is not limited in this embodiment.

Optionally, a data sending method and a data receiving end address may be configured in the first buried point deployment information to indicate that the information monitoring point sends the acquired operation behavior monitoring data to the target data receiving end in a specified manner. And configuring a data sending mode and a data receiving end address in the second buried point deployment information so as to indicate the information monitoring point to send the acquired operation result monitoring data to a target data receiving end in a specified mode.

For example, the first site deployment information may be configured to instruct the information monitoring point to send the operation behavior monitoring data to the storage space with the address of B1 through the a1 interface. Meanwhile, the second buried point deployment information can be configured to instruct the monitoring point to send the operation behavior monitoring data to the storage space with the address of B2 through the A2 interface. The address B1 and the address B2 may be the same address or different addresses, and the embodiment is not limited.

Optionally, a unique identification (e.g., logID) may be set for each event as it is landed. And the operation behavior monitoring data and the operation result monitoring data generated after each event is triggered by the access operation carry the unique identification of the event. Based on the unique identification of the event, the operation behavior monitoring data and the operation result monitoring data corresponding to the event can be correlated.

Based on the above, when the access operation on the first page element is analyzed, the event bound by the first page element can be determined, and then the operation behavior monitoring data and the operation result monitoring data corresponding to the event are acquired from the target number receiving terminal according to the unique identification of the event. Next, the access operation on the first page element may be analyzed according to the acquired operation behavior monitoring data and operation result monitoring data.

Optionally, analyzing the access operation on the first page element may include: analyzing the distribution characteristics of the access operand, the number of access users, the number of processing requests, the response success rate of the access operation, the response failure rate of the access operation, the failure reason of the access operation and/or the failure reason on the first page element.

The access operand refers to the frequency of access operations on the first page, and can be obtained by statistics according to the action attribute data in the operation behavior monitoring data. The frequency of operations may be recorded plus one every time an access operation is detected. If the access operation on the page element includes multiple different types, the frequency of each type of access operation can be respectively counted, and further description is omitted.

The number of access users refers to the number of users initiating access operations on the first page element, and can be obtained by monitoring according to the number of user attributes in the operation behavior monitoring data. For example, the number of access users may be counted according to the number of user accounts initiating the access operation, which is not described again.

The processing request number may be counted according to the number of times of obtaining the operation result monitoring data. The operation result monitoring data is acquired by tracking the processing request, and therefore, the frequency of sending the processing request can be considered to be the same as or similar to the frequency of acquiring the operation result monitoring data.

The response success rate can be calculated by combining the frequency of response success and the number of access operands, and the response failure rate can be calculated by combining the frequency of response failure and the number of access operands. The frequency of response and the frequency of response failure may be determined according to the interface state data and the response content data in the operation result monitoring data, and are not described again.

The access operation failure reason can be obtained according to operation verification data in the operation behavior monitoring data and response failure type data in the operation result monitoring data.

The distribution characteristics of the failure reasons can be obtained by counting the occurrence frequency of each type of failure reason. For example, the number of operation failures caused by the failure of the front-end operation check data may be counted, and the number of operation failures caused by the server-side abnormality may be counted, which is not described in detail.

It should be noted that if the first page element is bound with a plurality of events, the access operation triggering each event may be separately analyzed, which is not described in detail.

In the embodiment, the automatic page point burying operation is realized based on the abstract syntax tree of the page, and based on twice point burying, various data generated by the access operation on the page elements can be automatically and streamingly monitored, which is beneficial to more accurately analyzing the access operation on the page elements.

It should be noted that, on the basis of the above-mentioned steps, as shown in fig. 2, the method further includes:

step 209, responding to the viewing operation on the first page element, and acquiring a result of analyzing the access operation on the first page element.

And step 210, visually displaying the result of analyzing the access operation on the first page element on the page.

The user initiating the viewing operation may be a page development user or a page optimization user. When the execution main body is the terminal device, the terminal device can judge the viewing permission of the user according to the user account of the access page. If the terminal equipment judges that the user accessing the page has the permission to view the analysis result according to the user account, the analysis result of the access operation on the page element can be displayed to the user according to the user viewing operation.

Optionally, the viewing operation may be implemented as a frame selection operation on the page element, or a pointer hovering operation on the page element, or a selection operation of a check button bound to the page element, and the like, which is not limited in this embodiment.

In some scenarios, to enhance the display effect, the viewing operation may be implemented as a hovering operation of a mouse pointer over the page element. For example, for a browser, a page element over which a mouse pointer hovers may be selected based on a hover selector. When a 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, according to the identifier of the page element, a result of analyzing the access operation on the pair of page elements may be obtained and displayed.

Optionally, the analysis result of the access operation on the page element may be displayed in a floating window or a pop-up window on the page to be more intuitively displayed to the user. For example, upon detecting a hover operation on a first page element, a hover window may be presented on the page proximate to the first page element, and an analysis result of an access operation on the first page element may be presented within the hover window.

Alternatively, the analysis results may be presented in a graph-based manner. Among others, charts may include, but are not limited to: bar charts (histograms), line charts, pie charts, bar charts, radar charts, word clouds, funnel charts, data maps, waterfall charts, and the like. For example, the access success rate, the failure rate, and the proportion of various error types corresponding to the first page element may be shown based on the bar chart, and are not described again.

A typical presentation may be as shown in figure 3. In fig. 3, a page is shown with page element 1, page element 2, and page element 3. When the mouse pointer is placed on the page element 2, a floating window can pop up on the page, and the analysis result of the access operation on the page element 2 is displayed in the floating window through the column diagram.

Alternatively, step 209 and step 210 may be implemented by a browser plug-in or an application plug-in with the aid of a chart rendering tool. The browser plug-in or the application program plug-in can obtain the analysis result of the access operation on the viewed page element when the user accessing the page is determined to have the permission to view the analysis result, call a chart rendering tool to draw the analysis result, and display the analysis result on the page where the page element is located. Optionally, the rendering tool may be a Bizcharts tool (an open source software providing tools for rendering multiple types of charts) or other optional chart rendering tools, and the embodiment is not limited.

In the 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 on the page in a visual mode, so that the viewing is more intuitive and is convenient for the user to view.

Fig. 4 is a flowchart illustrating a page operation analysis method according to another exemplary embodiment of the present application, where as shown in fig. 4, the method includes:

step 401, a page is displayed, where the page includes a first page element.

Step 402, responding to the access operation on the first page element, and tracking an event triggered by the access operation according to the first embedded point deployment information to obtain operation behavior monitoring data.

Step 403, sending a processing request to the server according to the event triggered by the access operation.

Step 404, according to the second site deployment information, tracking the processing request to obtain a response result of the server to the processing request, which is used as operation result monitoring data.

Step 405, analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

For alternative implementation of the above steps, reference may be made to the descriptions of the foregoing embodiments, which are not repeated herein.

In this embodiment, after the access operation on the page element is detected, various data generated by the access operation can be automatically and flowedly monitored in multiple links based on the first buried point deployment information and the second buried point deployment information, which is beneficial to more accurately analyzing the access operation on the page element.

Besides the page operation analysis method provided by each of the foregoing embodiments, an embodiment of the present application further provides a point burying method, including: and acquiring an abstract syntax tree corresponding to the page. At least one event associated with the page is determined according to the abstract syntax tree. Adding first buried point deployment information and second buried point deployment information in an event processor corresponding to each event; the first embedded point deployment information is used for tracking the event when the event is triggered, and the second embedded point deployment information is used for tracking the processing request corresponding to the event.

The method may be implemented by a browser-based plug-in or an application plug-in. When the page is opened in the browser or the application program, the plug-in the browser or the application program can automatically analyze the AST corresponding to the page, and automatically perform two times of embedding points on each event which can be triggered by operation in the code according to the AST.

The first embedded point deployment information and the second embedded point deployment information may be configured according to actual requirements, and this embodiment is not limited.

In the embodiment, the automatic page point burying operation is realized based on the abstract syntax tree of the page, so that the labor cost is reduced; based on twice embedding, various data generated by the access operation on the page elements can be automatically and streamingly monitored, and the access operation on the page elements can be more accurately analyzed.

It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of step 201 to step 204 may be device a; for another example, the execution subject of

steps

201 and 202 may be device a, and the execution subject of step 203 may be device B; and so on.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 201, 202, etc., are merely used for distinguishing different operations, and the sequence numbers do not represent any execution order per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

The above and following embodiments of the present application can be applied to page operation analysis in a variety of different application scenarios. As will be exemplified below.

In some scenarios, the operation analysis method can be used for performing operation analysis on a webpage provided by a browser based on the webpage operation analysis method provided by the embodiment of the application. The web page may 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, or the like, which is not limited in this embodiment. By carrying out operation analysis on the webpage, the design rationality and the function perfection of the webpage can be analyzed; alternatively, the content in which the user is interested can be mined, and the information displayed by the webpage can be adjusted according to the content in which the user is interested. Taking the e-commerce webpage as an example, the page elements on the e-commerce webpage may include a plurality of category tags corresponding to a plurality of categories of goods. The access times of the multiple category labels are counted, the ratio of the access times of each category label is calculated, and the degree of the user's feeling of multiple commodity categories can be analyzed.

Taking an educational web page as an example, page elements on the educational web page may be implemented as links to various courses. The link may point to course resources provided by the website, and may also point to course resources provided by other websites. After each link is clicked, the click result is tracked, the error reason for failing to respond the click operation is obtained, and the faults of the website or other websites can be positioned and analyzed so as to further optimize the functions of the webpage.

In other scenarios, the operation analysis may be performed on the application page provided by the application program based on the page operation analysis method provided in the embodiment of the present application. The application program can be realized as an application program running on a computer terminal or an application program running on an intelligent terminal. Wherein, intelligent terminal can include smart mobile phone, intelligent wearing equipment, intelligent house equipment etc. and this embodiment does not do the restriction. By carrying out operation analysis on the application program page, the design rationality and the function perfectness of the application program page can be analyzed; alternatively, content of interest to the user may be mined and information presented by the application page adjusted according to the content of interest to the user.

The application program can be client software which is provided by a plurality of different fields, can interact with the user and provides set services for the user. This different area, including but not limited to: the system comprises the following fields of e-commerce, cloud computing, games, news, video, music, education, live broadcast and the like. Taking a news client implemented as a mobile phone end by the application program as an example, page elements on the news client can comprise a plurality of news field tags, and in the process that a user uses the news client, the number of clicks on the plurality of news field tags and the number of times of successfully returning click results are counted, so that the success rate of successfully displaying news contents in different fields by the news client can be calculated, and the access stability of the news client is further analyzed.

The page analysis method provided by the present application will be further exemplified below by taking a web page provided by a website as an example. The website developer can develop a browser plug-in based on a babel tool, the browser plug-in can bury each event which can be triggered by access operation on the webpage twice based on AST of the webpage, namely bury the point before the request and bury the point after the request, and set a logID for each event.

When a user initiates an access operation on a page element in a process of browsing a webpage, a pre-buried point is requested to perform operation statistics, or capture an exception (for example, the user information is incomplete, the previous interface is dependent on a problem, and the operation cannot be performed). After the processing request is sent, the embedded point can obtain interface return information after the request. Based on the data acquired by the pre-request buried point and the post-request buried point and the logID, the response success rate, the failure rate and the percentage of various error types of the access operation on the page element can be counted. The website developer may also develop a dynamic display plug-in based on the interface provided by the browser. When the website develops or maintains a related user access page, the website can log in an access account and move a mouse pointer to a target page element which is desired to be viewed. And when the dynamic display plug-in determines that the visitor has the right to view the analysis result based on the access account, the dynamic display plug-in can acquire the result of analyzing the access operation on the target page element, render the result through an icon rendering tool, and display the rendered result on the webpage through a floating window.

Fig. 5 is a schematic structural diagram of a page operation analysis apparatus according to an exemplary embodiment of the present application, and as shown in fig. 5, the apparatus includes: a presentation module 501, a first monitoring module 502, a request module 503, a second monitoring module 504, and an analysis module 505.

The display module 501 is configured to: a page is presented, the page including a first page element.

A first monitoring module 502 for: and responding to the access operation on the first page element, and acquiring operation behavior monitoring data corresponding to the access operation.

A request module 503, configured to: and sending a processing request to a server according to the event triggered by the access operation.

A second monitoring module 504 configured to: and monitoring a response result of the server to the processing request to obtain operation result monitoring data.

An analysis module 505 for: and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

Further optionally, the display module 501 is further configured to: responding to the viewing operation on the first page element, and acquiring a result of analyzing the access operation on the first page element; and visually displaying the result of analyzing the access operation on the first page element on the page.

Further optionally, when obtaining the operation behavior monitoring data corresponding to the access operation, the first monitoring module 502 is specifically configured to: tracking an event triggered by the access operation according to the first embedded point deployment information; and acquiring the tracked data associated with the event as the operation behavior monitoring data.

Further optionally, when monitoring a response result of the server to the processing request and obtaining operation result monitoring data, the second monitoring module 504 is specifically configured to: tracking the processing request according to the second embedded point deployment information; and acquiring the tracked response result of the server to the processing request as the operation result monitoring data.

Further optionally, the apparatus further comprises a buried point module 506.

Wherein the buried point module 506 is configured to: acquiring an abstract syntax tree corresponding to the page; determining 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; and adding the first buried point deployment information and the second buried point deployment information in an event processor corresponding to each of the at least one event.

Further optionally, when the first buried point deployment information and the second buried point deployment information are added to the event processor corresponding to the at least one event, the buried point module 506 is specifically configured to: for a first event in the at least one event, determining target code in an event processor corresponding to the first event; the object code is used for sending a corresponding processing request to the server when the first event is triggered; adding a code corresponding to the first buried point deployment information before the target code, and adding a code corresponding to the second buried point deployment information after the target code.

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

Further optionally, when analyzing the access operation on the first page element, the analyzing module 505 is specifically configured to: analyzing the distribution characteristics of the access operand, the number of access users, the number of processing requests, the response success rate of the access operation, the response failure rate of the access operation, the failure reason of the access operation and/or the failure reason on the first page element.

Each module in the page operation analysis apparatus shown in fig. 5 may further execute the page operation analysis method according to the following logic:

a display module 501, configured to: a page is presented, the page including a first page element. A first monitoring module 502 for: and responding to the access operation on the first page element, and tracking an event triggered by the access operation according to first buried point deployment information so as to obtain operation behavior monitoring data. A request module 503, configured to: and sending a processing request to a server according to the event triggered by the access operation. A second monitoring module 504 configured to: and tracking the processing request according to the second buried point deployment information to obtain a response result of the server to the processing request as operation result monitoring data. An analysis module 505 for: and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

Fig. 6 is a schematic structural diagram of a buried point device according to an exemplary embodiment of the present application, where the device shown in fig. 6 includes: a page analysis module 601 and a buried point module 602.

The page analysis module 601 is configured to: acquiring an abstract syntax tree corresponding to a page; and determining at least one event associated with the page according to the abstract syntax tree.

A buried point module 602 for: adding first buried point deployment information and second buried point deployment information in an event processor corresponding to each event; the first buried point deployment information is used for tracking the event when the event is triggered, and the second buried point deployment information is used for tracking the processing request corresponding to the event.

The embedded point device provided by the embodiment can be packaged as an automatic embedded point tool and provided for a third-party user for use, and further description is omitted.

Fig. 7 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application, and as shown in fig. 7, the electronic device includes: a memory 701 and a processor 702.

The memory 701 is used for storing a computer program and may be configured to store other various 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, phonebook data, messages, pictures, videos, and so forth.

The memory 702 may be implemented, among other things, by any type of volatile or non-volatile storage device or 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 or optical disk.

When the electronic device is applied to the page analysis operation, the method may further include: a communications component 703 and a display component 704.

The processor 702, coupled to the memory 701, is configured to execute the computer program in the memory 701, so as to: presenting, by display component 704, a page, the page comprising a first page element; responding to the access operation on the first page element, and acquiring operation behavior monitoring data corresponding to the access operation; sending a processing request to a server through a communication component 703 according to an event triggered by the access operation; monitoring a response result of the server to the processing request to obtain operation result monitoring data; and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

Further optionally, the processor 702 is further configured to: responding to the viewing operation on the first page element, and acquiring a result of analyzing the access operation on the first page element; the results of the analysis of the access operation on the first page element are visually presented on the page by display component 704.

Further optionally, when obtaining the operation behavior monitoring data corresponding to the access operation, the processor 702 is specifically configured to: tracking an event triggered by the access operation according to the first embedded point deployment information; and acquiring the tracked data associated with the event as the operation behavior monitoring data.

Further optionally, when monitoring a response result of the server to the processing request and obtaining operation result monitoring data, the processor 702 is specifically configured to: tracking the processing request according to the second embedded point deployment information; and acquiring the tracked response result of the server to the processing request as the operation result monitoring data.

Further optionally, the processor 702 is further configured to: acquiring an abstract syntax tree corresponding to the page; determining 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; and adding the first buried point deployment information and the second buried point deployment information in an event processor corresponding to each of the at least one event.

Further optionally, when the first buried point deployment information and the second buried point deployment information are added to the event processor corresponding to the at least one event, the processor 702 is specifically configured to: for a first event in the at least one event, determining target code in an event processor corresponding to the first event; the object code is used for sending a corresponding processing request to the server when the first event is triggered; adding a code corresponding to the first buried point deployment information before the target code, and adding a code corresponding to the second buried point deployment information after the target code.

Further optionally, when analyzing the access operation on the first page element, the processor 702 is specifically configured to: analyzing the distribution characteristics of the access operand, the number of access users, the number of processing requests, the response success rate of the access operation, the response failure rate of the access operation, the failure reason of the access operation and/or the failure reason on the first page element.

Further, as shown in fig. 7, the electronic device further includes: power supply components 705, and the like. Only some of the components are schematically shown in fig. 7, and the electronic device is not meant to include only the components shown in fig. 7.

The communication component 703 is configured to facilitate communication between the device in which the communication component is located and other devices in a wired or wireless manner. The device in which the communication component is located may 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 may 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.

Display assembly 704 includes a screen, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP), among other things. If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal 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 boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

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

In addition to the execution logic described in the foregoing embodiment, the electronic device shown in fig. 7 may also execute the page analysis method according to the following logic: the processor 702 presents a page via the display component 704, the page including a first page element; responding to the access operation on the first page element, and tracking an event triggered by the access operation according to first embedded point deployment information to acquire operation behavior monitoring data; sending a processing request to a server through a communication component 703 according to an event triggered by the access operation; tracking the processing request according to second buried point deployment information to obtain a response result of the server to the processing request as operation result monitoring data; and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

In addition to the execution logic described in the foregoing embodiments, an electronic device comprising a memory and a processor may execute the page-spotting method according to the following logic: the processor acquires an abstract syntax tree corresponding to the page; determining at least one event associated with the page according to the abstract syntax tree; adding first buried point deployment information and second buried point deployment information in an event processor corresponding to each event; the first buried point deployment information is used for tracking the event when the event is triggered, and the second buried point deployment information is used for tracking the processing request corresponding to the event.

Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program is capable of implementing the steps that can be executed by the electronic device in the foregoing method embodiments when executed.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. 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 is characterized by comprising the following steps:

displaying a page, wherein the page comprises a first page element;

responding to the access operation on the first page element, and acquiring operation behavior monitoring data corresponding to the access operation;

sending a processing request to a server according to the event triggered by the access operation, and monitoring the response result of the server to the processing request to obtain operation result monitoring data;

and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

2. The method of claim 1, further comprising:

responding to the viewing operation on the first page element, and acquiring a result of analyzing the access operation on the first page element;

and visually displaying the result of analyzing the access operation on the first page element on the page.

3. The method of claim 1, wherein obtaining operation behavior monitoring data corresponding to the access operation comprises:

tracking an event triggered by the access operation according to the first embedded point deployment information;

and acquiring the tracked data associated with the event as the operation behavior monitoring data.

4. The method of claim 3, wherein monitoring the response result of the server to the processing request to obtain operation result monitoring data comprises:

tracking the processing request according to the second embedded point deployment information;

and acquiring the tracked response result of the server to the processing request as the operation result monitoring data.

5. The method of claim 4, further comprising:

acquiring an abstract syntax tree corresponding to the page;

determining 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;

and adding the first buried point deployment information and the second buried point deployment information in an event processor corresponding to each of the at least one event.

6. The method according to claim 5, wherein adding the first and second deployment information in the event handler corresponding to the at least one event comprises:

for a first event in the at least one event, determining target code in an event processor corresponding to the first event; the object code is used for sending a corresponding processing request to the server when the first event is triggered;

adding a code corresponding to the first buried point deployment information before the target code, and adding a code corresponding to the second buried point deployment information after the target code.

7. The method of any of claims 1-6, wherein the operational behavior monitoring data comprises: at least one of action attribute data, user attribute data, operation object attribute data and operation check data;

the operation result monitoring data includes: at least one of interface status data, response content data, and response failure type data.

8. The method of claim 7, wherein analyzing the access operation on the first page element comprises:

analyzing the distribution characteristics of the access operand, the number of access users, the number of processing requests, the response success rate of the access operation, the response failure rate of the access operation, the failure reason of the access operation and/or the failure reason on the first page element.

9. A page operation analysis method is characterized by comprising the following steps:

displaying a page, wherein the page comprises a first page element;

responding to the access operation on the first page element, and tracking an event triggered by the access operation according to first embedded point deployment information to acquire 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 buried point deployment information to obtain a response result of the server to the processing request as operation result monitoring data;

10. A method of burying a point, comprising:

acquiring an abstract syntax tree corresponding to a page;

determining at least one event associated with the page according to the abstract syntax tree;

adding first buried point deployment information and second buried point deployment information in an event processor corresponding to each event;

the first buried point deployment information is used for tracking the event when the event is triggered, and the second buried point deployment information is used for tracking the processing request corresponding to the event.

11. A page operation analysis apparatus, comprising:

a display module for: displaying a page, wherein the page comprises a first page element;

a first monitoring module to: responding to the access operation on the first page element, and acquiring operation behavior monitoring data corresponding to the access operation;

a request module to: sending a processing request to a server according to the event triggered by the access operation;

a second monitoring module to: monitoring a response result of the server to the processing request to obtain operation result monitoring data;

an analysis module to: and analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.

12. The apparatus of claim 11, further comprising:

a buried point module for: acquiring an abstract syntax tree corresponding to the page; determining 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; and adding the first buried point deployment information and the second buried point deployment information in an event processor corresponding to each of the at least one event.

13. The apparatus of claim 11 or 12, wherein the display module is further configured to: responding to the viewing operation on the first page element, and acquiring a result of analyzing the access operation on the first page element; and visually displaying the result of analyzing the access operation on the first page element on the page.

14. A page operation analysis apparatus, comprising:

a first monitoring module to: responding to the access operation on the first page element, and tracking an event triggered by the access operation according to first embedded point deployment information to acquire operation behavior monitoring data;

a second monitoring module to: tracking the processing request according to second buried point deployment information to obtain a response result of the server to the processing request as operation result monitoring data;

15. A point burying device, comprising:

a page analysis module to: acquiring an abstract syntax tree corresponding to a page; determining at least one event associated with the page according to the abstract syntax tree;

a buried point module for: adding first buried point deployment information and second buried point deployment information in an event processor corresponding to each event; the first buried point deployment information is used for tracking the event when the event is triggered, and the second buried point deployment information is used for tracking the processing request corresponding to the event.

16. An electronic device, comprising: a memory and a processor;

the memory is to store one or more computer instructions;

the processor is to execute the one or more computer instructions to: performing the page operation analysis method of any one of claims 1-9 or the burial point method of claim 10.

17. A computer-readable storage medium storing a computer program, wherein the computer program is capable of implementing the page operation analysis method according to any one of claims 1 to 10 or the dotting method according to claim 10 when the computer program is executed by a processor.