CN113515715B

CN113515715B - Buried point event code generation method, buried point event code processing method and related equipment

Info

Publication number: CN113515715B
Application number: CN202011106845.0A
Authority: CN
Inventors: 旷杰; 刘嘉; 李靖恺
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-10-15
Filing date: 2020-10-15
Publication date: 2024-03-15
Anticipated expiration: 2040-10-15
Also published as: CN113515715A

Abstract

The application relates to the technical field of cloud computing, in particular to a method for generating and processing a buried point event code and related equipment, wherein the method for generating the buried point event code comprises the following steps: acquiring an initial path of a target page element in a target page, wherein the initial path takes a page element of a designated element tag as a root node; converting the initial path to obtain a path character string; in the path character string, each page element in the initial path is identified through the combination of the corresponding element label and the element serial number; generating a buried point event code corresponding to the target page element according to the path character string and the page address corresponding to the target page; the present application enables a reduction in the bandwidth occupied in its transmission by reducing the amount of data encoded by a buried event.

Description

Buried point event code generation method, buried point event code processing method and related equipment

Technical Field

The application relates to the technical field of cloud computing, in particular to a buried point event code generation method, a buried point event code processing method and related equipment.

Background

With the development of cloud computing technology, the cloud computing technology is gradually applied to the embedded points of the page, and the embedded point events reported in the embedded points of the page are processed and counted based on the rapid and huge computing capacity provided by the cloud computing. Before the cloud processes the embedded point event, the embedded point event needs to be reported to the cloud by means of a certain network bandwidth, and when the reported data volume of the embedded point event is large, the corresponding bandwidth occupied in the transmission process is large.

In the related technology, the problems of large data volume of the buried point event and large bandwidth occupied by the reported buried point event exist.

Disclosure of Invention

The application provides a method for generating and processing buried point event codes and related equipment, and aims to solve the problems of large data volume of buried point events and large occupied bandwidth of reported buried point events in related technologies.

Other features and advantages of the present application will be apparent from the following detailed description, or may be learned in part by the practice of the application.

According to an aspect of the embodiments of the present application, there is provided a method for generating a buried point event code, including: acquiring an initial path of a target page element in a target page, wherein the initial path takes a page element of a designated element tag as a root node; converting the initial path to obtain a path character string; in the path character string, each page element in the initial path is identified by the combination of the corresponding element label and the element serial number; and generating a buried point event code corresponding to the target page element according to the path character string and the page address corresponding to the target page.

According to an aspect of the embodiments of the present application, there is provided a method for processing a buried point event, including: acquiring buried point configuration information, wherein the buried point configuration information comprises buried point event codes of buried point page elements, and the buried point event codes of the buried point page elements are generated according to the generation method of the buried point event codes;

And if the embedded point event code reported by the terminal is the embedded point event code of the embedded point page element, storing the reported embedded point event code into an analysis database, and generating and reporting a corresponding embedded point event code according to the embedded point event code generation method when the page element in the displayed page is triggered by the terminal.

According to an aspect of an embodiment of the present application, there is provided a generating device for buried point event codes, the device including:

the initial path acquisition module is used for acquiring an initial path of a target page element in a target page, wherein the initial path takes a page element of a designated element tag as a root node;

the conversion module is used for converting the initial path to obtain a path character string; each page element in the initial path is identified through the combination of the corresponding element label and the element sequence number;

and the code generation module is used for generating a buried point event code corresponding to the target page element according to the path character string and the page address corresponding to the target page.

According to an aspect of an embodiment of the present application, there is provided a processing apparatus for a buried point event, including:

The embedded point configuration information acquisition module is used for acquiring embedded point configuration information, wherein the embedded point configuration information comprises embedded point event codes of embedded point page elements, and the embedded point event codes of the embedded point page elements are generated according to the generation method of the embedded point event codes;

and the storage module is used for storing the reported buried point event code into an analysis database if the buried point event code reported by the terminal is the buried point event code of the buried point page element, and generating and reporting the corresponding buried point event code according to the generation method of the buried point event code when the page element in the displayed page is triggered by the terminal.

According to an aspect of an embodiment of the present application, there is provided an electronic device including: a processor; and a memory having stored thereon computer readable instructions which, when executed by the processor, implement the method of generating a buried point event code or the method of processing a buried point event as described above.

According to an aspect of the embodiments of the present application, there is provided a computer-readable storage medium having stored thereon computer-readable instructions which, when executed by a processor, implement the above method for generating a buried point event code or the method for processing a buried point event.

In the scheme of the application, the initial path is converted into the path character string, so that the attribute information of each page element in the initial path is filtered in the path character string, each page element is identified only through the combination of the element label and the element serial number, the data volume of the path character string is greatly reduced compared with the data volume of the initial path, and the simplification of the initial path is realized. Correspondingly, compared with the embedded point event code generated according to the initial path, the data volume of the embedded point event code generated by the path character string obtained through path simplification is also greatly reduced, so that in the process of reporting the embedded point event code, the network bandwidth occupied by transmitting the embedded point event code is correspondingly reduced due to the reduced data volume of the embedded point event code, and the utilization rate of the network is improved.

Moreover, because the attribute information of the page element is related to the content of the page and the path character string does not comprise the attribute information of the page element, the independence of the path character string and the page content is realized, and the path character string only reflects the structure information of the path corresponding to the target page element. If the attribute information of the page element changes in the page, the path character string of the target page element does not carry the attribute information of each page element, so that the path character string corresponding to the target page element remains unchanged, and further, buried event matching and processing can be ensured under the condition that the attribute information of the page element changes.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. It is apparent that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art. In the drawings:

FIG. 1 shows a schematic diagram of an exemplary system architecture to which the technical solutions of embodiments of the present application may be applied;

FIG. 2 is a flow chart illustrating a method of generating a buried point event code according to an embodiment of the present application;

FIG. 3 shows a partial page schematic in a page;

FIG. 4 is a flow chart of step 210 in an embodiment of the present application;

FIG. 5 is a flow chart illustrating a method of processing a buried point event according to an embodiment of the present application;

FIG. 6 is a schematic diagram of an application scenario according to an embodiment of the present application;

FIG. 7 is a flow chart of buried point event code generation and buried point event processing shown based on the application scenario of an embodiment of the present application shown in FIG. 6;

FIG. 8 is a flowchart illustrating the operation of a buried point SDK according to an embodiment of the present application;

FIG. 9 is an interface diagram illustrating a management page buried point configuration in a buried point background according to an embodiment of the present application;

FIG. 10 is a schematic diagram illustrating creation of a page buried point configuration interface in a buried point background according to an embodiment of the present application;

FIG. 11 is a schematic diagram of a management element embedded point page, according to an embodiment of the present application;

FIG. 12 is a schematic diagram of a buried point detail page for a page element buried point, according to an embodiment of the present application;

FIG. 13 is an interface schematic diagram illustrating a visualization circle selection page exposure event, according to an embodiment of the present application;

FIG. 14 is a schematic diagram showing a page element in the home page of the A website embedded in a configuration page of the embedded point background according to an embodiment of the present application;

FIG. 15 illustrates a schematic diagram of highlighting circled page elements in the first page of the A website in the buried-point background in accordance with an embodiment of the present application;

FIG. 16 is a schematic diagram showing page elements being circled according to an embodiment of the present application;

FIG. 17 is a schematic diagram showing buried point detail data showing a circled page element, according to an embodiment of the present application;

FIG. 18 is a block diagram of a buried point event code generation apparatus according to an embodiment of the present application;

FIG. 19 is a block diagram of a processing device for a buried point event according to an embodiment of the present application;

fig. 20 is a schematic diagram illustrating a computer system suitable for use in implementing the electronic device of an embodiment of the present application, in accordance with an embodiment of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present application. One skilled in the relevant art will recognize, however, that the aspects of the application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.

The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.

Big data (Big data) refers to a data set which cannot be captured, managed and processed by a conventional software tool within a certain time range, and is a massive, high-growth-rate and diversified information asset which needs a new processing mode to have stronger decision-making ability, insight discovery ability and flow optimization ability. With the advent of the cloud age, big data has attracted more and more attention, and special techniques are required for big data to effectively process a large amount of data within a tolerant elapsed time. Technologies applicable to big data include massively parallel processing databases, data mining, distributed file systems, distributed databases, cloud computing platforms, the internet, and scalable storage systems.

