CN107295050B - Front-end user behavior statistical method and device - Google Patents

Front-end user behavior statistical method and device Download PDF

Info

Publication number
CN107295050B
CN107295050B CN201610204743.XA CN201610204743A CN107295050B CN 107295050 B CN107295050 B CN 107295050B CN 201610204743 A CN201610204743 A CN 201610204743A CN 107295050 B CN107295050 B CN 107295050B
Authority
CN
China
Prior art keywords
page
end user
file
behavior
event
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201610204743.XA
Other languages
Chinese (zh)
Other versions
CN107295050A (en
Inventor
罗健
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201610204743.XA priority Critical patent/CN107295050B/en
Priority to TW106107619A priority patent/TWI753887B/en
Priority to PCT/CN2017/077244 priority patent/WO2017167042A1/en
Publication of CN107295050A publication Critical patent/CN107295050A/en
Application granted granted Critical
Publication of CN107295050B publication Critical patent/CN107295050B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/535Tracking the activity of the user
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201Market modelling; Market analysis; Collecting market data

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Marketing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention provides a front-end user behavior statistical method and a device, wherein a page click event of a page is monitored in the page running process by acquiring a preset embedded point rule for the page, and behavior data of a front-end user of the page is counted based on the embedded point rule after the page click event is monitored. In order to realize automatic point burying of the page, a point burying rule is firstly set for the page, and the point burying starting is triggered by a page clicking event when the page runs, so that the problem that the prior manual point burying has complex mistake and poor convenience is solved, the behavior of a front-end user of the page can be subjected to global statistics, and the statistical efficiency is high.

Description

Front-end user behavior statistical method and device
Technical Field
The invention relates to the technical field of data processing, in particular to a front-end user behavior statistical method and device.
Background
Today, whether it is the operator of an e-commerce store or a personal captain, the rapid growth of the internet, if it is possible to keep track of some of the user's clicks during the residence of the page and to analyze them well, will provide the most immediate and efficient help in improving the user experience of the web page and attracting the user's clicks.
Usually, a click behavior of a user is recorded by performing a point burying operation on a page, and in a popular way, the point burying of the page is an operation of collecting data accessed and clicked by the user through a scripting language (JavaScript, JS for short). When a user opens a webpage and clicks, a JS code embedded in the webpage is executed, and the JS code returns collected data to a website server.
In the current point burying technology, a point is buried for a designated button manually, and the behavior of a user is counted based on the clicking operation of the designated button. In practical application, the page needs to be subjected to global statistics, and the manual point burying process is complicated, so that the problem of poor convenience exists.
Disclosure of Invention
The invention provides a front-end user behavior statistical method and device, which are used for solving the problems of complexity and poor convenience in a manual point burying process when a page is subjected to global statistics.
In order to achieve the above object, the present invention provides a front-end user behavior statistical method, which comprises:
acquiring a preset embedding point rule for a page;
monitoring a page click event of the page in the page operation process;
and after the page click event is monitored, counting behavior data of a user at the front end of the page based on the buried point rule.
In order to achieve the above object, the present invention provides a front-end user behavior statistics apparatus, including:
the acquisition module is used for acquiring a preset embedded point rule for the page;
the monitoring module is used for monitoring the page click event of the page in the page running process;
and the statistical module is used for counting the behavior data of the front-end user of the page based on the embedded point rule after the page click event is monitored.
According to the front-end user behavior statistical method and device provided by the invention, the page click event of the page is monitored in the page running process by acquiring the preset embedded point rule for the page, and after the page click event is monitored, the behavior data of the front-end user of the page is counted based on the embedded point rule. In order to realize automatic point burying of the page, a point burying rule is firstly set for the page, and the point burying starting is triggered by a page clicking event when the page runs, so that the problem that the prior manual point burying has complex mistake and poor convenience is solved, the behavior of a front-end user of the page can be subjected to global statistics, and the statistical efficiency is high.
Drawings
Fig. 1 is a schematic flow chart illustrating a front-end user behavior statistical method according to a first embodiment of the present invention;
FIG. 2 is a flowchart illustrating a front-end user behavior statistical method according to a second embodiment of the present invention;
fig. 3 is a schematic flow chart illustrating a front-end user behavior statistical method according to a third embodiment of the present invention;
fig. 4 is a schematic flow chart illustrating a front-end user behavior statistical method according to a fourth embodiment of the present invention;
fig. 5 is a schematic flow chart of a front-end user behavior statistical method according to a fifth embodiment of the present invention;
fig. 6 is a schematic structural diagram of a front-end user behavior statistics apparatus according to a sixth embodiment of the present invention;
fig. 7 is a schematic structural diagram of a front-end user behavior statistics apparatus according to a seventh embodiment of the present invention.
Detailed Description
The following describes in detail a front-end user behavior statistical method and apparatus provided by the embodiments of the present invention with reference to the accompanying drawings.
Example one
Fig. 1 is a schematic flow chart of a front-end user behavior statistical method according to a first embodiment of the present invention.
The front-end user behavior statistical method comprises the following steps:
s101, acquiring a preset embedded point rule for the page.
In this embodiment, a dot embedding rule is set for the page in advance, specifically, all the controls of the page are obtained, and the dot embedding rule is set for different controls according to statistical requirements. Optionally obtaining the type of each control, and setting the same embedded point rule for all the controls of the same type.
Wherein, the embedded point rule defines the embedded point object of the page, and a statistical strategy corresponding to the embedded point object is set.
During the operation of the page, the embedded point rule of the page needs to be acquired, and specifically, when the page is started, the embedded point rule is loaded into a service file of the page. The service file of the page is a service processing flow of the page.
S102, monitoring a page click event of the page in the page running process.
After a user opens a page, a service file of the page can be executed, namely a service processing flow of the page is started, and a page click event belonging to the page is monitored in the process of executing the processing flow. That is to say, when the front-end user clicks a page on a web page, a page click event can be triggered, and the service file corresponding to the page can monitor the page click event.
In this embodiment, a page is embedded, when the page is started, that is, when a service file of the page is loaded, a rule of embedding the point corresponding to the page is loaded at the same time, and accordingly, a function of embedding the point is started, and page click events of all controls under the page are monitored.
S103, after the page click event is monitored, behavior data of a user at the front end of the page are counted based on a buried point rule.
After a page click event is monitored, a target object corresponding to the page click event is determined, and further, after the target object is determined, whether the target object opens a buried point or not needs to be judged. In this embodiment, the object for opening the buried point is defined in the buried point rule, and the object for buried point may be a button label or other designated control such as a label.
In this embodiment, the embedded point rule defines the embedded point object and the statistical strategy corresponding to the embedded point object. Two alternatives for the buried object to open the buried point are as follows:
firstly, the embedded point object is opened to carry out embedded point recording when the page is loaded. Specifically, when a preset embedding rule is loaded, embedding is automatically started for all embedding objects such as button labels belonging to the page.
And secondly, judging whether each embedded point object under the page has a corresponding statistical strategy, if the statistical strategy of the embedded point object is not null, indicating that the embedded point is opened by the target object, and counting the behavior data of the front-end user based on the statistical strategy of the target object. And if the statistical strategy of the target object is null, the target object is not counted if the target object does not open the buried point.
When the buried point is judged to be opened by the target object, the buried point record can be performed on the target object, and optionally, the button, time and coordinate of the click event are recorded, wherein the coordinate of the click event is the position in the page and can also be called as the coordinate. Furthermore, a statistical strategy of the target object is obtained, the buried point record of the target object can be counted according to the statistical strategy, that is, information of a click position, a click event, a user ID, a module to which the control belongs and the like can be counted, so that behavior data of the front-end user can be obtained. For example, when the type of the control is a button type, that is, the corresponding HTML tag is (button/a/span), the position, 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, and if the page click event has a trigger background request, information such as a Uniform Resource Locator (URL) of the background request, time consumed by the background request, and whether the background request is successful or not is recorded. Further, after the information of the control is obtained, the control needs to be counted at a specific time, a counting strategy corresponding to the control is obtained according to the control and the control type of the control, and then the user behavior data of the control is counted according to the counting strategy. In the process of using the page, the user behavior of the front-end user can be supervised based on the embedded point rule, so that the behavior data of the front-end user when using the page can be obtained through statistics.
In the front-end user behavior statistical method provided by this embodiment, a page click event of a page is monitored in a page operation process by obtaining a preset embedded point rule for the page, and behavior data of a front-end user of the page is counted based on the embedded point rule after the page click event is monitored. In order to realize the automatic point burying of the page in the embodiment, a point burying rule is set for the page, the point burying is triggered by a page clicking event during the page operation, the problem that the prior point burying is mistaken and complicated and is poor in convenience is solved, the behavior of a page front-end user can be subjected to global statistics, and the statistical efficiency is high.
Example two
Fig. 2 is a schematic flow chart illustrating a front-end user behavior statistical method according to a second embodiment of the present invention. The front-end user behavior statistical method provided by this embodiment needs to be executed on the basis of modularizing the front end of the page. The front-end user behavior statistical method comprises the following steps:
s201, performing modularization processing on the page.
Under the rapid development of the internet, a page gradually becomes an internet application program, in order to adapt to intense market competition and meet the requirement of a user on diversification, JS codes embedded in a webpage are increasingly huge and complex, the page is also increasingly similar to a desktop program, and labor division cooperation, progress management, unit testing and the like are needed. In order to improve the development experience of the developer and provide good support for performance optimization, the developer can program the front end of the page based on modularization. The purpose of front-end modularization of the page can be achieved, the page can be cooperatively developed by multiple persons, the page research and development speed is increased, and the maintenance difficulty is reduced.
S202, a buried point rule is configured for the page corresponding module.
In order to realize global statistics of the page, a buried point rule is configured for a corresponding module of the page in advance. Specifically, all the controls, the control types, and the modules to which the controls belong of the page are obtained, and different modules can set different embedding rules, or one embedding rule can be globally set. Acquiring the control type needing embedding, setting a corresponding embedding rule for the control type, and attributing the embedding rule of the control type belonging to the same module to a file to form the embedding rule of the module.
S203, monitoring the click event belonging to the page in the operation process by executing the service file operation page.
When a front-end user tries to use a page, before the page is run, a service file of a module corresponding to the page needs to be acquired, wherein the service file is a service processing flow of the module corresponding to the page. And executing the service file, namely operating the service processing flow of the corresponding module of the page. In this embodiment, when executing the service file, the embedded point rule of the module corresponding to the page is loaded at the same time.
In the running process of the service file, based on the embedded object defined in the embedded rule, specifically, when the embedded point is opened by the page corresponding module, the click events of all controls under the module are monitored, and according to the embedded rule bound by the corresponding module, when the control corresponding to the click event is monitored to be the control of the embedded point, the behavior data of the page front-end user is acquired.
And S204, after the page click event is monitored, counting behavior data of a user at the front end of the page based on the buried point rule.
In the process of using the page, the user behavior of the front-end user can be supervised based on the embedded point rule, so that the behavior data of the front-end user when using the page can be obtained through statistics. For a specific process, reference may be made to the description of the related contents in the above second embodiment, which is not described herein again.
According to the front-end user behavior statistical method provided by the embodiment, the embedded point rule is configured for the corresponding module of the page on the basis of modularization of the page, when the service file of the page is executed, the corresponding embedded point rule is obtained, and the behavior data of the front-end user of the page is obtained based on the embedded point rule in the process of executing the service file, so that global automatic embedding of the page is realized, global statistics on the behavior of the front-end user of the page can be realized, and the statistical efficiency is high.
EXAMPLE III
Fig. 3 is a schematic flow chart of a front-end user behavior statistical method according to a third embodiment of the present invention. The front-end user behavior statistical method provided by this embodiment needs to be executed on the basis of modularizing the front end of the page.
The front-end user behavior statistical method comprises the following steps:
s301, determining a dependent file required by the operation of the corresponding module of the page according to the service file of the corresponding module of the page.
Currently, developers program the front end of a page modularly in order to facilitate optimization of the page. When a front-end user tries to use a page, before the page is run, a service file of a module corresponding to the page needs to be acquired, wherein the service file is a service processing flow of the module corresponding to the page.
In the page, generally, in the modularization process, a module corresponding to the page writes a dependent related code file according to defined dependence. After the business file of the module corresponding to the page is obtained, the business file is analyzed, and a dependent file required by the operation of the module corresponding to the page can be determined. The general page correspondence module includes three types of dependent files: HyperText Markup Language (HTML) dependent files, Cascading Style Sheets (CSS) dependent files, and JS dependent files.
S302, loading a dependency file and a buried point rule configured for a page corresponding module in advance.
In this embodiment, in order to implement a global point burying mechanism, a point burying rule is configured for the page corresponding module in advance, and a point burying object of the module is defined in the point burying rule. For example, the object of the buried point may be a button tag or other designated tag. While loading the dependent file, loading a buried point rule configured for the page object module in advance.
S303, executing the service file based on the embedded point rule to obtain behavior data of the front-end user of the page in a statistical manner.
And after the dependence file and the embedded point rule are loaded, executing the service file of the module corresponding to the page, namely, running the service processing flow of the module corresponding to the page. In this embodiment, since the embedded point rule corresponding to the module is loaded, in the running process of the service 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 a front-end user uses a page, a control in the page can be clicked, the control can be monitored in this embodiment, and when it is monitored that the clicked control is a buried point object, a buried point record of the control can be obtained. Further, the embedded point rule further includes a statistical strategy of the embedded point object, after the embedded point record of the embedded point object is obtained, the statistical strategy of the embedded point object is obtained, if the statistical strategy of the embedded point object is empty, the embedded point record of the embedded point object is not counted, and if the statistical strategy is obtained, the embedded point record is counted according to the statistical strategy.
For example, when the type of the control is a button type, that is, the corresponding HTML tag is (button/a/span), the position, 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, and if the click event has a background request triggered, information such as a Uniform Resource Locator (URL), time consumption of the background request, and whether the background request is successful or not is recorded. Further, after the information of the control is obtained, the control needs to be counted at a specific time, a statistical strategy corresponding to the control is inquired and obtained from a background database according to the name of the module to which the control belongs and the control type of the control, and then the user behavior data of the control is counted according to the statistical strategy. In this embodiment, the statistical strategy is stored in a 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 embedded point rule, so that the behavior data of the front-end user when using the page can be obtained through statistics.
According to the front-end user behavior statistical method provided by the embodiment, the dependency file required by the operation of the corresponding module of the page is determined according to the service file of the corresponding module of the page, the dependency file and the embedded point rule configured for the corresponding module of the page in advance are loaded, the service file is executed based on the embedded point object defined in the embedded point rule, and the behavior data of the front-end user of the page is obtained. The embodiment provides a global point burying mechanism, a dependency file is loaded, a point burying rule of a module is written in, behaviors of front-end users can be counted based on the point burying rule, global statistics of the behaviors of the front-end users of the page can be achieved for global automatic point burying of the page, and the statistical efficiency is high.
Example four
Fig. 4 is a schematic flow chart of a front-end user behavior statistical method according to a fourth embodiment of the present invention. At present, RequireJS is a very small JavaScript module loading frame, and in this embodiment, the RequireJS frame is selected as a bottom-layer dependency implementation, and front-end modularization of a page is implemented on the basis. On the basis of the above embodiment, the process of loading the preset embedded point rule to the service file corresponding to the page includes:
s401, loading the business file of the page.
When a front-end user tries to use a page, before the operation, a service file of a module corresponding to the page needs to be called, wherein the service file is a service processing flow of the module corresponding to the page. In this embodiment, the service file of the corresponding module of the page is loaded based on the RequireJS frame, the service file is written in the JavaScript scripting language, and the JS is used as the JS file of the extension.
S402, analyzing the service file to obtain a dependent file required by the page operation.
And in the process of calling the service file, analyzing the service file to obtain the dependent file of the module. In the page modularization process, the dependency of the module can be defined, and a developer can write a related code file according to the dependency definition. The modules of a generic page include three types of dependent files: HTML dependent files, CSS dependent files, and JS dependent files.
In this embodiment, since RequireJS only supports dependency analysis of JS-dependent files, in order to implement analysis of HTML-dependent files and CSS-dependent files, a third-party plug-in needs to be inserted into the RequireJS frame, so that the RequireJS frame can support analysis of HTML-dependent files and CSS-dependent files.
And S403, packaging the service file.
After the required dependency file of the module corresponding to the page is analyzed, the dependency file of the module is loaded, and in practice, the service file of the module can be directly executed after the JS dependency file loading of the module is completed due to the Require JS frame. In this embodiment, the module needs to load the HTML dependent file and the CSS dependent file in addition to the JS dependent file.
In order to execute the service processing flow of the module after all the dependent files are loaded, in this embodiment, the service processing flow of the service file of the module is encapsulated based on the RequireJS framework, and the encapsulated service processing flow is not executed any more and is executed only after the encapsulation is released.
S404, loading a buried point rule of the dependent file and the page.
In order to implement a mechanism for global statistics on a page, in this embodiment, a dependent file of a module is loaded, and a buried point rule configured for the module in advance is loaded at the same time. The object of the buried point may be a button label or other designated label. Specifically, the burial point can be automatically opened for the objects of button labels (button/span/a) in all the Dom files belonging to the module, so that the burial point statistics can be carried out through all the button labels of the module.
S405, performing HTML template rendering and CSS rendering on the service file.
In this embodiment, after the dependent file is loaded, HTML template rendering and CSS rendering are performed on the service file of the module based on the dependent file.
S406, removing the encapsulation of the service file.
After the service file of the module is rendered, since the service file of the module is encapsulated before, the service processing flow of the service file needs to be decapsulated, so that the service file of the module can be executed.
After the encapsulation of the service file of the module is released, the service file is executed based on the RequireJS framework. In the process of executing the service file, because the embedded point rule of the module is loaded in the service file, the click behavior of the front-end user is recorded based on the embedded point object defined in the embedded point rule, so that the behavior data of the front-end user can be counted.
It should be noted here that the implementation of dependency using RequierJS as the bottom layer is a complete example here, and is not a condition for limiting the present invention. The front-end user statistical method can also be realized based on the underlying dependencies such as the SeaJS framework.
The front-end user behavior statistical method provided in this embodiment obtains behavior data of a page front-end user by loading a service file of a module corresponding to the page, parsing a dependent file of a service file obtaining module, encapsulating a service processing flow of the service file, loading the dependent file of the module and a embedding rule preset by the module, performing HTML template rendering and CSS rendering on the service file, removing encapsulation of the service file, and executing statistics of embedded objects defined in the embedding rule by the service file. The embodiment provides a global point burying mechanism, a dependent file is loaded, a point burying rule of a module is written in at the same time, behaviors of a front-end user can be counted based on a point burying object in the point burying rule, global statistics of the behaviors of the front-end user can be realized for global automatic point burying of a page, and the statistical efficiency is high.
EXAMPLE five
Fig. 5 is a schematic flow chart of a front-end user behavior statistical method according to a fifth embodiment of the present invention. On the basis of the above embodiment, the front-end user behavior statistical method includes the following steps:
s501, monitoring a page click event belonging to a page in the process of executing the service file.
After the business file is loaded and rendered, the business processing flow of the business file can be executed, and in the process of executing the processing flow, the business file monitors the page click event of the corresponding module of the affiliated page. That is to say, when a front-end user clicks a page on a web page, a page click event can be triggered, and a service file corresponding to a module to which the page click event belongs can monitor the page click event.
In this embodiment, a page is subjected to modular processing, then a module corresponding to the page is subjected to point burying, when the module is loaded, a point burying rule configured for the page is loaded at the same time, and page click events of all controls under the module are monitored under the condition that the module opens the point burying.
S502, determining a target object corresponding to the monitored page click event.
And when the business file of the page monitors a page click event, determining a target object corresponding to the page click event.
S503, judging whether the target object starts a buried point function or not.
In the above embodiment, when the service file loads the dependent file, the embedded point rule preset for the page is loaded at the same time. The embedded point rule defines the embedded point object of the page corresponding module, and is provided with a statistical strategy corresponding to the embedded point object. In this embodiment, the object for opening the buried point is defined in the code of the buried point rule, and the object for buried point may be a button label or other designated control such as a label. In this embodiment, the embedded point rule defines the embedded point object and the statistical strategy corresponding to the embedded point object. There are two alternative ways to open the buried point: firstly, the embedded point object is opened to carry out embedded point recording when the page is loaded. Specifically, when a preset embedding rule is loaded, embedding is automatically started for embedding objects such as button labels in all Dom files belonging to the page. And secondly, judging whether each buried point object has a corresponding statistical strategy, if the statistical strategy of the buried point object is not null, indicating that the target object starts a buried point function, and performing user behavior data statistics based on the buried point object. And if the statistical strategy of the target object is null, the target object is not counted if the statistical strategy of the target object indicates that the buried point function of the target object is not started.
If the target object is judged to start the embedded point function, S504 is executed; otherwise, return to execute S501.
S504, point burying recording is conducted on the clicking behaviors of the target object, and behavior data of the front-end user are counted according to the point burying recording and the statistical strategy of the target object.
When the buried point is judged to be opened by the target object, the buried point record can be performed on the target object, and optionally, the button, time and coordinate of the click event are recorded, wherein the coordinate of the click event is the position in the page and can also be called as the coordinate.
Furthermore, a statistical strategy of the target object is obtained, the buried point record of the target object can be counted according to the statistical strategy, that is, information of a click position, a click event, a user ID, a module to which the control belongs and the like can be counted, so that behavior data of the front-end user can be obtained.
And S505, while the click behavior of the target object is recorded in a buried point mode, acquiring a request event corresponding to the click behavior, and recording the service logic of the request event.
Further, each click behavior of the front-end user corresponds to one request event of the web page, and each request event has a certain service logic.
S506, judging whether the recorded times exceed a threshold value.
If the judgment result is negative, executing S507; otherwise, S508 is performed.
S507, judging whether a page refreshing event or a page closing event is monitored in the process of executing the service file.
If the judgment result is yes, executing S508; otherwise, returning to execute S501 to continue monitoring the page click event.
And S508, writing the behavior data of the front-end user and the recorded business logic into a log file.
In this embodiment, the behavior data and the service logic are locally stored at the front end, and when the number of records is N, the recorded behavior data and the recorded service logic may be written in a log file in batch for storage. That is, during the 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 in the log file in batches. In practical application, in order to relieve the pressure of local storage, when the number of times of recording exceeds a threshold value, the recorded behavior data and the service logic may be sent to the server in batch for storage, and after receiving the behavior data and the service logic, the server may write the behavior data and the service logic into a log file according to a set data format.
Further, in this embodiment, a page refresh event and a page close event of the page may also be monitored during the process of executing the service file, and when the page refresh event or the page close event is monitored, the recorded behavior data and the service logic are written into the log file. In order to avoid information loss, the recorded behavior data and the business logic are sent to a back-end server for storage. After receiving the behavior data and the service logic, the server can write the behavior data and the service logic into a log file according to a set data format.
Further, the log file containing the behavior data is analyzed, and based on the counted behavior data of the front-end user, the operation data of some webpages can be acquired. The operation data may include the number of independent visitors (UV for short), Page View volume or click volume (PV for short), module heat, project heat, request time consumption statistics, request success rate, statistics of designated buttons, partial module statistics of designated pages, click thermodynamic diagram of designated pages, and the like. Furthermore, the analysis result can be displayed to a web page developer, and the developer can use the operation data as reference data to provide reference for actual product operation and design troubleshooting errors and provide basis for front-end interactive design.
In the front-end user behavior statistical method provided in this embodiment, in the process of executing the service file of the page corresponding module, the page click event belonging to the page is monitored, a target object corresponding to the monitored page click event is determined, whether the target object is a buried object defined in the buried point rule is determined, when the target object starts a buried point function, a buried point record may be performed on the click behavior of the front-end user, and behavior data of the front-end user is counted according to the buried point record. The embodiment realizes the global statistics of the front-end user behavior of the webpage based on the embedded point rule loaded in the module, can acquire the global behavior data of the page, and is convenient for providing reference basis for the later maintenance or perfection of the page.
EXAMPLE six
Fig. 6 is a schematic structural diagram of a front-end user behavior statistics apparatus according to a sixth embodiment of the present invention. The front-end user behavior statistical device comprises: the device comprises an acquisition module 11, a monitoring module 12 and a statistic module 13.
The obtaining module 11 is configured to obtain a preset embedding rule for a page.
In this embodiment, a dot embedding rule is set for the page in advance, specifically, all the controls of the page are obtained, and the dot embedding rule is set for different controls according to statistical requirements. Optionally obtaining the type of each control, and setting the same embedded point rule for all the controls of the same type.
Wherein, the embedded point rule defines the embedded point object of the page, and a statistical strategy corresponding to the embedded point object is set.
During the operation of a page, the obtaining module 11 needs to obtain a buried point rule of the page, and specifically, when the page is started, the obtaining module 11 loads the buried point rule into a service file of the page. The service file of the page is a service processing flow of the page.
The monitoring module 12 is configured to monitor a page click event of a page in a page running process.
When a user opens a page, the service file of the page can be executed, that is, the service processing flow of the page is started, and in the process of executing the processing flow, the monitoring module 12 monitors the page click event belonging to the page. That is to say, when the front-end user clicks a page on a web page, a page click event can be triggered, and the service file corresponding to the page can monitor the page click event.
In this embodiment, a page is embedded, when the page is started, that is, when a service file of the page is loaded, a rule of embedding the corresponding page is loaded, and accordingly, a function of embedding the point is started, so that page click events of all controls under the page are all monitored by the monitoring module 12.
And the counting module 13 is used for counting behavior data of a user at the front end of the page based on the embedded point rule after the page click event is monitored.
After monitoring the page click event, the statistical module 13 determines a target object corresponding to the page click event, and further, after determining the target object, the statistical module 13 needs to determine whether the target object opens a buried point. In this embodiment, the object for opening the buried point is defined in the buried point rule, and the object for buried point may be a button label or other designated control such as a label.
In this embodiment, two optional ways of opening the buried point for the buried point object can be referred to the related descriptions in the above embodiments, and are not described herein again.
When the buried point of the target object is judged to be opened, the buried point of the target object can be recorded, and the statistical module 13 supervises the user behavior of the front-end user based on the statistical strategy corresponding to the target object, so that the behavior data of the front-end user when the front-end user uses the page can be obtained through statistics. For details, reference may be made to the related descriptions in the above embodiments, which are not described herein again.
The front-end user behavior statistical apparatus provided in this embodiment monitors a page click event of a page in a page operation process by obtaining a preset embedding rule for the page, and performs statistics on behavior data of a front-end user of the page based on the embedding rule after monitoring the page click event. In order to realize the automatic point burying of the page in the embodiment, a point burying rule is set for the page, the point burying is triggered by a page clicking event during the page operation, the problem that the prior point burying is mistaken and complicated and is poor in convenience is solved, the behavior of a page front-end user can be subjected to global statistics, and the statistical efficiency is high.
EXAMPLE seven
Fig. 7 is a schematic structural diagram of a front-end user behavior statistics apparatus according to a seventh embodiment of the present invention. The front-end user behavior statistical device comprises: the device comprises an acquisition module 11, a monitoring module 12 and a statistic module 13.
In this embodiment, an optional structure manner of the statistical module 13 includes: an acquisition unit 131, a judgment 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 monitored page click event;
a determining unit 132, configured to determine whether the target object opens a buried point;
the recording unit 133 is configured to perform a buried point record on the click behavior of the target object when the determining unit determines that the buried point is opened by the target object, and count the behavior data of the front-end user according to the buried point record and the statistical policy of the target object.
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 a service logic of the request event.
A writing unit 134, configured to write the behavior data and the service 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 page operation.
The writing unit 134 is further configured to write the behavior data and the service logic into a log file when the monitoring module 12 monitors the page refresh event or the page close event.
Optionally, the behavior data and the service logic are locally stored at the front end, in practical applications, in order to relieve the pressure of local storage, the recorded behavior data and the service logic may be sent to the server in batch for storage when the number of times of recording exceeds a threshold, and after receiving the behavior data and the service logic, the server may write the behavior data and the service logic into a log file according to a set data format.
Optionally, after a page refresh event or a page close event is monitored, to avoid information loss, the recorded behavior data and the service logic are sent to a server at the back end for storage. After receiving the behavior data and the service logic, the server can write the behavior data and the service logic into a log file according to a set data format.
In this embodiment, an optional structural manner of the obtaining module 11 includes: a modularization unit 111 and an acquisition unit 112.
The modularization unit 11 is configured to perform modularization processing on the page.
An obtaining unit 112, configured to load the embedded point rule into a service file of a module corresponding to the page when the page is started. And the service file is a service processing flow of the page.
An optional structure of the obtaining unit 112 includes: a loading sub-unit 1121, a parsing sub-unit 1122, an encapsulation sub-unit 1123, a rendering sub-unit 1124, and a decapsulation sub-unit 1125.
A parsing subunit 1122, configured to parse the service file to obtain the dependent 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, so as to obtain a dependent file of the page corresponding module.
The module of the general page has three types of dependent files, namely an HTML dependent file, a CSS dependent file and a JS dependent file.
The loading subunit 1121 is specifically configured to load a service file of a page, and a rule of embedding points in the service file of the page is loaded. 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.
And an encapsulating subunit 1123, configured to encapsulate the service file.
Before the loading subunit 1121 loads the dependency file and the embedded point rule configured in advance for the page corresponding module, the encapsulating subunit 1123 encapsulates the service processing flow of the service file.
And the decapsulating subunit 1125 is configured to decapsulate the service file.
Before the statistics module 13 executes the buried object defined by the service file based on the buried rule, and statistics is performed to obtain the behavior data of the front-end user of the page, the decapsulating subunit 1125 decapsulates the service file.
The rendering subunit 1124 is configured to perform HTML template rendering and CSS rendering on the service file.
Before the decapsulating subunit 1125 decapsulates the service file, the service file is HTML template rendered and CSS rendered using the dependent file.
Each functional module of the front-end user behavior statistical apparatus provided in this embodiment may be used to execute the flow of the front-end user behavior statistical method shown in fig. 1 to 5, and specific working principles thereof are not described again, for details, see description of method embodiments.
In this embodiment, based on the modularization of the page, a node burying rule is configured for a corresponding module of the page, when a service file of the page is executed, a corresponding node burying rule is obtained, and behavior data of a front-end user of the page is obtained based on the node burying rule in the process of executing the service file, so that global automatic node burying of the page is realized, global statistics on behaviors of the front-end user of the page can be performed, and the statistical efficiency is high.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.

Claims (14)

1. A front-end user behavior statistical method is characterized by comprising the following steps:
acquiring a preset embedding point rule for a page;
monitoring a page click event of the page in the page operation process;
after the page click event is monitored, the behavior data of the front-end user of the page is counted based on the buried point rule,
after the page click event is monitored, the behavior data of the page front-end user is counted based on the buried point rule, and the method comprises the following steps:
determining a target object corresponding to the monitored page clicking event;
judging whether the target object opens the buried point or not, wherein the target object opening the buried point is defined in the buried point rule;
and if so, performing buried point recording on the clicking behavior of the target object, and counting the behavior data of the front-end user according to the buried point recording and the statistical strategy corresponding to the target object.
2. The front-end user behavior statistics method of claim 1, further comprising:
and while carrying out embedded point recording on the click behavior of the target object, determining a request event corresponding to the click behavior, and recording the service logic of the request event.
3. The front-end user behavior statistical method according to claim 2, after the statistics of the behavior data of the front-end user according to the statistical strategies corresponding to the buried point records and the target objects, further comprising:
and when the recorded times exceed a threshold value, writing the behavior data and the business logic into a log file.
4. The front-end user behavior statistical method according to claim 3, after the statistics of the behavior data of the front-end user according to the statistical strategies corresponding to the buried point records and the target objects, further comprising:
monitoring a page refreshing event or a page closing event in the process of running the page;
and when the page refreshing event or the page closing event is monitored, writing the behavior data and the service logic into a log file.
5. The front-end user behavior statistical method according to any one of claims 1 to 4, wherein the obtaining of the preset embedding rule for the page comprises:
performing modular processing on the page;
when the page is started, loading the embedded point rule into a service file of a module corresponding to the page;
and the service file is a service processing flow of the page.
6. The front-end user behavior statistical method according to claim 5, wherein the loading a preset embedded point rule into a service file of a module corresponding to the page when the page is started comprises:
loading the service file of the page;
analyzing the service file to obtain a dependent file required by the page operation;
packaging the service file;
loading the dependency file and the buried point rule;
performing hypertext markup language (HTML) template rendering and Cascading Style Sheet (CSS) rendering on the service file;
and releasing the encapsulation of the service file.
7. The front-end user behavior statistical method according to claim 6, wherein the monitoring of the page click event of the page in the page running process comprises:
and monitoring the click event belonging to the page in the operation process by executing the service file to operate the page.
8. A front-end user behavior statistics apparatus, comprising:
the acquisition module is used for acquiring a preset embedded point rule for the page;
the monitoring module is used for monitoring the page click event of the page in the page running process;
a statistic module for counting the behavior data of the front-end user of the page based on the buried point rule after monitoring the page click event,
the statistic module comprises:
the acquisition unit is used for determining a monitored target object corresponding to the page click event;
the judging unit is used for judging whether the target object opens the buried point or not, wherein the target object which opens the buried point is defined in the buried point rule;
and the recording unit is used for recording the embedded point of the click behavior of the target object when the judging unit judges that the embedded point of the target object is opened, and counting the behavior data of the front-end user according to the embedded point record and the statistical strategy of the target object.
9. The front-end user behavior statistics apparatus according to claim 8, wherein the recording unit is further configured to determine a request event corresponding to the click behavior while performing a point burying recording on the click behavior of the target object, and record a service logic of the request event.
10. The front-end user behavior statistics apparatus of claim 9, wherein the statistics module further comprises:
and the writing unit is used for writing the behavior data and the service logic into a log file when the recorded times exceed a threshold value.
11. The front-end user behavior statistics apparatus according to claim 10, wherein the monitoring module is further configured 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 monitoring module monitors the page refresh event or the page close event.
12. The front-end user behavior statistics apparatus according to any one of claims 8-11, wherein the obtaining module comprises:
the modularization unit is used for carrying out modularization processing on the page;
the acquiring unit is used for loading the embedded point rule into a service file of a module corresponding to the page when the page is started;
and the service file is a service processing flow of the page.
13. The front-end user behavior statistics apparatus according to claim 12, wherein the obtaining unit comprises:
a loading subunit, configured to load a service file of the page, a dependency file required by the page during running, and the embedding rule;
the analysis subunit is used for analyzing the service file to acquire the dependent file;
the packaging subunit is used for packaging the service file;
the rendering subunit is used for performing hypertext markup language (HTML) template rendering and Cascading Style Sheet (CSS) rendering on the service file;
and the decapsulation subunit is used for decapsulating the service file.
14. The front-end user behavior statistics apparatus according to claim 13, wherein the monitoring module is specifically configured to execute the service file to run the page, and monitor the click event attached to the page during a running process.
CN201610204743.XA 2016-04-01 2016-04-01 Front-end user behavior statistical method and device Active CN107295050B (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201610204743.XA CN107295050B (en) 2016-04-01 2016-04-01 Front-end user behavior statistical method and device
TW106107619A TWI753887B (en) 2016-04-01 2017-03-08 Front-end user behavior statistics method and device
PCT/CN2017/077244 WO2017167042A1 (en) 2016-04-01 2017-03-20 Statistical method and apparatus for behaviors of front-end users

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610204743.XA CN107295050B (en) 2016-04-01 2016-04-01 Front-end user behavior statistical method and device

Publications (2)

Publication Number Publication Date
CN107295050A CN107295050A (en) 2017-10-24
CN107295050B true CN107295050B (en) 2021-05-11

Family

ID=59963450

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610204743.XA Active CN107295050B (en) 2016-04-01 2016-04-01 Front-end user behavior statistical method and device

Country Status (3)

Country Link
CN (1) CN107295050B (en)
TW (1) TWI753887B (en)
WO (1) WO2017167042A1 (en)

Families Citing this family (67)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108810057B (en) * 2017-05-05 2021-05-07 腾讯科技(深圳)有限公司 User behavior data acquisition method and device and storage medium
CN109857461B (en) * 2017-11-27 2021-03-30 北京京东尚科信息技术有限公司 Page generation method and device
CN108038053B (en) * 2017-11-29 2019-07-26 上海恺英网络科技有限公司 A kind of dynamic configuration buries method and apparatus a little
CN110347945A (en) * 2018-01-15 2019-10-18 北京京东金融科技控股有限公司 The method and apparatus for obtaining the data of the page
CN108197002B (en) * 2018-01-16 2021-03-16 吉浦斯信息咨询(深圳)有限公司 Mobile device non-buried point data statistical method, system, terminal and medium
CN108280014B (en) * 2018-02-06 2021-03-16 武汉斗鱼网络科技有限公司 Method and device for monitoring browser page and computer equipment
CN108536589A (en) * 2018-03-26 2018-09-14 广州小鹏汽车科技有限公司 A kind of application program buries point methods and system
CN108733559B (en) * 2018-04-09 2023-03-28 平安普惠企业管理有限公司 Page event triggering method, terminal equipment and medium
CN110704771B (en) * 2018-06-22 2024-03-01 北京京东尚科信息技术有限公司 Page abnormality monitoring method, system, device, electronic equipment and readable medium
CN110825594B (en) * 2018-08-07 2023-10-24 阿里巴巴(中国)有限公司 Data reporting and issuing method, client and server
CN109101425B (en) * 2018-08-14 2021-12-07 创新先进技术有限公司 Index point burying method and device for dynamic page AB test
CN109240664B (en) * 2018-08-22 2023-04-28 平安普惠企业管理有限公司 Method and terminal for collecting user behavior information
CN109542529B (en) * 2018-10-26 2022-04-05 深圳壹账通智能科技有限公司 Function name-based point burying method and device, computer equipment and storage medium
CN111105259B (en) * 2018-10-29 2024-04-02 北京奇虎科技有限公司 User identification method, device, electronic equipment and storage medium
CN109684583A (en) * 2018-11-12 2019-04-26 深圳壹账通智能科技有限公司 Analysis method, device, terminal and the readable storage medium storing program for executing of Page user behavior
CN109582418A (en) * 2018-11-21 2019-04-05 平安科技(深圳)有限公司 User behavior data collection method, device, computer installation, storage medium
CN109819098A (en) * 2018-12-11 2019-05-28 平安科技(深圳)有限公司 Menu option display methods, server, system and computer readable storage medium
CN109688207B (en) * 2018-12-11 2022-06-03 北京云中融信网络科技有限公司 Log transmission method and device and server
CN109767259A (en) * 2018-12-15 2019-05-17 深圳壹账通智能科技有限公司 Based on operation event promotion method, apparatus, equipment and the medium for burying point data
CN109933317B (en) * 2018-12-24 2023-04-11 创新先进技术有限公司 Point burying method, device, server and readable storage medium
CN109902253A (en) * 2019-01-18 2019-06-18 中国平安人寿保险股份有限公司 Page data acquisition method and device, electronic equipment, storage medium
CN110020912B (en) * 2019-01-31 2022-03-22 创新先进技术有限公司 Page display method, device and equipment
CN109885305B (en) * 2019-02-26 2022-10-28 广州虎牙信息科技有限公司 Method, device, equipment and storage medium for processing special topic pages
CN109871212B (en) * 2019-02-26 2022-10-28 广州虎牙信息科技有限公司 Method, device and equipment for processing special topic page and storage medium
CN110083459A (en) * 2019-03-16 2019-08-02 平安城市建设科技(深圳)有限公司 The data in cross-page face bury point methods, device, equipment and storage medium
CN109960633A (en) * 2019-03-28 2019-07-02 深圳市跃动运营科技有限公司 A kind of data visualization buries point methods, storage medium and intelligent terminal
CN110019079A (en) * 2019-04-19 2019-07-16 山东浪潮云信息技术有限公司 A kind of front end log collecting method and device
CN110109700B (en) * 2019-05-08 2023-06-30 吉旗(成都)科技有限公司 Data statistics method and device for iOS App without buried points
CN110298000A (en) * 2019-05-21 2019-10-01 平安普惠企业管理有限公司 Acquisition methods, terminal device and the medium of page parameter
CN110457089B (en) * 2019-07-05 2023-09-26 中国平安人寿保险股份有限公司 Data acquisition method, data acquisition device, computer readable storage medium and computer equipment
CN110569185A (en) * 2019-08-02 2019-12-13 贝壳技术有限公司 front-end point burying method and device
CN110659188B (en) * 2019-08-14 2023-03-21 平安普惠企业管理有限公司 Page portrait data processing method and device, computer equipment and storage medium
CN110781061B (en) * 2019-09-20 2022-11-25 平安科技(深圳)有限公司 Method and device for recording user behavior link
CN110990619B (en) * 2019-10-12 2023-09-01 平安银行股份有限公司 Buried data query method, buried data query device, buried data query system, buried data query device and computer storage medium
CN112711731A (en) * 2019-10-25 2021-04-27 腾讯科技(深圳)有限公司 Data point burying method, device, equipment and storage medium
CN112733008A (en) * 2019-10-28 2021-04-30 浙江大搜车软件技术有限公司 Label value generation method and device, electronic equipment and storage medium
CN111191998A (en) * 2019-10-29 2020-05-22 腾讯科技(深圳)有限公司 Item processing method and device
CN111061627B (en) * 2019-11-20 2023-10-03 北京达佳互联信息技术有限公司 Webpage embedding method and device, electronic equipment and storage medium
CN110933165A (en) * 2019-11-27 2020-03-27 中国银行股份有限公司 Operation behavior tracking method and device
CN112905427A (en) * 2019-12-04 2021-06-04 北京沃东天骏信息技术有限公司 Data processing method and device
CN111193613A (en) * 2019-12-10 2020-05-22 北京你财富计算机科技有限公司 Method, device and system for collecting dotting information at client application
CN111159590A (en) * 2019-12-31 2020-05-15 亚信科技(中国)有限公司 Serial connection method and device based on front-end and back-end service call links
CN111241446B (en) * 2020-01-13 2023-10-31 杭州安恒信息技术股份有限公司 Method, device, equipment and medium for extracting text content of web page
CN111695064B (en) * 2020-04-29 2023-08-18 北京城市网邻信息技术有限公司 Buried point loading method and device
CN111901192B (en) * 2020-07-15 2023-09-12 腾讯科技(深圳)有限公司 Statistical method and device for page access data
CN111797025B (en) * 2020-07-17 2023-11-14 北京中指讯博数据信息技术有限公司 Application-oriented data processing method and device
CN112000541A (en) * 2020-07-23 2020-11-27 招联消费金融有限公司 Buried point data reporting method and device, computer equipment and storage medium
CN111930422B (en) * 2020-09-02 2023-07-25 度小满科技(北京)有限公司 Information acquisition method, device, server and storage medium
CN112102008A (en) * 2020-09-25 2020-12-18 中国建设银行股份有限公司 Configurable user behavior acquisition method and device
CN112181770A (en) * 2020-09-28 2021-01-05 北京达佳互联信息技术有限公司 Method, device and system for setting buried object
CN112148413A (en) * 2020-09-29 2020-12-29 无线生活(杭州)信息科技有限公司 Page optimization method and device
CN112256701A (en) * 2020-10-22 2021-01-22 广东万唯计算机服务有限公司 Dynamic buried point data acquisition system and use method thereof
CN112199267A (en) * 2020-11-12 2021-01-08 支付宝(杭州)信息技术有限公司 Behavior log acquisition method and device
CN113761415A (en) * 2020-11-24 2021-12-07 北京沃东天骏信息技术有限公司 Page display method and device
CN113010831A (en) * 2021-04-06 2021-06-22 金宝贝网络科技(苏州)有限公司 Thermodynamic diagram optimization method, thermodynamic diagram optimization system and storage medium
CN113204463A (en) * 2021-04-21 2021-08-03 宝宝巴士股份有限公司 Embedding point statistical method and device for apk download installation rate
CN113807880A (en) * 2021-04-21 2021-12-17 北京沃东天骏信息技术有限公司 Method and device for data monitoring, electronic equipment and storage medium
CN113138905A (en) * 2021-05-11 2021-07-20 北京京东拓先科技有限公司 Software function monitoring method and device
CN113239251A (en) * 2021-05-27 2021-08-10 深圳市金蝶天燕云计算股份有限公司 Processing method of buried point data, related device and storage medium
CN113485883B (en) * 2021-05-31 2024-02-13 济南浪潮数据技术有限公司 Optimization monitoring method, device, equipment and medium for server virtualization system
CN113505079A (en) * 2021-07-27 2021-10-15 平安普惠企业管理有限公司 Application program testing method, device, equipment and medium
CN113590959B (en) * 2021-08-02 2023-07-28 北京奇艺世纪科技有限公司 User behavior data acquisition method, device, equipment and storage medium
CN114138630B (en) * 2021-11-10 2023-06-30 浪潮卓数大数据产业发展有限公司 Buried point data collection method and device based on ES6 decorator
CN114489660B (en) * 2021-12-22 2024-03-08 抖音视界有限公司 Buried point code adding method, device and equipment
CN115022388A (en) * 2022-05-31 2022-09-06 济南浪潮数据技术有限公司 Data acquisition method, device, equipment and medium
CN115510352B (en) * 2022-11-15 2023-05-05 中国外运股份有限公司 User behavior acquisition method and device, electronic equipment and storage medium
CN117290256A (en) * 2023-11-24 2023-12-26 北京中指实证数据信息技术有限公司 Code burying method for counting user behaviors

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103916293A (en) * 2014-04-15 2014-07-09 浪潮软件股份有限公司 Method for monitoring and analyzing website user behaviors
CN104915398A (en) * 2015-05-29 2015-09-16 北京京东尚科信息技术有限公司 Method and device for webpage point burying
CN105162822A (en) * 2015-06-30 2015-12-16 浪潮(北京)电子信息产业有限公司 Website log data processing method and device

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348650B (en) * 2013-08-05 2019-07-16 腾讯科技(深圳)有限公司 Monitoring method, service apparatus and the system of website
CN104683294B (en) * 2013-11-27 2019-01-18 阿里巴巴集团控股有限公司 A kind of data processing method and system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103916293A (en) * 2014-04-15 2014-07-09 浪潮软件股份有限公司 Method for monitoring and analyzing website user behaviors
CN104915398A (en) * 2015-05-29 2015-09-16 北京京东尚科信息技术有限公司 Method and device for webpage point burying
CN105162822A (en) * 2015-06-30 2015-12-16 浪潮(北京)电子信息产业有限公司 Website log data processing method and device

Also Published As

Publication number Publication date
TW201810076A (en) 2018-03-16
TWI753887B (en) 2022-02-01
CN107295050A (en) 2017-10-24
WO2017167042A1 (en) 2017-10-05

Similar Documents

Publication Publication Date Title
CN107295050B (en) Front-end user behavior statistical method and device
US7801891B2 (en) System and method for collecting user interest data
US8413044B2 (en) Method and system of retrieving Ajax web page content
CN109254910B (en) Application program testing method and device, electronic equipment and storage medium
CN102999314B (en) Delay tracker instrument immediately
CN108804707A (en) A kind of page processing method, device and relevant device
US20140137006A1 (en) Graphical Overlay Related To Data Mining And Analytics
CN110020339B (en) Webpage data acquisition method and device based on non-buried point
CN101222349A (en) Method and system for collecting web user action and performance data
CN102043815B (en) A kind of player method of internet extension advertisement and extension advertisement processor
CN106897347A (en) A kind of web page display method, Action Events recording method and device
CN112948226B (en) User portrait drawing method and device
CN106598991A (en) Web crawler system capable of realizing website interaction and automatic form extraction by conversational mode
CN110851681A (en) Crawler processing method and device, server and computer readable storage medium
CN109635210B (en) Behavior data reporting method, device, equipment and storage medium
CN109947635A (en) A kind of data reporting method, device, storage medium and terminal device
CN114138244A (en) Method and device for automatically generating model files, storage medium and electronic equipment
US20170212735A1 (en) Replicating a web technology
CN106095660A (en) The quality control method of application and device
CN113987393A (en) Web page operation recorder, system, device and method
CN109240664A (en) A kind of method and terminal acquiring user behavior information
CN111026945B (en) Multi-platform crawler scheduling method, device and storage medium
CN109062784B (en) Interface parameter constraint code entry positioning method and system
CN106648912A (en) Modular method and apparatus for data processing in data acquisition platform
CN109062785B (en) Interface parameter constraint code positioning method and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant