TWI753887B - Front-end user behavior statistics method and device - Google Patents

Abstract

The invention provides a front-end user behavior statistics method and device. By acquiring the pre-set burying rules for the page, during the running process of the page, the page click event of the page is monitored, and after the page click event is monitored, based on the burying rule Statistics on the behavior data of the front-end users of this page. In the present invention, in order to realize the automatic burying of the page, the burying rule is firstly set for the page, and the page click event triggers the burying to open when the page is running, which solves the problem of the existing manual burying of faults, which is cumbersome, cumbersome, and inconvenient. Moreover, it can conduct global statistics on the behavior of users at the front end of the page, and the statistical efficiency is high.

Description

Front-end user behavior statistics method and device

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

In today's rapid development of the Internet, whether as an operator of an e-commerce store or a personal webmaster, if you can understand the click behavior of users during the stay on the page, and can analyze them well, they will be very helpful. Provides the most direct and efficient assistance in improving the user experience of web pages and attracting users to click.

The user's click behavior is usually recorded by burying the page. In layman's terms, page burying is an operation that collects user access and click data through the scripting language (JavaScript, JS for short) method. When the user opens a web page and clicks, the embedded JS code in the page will be executed, and the JS code will return the collected data to the web server.

In the current tracking technology, the specified button is manually embedded, and the user's behavior is counted based on the click operation of the specified button. When it is necessary to perform global statistics on pages in practical applications, this process of manually burying points is relatively difficult. It is cumbersome and has the problem of poor convenience.

The present invention provides a front-end user behavior statistics method and device, which are used to solve the problem that the manual tracking process is cumbersome and inconvenient when performing global statistics on a page.

In order to achieve the above object, the present invention provides a front-end user behavior statistics method, which includes: acquiring a pre-set embedment rule for a page; during the running process of the page, monitoring the page click event of the page; After the page click event, the behavior data of the front-end user of the page is counted based on the point-buying rule.

In order to achieve the above purpose, the present invention provides a front-end user behavior statistics device, including: an acquisition module, used for acquiring the pre-set embed rules for the page; The page click event of the page is monitored; the statistics module is used to collect statistics on the behavior data of the front-end users of the page based on the buried point rule after monitoring the page click event.

The front-end user behavior statistics method and device provided by the present invention monitor the page click event of the page during the running process of the page by acquiring the pre-set embed rules for the page, and after monitoring the page click event, based on the embed rules Statistics on the behavior data of the front-end users of this page. In the present invention In order to realize the automatic burying of the page, first set the burying rule for the page, when the page is running, the page click event triggers the burying to open, which solves the problem of the existing manual burying of faults, which is cumbersome and inconvenient. The behavior of users at the front end of the page is counted globally, and the statistical efficiency is high.

101, 102, 103‧‧‧Method steps

201, 202, 203, 204‧‧‧Method steps

301, 302, 303‧‧‧Method steps

401, 402, 403, 404, 405, 406‧‧‧Method steps

501, 502, 503, 504, 505, 506, 507, 508‧‧‧Method steps

11‧‧‧Get the module

12‧‧‧Monitoring module

13‧‧‧Statistical module

131‧‧‧Acquisition Unit

132‧‧‧Judgment Unit

133‧‧‧Recording unit

134‧‧‧Write Unit

1121‧‧‧Load subunit

1122‧‧‧Analysis Subunit

1123‧‧‧Packaging subunits

1124‧‧‧Rendering Subunit

1125‧‧‧Decapsulating Subunits

FIG. 1 is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 1 of the present invention; FIG. 2 is a schematic flowchart of a front-end user behavior statistics method according to Embodiment 2 of the present invention; FIG. 3 is 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 statistical method according to Embodiment 4 of the present invention; FIG. 5 is a schematic flowchart of a front-end user behavior statistical method according to Embodiment 5 of the present invention; A schematic structural diagram of a user behavior statistics device; FIG. 7 is a schematic structural diagram of a front-end user behavior statistics device according to Embodiment 7 of the present invention.

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

Example 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 methods include:

S101. Acquire a pre-set embed rule for the page.