In the related art, in order to implement data mining, data collection is generally performed by a buried point technology, for example, by burying a point in a page element in a page, to determine a trigger condition of the page element in the page triggered by a user. Specifically, by burying points on page elements in the page, when the page elements are triggered by a user, the terminal reports burying point events to the server, so that statistics of user operation behaviors in the page is realized. The server performs data mining and analysis by analyzing a large number of collected buried point events, and uses the collected buried point events as data support for further optimizing products or providing operation.

Fig. 1 shows a schematic diagram of an exemplary system architecture to which the technical solutions of the embodiments of the present application may be applied.

As shown in fig. 1, the system architecture may include a terminal 110 and a server 120, where the terminal 110 and the server 120 communicate through a wired or wireless network, and the terminal 110 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, etc., which is not limited herein.

It should be understood that the number of terminals 110 and servers 120 in fig. 1 is merely illustrative. There may be any number of terminals 110 and servers 120, as desired for implementation. For example, the server 120 may be a server cluster formed by a plurality of servers.

The terminal 110 is configured to report a buried event. The terminal 110 may display a page, and if the page element in the page is triggered by the user, a buried event code is generated and reported according to the scheme of the present application. The page displayed in the terminal may be a web page or a page of an application program, which is not specifically limited herein.

In some embodiments of the present application, the page may be embedded by monitoring code, and may also be embedded by a software development kit (Software Development Kit, SDK) integrated into the application.

The server 120 is configured to receive the embedded point event reported by the terminal, and further may further process the received embedded point event, for example, perform visualization on a page element corresponding to the embedded point event.

In the terminal, if more triggered page elements are needed, the triggered page elements are required to generate the embedded point event and report the embedded point event to the server, the data transmission amount is extremely large, and the occupied bandwidth is also more, so that in order to reduce the data transmission amount in the embedded point event reporting process, the network utilization rate in the embedded point event reporting process is improved, and the scheme of the application is provided.

The implementation details of the technical solutions of the embodiments of the present application are described in detail below:

fig. 2 is a flowchart illustrating a method for reporting a buried point event, which may be performed by the terminal shown in fig. 1, according to an embodiment of the present application. Referring to fig. 2, the reporting method of the buried event at least includes steps 210 to 230, which are described in detail below.

Step 210, obtaining an initial path of a target page element in the target page, wherein the initial path takes a page element of a designated element tag as a root node.

For ease of understanding, some explanations are made herein for terms: the target page element does not refer to a certain page element in particular, but refers to a buried point page element capable of interacting, for example, an element capable of triggering a click operation, an element capable of inputting content, an element capable of triggering a drag operation, an element capable of triggering a drop-down operation, and the like in a page. Similarly, the target page does not refer specifically to a page, but rather refers broadly to a page in which there are embedded page elements.

And acquiring control behavior data of the user in the page by burying the page elements. In some embodiments of the present application, after detecting that a target page element in a target page is triggered, step 210 and subsequent steps are performed to generate a buried event code for the triggered target page element, and perform automatic reporting of the buried event code to record that the target page element is triggered by a user.

The embedded point of the target page element can be embedded point based on configuration information or can be a full embedded point. The embedding of the point based on the configuration information means that if the configuration information indicates embedding of a certain page element, the page element is used as a target page element, and trigger detection is performed on the page element indicated by the configuration information. The fully embedded point is to take any page element in the page as a detected object, and if any page element is detected to be triggered, reporting an embedded point event for the page element.

In some embodiments of the present application, a buried point SDK (Software Development Kit, a software development kit) is integrated in a target page, through which a trigger event of any target page element in the target page is detected, for example, a click, a page exposure, etc. triggered by a user is detected at the buried point SDK, and when the event is triggered, a processing function is called, and a corresponding buried point event code is calculated according to the method of the present application and is automatically reported. The page exposure event refers to an event of displaying a page in a display screen of the terminal, and it can be understood that the triggering of the target page element in the target page is performed on the basis that the target page is displayed, so that when the page exposure event of the target page is detected, that is, the target page is displayed. The pages referred to in this application are described by a page document whose structure includes a header and a body, the body of the page document determining the content displayed in the page, wherein the body is the content under the body tag. The page document may be an html (hypertext markup-up Language) document.

The initial path of a target page element refers to an ordered set of elements from the target page element to the page root element in the target page where it is located. The page root element in the target page refers to a page element serving as a root node. In a specific embodiment, the root element (the page element serving as the root node) of the page can be specified according to actual needs, that is, the page element with the specified element tag is taken as the root node in the initial path, so that subsequent embedded point event coding is facilitated.

For example, if the whole html document is defined by an html tag in the html document, the html tag may be used as a specified element tag in the initial path of the target page element. For another example, since the main body part in the html document determines the content displayed in the page, and the target page element is used as the page element capable of interacting in the page, in the page document, the element information corresponding to the page element is located in the content under the body label, in other words, the triggered target page element is a sub-page element under the body label, which may be a first-level sub-page element or a deeper-level sub-page element. Thus, the body tag can also be used as a specified element tag, and particularly in an html document, the body tag is embedded under the html tag.

If html tag is used as the designated element tag, the initial path of a target page element is: html/body/div [1]/form [1] @ name = "f" ]/span [1] @ class = "bt" ]/input [1] @ id = "su" ]. Html, body, div, form, span and input in this initial path are element tags for the corresponding page element. In the initial path, the last page element, i.e. the element tag is the "input" page element, is the target page element. The content in brackets behind the element tag is the element information of the located page element, and the element information includes attribute information of the page element, for example [ @ name= "f" ] indicates the element name of the page element whose element tag is "form" in the initial path, [ @ class= "bt" ] indicates the class attribute of the page element whose element tag is "span" in the initial path, [ @ id= "su" ] indicates the ID of the page element whose element tag is "input" in the initial path. Wherein, the number 1 in the brackets behind the page element with the element label of "form" is the element serial number corresponding to the page element. Similarly, the numbers in brackets after the corresponding element tags of other page elements are element numbers.

For the listed target page element, if the body tag is used as the designated element tag, the initial path of the target page element is as follows: body/div [1]/form [1] @ name = "f" ]/span [1] @ class = "bt" ]/input [1] @ id = "su" ]. As can be seen from the above, since the body tag is embedded under the html tag in the page document, when the body tag is used as the specified page element, compared with the html tag being used as the specified element, the initial path of the target page element is shortened, correspondingly, the data volume of the embedded point event code obtained later correspondingly decreases, and the transmission volume of the data correspondingly decreases in the process of reporting the embedded point event.

Step 220, converting the initial path to obtain a path character string; in the path character string, each page element in the initial path is identified by the combination of the corresponding element tag and element serial number.

The initial path of the target page element comprises element information of each related page element, wherein the element information of the page element not only comprises element labels and element serial numbers of the page element, but also possibly comprises attribute information of the page element, wherein the attribute information can be text attribute, identification (ID) attribute, class (class) attribute, other custom attribute and the like, and the attribute information can also comprise size information of the page element in the target page, such as height, width and the like of the page element.

In a page, there may be one or more sub-page elements under an element tag, and the element sequence number of a page element refers to the sequence number of the page element in the parent page element corresponding to the page element. For example, if there are 4 sequentially arranged page elements of the div tag under the body tag, then body/div:5 represents the 5 th div page element under the body tag.

Step 220 corresponds to converting the initial path into a structure-oriented "element tag: element sequence number "path form, i.e. each page element in the initial path passes" element tag: the element serial number is used for identification, and the path character string is obtained.

It will be appreciated that if at a level one page element there is only one page element and there is no peer page element at the same level as that page element, then the element sequence number of that page element is null. For example, in an html document, a page element of the same level does not exist in a body tag, and therefore, the element sequence number of the page element corresponding to the body tag is generally null.

Continuing the example where the initial path is "/html/body/div [1]/form [1] @ name =" f "]/span [1] @ class =" bt "]/input [1] @ id =" su "]", converting the initial path according to step 220, filtering out attribute information of each page element in the initial path, where the obtained path string may be: html/body/div:1/form 1/span:1/input 1. In the obtained path character string, the element information corresponding to each page element does not include attribute information, and the page element is identified by a combination of an element tag and an element sequence number. It can be seen from this that by converting the initial path, the path character string that does not include the attribute information of the page element is obtained, the character length of the obtained path character string is greatly shortened as compared with the initial path, and the data amount corresponding to the corresponding path character string is also greatly reduced as compared with the data amount of the initial path.

