WO2017167042A1

WO2017167042A1 - Statistical method and apparatus for behaviors of front-end users

Info

Publication number: WO2017167042A1
Application number: PCT/CN2017/077244
Authority: WO
Inventors: 罗健
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2016-04-01
Filing date: 2017-03-20
Publication date: 2017-10-05
Also published as: TWI753887B; TW201810076A; CN107295050A; CN107295050B

Abstract

The present invention provides a statistical method and apparatus for behaviors of front-end users. The method comprises: obtaining a point burying rule preset for a page; monitoring a page click event of the page in a page operating process; and after the page click event is monitored, collecting statistics on behavior data of front-end users of the page according to the point burying rule. In the present invention, to implement automatic point burying, a point burying rule is set for a page first, the starting of point burying is triggered by a page click event when the page operates, so that the problems of frequent occurrence of errors and poor convenience in manual point burying in the prior art are resolved, and global statistics collection can be performed on behaviors of front-end users of the page, and the statistical efficiency is high.

Description

Front-end user behavior statistics method and device

The present application claims priority to Chinese Patent Application Serial No. No. No. No. No. No. No. No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

Technical field

The present invention relates to the field of data processing technologies, and in particular, to a front-end user behavior statistics method and apparatus.

Background technique

Today, with the rapid development of the Internet, whether it is an operator of an e-commerce store or a personal webmaster, if you can know some of the click behaviors of the user during the page stay, and can analyze it well, it will be improved. The most direct and efficient help for the user experience of the web page and the attraction of user clicks.

The user's click behavior is usually recorded by burying the page. In layman's terms, the page burying point is an operation of collecting user access and clicking data through a scripting language (JavaScript, JS for short). When the user opens a web page and clicks, the buried JS code in the page will be executed, and the JS code will pass the collected data back to the web server.

In the current buried point technology, the specified button is manually buried, and the user's behavior is counted based on the click operation of the designated button. When the actual application needs to perform global statistics on the page, the process of manually burying the points is cumbersome and has a problem of poor convenience.

Summary of the invention

The invention provides a front-end user behavior statistics method and device, which are used to solve the problem that the manual burying process is relatively cumbersome and convenient when the page is globally statistic.

To achieve the above objective, the present invention provides a front-end user behavior statistics method, including:

Obtain a burying rule pre-set for the page;

During the running of the page, the page click event of the page is monitored;

After the page click event is monitored, the behavior data of the front end user of the page is counted according to the buried point rule.

In order to achieve the above object, the present invention provides a front-end user behavior statistics device, including:

The obtaining module is configured to obtain a burying rule preset for the page;

a monitoring module, configured to monitor a page click event of the page during the running of the page;

The statistic module is configured to collect behavior data of the front end user of the page based on the burying point rule after the page click event is monitored.

The front-end user behavior statistics method and device provided by the present invention acquires a burying rule preset for a page, monitors a page click event of a page during a page running process, and monitors a page click event based on a burying point The rules count the behavior data of the front-end users of the page. In the invention, in order to realize the automatic burying of the page, the burying rule is set for the page first, and the burying point is triggered by the page click event when the page is running, which solves the problem that the existing manual burying point is cumbersome and convenient. The problem, and the ability to global statistics on the behavior of the front-end users of the page, the statistical efficiency is higher.

DRAWINGS

1 is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 1 of the present invention;

2 is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 2 of the present invention;

3 is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 3 of the present invention;

4 is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 4 of the present invention;

5 is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 5 of the present invention;

6 is a schematic structural diagram of a front-end user behavior statistics apparatus according to Embodiment 6 of the present invention;

FIG. 7 is a schematic structural diagram of a front-end user behavior statistics apparatus according to Embodiment 7 of the present invention.

detailed description

The front-end user behavior statistics method and apparatus provided by the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

Embodiment 1

As shown in FIG. 1 , it is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 1 of the present invention.

The front-end user behavior statistics method includes:

S101. Acquire a burying rule preset for the page.

In this embodiment, a burying rule is set for the page in advance, specifically, all the controls of the page are acquired, and burying rules are set for different controls according to statistical requirements. Optionally get the type of each control and set the same burying rule for all controls of the same type.

The buried point rule defines a buried point object of the page, and a statistical strategy corresponding to the buried point object is set.

During the running of the page, the burying rule of the page needs to be obtained. Specifically, when the page is started, the burying rule is loaded into the business file of the page. The business file of the page is the business process flow of the page.

