CN113254320A

CN113254320A - Method and device for recording user webpage operation behaviors

Info

Publication number: CN113254320A
Application number: CN202110627718.3A
Authority: CN
Inventors: 黄振增
Original assignee: Shenzhen Golden Axe Network Technology Co ltd
Current assignee: Shenzhen Golden Axe Network Technology Co ltd
Priority date: 2021-06-05
Filing date: 2021-06-05
Publication date: 2021-08-13

Abstract

The embodiment of the application discloses a method for recording user webpage operation behaviors, which is applied to a client and comprises the following steps: when a client side monitors an event that a user triggers a backtracking page, DOM data triggering the backtracking page is collected; serializing the DOM data to obtain virtualized DOM data; judging whether the virtualized DOM data is a key frame or not, and if so, uploading the key frame to a cloud server; if not, caching the virtualized DOM data to a client cache, and when the virtualized DOM data reaches the client cache threshold value, sending the virtualized DOM data to the cloud server. The method can prevent the page from being missed and reduce the probability of frame dropping; and the problem of data loss caused by accumulation of a large amount of cache data in a weak network environment is greatly solved.

Description

Method and device for recording user webpage operation behaviors

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for recording a user webpage operation behavior, an electronic device, and a computer-readable medium.

Background

In recent years, blowout type outbreaks are met by internet insurance, the internet insurance takes users as the center, original product design methods, pricing modes and insurance acceptance wind control modes of traditional insurance companies are remodeled by relying on massive user data of the internet, and a large number of users are attracted to select the internet insurance. The online insurance sales often does not have a recording and video recording link, so that the problems of difficult proof taking, difficult responsibility confirmation and the like can occur when claim settlement disputes occur, an online sales behavior traceable mechanism is established, and the restorable sales process is realized.

At present, a backtracking system firstly faces the problem that a large number of DOM nodes are acquired in a short time, so that a main thread is blocked, and program crash can be caused seriously, which is intolerable to an applicant, and the experience of a user is very poor.

Disclosure of Invention

The embodiment of the application provides a method for recording user webpage operation behaviors, which can accurately prevent page missing recording and reduce the probability of frame dropping; and the problem of data loss caused by accumulation of a large amount of cache data in a weak network environment is greatly solved.

The embodiment of the application provides a method for recording a user webpage operation behavior, which comprises the following steps:

when a client side monitors an event that a user triggers a backtracking page, DOM data triggering the backtracking page is collected;

serializing the DOM data to obtain virtualized DOM data;

judging whether the virtualized DOM data is a key frame;

if yes, uploading the key frame to a cloud server;

if not, caching the virtualized DOM data to a client cache, and when the virtualized DOM data reaches the client cache threshold value, sending the virtualized DOM data to the cloud server.

In some embodiments, after the client monitors the event triggering the backtracking page and the loading of the first backtracking page is successful, a unique backtracking ID is generated and cached to the client.

In some embodiments, further comprising:

requesting data from a cloud server according to the backtracking ID, and receiving backtracking data returned by the cloud server;

deserializing the traceable data to establish a virtual DOM tree;

and rendering a playing page according to the virtual DOM tree, and playing the rendered page.

In some embodiments, before the deserializing for each frame of data, the deserializing further comprises:

the player of the client verifies the integrity of the traceable data;

decompressing the traceable data in response to a successful verification;

and constructing a virtual DOM tree according to the decompressed backtraceable data.

In some embodiments, further comprising:

monitoring the DOM data by using a DOM change observer;

responding to the condition that the trigger event exceeds a threshold value, and collecting DOM data of the change node by adopting a throttling function;

serializing DOM data of the changed DOM nodes when the DOM data reaches a threshold value;

and responding to the condition that the data volume of the DOM data exceeds the threshold value, and distributing node identifications to the current node, the father node and the brother node before the current node finishes collecting the DOM data.

In some embodiments, further comprising:

sending the virtualized DOM data to the cloud server by adopting a message queue;

when the data volume of the virtualized DOM data is larger than a threshold value, the virtualized DOM data is directly uploaded to the cloud server;

and merging a plurality of pieces of the virtualized DOM data, and uploading the merged data to the cloud server.

In some embodiments, the present application further provides a method for recording a user webpage operation behavior, which is applied to a cloud server side, and includes the following steps:

receiving virtualized DOM data sent by a client;

preprocessing the virtualized DOM data, and temporarily storing the preprocessed data to an OSS;

and storing the key information in the virtualized DOM data into a database, and establishing an index.

In some embodiments, the present application further provides an apparatus for recording a user webpage operation behavior, including:

the data acquisition module is used for acquiring DOM data triggering the backtracking page when the client monitors that the user triggers the event of the backtracking page;

the data conversion module is used for carrying out serialization processing on the DOM data to obtain virtualized DOM data;

the data uploading module is used for judging whether the virtualized DOM data is a key frame;

if yes, uploading the key frame to a cloud server;

the data receiving module is used for receiving the virtualized DOM data sent by the client;

the data storage module is used for preprocessing the virtualized DOM data and temporarily storing the preprocessed data to an OSS; and storing the key information in the virtualized DOM data into a database, and establishing an index.

In some embodiments, the present application also provides an electronic device including a memory and a processor, the memory having stored thereon computer-executable instructions, and the processor implementing the method described above when executing the computer-executable instructions on the memory.

In some embodiments, the present application also proposes a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the above-described method.

According to the method and the device for recording the webpage operation behaviors of the user, when the client successfully loads the webpage or switches the webpage, the current webpage recording is started, each time one frame of acquisition is completed, the virtual DOM node ID is pre-generated, program blocking and false death are reduced, and by judging the attribute of the acquired DOM data, if the acquired DOM node ID is the key frame, the data key frame is identified for real-time reporting, so that missing recording of the webpage is prevented, and the probability of frame dropping is reduced; if the non-key frame is cached by the client, the problem of data loss caused by accumulation of a large amount of cached data in a weak network environment is greatly solved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments will be briefly introduced below.

FIG. 1 is a schematic diagram of an application scenario of a method for recording user webpage operation behavior in some embodiments;

FIG. 2 is a flow diagram of a method of recording user web page operational behavior in some embodiments;

FIG. 3a is a flow diagram of DOM data collection in some embodiments;

FIG. 3b is an example diagram of DOM data collection in some embodiments;

FIG. 4a is a flow diagram of sending virtualized DOM data to a cloud server in some embodiments;

FIG. 4b is an example diagram of virtualized DOM data being sent to a cloud server in some embodiments;

FIG. 5a is a flowchart of a method for recording user web page operation behavior in further embodiments;

FIG. 5b is a diagram illustrating a method for recording user web page operation behavior in further embodiments;

fig. 6 is a schematic diagram of cloud server side stored data in some embodiments;

FIG. 7a is a flow diagram that illustrates the act of playing a user-manipulated web page in some embodiments;

FIG. 7b is a diagram illustrating the act of playing a user-operated web page in further embodiments;

FIG. 8 is a block diagram of an apparatus for recording user web page operation behavior in some embodiments;

FIG. 9 is a block diagram of an apparatus for recording user web page manipulation behavior in some embodiments;

fig. 10 is a schematic structural diagram of an apparatus for recording user web page operation behaviors according to some embodiments.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application, and it should be understood that the described embodiments are some, but not all embodiments of the present application. 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 application.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted, depending on the context, to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".

The internet insurance refers to the networking of the whole process of insurance such as insurance information consultation, insurance plan design, insurance application, payment, underwriting, insurance policy information inquiry, insurance change, renewal payment, claim settlement and payment. Internet insurance is a new insurance marketing mode using computer internet as a medium, and refers to economic behaviors of an insurance company or a novel third-party insurance network which uses internet and electronic commerce technology as tools to support operation and management activities of insurance sales. Online product consultation, sending of the electronic insurance policy to a mailbox and the like can be completed by clicking a mouse and the like. The user needs to operate on the browser of the client, and the operation result is stored in the cloud server, so that the user can conveniently check, backtrack and the like. In this embodiment, the client refers to an electronic device such as a computer with a data entry function, and the electronic device may also have an image/video capture module such as a camera, which is not limited herein.

In the embodiment of the present invention, a method for recording a user webpage operation behavior is provided, and the method is applied to a system for recording a user webpage operation behavior, and the system is, as shown in fig. 1, divided into a data acquisition end (recording), a virtualized DOM (Document Object Model), a browser cache, a data conversion (data reporting), a cloud service, and a data playing (playback). The data acquisition end is various clients loaded on the terminal, and can be in various forms, such as Web, App, small programs and the like. The terminal is an electronic device such as a computer, a smart phone, a tablet computer, and the like having data input and processing functions. And the client serializes the DOM in the page, namely virtualizing the DOM, and storing the DOM in the browser cache in a character string mode. And when a certain threshold value is reached, the data conversion module compresses the data and uploads the data to the cloud server.

The cloud Service end provides an interface gateway, data cleaning, data arranging, data permanent Storage, data remote playing and the like, and temporarily stores the received data to an Object Storage Service (OSS). And when a flow end event is received, cleaning and arranging the current recording process data, finally storing the key information into a database, and establishing an index.

