Data processing method, device and system

Abstract

The present application proposes a data processing method, device and system. The client running on the terminal responds to a page trigger event, obtains the data to be recorded for the trigger element of the page, and proposes to use the hardware resources of the client to implement integrity check and data completion processing on the data to be recorded. Therefore, the client can obtain the coding information of the trigger element based on the data to be recorded, and can retrieve the reference data corresponding to the coding information of the trigger element from the local storage space, so that the front end obtains the complete target recording data for the trigger element based on the comparison result between the reference data and the obtained data to be recorded, and then sends it to the back-end server. There is no need for back-end operation and maintenance personnel to perform data integrity check and supplementary processing, which improves data processing efficiency, improves data collection quality, and ensures the accuracy of data sent by the client to the server.

Description

Technical Field

[0001] The present application mainly relates to the field of Internet applications, and more specifically to a data processing method, device and system. Background Art

[0002] In the era of Internet big databases, data collection is usually carried out by data point embedding, based on which product analysis such as websites / applications is carried out to obtain the required analysis results. Therefore, the comprehensiveness of data collection directly affects the reliability and accuracy of the analysis results.

[0003] In actual applications, due to product upgrades, tracking errors, tracking program exceptions and other reasons, the data collected based on data tracking may be incomplete. This requires the back-end collection equipment to perform data analysis and complete the data points through corresponding data operations to supplement the integrity of the collected data. This workload is large and the integrity and reliability of the collected data cannot be guaranteed. Summary of the invention

[0004] In view of this, the present application provides a data processing method, which is applied to the client side, and the method includes:

[0005] In response to a page triggering event, obtaining data to be recorded for a triggering element of the page;

[0006] Obtaining encoding information of the trigger element for the page according to the data to be recorded of the trigger element;

[0007] Determine reference data corresponding to the coding information of the trigger element in the local storage space; wherein the reference data corresponding to the coding information of different elements in the page stored in the local storage space is obtained from a server;

[0008] According to the comparison result between the data to be recorded and the determined reference data, target recording data for the trigger element of the page is output.

[0009] Optionally, the method further includes:

[0010] Obtaining a page identifier of the loaded page, and sending the page identifier to a server;

[0011] receiving page encoding rule data associated with the page identifier fed back by the server, and storing the page encoding rule data in a local storage space; the page encoding rule data includes reference data corresponding to encoding information of different elements in the page;

[0012] The determining of reference data corresponding to the encoding information of the trigger element in the local storage space includes:

[0013] The reference data corresponding to the coding information of the trigger element of the page is obtained from the page coding rule data stored in the local storage space.

[0014] Optionally, obtaining the coding information of the trigger element for the page according to the data to be recorded of the trigger element includes:

[0015] Determining a trigger path of the trigger element in the data structure of the page according to the data to be recorded of the trigger element;

[0016] The trigger path is encoded according to a preset encoding method to obtain encoding information of the trigger element being triggered on the page.

[0017] Optionally, outputting target recording data for the trigger element of the page according to a comparison result between the data to be recorded and the determined reference data includes:

[0018] Performing integrity check on the data to be recorded based on the determined reference data;

[0019] If the data to be recorded is incomplete, the data to be recorded is updated using the reference data to obtain target recorded data for the trigger element of the page;

[0020] The target record data is sent to the server.

[0021] The present application also proposes a data processing method, which is applied to the server side, and the method includes:

[0022] Determine page encoding rule data of the client page; the page encoding rule data includes reference data corresponding to encoding information of different elements in the page;

[0023] According to the loading request of the client, the page encoding rule data corresponding to the loading page is sent to the client, so that the client stores the encoding information of different elements in the loading page contained in the page encoding rule data and the reference data corresponding to the encoding information in the local storage space;

[0024] Receiving target record data for the trigger element of the loading page sent by the client;

[0025] The target recording data is determined based on a comparison result between the reference data corresponding to the coding information of the trigger element and the data to be recorded acquired when the trigger element is triggered.

[0026] Optionally, the determining of page encoding rule data of the client page includes:

[0027] Mark the positions of elements at different positions in the data structure of any page of the client;

[0028] Encoding the position marks of different elements in the page to obtain encoding information capable of representing a triggering path for displaying the corresponding elements in the page;

[0029] Retrieving historical record information obtained by triggering different elements of the page;

[0030] Determine reference data of the corresponding element in the page according to the historical record information;

[0031] The encoding information corresponding to different elements of the page and the reference data constitute page encoding rule data of the page.

[0032] Optionally, the method further includes:

[0033] Obtaining a total number of data acquisitions for an element in the page that is counted within a preset time period; the total number of data acquisitions for the element is cumulatively updated each time the client obtains corresponding target record data;

[0034] According to the total number of data acquisition times and preset verification rules, it is determined whether the target recorded data obtained by triggering the corresponding element within the preset time period is valid.

[0035] The present application also proposes a data processing device, which is applied to a client side, and the device includes:

[0036] A data acquisition module, used for acquiring the data to be recorded for the triggering element of the page in response to the page triggering event;

[0037] A coding information obtaining module, used for obtaining coding information of the trigger element of the page according to the data to be recorded of the trigger element;

[0038] A reference data determination module, used to determine the reference data corresponding to the coding information of the trigger element in the local storage space; wherein the reference data corresponding to the coding information of different elements in the page stored in the local storage space is obtained from the server;

[0039] The target record data output module is used to output the target record data for the trigger element of the page according to the comparison result between the data to be recorded and the determined reference data.

[0040] The present application also proposes a data processing device, which is applied to a server side, and the device includes:

[0041] A page coding rule data determination module, used to determine page coding rule data of a client page; the page coding rule data includes reference data corresponding to coding information of different elements in the loaded page;

[0042] A page encoding rule data sending module is used to send the page encoding rule data corresponding to the loaded page to the client according to the loading request of the client, so that the client stores the encoding information of different elements in the loaded page contained in the page encoding rule data and the reference data corresponding to the encoding information in the local storage space;

[0043] A target record data receiving module, used for receiving target record data sent by the client for the trigger element of the loading page;

[0044] The target recording data is determined based on a comparison result between the reference data corresponding to the coding information of the trigger element and the data to be recorded acquired when the trigger element is triggered.

[0045] The present application also proposes a data processing system, which includes a terminal and a server, wherein:

[0046] The terminal is used to implement the data processing method executed by the client side;

[0047] The server is used to implement the data processing method executed by the server side.