Fig. 3 shows a schematic view of a part of a page in a page, as shown in fig. 3, a page element corresponding to an area where a frame 1 in fig. 3 is located is a page element with a div as a 5 th element tag under a body tag (the page element may be represented as div:5 in the form of "element tag: element sequence number"); the page element corresponding to the area where the frame 2 is located is the page element with div as the 1 st element label under the page element corresponding to the frame 1 (the page element can be expressed as div:1 according to the form of 'element label: element serial number'). The page element corresponding to the area where the frame 3 is located is the page element with div as the 1 st element label under the page element corresponding to the frame 2 (the page element can be expressed as div:1 according to the form of 'element label: element serial number').

Assuming that the page element corresponding to the area where the frame 1 is located is the first-stage sub-page element under the body tag, and assuming that the designated element tag is the body tag, if the page element corresponding to the area where the frame 3 is located in fig. 3 is taken as the target page element, the element tag is as follows: element sequence number "path form, the path string of the target page element can be expressed as: body/div 5/div 1.

Step 230, generating a buried point event code corresponding to the target page element according to the path character string and the page address corresponding to the target page.

The page address corresponding to the target page may be a URL (Uniform Resource Locator ) of the target page.

In some embodiments of the present application, the path string and the page address corresponding to the target page may be spliced and combined to obtain a pre-encoded string, and then the obtained pre-encoded string is encoded according to an encoding algorithm to obtain the buried event code. And encoding the page addresses corresponding to the path character string and the target page, which is equivalent to encrypting the page addresses corresponding to the path character string and the target page.

The encoding Algorithm may be an MD5 Algorithm (Message-Digest Algorithm) among others. Of course, the encoding algorithm is not limited to the MD5 algorithm, but may be an algorithm such as SHA (Secure Hash Algorithm ), MAC (Message Authentication Code, message authentication code algorithm), or the like, and is not particularly limited herein.

For data with any length, the length of the MD value of the data obtained after the data is encoded by adopting the MD5 algorithm is fixed, so that the combined character string with the indefinite length can be converted into the buried point event code with the definite length by adopting the MD5 algorithm, the buried point event code can be stored conveniently, and the problem that the overlong combined character string cannot be formatted and stored effectively can be prevented. The path character string is used for indicating the path of the target page element in the target page, so that the embedded point event code of the target page element is generated according to the path character string and the page address corresponding to the target page, and the embedded point event code not only can embody the target page where the target page element is located, but also can further embody the path of the target page element in the target page.

In some embodiments of the present application, after step 230, the method further comprises: reporting the buried point event code.

In some embodiments of the present application, the embedded point event codes are reported to the server, and the server performs data analysis according to the received numerous embedded point event codes, for example, performs analysis of user operation behaviors, counts the number of times each page element is triggered, and so on. Reporting the buried point event code to realize reporting of the buried point event.

In some embodiments of the present application, a terminal deploys a report queue, adds a buried event code to the report queue after obtaining the buried event code, and extracts the buried event code from the report queue and sends the buried event code to a server when the buried event code in the report queue satisfies a sending condition.

In some embodiments of the present application, a temporary database is deployed in the server, and the embedded event codes in the report queue are uploaded to the temporary database for temporary storage.

In the scheme of the application, the initial path is converted into the path character string, so that the attribute information of each page element in the initial path is filtered in the path character string, each page element is identified only through the combination of the element label and the element serial number, the data volume of the path character string is greatly reduced compared with the data volume of the initial path, and the simplification of the initial path is realized. Compared with the embedded point event code generated according to the initial path, the data volume of the embedded point event code generated by the path character string obtained by path simplification is also greatly reduced, so that in the process of reporting the embedded point event code, the network bandwidth occupied by transmitting the embedded point event code is correspondingly reduced due to the reduced data volume of the embedded point event code, and the utilization rate of the network is improved.

In the application scene of the full buried point, all page elements in the page are required to be used as buried point objects, and buried point event codes are correspondingly reported, so that the data quantity required to be transmitted is huge, and the initial path is converted according to the method of the application, and the buried point event codes are correspondingly generated and reported, so that the data transmission quantity can be greatly reduced.

Moreover, because the attribute information of the page element is related to the content of the page and the path character string does not comprise the attribute information of the page element, the independence of the path character string and the page content is realized, and the path character string only reflects the structure information of the path corresponding to the target page element.

In the related art, more and more online projects are built by adopting component style processing technologies such as CSS Modules, and when each project is built, a class (class) name completely different from a previous version may be regenerated, so that class attributes of page elements are changed, in this case, the initial path is converted according to the process of step 220, so that it can be ensured that even if class attributes of each page element involved in the initial path of a target page element are changed, and a path character string corresponding to the target element remains unchanged. Similarly, even if the text attribute or the identification attribute of each page element involved in the initial path of the target page element changes, the path character string corresponding to the target element can be ensured to be unchanged.

In summary, when the page content changes due to the change of the attribute information of the page element in the page, the path character string of the target page element does not carry the attribute information of each page element, so that the path character string corresponding to the target page element remains unchanged, and further, it can be ensured that buried event matching and processing can still be performed under the condition that the attribute information of the page element changes.

In some embodiments of the present application, as shown in fig. 4, step 210 includes:

step 410, obtain triggered coordinate information of the target page element.

The triggered coordinate information is used to indicate the coordinate of the triggered position when the target page element is triggered by the user, for example, if the target page element is clicked by the user, the triggered coordinate information is used to indicate the clicked coordinate on the target page element.

Step 420, searching the parent page element step by step according to the triggered coordinate information until the element label corresponding to the searched parent page element is the appointed element label.

The parent page element refers to the previous page element of the page element that needs to be traced back currently, that is, the parent page element is relative to the current page element. In step 420, backtracking is performed step by step based on the target page element, and the corresponding parent page element is searched.

In some embodiments of the present application, the document/element from point interface is configured to obtain all page elements at the specified coordinates in the current viewport, so that the document/element from point interface may be used to obtain the target page element according to the triggered coordinate information, and further, search the parent page element step by step with the target page element as a base point until the element tag of the found parent page element is the specified element tag.

For example, if the designated element tag is a body tag, if the element tag of a parent page element is found to be the body tag, the backtracking is stopped, and the found page element with the body tag is the root node in the initial path.

After each parent page element is found, element information of the corresponding page element can be correspondingly obtained from the page document of the target page, wherein the element information of the page element comprises element labels, element serial numbers and attribute information of the page element, and the attribute information comprises text attributes, identification attributes, class attributes, size information and the like listed above.

Step 430, generating an initial path according to the element information corresponding to the target page element and the element information corresponding to each searched parent page element, wherein the element information at least comprises the element label and the element serial number of the corresponding page element.

And combining the searched element information corresponding to each page element and the element information corresponding to the target page element according to the corresponding upper-lower relationship to obtain an initial path.

Through the process of steps 410-430 above, the acquisition of the initial path corresponding to the target page element is achieved.

In some embodiments of the present application, the element information includes attribute information of the page element; prior to step 220, the method further comprises: and determining the buried point type of the target page element according to the attribute information of the target page element. In this embodiment, step 220 includes:

and converting the initial path according to a conversion mode corresponding to the buried point type to which the target page element belongs, so as to obtain a path character string.

In this embodiment, the page elements are classified according to the attribute information of the page elements, and each type corresponds to a buried point type, where each buried point type corresponds to a conversion mode.

In some embodiments of the present application, the embedded point type includes a first type and a second type, and the page element belonging to the first type is a heterogeneous element, and the page element belonging to the second type is a homogeneous element.

Converting the initial path according to a conversion mode corresponding to the buried point type to which the target page element belongs, and obtaining a path character string, wherein the method comprises the following steps:

If the embedded point type of the target page element is the first type, combining the element serial numbers corresponding to the page elements extracted from the initial path with the corresponding element labels according to the arrangement sequence of the page elements in the initial path to obtain a path character string.