S102: Listening to a page click event of the page during the running of the page.

After the user opens the page, the business file of the page can be executed, that is, the business process of the page is started, and during the process of executing the process, the page click event belonging to the page is monitored. That is to say, when the current end user clicks on the webpage, a page click event can be triggered, and the corresponding business file of the page can monitor the click event of the page.

In this embodiment, the page is buried, and when the page is loaded, the page's business file is loaded, and the corresponding point burying rule is loaded at the same time, and the function of burying the point is opened accordingly, and all the controls under the page are Page click events are monitored.

S103. After listening to the page click event, calculate behavior data of the front end user of the page based on the burying rule.

After the page click event is monitored, the target object corresponding to the page click event is determined. Further, after the target object is determined, it is necessary to determine whether the target object starts to bury the point. In this embodiment, the object that opens the buried point is defined in the burying rule, and the object of the burying point may be a button label or other specified label and the like.

In this embodiment, the burying point rule defines a statistical strategy corresponding to the burying point object and the burying point object. Two options for burying a point to open a buried point are as follows:

First, when the page is loaded, the buried point object is turned on for buried point recording. Specifically, when the preset burying rule is loaded, the burying point is automatically turned on for all the button labels and the like that belong to the page.

2. Determine whether each buried point object has a corresponding statistical strategy under the page. If the statistical strategy of the buried object is not empty, it indicates that the target object has a buried point, and the behavior data of the front-end user can be based on the statistical policy of the target object. Perform statistics. If the target object's statistical policy is empty, indicating that the target object does not open the buried point, the target object is not counted.

When it is determined that the target object has opened the burying point, it indicates that the target object can be buried and recorded, and the button, time and coordinates of the click event are optionally recorded, wherein the coordinates of the click event are positions in the page, which may also be referred to as coordinates. Further, obtaining a statistical strategy of the target object, according to the statistical policy, performing statistics on the buried point record of the target object, that is, performing statistics on the location of the click, the click event, the user ID, and the module to which the control belongs, so that Get behavior data to front-end users. For example, when the control type is a button class, that is, the corresponding HTML tag is (button/a/span), the position of the control, the click time, the user ID, the module to which the control belongs, and the application to which the current operation belongs may be recorded, if the page is clicked. If the event triggers a background request, the background request Uniform Resource Locator (URL), the time of the background request, and the background request are recorded. Success and other information. Further, after obtaining the above information of the control, when the control needs to be counted at a specific time, the statistical policy corresponding to the control is obtained according to the control and the control type of the control, and then the statistics are calculated according to the statistical policy. User behavior data for this control. In the process of using the page, the user behavior of the front-end user can be supervised based on the burying rule, so that the behavior data of the front-end user when using the page can be statistically obtained.

The front-end user behavior statistics method provided in this embodiment obtains a burying rule pre-set for the page, monitors the page click event of the page during the running of the page, and monitors the page click event based on the burying rule. Count the behavior data of the front-end users of the page. In this embodiment, in order to realize the automatic burying of the page, the burying rule is set for the page first, and the burying point is triggered by the page click event when the page is running, which solves the problem that the existing manual burying point is cumbersome and convenient. The problem, and the ability to global statistics on the behavior of the front-end users of the page, the statistical efficiency is higher.

Embodiment 2

As shown in FIG. 2, it is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 2 of the present invention. The front-end user behavior statistics method provided by this embodiment needs to be performed on the basis of modularizing the front end of the page. The front-end user behavior statistics method includes:

S201, the page is modularized.

At the moment of the rapid development of the Internet, the page has gradually become an Internet application. In order to adapt to the fierce market competition and meet the needs of users for diversification, the JS code embedded in the web page is getting larger and larger, more and more complicated, and the page is more and more More like a desktop application, it requires division of labor, progress management, unit testing, and so on. To enhance the developer's development experience and provide good support for performance optimization, developers can program the front end of the page based on modularity. The purpose of front-end modularization of the page is to enable multi-person collaborative development of the page, improve page development speed and reduce maintenance difficulty.

S202. Configure a burying rule for the page corresponding module.

In order to implement global statistics on the page, a burying rule is configured in advance for the corresponding module of the page. Specifically, all the controls, control types, and modules to which the controls belong are acquired. Since different modules can set different burying rules, a burying rule can also be set globally. Get the type of the control that needs to be buried, set the corresponding burying rule for the control type, and categorize the burying rules of the control type belonging to the same module into a file to form the burying rule of the module.