In this embodiment, a tracking rule is set for the page in advance. Specifically, all control items of the page are acquired, and tracking rules are set for different control items according to statistical requirements. Optionally obtain the type of each control item, and set the same buried rule for all control items of the same type.

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

Before the page is running, it is necessary to obtain the embedded rules of the page. Specifically, when the page is started, the embedded rules are loaded into the business file of the page. The business file of the page is the business processing flow of the page.

S102. During the running process of the page, monitor the page click event of the page.

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

In this embodiment, a page is buried, and when the page is started, that is, when the business file of the page is loaded, the corresponding buried rules of the page are loaded at the same time, and the function of buried points is enabled accordingly. page of controls Surface click events are monitored.

S103, after monitoring the click event of the page, statistics the 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 has a buried point enabled. In this embodiment, the object that enables the buried point is defined in the buried point rule, and the buried point object may be a control item such as a button label or other specified label.

In this embodiment, the buried point rule defines the buried point object and the statistical strategy corresponding to the buried point object. There are two optional ways to enable buried objects for buried objects as follows:

First, when the page is loaded, the buried point object will be opened to record the buried point. Specifically, when the preset embed rules are loaded, embeds are automatically enabled for all embed objects such as button labels that belong to the page.

2. Determine whether each buried point object under the page has a corresponding statistical strategy. If the statistical strategy of the buried point object is not empty, it means that the target object has enabled the buried point. Based on the statistical strategy of the target object, the behavior data of front-end users can be analyzed. Do statistics. If the statistics strategy of the target object is empty, it means that the target object has not opened the buried point, and the statistics of the target object will not be calculated.

When it is determined that the target object has enabled tracking, it means that the tracking can be recorded for the target object, optionally recording the button, time, and coordinates of the click event, where the coordinates of the click event are the positions on the page, which can also be called coordinates. Further, obtain the statistical strategy of the target object, according to the statistical strategy It is possible to perform statistics on the buried point records of the target object, that is, statistics on the clicked location, click event, user ID, module to which the control item belongs, etc., so as to obtain the behavior data of front-end users. For example, when the control item type is a button class, that is, the corresponding HTML tag is (button/a/span), the position of the control item, the click time, the user ID, the module to which the control item belongs, and the application to which the current operation belongs can be recorded. If the click event of the page triggers a background request, information such as the background request uniform resource locator (Uniform Resource Locator, URL for short), the time-consuming of the background request, and whether the background request is successful is recorded. Further, after obtaining the above-mentioned information of the control item, when the control item needs to be counted at a specific time, the statistical strategy corresponding to the control item is obtained according to the control item and the control item type of the control item, and then According to the statistical strategy, the user behavior data of the control item are collected. In the process of using the page, the user behavior of the front-end user can be supervised based on the buried point rules, so that the behavior data of the front-end user when using the page can be obtained statistically.

In the front-end user behavior statistics method provided by this embodiment, by acquiring the pre-set embed rules for the page, during the running process of the page, the page click event of the page is monitored, and after the page click event is monitored, statistics are made based on the embed rules. The behavior data of the front-end users of this page. In this embodiment, in order to realize the automatic tracking of the page, first set the tracking rule for the page, and when the page is running, the page click event triggers the tracking to open, which solves the problem of the existing manual tracking, which is cumbersome and inconvenient. , and can conduct global statistics on the behavior of users at the front end of the page, with high statistical efficiency.

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 in this embodiment needs to be executed on the basis of modularizing the front-end of the page. The front-end user behavior statistics methods include:

S201 , modularizing the page.

With the rapid development of the Internet, pages have gradually become Internet applications. In order to adapt to the fierce market competition and meet the diverse needs of users, the JS codes embedded in web pages are becoming larger and more complex, and the pages are becoming more and more complex. More like a desktop program, it requires division of labor, progress management, unit testing, and more. In order to improve the developer's development experience and provide good support for performance optimization, developers can program the front end of the page based on modularization. The purpose of front-end modularization of the page can realize the collaborative development of pages by multiple people, improve the speed of page development and reduce the difficulty of maintenance.

S202. Configure a point-embedding rule for the module corresponding to the page.