If the embedded point type of the target page element is the second type, combining the element serial number corresponding to the page element extracted from the initial path as the intermediate node with the element label corresponding to the page element and the element label corresponding to the extracted target page element according to the arrangement sequence of the page elements in the initial path to obtain a path character string.

Homogeneous elements, which may also be referred to as homogeneous elements, refer to page elements that do not have a sequential relationship with each other under the same parent page element, that is, there is no sequential relationship between multiple page elements under the parent page element, and homogeneous elements, such as unordered list item elements, cell elements, etc. in a page. Otherwise, if the page elements with the sequence relationship with each other under the same-level parent page element are heterogeneous elements. For example, in fig. 3, if there is a sequential relationship between the page element corresponding to the region where the frame 1 is located and other div elements under the body label, the page element corresponding to the region where the frame 1 is located is a heterogeneous element.

For homogeneous elements, the aggregation result of all page elements at the same level is often required to be counted, but the meaning of counting each homogeneous element is not great. Therefore, in this embodiment, if the type of the buried point to which the target page element belongs is the second type (i.e., the target page element is a homogeneous element), in the path character string corresponding to the target page element, the element tag corresponding to the target page element is explicitly specified, that is, the target page element is identified by the corresponding element tag, and then the path character string corresponding to other homogeneous elements in the same level of the target page element is the same as the path character string corresponding to the target page element, so that the server may perform aggregate statistics on the plurality of homogeneous elements instead of performing statistics on each homogeneous element in the level.

For heterogeneous elements, in the path character string, each page element is identified by a corresponding element tag and element serial number.

Continuing the example corresponding to fig. 3, taking the page element corresponding to the area where the frame 3 in fig. 3 is located as the target page element, if the type of the embedded point to which the target page element belongs is the first type, the path character string corresponding to the target page element is "body/div:5/div:1/div:1"; if the embedded point type of the target page element is the second type, the path character string corresponding to the target page element is 'body/div: 5/div: 1/div'.

In some embodiments of the present application, the first type includes a first subtype, and the page elements belonging to the first subtype include at least two controls; in this embodiment, step 230 includes: generating a precoding character string according to the path character string, the page address corresponding to the target page and the additional information corresponding to the target page element, wherein the additional information comprises the buried point type of the target page element; when the buried point type of the target page element is the first subtype, the additional information also comprises text attribute content corresponding to the triggered control in the target page element; and encrypting the pre-coding character string to obtain the embedded point event code corresponding to the target page element.

For a page element comprising at least two controls, the user triggers different controls in the page element to perform different operations, and because the plurality of controls are positioned in the same page element, if the controls are not distinguished, buried point event codes triggering different controls in the page element are aggregated together.

Therefore, when the embedded point type to which the target page element belongs is the first subtype, in order to facilitate the service end to distinguish different controls in the same target page element, text attribute content corresponding to the triggered control in the target page element is added into the attachment information, and the text attribute content corresponding to the control is used as part of information of embedded point event coding, so that the service end can distinguish different controls in the target page element according to the text attribute content in the attachment information.

For example, if a target page element includes two controls, namely, a "registration" control and a "login" control, text attribute content corresponding to the "registration" control is used to indicate that the control is used to trigger a registration operation, and text attribute content corresponding to the "login" control is used to indicate that the control is used to trigger a login operation.

In some embodiments of the present application, the first type further includes a second subtype, the number of controls included in the page element attributed to the second subtype not exceeding one; for page elements that include no more than one control, the additional information may not include the text attribute content of the triggered control, as no differentiation of controls is required.

In the scheme of the embodiment, the reporting of the homogeneous element and the element text content event is supported, and the collection of embedded point event codes of the same type of page elements and the sensing of element text content change can be realized.

In some embodiments of the present application, before the step of generating the precoding string according to the path string, the page address corresponding to the target page, and the additional information corresponding to the target page element, the method further includes: simplifying the path character string, omitting the element information corresponding to the page element serving as the root node in the simplified path character string, identifying the page element serving as the intermediate node by the corresponding element serial number, and identifying the target page element by the corresponding element label or the corresponding element serial number; and combining the target path character string, the page address corresponding to the target page and the additional information corresponding to the target page element to obtain a precoding character string.

In this embodiment, in order to further reduce the data transmission amount, the path string is simplified, so that in the simplified path string, the element information corresponding to the page element serving as the root node is omitted, the page element serving as the intermediate node is identified by the corresponding element sequence number, and the target page element is identified by the corresponding element tag or the corresponding element sequence number. For the page element identified by the element sequence number, the element sequence number can identify what sub-element the page element is the page element of the upper stage, so that since the page element of the subsequent stage can be determined by taking the page element of the root node as the parent element in the case that the page element of the root node is known in the initial path.

In some embodiments of the present application, if the type of the buried point to which the target page element belongs is the first type, the target page element in the target path string is identified by the corresponding element sequence number; if the buried point type to which the target page element belongs is the second type, the target page element in the target path character string is identified through the corresponding element tag.

Continuing with the example corresponding to fig. 3, continuing to use the page element corresponding to the area where the border 3 in fig. 3 is located as the target page element, and then the path character string corresponding to the target page element is "body/div:5/div:1/div:1". If the buried point type of the target page element is the first type, simplifying the path character string corresponding to the target page element to obtain a path character string of "/5/1/1"; if the buried point type of the target page element is the second type, simplifying the path character string corresponding to the target page element to obtain a path character string of "/5/1/div".

In this embodiment, in the case that the page element after the root node in the initial path is the page element of the nested multi-layer identical element tag, by simplifying the initial path string, the length of the path string after simplification is greatly shortened relative to the length of the path string before simplification, and the data volume is correspondingly reduced, in the above example, the target path string is "/5/1/1" compared with the path string "body/div:5/div:1/div:1", and the data volume of the target path string is reduced by 84%.

Under the condition that the page elements behind the root node in the initial path are nested multi-layer page elements with the same element labels, combining the simplified path character string, the page address corresponding to the target page and the additional information corresponding to the target page element to obtain a pre-coding character string; of course, if the page element after the root node in the initial path is not the nested page element with the same multi-layer element tag (in other words, the page element after the root node in the initial path includes at least two different element tags), the path character string, the page address corresponding to the target page and the additional information corresponding to the target page element are directly combined to obtain the pre-coding character string.

In some embodiments of the present application, prior to step 220, the method further comprises: and filtering the target page element according to a preset filtering rule.

For a page element which is provided for a user to input randomly, for example, a word input box for the user to input a word to be translated, a word query input box and the like, because the page element is provided for the user to input randomly, if text content input in the page element is added to additional information and a buried event code is reported for the page element, under the condition that input content is different, the buried event codes generated for the page element are correspondingly different, the obtained buried event codes may be completely divergent, and further data cannot be aggregated.

Therefore, in order to avoid such a situation, a filtering rule may be preset, and the page elements for inputting content are filtered, that is, the embedded point event code is not generated for the page elements.

In some embodiments of the present application, whether a page element is a page element for content input may be identified from element information of the page element. If the element information of the page element comprises an input tag or a text-area tag, determining the page element as the page element for inputting the content.

In some embodiments of the present application, the preset filtering rule defines that the page element to be filtered out may be that the target page element is an element for inputting content, a page element for inputting content is included in a sub-page element, and a page element for inputting content is included in a sibling page element.

For example, the initial path is "/html/body/div [1]/form [1] @ name =" f "]/span [1] @ class =" bt "]/input [1] @ id =" su "]" and the element tag of the target page element is "input", which indicates that the target page element is the element for inputting content, and according to the filtering rule, the element tag is the target page element of "input" and is the page element to be filtered, and then it is not necessary to generate the embedded point event code for the target page element.

Similarly, if the element tag of the target page element is "text-area", the target page element is also the page element that needs to be filtered according to the filtering rule described above.

Under the above filtering rule, for a target page element, element information of a sub page element of the target page element and element information of a sibling page element of the target page element (i.e., a page element identical to the target page element) need to be acquired, whether an element tag of the sub page element or the sibling page element of the target page element is an "input" tag or a "text-area" tag is judged according to the acquired element information, and if yes, the target page element is also the page element to be filtered, and no buried event code needs to be generated for the target page element. Of course, in other embodiments, the filtering rule may be set according to actual needs to filter out other page elements that do not need to generate the embedded event code, which is not limited herein specifically.