[0048] It can be seen that the present application provides a data processing method, device and system. The client running on the terminal responds to the page trigger event, obtains the data to be recorded for the trigger element of the page, and proposes to use the hardware resources of the client to implement integrity check and data completion processing on the data to be recorded. Therefore, the client can obtain the coding information of the trigger element based on the data to be recorded, and can retrieve the reference data corresponding to the coding information of the trigger element from the local storage space, so that the front end can obtain the complete target recording data for the trigger element based on the comparison result between the reference data and the obtained data to be recorded, and then send it to the back-end server. There is no need for background operation and maintenance personnel to perform data integrity check and supplementary processing, which improves data processing efficiency, improves data collection quality, and ensures the accuracy of data sent by the client to the server. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0050] Figure 1 A schematic diagram of an optional example of the architecture of the data processing system proposed in this application;

[0051] Figure 2 A schematic diagram of an optional example of a computer device applicable to the data processing method proposed in the present application;

[0052] Figure 3 A schematic structural diagram of another optional example of a computer device applicable to the data processing method proposed in the present application;

[0053] Figure 4 A flowchart of an optional example of a data processing method performed by a client side proposed in this application;

[0054] Figure 5 A flowchart of another optional example of a data processing method executed by a client side proposed in this application;

[0055] Figure 6 A flowchart of an optional example of a data processing method performed by a server side proposed in this application;

[0056] Figure 7 A flowchart diagram of another optional example of the data processing method performed by the server side proposed in the present application;

[0057] Figure 8 In the data processing method implemented by the server side proposed in this application, a page encoding rule data example diagram

[0058] Fig. 9 A signaling flow diagram of another optional example of the data processing method proposed in this application;

[0059] Fig.10 A schematic diagram of click statistics of each element in any client page in the data processing method implemented by the server side proposed in this application;

[0060] Fig.11 A schematic diagram of the structure of an optional example of the data processing device proposed in this application;

[0061] Fig.12 A schematic structural diagram of another optional example of the data processing device proposed in this application;

[0062] Fig.13 A schematic structural diagram of another optional example of the data processing device proposed in this application;

[0063] Fig.14 This is a schematic structural diagram of yet another optional example of the data processing device proposed in the present application. DETAILED DESCRIPTION

[0064] Regarding the technical problem of incomplete collected data described in the background technology section, for example, in actual situations, the data collection service provided by a certain enterprise may have problems such as incomplete data attributes of about 22% and unavailable data locations of 11%. In this regard, the integrity of data collection can be ensured by enhancing the back-end collection service or increasing the construction of collection service monitoring; or by using the scheduled service tasks configured in the back-end to calculate and complete the data within a certain period; or by upgrading the logic of related collection programs (such as point-of-sale programs), combined with the data tags agreed upon by website developers, data comparison and collection can be achieved. However, these data processing methods require a large amount of computing, storage, and hardware resources, and targeted data checks are performed to complete the integrity of the data, which is time-consuming and labor-intensive.

[0065] In order to improve the above-mentioned problems, the present application proposes to load a data collection program (such as a JS program for implementing automatic marking, etc.) on the front end (i.e., the client side), and store the encoding rule data of the page running on the client (which may include the encoding information of different elements in the page, and the corresponding data of the element in the page, such as the various attribute values ​​of the element, etc.) in the local storage space. In this way, when a trigger operation is performed on any element in the page, a record data of the trigger operation is obtained based on the data collection program. The reference data of the trigger element can be queried from the local storage space, and the data to be recorded that is actually collected can be compared. In this way, if the data to be recorded has omissions or other incomplete problems, the reference data can be used to complete it, thereby ensuring the integrity of the output target record data for the trigger element.

[0066] It can be seen that this application writes the data completion work performed by the back-end into the local storage space of the front-end page in advance through coding rules, and performs data checking and data completion work through the client's hardware resources, thereby improving work efficiency and data collection quality, and thereby ensuring the accuracy of the target record data output by the client for the trigger element.

[0067] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0068] Reference Figure 1 , is a schematic diagram of an optional example of the architecture of the data processing system proposed in this application, the data processing system can be applied to application scenarios such as website data collection and analysis, application usage data collection and analysis, etc. Figure 1As shown, the data processing system may include: a terminal 11 and a server 12, wherein:

[0069] The terminal 11 may include but is not limited to smart phones, tablet computers, wearable devices, smart watches, augmented reality (AR) devices, virtual reality (VR) devices, vehicle-mounted devices, smart speakers, robots, smart medical devices, smart transportation equipment, desktop computers and other electronic devices. The terminal 11 can run a client to implement the data processing method proposed in this application. The client can be an application installed and run by the terminal 11 or logged in online, such as a browser, various social software, professional data analysis software, game software, enterprise office software, etc. This application does not elaborate on the application type of the client and its working principle. It can be seen that the terminal 11 can implement the data processing method described in the method embodiment of the client side below, and the implementation process of this embodiment is not described in detail here.

[0070] The server 12 may be a service device that supports the implementation of client functions, and may be a server, such as an independent physical server, a server cluster consisting of multiple physical servers, or a cloud server that can implement cloud computing, etc. The server 12 may establish a communication connection with the terminal 11 through a communication method such as a wired network or a wireless network, so as to implement data interaction between the server 12 and the client running on the terminal 11, and meet application requirements. The implementation process is not described in detail in this application.

[0071] In the embodiment of the present application, in order to realize the analysis of client functions, etc., it is necessary to collect data based on the trigger events of the client by the user. In order to ensure the comprehensiveness and accuracy of the collected data and improve the data processing efficiency, the server can execute the data processing method described in the method embodiment of the server side below. The implementation process of this embodiment will not be described in detail here.

[0072] It should be noted that the data processing system proposed in this application includes but is not limited to Figure 1 The system structure of the present embodiment shown in the figure may also include monitoring equipment, database and other equipment according to different business processing requirements, which are not listed one by one in this application.

[0073] In some embodiments, reference Figure 2 The structure diagram of an optional example of a computer device applicable to the data processing method proposed in the present application is shown in FIG. The computer device can be any of the terminals listed above or a server. Taking the computer device as a terminal as an example, the hardware structure of the computer device is described. Figure 2 As shown, the computer device may include a communication interface 21, a memory 22 and a processor 23, wherein:

[0074] The communication interface 21 may include an interface of a communication module used for the computer device to communicate data with other devices. The communication module may include a WIFI module, a 5G / 6G (fifth-generation mobile communication network / sixth-generation mobile communication network) module, a GPRS module, a near-field communication module, and other communication modules that support wireless communication / wired communication. The computer device can choose to configure one or more communication modules according to communication requirements, and each communication module can be configured with one or more communication interfaces that support the communication method.

[0075] In addition, the communication interface 21 may also include a signal transmission interface for realizing data interaction between components inside the computer device, such as a USB interface, a serial / parallel port, a multimedia interface, etc. The type and number of the communication interface 21 configured to realize internal data transmission can be determined according to the device type and function of the computer device, and the embodiments of the present application do not list them one by one.