In order to achieve global statistics on the page, configure the embedded point rules for the module corresponding to the page in advance. Specifically, obtain all control items, control item types, and modules to which each control item belongs on the page. Since different modules can set different tracking rules, you can also set a global tracking rule. Get the control item type that needs to be buried, set the corresponding buried point rule for the control item type, and summarize the buried point rules of the control item type belonging to the same module into a file to form the module's buried point rule.

S203 , by executing the business file running page, during the running process, monitor the click event belonging to the page.

When the current end user tries to use the page, before running the page, it is necessary to obtain the business file of the module corresponding to the page, wherein the business file is the business processing flow of the module corresponding to the page. Executing the business file means running the business processing flow of the module corresponding to the page. In this embodiment, when the business file is executed, the embedded point rules of the module corresponding to the page will be loaded at the same time.

During the running process of the business file, it can be based on the embedded objects defined in the embedded rules. Specifically, when the corresponding module on the page has enabled embedded, the click events of all control items under the module are monitored, according to the The embedded point rule bound by the corresponding module, when the control item corresponding to the click event is monitored as the control item of the embedded point, the behavior data of the front-end user of the page is obtained.

S204 , after monitoring the page click event, statistics the behavior data of the user at the front end of the page based on the burying rule.

In the process of using the page, the user behavior of the front-end user can be supervised based on the buried point rules, so that the behavior data of the front-end user when using the page can be obtained statistically. For a specific process, reference may be made to the description of the relevant content in the above-mentioned Embodiment 2, which will not be repeated here.

In the front-end user behavior statistics method provided in this embodiment, on the basis of modularization of the page, a burying rule is configured for the module corresponding to the page. When the business file of the page is executed, the corresponding burying rule is obtained, and the In the process of the business file, based on the tracking rules, the behavior data of the front-end users of the page is obtained, and the global automatic tracking of the page can be realized.

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 in this embodiment needs to be executed on the basis of modularizing the front-end of the page.

The front-end user behavior statistics methods include:

S301 , according to the business file of the module corresponding to the page, determine the dependency file required when the module corresponding to the page runs.

At present, in order to facilitate the optimization of the page, the developer conducts modular programming on the front end of the page. When the current end user tries to use the page, before running the page, it is necessary to obtain the business file of the module corresponding to the page, wherein the business file is the business processing flow of the module corresponding to the page.

Usually in the page, the module corresponding to the page writes the dependent code files according to the defined dependencies during the modularization process. After obtaining the business file of the module corresponding to the page, analyzing the business file can determine the dependency file required when the module corresponding to the page runs. A general page corresponding module includes three dependency files: HyperText Markup Language (HTML for short) dependency file, Cascading Style Sheets (CSS for short) dependency file and JS dependency file.

S302, load the dependency file and the pre-configured burying rules for the module corresponding to the page.

After the required dependency file of the module corresponding to the page is determined, the dependency file is loaded. In this embodiment, in order to realize the global tracking mechanism, a tracking rule is configured for the module corresponding to the page in advance. Embed objects with mods are limited. For example, buried objects can be button labels or other specific labels. When loading the dependent files, it is also necessary to load the pre-configured page objects. Embedding rules for component module configuration.

S303 , the execution business file is based on the embedded point rule to obtain the behavior data of the front-end user of the page by statistics.

After the dependency files and embedded rules are loaded, execute the business file of the module corresponding to the page, that is, run the business processing process of the module corresponding to the page. In this embodiment, since the embedded point rule corresponding to the module is loaded, during the running process of the business file, the behavior data of the user at the front end of the page can be obtained based on the embedded point object defined in the embedded point rule.

Specifically, when the current end user is using the page, he can click the control item in the page. In this embodiment, the control item can be monitored, and when the clicked control item is monitored to be a buried object, it can be obtained. Buried point record of this control item. Further, the burying rule also includes a statistical strategy of the buried object. After obtaining the buried record of the buried object, the statistical strategy of the buried object is obtained. If the statistical strategy of the buried object is empty, it is not valid. The buried point record of the buried point object is counted, and if a statistical strategy is obtained, the buried point record is counted according to the statistical strategy.