S203. Perform a service page to execute a page, and listen to a page click event in the running process.

When the current user tries to use the page, the service of the corresponding module of the page needs to be obtained before the page is run. The file, where the business file is the business process flow of the corresponding module of the page. Execute the business file, that is, run the business process of the module corresponding to the page. In this embodiment, when the service file is executed, the burying rule of the corresponding module of the page is simultaneously loaded.

During the running of the service file, the buried point object defined in the burying point rule may be used. Specifically, when the page corresponding module opens the burying point, the click events of all the controls under the module are monitored, and the corresponding module is tied according to the corresponding module. The fixed burying rule, when monitoring the control corresponding to the click event is a buried point control, obtains the behavior data of the front end user of the page.

S204. After monitoring the page click event, the behavior data of the front end user of the page is counted based on the burying point rule.

In the process of using the page, the user behavior of the front-end user can be supervised based on the burying rule, so that the behavior data of the front-end user when using the page can be statistically obtained. For details, refer to the description of related content in the foregoing Embodiment 2, and details are not described herein again.

The front-end user behavior statistics method provided by this embodiment is based on the modularization of the page, and the burying point rule is configured for the page corresponding module. When the business file of the page is executed, the corresponding burying rule is obtained, and the business file is executed. In the process, based on the burial rules, the behavior data of the front-end user of the page is obtained, and the global automatic burying of the page is realized, and the global statistics of the user behavior of the front end of the page can be obtained, and the statistical efficiency is high.

Embodiment 3

As shown in FIG. 3, it is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 3 of the present invention. The front-end user behavior statistics method provided by this embodiment needs to be performed on the basis of modularizing the front end of the page.

The front-end user behavior statistics method includes:

S301. Determine, according to the service file of the corresponding module of the page, a dependency file required for the page corresponding module to run.

Currently, in order to facilitate the optimization of the page, the developer modularizes the front end of the page. When the current user tries to use the page, the service file of the corresponding module of the page needs to be obtained before the page is run. The service file is the service processing flow of the corresponding module of the page.

Usually in the page, the module corresponding to the page in the modular process writes dependent code files according to the defined dependencies. After obtaining the business file of the corresponding module of the page, the business file is analyzed, and the dependent file required for the page corresponding module to run may be determined. The general page corresponding module includes three kinds of dependent files: HyperText Markup Language (HTML) dependent files, Cascading Style Sheets (CSS) dependent files, and JS dependent files.

S302. Load a dependency file and a burying rule configured in advance for the corresponding module of the page.

After determining the required dependency file of the corresponding module of the page, the dependent file is loaded. In this embodiment, In order to implement the global burying mechanism, a burying point rule is configured in advance for the page corresponding module, and the burying point object of the module is defined in the burying point rule. For example, the object of the buried point can be a button label or other specified label. While loading the dependent file, you also need to load the burying rules that are configured in advance for the page object module.

S303. Execute the business file based on the burying rule, and obtain the behavior data of the front end user of the page by statistics.

After the dependent file and the burying rule are loaded, the service file of the module corresponding to the page is executed, that is, the service processing flow of the corresponding module of the page is executed. In this embodiment, since the burying rule corresponding to the module is loaded, during the running of the service file, the behavior data of the front end user of the page may be obtained based on the burying point object defined in the burying rule.

Specifically, when the current end user uses the page, the user can click on the control in the page. In this embodiment, the control can be monitored. When the control that clicks on the click is a buried object, the control can be obtained. Buried record. Further, the burying point rule further includes a statistic strategy of the burying point object, and after obtaining the burying point record of the burying point object, acquiring a statistical strategy of the burying point object, if the statistic strategy of the burying point object is empty, then The buried point record of the buried point object is counted. If a statistical strategy is obtained, the buried point record is counted according to the statistical strategy.

For example, when the control type is a button class, that is, the corresponding HTML tag is (button/a/span), the position of the control, the click time, the user ID, the module to which the control belongs, and the application to which the current operation belongs may be recorded, if the click event If a background request is triggered, the background request Uniform Resource Locator (URL), the time spent in the background request, and the success of the background request are recorded. Further, after obtaining the above information of the control, when the control needs to be counted at a specific time, according to the name of the module to which the control belongs and the control type of the control, the query corresponding to the control is obtained from the background database. The statistical strategy, and then the user behavior data of the control is counted according to the statistical strategy. In this embodiment, the statistical policy is stored in the background database, so that real-time modification can be performed.