[0076] Based on this, in an embodiment of the present application, during the process of terminal 11 running the client to load any page, the page data of the page sent by the server can be received through the communication interface 21. During the process of the user triggering the loaded and outputted page, the operation data can be detected and sent to the processor through the corresponding communication interface; the processor can also implement various business functions supported by the terminal 11 based on the received data. The present application does not elaborate on the business functions that the terminal 11 can implement and their implementation process. It can be understood that in the process of implementing different business functions, the required devices and their communication connection methods in the terminal 11 are often different, and the present application does not give detailed examples one by one.

[0077] Similarly, when the computer device is a server 12, the server 12 can realize data communication with each terminal 11 through a communication interface that supports wireless / wired communication, and in the process of the server 12 executing the data processing method, the processor of the server 12 can interact with the memory for data to implement the data processing method executed on the server side. The implementation process will not be described in detail in the embodiment of this application.

[0078] Based on the above analysis, when the computer device is a terminal 11, the memory 22 can be used to store an application program that supports the operation of the client, and a first program that implements the data processing method executed on the client side; the processor 23 can be used to load and execute the first program to implement the data processing method executed on the client side proposed in this application; when the computer device is a server 12, its memory 22 can be used to store program codes that support the operation of the client, and a second program that implements the data processing method executed on the server side, and the processor 23 in the server 12 can be used to load and execute the second program to implement the data processing method executed on the server side. The implementation process of the data processing method implemented by the client side and the server side can refer to but is not limited to the description of the corresponding side method embodiment below, and this embodiment will not be described in detail here.

[0079] In the embodiment of the present application, the memory 22 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device. The processor 23 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices. In different terminals 11 and servers 12, the device type and quantity of the memory 22 and the processor 23 may be determined according to the circumstances, and the embodiment of the present application does not limit it.

[0080] It should be understood that Figure 2 The structure of the computer device shown does not constitute a limitation on the computer device in the embodiment of the present application. In practical applications, the computer device may include Figure 2 More or fewer components as shown, or combining certain components, such as in the case where the computer device is a terminal 11, Figure 3 As shown, the computer device may also include: at least one input component such as a touch sensing unit for sensing touch events on the touch display panel, a keyboard, a mouse, a camera, a microphone, etc.; at least one output component such as a display, a speaker, a vibration mechanism, a lamp, etc.; an antenna; a sensor module; a power module, etc. Figure 3 The hardware components listed are not shown. The hardware structure can be determined according to the terminal type and its functional requirements, and this application does not list them one by one here.

[0081] Reference Figure 4, is a flowchart of an optional example of the data processing method proposed in this application. The method can be applied to the terminals listed above and can be executed by the client running on the terminal. This application does not limit the application type of the client. Figure 4 As shown, the data processing method may include:

[0082] Step S41, in response to a page triggering event, obtaining data to be recorded for a triggering element of the page;

[0083] In combination with the above description of the technical solution of the present application, in order to realize client analysis, etc., in the application scenario where data is collected during the client usage process, a tracking point method can be used to realize data collection, that is, a corresponding tracking point program (that is, a data collection program, such as a JS automatic tracking point program, etc.) is configured for the client. In this way, during the process of the terminal running the client, the user can trigger any page of the client according to the operation requirements and generate a corresponding page trigger event.

[0084] It should be noted that this application does not restrict the implementation method of triggering the page, such as using input devices such as a mouse and keyboard to select touch operations; users using voice control; clicking and touching the touch screen of the terminal, etc., depending on the situation. Moreover, the triggered page can be an application page of different levels of the client, which can be determined based on the user's access processing process to the client. Since the triggering operation of different pages and the implementation process of obtaining the complete record data generated by this triggering operation are similar, this application does not give detailed examples one by one.

[0085] Following the above analysis, the client can start a data collection program pre-configured for the client in response to the obtained page trigger event, and collect data for the trigger element in the currently triggered page, to obtain data directly collected based on the data collection program. As analyzed above, the data directly collected here may be incomplete, and this application will not directly generate a record data for the trigger element from the collected data. It will temporarily use it as data to be recorded, and perform integrity detection and completion according to the method described below.

[0086] Step S42, obtaining coding information of the trigger element for the page according to the data to be recorded of the trigger element;

[0087] In order to reduce the data completion workload of the back-end server and ensure the integrity of the recorded data of any page trigger element obtained by the client, the client can first perform an integrity check on the data to be recorded for the trigger element after obtaining the data to be recorded for the trigger element. To this end, the client needs to first determine the reference data used for the integrity check of the data to be recorded. As can be seen from the above description of the technical solution of the present application, the back-end server pre-stores the encoding information of each element contained in the triggered page and the attributes of the corresponding element in the page in the local storage space of the client according to a preset data format. Therefore, after the client determines the trigger element that is triggered this time, it can first determine the encoding information of the trigger element.

[0088] Among them, since the encoding information of the trigger element in the page can represent the query path of the trigger element in the client's data structure, this application can determine the encoding information of the trigger element based on the element name, URL and other element identifiers contained in the information to be recorded of the trigger element. There is no restriction on the method and content of obtaining the encoding information, which can be determined according to the circumstances.

[0089] Step S43, determining reference data corresponding to the coding information of the trigger element in the local storage space;

[0090] As analyzed above, for the client running on the terminal, the present application stores in its local storage space the coding information corresponding to the elements in each page of the client, as well as reference data consisting of various attributes of the element in the page to which it belongs. These reference data can be determined based on information such as the historical access data of the page and the historical completion data (such as frequently lost attributes, etc.). Normally, the reference data corresponding to the coding information of different elements in the client page is determined by the server and sent to the client's local storage space for storage. The present application does not limit the method for obtaining data of the element in the page and its content.

[0091] Based on this, the coding information of the trigger element determined by the user for triggering the page this time can be compared with the coding information of each element stored in the local storage space of the page to determine whether the coding information of the trigger element is stored in the local storage space. If so, the data corresponding to the coding information in the local storage space is determined as the reference data of the trigger element in the page, which may include the complete data of the trigger element in the client page, or at least include data that is often lost during data collection for the trigger element.

[0092] Step S44: outputting target recording data for the triggering element of the page according to the comparison result between the data to be recorded and the determined reference data.

[0093] Following the above description of the reference data of each element in the client page stored in the local storage space, it can represent the complete data that should be collected when the element is used as a trigger element. Therefore, after the reference data of the trigger element is determined from the local storage space, it can be compared with the directly collected data to be recorded. If the data of the two are consistent, it can be determined that the data collection program is called to collect data for the trigger element, and the obtained data to be recorded is complete and no further completion processing is required; conversely, if the two are inconsistent, it means that the directly collected data to be recorded is incomplete. The reference data corresponding to the determined trigger element can be used to complete the data to be recorded to obtain the complete target record data of the trigger element. The completion processing method of the embodiment of this application will not be described in detail here.