For example, when the control item type is a button class, that is, the corresponding HTML tag is (button/a/span), the position of the control item, the click time, the user ID, the module to which the control item belongs, and the application to which the current operation belongs can be recorded. If the click event triggers a background request, information such as a background request uniform resource locator (Uniform Resource Locator, URL for short), the time-consuming of the background request, and whether the background request is successful is recorded. Further, after obtaining the above-mentioned information of the control item, when the control item needs to be counted at a specific time, according to the name of the module to which the control item belongs and the For the control item type of the control item, the statistical strategy corresponding to the control is obtained by querying from the background database, and then the user behavior data of the control item is counted according to the statistical strategy. In this embodiment, the statistical strategy is stored in the background database, so that it can be modified in real time.

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

The front-end user behavior statistics method provided in this embodiment determines the dependency files required when the page-corresponding module runs according to the business file of the page-corresponding module, loads the dependency file and pre-configured embedded points for the page-corresponding module Rules, execute the business file based on the embedded objects defined in the embedded rules to obtain the behavior data of the front-end users of the page. This embodiment provides a global tracking mechanism, which writes the tracking rules of the module while loading the dependency file. Based on the tracking rules, the behavior of front-end users can be counted, and the global automatic tracking of the page can be realized. Global statistics on user behavior at the front end of the page, and the statistical efficiency is high.

Embodiment 4

As shown in FIG. 4 , it is a schematic flowchart of a method for statistics of front-end user behavior according to Embodiment 4 of the present invention. Currently RequireJS is a very small JavaScript module loading architecture. In this embodiment, the RequireJS architecture is selected as the underlying dependency implementation, and on this basis, the front-end modularization of the page is realized. On the basis of the above-mentioned embodiment, the process of loading the preset burying rules into the business file corresponding to the page includes:

S401. Load the business file of the page.

When the front-end user tries to use the page, before running, the business file of the module corresponding to the page needs to be called, wherein the business file is the business processing flow of the module corresponding to the page. In this embodiment, the business file of the module corresponding to the page is loaded based on the RequireJS architecture, and the business file is a file JS file with JS as the file extension, which is written in the JavaScript instruction code language.

S402 , parse the business file to obtain the dependency file required when the page runs.

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 page modularization, the dependencies of modules can be defined, and developers can write relevant code files according to the definition of dependencies. A general page module includes three types of dependencies: HTML dependencies, CSS dependencies, and JS dependencies.

In this embodiment, since RequireJS only supports dependency parsing of JS dependency files, in order to realize the parsing of HTML dependency files and CSS dependency files, it is necessary to insert third-party plug-ins into the RequireJS architecture, so that the RequireJS architecture can support parsing HTML dependencies files and CSS dependencies.

S403, encapsulating the business file.

After parsing the required dependency file of the module corresponding to the page, load the module's dependency file. In fact, due to the RequireJS architecture, after the module's JS dependency file is loaded, the module's business will be directly executed. files. In this embodiment, in addition to loading the JS dependency file, the module also needs to load the HTML dependency file and the CSS dependency file.

In order to execute the business processing flow of the module after all the dependency files are loaded, in this embodiment, the business processing flow of the business file of the module is encapsulated based on the RequireJS architecture, and the business processing flow will not be executed after the encapsulation. , will only be executed after the package is released.

S404, load the embedded point rule of the dependent file and the page.

In order to realize the mechanism of global statistics on the page, in this embodiment, when loading the dependency file of the module, the embedded rules pre-configured for the module are loaded. It is defined in the code of the rule, that is to say, the buried point object of this module is set in the buried point rule. Embedding objects can be button labels or other specific labels. Specifically, the button labels (button/span/a) in all Dom files belonging to the module can be automatically enabled for tracking, so that tracking statistics can be performed through all the button labels of the module.

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

In practice, templates and styles of pages need to be rendered. In this embodiment, after the loading of the dependency files is completed, HTML template rendering and CSS rendering are performed on the business files of the module based on the dependency files.

S406. Unencapsulate the service file.

After rendering the business file of the module, since the business file of the module has been encapsulated before, the business processing flow of the business file needs to be decapsulated so that the business file of the module can be executed.

After unpacking the business file of the module, execute the business file based on the RequireJS architecture. In the process of executing the business file, since the embedded rules of the module are loaded in the business file, based on the embedded objects defined in the embedded rules The software is used to record the click behavior of front-end users, so that the behavior data of front-end users can be counted.