In the process of using the page, the user behavior of the front-end user can be supervised based on the burying rule, so that the behavior data of the front-end user when using the page can be statistically obtained.

The front-end user behavior statistics method provided by the embodiment determines the dependency file required to determine the running of the corresponding module of the page according to the service file of the corresponding module of the page, loads the dependent file, and pre-sets the burying rules for the corresponding module of the page, and executes the service. The file obtains the behavior data of the user at the front end of the page based on the buried point object defined in the burying rule. The embodiment provides a global burying mechanism, and writes a burying rule of the module while loading the dependent file, and can perform statistics on the behavior of the front-end user based on the burying rule, and automatically bury the page on the page, and can implement the page. Global statistics of front-end user behavior, and statistical efficiency is high.

Embodiment 4

As shown in FIG. 4, it is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 4 of the present invention. At present, RequireJS is a very small JavaScript module loading framework. In this embodiment, the RequireJS framework is selected as the underlying dependency implementation, and on this basis, the front end of the page is modularized. On the basis of the foregoing embodiment, the process of loading a preset burying rule into a service file corresponding to a page includes:

S401. Load a business file of the page.

When the front-end user tries to use the page, the service file of the corresponding module of the page needs to be called before running, where the service file is the service processing flow of the corresponding module of the page. In this embodiment, the business file of the corresponding module of the page is loaded based on the RequireJS framework, and the business file is a file JS file written with a JavaScript scripting language and with a JS extension.

S402. Parse the business file to obtain a dependency file required for the page to run.

In the process of calling the business file, the business file is parsed to obtain the dependency file of the module. In the process of modularizing the page, the dependency of the module can be defined, and the developer can write the relevant code file according to the definition of the dependency. The general page module includes three dependent files: HTML dependent files, CSS dependent files, and JS dependent files.

In this embodiment, since RequireJS only supports dependency resolution of JS dependent files, in order to implement parsing of HTML dependent files and CSS dependent files, a third-party plug-in needs to be inserted in the RequireJS framework, so that the RequireJS framework can support parsing HTML dependent files. And CSS dependent files.

S403. Encapsulating a business file.

After the required dependency file of the corresponding module of the page is parsed, the dependent file of the module is loaded. In fact, since the RequireJS framework loads the JS dependency file of the module, the business file of the module is directly executed. In this embodiment, in addition to loading the JS dependent file, the module needs to load the HTML dependent file and the CSS dependent file.

In order to perform the business process flow of the module after loading all the dependent files, the business process flow of the business file of the module is encapsulated based on the RequireJS framework in this embodiment, and the business process flow after the encapsulation will not be executed again. The package will not be executed until it is released.

S404, loading dependent files and burying rules of the page.

In the embodiment, in the embodiment, the burying point rule configured in advance for the module is loaded at the same time as the dependent file of the module is loaded. In this embodiment, the object of the burying point is opened in the code of the burying rule. Define, that is, set the buried point object of the module in the burying rule. The object to be buried can be a button label or other specified label. Specifically, button labels can be applied to all Dom files belonging to the module. (button/span/a) These objects automatically open the burying point so that all the button labels of the module can be used for burying statistics.

S405. Perform HTML template rendering and CSS rendering on the business file.

In practice, the template and the rendering of the template are required. In this embodiment, after the dependent file is loaded, the template file is used to perform HTML template rendering and CSS rendering on the business file of the module.

S406. Release the encapsulation of the service file.

After the service file of the module is rendered, the service file of the module needs to be decapsulated, so that the service file of the module can be executed.

After the module's business file is unpacked, the business file is executed based on the RequireJS framework. In the process of executing the business file, because the burying rule of the module is loaded in the business file, the click behavior of the front-end user is recorded based on the buried point object defined in the burying rule, so that the behavior data of the front-end user can be counted. .

It should be noted here that the use of RequierJS as the underlying dependency implementation is a complete example herein and is not intended as a limitation of the invention. The front-end user statistics method can also be implemented based on the underlying dependencies such as the SeaJS framework.