[0094] It can be seen that in the embodiment of the present application, based on the above comparison results, it can be determined whether the data to be recorded needs to be completed, ensuring that the target record data for the trigger element of the page finally obtained by the client is complete, and there is no need for the back-end server to perform data completion processing.

[0095] In summary, in the embodiments of the present application, the client running on the terminal responds to the page trigger event, obtains the data to be recorded for the trigger element of the page, and proposes to use the hardware resources of the client to implement integrity check and data completion processing on the data to be recorded. Therefore, the client can obtain the coding information of the trigger element based on the data to be recorded, and can retrieve the reference data corresponding to the coding information of the trigger element from the local storage space, so that the front end can obtain the complete target recording data for the trigger element based on the comparison result between the reference data and the obtained data to be recorded, and then send it to the back-end server. There is no need for background operation and maintenance personnel to perform data integrity check and supplementary processing, which improves data processing efficiency, improves data collection quality, and ensures the accuracy of data sent by the client to the server.

[0096] Reference Figure 5 , which is a flowchart of another optional example of the data processing method proposed in this application, which can be an optional detailed implementation method of the data processing method executed by the client side, such as Figure 5 As shown, the refinement implementation method may include:

[0097] Step S51, obtaining the page identifier of the loaded page, and sending the page identifier to the server;

[0098] Step S52, receiving the page encoding rule data associated with the page identifier fed back by the server, and storing the page encoding rule data in the local storage space;

[0099] In the embodiment of the present application, the page coding rule data may include reference data corresponding to the coding information of each element in the corresponding page. The present application does not limit the content and output form thereof, which may be determined as the case may be. In the process of the server obtaining the page coding rule data corresponding to different pages, the position of different elements in the page in the entire data structure may be determined based on the data structure of the corresponding page (such as the Document Object Model (DOM), etc.), and each element may be encoded accordingly to obtain the coding information of the corresponding element in the page. At the same time, the point data such as the attribute value of the element in the corresponding page may be determined based on the historical record data of the client page (such as the record data obtained by the data acquisition program when any user uses the page), and the page coding rule data may be obtained after structured processing, and the page coding rule data may be associated with the page identifier of the page and stored.

[0100] In this way, when the terminal starts the client running process, when the client loads any page, the page identifier of the page can be sent to the server, and the server queries the page encoding rule data associated with the page identifier from the pre-constructed different page encoding rule data, or constructs the page encoding rule data for the page based on the data structure corresponding to the page identifier, such as constructing it online as described above, or retrieving the encoding information and attribute data corresponding to each element contained in the page to form the corresponding page encoding rule data, etc. After that, the server can send the page encoding rule data to the client.

[0101] The page encoding rule data in the server can be updated in real time or periodically according to but not limited to the construction method described above, and the updated page encoding rule data is sent to the next user-triggered client page of the corresponding page. This application does not limit the implementation method of the server to construct and update the page encoding rule data, and the content contained in the page encoding rule data, which can be determined according to the circumstances.

[0102] After the client receives the page encoding rule data fed back by the server according to the above method, it can store the page encoding rule data or its contents in the local storage space of the page according to its own data storage format requirements (such as a format that can be recognized by the client later, etc.), such as JSON format, for subsequent calls during access to the page to implement integrity checks on the data collected from the page elements. This application does not limit the implementation method of how the local storage space of the page stores the received page encoding rule data.

[0103] Step S53, in response to the page triggering event, obtaining the data to be recorded for the triggering element of the page;

[0104] Step S54, determining the trigger path of the trigger element in the data structure of the page according to the data to be recorded of the trigger element;

[0105] Step S55, encoding the trigger path according to a preset encoding method to obtain encoding information of the trigger element being triggered on the page;

[0106] After the local storage space of any page loaded and run by the client stores the corresponding page encoding rule data, the user accesses the page content and triggers any element it contains. The client can respond to the page trigger event generated thereby and obtain the data to be recorded of the trigger element, such as the address of the trigger element in the page, attribute information and other element identifiers. This application does not impose any restrictions on the content of the data to be recorded.

[0107] Among them, the client pages usually include pages with the same level relationship (for example, you can enter page A and page B from the client home page, and the relationship between page A and page B is a same level relationship), and multiple pages with cascading relationships (that is, entering page B through page A, the relationship between page A and page B can be recorded as a cascading relationship, if you continue to enter page C from page B, the relationship between page A and page C can also be recorded as a cascading relationship). Each page usually contains multiple elements, and the business functions corresponding to different elements and / or the data content contained may be different.

[0108] Based on this, when any page is output on the client and a trigger operation is performed on any element displayed on the page, the trigger path of the entire process from the client's home page to the trigger element can be recorded. The trigger path can be composed of the page element identifier called in the process. This application does not impose any restrictions on the method of obtaining the trigger path of the trigger element in the data structure of the page and its representation, which can be determined according to the circumstances.

[0109] Afterwards, the present application encodes the trigger path of the determined trigger element in the data structure of the page according to a preset encoding method, and obtains encoding information that can characterize the trigger path of the trigger element being triggered on the page. The present application does not elaborate on the content of the preset encoding method and its encoding implementation method. Exemplarily, the position of the elements in the page in its data structure can be marked, and the trigger path of the trigger element can be represented by the position mark of each element, and the encoding information of the trigger element can even be constituted by the position mark. The present application does not elaborate on the implementation method of the above steps S54 and S55.

[0110] Step S56, obtaining reference data corresponding to the coding information of the trigger element of the page from the page coding rule data stored in the local storage space;

[0111] Combined with the above description of page encoding rule data, after the client determines the encoding information of the trigger element, it can query whether there is encoding information of the trigger element from the page encoding rule data of the page stored in the local storage space, and determine the data corresponding to the queried encoding information of the trigger element as reference data to implement the basis for data collection integrity check of the trigger element.

[0112] Step S57, performing integrity check on the data to be recorded based on the determined reference data;

[0113] Step S58, if the data to be recorded is incomplete, the data to be recorded is updated using the reference data to obtain target recording data for the trigger element of the page;

[0114] Step S59, sending the target record data to the server.

[0115] Continuing the above description of reference data, step S57 may include comparing the determined reference data with the acquired data to be recorded. If the two have the same content or consistent semantics, the data to be recorded may be considered complete and sent to the server as target record data. Otherwise, it may be considered that the data to be recorded is missing (such as the data to be recorded includes Null, Undefined, etc., or the contents of the two are different), and the data to be recorded may be supplemented with reference to the reference data, and the complete target record data may be obtained and sent to the server.