Fig. 5 is a flowchart illustrating a method of processing a buried point event, which may be performed by the server shown in fig. 1, according to an embodiment of the present application. Referring to fig. 5, the method for processing the buried event at least includes steps 510 to 520, which are described in detail below.

Step 510, obtaining buried point configuration information, where the buried point configuration information includes buried point event codes of the buried point page elements, where the buried point event codes of the buried point page elements are generated according to the generation method of the buried point event codes.

In some embodiments of the present application, the embedded point configuration information is generated by embedding the page elements, and the generated embedded point configuration information indicates which embedded point event encodings of the page elements are required.

In some embodiments of the present application, prior to step 510, the method further comprises: in a first target page displayed in an embedded manner in a buried point element configuration page, generating a corresponding buried point event code for a triggered page element according to an element buried point configuration operation triggered on the page element in the first target page and the generation method of the buried point event code; and generating buried point configuration information according to the generated buried point event code.

In this embodiment, a page for performing embedded point element configuration, that is, an embedded point element configuration page in which an analyst can embed points for page elements is provided.

The first target page does not refer to a certain page, but refers to a page needing to be embedded with page elements. In this embodiment, the first target page is displayed in-line in the embedded point element configuration page. The first target page may be displayed in an embedded point element configuration page in an iframe manner. Because the first target page is displayed in the embedded point element configuration page in an embedded manner, an analyst can conveniently visually and circularly select the page elements in the first target page so as to embed points of the circularly selected page elements, and the circularly selected page elements are embedded point page elements.

In this embodiment, since the first target page is displayed in the embedded point element configuration page, an analyst may circle and select a page element in the displayed first target page, then correspondingly obtain an initial path of the circled page element, and generate a corresponding embedded point event code according to the initial path of the circled page element according to the above embedded point event code generation method.

And step 520, if the embedded point event code reported by the terminal is the embedded point event code of the embedded point page element, storing the reported embedded point event code into an analysis database, and when the page element in the displayed page is triggered, generating and reporting a corresponding embedded point event code according to a generation method of the embedded point event code by the terminal.

In this embodiment, the terminal displays the page, if the page element in the page displayed in the terminal is triggered, the initial path of the triggered page element is correspondingly acquired, the embedded point event code of the triggered page element is generated according to the method for generating the embedded point event code, and then the generated embedded point event code is reported to the server.

After reporting the embedded point event code to the server by the terminal, the server judges whether the embedded point event code reported by the terminal is consistent with the embedded point event code of the embedded point page element according to the embedded point event code of the embedded point page element in the embedded point configuration information, and if so, the embedded point event code reported by the terminal is indicated to be the embedded point event code of the embedded point page element; otherwise, the embedded point event code indicating that the embedded point event code reported by the terminal is not the embedded point event code of the embedded point page element

In this embodiment, the terminal reports the embedded point event code, the server screens the embedded point event code reported by the terminal according to the embedded point configuration information, that is, if the embedded point event code reported by the terminal is the embedded point event code of the embedded point page element indicated by the embedded point configuration information, the embedded point event code reported by the terminal is stored in the analysis database, so that the terminal does not need to issue the embedded point configuration information first, the terminal can generate the embedded point event code for the triggered page element when any page element in the displayed page is triggered and report the embedded point event code, and the server screens the embedded point event code reported by the terminal according to the embedded point configuration information, which is equivalent to implementing full embedded point on the page element in the terminal. In addition, because the terminal is a full embedded point of the page element, when the embedded point configuration information is changed, the corresponding embedded point event codes can be screened out from the embedded point event codes reported by the terminal according to the changed embedded point configuration information.

In some embodiments of the present application, a temporary database is further provided in the server, and if the embedded point event code reported by the terminal is not the embedded point event code of the embedded point page element, the embedded point event code reported by the terminal is stored in the temporary database, so that an analyst can extract the embedded point event code of the required page element from the temporary database as required to perform data analysis.

In some embodiments of the present application, after the step of generating the buried point configuration information according to the generated buried point event code, the method further includes:

and displaying the embedded point page element in the first target page in the embedded display mode according to the appointed display mode.

The specific display mode may be a specific color, or a mark or the like additionally set for the embedded point page element, and is not particularly limited herein. In a particular embodiment, the specified display mode may be highlighting, i.e., the embedded point page element is highlighted in the first target page of the in-line display.

The embedded point page elements are displayed according to the appointed display mode, so that the display mode of the embedded point page elements is different from the display mode of the non-embedded point page elements, and a user or an analyst can conveniently and intuitively determine which page elements in the displayed first target page are the embedded point page elements.

In some embodiments of the present application, the embedded point element configuration page is provided with an operation control for controlling whether to display the embedded point page element according to a designated display mode, if the operation control is triggered to be opened, the embedded point page element indicated by the embedded point configuration information is displayed according to the designated display mode, otherwise, if the operation control is triggered to be closed, the embedded point page element is displayed according to the same mode as the non-embedded point page element, that is, in the first target page, the non-embedded point page element and the embedded point page element are displayed indifferently.

It will be appreciated that prior to displaying the embedded point page element in the specified display mode, it is also necessary to determine the location of the embedded point page element in the displayed first target page.

In some embodiments of the present application, before the embedded point page element is displayed in the first target page in the in-line display manner, the method further includes: acquiring a path character string of the embedded point page element; carrying out path reconstruction according to the path character strings of the embedded point page elements to obtain path information of the embedded point page elements; and determining the position of the embedded point page element in the first target page displayed in an embedded manner according to the path information of the embedded point page element.

In some embodiments of the present application, the path string of the acquired embedded point page element may be reported by the terminal. As described above, in the process of generating the buried point event code, the terminal needs to convert the initial path of the target page element first to obtain the path character string of the target page element. Therefore, the terminal can report the obtained path character string to the server, and store the reported path character string of the page element and the embedded point event code of the page element in a correlated manner. Therefore, when the server determines that the embedded point event code reported by the terminal is the embedded point event code of the embedded point page element, the path character string of the embedded point page element can be correspondingly acquired.

In other embodiments of the present application, the obtained path string of the embedded point page element may also be obtained in the process of embedding the point configuration on the page element. As described above, in the process of embedding point configuration on a page element in a first target page displayed in an embedded manner in a embedding point element configuration page, when a user circles the page element in the displayed first target page, the initial path of the page element is correspondingly obtained, and the embedding point event code of the circled page element is generated according to the generating method of the embedding point event code, and then the circled page element is the embedded point page element. In this process, a process of converting the initial path of the circled page element to obtain the path character string of the circled page element is still involved. Thus, in this embodiment, the path string of the circled page element obtained in this process may be stored in association with the generated buried event code, for example, as part of the buried configuration information. In this embodiment, after determining that the buried point event code reported by the terminal is the buried point event code of the buried point page element, the path string obtained by using the one end performing the buried point configuration as the buried point page element may be correspondingly obtained.

In some embodiments of the present application, a step of performing path reconstruction according to a path string of the embedded point page element to obtain path information of the embedded point page element includes: converting element labels and corresponding element serial numbers corresponding to page elements in the path character string into corresponding selector identifiers; and carrying out path reconstruction according to the selector identifiers corresponding to the page elements to obtain path information of the embedded point page elements.

It should be noted that the selector identifier herein refers to the selector identifier of the tag selector. In some embodiments of the present application, the selector identifier of the page element may be obtained by using an element number corresponding to each page element in the path string in the form of "nth-child (n)", where n in "child (n)" is an element number. For example, in the path string "body/div:5/div:1/div:1", the selector identification of the page element "div:5" may be "div: nth-child (5)".

Continuing with the example of FIG. 3 above, if the path string is "body/div:5/div:1/div:1", the path information obtained by performing path reconstruction may be "body div: nth-child (5) div: nth-child (1) div: nth-child (1)"; in the case where the page element following the root node in the initial path is a nested multi-layer page element with the same element tag, the path information may be further simplified to "body: nth-child (5): nth-child (1): nth-child (1)".

In some embodiments of the present application, after obtaining the path information of the embedded point page element, the path information may be transferred to a document.

After determining the position of the embedded point page element in the first target page displayed in-line, the embedded point page element may be displayed in a designated display manner, for example, highlighting the embedded point page element as listed above.