The data playing is that a client is used as a carrier, requests data from a cloud server, deserializes each frame of data, establishes a virtual DOM tree, and delivers the virtual DOM tree to the client to render a real DOM tree, so that the whole operation process of a user is clear and visible.

In the embodiment of the present invention, a method for recording a user webpage operation behavior as shown in fig. 2 includes the following steps:

step 201, when the client monitors that the user triggers the event of the backtracking page, collecting DOM data triggering the backtracking page.

In this embodiment, the event that the user triggers the backtracking page includes that when the user successfully clicks the browser to load the page or switches the page, the backtracking page may be in various forms, and the events may be triggered by a mouse click or a touch screen touch click, through the client such as a Web, an App, a applet, or the like. The DOM is a programmatic interface for HTML and XML documents. It provides a structured representation of a document and defines a way to access the structure from a program to change the structure, style and content of the document.

Further, after the client monitors an event triggering the backtracking page and the loading of the first backtracking page is successful, a unique backtracking ID is generated and cached to the client.

In this embodiment, the trace-back ID is a global identifier for identifying a series of operations, and each page uses the global identifier from the beginning to the end of the trace-back. When the client successfully loads the first backtracking page, a unique backtracking ID is generated and cached to the client, and in the whole backtracking process, the ID is globally unique, and the uniqueness is not only unique on the current client but is unique on all clients.

And 203, performing serialization processing on the DOM data to obtain virtualized DOM data.

The virtual DOM is an abstraction of the DOM, essentially a JavaScript object, which is a much lighter description of the DOM. And the client serializes the DOM data in the backtracking page, namely virtualizing the DOM.

Step 205, determine whether the virtualized DOM data is a key frame, if yes, execute step 207, and if not, execute step 209.

In this embodiment, the key frame is used to provide complete webpage data for a moment during playback, and the key frame completes one acquisition of a webpage when the page is completely loaded or the recorded data reaches a set size or the recording time reaches a set duration.

If the key frame is the key frame, step 207 is executed to upload directly to the cloud server, otherwise, step 209 is executed.

And step 207, uploading the key frame to a cloud server.

If the key frame is the key frame, in order to ensure the integrity and the importance of the data, the key frame is directly uploaded to a cloud server in real time, wherein the uploading format is as follows: partner ID/product ID/backtrack ID/acquisition time-page ID-page session unique ID-self-incrementing frame number.

Step 209, caching the virtualized DOM data to a client cache, and sending the virtualized DOM data to the cloud server when the virtualized DOM data reaches the client cache threshold.

If the virtualized DOM data is not a key frame, the virtualized DOM data is stored to the client cache in the form of a string. And when a certain threshold value is reached and the virtualized DOM data reaches a client cache threshold value, sending the virtualized DOM data to the cloud server.

According to the method for recording the webpage operation behaviors of the user, when the client successfully loads the webpage or the webpage is switched, the current webpage recording is started, each time one frame of acquisition is completed, the virtual DOM node ID is pre-generated, program blocking and false death are reduced, and by judging the attribute of the acquired DOM data, if the attribute is the key frame, the data key frame is identified for real-time reporting, so that the missing recording of the webpage is prevented, and the probability of frame dropping is reduced; if the non-key frame is cached by the client, the problem of data loss caused by accumulation of a large amount of cached data in a weak network environment is greatly solved.

In some embodiments, as shown in fig. 3a and 3b, further comprising:

step 302, monitoring the DOM data by using a DOM alteration viewer.

In the whole DOM data acquisition process, a DOM change observer (MutationObserver) monitors and triggers frequent call-back or calls back a large amount of data once, so that an interface is jammed or a false death event is caused.

And 304, in response to the condition that the trigger event exceeds the threshold value, adopting a throttling function to collect DOM data of the change node.

In response to the trigger event exceeding a threshold, i.e. for frequent triggering, a throttling function is introduced, and the changed nodes are collected first. For example, when a user scrolls through pages quickly, page positions are frequently recorded (non-essential data), preventing frequent collection. Or when a premium selection selector is popped up, the selector comprises thousands of nodes (namely a large number of nodes are generated), and it is time-consuming to collect nodes, and at this time, a throttling function is needed to collect DOM data of the changed nodes.

And when the DOM data reach a threshold value, serializing the DOM data of the changed DOM nodes.

And step 306, responding to the fact that the data volume of the DOM data exceeds the threshold value, and distributing node identifiers to the current node, the father node and the brother node before the current node finishes acquiring the DOM data.