[0116] Among them, for any element in the page, the corresponding complete target record data can be obtained according to the method described above, and then the statistical value of the triggering number of the corresponding element (that is, the number of data acquisition times) is increased by 1, that is, the data acquisition number of the triggering element is updated and sent to the server, so that the server can analyze whether the data collection of the corresponding triggering element is effective within the preset time. The implementation process can refer to the description content of the corresponding part of the data processing method embodiment described on the server side below, and this embodiment will not be described in detail here.

[0117] In summary, in the present embodiment, during the process of loading and running a page, the coding information representing each element in the page and the page coding rule data representing the attribute information of its point data can be obtained in advance, and stored in the local storage space of the client page. In this way, the client user triggers any element in the page, and performs data collection for this trigger operation process based on the data collection program. After obtaining the data to be recorded, the corresponding reference data stored in the local storage space is queried based on the coding information of the trigger element. The reference data can be used at the front end to perform integrity detection on the collected data to be recorded without sending it to the back-end server for inspection and completion by the operation and maintenance personnel, thereby improving processing efficiency. Moreover, the client can use the reference data to directly complete the incomplete data to be recorded, thereby ensuring the integrity of the target recorded data sent to the server and improving the quality and accuracy of data collection.

[0118] Reference Figure 6 , which is a flowchart of another optional example of the data processing method proposed in the present application. In this embodiment, the data processing method proposed in the present application can be described from the server side. That is, the data processing method described in this embodiment can be executed by the server, such as Figure 6 As shown, the method may include:

[0119] Step S61, determining page encoding rule data of the client page;

[0120] Combined with the description of the corresponding parts of the above embodiments, the page encoding rule data for any page may include the encoding information of each element in the page and its corresponding reference data, etc. In actual applications, the server may construct the page encoding rule data of the page after publishing the page contained in the client according to but not limited to the method described above; it may also construct the page encoding rule data based on the historical record data of each page of the client and the data structure of the page elements after different users have used the client for a period of time; or it may construct the page rule data required by the client during the process of starting and running the client at any terminal, etc. The present application does not limit the method and timing of constructing the page encoding rule number, which may be determined according to the situation.

[0121] Step S62, according to the loading request of the client, the page encoding rule data corresponding to the loading page is sent to the client;

[0122] The embodiment of the present application is explained by taking the page encoding rule data of the client page pre-built by the server as an example. In this way, when the terminal loads and runs the client, a loading request for the client can be sent to the server. In this way, the client can retrieve the page encoding rule data corresponding to the page identifier based on the page identifier of the client loading page carried by the loading request, and feed it back to the client, so that the client can store the encoding information of different elements in the loading page contained in the page encoding rule data, and the reference data corresponding to the encoding information in the local storage space. The data processing method executed on the client side can refer to the description of the corresponding part of the above embodiment, and this embodiment will not be repeated here.

[0123] Step S63: receiving target record data for the trigger element of the loading page sent by the client.

[0124] It can be seen from the data processing method executed on the client side that the target recorded data can be determined based on the comparison result between the reference data corresponding to the coding information of the trigger element and the data to be recorded obtained when the trigger element is triggered. The implementation process of this embodiment will not be described in detail here.

[0125] It can be seen that in the process of the terminal running the client loading page, the server can send the page encoding rule data of the loading page to the client and store it in the local storage space of the client page. In this way, after the user triggers the loading page and obtains the data to be recorded of the trigger element, the integrity of the data to be recorded can be checked based on the reference data of the trigger element stored in the local storage space. After obtaining the complete target record data of the trigger element in the loading page, the target record data is sent to the server, ensuring that the target record data for the client page elements received by the server is complete and accurate, and there is no need for back-end operation and maintenance personnel to perform integrity checks and completion processing on it, which improves data processing efficiency and ensures data collection quality and accuracy.

[0126] Reference Figure 7 , is a flowchart of another optional example of the data processing method proposed in this application, which can be an optional detailed implementation method of the data processing method executed by the server side, such as Figure 7 As shown, the refinement implementation method may include:

[0127] Step S71, marking the positions of elements at different positions in the data structure of any page of the client;

[0128] The embodiment of the present application describes a method for obtaining page encoding rule data of a client page, but is not limited to the implementation method described in the present embodiment. The present application uses this as an example for illustration. After the server obtains the data structure of any page of the client, such as the page DOM, it can mark the positions of each element in the page (i.e., each component of the page content) according to the tree structure based on the data structure. It can use letters, numbers, or identifiers to determine the position marks of elements located at different positions, such as position marks such as d1, d2, and d3. The present application does not limit the content of the position mark and its acquisition method, which can be determined according to the situation.

[0129] Step S72, encoding the position marks of different elements in the page to obtain encoding information that can represent the triggering path of the corresponding element displayed in the page;

[0130] After determining the position mark of each element in any page of the client, the encoding information of the element can be sequentially composed according to the position marks involved in the trigger path from the vertex position to the position of the corresponding element in the page data structure, such as d3-d2-d2-d16-d2-d1-d3. Of course, the position marks composed in sequence can be further encoded to obtain the encoding information of the corresponding element. It can be seen that the encoding information of the element in the page obtained in this embodiment can represent the trigger path of the element under the page data structure, but is not limited to the encoding implementation method described in this embodiment.

[0131] Step S73, retrieving the historical record information obtained by triggering different elements of the page;

[0132] Step S74, determining reference data of the corresponding element in the page according to the historical record information;

[0133] In order to obtain the complete data of the page elements, the back-end server can obtain the point data used to collect the attribute data of the corresponding element based on the historical record information of the client page, and define the point data as the tag attribute latag value of the element. This application does not give detailed examples of the content of the element tag attributes, which can be determined based on the page type and its page content, the business types supported by the client, etc.

[0134] Among them, the historical record information may include the triggering operations on the elements in each page of the client during the use of the client by each user in the past period of time, based on the complete record data obtained by the data collection program, and may also include attribute data that is often lost during the data collection process as needed. This application does not limit the content contained in the historical record information.

[0135] For example, Figure 8As shown in the example diagram of page encoding rule data, for any page of the client, the encoding information of different elements in the page and the tag attribute latag value of the element in the page (i.e., the reference data described above) can be determined according to the method described above, wherein the page identifier of each page can be represented by the URL or unique identifier of the page, such as Figure 8 The page shown - _url (page_uniform resource locator) corresponds to the page identifier duct / 101678... The page element with the coding information of d3-d2-d2-d16-d2-d1-d3 can have the reference data of: latag_pc_detail_bottom_fixed_orderimmediately_1014386; the element with the element coding information of d3-d2-d2-d16-d6-d1-d1 can have the reference data of: latag_savior_Y7000P_customized_quotation_price_how much_xx mall, etc. The embodiments of this application will not give examples one by one here.

[0136] Step S75, the coding information and reference data corresponding to different elements of the page constitute the page coding rule data of the page.