The method for generating the embedded point event code and the method for processing the embedded point event according to the present application will be described with reference to an embodiment.

Fig. 6 shows an application scenario diagram in the present embodiment, as shown in fig. 6, where the application scenario includes a terminal, a buried point background, and an analysis end, where the analysis end includes a first analysis platform and a second analysis platform.

The embedded point background provides a configuration page, a data analysis personnel can select the page element in the first target page in an embedded manner in the configuration page, (the selected page element is also called embedded point page element), further, embedded point configuration information (the embedded point configuration information can be called embedded point configuration information) corresponding to the selected page element is generated, and the embedded point configuration information is uploaded to the first analysis platform. The embedded point background is provided with an embedded point SDK, when the page element in the first target page which is displayed in an embedded manner in the embedded point background is selected, the embedded point event code of the selected page element can be generated through the embedded point SDK, and further embedded point configuration information aiming at the selected page element is generated according to the generated embedded point event code. The embedded point configuration information can be issued to the analysis end.

The terminal is provided with a buried point SDK, and after detecting that page elements in a page displayed in the terminal are triggered, the buried point SDK calculates buried point event codes and reports the buried point event codes to the first analysis platform.

The first analysis platform screens the embedded point event codes reported by the terminal according to the embedded point configuration information, and if the reported embedded point event codes are determined to be the embedded point event codes of the embedded point page elements indicated by the embedded point configuration information, the embedded point event codes reported by the terminal are sent to the second analysis platform, and the second analysis platform further analyzes the embedded point event codes.

Fig. 7 is a flowchart of buried event code generation and buried event processing shown based on the application scenario shown in fig. 6.

As shown in fig. 7, the analysis end establishes communication connection with the terminal and the embedded point background. The analysis end is provided with a data reporting service, an application service and a data analysis service, and a temporary storage database, an analysis database and an application configuration database. The data reporting service is used for receiving the embedded point event codes reported by the terminal; the application service is used for receiving the circle selection configuration information reported by the embedded point background, providing the stored circle selection configuration information for the embedded point background, and storing the circle selection configuration information into the application configuration database after receiving the reported circle selection configuration information.

As shown in fig. 7, in the terminal, if the user opens the page integrated with the embedded point SDK, reporting of the embedded point event code is performed through the following steps 721-724: step 721, the buried point SDK detects events such as page clicking, exposure, etc., and step 722, detects that a page element is triggered by a user; step 723, buried point SDK generates buried point event code; step 724, add the embedded event code to the report queue, delay reporting. The embedded point SDK calls a processing function, calculates a corresponding embedded point event code, adds the event code to a reporting queue, delays communication with a data reporting service, and stores event embedded point data into an analysis data temporary storage database.

In the embedded point background, the first target page is displayed in the embedded point background in a embedded manner through the following steps 711-714: step 711, the buried point SDK detects that the buried point background usage scene is in the buried point background, and establishes connection with the buried point background; step 712, in the browsing state of the embedded point background, the embedded point SDK intercepts the jump behavior in the page; step 713, in the embedded point background in a circle selection state, the embedded point SDK intercepts the click action of the user and transmits the information of the clicked page element to the embedded point background; step 714, the embedded point background is continuously communicated with the embedded point SDK to obtain element information and provide a visual circled configuration page; the first target page is displayed in the configuration page in an embedded manner, so that a user can conveniently conduct visual circle selection on page elements in the first target page displayed in the embedded manner.

In the buried point background, a data analysis person can log in the buried point background and can configure a page needing to be buried point configuration. The data analyst can communicate with the appointed data form of the buried point SDK through the buried point background by using a mouse click mode. The embedded point background provides a visual configuration page to carry out page element circle selection, and the generated embedded point configuration information is sent to the application service, completes event registration and is stored in the application configuration database by circle selection of page elements and further generation of embedded point configuration information of the circled page elements.

In the analysis end, when the circle selection allocation information is effective for the first time, the application service processes the buried point event codes in the temporary storage database in batches within a certain period, compares the buried point allocation information stored by the data analysis personnel with the buried point event codes to be processed, and transfers the buried point event codes corresponding to the buried point page elements indicated by the buried point allocation information in the temporary storage database to the analysis database for persistent storage. The data analysis service can then access the data in the analysis database on the fly. When the circle selection configuration information is effective, the application service judges whether the embedded point event code reported by the terminal is the embedded point event code of the embedded point page element according to the embedded point configuration information, if so, the reported embedded point event code is stored in the analysis database in a second-level delay mode, and therefore time delay caused by a batch processing period can be reduced.

Fig. 8 is a flowchart illustrating the operation of the buried point SDK according to an embodiment of the present application. As shown in fig. 8, after the embedded point SDK is started, if the embedded point SDK is not in the embedded point background environment, that is, it is indicated that the embedded point SDK is in the terminal where the user is running, the embedded point SDK executes the following steps 801-810:

step 801, reporting a page event and detecting a page close event;

step 802, detecting a click event for a page element; if a click event is detected, step 803 is performed;

step 803, obtaining an initial path of a target page element;

step 804, calculating a path character string of the target page element;

step 805, judging whether the content collection condition is satisfied; if yes, go to step 806; if not, go to step 807;

step 806, generating a pre-encoded string. Specifically, a precoding character string is generated according to the path character string of the target page element, the page address of the page where the target page element is located and the additional information of the target page element.

Step 807, the MD5 is encrypted and added to an reporting queue; specifically, the pre-coding character string is subjected to MD5 encryption processing to obtain a buried point event code, and the buried point event code is added into a report queue.

Step 808, reporting the embedded point event code in a delayed manner;

step 809, judging whether the application program where the page is located is finished running; if so, step 810 is performed, and if not, step 802 is performed again.

Step 810, reporting a page close event.

After the buried point SDK is started, if the buried point SDK is in a buried point background environment, requesting the buried point background to establish a circle selection connection; after the circling connection is successful, if the embedded point background is in the circling state, the following steps 11-817 are executed:

step 811, acquiring circle selection configuration information;

step 812, the page element path backtracks and displays the circled elements; specifically, path backtracking is carried out on the path character strings of the selected page elements, path information of the corresponding page elements is determined, then the positions of the selected page elements in the page are determined according to the path information, and the selected page elements are highlighted.

Step 813, detecting whether there are unreturned elements; if not, go to step 814; if so, then step 814-1 is performed: carrying out a spring frame prompt at a buried point background;

step 814, the page basic information, such as the page height and width, is transferred to the embedded point background.

Step 815, detecting a click event in the configuration page and preventing default click behavior of the page; if a click event in the configuration page is detected, then step 816 is performed; if a click event in the configuration page is not detected, continuing to execute step 815;

Step 816, the selected page element is displayed, and the element information, such as the element path character string, the element screenshot, etc., of the selected page element is transferred to the embedded point background for previewing.

Step 817, detecting whether the circling is exited; if yes, detecting whether the ring selection state exists; if not, go back to step 815.

After the circling connection is successful, if the buried point background is not in the circling state, steps 818-820 are sequentially executed:

step 818, loading the page in the terminal, specifically, displaying the page in an embedded manner in an iframe mode.

Step 819, detecting a page jump event, preventing page jump behavior;

step 820, it is detected whether the background is exited, if not, the process returns to step 818, if yes, the process ends.

In summary, it can be seen that the workflow of the buried SDK is related to the working environment in which it is located. When the buried point SDK is positioned in a page of the terminal, the buried point SDK can report page exposure event data by default, meanwhile, the global clicking event of a user is detected, and when the user clicks, each type of buried point event code is calculated and reporting is delayed; when the buried SDK is in the buried background environment, it may delay acquiring page elements of the circled portion and perform additional tasks to provide visual circling functions, such as intercepting click events, tracing back circled elements, highlighting circled elements, etc.

In this embodiment, the embedded point SDK automatically and fully embeds points, and can automatically collect and report the number of click or exposure events occurring on a page displayed in the terminal, and the reported event data will be temporarily stored in the analysis background. And performing visual preview and visual circle selection of the page elements serving as the embedded point objects in the configuration page provided by the embedded point background. The buried event codes corresponding to the successfully selected page elements are stored in an analysis database and further incorporated into a more complex data analysis process.