The front-end user behavior statistics method provided in this embodiment is to parse the service file of the service file acquisition module by loading the service file of the corresponding module of the page, to encapsulate the service processing flow of the service file, and to load the dependency file of the module and the preset point of the module. The rule is to perform HTML template rendering and CSS rendering on the business file, to unpack the business file, and execute the business file to obtain the behavior data of the front end user of the page based on the buried point object statistics defined in the burying rule. This embodiment provides a global burying mechanism, which writes a burying rule of a module while loading a dependent file, and the burying point object based on the burying point rule can perform statistics on the behavior of the front-end user, and automatically bury the page globally. Point, can achieve global statistics on the user behavior of the front end of the page, and the statistical efficiency is high.

Embodiment 5

As shown in FIG. 5, it is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 5 of the present invention. Based on the above embodiment, the front-end user behavior statistics method includes the following steps:

S501: Listening to a page click event belonging to the page in the process of executing the business file.

After the business file is loaded and rendered, the business process of the business file can be executed. During the process of executing the process, the business file monitors the page click event of the module corresponding to the subordinate page. That is to say, when the current end user clicks on the webpage, a page click event can be triggered, and the service file corresponding to the module to which the click event belongs can monitor the page click event.

In this embodiment, the page is modularized, and then the page is buryed by the module. When the module is loaded, the burying rule configured for the page is loaded at the same time, and the module is opened when the module starts to bury the point. All under The page click event of the control is monitored.

S502. Determine a target object corresponding to the monitored page click event.

After the page's business file listens to the page click event, the target object corresponding to the page click event is determined.

S503. Determine whether the target object has a buried point function.

In the above embodiment, when the business file loads the dependent file, the burying rule preset for the page is loaded at the same time. The burying point rule defines a burying point object corresponding to the page corresponding module, and sets a statistical strategy corresponding to the burying point object. In this embodiment, the object that opens the buried point is defined in the code of the buried point rule, and the object of the buried point may be a button label or other specified label and the like. In this embodiment, the burying point rule defines a statistical strategy corresponding to the burying point object and the burying point object. There are two options for opening the buried point: one is to open the buried point object for buried point recording when the page is loaded. Specifically, when the preset buried point rule is loaded, the buried point is automatically turned on for the buried point object such as the button label in all the Dom files belonging to the page. Second, it is determined whether each buried point object has a corresponding statistical strategy. If the statistical strategy of the buried point object is not empty, it indicates that the target object has the buried point function enabled, and the user's behavior data statistics can be performed based on the buried point object. If the target object's statistical policy is empty, indicating that the target object does not have the buried point function enabled, the target object is not counted.

If it is determined that the target object turns on the burying point function, then S504 is performed; otherwise, the process returns to S501.

S504: Perform a buried point record on the click behavior of the target object, and collect behavior data of the front-end user according to the buried point record and the statistical strategy of the target object.

When it is determined that the target object has opened the burying point, it indicates that the target object can be buried and recorded, and the button, time and coordinates of the click event are optionally recorded, wherein the coordinates of the click event are positions in the page, which may also be referred to as coordinates.

Further, obtaining a statistical strategy of the target object, according to the statistical policy, performing statistics on the buried point record of the target object, that is, performing statistics on the location of the click, the click event, the user ID, and the module to which the control belongs, so that Get behavior data to front-end users.

S505. Acquire a request event corresponding to the click behavior while performing a buried point record on the click behavior of the target object, and record the business logic of the request event.

Further, each click behavior of the front-end user corresponds to a request event of the webpage, and each request event has a certain business logic. In this embodiment, the click behavior of the target user is recorded, and the click behavior is recorded accordingly. The business logic of the request event.

S506. Determine whether the number of records exceeds a threshold.

If the result of the determination is no, S507 is performed; otherwise, S508 is performed.

S507. Determine whether a page refresh event or a page close event is detected during the execution of the business file.

If the result of the determination is yes, execute S508; otherwise, return to execution S501 to continue monitoring the page click event.

S508. Write the behavior data of the front-end user and the business logic of the record to the log file.

In this embodiment, the behavior data and the service logic are locally saved in the front end. After the records are full, the recorded behavior data and business logic can be written to the log file for storage in batches. That is to say, in the process of recording, the number of times of recording is compared with a preset threshold, and when the number of times of recording exceeds the threshold, the recorded behavior data and business logic are written into the log file in batches. In actual application, in order to alleviate the pressure of local storage, when the number of records exceeds the threshold, the recorded behavior data and business logic may be sent to the server for storage in batches. After receiving the behavior data and business logic, the server may follow The set data format is written to the log file.