[0137] According to the method described above, after obtaining the coding information and reference data of the page elements, the embodiment of the present application can perform structured combination processing on them to obtain the page coding rule data of the page. It should be noted that in order to facilitate the server to accurately send the page coding rule data of the required page to the client, the page coding rule data not only includes the coding information and reference data of the page elements, such as Figure 8 As shown, it can also include the page identifier of the corresponding page, and even the total number of data acquisition times for different page elements (i.e., the page element click statistics, which can be continuously updated with the number of visits to the page elements), etc. The content of the page encoding rule data can be determined based on application requirements.

[0138] In some other embodiments, the present application can determine the encoding information and reference data corresponding to each element contained in different pages according to the processing method described above, and thereby constitute the encoding rule data of each page element of the client, that is, constitute the page encoding set of the client. Thereafter, when the client runs to load the page, the server can extract the element encoding information and reference information corresponding to the page identifier of the page based on the page identifier of the page, and constitute the page encoding rule data of the page.

[0139] Afterwards, the server can send the page encoding rule data obtained in the manner described above to the client, and store it in the local storage space of the page to implement integrity detection of the data to be recorded for different trigger elements in the page, and obtain the target recording data of the trigger element. The implementation process can refer to the description of the corresponding part of the method implementation example executed on the client side above, and this embodiment will not be described in detail here.

[0140] Reference Fig. 9 , which is a signaling flow diagram of another optional example of the data processing method proposed in this application. This embodiment can be an optional detailed implementation method of the data processing method proposed in the above embodiments, such as Fig. 9 As shown, the refinement implementation method may include:

[0141] Step S91, the client sends a loading request to the server in response to the trigger operation;

[0142] Step S92, the server responds to the loading request and determines page encoding rule data corresponding to the loaded page;

[0143] Step S93, the server sends the page encoding rule data to the client;

[0144] Regarding the implementation method of the server obtaining the page encoding rule data corresponding to the page loaded by the client, please refer to the description of the corresponding part of the context embodiment, which will not be described in detail in this embodiment.

[0145] Step S94, the client stores the encoding information of different elements in the loaded page contained in the page encoding rule data and the reference data corresponding to the encoding information in the local storage space;

[0146] After receiving the page rule data sent by the server, the client can convert it into a recognizable preset format for storage, such as storing it in the local storage space of the page (i.e. LocalStorage) in JSON format. Taking the page encoding rule data described above as an example, the encoding information and reference data of each element in the page stored in the local storage space of the client page can be: [

[0148] {"d3-d2-d2-d16-d2-d1-d3":"latag_pc_detail_bottom_fixed_orderimmediately_1014386"

[0149] }

[0150] {“d3-d2-d2-d16-d6-d1-d1”:“latag_Savior_Y7000P_Customized_Quote_Price_How much_xx Mall”

[0151] …

[0152] } ]

[0154] Step S95, the client obtains the data to be recorded for the triggering element of the page in response to the page triggering event;

[0155] Step S96, the client obtains the coding information of the trigger element for the page according to the data to be recorded of the trigger element;

[0156] Step S97, the client determines reference data corresponding to the coding information of the trigger element in the local storage space;

[0157] Step S98, the client determines the target recording data for the trigger element of the page according to the comparison result between the data to be recorded and the determined reference data;

[0158] Step S99, the client sends the target record data of the trigger element to the server;

[0159] Regarding the implementation process of step S95 to step S99, reference may be made to the description of the corresponding parts of the above embodiment, which will not be elaborated in this embodiment.

[0160] In actual applications, a page trigger rule checker can be configured in the client. In this way, when the user performs a click trigger operation on the client page, such as when a click event occurs on the client page, the data collection program can be called to collect data. After that, the document.getElementsByTagName() method in the DOM of the client page, that is, the method of obtaining element data by tag name, can be used to obtain the page collection, and then the page data encoding data in the local storage space of the page (that is, the LocalStorage collection) is looped through to determine the reference data corresponding to the encoding information of each embedded element in the page tag, such as the tag attribute latag value, and compared with the data to be recorded of the corresponding trigger element obtained based on the data collection program to determine whether the collected data to be recorded is complete. If it is incomplete, the collected data can be directly completed on the front-end client side to correct the omissions and irregular formats of the collected data to be recorded, so as to ensure the integrity and accuracy of the obtained target recorded data.

[0161] Exemplarily, this embodiment can determine the coding information of the trigger element of the client page according to the method described above, such as the coding ID value of d3-d2-d2-d16-d2-d1-d3, input it into the corresponding inspection program, traverse the coding ID of each buried point element of the page in the local storage space for comparison, and implement the integrity check of the data to be recorded collected by calling the JS program. In this comparison process, in order to realize automatic comparison based on the inspection program, the coding ID value can be converted into recognizable coding information, and its corresponding tag attribute latag value is the same as the collected data to be recorded. The coding ID value listed above is used as an example to illustrate that the page coding rule data is queried to obtain node[3].childNode[2].childNode[2].childNode

[16] .childNode[2].childNode[1].childNode[1].latag, and then according to the integrity detection logic, it is judged whether it is complete with the collected data to be recorded, that is, whether the data to be recorded needs to be completed.

[0162] Among them, the integrity detection logic may include: if the two compared data are the same, it can be determined that the data to be recorded is complete; if the comparison determines that the data to be recorded has abnormal problems such as Null or Undefined, or the two compared data are not the same, the latag data in the data to be recorded can be completed by using the retrieved tag attribute latag value, and then the total number of acquisitions of the corresponding element is increased by 1 to obtain the new total number of acquisitions of the element.

[0163] In some other embodiments, when the client determines that the data to be recorded for a trigger element is incomplete, it may also update the data collection program for the trigger element based on the data that needs to be completed, or complete the collected data to be recorded when the trigger element is accessed next time, to ensure the integrity and accuracy of the data subsequently collected for the trigger element.

[0164] Step S910, the server obtains the total number of data acquisitions for the element in the triggered page within a preset time period;

[0165] Step S911, the server determines whether the target record data obtained by triggering the corresponding element within a preset time period is valid according to the total number of data acquisition times and preset verification rules.

[0166] Based on the description of the above embodiments, after the server receives the target record data sent by the client running on any terminal, as well as the total number of data acquisition times for the corresponding trigger element (i.e., any buried point element triggered by the operation) counted within the current preset time length, the server can determine whether the target record data of each buried point element acquired within the preset time length is valid, and determine the effective buried point inspection results for each buried point element within the preset time length. This application does not impose any restrictions on the effective detection implementation method.

[0167] Among them, the total number of data acquisitions for any element counted within a preset time period can be obtained after the client obtains the target record data and updates the data acquisition times for the corresponding trigger element, or the client obtains the target record data and sends the target record data and the data acquisition times update instruction for the corresponding trigger element to the server, so that the server responds to the data acquisition times update instruction, updates the data acquisition times for the trigger element, and obtains a new total number of data acquisitions. It can be understood that the total number of data acquisitions for the same element in the client page refers to the number of data acquisitions obtained based on the trigger operation of each user on the element of the client page according to the method described above.

