CN111506471A - Data monitoring method and system based on Js (Java native server) embedded points - Google Patents
Data monitoring method and system based on Js (Java native server) embedded points Download PDFInfo
- Publication number
- CN111506471A CN111506471A CN202010244568.3A CN202010244568A CN111506471A CN 111506471 A CN111506471 A CN 111506471A CN 202010244568 A CN202010244568 A CN 202010244568A CN 111506471 A CN111506471 A CN 111506471A
- Authority
- CN
- China
- Prior art keywords
- monitored
- conversion
- event
- behavior
- embedded point
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45529—Embedded in an application, e.g. JavaScript in a Web browser
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Mathematical Physics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the invention provides a data monitoring method and a data monitoring system based on Js buried points, which comprise the following steps: a basic embedded point based on a JavaScript frame is arranged on an event to be monitored, and the triggered behavior of the event to be monitored is monitored through the basic embedded point; setting a conversion tracking embedded point based on a JavaScript frame on the conversion behavior of the event to be monitored, and monitoring the conversion behavior of the event to be monitored through the conversion tracking embedded point; after the basic embedded point of the event to be monitored is triggered successfully, monitoring the conversion behavior of the event, and after the conversion tracking embedded point of the event to be monitored is triggered successfully, collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point; and displaying the recorded data related to the transformation behavior monitored by the transformation tracking buried points to the terminal. The monitoring mode is unified, the monitoring data is relatively controllable, and the tracking and converting behaviors are effectively monitored.
Description
Technical Field
The invention relates to the field of data monitoring, in particular to a data monitoring method and system based on a buried point.
Background
Most of the existing landing page event monitoring is based on an api interface or an html monitoring mode.
The monitoring mode based on the api interface means that an advertiser develops a callback interface, the advertiser decides and realizes statistics and unlimited modes of page data, and when a landing page event trigger from a media side is collected, the data is transmitted back to a data receiving side through the callback api interface.
The monitoring mode based on the html means that data monitoring statistics is realized on the advertiser landing page in a html code point burying mode.
In the process of implementing the invention, the applicant finds that at least the following problems exist in the prior art:
when the Api monitoring mode is adopted, the development cost of an advertiser is high, the capability of realizing page data monitoring needs to be provided for the advertiser side technology, and the data accuracy needs to be testified due to the fact that the advertiser side monitoring mode is not uniform.
When the monitoring mode of Html is adopted, only the click behavior of the page event can be monitored, and the user can send monitoring once and record the triggering times once by clicking once, namely, only knowing that the user triggers a certain action, but cannot monitor the follow-up action, and cannot know whether the action is triggered successfully.
Disclosure of Invention
The embodiment of the invention provides a data monitoring method and system based on Js buried points, which realize uniform monitoring mode, relatively controllable monitoring data and effective monitoring, tracking and converting behaviors.
To achieve the above object, in one aspect, an embodiment of the present invention provides a data monitoring method based on a buried point, including:
a basic embedded point based on a JavaScript frame is arranged on an event to be monitored, and the triggered behavior of the event to be monitored is monitored through the basic embedded point; setting a conversion tracking embedded point based on a JavaScript frame on the conversion behavior of the event to be monitored, and monitoring the conversion behavior of the event to be monitored through the conversion tracking embedded point;
after the basic embedded point of the event to be monitored is triggered successfully, monitoring the conversion behavior of the event, and after the conversion tracking embedded point of the event to be monitored is triggered successfully, collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point;
and displaying the recorded data related to the transformation behavior monitored by the transformation tracking buried points to the terminal.
On the other hand, an embodiment of the present invention further provides a data monitoring system based on Js embedded point, including:
the embedded point setting unit is used for setting a basic embedded point based on a JavaScript frame on an event to be monitored and monitoring the triggered behavior of the event to be monitored through the basic embedded point; setting a conversion tracking embedded point based on a JavaScript frame on the conversion behavior of the event to be monitored, and monitoring the conversion behavior of the event to be monitored through the conversion tracking embedded point;
the monitoring and recording unit is used for monitoring the conversion behavior of the event after the basic embedded point of the event to be monitored is triggered successfully, and collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point after the conversion tracking embedded point of the event to be monitored is triggered successfully;
and the display unit is used for displaying the recorded data related to the conversion behavior monitored by the conversion tracking buried point to the terminal.
The technical scheme has the following beneficial effects: and a js buried point monitoring mode is adopted, so that compared with the api monitoring, the js monitoring can reduce the development cost of advertisers, the monitoring mode is unified, and the monitoring data is relatively controllable. Compared with html monitoring, the js buried point monitoring mode can convert behaviors for tracking, and starts monitoring after an event is successfully triggered instead of sending the event once a submit button is clicked. And the conversion behavior is recorded only when the event conversion tracking buried point is successfully triggered.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of a data monitoring method based on a buried point according to an embodiment of the present invention;
FIG. 2 is a block diagram of a data monitoring system based on a buried site according to an embodiment of the present invention;
fig. 3 is a flowchart of an embodiment of a data monitoring method based on a buried point.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, a data monitoring method based on Js buried point is provided in combination with an embodiment of the present invention, and includes:
s101: a basic embedded point based on a JavaScript frame is arranged on an event to be monitored, and the triggered behavior of the event to be monitored is monitored through the basic embedded point; setting a conversion tracking embedded point based on a JavaScript frame on the conversion behavior of the event to be monitored, and monitoring the conversion behavior of the event to be monitored through the conversion tracking embedded point;
s102: after the basic embedded point of the event to be monitored is triggered successfully, monitoring the conversion behavior of the event, and after the conversion tracking embedded point of the event to be monitored is triggered successfully, collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point;
s103: and displaying the recorded data related to the transformation behavior monitored by the transformation tracking buried points to the terminal.
Preferably, in step 101, the step of setting the basic buried point based on the JavaScript frame on the event to be monitored specifically includes:
and setting the code of the basic embedded point in the webpage website code of the event to be monitored.
Preferably, in step 101, the setting the conversion tracking embedding point based on the JavaScript frame on the conversion behavior of the event to be monitored specifically includes:
generating a custom field code representing the conversion tracking embedded point, and arranging the custom field code in a service code of the conversion behavior of the event to be monitored;
the custom field code also identifies a type of conversion behavior for the event to be monitored.
Preferably, in step 102, after the conversion tracking embedded point of the event to be monitored is successfully triggered, collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point; the method comprises the following steps:
and when the conversion tracking embedded point of the event to be monitored is successfully triggered, generating a mark of successful triggering, and collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point according to the mark of successful triggering.
Preferably, the data relating to the transformation behaviour monitored by the transformation tracking burial point comprises: the conversion behavior type code and the unique identification of the conversion behavior; wherein the unique identification of the conversion behavior comprises: exposure time, trigger time and trigger user ip;
step 103 specifically comprises:
displaying the recorded data related to the transformation behavior monitored by the transformation tracking buried points to a terminal, wherein the data specifically comprises the following steps:
and according to the conversion behavior type codes, classifying the recorded data related to the conversion behavior monitored by the conversion tracking buried points according to the conversion behavior types to form a table, and displaying the table to the terminal.
As shown in fig. 2, in combination with the embodiment of the present invention, there is also provided a data monitoring system based on Js buried point, including:
the embedded point setting unit 21 is configured to set a basic embedded point based on a JavaScript frame on an event to be monitored, and monitor a triggered behavior of the event to be monitored through the basic embedded point; setting a conversion tracking embedded point based on a JavaScript frame on the conversion behavior of the event to be monitored, and monitoring the conversion behavior of the event to be monitored through the conversion tracking embedded point;
the monitoring and recording unit 22 is configured to monitor the conversion behavior of the event after the basic embedded point of the event to be monitored is successfully triggered, and collect and record data related to the conversion behavior monitored by the conversion tracking embedded point after the conversion tracking embedded point of the event to be monitored is successfully triggered;
and the display unit 23 is used for displaying the recorded data related to the conversion behavior monitored by the conversion tracking buried point to the terminal.
Preferably, the buried point setting unit 21 is specifically configured to:
and setting the code of the basic embedded point in the webpage website code of the event to be monitored.
Preferably, the buried point setting unit 21 is specifically configured to:
generating a custom field code representing the conversion tracking embedded point, and arranging the custom field code in a service code of the conversion behavior of the event to be monitored; the custom field code also identifies a type of conversion behavior for the event to be monitored.
Preferably, the monitoring and recording unit 22 is specifically configured to:
and when the conversion tracking embedded point of the event to be monitored is successfully triggered, generating a mark of successful triggering, and collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point according to the mark of successful triggering.
Preferably, the data relating to the transformation behaviour monitored by the transformation tracking burial point comprises: the conversion behavior type code and the unique identification of the conversion behavior; wherein the unique identification of the conversion behavior comprises: exposure time, trigger time and trigger user ip;
the display unit 23 is specifically configured to:
and according to the conversion behavior type codes, classifying the recorded data related to the conversion behavior monitored by the conversion tracking buried points according to the conversion behavior types to form a table, and displaying the table to the terminal.
The invention has the following beneficial effects:
and a js buried point monitoring mode is adopted, so that compared with the api monitoring, the js monitoring can reduce the development cost of advertisers, the monitoring mode is unified, and the monitoring data is relatively controllable. Compared with html monitoring, the js buried point monitoring mode can convert behaviors for tracking, and starts monitoring after an event is successfully triggered instead of sending the event once a submit button is clicked. And the conversion behavior is recorded only when the event conversion tracking buried point is successfully triggered.
The above technical solutions of the embodiments of the present invention are described in detail below with reference to specific application examples, and reference may be made to the foregoing related descriptions for technical details that are not described in the implementation process.
The invention relates to a data monitoring and recycling method based on js (javascript), which can be used for data monitoring, data recycling, js monitoring, landing page monitoring, url event monitoring and the like and is used for data monitoring and recycling. The problem of reducing advertiser development cost, being uniform in data format and relatively controllable in accuracy through standardization of buried points can be solved, and the problem of monitoring complete events can be solved.
As shown in fig. 3, the data monitoring using the js buried point of the present invention will be specifically described by practical application.
First, an end user accesses landing pages, such as a microblog landing page, and accesses the advertiser's landing page by clicking (i.e., triggering) the advertiser's landing page url.
Then, when the user terminal accesses the landing page of the advertiser through the microblog and is clicked, the microblog app jumps to the landing page of the advertiser and triggers a uniform code (namely a spot-burying code) which is buried in a front-end page of the landing page in advance by the advertiser, the code is provided by the microblog, the advertiser performs spot-burying processing, and the spot-burying is set at the front end of the page. The embedded point code is realized through a js code (code for realizing js monitoring), the js code comprises a basic code and a conversion tracking code, the basic code is used for realizing the requirement of triggering success statistics when the front end is opened, after the basic code is successfully triggered, a monitoring module is started to monitor whether the conversion tracking code is triggered or not, and the conversion tracking code is used for identifying and distinguishing the conversion behavior type. The two embedded point modes are different from the conventional mode, so that the acquired behavior types are different, and a successful triggering recording mode can be supported for the event to be monitored, wherein the triggering refers to whether the user triggers the behavior of the embedded point, and the triggering can be in various modes such as clicking, browsing, submitting and the like.
The basic code segment is designed as follows, when an advertiser designs the basic code embedded point, the advertiser fills the basic code segment between the head and the head of the website code to be counted by calling the link of the basic code, and the monitoring and counting of the event can be triggered by clicking the event (such as video) on the website.
The conversion tracking code is as follows, the eventtype field is a self-defined name, so different eventtype fields can be adopted, so that the conversion behavior of the buried point can be uniquely identified by the eventtype field by utilizing the difference of the eventtype fields, and the conversion behavior can be used as the conversion behavior to be monitored by the identification, for example, 'eventtype' and 'phone' identify that the 'telephone dialing' behavior is monitored. The translation tracking code needs to be embedded at the corresponding event (such as telephone call) set by the website code (the front end code corresponding to the website page).
Then, the front-end code (referring to the basic code and the conversion tracking code) requests the microblog server monitoring module, namely, the monitoring module is triggered to monitor when the front-end code is triggered.
After the basic code is successfully triggered, the monitoring module starts to monitor whether the conversion tracking code is triggered, if the conversion tracking code of the monitoring event is not triggered, the monitoring module does not record the conversion tracking code until the conversion tracking code of the monitoring event is triggered, data is generated, the monitoring module starts to record the data, and the generated data is recorded. And the log is sent after the basic buried point of the event is successfully triggered, the log sending is the embodiment of successful triggering, and the log is an identifier and a segment of interface code and represents the record. Similarly, the log is sent only when the transformation tracking buried point is triggered successfully.
After the monitoring module records the data, the microblog server monitoring module requests the data statistics module, and transmits information such as mark and the like to the data statistics module through interface callback (also called postback), so that the data is permanently recorded. The callback adopts an http mode, and comprises information such as time for acquiring and converting tracking data, a unique identifier mark, a behavior code and the like by a callback interface, wherein the behavior code identifier is a behavior acquired at this time, the unique identifier mark carries source information of the acquired action at this time, such as exposure time, trigger time, a trigger user ip and the like, and in addition, the information of the trigger user is generally recorded, but belongs to privacy secret and is not suitable for disclosure, except for special cases.
And finally, the data statistics module classifies the callback data into a drop table according to the behavior codes in the callback information, simultaneously sends the data of the classified drop table to the display terminal, and the display terminal displays the data according to the received information.
The beneficial effects produced by the invention are as follows:
the invention adopts a js buried point monitoring mode, compared with api monitoring, js monitoring can reduce the development cost of advertisers, realize the unification of monitoring modes and relatively control monitoring data.
Compared with html monitoring, the js buried point monitoring mode can convert behaviors for tracking, and starts monitoring after an event is successfully triggered instead of sending the event once a submit button is clicked. And the conversion behavior is recorded only when the event conversion tracking buried point is triggered successfully, so that the conversion behavior can be effectively monitored and tracked, and the purpose of monitoring is realized.
It should be understood that the specific order or hierarchy of steps in the processes disclosed is an example of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged without departing from the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not intended to be limited to the specific order or hierarchy presented.
In the foregoing detailed description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, invention lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby expressly incorporated into the detailed description, with each claim standing on its own as a separate preferred embodiment of the invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. To those skilled in the art; various modifications to these embodiments will be readily apparent, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
What has been described above includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean a "non-exclusive or".
Those of skill in the art will further appreciate that the various illustrative logical blocks, units, and steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate the interchangeability of hardware and software, various illustrative components, elements, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.
The various illustrative logical blocks, or elements, described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may be located in a user terminal. In the alternative, the processor and the storage medium may reside in different components in a user terminal.
In one or more exemplary designs, the functions described in the embodiments of this invention may be implemented in hardware, software, firmware, or any combination thereof, if implemented in software, these functions may be stored on a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium including a computer storage medium and a communications medium that facilitates transfer of a computer program from one place to another.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A data monitoring method based on Js buried points is characterized by comprising the following steps:
a basic embedded point based on a JavaScript frame is arranged on an event to be monitored, and the triggered behavior of the event to be monitored is monitored through the basic embedded point; setting a conversion tracking embedded point based on a JavaScript frame on the conversion behavior of the event to be monitored, and monitoring the conversion behavior of the event to be monitored through the conversion tracking embedded point;
after the basic embedded point of the event to be monitored is triggered successfully, monitoring the conversion behavior of the event, and after the conversion tracking embedded point of the event to be monitored is triggered successfully, collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point;
and displaying the recorded data related to the transformation behavior monitored by the transformation tracking buried points to the terminal.
2. The data monitoring method based on Js buried point according to claim 1, wherein the step of setting the basic buried point based on the JavaScript frame on the event to be monitored specifically includes:
and setting the code of the basic embedded point in the webpage website code of the event to be monitored.
3. The Js-embedded-point-based data monitoring method as claimed in claim 1, wherein the locating of the conversion tracking embedded point based on the JavaScript frame on the conversion behavior of the event to be monitored specifically includes:
generating a custom field code representing the conversion tracking embedded point, and arranging the custom field code in a service code of the conversion behavior of the event to be monitored; the custom field code also identifies a type of conversion behavior for the event to be monitored.
4. The Js-based data monitoring method as claimed in claim 1, wherein, after the conversion tracking embedded point of the event to be monitored is successfully triggered, data related to the conversion behavior monitored by the conversion tracking embedded point is collected and recorded; the method comprises the following steps:
and when the conversion tracking embedded point of the event to be monitored is successfully triggered, generating a mark of successful triggering, and collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point according to the mark of successful triggering.
5. The Js-based data monitoring method as claimed in claim 1, wherein the data relating to the transformation behavior monitored by the transformation tracking burial point comprises: the conversion behavior type code and the unique identification of the conversion behavior; wherein the unique identification of the conversion behavior comprises: exposure time, trigger time and trigger user ip;
displaying the recorded data related to the transformation behavior monitored by the transformation tracking buried points to a terminal, wherein the data specifically comprises the following steps:
and according to the conversion behavior type codes, classifying the recorded data related to the conversion behavior monitored by the conversion tracking buried points according to the conversion behavior types to form a table, and displaying the table to the terminal.
6. A data monitoring system based on Js buried point, characterized by comprising:
the embedded point setting unit is used for setting a basic embedded point based on a JavaScript frame on an event to be monitored and monitoring the triggered behavior of the event to be monitored through the basic embedded point; setting a conversion tracking embedded point based on a JavaScript frame on the conversion behavior of the event to be monitored, and monitoring the conversion behavior of the event to be monitored through the conversion tracking embedded point;
the monitoring and recording unit is used for monitoring the conversion behavior of the event after the basic embedded point of the event to be monitored is triggered successfully, and collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point after the conversion tracking embedded point of the event to be monitored is triggered successfully;
and the display unit is used for displaying the recorded data related to the conversion behavior monitored by the conversion tracking buried point to the terminal.
7. The Js buried point based data monitoring system according to claim 6, wherein the buried point setting unit is specifically configured to:
and setting the code of the basic embedded point in the webpage website code of the event to be monitored.
8. The Js buried point based data monitoring system according to claim 6, wherein the buried point setting unit is specifically configured to:
generating a custom field code representing the conversion tracking embedded point, and arranging the custom field code in a service code of the conversion behavior of the event to be monitored; the custom field code also identifies a type of conversion behavior for the event to be monitored.
9. The Js-buried-point-based data monitoring system as claimed in claim 1, wherein the monitoring and recording unit is specifically configured to:
and when the conversion tracking embedded point of the event to be monitored is successfully triggered, generating a mark of successful triggering, and collecting and recording data related to the conversion behavior monitored by the conversion tracking embedded point according to the mark of successful triggering.
10. The Js-based data monitoring system of claim 6, wherein the data relating to conversion behavior monitored by conversion tracking buries comprises: the conversion behavior type code and the unique identification of the conversion behavior; wherein the unique identification of the conversion behavior comprises: exposure time, trigger time and trigger user ip;
the display unit is specifically configured to:
and according to the conversion behavior type codes, classifying the recorded data related to the conversion behavior monitored by the conversion tracking buried points according to the conversion behavior types to form a table, and displaying the table to the terminal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010244568.3A CN111506471A (en) | 2020-03-31 | 2020-03-31 | Data monitoring method and system based on Js (Java native server) embedded points |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010244568.3A CN111506471A (en) | 2020-03-31 | 2020-03-31 | Data monitoring method and system based on Js (Java native server) embedded points |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111506471A true CN111506471A (en) | 2020-08-07 |
Family
ID=71878281
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010244568.3A Pending CN111506471A (en) | 2020-03-31 | 2020-03-31 | Data monitoring method and system based on Js (Java native server) embedded points |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111506471A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101138002A (en) * | 2004-03-31 | 2008-03-05 | Google公司 | Systems and methods for determining user actions |
| US20170139802A1 (en) * | 2014-07-03 | 2017-05-18 | Realeyes Oü | Method of collecting and processing computer user data during interaction with web-based content |
| CN106933722A (en) * | 2017-03-06 | 2017-07-07 | 腾云天宇科技（北京）有限公司 | A kind of web application monitoring method, server and system |
| CN110766476A (en) * | 2019-10-31 | 2020-02-07 | 北京达佳互联信息技术有限公司 | Advertisement processing method and device, computer equipment and storage medium |
-
2020
- 2020-03-31 CN CN202010244568.3A patent/CN111506471A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101138002A (en) * | 2004-03-31 | 2008-03-05 | Google公司 | Systems and methods for determining user actions |
| US20170139802A1 (en) * | 2014-07-03 | 2017-05-18 | Realeyes Oü | Method of collecting and processing computer user data during interaction with web-based content |
| CN106933722A (en) * | 2017-03-06 | 2017-07-07 | 腾云天宇科技（北京）有限公司 | A kind of web application monitoring method, server and system |
| CN110766476A (en) * | 2019-10-31 | 2020-02-07 | 北京达佳互联信息技术有限公司 | Advertisement processing method and device, computer equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 大_斌: "头条转化跟踪", 《HTTPS://WWW.JIANSHU.COM/P/A0D1A1BAC4D0》 * |
| 聚搜: "快手广告代理商:ocpc代码怎么加，快手广告cpa代码怎么加？", 《HTTPS://M.JUSOUCN.COM/JUSOUDONGTAI/1730.HTML》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2018282471B2 (en) | Methods and apparatus to share online media impressions data | |
| CN106294648B (en) | Processing method and device for page access path | |
| JP5764554B2 (en) | Event tracking for electronic paper display | |
| CN110163654B (en) | Advertisement delivery data tracking method and system | |
| CN102314455A (en) | Method and system for calculating click flow of web page | |
| CN111522711B (en) | Data monitoring processing system, method, execution end, monitoring end and electronic equipment | |
| TW532010B (en) | Remote device monitoring | |
| CN112486708B (en) | Page operation data processing method and processing system | |
| CN108322350B (en) | Service monitoring method and device and electronic equipment | |
| WO2016107465A1 (en) | Method, device, and system for implementing card-type desktop | |
| CN110781372B (en) | Method and device for optimizing website, computer equipment and storage medium | |
| CN104881774A (en) | Method and apparatus for automatically establishing schedule | |
| CN110134653B (en) | Method and system for assisting database auditing by using logs | |
| CN109240664B (en) | Method and terminal for collecting user behavior information | |
| CN111506471A (en) | Data monitoring method and system based on Js (Java native server) embedded points | |
| WO2021189766A1 (en) | Data visualization method and related device | |
| CN111859083A (en) | Service data processing method, device, equipment and computer readable storage medium | |
| CN111245880B (en) | Behavior trajectory reconstruction-based user experience monitoring method and device | |
| CN115563423A (en) | Data acquisition method and device, computer equipment and storage medium | |
| CN114465783B (en) | Method, system and storage medium for associating attack point with service message | |
| CN110457089A (en) | Collecting method, device, computer readable storage medium and computer equipment | |
| CN115509872A (en) | Client behavior data acquisition method and device | |
| CN112989162B (en) | Buried point reporting method, device, equipment and storage medium | |
| CN112671615B (en) | Method, system and storage medium for collecting front-end user operation behavior data | |
| CN114595419A (en) | Advertisement page embedded point processing method, system, equipment and storage medium |
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 |