Further, in the process of executing the service file in this embodiment, the page refresh event and the page close event of the page may be monitored, and when the page refresh event or the page close event is monitored, the recorded behavior data and the business logic are written. Into the log file. In order to avoid the loss of information, the recorded behavior data and business logic are sent to the back-end server for storage. After receiving the behavior data and business logic, the server can write to the log file according to the set data format.

Further, the log file including the behavior data is analyzed, and based on the statistical behavior data of the front-end user, the operation data of some web pages can be obtained. Among them, the number of independent visitors (Unique Visitor referred to as UV), page views or clicks (Page View referred to as PV), module heat, project heat, request time-consuming statistics, request success rate, specified button statistics , specify the module statistics of the page, click the heat map of the specified page, and so on. Further, the results of the analysis can be displayed to the developer of the webpage, and the developer can use the operational data as reference data to provide reference for actual product operation and design troubleshooting, and provide a basis for front-end interaction design.

The front-end user behavior statistics method provided in this embodiment monitors the page click event belonging to the page in the process of executing the business file of the corresponding module of the page, determines the target object corresponding to the page click event, and determines the target object. Whether it is a buried point object defined in the burying rule, when the target object turns on the burying point function, the front end user's click behavior can be buried and recorded, and the front end user's behavior data is counted according to the burying point record. In this embodiment, based on the burying rules loaded in the module, global statistics on the front-end user behavior of the webpage are obtained, and the behavior data of the global page can be obtained, which is convenient for providing reference for the later maintenance or improvement of the page.

Embodiment 6

FIG. 6 is a schematic structural diagram of a front-end user behavior statistics apparatus according to Embodiment 6 of the present invention. The front-end user behavior statistics device includes: an obtaining module 11, a listening module 12, and a statistics module 13.

The obtaining module 11 is configured to acquire a burying rule preset for the page.

During the running of the page, the obtaining module 11 needs to obtain the burying rule of the page. Specifically, when the page is started, the obtaining module 11 loads the burying rule into the business file of the page. The business file of the page is the business process flow of the page.

The monitoring module 12 is configured to monitor a page click event of the page during the running of the page.

After the user opens the page, the business file of the page can be executed, that is, the business process flow of the page is started. During the process of executing the process, the monitoring module 12 monitors the page click event belonging to the page. That is to say, when the current end user clicks on the webpage, a page click event can be triggered, and the corresponding business file of the page can monitor the click event of the page.

In this embodiment, the page is buried, and when the page is loaded, the page's business file is loaded, and the corresponding point burying rule is loaded at the same time, and the function of burying the point is opened accordingly, and all the controls under the page are Page click events are monitored by the listening module 12.

The statistics module 13 is configured to collect behavior data of the front-end user of the page based on the burying point rule after the page click event is monitored.

After the page click event is detected, the statistic module 13 determines the target object corresponding to the page click event. Further, after determining the target object, the statistic module 13 needs to determine whether the target object starts the burying point. In this embodiment, the object that opens the buried point is defined in the burying rule, and the object of the burying point may be a button label or other specified label and the like.

In this embodiment, the two alternatives for the burying point to open the burying point can be referred to the related description in the foregoing embodiment, and details are not described herein again.

When it is determined that the target object is turned on, it indicates that the target object can be buried. The statistics module 13 supervises the user behavior of the front-end user based on the statistical policy corresponding to the target object, so that the front-end user can use the statistics. Behavior data at the time. For details, refer to related descriptions in the foregoing embodiments, and details are not described herein again.

The front-end user behavior statistics device provided in this embodiment obtains a pre-set burying rule for the page, During the running of the page, the page click event of the page is monitored, and after the page click event is monitored, the behavior data of the front end user of the page is counted based on the burying point rule. In this embodiment, in order to realize the automatic burying of the page, the burying rule is set for the page first, and the burying point is triggered by the page click event when the page is running, which solves the problem that the existing manual burying point is cumbersome and convenient. The problem, and the ability to global statistics on the behavior of the front-end users of the page, the statistical efficiency is higher.

Example 7

FIG. 7 is a schematic structural diagram of a front-end user behavior statistics apparatus according to Embodiment 7 of the present invention. The front-end user behavior statistics device includes: an obtaining module 11, a listening module 12, and a statistics module 13.

In this embodiment, the statistic module 13 includes an obtaining unit 131, a determining unit 132, a recording unit 133, and a writing unit 134.

The obtaining unit 131 is configured to determine a target object corresponding to the page click event that is monitored;

The determining unit 132 is configured to determine whether the target object opens a buried point;

a recording unit 133, configured to: when the determining unit determines that the target object opens a buried point, perform a buried point recording on the click behavior of the target object, and according to the buried point record and the statistical strategy of the target object Statistics of the behavior of the front-end user.

Further, the recording unit 133 is further configured to determine a request event corresponding to the click behavior while performing a buried point recording on the click behavior of the target object, and record the business logic of the request event.

The writing unit 134 is configured to write the behavior data and the business logic into a log file when the number of times of recording exceeds a threshold.

Further, the monitoring module 12 is further configured to monitor a page refresh event or a page close event during the running of the page.

The writing unit 134 is further configured to write the behavior data and the business logic to the log file when the listening module 12 listens to the page refresh event or the page close event.

Optionally, the behavior data and the service logic are locally saved in the front end. In actual application, in order to alleviate the pressure of the local storage, the recorded behavior data and the business logic may be sent to the server in batches when the number of records exceeds the threshold. After saving, after receiving the behavior data and business logic, the server can write to the log file according to the set data format.

Optionally, after the page refresh event or the page close event is detected, in order to avoid information loss, the recorded behavior data and business logic are sent to the server at the back end for storage. After receiving the behavior data and business logic, the server can write to the log file according to the set data format.

In this embodiment, an optional structure of the obtaining module 11 includes: a modular unit 111 and an obtaining unit 112.

The modular unit 11 is configured to perform modular processing on the page.

The obtaining unit 112 is configured to load the burying rule into a service file of a module corresponding to the page when the page is started. The service file is a service processing flow of the page.

An optional structure of the obtaining unit 112 includes: a loading subunit 1121, a parsing subunit 1122, a packaging subunit 1123, a rendering subunit 1124, and a decapsulating subunit 1125.

The parsing subunit 1122 is configured to parse the service file to obtain the dependency file.

The parsing subunit 1122 is configured to parse the service file after the loading subunit 1121 loads the service file of the page corresponding module to obtain the dependent file of the page corresponding module.

The general page module has three dependent file HTML dependent files, CSS dependent files, and JS dependent files.

The loading sub-unit 1121 is specifically configured to load a business file of the page, and a burying rule of the business file in the loading page. Further, the loading sub-unit 1121 is specifically configured to load a hypertext markup language HTML dependent file, a cascading style sheet CSS dependent file, and a JS dependent file.

The encapsulation subunit 1123 is configured to encapsulate the service file.

The packaging subunit 1123 encapsulates the service processing flow of the service file before the loading subunit 1121 loads the dependency file and the burying rule configured in advance for the page corresponding module.

The decapsulation subunit 1125 is configured to release the encapsulation of the service file.

Before the statistic module 13 executes the burying point object defined by the traversing point rule of the service file, and before collecting the behavior data of the front end user of the page, the decapsulation subunit 1125 releases the encapsulation of the service file.

The rendering sub-unit 1124 is configured to perform hypertext markup language HTML template rendering and cascading style sheet CSS rendering on the business file.

Before the decapsulation subunit 1125 unpacks the business file, the business file is subjected to HTML template rendering and CSS rendering using a dependency file.

The function modules of the front-end user behavior statistics device provided in this embodiment can be used to execute the flow of the front-end user behavior statistics method shown in FIG. 1 to FIG. 5, and the specific working principle is not described here. For details, refer to the description of the method embodiment.

In this embodiment, on the basis of the modularization of the page, a burying rule is configured for the page corresponding module, and when the business file of the page is executed, the corresponding burying rule is obtained, and the burying point is performed in the process of executing the business file. The rule obtains the behavior data of the user at the front end of the page, realizes the global automatic burying of the page, and can globally count the behavior of the user at the front end of the page, and the statistical efficiency is high.

One of ordinary skill in the art will appreciate that all or part of the steps to implement the various method embodiments described above may be accomplished by hardware associated with the program instructions. The aforementioned program can be stored in a computer readable storage medium. The program, when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Finally, it should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

A front-end user behavior statistics method, comprising:

Obtain a burying rule pre-set for the page;

During the running of the page, the page click event of the page is monitored;