[0168] In some embodiments, in the process of checking the validity of the target record data of any element, the preset verification rules may include but are not limited to: the server determines whether the total number of data acquisitions is less than the number threshold. If so, it can be considered that the target record data acquired for the element within the preset time period is invalid, and the subsequent processing will no longer be based on the target record data to meet other business processing needs, or a prompt message indicating that the data collection for the element is invalid can be sent to the terminal of the operation and maintenance personnel to remind the operation and maintenance personnel to adjust the data collection program in time to ensure that the valid record data of the element can be obtained within the next preset time period, etc. The present application does not limit the subsequent processing performed after determining that the target record data of any element within the preset time period is invalid, which can be determined according to the circumstances.

[0169] If it is determined that the total number of data acquisitions of the trigger element within the preset time is equal to or greater than the number threshold, the corresponding target record data can be directly determined to be valid; the total number of data acquisitions of the trigger element within the previous preset time can be further obtained, and based on the comparison result of the total number of data acquisitions obtained in two adjacent times, the predicted probability that the target record data of the trigger element within the current preset time is valid is determined, and then based on the predicted probability, the validity verification result of the target record data acquired by the trigger element within the preset time is obtained. For example, the obtained predicted probability can be compared with different preset probability thresholds, and the corresponding validity verification result can be obtained according to the validity verification rule corresponding to the probability threshold reached by the predicted probability, etc. This application does not describe this implementation process in detail.

[0170] It should be noted that this application does not impose any restrictions on the above-mentioned preset duration, number thresholds and respective values ​​of each probability threshold, which can be determined according to different business processing requirements.

[0171] For example, refer to Fig.10 The schematic diagram of click statistics of each element in a client page is shown. For the client page with page identifier / product / 1016780.html, according to the method described above, the target record data (i.e., buried point data) determined by the clicks on the elements in the page within 24 hours is obtained, the number of clicks on the element within the 24 hours is updated, and the click statistics of the element within 24 hours (such as the total number of data acquisition) are obtained. If the click statistics is 0 within 24 hours, it can be considered that the buried point data of the element sent by the client is invalid; if the click statistics is not 0 within 24 hours, the buried point data of the element received within the current 24 hours can be statistically compared with the buried point data of the element received within the previous 24 hours to determine whether the buried point data of the element received within the current 24 hours is valid.

[0172] Reference Fig.11 , is a schematic diagram of an optional example of a data processing device proposed in the present application, which can be described from the client side, such as Fig.11 As shown, the method may include:

[0173] The data acquisition module 111 is used to acquire the data to be recorded for the triggering element of the page in response to the page triggering event;

[0174] The coding information obtaining module 112 is used to obtain the coding information of the trigger element of the page according to the data to be recorded of the trigger element;

[0175] The reference data determination module 113 is used to determine the reference data corresponding to the coding information of the trigger element in the local storage space; wherein the reference data corresponding to the coding information of different elements in the page stored in the local storage space is obtained from the server;

[0176] The target record data output module 114 is used to output the target record data for the trigger element of the page according to the comparison result between the data to be recorded and the determined reference data.

[0177] In some other embodiments, Fig.12 As shown, the above data processing device may further include:

[0178] The page identifier sending module 115 is used to obtain the page identifier of the loaded page and send the page identifier to the server;

[0179] The page coding rule data storage module 116 is used to receive the page coding rule data associated with the page identifier fed back by the server, and store the page coding rule data in a local storage space; the page coding rule data includes reference data corresponding to the coding information of different elements in the page;

[0180] Based on this, Fig.12 As shown, the reference data determination module 113 may include:

[0181] The reference data acquisition unit 1131 is used to acquire reference data corresponding to the encoding information of the trigger element of the page from the page encoding rule data stored in the local storage space.

[0182] In some other embodiments, Fig.12 As shown, the above-mentioned coding information obtaining module 112 may include:

[0183] A trigger path determining unit 1121, configured to determine a trigger path of the trigger element in the data structure of the page according to the data to be recorded of the trigger element;

[0184] The encoding unit 1122 is used to encode the trigger path according to a preset encoding method to obtain encoding information of the trigger element being triggered on the page.

[0185] Based on the description of the above embodiments, Fig.12 As shown, the target record data output module 114 may include:

[0186] An integrity detection unit 1141 is used to perform integrity detection on the data to be recorded based on the determined reference data;

[0187] a target record data determination unit 1142, configured to update the data to be recorded using the reference data if the data to be recorded is incomplete, so as to obtain target record data for the trigger element of the page;

[0188] The target record data sending unit 1143 is used to send the target record data to the server.

[0189] Reference Fig.13 , which is a structural diagram of another optional example of the data processing device proposed in this application. This embodiment can be described from the server side, such as Fig.13 As shown, the device may include:

[0190] The page coding rule data determination module 131 is used to determine the page coding rule data of the client page; the page coding rule data includes reference data corresponding to the coding information of different elements in the loaded page;

[0191] The page encoding rule data sending module 132 is used to send the page encoding rule data corresponding to the loaded page to the client according to the loading request of the client, so that the client stores the encoding information of different elements in the loaded page contained in the page encoding rule data and the reference data corresponding to the encoding information in the local storage space;

[0192] The target record data receiving module 133 is used to receive the target record data for the trigger element of the loading page sent by the client.

[0193] The target recording data is determined based on a comparison result between the reference data corresponding to the coding information of the trigger element and the data to be recorded acquired when the trigger element is triggered.

[0194] In some other embodiments, Fig.14 As shown, the page encoding rule data determination module 131 may include:

[0195] The position marking unit 1311 is used to mark the positions of elements at different positions in the data structure of any page of the client;

[0196] The coding information obtaining unit 1312 is used to encode the position marks of different elements in the page to obtain coding information that can represent a triggering path for displaying the corresponding element in the page;

[0197] A history record information retrieving unit 1313, used to retrieve the history record information obtained by triggering different elements of the page;

[0198] A reference data determining unit 1314, configured to determine reference data of a corresponding element in the page according to the historical record information;

[0199] The page encoding rule data forming unit 1315 is used to form the page encoding rule data of the page using the encoding information corresponding to different elements of the page and the reference data.

[0200] Based on the description of the above embodiments, the above data processing device may further include:

[0201] The data acquisition total times acquisition module is used to obtain the total number of data acquisitions for the elements in the page within a preset time period; the total number of data acquisitions for the elements is cumulatively updated each time the client obtains the corresponding target record data;

[0202] The data validity verification module is used to determine whether the target record data obtained by triggering the corresponding element within the preset time period is valid based on the total number of data acquisition times and preset verification rules.

[0203] Among them, regarding the content of the preset verification rules and their configuration methods, reference can be made to the description of the corresponding part of the above method embodiment, which will not be described in detail in this embodiment.

[0204] It should be noted that the various modules, units, etc. in the above-mentioned device embodiments can be stored in the memory as program modules, and the processor executes the above-mentioned program modules stored in the memory to implement the corresponding functions. For the functions implemented by each program module and its combination, as well as the technical effects achieved, please refer to the description of the corresponding parts of the above-mentioned method embodiments, which will not be repeated in this embodiment.

[0205] The present application also provides a computer-readable storage medium on which a computer program can be stored. The computer program can be called and loaded by a processor in a terminal or a server to implement the various steps of the data processing method described in the corresponding side of the above embodiment.

[0206] Finally, it should be noted that, with respect to the above embodiments, unless the context clearly indicates an exception, the words "a", "an", "a kind" and / or "the" do not specifically refer to the singular, but may also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of clearly identified steps and elements, and these steps and elements do not constitute an exclusive list, and the method or device may also include other steps or elements. The elements defined by the sentence "includes a..." do not exclude the existence of other identical elements in the process, method, commodity or device that includes the elements.

[0207] In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0208] The terms such as "first", "second", etc. used in this application are only used for descriptive purposes to distinguish one operation, unit or module from another operation, unit or module, and do not necessarily require or imply any actual relationship or order between these units, operations or modules. They cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined as "first" or "second" may explicitly or implicitly include one or more of the features.

[0209] In addition, the various embodiments in this specification are described in a progressive or parallel manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the systems, devices, and computer equipment disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0210] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A data processing method, applied to a client side, comprising: Obtaining a page identifier of the loaded page, and sending the page identifier to the server; receiving page encoding rule data associated with the page identifier fed back by the server, and storing the page encoding rule data in a local storage space; The page encoding rule data includes reference data corresponding to encoding information of different elements in the page; In response to a page triggering event, obtaining data to be recorded for a triggering element of the page; Obtaining encoding information of the trigger element for the page according to the data to be recorded of the trigger element; Determine reference data corresponding to the coding information of the trigger element in the local storage space; wherein the reference data corresponding to the coding information of different elements in the page stored in the local storage space is obtained from a server; According to the comparison result between the data to be recorded and the determined reference data, the target recording data for the trigger element of the page is output; the comparison result is used to indicate whether the data to be recorded needs to be supplemented.

2. The method according to claim 1, wherein determining the reference data corresponding to the encoding information of the trigger element in the local storage space comprises: The reference data corresponding to the coding information of the trigger element of the page is obtained from the page coding rule data stored in the local storage space.

3. The method according to claim 1, wherein obtaining the coding information of the trigger element for the page according to the data to be recorded of the trigger element comprises: Determining a trigger path of the trigger element in the data structure of the page according to the data to be recorded of the trigger element; The trigger path is encoded according to a preset encoding method to obtain encoding information of the trigger element being triggered on the page.

4. The method according to any one of claims 1 to 3, wherein the step of outputting target recording data for the trigger element of the page according to a comparison result between the data to be recorded and the determined reference data comprises: Performing integrity check on the data to be recorded based on the determined reference data; If the data to be recorded is incomplete, the data to be recorded is updated using the reference data to obtain target recorded data for the trigger element of the page; The target record data is sent to the server.

5. A data processing method, applied to a server side, comprising: Determine page encoding rule data for client pages; The page encoding rule data includes reference data corresponding to encoding information of different elements in the page; According to the loading request of the client, the page encoding rule data corresponding to the loading page is sent to the client, so that the client stores the encoding information of different elements in the loading page contained in the page encoding rule data and the reference data corresponding to the encoding information in the local storage space; Receiving target record data for the trigger element of the loading page sent by the client; The target recorded data is determined based on a comparison result between reference data corresponding to the coding information of the trigger element and the data to be recorded obtained when the trigger element is triggered; the comparison result is used to indicate whether the data to be recorded needs to be supplemented.

6. The method according to claim 5, wherein determining the page encoding rule data of the client page comprises: Mark the positions of elements at different positions in the data structure of any page of the client; Encoding the position marks of different elements in the page to obtain encoding information capable of representing a triggering path for displaying the corresponding elements in the page; Retrieving historical record information obtained by triggering different elements of the page; Determine reference data of the corresponding element in the page according to the historical record information; The encoding information corresponding to different elements of the page and the reference data constitute page encoding rule data of the page.

7. The method according to claim 5 or 6, further comprising: Obtaining the total number of data acquisitions for the elements in the page within a preset time period; The total number of times the data of the element is obtained is cumulatively updated each time the client obtains the corresponding target record data; According to the total number of data acquisition times and preset verification rules, it is determined whether the target recorded data obtained by triggering the corresponding element within the preset time period is valid.

8. A data processing device, applied to a client side, comprising: A page identifier sending module, used to obtain the page identifier of the loaded page and send the page identifier to the server; A page encoding rule data storage module is used to receive the page encoding rule data associated with the page identifier fed back by the server, and store the page encoding rule data in a local storage space; The page encoding rule data includes reference data corresponding to encoding information of different elements in the page; A data acquisition module, used for acquiring the data to be recorded for the triggering element of the page in response to the page triggering event; A coding information obtaining module, used for obtaining coding information of the trigger element of the page according to the data to be recorded of the trigger element; A reference data determination module, used to determine the reference data corresponding to the coding information of the trigger element in the local storage space; wherein the reference data corresponding to the coding information of different elements in the page stored in the local storage space is obtained from the server; The target record data output module is used to output the target record data for the trigger element of the page according to the comparison result between the data to be recorded and the determined reference data; the comparison result is used to indicate whether the data to be recorded needs to be supplemented.

9. A data processing device, applied to a server side, comprising: A page encoding rule data determination module, used to determine the page encoding rule data of the client page; The page encoding rule data includes reference data corresponding to encoding information of different elements in the loaded page; A page encoding rule data sending module is used to send the page encoding rule data corresponding to the loaded page to the client according to the loading request of the client, so that the client stores the encoding information of different elements in the loaded page contained in the page encoding rule data and the reference data corresponding to the encoding information in the local storage space; A target record data receiving module, used for receiving target record data sent by the client for the trigger element of the loading page; The target recorded data is determined based on a comparison result between reference data corresponding to the coding information of the trigger element and the data to be recorded obtained when the trigger element is triggered; the comparison result is used to indicate whether the data to be recorded needs to be supplemented.

10. A data processing system, comprising a terminal and a server, wherein: The terminal is used to implement the data processing method according to any one of claims 1 to 4; The server is used to implement the data processing method as described in any one of claims 5-7.

Images