It should be noted here that the use of RequierJS as the underlying dependency implementation is a complete example here, and is not a condition for limiting the present invention. The front-end user statistics method can also be implemented based on underlying dependencies such as the SeaJS architecture.

The front-end user behavior statistics method provided in this embodiment, by loading the business file of the corresponding module on the page, parses the business file to obtain the module's dependency file, encapsulates the business processing flow of the business file, and loads the module's dependency file and module. Set preset embed rules, perform HTML template rendering and CSS rendering for business files, unencapsulate business files, and execute business files to obtain behavior data of front-end users based on the statistics of embed objects defined in the embed rules. This embodiment provides a global tracking mechanism, which writes the tracking rules of the module while loading the dependency file. Based on the tracking objects in the tracking rules, the behavior of the front-end users can be counted, and the global automatic tracking of the page can be calculated. Buried points can realize global statistics of user behavior on 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 method for statistics of front-end user behavior according to Embodiment 5 of the present invention. On the basis of the foregoing embodiment, the front-end user behavior statistics method includes the following steps:

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

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

In this embodiment, the page is modularized, and then the page should be embedded in the module. When the module is loaded, the embedded rules configured for the page are loaded at the same time, and the embedded point is enabled in the module. In the case of , the page click events of all control items under this module will be monitored.

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

When the business file of the page monitors the page click event, it determines the target object corresponding to the page click event.

S503, judging whether the target object has a buried point function enabled.

In the above embodiment, when the business file loads the dependency file, the pre-set embed rules for the page are loaded at the same time. Among them, the buried point rule defines the buried point object of the module corresponding to the page, and sets a statistical strategy corresponding to the buried point object. In this embodiment, the object that enables the buried point is defined in the code of the buried point rule, and the buried point object may be a control item such as a button label or other specified labels. In this embodiment, the buried point rule defines the buried point object and the statistical strategy corresponding to the buried point object. There are two optional ways to enable burying points: one is to open the burying point object to record the burying points when the page is loaded. Specifically, when the preset embed rules are loaded, embeds are automatically enabled for embed objects such as button labels in all Dom files belonging to the page. 2. Determine whether each buried object has a corresponding statistical strategy. If the statistics of the buried object If the policy is not empty, it means that the target object has enabled the tracking function, and the user's behavior data can be counted based on the tracking object. If the statistics strategy of the target object is empty, it means that the target object does not have the buried point function enabled, and the statistics of the target object will not be counted.

If it is determined that the target object has the function of burying points enabled, execute S504; otherwise, return to execute S501.

S504 , performing an embed record on the click behavior of the target object, and statistics the behavior data of the front-end user according to the embed record and the statistical strategy of the target object.

When it is determined that the target object has enabled tracking, it means that the tracking can be recorded for the target object, optionally recording the button, time, and coordinates of the click event, where the coordinates of the click event are the positions on the page, which can also be called coordinates.

Further, the statistical strategy of the target object is obtained, and the buried point records of the target object can be counted according to the statistical strategy, that is, the information such as the clicked position, the clicked event, the user ID, the module to which the control item belongs can be counted, Thereby, the behavior data of front-end users can be obtained.

S505 , while recording the click behavior of the target object, obtain a request event corresponding to the click behavior, and record the business logic of the request event.

Further, each click behavior of the front-end user will correspond to a request event of the web page, and each request event will have a certain business logic. In this embodiment, while recording the click behavior of the target user, the corresponding click behavior is recorded. The business logic of the request event.

S506. Determine whether the number of times of recording exceeds a threshold.

If the judgment result is no, execute S507; otherwise, execute S508.

S507: Determine whether a page refresh event or a page close event is monitored during the process of executing the business file.

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

S508: Write the behavior data of the front-end user and the recorded business logic into the log file.

In this embodiment, the behavior data and business logic are first stored locally at the front end, and when N records are filled, the recorded behavior data and business logic can be written into the log file in batches for preservation. That is to say, in the process of recording, the number of records is compared with a preset threshold, and when the number of records exceeds the threshold, the recorded behavior data and business logic are written into the log file in batches. In practical applications, in order to relieve the pressure on the local storage area, when the number of records exceeds the threshold, the recorded behavior data and business logic can be sent to the server in batches 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, in this embodiment, in the process of executing the business file, the page refresh event and page close event of the page can also be monitored, and when the page refresh event or the page close event is monitored, the recorded behavior data and 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 preservation. After the server receives the behavior data and business logic, it can follow the set data. The material format is written to the log file.