In the scheme, the embedded point configuration is not needed in the background, the embedded point SDK in the terminal can process the triggered interaction event based on the embedded point type, and the corresponding embedded point event code is generated and reported, so that an additional embedded point configuration network request is not needed to be introduced into the terminal where the user is located.

The embedded point background is embedded into the page in an iframe mode, communication connection is established between the embedded point background and the embedded point SDK through a contract information message (data format of a postMessage interface), and functions such as element embedded point data preview, element screenshot preview, page element circle selection and the like are completed through event information exchange.

FIG. 9 is an interface diagram illustrating a management page buried point configuration in a buried point background, according to an embodiment. As shown in fig. 9, the buried point background named "XX growth" may be used to perform buried point configuration for pages in Web platforms, android platforms, and IOS platforms. Clicking on the "new buried point configuration" control in fig. 9 may enter the create page buried point configuration interface shown in fig. 10, and as shown in fig. 10, configuration names, applications to which the page belongs (i.e., applications to which the page belongs), and presentation page URLs (Uniform Resource Locator, uniform resource locators) may be configured, and provides "exact match" options and "fuzzy match" options for the user to select. In this embodiment, for the application to which the application belongs, application information configuration may be further performed, where the information such as the application name, the platform type where the application is located, the creation time, the application ID, the creator, and the like is configured.

For each page, the embedded point configuration can be performed on the page elements included in the page in the embedded point configuration page corresponding to the page, and the embedded point configuration can be performed on the page elements in a page.

Fig. 11 is a schematic diagram of a management element embedded point page, which is shown in fig. 11, and shows, for the home page of the a-official network, partial embedded point configuration information of the circled (embedded point) page element, where the embedded point configuration information includes information of an event name, an event ID, an event description, a creator, a creation date, and the like. Further, the data analyst may also perform operations, such as deletion operations, editing operations, etc., on the configured page burial points based on the operation options provided by the management element burial point page.

Clicking on the buried point configuration information for any page element in fig. 11 may enter the buried point detail page for the buried point of the page element shown in fig. 12. As shown in fig. 12, in the buried point detail page, buried point configuration information (event name, page address, event type, statistics type, event description, event code), data trend, and buried point screenshot, other information (creator, creation time, last update person, etc.) corresponding to the page element are displayed. Wherein the event code is a buried event code generated for the buried page element.

The embedded point background can also display each page element in the page in an embedded display mode. In the page displayed in the embedded background of the embedded point, the circle selection configuration can be carried out according to the page elements in the displayed page. FIG. 13 illustrates an interface diagram of a visualization circle selected to define page exposure events in which, as shown in FIG. 13, the definition of page names, page addresses, page rules may be performed.

Fig. 14 shows a schematic diagram of displaying page elements in the home page of the a website in an embedded background configuration page, and if the "browse mode" control in the configuration page is clicked, the content in the bold line box in fig. 14 may be displayed, where the content in the bold line box is the content in the home page of the a website. As shown in fig. 14, two modes of displaying page elements in a terminal page are provided in a background of a buried point, namely a buried point mode and a browsing mode, in which each page element in the displayed terminal page can be browsed, and fig. 14 is a display schematic diagram of each page element in the terminal page in the browsing mode.

In the embedded point mode, the data analysis personnel can perform embedded point configuration on the page elements in the displayed terminal page, and the configuration page of the embedded point background also provides an option of highlighting the circled page elements, and if the option of highlighting the circled page elements is selected, the circled page elements are highlighted in the embedded point background. FIG. 15 shows a schematic diagram of highlighting the circled page elements in the A website top page in the buried-point background, as shown in FIG. 15, where the circled page elements in the A website top page are highlighted, thereby facilitating the user to quickly know which page elements are circled page elements. In fig. 15, the page element that is deepened in the bold line box is the highlighted page element.

Based on each page element in the target page displayed by the embedded point background, the page elements in the displayed target page can be visually selected in the interface of the embedded point background. For example, as shown in fig. 16, in the embedded point mode, if the displayed text content is "chinese" page element is clicked, the page element is triggered to be selected by a circle, and the page element can be selected by a circle correspondingly. In this embodiment, for a page element in the top page of the a website displayed in the embedded point background, if a page element is a circled page element, clicking the circled page element may display embedded point detail data for the circled page element shown in fig. 17. As shown in fig. 17, the buried point detail data includes an event name, a page rule, a buried point type, an element data trend, and the like, which correspond to the page element.

The following describes apparatus embodiments of the present application that may be used to perform the methods of the above-described embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments described above in the present application.

Fig. 18 is a block diagram illustrating a buried event code generation apparatus according to an embodiment, which may be configured in the terminal illustrated in fig. 1, as illustrated in fig. 18, and includes: an initial path obtaining module 1810, configured to obtain an initial path of a target page element in a target page, where the initial path uses a page element of a designated element tag as a root node; a conversion module 1820, configured to convert the initial path to obtain a path string; each page element in the initial path is identified through the combination of the corresponding element label and the element serial number; the code generation module 1830 is configured to generate a buried event code corresponding to the target page element according to the path string and the page address corresponding to the target page.

In some embodiments of the present application, the initial path acquisition module 1810 includes: the triggered coordinate information acquisition unit is used for acquiring triggered coordinate information of the target page element; the parent page element searching unit is used for searching the parent page element step by step according to the triggered coordinate information until the element label corresponding to the searched parent page element is a designated element label; the initial path generation unit is used for generating an initial path according to the element information corresponding to the target page element and the element information corresponding to each searched parent page element, wherein the element information at least comprises the element label and the element serial number of the corresponding page element.

In some embodiments of the present application, the element information includes attribute information of the page element; the embedded point event reporting device further comprises:

the embedded point type determining module is used for determining the embedded point type of the target page element according to the attribute information of the target page element;

in this embodiment, the conversion module is further configured to: and converting the initial path according to a conversion mode corresponding to the buried point type to which the target page element belongs, so as to obtain a path character string.

In some embodiments of the present application, the embedded point type includes a first type and a second type, the page element belonging to the first type is a heterogeneous element, and the page element belonging to the second type is a homogeneous element;

In the step of converting the initial path according to the conversion mode corresponding to the buried point type to which the target page element belongs to obtain the path character string, the conversion module is further configured to: if the embedded point type of the target page element is the first type, combining the element serial numbers corresponding to the page elements extracted from the initial path with the corresponding element labels according to the arrangement sequence of the page elements in the initial path to obtain a path character string; if the embedded point type of the target page element is the second type, combining the element serial number corresponding to the page element extracted from the initial path as the intermediate node with the element label corresponding to the page element and the element label corresponding to the extracted target page element according to the arrangement sequence of the page elements in the initial path to obtain a path character string.

In some embodiments of the present application, the first type includes a first subtype, and the page element belonging to the first subtype includes at least two controls; the code generation module 1830 includes: the precoding character string generation unit is used for generating a precoding character string according to the path character string, the page address corresponding to the target page and the additional information corresponding to the target page element, wherein the additional information comprises the buried point type of the target page element; when the buried point type of the target page element is the first subtype, the additional information also comprises text attribute content corresponding to the triggered control in the target page element; and the encryption unit is used for encrypting the pre-coding character string to obtain the embedded point event code corresponding to the target page element.

In some embodiments of the present application, a page element after the root node in the initial path is a page element of a nested multi-layer identical element tag, and the generating device of the buried point event code further includes: the path character string simplifying module is used for simplifying the path character string; in the simplified path character string, the corresponding element information of the page element serving as the root node is omitted, the page element serving as the intermediate node is identified by the corresponding element serial number, and the target page element is identified by the corresponding element label or the corresponding element serial number.

In some embodiments of the present application, the generating device of the buried point event code further includes: and the reporting module is used for reporting the buried point event code.

Fig. 19 is a block diagram of a processing apparatus for a buried point event according to an embodiment, which may be configured in the buried point background shown in fig. 7, as shown in fig. 19, and includes: a buried point configuration information obtaining module 1910, configured to obtain buried point configuration information, where the buried point configuration information includes a buried point event code of a buried point page element, where the buried point event code of the buried point page element is generated according to the method for generating a buried point event code shown in any one of the embodiments above; the storage module 1920 is configured to store the reported embedded point event code into the analysis database if the embedded point event code reported by the terminal is the embedded point event code of the embedded point page element, and when the page element in the displayed page is triggered, the terminal generates and reports a corresponding embedded point event code according to the generation method of the embedded point event code.