After the page click event is monitored, the behavior data of the front end user of the page is counted according to the buried point rule.
The front-end user behavior statistics method according to claim 1, wherein after the monitoring of the page click event, the behavior data of the front-end user of the page is calculated based on the burying point rule, including:

Determining a target object corresponding to the page click event that is monitored;

Determining whether the target object opens a buried point;

If the result of the determination is yes, the click behavior of the target object is buried, and the behavior data of the front-end user is counted according to the buried point record and a statistical policy corresponding to the target object.
The front-end user behavior statistics method according to claim 2, further comprising:

While performing a buried point recording on the click behavior of the target object, determining a request event corresponding to the click behavior, and recording a business logic of the request event.
The front-end user behavior statistics method according to claim 3, wherein the collecting the behavior data of the front-end user according to the burying point record and the statistical policy corresponding to the target object further includes:

The behavior data and the business logic are written to the log file when the number of records exceeds a threshold.
The front-end user behavior statistics method according to claim 4, wherein the calculating the behavior data of the front-end user according to the burying point record and the statistical policy corresponding to the target object further includes:

Listening to a page refresh event or a page close event during the running of the page;

The behavior data and the business logic are written to the log file when the page refresh event or the page close event is listened to.
The front-end user behavior statistics method according to any one of claims 1-5, wherein the obtaining is a pre-set burying rule for the page, including:

Modulating the page;

When the page is started, the burying rule is loaded into a service file of a module corresponding to the page;

The service file is a service processing flow of the page.
The front-end user behavior statistics method according to claim 6, wherein when the page is started, the preset burying rule is loaded into the service file of the module corresponding to the page, including:

Loading the business file of the page;

Parsing the business file to obtain a dependency file required for the page to run;

Encapsulating the business file;

Loading the dependency file and the burying rule;

Performing a hypertext markup language HTML template rendering and a cascading style sheet CSS rendering on the business file;

Unpack the business file.
The front-end user behavior statistics method according to claim 7, wherein the monitoring of the page click event of the page during the running of the page comprises:

The page is accessed by executing the business file, and the click event belonging to the page is monitored during the running process.
A front-end user behavior statistics device, comprising:

The obtaining module is configured to obtain a burying rule preset for the page;

a monitoring module, configured to monitor a page click event of the page during the running of the page;

The statistic module is configured to collect behavior data of the front end user of the page based on the burying point rule after the page click event is monitored.
The front-end user behavior statistics apparatus according to claim 9, wherein the statistics module comprises:

An obtaining unit, configured to determine a target object corresponding to the page click event that is monitored;

a determining unit, configured to determine whether the target object opens a buried point;

a recording unit, configured to: when the determining unit determines that the target object opens a buried point, perform a buried point recording on the click behavior of the target object, and perform statistics according to the buried point record and the statistical strategy of the target object. Behavior data of the front-end user.
The front-end user behavior statistics device according to claim 10, wherein the recording unit is further configured to: determine a request corresponding to the click behavior while performing a buried point recording on the click behavior of the target object An event that records the business logic of the request event.
The front-end user behavior statistics apparatus according to claim 11, wherein the statistics module further comprises:

a writing unit, configured to write the behavior data and the business logic to a log file when the number of records exceeds a threshold.
The front-end user behavior statistics device according to claim 12, wherein the monitoring module, It is also used to monitor a page refresh event or a page close event during the running of the page;

The writing unit is further configured to write the behavior data and the service logic into a log file when the listening module listens to the page refresh event or the page close event.
The front-end user behavior statistics device according to any one of claims 9 to 13, wherein the obtaining module comprises:

a modular unit for modular processing of the page;

An obtaining unit, configured to load the burying rule into a service file of a module corresponding to the page when the page is started;

The service file is a service processing flow of the page.
The apparatus for estimating the front-end user behavior according to claim 14, wherein the obtaining unit comprises:

a loading subunit, configured to load a business file of the page, a dependency file required for the page to run, and the burying rule;

a parsing subunit, configured to parse the service file to obtain the dependency file;

a packaging subunit, configured to encapsulate the service file;

a rendering subunit for performing hypertext markup language HTML template rendering and cascading style sheet CSS rendering on the business file;

The decapsulation subunit is configured to release the encapsulation of the service file.
The front-end user behavior statistics device according to claim 15, wherein the monitoring module is configured to: run the page by executing the service file, and monitor the click event belonging to the page during the running process. .