Further, the log file containing the behavior data is analyzed, and based on the collected behavior data of the front-end user, the operation data of some web pages can be obtained. Among them, the operation data can include the number of unique visitors (Unique Visitor referred to as UV), the number of page views or clicks (Page View referred to as PV), module popularity, project popularity, request time-consuming statistics, request success rate, designated buttons statistics, some module statistics of the specified page, click heat map of the specified page, etc. Further, the analysis results can be displayed to the developer of the web page, and the developer can use these operation materials as reference materials to provide reference for actual product operation, design troubleshooting, and provide a basis for front-end interaction design.

In the front-end user behavior statistics method provided in this embodiment, in the process of executing the business file of the module corresponding to the page, by monitoring the page click event belonging to the page, determining the target object corresponding to the monitored page click event, and judging the target Whether the object is a buried point object defined in the buried point rule, when the target object enables the buried point function, the front-end user's click behavior can be buried and recorded, and the front-end user's behavior data can be counted according to the buried point record. This embodiment implements global statistics on the front-end user behavior of the web page based on the embedded point rules loaded in the module, and can obtain behavior data of the entire page, which is convenient for providing reference for later maintenance or improvement of the page.

Embodiment 6

As shown in FIG. 6 , it 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: Take module 11, monitoring module 12 and statistics module 13.

Among them, the obtaining module 11 is used to obtain the embedded point rules preset for the page.

In this embodiment, a tracking rule is set for the page in advance. Specifically, all control items of the page are acquired, and tracking rules are set for different control items according to statistical requirements. Optionally obtain the type of each control item, and set the same buried rule for all control items of the same type.

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

Before the page is running, the acquisition module 11 needs to acquire the embedded point rules of the page. Specifically, when the page is started, the acquisition module 11 loads the embedded point rules into the business file of the page. The business file of the page is the business processing flow of the page.

The monitoring module 12 is used for monitoring the page click event of the page during the running process of the page.

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

In this embodiment, a page is buried, and when the page is started, that is, when the business file of the page is loaded, the corresponding buried rules of the page are loaded at the same time, and the function of buried points is enabled accordingly. page of controls The face click event will be monitored by the monitoring module 12 .

The statistics module 13 is used for, after monitoring the click event of the page, to count the behavior data of the front-end users of the page based on the burying rules.

After monitoring the page click event, the statistics module 13 determines the target object corresponding to the page click event. Further, after determining the target object, the statistics module 13 needs to determine whether the target object has a buried point enabled. In this embodiment, the object that enables the buried point is defined in the buried point rule, and the buried point object may be a control item such as a button label or other specified label.

In this embodiment, for the two optional ways for the buried object to open the buried point, reference may be made to the relevant records in the above-mentioned embodiment, which will not be repeated here.

When it is determined that the target object has enabled tracking, it means that tracking records can be performed on the target object. The statistics module 13 supervises the user behavior of the front-end user based on the statistical strategy corresponding to the target object, so that it can be statistically obtained that the front-end user is using behavioral data at the time of the page. For specific content, reference may be made to the relevant records in the foregoing embodiments, which will not be repeated here.

The front-end user behavior statistics device provided by this embodiment, by acquiring the pre-set burying rules for the page, monitors the page click events of the page during the running process of the page, and after monitoring the page click events, collects statistics based on the burying rules The behavior data of the front-end users of this page. In this embodiment, in order to realize the automatic tracking of the page, first set the tracking rule for the page, and when the page is running, the page click event triggers the tracking to open, which solves the problem of the existing manual tracking, which is cumbersome and inconvenient. , and can conduct global statistics on the behavior of users at the front end of the page, with high statistical efficiency.

Embodiment 7

As shown in FIG. 7 , it 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 acquisition module 11 , a monitoring module 12 and a statistics module 13 .

