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 clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In some conventional page operation analysis methods, access operations on a page are typically analyzed by manually analyzing a back-end interface log, or an exception capture statement (e.g., a try/catch statement for capturing a web page error) is used at the front-end to monitor access operations on page elements. These conventional page operation analysis methods cannot analyze access operations on different page elements on a page more accurately.
In view of the foregoing technical problems, in some embodiments of the present application, a solution is provided, and in the following, the technical solutions provided by the embodiments of the present application are described in detail with reference to the accompanying drawings.
Fig. 1 is a flow chart of a page operation analysis method according to an exemplary embodiment of the present application, as shown in fig. 1, the method includes:
step 101, displaying a page, wherein the page comprises a first page element.
Step 102, responding to the access operation on the first page element, and acquiring operation behavior monitoring data corresponding to the access operation.
Step 103, according to the event triggered by the access operation, sending a processing request to a server, 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 body of the embodiment may be a terminal device, which may be implemented as a computer, a mobile phone, a tablet computer, etc., and the embodiment is not limited. 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 program of a 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, etc., hyperlink elements, e.g., text hyperlinks, picture hyperlinks, etc. The page element may provide the user with a variety of different operation portals to facilitate the user's access to and use of the functionality provided by the page based on the different operation portals. For example, when the page element is implemented as a button control such as "edit", "delete", "save", etc., the user can access and use the functions of editing data, deleting data, and saving data provided by the page based on the button control. 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, which will not be described again.
The user who initiates the access operation to the page element is usually a service object of the page information. For example, a user who causes the terminal device to access the application page, a user who accesses the 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 page development effects or a computer program for simulating page testing, and the present embodiment is not limited.
An access operation on a page element refers to some kind of operation initiated by a user on the page element that can be detected. The access operation may be implemented as a plurality of different types of operations, for example, may be implemented as a click operation, an input operation, a drag operation, a long press operation, etc. for the page element, and the embodiment is not limited. The first page element refers to any page element on a page, and is defined herein by "first" 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, and operation behavior monitoring data can be obtained. The operation behavior monitoring data may include various 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 operation behavior.
Wherein each page element may bind one or more events, each event corresponding to an event listener and event handler (EVENT HANDLER). The event monitor is used for monitoring 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, an event processor needs to complete event processing operations with support from a server, e.g., the server is required to provide data support and computational power support. When an access operation occurs on the first page element, a certain event of the first page element binding 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's click on a "delete" button on a page triggers a delete event for specific data stored on the server. Then the event handler of 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 can monitor the 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 an event triggered by the access operation is successfully processed, namely, 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 element 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 the embodiment, after the access operation for the page element is detected, the operation behavior monitoring data corresponding to the access operation is obtained, after the processing request is sent to the server, the response result of the processing request is monitored by the server, and the operation result monitoring data is obtained, 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 obtained more comprehensively, the function level monitoring on the access operation on the page element is realized, and the access operation on the page element can be analyzed more accurately.
It should be noted that, in the above and the following 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 may be obtained by burying the access operation on the page multiple times.
The buried point, also called event tracking (EVENT TRACKING), is to add an information monitoring point in a specific processing link, where 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 by the embodiment of the application is further described below in connection with the buried point operation.
Fig. 2 is a flow chart of a page operation analysis method according to another exemplary embodiment of the present application, as shown in fig. 2, the method includes:
Step 201, obtaining an abstract syntax tree corresponding to a page.
Step 202, 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 a bound page element.
Step 203, adding the first buried point deployment information and the second buried point deployment information in the event processors corresponding to the at least one event.
Step 204, the page is displayed, and at least one page element is displayed 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 embedded point deployment information so as to acquire operation behavior monitoring data.
And 206, sending a processing request to the server according to the event triggered by the access operation.
Step 207, tracking the processing request according to the second buried point deployment information to obtain operation result monitoring data.
And step 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 (Abstract Syntax Tree, AST) is an abstract representation of the source code syntax structure. 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.
Alternatively, if the page is developed using JavaScript (a programming language, abbreviated as JS) language, a Babel tool may be used to obtain an abstract syntax tree of the page. The Babel tool is a JS editor that can convert source language. For example, the Babel tool may convert the JS source code corresponding to the page into AST according to the babylon library, which is not described herein.
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 the page element, each event being triggerable 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, which may be triggered by a single click operation on the page button, and a long press event, which may be triggered by a long press operation on the page button. For another example, a page picture may bind a double click event and a drag event, wherein the double click event may be triggered by a double click operation on the page picture and the drag event may be triggered by a drag operation on the page picture.
In step 203, the event handler is configured to execute a set event handling operation when the 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 perfect the monitoring flow of the access operation, two burial points can be performed in the event processor to form two information monitoring points in the event processor. Alternatively, the first buried point deployment information and the second buried point deployment information may be added in each event processor. The first embedded point deployment information is used for tracking the event to which the first embedded point deployment information belongs when the event to which the first embedded point deployment information belongs is triggered, and the second embedded point deployment information is used for tracking a processing request corresponding to the event to which the second embedded point deployment information belongs.
Two buried point operations will be exemplarily described below taking any one of the at least one event as an example. For convenience of description, this arbitrary event is described as a first event.
Alternatively, the code corresponding to the event handler of the first event may be determined in the source code corresponding to the page. Then, an object code may be determined in the code corresponding to 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 operations, two information monitoring points are formed in the event processor, the first information monitoring point being before the processing request is sent, and the second information monitoring point being after the processing request is sent.
Alternatively, steps 201-203 described above may be implemented by a browser plug-in or an application plug-in developed based on the Babel tool. When the page is opened in a browser or an application program, the plug-in can automatically analyze AST corresponding to the page, and automatically burial each event in the code, which can be triggered by operation, twice according to the AST. Furthermore, automatic point burying operation based on a browser or an application program is realized, and labor cost is reduced.
In step 204, the page may optionally be presented when the user accesses the page through the terminal device. Or the page may be presented upon 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 the first page element may trigger some event of the first page element binding. Based on the record of the buried point step, the event processor corresponding to the triggered event comprises two information monitoring points, namely, the information monitoring point corresponding to the first buried point deployment information and the information monitoring point corresponding to the second buried point deployment information.
The information monitoring points corresponding to the first embedded point deployment information can track an event triggered by the access operation when the access operation occurs on the first page element, and the tracked data associated with the event is used as 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.
The action attribute data may include an operation frequency, an operation type, and the like of the access operation triggering the event. User attribute data, which may include an identification of the user (e.g., user account number, etc.) that initiated the access operation. The operation object data may include related information of the accessed page element, such as an identification of the page element, a type of the page element, a business function corresponding to the page element, and the like. The operation check data may include configuration information check data, interface check data, JS form check data, and the like. And will not be described in detail.
It should be appreciated that the first buried point deployment information may be configured individually to instruct information monitoring points which operational behavior monitoring data to acquire during a trace event. The above listed data are for illustrative purposes only and the present embodiment includes but is not limited to such.
In step 206, a corresponding processing request may be sent to the server based on 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 events triggered by the access operation are different, the processing requests sent to the server are also different.
For example, a button on a 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 single click operation, the single click operation triggers a single click event, a processing request corresponding to the M function can be sent to the server, and if the access operation is a double click operation, the double click operation triggers 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 may be tracked according to the second embedded point deployment information. In the process of tracking the processing request, the information monitoring point can capture the response result of the server to the processing request, and operation result monitoring data is obtained.
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 can comprise interface abnormal data, interface normal data and the like. Based on the interface status data, the cause of failure of the access operation may be analyzed. For example, in some scenarios, an abnormality occurs in the communication interface between the terminal device and the server, and the server cannot receive the processing request, which results in failure to respond to the access operation on the page element successfully.
Wherein, the response content refers to the actual content returned by the server according to the processing request. Analyzing the response content can identify whether the access operation on the page element cannot be successfully responded due to the reason of the server side. For example, in some scenarios, no exception occurs to the interface, the server successfully receives the processing request, but the server side exception causes processing failure, and the response content indicates that the processing request was not successfully processed, although the server successfully returned the response content. 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 cause of the failure of the access operation response comes from the server side or not can be accurately analyzed.
The response failure type may include an interface exception failure type, a server exception failure type, or a type of failure caused by other reasons at 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 more 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 in a particular period may be counted for analysis in accordance with the counted period. The specific period may be one day, three days, or one week. Or the specific period can be flexibly adjusted according to the information content published on the page, and the embodiment is not limited.
Optionally, a data sending mode and a data receiving end address may be configured in the first embedded point deployment information, so as to instruct the information monitoring point to send the obtained operation behavior monitoring data to the target data receiving end in a specified mode. And the data sending mode and the data receiving end address can be configured in the second embedded point deployment information so as to instruct the information monitoring point to send the obtained operation result monitoring data to the target data receiving end in a specified mode.
For example, the information monitoring point may be instructed to send the operation behavior monitoring data to the storage space with the address B1 through the A1 interface by configuring the first buried point deployment information. Meanwhile, the second embedded 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, which is not limited in this embodiment.
Alternatively, a unique identification (e.g., logID) may be set for each event as it is buried. 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 associated.
Based on the above, when the access operation on the first page element is analyzed, the event bound to 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 obtained from the target number receiving end according to the unique identification of the event. Then, the access operation on the first page element may be analyzed according to the obtained operation behavior monitoring data and operation result monitoring data.
Optionally, analyzing the access operation on the first page element may include analyzing an access operand, a number of access users, a number of processing requests, a response success rate of the access operation, a response failure rate of the access operation, a failure cause of the access operation, and/or a distribution characteristic of the failure cause on the first page element.
The access operand refers to the frequency of access operation on the first page, and can be obtained according to action attribute data statistics in the operation behavior monitoring data. The frequency of operations may be recorded plus one each 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 counted respectively, and the description is omitted.
The number of access users refers to the number of users initiating access operation on the first page element, and the number of access users can be obtained according to the monitoring of the number of user attributes in the operation behavior monitoring data. For example, the number of access users can be counted according to the number of user accounts initiating the access operation, which is not described in detail.
The processing request number can be counted according to the number of times of acquiring the operation result monitoring data. The operation result monitoring data is acquired by tracking the processing request, and therefore, the frequency of transmitting the processing request can be regarded as 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 access operand, and the response failure rate can be calculated by combining the frequency of response failure and the access operand. The response frequency and the response failure frequency can 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 failure cause of the access operation can be obtained according to operation check 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 reasons. For example, the number of operation failures caused by the failure of the front-end operation verification data can be counted, and the number of operation failures caused by the server-side abnormality can be counted, which is not described again.
It should be noted that, if the first page element is bound with a plurality of events, the access operation for triggering each event may be separately analyzed, which is not described herein.
In the embodiment, based on the abstract syntax tree of the page, automatic page embedded point operation is realized, and based on two embedded points, various data generated by the access operation on the page element can be automatically and flowably monitored, so that the access operation on the page element can be more accurately analyzed.
It should be noted that, on the basis of the above steps, as shown in fig. 2, the method further includes:
Step 209, responding to the view operation on the first page element, and obtaining the result of analyzing the access operation on the first page element.
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 development user of the page or an optimization user of the page. When the execution subject is the terminal equipment, the terminal equipment can judge the viewing authority of the user according to the user account number of the access page. If the terminal equipment judges that the user accessing the page has the authority 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 viewing operation of the user.
Alternatively, the view operation may be implemented as a box operation on the page element, or a pointer hover operation on the page element, or a selection operation of a tick button bound to the page element, or 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 hover operation of a mouse pointer over a page element. For example, for a browser, a page element hovering with a mouse pointer may be selected based on a river selector. When the mouse pointer hovers over a page element, the user may be considered to want to view the analysis results corresponding to the page element. And then, according to the identification of the page element, acquiring the analysis result of the access operation on the page element and displaying the analysis result.
Optionally, the analysis result of the access operation on the page element may be displayed in a floating window or popup window on the page, so as to be more intuitively displayed to the user. For example, after detecting a hover operation on a first page element, a floating window may be presented on the page at a location near the first page element, and an analysis result of the access operation on the first page element may be presented within the floating window.
Alternatively, the analysis results may be presented graphically. The 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 duty ratio of various error types corresponding to the first page element can be shown based on the bar graph, which is not described again.
A typical display effect may be as shown in fig. 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 be popped 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 bar graph.
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 acquire the analysis result of the access operation on the checked page element when the user accessing the page is determined to have the authority to check the analysis result, call the chart rendering tool to draw the analysis result, and display the analysis result on the page where the page element is located. Alternatively, the rendering tool may be Bizcharts tools (an open source software, a tool that provides multiple types of chart rendering) or other alternative chart rendering tools, which is not limited in this embodiment.
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 method is more visual and is convenient for the user to view.
Fig. 4 is a flowchart of a page operation analysis method according to another exemplary embodiment of the present application, as shown in fig. 4, where the method includes:
step 401, a page is displayed, wherein the page comprises 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 so as to acquire operation behavior monitoring data.
Step 403, according to the event triggered by the access operation, sending a processing request to the server.
And step 404, tracking the processing request according to the second embedded point deployment information to acquire a response result of the server to the processing request as operation result monitoring data.
And step 405, analyzing the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.
Alternative implementations of the above steps may refer 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, multiple data generated by the access operation can be automatically and flowably monitored in multiple links based on the first buried point deployment information and the second buried point deployment information, so that the access operation on the page element can be more accurately analyzed.
In addition to the page operation analysis method provided by the above embodiments, the embodiment of the present application further provides a point embedding method, where the method includes obtaining an abstract syntax tree corresponding to a page. At least one event associated with the page is determined from the abstract syntax tree. And adding first buried point deployment information and second buried point deployment information into event processors corresponding to the at least one event, wherein 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 a 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 AST corresponding to the page, and according to the AST, each event in the code, which can be triggered by operation, is automatically buried twice.
The first buried point deployment information and the second buried point deployment information can be configured according to actual requirements, and the embodiment is not limited.
In the embodiment, the automatic page embedding operation is realized based on the abstract syntax tree of the page, the labor cost is reduced, and based on the twice embedding operation, various data generated by the access operation on the page element can be automatically and flowably monitored, thereby being beneficial to more accurately analyzing the access operation on the page element.
It should be noted that, the execution subjects of each step of the method provided in the above embodiment may be the same device, or the method may also be executed by different devices. For example, the execution bodies of steps 201 through 204 may be device A, and for example, the execution bodies of steps 201 and 202 may be device A, the execution body 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 appearing in a specific order are included, but it should be clearly understood that the operations may be performed out of the order in which they appear herein or performed in parallel, the sequence numbers of the operations such as 201, 202, etc. are merely used to distinguish between the various operations, and the sequence numbers themselves do not represent any order of execution. In addition, 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" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.
The above and the following embodiments of the present application can be applied to page operation analysis in a plurality of different application scenarios. An exemplary description will be made below.
In some scenes, the operation analysis can be performed on the webpage provided by the 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, and the like, which is not limited in this embodiment. Through operation analysis on the webpage, the design rationality and the functional perfection of the webpage can be analyzed, or the content of interest of the user can be mined, and the information of webpage display can be adjusted according to the content of interest of the user. Taking an e-commerce web page as an example, the page elements on the e-commerce web page may include a plurality of category labels corresponding to a plurality of commodity categories. The access times of the plurality of category labels are counted, the ratio of the access times of each category label is calculated, and the user's sense of sight of the plurality of 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 be directed to the course resources provided by the website or may be directed to course resources provided by other websites. After each link is clicked, the clicking result is tracked, and error reasons which cannot respond to clicking operation successfully are obtained, so that faults of the website or other websites can be positioned and analyzed, and the webpage functions are further optimized.
In other cases, the operation analysis can be performed on the application program page provided by the application program based on the page operation analysis method provided by the embodiment of the application. The application program can be implemented as an application program running on a computer end or as an application program running on an intelligent terminal. The smart terminal may include a smart phone, an intelligent wearable device, an intelligent home device, and the like, which is not limited in this embodiment. Through operation analysis of the application program page, design rationality and functional perfection of the application program page can be analyzed, or content of interest to a user can be mined, and information displayed on the application program page can be adjusted according to the content of interest to the user.
The application may be client software provided in a plurality of different fields that can interact with the user and provide setup services to the user. The different fields include, but are not limited to, e-commerce fields, cloud computing fields, game fields, news fields, video fields, music fields, education fields, live broadcast fields, etc. Taking a news client implemented as a mobile phone end by using the application program as an example, page elements on the news client can comprise a plurality of news field labels, in the process of using the news client by a user, the number of clicks on the plurality of news field labels and the number of times of successful return of clicking results are counted, the success rate of successful display of news contents in different fields by the news client can be calculated, and then the access stability of the news client is analyzed.
The page analysis method provided by the application will be further exemplified by a web page provided by a website. The website developer may develop a browser plug-in based on babel tools, which may perform two burial points for each event on the web page that may be triggered by the access operation, i.e., a pre-request burial point and a post-request burial point, based on the AST of the web page, and set one logID for each event.
When a user initiates access operation to a page element in the process of browsing a webpage, the buried point before the request can perform operation statistics or capture anomalies (such as incomplete user information, incapacity of operation caused by the previous interface dependence problem, and the like). After sending the processing request, the embedded point can acquire the interface return information after the request. Based on the data acquired by the buried point before and after the request and logID, the response success rate, the failure rate and the duty ratio of various error types of the access operation on the page element can be counted. The web site developer may also develop a dynamic display plug-in based on the interface provided by the browser. When a related user accesses a page, the website is developed or maintained, an access account can be logged in, and a mouse pointer can be moved to a target page element to be viewed. When the dynamic display plug-in determines that the visitor has the right to view the analysis result based on the access account, the result of analyzing the access operation on the target page element can be obtained, the result is rendered through the icon rendering tool, and the rendered result is displayed on the webpage through the floating window.
Fig. 5 is a schematic structural diagram of a page operation analysis device according to an exemplary embodiment of the present application, and as shown in fig. 5, 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.
The display module 501 is configured to display a page, where the page includes a first page element.
The first monitoring module 502 is configured to respond to an access operation on the first page element, and obtain operation behavior monitoring data corresponding to the access operation.
And the request module 503 is configured to send a processing request to the server according to the event triggered by the access operation.
And the second monitoring module 504 is configured to monitor a response result of the server to the processing request, and obtain operation result monitoring data.
And the analysis module 505 is configured to analyze 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 obtain, in response to a viewing operation on the first page element, a result of analyzing the access operation on the first page element, and visually display, on the page, a result of analyzing the access operation on the first page element.
Further optionally, the first monitoring module 502 is specifically configured to track an event triggered by the access operation according to the first embedded point deployment information when acquiring the operation behavior monitoring data corresponding to the access operation, and acquire the tracked data associated with the event as the operation behavior monitoring data.
Further optionally, the second monitoring module 504 is specifically configured to track the processing request according to the second embedded point deployment information when monitoring a response result of the server to the processing request to obtain operation result monitoring data, and obtain 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.
The embedded point module 506 is configured to obtain 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 bound page element, and add the first embedded point deployment information and the second embedded point deployment information in an event processor corresponding to each of the at least one event.
Further optionally, the embedded point module 506 is specifically configured to determine, for a first event of the at least one event, an object code in an event processor corresponding to the first event when adding the first embedded point deployment information and the second embedded point deployment information in an event processor corresponding to the at least one event, where the object code is configured to send a corresponding processing request to the server when the first event is triggered, add a code corresponding to the first embedded point deployment information before the object code, and add a code corresponding to the second embedded point deployment information after the object code.
Further optionally, the operation behavior monitoring data comprises at least one of action attribute data, user attribute data, operation object attribute data and operation verification data, and the operation result monitoring data comprises at least one of interface state data, response content data and response failure type data.
Further optionally, the analysis module 505 is specifically configured to analyze the number of access operations, the number of access users, the number of processing requests, the response success rate of the access operations, the response failure rate of the access operations, the failure cause of the access operations, and/or the distribution characteristics of the failure cause on the first page element when analyzing the access operations on the first page element.
In the embodiment, after the access operation for 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.
The respective modules in the page operation analysis apparatus shown in fig. 5 may also execute the page operation analysis method according to the following logic:
A display module 501 is configured to display a page, where the page includes a first page element. The first monitoring module 502 is configured to respond to an access operation on the first page element, and track an event triggered by the access operation according to first buried point deployment information, so as to obtain operation behavior monitoring data. And the request module 503 is configured to send a processing request to the server according to the event triggered by the access operation. And the second monitoring module 504 is configured to track the processing request according to the second embedded point deployment information, so as to obtain a response result of the server to the processing request, and use the response result as operation result monitoring data. And the analysis module 505 is configured to analyze the access operation on the first page element according to the operation behavior monitoring data and the operation result monitoring data.
In this embodiment, after the access operation on the page element is detected, multiple data generated by the access operation can be automatically and flowably monitored in multiple links based on the first buried point deployment information and the second buried point deployment information, so that the access operation on the page element can be more accurately analyzed.
Fig. 6 is a schematic structural diagram of a buried point device according to an exemplary embodiment of the present application, and 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 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.
The embedded point module 602 is configured to add first embedded point deployment information and second embedded point deployment information to event processors corresponding to the at least one event, where the first embedded point deployment information is used to track the event when the event is triggered, and the second embedded point deployment information is used to track a processing request corresponding to the event.
The point burying device provided in this embodiment may be packaged as an automatic point burying tool and provided for a third party user, and will not be described again.
In the embodiment, the automatic page embedding operation is realized based on the abstract syntax tree of the page, the labor cost is reduced, and based on the twice embedding operation, various data generated by the access operation on the page element can be automatically and flowably monitored, thereby being beneficial to more accurately analyzing the access operation on the page element.
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.
Memory 701 is used to store a computer program and may be configured to store various other data to support operations on an 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 the like.
The memory 701 may be implemented by any type or combination of volatile or nonvolatile memory devices 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.
The electronic device, when applied to page analysis operations, may also include a communication component 703 and a display component 704.
The processor 702 is coupled to the memory 701 and is configured to execute a computer program in the memory 701, and configured to display a page through the display component 704, where the page includes a first page element, obtain operation behavior monitoring data corresponding to an access operation in response to the access operation on the first page element, send a processing request to a server through the communication component 703 according to an event triggered by the access operation, monitor a response result of the server to the processing request, obtain operation result monitoring data, and analyze 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 obtain, in response to a viewing operation on the first page element, a result of analyzing the access operation on the first page element, and visually display, on the page, the result of analyzing the access operation on the first page element through the display component 704.
Further optionally, the processor 702 is specifically configured to track an event triggered by the access operation according to the first embedded point deployment information when acquiring the operation behavior monitoring data corresponding to the access operation, and acquire the tracked data associated with the event as the operation behavior monitoring data.
Further optionally, the processor 702 is specifically configured to track the processing request according to the second embedded point deployment information when monitoring a response result of the server to the processing request to obtain operation result monitoring data, and obtain a 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 obtain 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 bound to the event, and add 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, the processor 702 is specifically configured to determine, for a first event of the at least one event, an object code in an event processor corresponding to the first event when adding the first embedded point deployment information and the second embedded point deployment information in the event processor corresponding to the at least one event, where the object code is configured to send a corresponding processing request to the server when the first event is triggered, add, before the object code, a code corresponding to the first embedded point deployment information, and add, after the object code, a code corresponding to the second embedded point deployment information.
Further optionally, the operation behavior monitoring data comprises at least one of action attribute data, user attribute data, operation object attribute data and operation verification data, and the operation result monitoring data comprises at least one of interface state data, response content data and response failure type data.
Further optionally, the processor 702 is specifically configured to analyze an access operand, a number of access users, a number of processing requests, a response success rate of the access operation, a response failure rate of the access operation, a failure cause of the access operation, and/or a distribution feature of the failure cause on the first page element when analyzing the access operation on the first page element.
Further, as shown in FIG. 7, the electronic device may also include other components such as a power supply component 705. Only some of the components are schematically shown in fig. 7, which does not mean that the electronic device only comprises the components shown in fig. 7.
Wherein the communication component 703 is configured to facilitate wired or wireless communication between the device in which the communication component is located and other devices. 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 one exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one 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.
Among other things, the display assembly 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 touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation.
Wherein the power supply assembly 705 provides power to the various components of the device in which the power supply assembly is located. The power components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the devices in which the power components are located.
In the embodiment, after the access operation for 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.
In addition to the execution logic described in the foregoing embodiment, the electronic device shown in fig. 7 may further perform a page analysis method according to logic that the processor 702 displays, through the display component 704, a page, where the page includes a first page element, tracks, in response to an access operation on the first page element, an event triggered by the access operation according to first embedded point deployment information to obtain operation behavior monitoring data, sends, in response to the access operation triggering event, a processing request to a server through the communication component 703, tracks, in response to the processing request according to second embedded point deployment information, to obtain, as operation result monitoring data, a response result of the server to the processing request, and analyzes, in accordance with the operation behavior monitoring data and the operation result monitoring data, the access operation on the first page element.
Besides the execution logic described in the foregoing embodiment, the electronic device including the memory and the processor may further perform a page embedding method according to logic that the processor obtains an abstract syntax tree corresponding to a page, determines at least one event associated with the page according to the abstract syntax tree, and adds first embedding point deployment information and second embedding point deployment information to an event processor corresponding to each at least one event, where the first embedding point deployment information is used to track the event when the event is triggered, and the second embedding point deployment information is used to track a processing request corresponding to the event.
Accordingly, the present application also provides a computer readable storage medium storing a computer program, where the computer program is executed to implement the steps executable by the electronic device in the above method embodiments.
It will be appreciated by those skilled in the art that 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
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 storage media for a computer 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, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
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 one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.