Aiming at large data volume, the major cycle is mainly optimized, and when the nodes are completely collected, node identifications are distributed to the current node, the father node and the brother node in advance.

By the method, the current node can be serialized only after the father node is serialized, the algorithm complexity O (n ^2) of the embodiment is reduced to O (n), the large cycle is eliminated, and the DOM data acquisition speed is increased.

In some embodiments, as shown in figures 4a and 4b, a message queue is employed to send the virtualized DOM data to the cloud server;

step 402, when the data volume of the virtualized DOM data is greater than a preset threshold, directly uploading the data to the cloud server.

In this embodiment, a message queue is used to control the concurrency number and prevent the page interface resources from being preempted. And taking out IndexedDB (a transaction database embedded in the browser) data, directly reporting an output data frame of the acquisition end if the data volume is larger than a preset threshold, otherwise caching the data frame in a data queue, and writing the data frame into the IndexedDB when the data volume reaches the preset threshold, thereby preventing the data frame from being frequently written into the DB (a terminal memory) and causing performance loss.

And step 404, merging the multiple pieces of virtualized DOM data, and uploading the merged data to the cloud server.

The reporting module combines a plurality of pieces of virtual DOM data to report at one time, so that the problem that the mobile terminal weak network consumes time when establishing connection for multiple times is solved. If there is no data in the DB, the reporting module will exit until the new event comes.

In addition, the backtracking page or the new page (different domains) is actively closed in the user operation process, and the data in the data queue is synchronized to the client for caching, so that the data is not lost when the page exits.

In some embodiments, as shown in fig. 5a and 5b, a method for recording user webpage operation behavior is further provided, which is applied to a cloud server side, and includes the following steps:

step 501, receiving virtualized DOM data sent by a client.

The client continuously sends data to the server, the cloud server provides an interface gateway to receive the data sent by the client, performs data cleaning, data arrangement, data permanent Storage, data remote playing and the like, and temporarily stores the received data in an OSS (Object Storage Service). When a data transmission end event is received, cleaning and arranging the recording process data, finally storing the key information into a database, and establishing an index.

Step 503, preprocessing the virtualized DOM data, and temporarily storing the preprocessed data to the OSS.

And 505, storing the key information in the virtualized DOM data into a database, and establishing an index.

In this embodiment, as shown in fig. 6, the OSS file of the whole process is screened out according to the backtracking ID in the request URL, whether the check file MD5 is consistent or not is checked, and if not, the check file MD5 is screened out. And then sorting all files according to the file acquisition time, merging files with the same page ID in the file name according to a first frame, a second frame, an nth frame, storing the files in an OSS, and updating the path of the file name to a database. And after the combination is completed, the order ID and the backtracking ID are associated to the database. Wherein, the time mark on the graph is the page opening starting time-the page closing ending time, and the product _ detail is the page mark.

If the process is abnormal, the daemon process triggers the backtracking cleaning task again, if the backtracking cleaning task is abnormal after 3 times of retrying, the related users are notified in a mail and message mode, and in the embodiment, the related users comprise insurance users or insurance agents and the like.

In some embodiments, the cloud server further comprises: and visualizing the behavior of the user operation webpage.

Through the data cleaning and arranging of the cloud server side of the embodiment, the whole ordering process is stored, and the operation of a user is clear through the visualization of the editing background.

In some embodiments, as shown in fig. 7a and 7b, the method for recording the operation behavior of the user webpage applied to the client further includes:

step 701, sending a data playing request to a cloud server according to the backtracking ID, and receiving backtracking data returned by the cloud server.

In this embodiment, the client sends a data playing request to the cloud server according to the backtracking ID, and the cloud server queries corresponding backtracking data according to the backtracking ID in the request, where the backtracking data includes a video stream operated by a user.

In one example, a user (such as a developer) inputs a playback password at a corresponding position of a client by clicking a playback link of the client, and after the password is verified, the cloud server returns the video stream.

Step 702, deserializing the traceable data and establishing a virtual DOM tree.

Before deserializing the traceable data, the player of the client needs to verify the integrity of the traceable data, namely the existence of a full frame, and if the verification is successful, deserializing is performed, namely the traceable data is decompressed, the first full frame is confirmed, and then a virtual DOM tree is constructed.

And step 703, rendering a playing page according to the virtual DOM tree, and playing the rendered page.

When loading of CSS (Cascading Style Sheets) dependent on a playing page is completed, a player starts a requestAnamationframe timer, executes a subsequent data frame, takes out a first frame N of a data queue, if the current system time-first frame playing time > N frame acquisition time-first frame acquisition time, plays a current frame, and otherwise waits for the next event period.