In this embodiment, an optional structural manner of the statistics module 13 includes: an acquisition unit 131 , a judgment unit 132 , a recording unit 133 and a writing unit 134 .

Among them, the acquiring unit 131 is used to determine the target object corresponding to the monitored page click event; the judging unit 132 is used to judge whether the target object has a buried point; the recording unit 133 is used to judge in the judging unit When the target object is turned on for tracking, a tracking record is performed on the click behavior of the target object, and the behavior data of the front-end user is counted according to the tracking record and the statistical strategy of the target object.

Further, the recording unit 133 is further configured to determine a request event corresponding to the click behavior while recording 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 records 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, when the monitoring module 12 monitors the page refresh event or the page close event, convert the behavior data to the The business logic is written to the log file.

Optionally, the behavior data and business logic are stored locally at the front end. In practical applications, in order to relieve the pressure on the local storage area, when the number of records exceeds the threshold, the recorded behavior data and business logic can be sent to the server in batches. It is stored on the server. After receiving the behavior data and business logic, the server can write it into the log file according to the set data format.

Optionally, when a page refresh event or a page close event is monitored, in order to avoid information loss, the recorded behavior data and business logic are sent to the back-end server for storage. After the server receives the behavior data and business logic, it can write it into the log file according to the set data format.

In this embodiment, an optional structural manner of the acquisition module 11 includes: a modularization unit 111 and an acquisition unit 112 .

Wherein, the modularization unit 11 is used for modularizing the page.

The obtaining unit 112 is configured to load the embedded point rule into the business file of the module corresponding to the page when the page is started. Wherein, the business file is the business processing flow of the page.

An optional structural manner of the acquiring 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 business file to obtain the dependency file.

The parsing subunit 1122 is used to load the page pair in the loading subunit 1121 After responding to the business file of the module, parse the business file to obtain the dependency file of the corresponding module on the page.

A general page module will have three types of dependencies: HTML dependencies, CSS dependencies, and JS dependencies.

The loading subunit 1121 is specifically used to load the business file of the page, and to load the embedded rules of the business file of the page. Further, the loading subunit 1121 is specifically configured to load the HTML dependency file of the hyperdocument markup language, the CSS dependency file of the Cascading Style Sheet and the JS dependency file.

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

Before the loading sub-unit 1121 loads the dependency file and the embedded point rules pre-configured for the page-corresponding module, the encapsulating sub-unit 1123 encapsulates the business processing flow of the business file.

The decapsulation subunit 1125 is used to decapsulate the service file.

Before the statistics module 13 executes the embedded object defined by the business file based on the embedded rules, and obtains the behavior data of the user at the front end of the page by statistics, the decapsulation sub-unit 1125 decapsulates the business file.

The rendering subunit 1124 is used for rendering the HTML template of the hyperdocument markup language and the CSS rendering of the cascading style sheet for the business document.

Before the decapsulation subunit 1125 decapsulates the business file, HTML template rendering and CSS rendering are performed on the business file using the dependency file.

Each functional module 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 FIGS. described.

In this embodiment, on the basis that the page is modularized, a burying rule is configured for the module corresponding to the page. When the business file of the page is executed, the corresponding burying rule is obtained. In the process of executing the business file, based on the Embedding rules, to obtain the behavior data of the front-end users of the page, to realize the automatic burying of the whole domain of the page, and to be able to conduct global statistics on the user's behavior at the front-end of the page, and the statistical efficiency is high.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by program instructions related to hardware. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps including the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features thereof can be equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the embodiments of the present invention. Scope.

Claims (14)

