CN110874307B - Method and device for collecting and reporting event buried points - Google Patents
Method and device for collecting and reporting event buried points Download PDFInfo
- Publication number
- CN110874307B CN110874307B CN201810996069.2A CN201810996069A CN110874307B CN 110874307 B CN110874307 B CN 110874307B CN 201810996069 A CN201810996069 A CN 201810996069A CN 110874307 B CN110874307 B CN 110874307B
- Authority
- CN
- China
- Prior art keywords
- event
- data
- reporting
- user
- attribute
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000004590 computer program Methods 0.000 claims description 9
- 238000013500 data storage Methods 0.000 claims description 3
- 230000006870 function Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 11
- 230000006399 behavior Effects 0.000 description 10
- 238000004891 communication Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000009933 burial Methods 0.000 description 5
- 238000004458 analytical method Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000011800 void material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Alarm Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method and a device for collecting and reporting event buried points, and relates to the technical field of computers. One embodiment of the method comprises the following steps: when a user triggers a preset embedded point control, collecting event data corresponding to user operation, wherein the event data comprises an operation identifier; assigning the operation identifier of the event to a next operation attribute of the last event of the event, wherein the next operation attribute is used for identifying a user operation corresponding to the next event of the current event; and reporting the event data of the event and the last event. According to the embodiment, the event attributes and the relation between the events can be reported to the server, so that each operation of the user on the website or the APP can be tracked, the behavior path of the user can be better analyzed, and operation guiding service can be provided for the user.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for collecting and reporting an event buried point.
Background
Buried point analysis is a common data acquisition method for website analysis. The data burial points enable related personnel such as products or operation to custom count more complex user data according to specific requirements. For example, when the behavior of a user is to be tracked, click data related to a page is observed, the conversion rate of a critical path is increased, and the activity effect of a certain event is analyzed, the data embedding is needed in advance, and corresponding data can be observed after a business application system is on line, so that analysis and research are performed. The collected operation data of the user at the client can be uploaded to the server through the data embedding point for subsequent analysis.
With the increasing maturity of the development of the internet, the functions and the accumulation of services of a website, an H5 (hypertext markup language 5 th edition) station, a mobile APP (Application program) and other service output ports are long-time, so that the functions are more and more perfect, and meanwhile, the functions are more and more complex and more bulky. The service output port has definite function entrance and perfect function, but has independent function, which is particularly obvious in application programs on mobile equipment.
Because the functions of the service system are independent, the behavior data of the user can not be collected only through the data embedded points, so that each action of the user on the website or the APP can not be tracked, and the behavior path of the user can not be analyzed better.
Disclosure of Invention
In view of this, the embodiments of the present invention provide a method and an apparatus for collecting and reporting an event buried point, which can report event attributes and relationships between events to a server, so as to track each operation of a user on a website or an APP, better analyze a behavior path of the user, and provide an operation guidance service for the user.
In order to achieve the above object, according to an aspect of the embodiments of the present invention, a method for collecting and reporting an event buried point is provided.
A method for collecting and reporting event buried points comprises the following steps: when a user triggers a preset embedded point control, collecting event data corresponding to user operation, wherein the event data comprises an operation identifier; assigning the operation identifier of the event to a next operation attribute of a last event of the event, wherein the next operation attribute is used for identifying a user operation corresponding to the next event of the current event; and reporting the event and the event data of the last event.
Optionally, attributes are added to the control by classifying the control and associating the attributes, and then the added attributes are assigned to bury the control.
Optionally, if the event is a null event, the next operation attribute of the previous event is assigned as null.
Optionally, if the event is the first event, event data of the event is directly reported.
Optionally, after collecting event data corresponding to the user operation, the method further includes: and storing the collected event data.
According to another aspect of the embodiment of the invention, a collecting and reporting device for an event buried point is provided.
An event buried point collecting and reporting device, comprising: the data acquisition module is used for acquiring event data corresponding to user operation when a user triggers a preset embedded point control, wherein the event data comprises an operation identifier; the attribute assignment module is used for assigning the operation identifier of the event to the next operation attribute of the last event of the event, wherein the next operation attribute is used for identifying the user operation corresponding to the next event of the current event; and the data reporting module is used for reporting the event data of the event and the last event.
Optionally, attributes are added to the control by classifying the control and associating the attributes, and then the added attributes are assigned to bury the control.
Optionally, if the event is a null event, the next operation attribute of the previous event is assigned as null.
Optionally, if the event is the first event, event data of the event is directly reported.
Optionally, the system further comprises a data storage module for: and after the event data corresponding to the user operation is collected, storing the collected event data.
According to still another aspect of the embodiment of the invention, an electronic device for collecting and reporting event buried points is provided.
An electronic device for collecting and reporting event buried points, comprising: one or more processors; and the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the collection and reporting method of the event buried points provided by the embodiment of the invention.
According to yet another aspect of an embodiment of the present invention, a computer-readable medium is provided.
A computer readable medium has stored thereon a computer program which when executed by a processor implements the method for collecting and reporting event buried points provided by the embodiment of the present invention.
One embodiment of the above invention has the following advantages or benefits: by collecting event data corresponding to user operation, assigning an operation identifier included in the event data to a next operation attribute of a previous event, and reporting the event and time data of the previous event, the relation between the event attribute and the event is reported to a server, so that each operation of a user on a website or an APP can be tracked, the behavior path of the user can be better analyzed, and operation guiding service can be provided for the user.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of main steps of a method for collecting and reporting event buried points according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of the main modules of a device for collecting and reporting event burial points according to an embodiment of the invention;
FIG. 3 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;
Fig. 4 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
In order to solve the problems in the prior art, the invention provides a method and a device for collecting event buried points, which can track each operation of a user on a website or an APP by collecting and analyzing the event buried points, better analyze the behavior path of the user and provide operation guiding service for the user.
Event burial points are different from common data burial points. Events are used to track or record user behavior or business processes, such as: registering account numbers, logging in, watching videos, praying, commenting, paying attention, and the like. The three elements of an event include: operations, parameters/attributes and attribute values, wherein operations such as click, drag, etc.; the parameter/attribute may be any attribute associated with the event, including the person triggering the event, time, device, business information, etc.; the attribute value refers to a value parameter of the corresponding attribute.
Taking event burying of the APP as an example, when event burying is carried out, event attributes can be added into a control of the APP by a software developer, and then required data are collected in a mode of assigning the event attributes.
When reporting an event buried point, reporting modes can be divided into two modes according to different acquisition time of the buried point: developer mode and online mode. The developer mode is to collect and report static events such as clicking, jumping and the like in the process of developing functions of the developer in the development and debugging stages; the online mode is that when a user enters a container interface (which is equivalent to a display interface of an APP and can receive all operations of the user on a current page), the container loads an event or triggers the event, and the event is collected and reported. For the two reporting modes of the event buried point, the server may perform different processing after collecting the reported event buried point, but the processing logic of the client for collecting and reporting the event buried point is the same, namely: and triggering an event embedded point control of the client interface by the user, and collecting the event embedded point by the APP and reporting the event embedded point to the server. The user operation is not limited to clicking, but may be sliding, double clicking, dragging, or the like.
Because the event buried points are different from the common data buried points, the collection and reporting modes of the event buried points are also different from the collection and reporting modes of the common data buried points. The following describes a specific implementation process of the method for collecting and reporting event buried points according to the present invention with reference to the accompanying drawings.
Fig. 1 is a schematic diagram of main steps of a method for collecting and reporting an event buried point according to an embodiment of the present invention. As shown in fig. 1, the method for collecting and reporting event buried points in the embodiment of the present invention mainly includes the following steps S101 to S103.
Step S101: when a user triggers a preset embedded point control, event data corresponding to user operation is collected, wherein the event data comprises an operation identifier.
The container interface of the application client is mainly composed of a control for displaying information and receiving user operation. When a user enters a container interface of a client and executes operation on a control, if the control is a control with a buried point set in advance, the buried point program can acquire event data corresponding to the user operation in real time.
In the embodiment of the invention, the attribute is added to the control by classifying the control and associating the attribute, and then the added attribute is assigned to bury the control. Controls are, for example, buttons or options on the application container interface, etc. Specifically, for example, a developer may add an operation identifier (actionID) attribute to a control by associating the operation identifier (actionID) attribute with a control class used to implement the user interface presentation (e.g., control class UIView in a mobile operating system iOS system developed by apple corporation, etc.); as another example, container identification (containerID) attributes may be added to a control by associating the container identification (containerID) attributes with a control class (e.g., control class UIViewController in an iOS system, etc.) for view display control, and so on. Wherein the operation identifier actionID is guaranteed to be unique within the container.
And then, the developer performs assignment on the added attribute to realize embedding the control. For example: the operation identification (actionID) attribute of the control is assigned to realize embedding of the control, wherein the control which does not assign the operation identification (actionID) attribute is not embedded, and therefore the acquired event is an empty event.
When a user executes an operation on the container interface, the embedded point program can collect event data corresponding to the user operation in real time, and then the collected event data is transmitted to the collecting unit to be collected. The collected event data mainly comprises class names of controls operated by a user, position coordinates of the controls on a container interface, operation identifiers actionID and the like. In the event data transmission, the event data transmission may be performed based on event transmission related technologies of the system, for example: for iOS systems, event data may be passed to a collection unit based on the iOS system's event-passing response chain technique.
Event data (including data related to the container, etc.) corresponding to all operations of the user on the container interface are transmitted through an event transmission method SENDEVENT method (void) SENDEVENT (UIEvent) event of the APP agent class of the application program. By adding new logic to the callback class appEvent for responding to the application system event, the purpose of receiving the event data corresponding to the user operation is achieved, and the event data corresponding to the user operation can be transferred to a storage unit (for example, a cache unit).
The storage unit is used for storing the event data so as to sort the event data and report the sorted data to the server. The storage unit continuously receives the collected event data, collates the event data according to step S102, and reports the collated time data according to step S103.
Step S102: and assigning the operation identification of the event to the next operation attribute of the last event of the event, wherein the next operation attribute is used for identifying the user operation corresponding to the next event of the current event.
According to the embodiment of the invention, in order to record and analyze the association relation between the operations of the user, a next operation (nextActionID) attribute is added to the event corresponding to the user operation, and is used for identifying the user operation corresponding to the next event of the current event.
Each time the storage unit receives an event data, the operation identifier of the event is assigned to the attribute of the next operation (nextActionID) of the previous event, so that the association relationship between the operations of the user is recorded, the action path of the user is better analyzed, and the operation guiding service is provided for the user.
Step S103: and reporting the event data of the event and the last event.
Because the related record of the event is newly added and the attribute of the next operation (nextActionID) of the previous event is modified each time new event data is received, the event and the event data of the previous event need to be reported together each time, so that the server can update the event data of the previous event, and the behavior path of the user is obtained according to the event data.
When event data is received for the first time, that is, the event is the first event, the event data of the event is directly reported. At this time, there is no previous event to the event, and thus, no other operation is required.
If the received event data is null, i.e., the event is a null event, then the next operation (nextActionID) attribute that the previous event had is assigned a null.
According to one embodiment of the invention, the received event data may be saved in a form similar to a queue, namely: data is added from the tail of the queue each time. Each time collected event data (e.g., including operations identifier actionID, container identifier containerID, remark comments, etc.) is received, the newly received event data may be assigned to event 1, and the original event 1 may be assigned to event 2, and so on. Then, the next operation (nextActionID) attribute for event 2 is assigned as the operation identifier actionID for event 1, and if event 1 is a null event, then nextActionID for event 2 is null. And then, the event data of the event 1 and the event 2 can be reported in a mode called by a notification center or an interface of the system. Thus, each attribute of the event and the relation between the events can be reported to the server. Because the data reported to the server side has redundancy, the server can perform redundancy elimination processing on the reported data to complete the collection work of all event data.
Fig. 2 is a schematic diagram of main modules of a device for collecting and reporting an event buried point according to an embodiment of the present invention. As shown in fig. 2, the device 200 for collecting and reporting an event buried point according to an embodiment of the present invention mainly includes a data acquisition module 201, an attribute assignment module 202, and a data reporting module 203.
The data acquisition module 201 is configured to acquire event data corresponding to user operation when a user triggers a preset embedded point control, where the event data includes an operation identifier;
the attribute assignment module 202 is configured to assign an operation identifier of the event to a next operation attribute that a previous event of the event has, where the next operation attribute is used to identify a user operation corresponding to the next event of the current event;
the data reporting module 203 is configured to report the event data of the event and the previous event.
According to the embodiment of the invention, the attribute is added to the control in a mode of classifying the control and associating the attribute, and then the added attribute is assigned to bury the control.
According to one embodiment of the invention, if the event is a null event, the next operational attribute that the previous event has is assigned as null.
According to another embodiment of the present invention, if the event is the first event, the event data of the event is directly reported.
According to yet another embodiment of the present invention, the collecting and reporting device 200 of the event burial point may further include a data storage module (not shown in the figure) for:
And after the event data corresponding to the user operation is collected, storing the collected event data.
According to the technical scheme of the embodiment of the invention, through collecting the event data corresponding to the user operation, assigning the operation identification included in the event data to the next operation attribute of the last event, and then reporting the event and the time data of the last event, the relation between the event attribute and the event is reported to the server, so that each operation of the user on the website or the APP can be tracked, the behavior path of the user can be better analyzed, and the operation guiding service can be provided for the user.
In addition, the technical scheme of the invention has no intrusion of engineering codes of the application program, ensures the running stability of the application program, and has the advantage of low access cost of developers.
Fig. 3 illustrates an exemplary system architecture 300 to which the method for collecting and reporting event buried points or the device for collecting and reporting event buried points according to an embodiment of the present invention may be applied.
As shown in fig. 3, the system architecture 300 may include terminal devices 301, 302, 303, a network 304, and a server 305. The network 304 is used as a medium to provide communication links between the terminal devices 301, 302, 303 and the server 305. The network 304 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 305 via the network 304 using the terminal devices 301, 302, 303 to receive or send messages or the like. Various communication client applications may be installed on the terminal devices 301, 302, 303, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 301, 302, 303 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 305 may be a server providing various services, such as a background management server (by way of example only) providing support for shopping-type websites browsed by users using the terminal devices 301, 302, 303. The background management server may analyze and process the received data such as the product information query request, and feedback the processing result (e.g., the target push information, the product information—only an example) to the terminal device.
It should be noted that, the method for collecting and reporting the event buried points provided in the embodiment of the present invention is generally executed by the server 305, and accordingly, the device for collecting and reporting the event buried points is generally disposed in the server 305.
It should be understood that the number of terminal devices, networks and servers in fig. 3 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 4, there is illustrated a schematic diagram of a computer system 400 suitable for use in implementing a terminal device or server in accordance with an embodiment of the present invention. The terminal device or server shown in fig. 4 is only an example, and should not impose any limitation on the functions and scope of use of the embodiments of the present invention.
As shown in fig. 4, the computer system 400 includes a Central Processing Unit (CPU) 401, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 402 or a program loaded from a storage section 408 into a Random Access Memory (RAM) 403. In RAM 403, various programs and data required for the operation of system 400 are also stored. The CPU 401, ROM 402, and RAM 403 are connected to each other by a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.
The following components are connected to the I/O interface 405: an input section 406 including a keyboard, a mouse, and the like; an output portion 407 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage section 408 including a hard disk or the like; and a communication section 409 including a network interface card such as a LAN card, a modem, or the like. The communication section 409 performs communication processing via a network such as the internet. The drive 410 is also connected to the I/O interface 405 as needed. A removable medium 411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed on the drive 410 as needed, so that a computer program read therefrom is installed into the storage section 408 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 409 and/or installed from the removable medium 411. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 401.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described units or modules may also be provided in a processor, for example, as: the processor comprises a data acquisition module, an attribute assignment module and a data reporting module. The names of these units or modules do not limit the units or modules themselves in some cases, for example, the data collection module may also be described as "a module for collecting event data corresponding to a user operation when the user triggers a preset embedded point control".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: when a user triggers a preset embedded point control, collecting event data corresponding to user operation, wherein the event data comprises an operation identifier; assigning the operation identifier of the event to a next operation attribute of a last event of the event, wherein the next operation attribute is used for identifying a user operation corresponding to the next event of the current event; and reporting the event and the event data of the last event.
According to the technical scheme of the embodiment of the invention, through collecting the event data corresponding to the user operation, assigning the operation identification included in the event data to the next operation attribute of the last event, and then reporting the event and the time data of the last event, the relation between the event attribute and the event is reported to the server, so that each operation of the user on the website or the APP can be tracked, the behavior path of the user can be better analyzed, and the operation guiding service can be provided for the user.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (12)
1. The method for collecting and reporting the event buried points is characterized by comprising the following steps:
when a user triggers a preset embedded point control, collecting event data corresponding to user operation, wherein the event data comprises an operation identifier;
assigning an operation identifier of an event to a next operation attribute of a last event of the event, wherein the next operation attribute is used for identifying a user operation corresponding to the next event of the current event;
and reporting the event and the event data of the last event, and updating the event data of the last event.
2. The method of claim 1, wherein attributes are added to the control by categorizing and associating the attributes with the control, and then assigning the added attributes to bury the control.
3. The method of claim 1, wherein if the event is a null event, assigning a next operational attribute possessed by the previous event to be null.
4. The method of claim 1, wherein if the event is a first event, reporting event data of the event directly.
5. The method of claim 1, further comprising, after collecting event data corresponding to the user operation:
and storing the collected event data.
6. The utility model provides a collection reporting device of event buried point which characterized in that includes:
The data acquisition module is used for acquiring event data corresponding to user operation when a user triggers a preset embedded point control, wherein the event data comprises an operation identifier;
The attribute assignment module is used for assigning the operation identifier of the event to the next operation attribute of the last event of the event, wherein the next operation attribute is used for identifying the user operation corresponding to the next event of the current event;
And the data reporting module is used for reporting the event and the event data of the last event and updating the event data of the last event.
7. The apparatus of claim 6, wherein attributes are added to the control by categorizing and associating the attributes with the control, and then assigning the added attributes to bury the control.
8. The apparatus of claim 6, wherein if the event is a null event, a next operational attribute possessed by the previous event is assigned a null.
9. The apparatus of claim 6, wherein if the event is a first event, reporting event data for the event directly.
10. The apparatus of claim 6, further comprising a data storage module for:
And after the event data corresponding to the user operation is collected, storing the collected event data.
11. An electronic device for collecting and reporting event buried points, comprising:
One or more processors;
Storage means for storing one or more programs,
When executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-5.
12. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810996069.2A CN110874307B (en) | 2018-08-29 | 2018-08-29 | Method and device for collecting and reporting event buried points |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810996069.2A CN110874307B (en) | 2018-08-29 | 2018-08-29 | Method and device for collecting and reporting event buried points |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110874307A CN110874307A (en) | 2020-03-10 |
| CN110874307B true CN110874307B (en) | 2024-08-16 |
Family
ID=69714615
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810996069.2A Active CN110874307B (en) | 2018-08-29 | 2018-08-29 | Method and device for collecting and reporting event buried points |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110874307B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111581356B (en) * | 2020-05-15 | 2023-08-01 | 北京易数科技有限公司 | User behavior path analysis method and device |
| CN111639007B (en) * | 2020-05-29 | 2024-05-03 | 北京金山云网络技术有限公司 | Data processing method, device, terminal and computer readable storage medium |
| CN113961110B (en) * | 2020-07-01 | 2024-08-13 | 腾讯科技（深圳）有限公司 | User operation response method, device, computer equipment and storage medium |
| CN113742161A (en) * | 2020-09-07 | 2021-12-03 | 北京沃东天骏信息技术有限公司 | Buried point reporting method and device |
| CN112579408A (en) * | 2020-10-29 | 2021-03-30 | 上海钱拓网络技术有限公司 | Classification method of embedded point information |
| CN112579237B (en) * | 2020-12-17 | 2024-06-11 | 百果园技术(新加坡)有限公司 | Event response method, device, equipment and medium based on MVVM mode |
| CN114003792A (en) * | 2021-09-14 | 2022-02-01 | 北京房江湖科技有限公司 | Path tracking method and device, electronic equipment and readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107491488A (en) * | 2017-07-18 | 2017-12-19 | 北京京东尚科信息技术有限公司 | The method and apparatus of page data collection |
| CN108153528A (en) * | 2017-12-15 | 2018-06-12 | 东软集团股份有限公司 | Extension processing method, device, storage medium and the electronic equipment of procedural model |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7970946B1 (en) * | 2007-11-27 | 2011-06-28 | Google Inc. | Recording and serializing events |
| US8365075B2 (en) * | 2009-11-19 | 2013-01-29 | International Business Machines Corporation | Recording events in a virtual world |
| CN107092544B (en) * | 2016-05-24 | 2020-09-15 | 口碑控股有限公司 | Monitoring method and device |
| CN107688943B (en) * | 2016-08-04 | 2021-08-17 | 阿里巴巴集团控股有限公司 | Data processing method, device and system |
| CN107784504B (en) * | 2017-07-31 | 2020-11-03 | 平安科技（深圳）有限公司 | Method for generating return visit event of client and terminal equipment |
-
2018
- 2018-08-29 CN CN201810996069.2A patent/CN110874307B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107491488A (en) * | 2017-07-18 | 2017-12-19 | 北京京东尚科信息技术有限公司 | The method and apparatus of page data collection |
| CN108153528A (en) * | 2017-12-15 | 2018-06-12 | 东软集团股份有限公司 | Extension processing method, device, storage medium and the electronic equipment of procedural model |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110874307A (en) | 2020-03-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110874307B (en) | Method and device for collecting and reporting event buried points | |
| CN107491488B (en) | Page data acquisition method and device | |
| CN107809331B (en) | Method and device for identifying abnormal flow | |
| CN109446274B (en) | Method and device for managing BI metadata of big data platform | |
| CN111190888A (en) | Method and device for managing graph database cluster | |
| CN110196790A (en) | The method and apparatus of abnormal monitoring | |
| CN111813685B (en) | Automatic test method and device | |
| CN112784152B (en) | Method and device for marking user | |
| CN110554951B (en) | Buried point management method and device | |
| US20150066965A1 (en) | Data processing, data collection | |
| CN111435326B (en) | Method and device for analyzing crash log | |
| CN111813765B (en) | Method, device, electronic equipment and computer readable medium for processing abnormal data | |
| CN116450622B (en) | Method, apparatus, device and computer readable medium for data warehouse entry | |
| CN111124858A (en) | Embedded point-free plug-in data processing method and system, terminal device and storage medium | |
| CN113111367B (en) | Security information management method, device and system | |
| CN113515715B (en) | Buried point event code generation method, buried point event code processing method and related equipment | |
| CN112132722B (en) | Government hot line quantity trend abnormity determining method and device, electronic equipment and medium | |
| CN111464599B (en) | Message pushing method, system, device, computer readable storage medium and equipment | |
| CN113590985A (en) | Page jump configuration method and device, electronic equipment and computer readable medium | |
| CN113778847A (en) | Test report generation method and device | |
| CN113760695A (en) | Method and device for positioning problem code | |
| CN112182080A (en) | Data integration system and data processing method based on data integration system | |
| CN112860538A (en) | Method and device for performing interface regression test based on online log | |
| CN113254325A (en) | Test case processing method and device | |
| CN112749204A (en) | Method and device for reading data |
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 |