In the playing process, the incremental frame is the most complex, and the frame comprises deletion, addition, attribute change and text node change. And preferentially matching the deleted nodes and removing the deleted nodes from the DOM tree. And then matching the newly added nodes, wherein the current node has father and brother nodes and is directly inserted into the DOM tree, otherwise, temporarily storing the waiting queue. And after the newly added node is matched, the matching waiting queue is obtained, and if the node has no father node, the node is ignored. And finally, matching the changed attribute with the changed text node.

In other embodiments of the present application, as shown in fig. 8, an apparatus for recording a webpage operation behavior of a user is further provided, including:

the data acquisition module 802 is configured to acquire DOM data triggering a backtracking page in response to a client monitoring an event that the user triggers the backtracking page;

the data conversion module 804 is used for carrying out serialization processing on the DOM data to obtain virtual DOM data;

a data uploading module 806, configured to determine whether the virtualized DOM data is a key frame;

if yes, uploading the key frame to a cloud server;

In other embodiments of the present application, as shown in fig. 9, an apparatus for recording a webpage operation behavior of a user is further provided, including:

a data receiving module 902, configured to receive virtualized DOM data sent by a client;

a data storage module 904, configured to preprocess the virtualized DOM data, and temporarily store the preprocessed data in an OSS; and storing the key information in the virtualized DOM data into a database, and establishing an index.

The functions or operation steps implemented by the modules are similar to those of the above method, and are specifically referred to corresponding parts, which are not described in detail herein.

Fig. 10 is a schematic structural diagram of an apparatus for recording a user webpage operation behavior according to another embodiment of the present application. The data detection device 4000 includes a processor 41, and may further include an input device 42, an output device 43, and a memory 44. The input device 42, the output device 43, the memory 44, and the processor 41 are connected to each other via a bus.

The memory includes, but is not limited to, Random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (CD-ROM), which is used for storing instructions and data.

The input means are for inputting data and/or signals and the output means are for outputting data and/or signals. The output means and the input means may be separate devices or may be an integral device.

The processor may include one or more processors, for example, one or more Central Processing Units (CPUs), and in the case of one CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor may also include one or more special purpose processors, which may include GPUs, FPGAs, etc., for accelerated processing. The memory is used to store program codes and data of the network device. The processor is used for calling the program codes and data in the memory and executing the steps in the method embodiment. Specifically, reference may be made to the description in the method embodiment, which is not repeated herein.

It will be appreciated that fig. 10 only shows a simplified design of the motion recognition means. In practical applications, the motion recognition devices may also respectively include other necessary components, including but not limited to any number of input/output devices, processors, controllers, memories, etc., and all the motion recognition devices that can implement the embodiments of the present application are within the protection scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the division of the unit is only one logic function division, and the actual implementation may have another division manner, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not executed. The shown or discussed mutual coupling, direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some interfaces, and may be in an electrical, mechanical or other form.

Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on or transmitted over a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optics, Digital Subscriber Line (DSL)), or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a read-only memory (ROM), or a Random Access Memory (RAM), or a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, a magnetic disk, or an optical medium, such as a Digital Versatile Disk (DVD), or a semiconductor medium, such as a Solid State Disk (SSD).

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present application, and these modifications or substitutions should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for recording user webpage operation behaviors is applied to a client and is characterized by comprising the following steps:

serializing the DOM data to obtain virtualized DOM data;

judging whether the virtualized DOM data is a key frame;

if yes, uploading the key frame to a cloud server;

2. The method of claim 1, wherein a unique trace ID is generated and cached to the client after the client monitors an event that triggers a trace back page and successfully loads the first trace back page.

3. The method of claim 2, further comprising:

deserializing the traceable data to establish a virtual DOM tree;

4. The method of claim 3, further comprising, prior to said deserializing each frame of data:

the player of the client verifies the integrity of the traceable data;

decompressing the traceable data in response to a successful verification;

5. The method of claim 1, further comprising:

monitoring the DOM data by using a DOM change observer;

6. The method according to claim 1, characterized in that a message queue is used to send the virtualized DOM data to the cloud server;

when the data volume of the virtualized DOM data is larger than a threshold value, directly uploading the data to the cloud server;

7. A method for recording user webpage operation behaviors is applied to a cloud server side and is characterized by comprising the following steps:

receiving virtualized DOM data sent by a client;

8. An apparatus for recording operation behavior of a user web page, comprising:

if yes, uploading the key frame to a cloud server;

9. An electronic device comprising a memory having computer-executable instructions stored thereon and a processor that, when executing the computer-executable instructions on the memory, implements the method of claims 1-6.

10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of claims 1-6.