A front-end user behavior statistics method, characterized in that, the front-end user behavior statistics method comprises: acquiring a pre-set embedment rule for a page; monitoring a page click event of the page during the running process of the page; After the click event of the page, the behavior data of the front-end user of the page is counted based on the tracking rule. The front-end user behavior statistics method, wherein, after the click event of the page is monitored, the front-end of the page is counted based on the tracking rule. The behavior data of the user, including: determining the target object corresponding to the monitored click event on the page; judging whether the target object has a buried point enabled, wherein the target event for enabling the buried point is defined in the buried point rule; and if it is judged The result is that the click behavior of the target object is tracked and recorded, and the behavior data of the front-end user is counted according to the track record and the statistical strategy corresponding to the target object. The front-end user behavior statistics method according to item 1 of the scope of the patent application, further comprising: while recording the click behavior of the target object, determining a request event corresponding to the click behavior, and determining the request event corresponding to the click behavior. The business logic is recorded. The front-end user behavior statistical method according to item 2 of the scope of the application, wherein the statistical data corresponding to the target object is based on the buried point record. After calculating the behavior data of the front-end user by the counting strategy, the method further includes: when the number of records exceeds the threshold, writing the behavior data and the business logic into the log file. According to the method for statistics of front-end user behavior described in item 3 of the scope of application for patent, wherein after collecting the behavior data of the front-end user according to the buried point record and the statistical strategy corresponding to the target object, the method further includes: a process of running on the page , monitor the page refresh event or the page close event; and when the page refresh event or the page close event is monitored, write the behavior data and the business logic into the log file. The front-end user behavior statistics method according to any one of items 1 to 4 of the scope of the patent application, wherein the acquiring the pre-set embedment rules for the page includes: modularizing the page; When the page is displayed, the embedded point rule is loaded into the business file of the module corresponding to the page, where the business file is the business processing flow of the page. The front-end user behavior statistics method according to item 5 of the scope of the patent application, wherein when starting the page, the preset embedment rules are loaded into the business file of the module corresponding to the page, including: loading The business file of the page; parse the business file to obtain the dependency file required for the page to run; encapsulate the business file; Load the dependency file and the embedding rule; perform the HTML template rendering of the hyperfile markup language and the CSS rendering of the cascading style sheet for the business file; and unencapsulate the business file. According to the front-end user behavior statistics method described in item 6 of the scope of the patent application, the monitoring of the page click event of the page during the running process of the page includes: running the page by executing the business file, and during the running process Monitor the click events belonging to the page. A front-end user behavior statistics device, characterized in that, the front-end user behavior statistics device includes: an acquisition module for acquiring pre-set embedment rules for a page; a monitoring module for in the running process of the page, The page click event of the page is monitored; and the statistics module is used to count the behavior data of the front-end users of the page based on the buried point rule after monitoring the click event of the page. The statistics module includes: an acquisition unit, used for Determine the target object corresponding to the monitored click event on the page; a judging unit for judging whether the target object opens a buried point, wherein the target event for opening the buried point is defined in the buried point rule; and a recording unit, with When the judging unit determines that the target object is enabled to track the target object, the click behavior of the target object is tracked and recorded, and according to the track record and the statistical strategy of the target object, the behavior of the front-end user is counted. for data. The front-end user behavior statistics device according to item 8 of the scope of the patent application, wherein the recording unit is further configured to determine the request event corresponding to the click behavior while recording the click behavior of the target object, Record the business logic of the request event. The front-end user behavior statistics device according to item 9 of the scope of the patent application, wherein the statistics module further includes: a writing unit for writing the behavior data and the business logic when the number of records exceeds a threshold log file. The front-end user behavior statistics device according to item 10 of the scope of the application, wherein the monitoring module is further configured to monitor the page refresh event or the page close event during the running process of the page; and the writing unit , and is also used to write the behavior data and the business logic into the log file when the monitoring module monitors the page refresh event or the page close event. The front-end user behavior statistics device according to any one of items 8 to 11 of the scope of the patent application, wherein the acquisition module includes: a modular unit for performing modular processing on the page; and an acquisition unit , which is used to load the embedded point rule into the business file of the module corresponding to the page when the page is started, where the business file is the business processing flow of the page. The front-end user behavior statistics device according to item 12 of the scope of the application, wherein the acquiring unit includes: a loading sub-unit for loading the business file of the page, the page running The required dependency file and the burying rule; the parsing sub-unit is used to parse the business file to obtain the dependency file; the encapsulation sub-unit is used to encapsulate the business file; the rendering sub-unit is used for the business file Rendering the HTML template of the hyperfile markup language and the CSS rendering of the cascading style sheet; and decapsulating the subunit for decapsulating the business document. The front-end user behavior statistics device according to item 13 of the scope of the application, wherein the monitoring module is specifically used to run the page by executing the business file, and monitor click events belonging to the page during the running process.

Images