In some embodiments of the present application, the processing device for a buried point event further includes:

the configuration module is used for generating corresponding embedded point event codes for the triggered page elements according to the embedded point configuration operation of the elements triggered by the page elements in the first target page in the embedded point element configuration page.

And the buried point configuration information generation module is used for generating buried point configuration information according to the generated buried point event codes.

the appointed display module is used for displaying the embedded point page element in the first target page in an embedded display mode.

and the path character string acquisition module is used for acquiring the path character string of the embedded point page element.

And the path backtracking module is used for carrying out path reconstruction according to the path character string of the embedded point page element to obtain the path information of the embedded point page element.

And the position determining module is used for determining the position of the embedded point page element in the first target page displayed in an embedded manner according to the path information of the embedded point page element.

Fig. 20 shows a schematic diagram of a computer system suitable for use in implementing the electronic device of the embodiments of the present application.

It should be noted that, the computer system 2000 of the electronic device shown in fig. 20 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.

As shown in fig. 20, the computer system 2000 includes a central processing unit (Central Processing Unit, CPU) 2001, which can perform various appropriate actions and processes, such as performing the method in the above-described embodiment, according to a program stored in a Read-Only Memory (ROM) 2002 or a program loaded from a storage section 2008 into a random access Memory (Random Access Memory, RAM) 2003. In the RAM 2003, various programs and data required for the system operation are also stored. The CPU 2001, ROM 2002, and RAM 2003 are connected to each other by a bus 2004. An Input/Output (I/O) interface 2005 is also connected to bus 2004.

The following components are connected to the I/O interface 2005: an input section 2006 including a keyboard, a mouse, and the like; an output portion 2007 including a Cathode Ray Tube (CRT), a liquid crystal display (Liquid Crystal Display, LCD), and the like, a speaker, and the like; a storage section 2008 including a hard disk and the like; and a communication section 2009 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 2009 performs communication processing via a network such as the internet. The drive 2010 is also connected to the I/O interface 2005 as needed. A removable medium 2011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 2010 as needed so that a computer program read out therefrom is mounted into the storage section 2008 as needed.

In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 2009 and/or installed from the removable medium 2011. When executed by a Central Processing Unit (CPU) 2001, the computer program performs the various functions defined in the system of the present application.

It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present application may be implemented by means of software, or may be implemented by means of hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.

As another aspect, the present application also provides a computer-readable storage medium that may be included in the electronic device described in the above embodiments; or may exist alone without being incorporated into the electronic device. The computer-readable storage medium carries computer-readable storage instructions that, when executed by a processor, implement the methods of the above embodiments.

According to an aspect of the present application, there is also provided an electronic device, including: a processor; and a memory having stored thereon computer readable instructions which, when executed by the processor, implement the method of the above embodiments.

It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit, in accordance with embodiments of the present application. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a usb disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a touch terminal, or a network device, etc.) to perform the method according to the embodiments of the present application.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method for generating buried point event codes, comprising:

acquiring an initial path of a target page element in a target page, wherein the initial path takes a page element of a designated element tag as a root node; the element information corresponding to the target page element comprises attribute information of the target page element;

determining the buried point type of the target page element according to the attribute information of the target page element; the embedded point type comprises a first type and a second type, wherein page elements belonging to the first type are heterogeneous elements, and page elements belonging to the second type are homogeneous elements;

if the buried point type of the target page element is a first type, combining an element serial number corresponding to each page element extracted from the initial path with a corresponding element tag according to the arrangement sequence of each page element in the initial path to obtain a path character string;

if the embedded point type of the target page element is the second type, combining an element serial number and a corresponding element label corresponding to the page element which is extracted from the initial path and serves as an intermediate node and an element label corresponding to the extracted target page element according to the arrangement sequence of the page elements in the initial path to obtain a path character string; in the path character string, each page element in the initial path is identified by the combination of the corresponding element label and the element serial number;

And generating a buried point event code corresponding to the target page element according to the path character string and the page address corresponding to the target page.

2. The method of claim 1, wherein the obtaining the initial path of the target page element comprises:

acquiring triggered coordinate information of the target page element;

searching parent page elements step by step according to the triggered coordinate information until the element label corresponding to the searched parent page element is the appointed element label;

generating the initial path according to the element information corresponding to the target page element and the element information corresponding to each searched parent page element, wherein the element information at least comprises an element tag and an element serial number of the corresponding page element.

3. The method of claim 1, wherein the first type comprises a first subtype and wherein the page elements belonging to the first subtype comprise at least two controls;

the generating a buried point event code corresponding to the target page element according to the path character string and the page address corresponding to the target page comprises the following steps:

generating a precoding character string according to the path character string, the page address corresponding to the target page and the additional information corresponding to the target page element, wherein the additional information comprises a buried point type to which the target page element belongs; when the buried point type of the target page element is a first subtype, the additional information further comprises text attribute content corresponding to a triggered control in the target page element;

And encrypting the pre-coding character string to obtain the embedded point event code corresponding to the target page element.

4. The method of claim 3, wherein before generating the pre-encoded string from the path string, the page address corresponding to the target page, and the additional information corresponding to the target page element, the method further comprises:

simplifying the path character string; in the simplified path character string, the corresponding element information of the page element serving as the root node is omitted, the page element serving as the intermediate node is identified by the corresponding element serial number, and the target page element is identified by the corresponding element label or the corresponding element serial number.

5. The method according to any one of claims 1-4, further comprising:

reporting the buried point event code.

6. A method for processing a buried point event, comprising:

acquiring buried point configuration information, wherein the buried point configuration information comprises buried point event codes of buried point page elements, and the buried point event codes of the buried point page elements are generated according to the method of any one of claims 1-5;

If the embedded point event code reported by the terminal is the embedded point event code of the embedded point page element, storing the reported embedded point event code into an analysis database, and when the page element in the displayed page is triggered, generating and reporting a corresponding embedded point event code according to the method as set forth in any one of claims 1-4 by the terminal.

7. The method of claim 6, wherein prior to the obtaining the buried point configuration information, the method further comprises:

in a first target page displayed in an embedded manner in a buried point element configuration page, generating a corresponding buried point event code for a triggered page element according to a method as set forth in any one of claims 1 to 5 according to an element buried point configuration operation triggered on a page element in the first target page;

and generating buried point configuration information according to the generated buried point event code.

8. The method of claim 7, wherein after generating the buried point configuration information from the generated buried point event code, the method further comprises:

9. The method of claim 8, wherein before displaying the embedded point page element in the specified display manner in the first target page displayed in-line, the method further comprises:

acquiring a path character string of the embedded point page element;

carrying out path reconstruction according to the path character strings of the embedded point page elements to obtain path information of the embedded point page elements;

and determining the position of the embedded point page element in the first target page displayed in an embedded manner according to the path information of the embedded point page element.

10. A buried point event code generation apparatus, the apparatus comprising:

the initial path acquisition module is used for acquiring an initial path of a target page element in a target page, wherein the initial path takes a page element of a designated element tag as a root node; the element information corresponding to the target page element comprises attribute information of the target page element;

The conversion module is used for combining the element serial numbers corresponding to the page elements extracted from the initial path and the corresponding element labels according to the arrangement sequence of the page elements in the initial path if the buried point type of the target page element is the first type, so as to obtain a path character string;

11. A point-buried event processing apparatus, comprising:

a buried point configuration information obtaining module, configured to obtain buried point configuration information, where the buried point configuration information includes a buried point event code of a buried point page element, where the buried point event code of the buried point page element is generated according to the method of any one of claims 1 to 5;

The storage module is used for storing the reported buried point event code into the analysis database if the buried point event code reported by the terminal is the buried point event code of the buried point page element, and the terminal generates and reports the corresponding buried point event code according to the method as set forth in any one of claims 1-4 when the page element in the displayed page is triggered.

12. An electronic device, comprising:

a processor;

a memory having stored thereon computer readable instructions which, when executed by the processor, implement the method of any of claims 1 to 9.

13. A computer readable storage medium having computer readable instructions stored thereon, which when executed by a processor, implement the method of any of claims 1 to 9.