CN113515715A

CN113515715A - Generating method, processing method and related equipment of buried point event code

Info

Publication number: CN113515715A
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: 2021-10-19
Anticipated expiration: 2040-10-15
Also published as: CN113515715B

Abstract

The application relates to the technical field of cloud computing, in particular to a generating method, a processing method and related equipment of a buried point event code, wherein the generating method of 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 specified 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 method and the device realize that the occupied bandwidth in the transmission is reduced by reducing the data volume of the buried point event codes.

Description

Generating method, processing method and related equipment of buried point event code

Technical Field

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

Background

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

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

Disclosure of Invention

The application provides a generating method, a processing method and related equipment of a buried point event code, which are used for solving the problems of large data volume of the buried point event and large bandwidth occupation of reported buried point events in the related technology.

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

According to an aspect of an embodiment 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 specified 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 an embodiment 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;

if the buried point event code reported by the terminal is the buried point event code of the buried point page element, the reported buried point event code is stored in an analysis database, and when the page element in the displayed page is triggered, the terminal generates and reports the corresponding buried point event code according to the buried point event code generation method.

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

the system comprises an initial path acquisition module, a path selection module and a path selection module, wherein the initial path acquisition module is used for acquiring an initial path of a target page element in a target page, and the initial path takes a page element of a specified 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 by the combination of the corresponding element label and the element serial number;

and the code generating 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 device for processing 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 embedded point event code generation method;

and the storage module is used for storing the reported embedded point event code into an 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 the terminal generates and reports the corresponding embedded point event code according to the embedded point event code generation method when the page element in the displayed page is triggered.

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

According to an aspect of 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 a method for generating a buried point event code or a method for processing a buried point event as above.

In the scheme of the application, the initial path is converted into the path character string, so that in the path character string, the attribute information of each page element in the initial path is filtered, 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 that of the initial path, and the simplification of the initial path is realized. Correspondingly, compared with the buried point event code generated according to the initial path, the data volume of the buried point event code generated by simplifying the obtained path character string through the path is greatly reduced, so that in the process of reporting the buried point event code, as the data volume of the buried point event code is reduced, the network bandwidth occupied by transmitting the buried point event code is correspondingly reduced, and the utilization rate of the network is improved.

In addition, the attribute information of the page element is related to the content of the page, and the path character string does not include the attribute information of the page element, so that the independence of the path character string and the content of the page is realized, and the path character string only reflects the structural information of the path corresponding to the target page element. If the attribute information of the page element in the page changes, the path character string corresponding to 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 the matching and processing of the embedded point event can be still performed 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 present application and together with the description, serve to explain the principles of the application. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:

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

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

FIG. 3 illustrates a partial page view of a page;

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

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

FIG. 6 is a schematic diagram illustrating 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 based on the application scenario of the embodiment of the present application shown in FIG. 6;

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

FIG. 9 is a schematic diagram of an interface for managing page burial point configuration in the burial point background according to an embodiment of the application;

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

FIG. 11 is a schematic diagram illustrating a management element landed page according to one embodiment of the present application;

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

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

FIG. 14 is a schematic diagram illustrating an embodiment of the present application for displaying page elements in a home page of website A in an embedded manner in a configuration page of a background of a buried point;

FIG. 15 is a schematic diagram illustrating highlighting of a selected page element in a website A home page in a buried site background according to an embodiment of the present application;

FIG. 16 is a diagram illustrating a page element being circled according to one embodiment of the present application;

FIG. 17 is a schematic diagram illustrating a display of buried point detail data for circled page elements, according to an embodiment of the present application;

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

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

fig. 20 is a schematic structural diagram illustrating a computer system suitable for implementing an electronic device according to an embodiment of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different 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 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 application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the application.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to 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 actual execution sequence may be changed according to the actual situation.

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 can have stronger decision-making power, insight discovery power and flow optimization capability only by a new processing mode. With the advent of the cloud era, big data has attracted more and more attention, and the big data needs special technology to effectively process a large amount of data within a tolerance elapsed time. The method is suitable for the technology of big data, and comprises a large-scale parallel processing database, data mining, a distributed file system, a distributed database, a cloud computing platform, the Internet and an extensible storage system.

In the related art, in order to implement data mining, data collection is generally performed through a point burying technology, for example, by performing point burying on page elements in a page, a triggering condition that the page elements in the page are triggered by a user is tracked. Specifically, by embedding points into page elements in a page, when the page elements are triggered by a user, a terminal reports a point embedding event to a server, so that statistics of user operation behaviors in the page is realized. And the server side performs data mining and analysis by analyzing a large number of collected buried point events, and the collected buried point events are used 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 solution of the embodiments of the present application can be applied.

As shown in fig. 1, the system architecture may include a terminal 110 and a server 120, the terminal 110 and the server 120 communicate with each other through a wired or wireless network, and the terminal 110 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, or the like, which is not limited in this respect.

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 an implementation. For example, the server 120 may be a server cluster composed of a plurality of servers.

The terminal 110 is configured to report a point burying event. The terminal 110 may display a page, where page elements in the page may be embedded, and if the page elements of the embedded points are triggered by a user, generate an embedded point event code according to the scheme of the present application and report the embedded point event code. The page displayed in the terminal may be a website page or an application page, and is not limited in this respect.

In some embodiments of the present application, the page may be embedded with the page elements by monitoring the code, and may also be embedded with the page elements by a Software Development Kit (SDK) integrated in the application.

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

In the terminal, if more page elements needing user behavior tracking are needed, the triggered page elements are required to generate a point burying event and report the point burying event to the server, so that the data transmission amount is extremely large, and the occupied bandwidth is more, therefore, in order to reduce the data transmission amount in the reporting process of the point burying event and improve the utilization rate of a network in the reporting process of the point burying event, the scheme of the application is provided.

The implementation details of the technical solution of the embodiment of the present application are set forth in detail below:

fig. 2 is a flowchart illustrating a reporting method of a buried point event according to an embodiment of the present application, where the reporting method of the buried point event can be executed by the terminal shown in fig. 1. Referring to fig. 2, the reporting method of the buried point 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, where the initial path takes a page element of the specified element tag as a root node.

For ease of understanding, the terms are used here for the purpose of illustration: the target page element does not refer to a certain page element, but refers to a page element capable of interacting with a buried point, such as 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 pull-down operation, and the like in a page. Similarly, a target page does not refer to a page, but rather refers to a page having page elements with buried points.

And collecting the control behavior data of the user in the page by embedding 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 the following steps are executed to generate a buried point event code for the triggered target page element, and automatically report the buried point event code, so as to record that the target page element is triggered by a user.

The buried point of the target page element can be a buried point based on the configuration information or a full buried point. The point burying based on the configuration information means that if the configuration information indicates to bury a certain page element, the page element is taken as a target page element, and the page element indicated by the configuration information is triggered and monitored. The full-embedded point is that any page element in a page is used as a monitored object, and if any page element is monitored to be triggered, an embedded point event is reported for the page element.

In some embodiments of the present application, a buried point SDK (Software Development Kit) is integrated in a target page, and a trigger event of any target page element in the target page is monitored by the buried point SDK, for example, a click event, a page exposure event, and the like triggered by a user are monitored by the buried point SDK, and a processing function is called when the event is triggered, and a corresponding buried point event code is calculated according to the method of the present application and 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 triggering of a target page element in a target page is performed on the basis that the target page is displayed, so that the page exposure event of the target page is monitored, that is, the target page is displayed. The page referred to in this application is described by a page document whose structure includes two major parts, a header part and a body part, and the body part of the page document determines the content displayed in the page, wherein the body part is the content under the body tag. The page document may be an html (Hyper Text Mark-up Language) document.

The initial path of the target page element refers to an ordered set of elements from the target page element to the page root element in the target page. The page root element in the target page is a page element serving as a root node. In a specific embodiment, the page root element (which is a page element of a root node) may be specified according to actual needs, that is, the page element of the specified element tag is used as the root node in the initial path, so as to facilitate subsequent buried point event encoding.

For example, if the entirety of the html document is defined by html tags in the html document, the html tags can be used as the specified element tags in the initial path of the target page elements. For another example, in the html document, the body part determines the content displayed in the page, and the target page element is an interactive page element in the page, so in the page document, the element information corresponding to the page element is located in the content under the body tag, in other words, the triggered target page element is a sub-page element under the body tag, and of course, it may be a first-level sub-page element or a deeper-level sub-page element. Therefore, the body tag can be used as a specified element tag, and particularly in the html document, the body tag is embedded under the html tag.

If the html tag is used as the designated element tag, the initial path of a target page element is as follows: [ html/body/div [1]/form [1] [ @ name ═ f "]/span [1] [ @ class ═ bt" ]/input [1] [ @ id ═ su "]. Html, body, div, form, span, and input in the initial path are the element tags of the corresponding page elements. In the initial path, the last page element, i.e., the element tag is an "input" page element, and is a target page element. The content in the square bracket behind the element tag is element information of the located page element, 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 above initial path, [ @ class ═ bt" ] indicates the class attribute of the page element whose element tag is "span" in the above initial path, and [ @ ID ═ su "] indicates the ID of the page element whose element tag is" input "in the above initial path. Wherein, the number 1 in the parentheses behind the page element with the element label of "form" is the element serial number corresponding to the page element. Similarly, the number in the parentheses behind the corresponding element tag of other page elements is also the element number.

For the listed target page elements, if the body label is the designated element label, the initial path of the target page element is: [ 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 in the html tag in the page document, when the body tag is used as the specified page element, compared with when the html tag is used as the specified element, the initial path of the target page element is shortened, and correspondingly, the amount of data of the subsequently obtained embedded point event code is correspondingly reduced, and the transmission amount of the data is correspondingly reduced in the embedded point event reporting process.

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

The initial path of the target page element includes element information of each involved page element, where the element information of the page element includes not only an element tag and an element number of the page element, but also possibly attribute information of the page element, where the attribute information may be a text attribute, an Identification (ID) attribute, a class (class) attribute, other custom attributes, and the like, and the attribute information may further include size information of the page element in the target page, such as a height, a width, and the like of the page element.

In a page, one or more child page elements may exist 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 div tag page elements under the body tag, then the body/div: 5 denotes the 5 th div page element under the body label.

Step 220 is equivalent to converting the initial path to a structure-oriented "element label: element number "path form, that is, each page element in the initial path passes through" element tag: and identifying the element serial number to obtain the path character string.

It can be understood that if at a level page element, there is only one page element, and there is no sibling page element at the same level as the page element, the element number of the page element is null. For example, in an html document, the body tag does not have the same level page elements, and therefore, the element number of the page element corresponding to the body tag is empty.

Continuing with the example that 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, so as to filter out the attribute information of each page element in the initial path, where the obtained path character 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 the combination of an element tag and an element serial number. Therefore, the path character string without the attribute information of the page element is obtained by converting the initial path, compared with the initial path, the character length of the obtained path character string is greatly shortened, and the data volume corresponding to the corresponding path character string is also greatly reduced compared with the data volume of the initial path.

Fig. 3 shows a partial page diagram in a page, and as shown in fig. 3, the page element corresponding to the area where the border 1 in fig. 3 is the page element whose 5 th element tag is div under the body tag (the page element may be represented as div: 5 according to the form of "element tag: element number"); the page element corresponding to the area where the frame 2 is located is a page element whose element tag 1 under the page element corresponding to the frame 1 is div (the page element may be represented as div: 1 according to the form of "element tag: element serial number"). The page element corresponding to the area where the frame 3 is located is a page element whose element tag 1 under the page element corresponding to the frame 2 is div (the page element may be represented as div: 1 according to the form of "element tag: element serial number").

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

and 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 application, the path character string and the page address corresponding to the target page may be spliced and combined to obtain a pre-coding character string, and then the obtained pre-coding character string is encoded according to an encoding algorithm to obtain a buried point event code. And coding the path character string and the page address corresponding to the target page, which is equivalent to encrypting the path character string and the page address corresponding to the target page.

The encoding Algorithm may be MD5 Algorithm (Message-Digest Algorithm 5). Of course, the encoding Algorithm is not limited to the MD5 Algorithm, and may be an Algorithm such as SHA (Secure Hash Algorithm), MAC (Message Authentication Code Algorithm), and 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 the MD5 algorithm is fixed, so that the MD5 algorithm can convert a combined character string with indefinite length into a buried point event code with definite length, the storage of the buried point event code is facilitated, and the problem that the overlong combined character string cannot be effectively formatted and stored can be prevented. The path character string is used for indicating the path of the target page element in the target page, and therefore 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, so that the embedded point event code can not only reflect the target page where the target page element is located, but also further reflect 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: and 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 embedded point event codes, for example, performs user operation behavior analysis, and counts the number of times that each page element is triggered. And reporting the embedded point event code to realize the reporting of the embedded point event.

In some embodiments of the application, a terminal deploys a reporting queue, after a buried point event code is obtained, the buried point event code is added to the reporting queue, and when the buried point event code in the reporting queue meets a sending condition, the buried point event code is extracted from the reporting queue and sent to a server.

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

In the scheme of the application, the initial path is converted into the path character string, so that in the path character string, the attribute information of each page element in the initial path is filtered, 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 that of the initial path, and the simplification of the initial path is realized. Compared with the buried point event code generated according to the initial path, the data volume of the buried point event code generated by the path character string obtained by simplifying the path is greatly reduced, so that in the process of reporting the buried point event code, the network bandwidth occupied by transmitting the buried point event code is correspondingly reduced due to the reduction of the data volume of the buried point event code, and the utilization rate of the network is improved.

In the application scenario of the full-buried point, all page elements in a page are required to be used as buried point objects and correspondingly subjected to buried point event coding reporting, the data volume to be transmitted is huge, and the initial path is converted according to the method of the application, and the buried point event coding and reporting are correspondingly generated, so that the data transmission volume can be greatly reduced.

In addition, the attribute information of the page element is related to the content of the page, and the path character string does not include the attribute information of the page element, so that the independence of the path character string and the content of the page is realized, and the path character string only reflects the structural information of the path corresponding to the target page element.

In the related art, more and more online projects are constructed by using a component style processing technology such as CSS Modules, and in each construction of a project, a class (class) name completely different from a previous version may be regenerated, which may cause a class attribute of a page element to change, and in this case, the initial path is converted according to the process of step 220, which may ensure that even if the class attribute of each page element involved in the initial path of the target page element changes, 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 kept unchanged.

In summary, when the page content changes due to the change of the attribute information of the page element in the page, because the path character string of the target page element does not carry the attribute information of each page element, the path character string corresponding to the target page element remains unchanged, and thus, it can be ensured that the matching and processing of the embedded point event 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 comprises:

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

The triggered coordinate information is used to indicate a coordinate of a 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 a clicked coordinate on the target page element.

And step 420, gradually searching the parent page element according to the triggered coordinate information until the element tag corresponding to the searched parent page element is the specified element tag.

The parent page element refers to a previous page element of the page element that needs to be backtracked currently, that is, the parent page element is relative to the current page element. In step 420, the target page element is used as a basis to perform backtracking step by step and search the corresponding parent page element.

In some embodiments of the present application, the document elementary frompoint interface is configured to obtain all page elements at the specified coordinate within the current viewport, so that the target page element may be obtained according to the triggered coordinate information through the document elementary frompoint interface, and then, with the target page element as a base point, parent page element search is performed step by step until an element tag of the found parent page element is a specified element tag.

For example, if the specified 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 page element with the found element tag being 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 includes an element tag, an element sequence number and attribute information of the page element, and the attribute information includes, for example, the text attribute, the identification attribute, the class attribute, the 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 found parent page element, where the element information at least includes an element tag and an element serial number of the corresponding page element.

And combining the element information corresponding to each searched page element and the element information corresponding to the target page element according to the corresponding upper and lower level relations to obtain the initial path.

Through the process of

steps

410 and 430, the acquisition of the initial path corresponding to the target page element is realized.

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 type of the embedded point to which the target page element belongs 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 type of the embedded point to which the target page element belongs to obtain a path character string.

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

In some embodiments of the present application, the buried point types include a first type and a second type, the page elements attributed to the first type are heterogeneous elements, and the page elements attributed to the second type are homogeneous elements.

Converting the initial path according to a conversion mode corresponding to the type of the embedded point to which the target page element belongs to obtain a path character string, wherein the step comprises the following steps of:

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

And if the embedded point type of the target page element is the second type, combining the element serial number and the element tag corresponding to the page element extracted from the initial path as the intermediate node and the element tag 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, such as unordered list item elements, cell elements, etc. in a page. On the contrary, if the page elements having the sequence relationship with each other are under the same level parent page element, the page elements are heterogeneous elements. For example, in fig. 3, there is an order relationship between the page element corresponding to the area where the frame 1 is located and other div elements under the body tag, and then the page element corresponding to the area where the frame 1 is located is an inhomogeneous element.

For homogeneous elements, it is often necessary to count the aggregation results of all page elements at the same level, and it is not significant to count each homogeneous element separately. Therefore, in this embodiment, if the type of the buried point to which the target page element belongs is the second type (that is, the target page element is a homogeneous element), then in the path 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, then the path string corresponding to other homogeneous elements of the same level as the target page element is the same as the path 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 the heterogeneous elements, in the path character string, each page element is identified by the corresponding element label and the element serial number.

Continuing with the example corresponding to fig. 3, taking the page element corresponding to the area where the frame 3 in fig. 3 is located as a 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 page elements belonging to the first subtype include at least two controls therein; in this embodiment, step 230 includes: generating a pre-coding 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 embedded point type of the target page element; when the type of the embedded point to which the target page element belongs is a first subtype, the additional information further comprises text attribute content corresponding to the triggered control in the target page element; and encrypting the pre-coding character string to obtain a buried point event code corresponding to the target page element.

For a page element comprising at least two controls, a user triggers different controls in the page element to perform different operations, and as the controls are located in the same page element, if the controls are not distinguished, the embedded point event codes triggering different controls in the page element are aggregated together.

Therefore, when the embedded point type of the target page element is the first subtype, in order to facilitate the service end to distinguish different controls in the same target page element, the text attribute content corresponding to the triggered control in the target page element is added to the attachment information, and the text attribute content corresponding to the controlled element is used as part of information of the embedded point event code, 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 "register" and "login", the text attribute content corresponding to the "register" control is used to indicate that the control is used to trigger the register operation, and the text attribute content corresponding to the "login" control is used to indicate that the control is used to trigger the login operation.

In some embodiments of the present application, the first type further comprises a second subtype, the number of controls included in page elements belonging to the second subtype being no more than one; for page elements that include no more than one control's data, its additional information may not include the text property content of the triggered control, since no distinction of controls is required.

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

In some embodiments of the present application, in this embodiment, before the step of generating the pre-coding 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, wherein in the simplified path character string, element information corresponding to the page element serving as a root node is omitted, the page element serving as an 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; 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 pre-coding character string.

In this embodiment, in order to further reduce the data transmission amount, the path character string is simplified, so that in the simplified path character string, the element information corresponding to the page element as the root node is omitted, the page element as the intermediate node is identified by the corresponding element number, and the target page element is identified by the corresponding element tag or the corresponding element number. For a page element identified by an element sequence number, the element sequence number can identify that the page element is the second child element of the page element at the previous level, and therefore, since the page element as the root node in the initial path is known, the page elements at the next level can be determined by taking the page element as the root node as the parent element.

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

Continuing with the example corresponding to fig. 3, if the page element corresponding to the area where the border 3 in fig. 3 is located is taken as the target page element, 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 first type, the path character string obtained by simplifying the path character string corresponding to the target page element is '/5/1/1'; if the embedded point type of the target page element is the second type, the simplified path character string corresponding to the target page element is "/5/1/div".

In this embodiment, in the case that the page element after the root node in the initial path is a nested page element with multiple layers of the same element tags, the initial path character string is simplified, so that the length of the path character string after simplification is greatly shortened relative to the length of the path character string before simplification, and the data amount is correspondingly reduced, in the above example, the target path character string is "/5/1/1" as compared with the path character string "body/div: 5/div: 1/div: 1 ", the data amount of the target path character string is reduced by 84%.

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 under the condition that the page element behind the root node in the initial path is a nested multi-layer page element with the same element label; of course, if the page elements after the root node in the initial path are not the nested page elements with multiple layers of the same element tags (in other words, the page elements after the root node in the initial path include 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 elements according to a preset filtering rule.

For a page element providing any input by a user, for example, a word input box for the user to input a word to be translated, a word query input box, etc., since the page element is provided for the user to input arbitrarily, if the text content input in the page element is added to the additional information and the page element is subjected to the buried point event code reporting, under the condition that the input content is different, the buried point event codes generated for the page element are correspondingly different, which may cause the obtained buried point event codes to be completely dispersed, and further may cause data to be unable to be aggregated.

Therefore, in order to avoid this situation, a filtering rule may be preset to filter the page elements for content input, that is, the buried 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 according to element information of the page element. And if the element information of the page element comprises an input tag or a text-area tag, determining that the page element is a page element for inputting content.

In some embodiments of the present application, the preset filtering rule defines that the page element to be filtered out may be an element for content input of the target page element itself, a page element for content input of the child page elements, and a page element for content input of the sibling page elements.

For example, if the initial path is "/html/body/div [1]/form [1] [ @ name ═ f" ]/span [1] [ @ class ═ bt "]/input [1] [ @ id ═ su" ] "target page element, and the element label of the target page element is" input ", which indicates that the target page element is an element for content input, then according to the filtering rule, the target page element with the element label of" input "is a page element that needs to be filtered out, and thus, a buried point event code does not need to be generated for the target page element.

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

Under the 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 having the same level as the target page element) are also required to be acquired, and 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 determined according to the acquired element information. Of course, in other embodiments, a filtering rule may be set according to actual needs to filter out other page elements that do not need to generate a buried point event code, which is not specifically limited herein.

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

Step 510, acquiring buried point configuration information, where the buried point configuration information includes 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.

In some embodiments of the present application, the buried point configuration information is generated by performing buried point on the page elements, and the generated buried point configuration information indicates which page elements whose buried point event encoding is required.

In some embodiments of the present application, prior to step 510, the method further comprises: in a first target page which is embedded and displayed in a buried point element configuration page, generating a corresponding buried point event code for a triggered page element according to a buried point configuration operation triggered by the page element in the first target page and a 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 the buried point element configuration, that is, a buried point element configuration page is provided, in which an analyst can perform the buried point on a page element.

The first target page does not refer to a certain page, but refers to a page needing page element embedding. In this embodiment, the first target page is displayed in-line in the buried point element configuration page. The first target page can be displayed in the embedded point element configuration page in an iframe mode in an embedded mode. The first target page is embedded and displayed in the embedded point element configuration page, so that analysts can conveniently visually select the page elements in the first target page to embed points of the selected page elements, and the selected page elements are the embedded point page elements.

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

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

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

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

In this embodiment, the terminal reports the buried-point event code, and the server filters the buried-point event code reported by the terminal according to the buried-point configuration information, that is, if the buried-point event code reported by the terminal is the buried-point event code of the page element of the buried point indicated by the buried-point configuration information, the buried-point event code reported by the terminal is stored in the analysis database, so that the terminal can generate the buried-point event code for the triggered page element and report the buried-point event code when any page element in the displayed page is triggered without issuing the buried-point configuration information to the terminal first, and the server filters the buried-point event code reported by the terminal according to the buried-point configuration information, which is equivalent to fully burying the page element in the terminal. Moreover, since the terminal is a full-buried point of the middle-pair page element, when the buried point configuration information changes, the corresponding buried point event code can be screened out from the buried point event codes reported by the terminal according to the changed buried point configuration information.

In some embodiments of the application, a temporary storage database is further arranged 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 storage database, so that an analyst can extract the embedded point event code of the required page element from the temporary storage 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 page elements of the buried points in the embedded displayed first target page according to a specified display mode.

The designated display mode may be a designated color, or a set mark may be added to the page element of the buried point, and the like, and is not particularly limited herein. In a specific embodiment, the designated display mode may be highlighting, that is, the embedded-point page element may be highlighted in the first target page displayed in an embedded manner.

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

In some embodiments of the 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 specified 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 specified 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 buried point page element in the specified display mode, the location of the buried point page element in the displayed first target page also needs to be determined.

In some embodiments of the present application, before displaying, in the first target page displayed in-line, the page element with the embedded point in the specified display manner, the method further includes: acquiring a path character string of a buried point page element; performing path reconstruction according to the path character string of the buried point page element to obtain path information of the buried point page element; and determining the position of the buried point page element in the embedded displayed first target page according to the path information of the buried point page element.

In some embodiments of the present application, the obtained path character string of the buried 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 to obtain the path character string of the target page element. Therefore, the terminal can report the obtained path character string to the server side, and store the path character string of the reported page element and the embedded point event code of the page element in a correlation manner. Therefore, when the server determines that the buried point event code reported by the terminal is the buried point event code of the buried point page element, the path character string of the buried point page element can be correspondingly acquired.

In other embodiments of the present application, the obtained path character string of the page element to be buried may also be obtained during the process of performing buried point configuration on the page element. As described above, in the process of performing embedded point configuration on page elements in a first target page that is displayed in an embedded manner in the embedded point element configuration page, when a user selects page elements in the displayed first target page, an initial path of the page elements is correspondingly obtained, and a point embedded event code of the selected page elements is generated according to the generation method of the point embedded event code, so that the selected page elements are the embedded point page elements. In the process, the 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. Therefore, in this embodiment, the path character string of the circled page element obtained in the process may be stored in association with the generated buried point event code, for example, the path character string may be stored in association with the buried point event code as a part of the buried point 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 character string obtained by using the end configured by the buried point as the buried point page element may be correspondingly obtained.

In some embodiments of the present application, the step of performing path reconstruction according to the path character string of the buried point page element to obtain the path information of the buried point page element includes: converting the element label corresponding to each page element in the path character string and the corresponding element serial number into a corresponding selector identifier; and performing path reconstruction according to the selector identifier corresponding to each page element to obtain path information of the page element of the buried point.

It is worth mentioning 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 a page element may be obtained in the form of "nth-child (n)", where n in "child (n)", is an element number, through an element number corresponding to each page element in the path string. For example, the path string "body/div: 5/div: 1/div: 1 "in," div: the selector identification for the page element of 5 "may be" div: nth-child (5) ".

Continuing with the example in FIG. 3 above, if the path string is "body/div: 5/div: 1/div: 1 ", then by performing path reconstruction, the obtained path information may be" body div: nth-child (5) div: nth-child (1) div: nth-child (1) "; if the page elements after the root node in the initial path are nested page elements with multiple layers of same element tags, the path information can be further simplified into "body: nth-child (5): nth-child (1): nth-child (1) ".

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

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

The following describes a method for generating a buried point event code and a method for processing a buried point event according to the present application with reference to a specific embodiment.

Fig. 6 shows an application scenario diagram in the present embodiment, and as shown in fig. 6, 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.

A configuration page is provided in the embedded point background, and a data analyst can select page elements in the embedded and displayed first target page in the configuration page (the selected page elements are also called embedded point page elements), further generate embedded point configuration information corresponding to the selected page elements (the embedded point configuration information can be called the embedded point configuration information), and upload the embedded point configuration information 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 embedded and displayed 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 the embedded point configuration information aiming at the selected page element is further generated according to the generated embedded point event code. The buried point configuration information can be issued to the analysis end.

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

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

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

As shown in fig. 7, the analysis end establishes communication connection with the terminal and the background of the embedded point. The analysis end is provided with a data reporting service, an application service and a data analysis service, and is provided with 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 selection configuration information reported by the embedded point background and providing the stored selection configuration information to the embedded point background, and the application service stores the selection configuration information into the application configuration database after receiving the reported selection configuration information.

As shown in fig. 7, in the terminal, if the user opens the page integrated with the embedded point SDK, the embedded point event code is reported through the following steps 721-: in step 721, the embedded point SDK monitors events such as page clicking, exposure and the like, and in step 722, it is monitored that the page element is triggered by the user; 723, generating a buried point event code by the buried point SDK; and 724, adding the buried point event codes to a reporting queue, and delaying reporting. The embedded point SDK calls a processing function, calculates corresponding embedded point event codes and adds the embedded point event codes into 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 embedded display of the first target page in the embedded point background is realized through the following steps 711 and 714: step 711, detecting that the embedded point SDK is in an embedded point background use scene, and establishing connection with the embedded point background; step 712, the background of the embedded point is in a browsing state, and the embedded point SDK intercepts the jump behavior in the page; 713, the embedded point background is in a circled selection state, and the embedded point SDK intercepts the clicking behavior of the user and transmits the information of the clicked page element to the embedded point background; 714, continuously communicating the embedded point background with the embedded point SDK to obtain element information and provide a visual circled configuration page; the first target page is embedded and displayed in the configuration page, and therefore a user can conveniently visually select page elements in the embedded and displayed first target page.

In the buried point background, a data analyst can log in the buried point background and can configure the page needing to be subjected to buried point configuration. Data analysts can communicate with the embedded point SDK in the form of appointed data by using a mouse click mode through the embedded point background. And the embedded point background provides a visual configuration page for page element selection, embedded point configuration information of the selected page elements is generated by selecting the page elements in a circle mode, and the generated embedded point configuration information is sent to the application service, completes event registration and is stored in the application configuration database.

In the analysis end, when the circled configuration information is in effect for the first time, the application service performs batch processing on the embedded point event codes in the temporary storage database in a certain period, compares the embedded point configuration information stored by a data analysis personnel with the embedded point event codes to be processed, and transfers the embedded point event codes corresponding to the embedded point page elements indicated by the embedded point configuration information in the temporary storage database to the analysis database for persistent storage. The data analysis service can then have immediate access to the data in the analysis database. When the circled 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 an analysis database in second-level delay, and time delay caused by a batch processing period can be reduced.

Fig. 8 is a flowchart illustrating the operation of a 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 indicates that the embedded point SDK runs in the terminal where the user is located, the embedded point SDK executes the following steps 801-:

step 801, reporting a page event and monitoring a page closing event;

step 802, monitoring click events for page elements; if a click event is monitored, go to step 803;

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

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

step 805, judging whether a content acquisition condition is met; if yes, go to step 806; if not, go to step 807;

at step 806, a pre-encoded string is generated. Specifically, a pre-coding 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 encrypts and adds the encrypted data to a 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 to a reporting queue.

Step 808, delaying reporting of a buried point event code;

step 809, judging whether the application program where the page is located finishes running; if yes, go to step 810, and if not, go back to step 802.

Step 810, reporting a page close event.

After the embedded point SDK is started, if the embedded point SDK is in an embedded point background environment, requesting an embedded point background to establish circled connection; after the circle selection connection is successful, if the background of the embedded point is in a circle selection state, executing the following steps 11-817:

step 811, acquiring circle selection configuration information;

step 812, backtracking the page element path and displaying the circled elements; specifically, path character strings of the circled page elements are traced back to determine path information of the corresponding page elements, then the positions of the circled page elements in the page are determined according to the path information, and the circled page elements are highlighted.

Step 813, detecting whether there are elements that are not backtracked; if not, go to step 814; if yes, go to step 814-1: performing frame popping prompt on a background of the buried point;

and 814, transmitting the basic information of the page, such as the height and the width of the page, to the buried point background.

Step 815, monitoring click events in the configuration page and preventing default click behaviors of the page; if a click event in the configuration page is monitored, go to step 816; if the click event in the configuration page is not monitored, continuing to execute step 815;

and 816, displaying the clicked and selected page element, and transmitting element information of the selected page element, such as an element path character string, an element screenshot and the like, to the buried point background for previewing.

817, detecting whether the circling selection is exited or not; if yes, detecting whether the selection is in a circling selection state; if not, go back to step 815.

After the circle selection connection is successful, if the embedded background is not in the circle selection state, then step 818-:

step 818, the page in the terminal is loaded, specifically, the page is displayed in an iframe manner in an embedded manner.

Step 819, monitor page jump events and prevent page jump behavior;

and 820, detecting whether to exit the background, if not, returning to the step 818, and if so, ending.

In summary, the work flow of the embedded point SDK is related to the work environment where the embedded point SDK is located. When the embedded point SDK is in a page of the terminal, the embedded point SDK reports page exposure event data by default, monitors a global click event of a user, calculates embedded point event codes of various types when the user clicks, and delays reporting; when the embedded point SDK is in the embedded point background environment, the acquisition of the page elements of the circled part can be delayed, and additional work tasks are executed to provide visual circled functions, such as interception of click events, tracing of circled elements, highlight of circled elements and the like.

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

In the scheme, because the embedded point configuration does not need to be performed in the background, the embedded point SDK in the terminal can process the triggered interaction event based on the embedded point type, generate the corresponding embedded point event code and report the embedded point event code, and therefore, an additional embedded point configuration network request does not need to be introduced into the terminal where the user is located.

The embedded point background embeds the page in an iframe mode, establishes communication connection with the embedded point SDK through an appointed information message (data format of a postMessage interface), and completes functions of element embedded point data preview, element screenshot preview, page element selection and the like through event information exchange.

FIG. 9 is a diagram illustrating an interface for managing page burial point configurations in the burial point background, according to an embodiment. As shown in fig. 9, the buried point background named "XX grow" may be used for performing buried point configuration on pages in a Web platform, an Android platform, and an IOS platform. Clicking the control of "new buried point configuration" in fig. 9 may enter the page buried point configuration creation interface shown in fig. 10, and as shown in fig. 10, configuration names, applications (i.e., applications to which a page belongs), and URL (Uniform Resource Locator) configurations of display pages may be performed, and an "accurate matching" option and a "fuzzy matching" option are provided for a user to select. In this embodiment, for the application, application information configuration may be further performed, and information such as the application name, the platform type of the application, the creation time, the application ID, and the creator may be configured.

For each page, the page elements included in the page may be subjected to embedded point configuration in the embedded point configuration page corresponding to the page, and the page elements subjected to embedded point configuration in one page may be managed.

Fig. 11 is a schematic diagram illustrating a management element site page according to an embodiment, and as shown in fig. 11, partial site configuration information of a circled (site-embedded) page element is displayed for an a-official website homepage, wherein the site configuration information includes information such as an event name, an event ID, an event description, a creator, and a creation date. Further, the data analyst can also perform operations on the configured page burial points, such as deletion operations, editing operations, and the like, 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 details page for the page element buried point shown in fig. 12. As shown in fig. 12, in the buried point detail page, the buried point configuration information (event name, page address, event type, statistical type, event description, event code), data trend, and the buried point screenshot corresponding to the page element, other information (creator, creation time, last update person, etc.) are displayed. Wherein the event code is a buried point event code generated for the buried point page element.

The embedded point background can also display each page element in the page according to the embedded display mode of the page. In the page embedded and displayed in the embedded point background, the circle selection configuration can be carried out according to the page elements in the displayed page. Fig. 13 is a schematic diagram illustrating an interface for visually selecting a defined page exposure event, and as shown in fig. 13, definition of a page name, a page address, and a page rule may be performed in the interface for defining a page exposure event.

Fig. 14 is a schematic diagram illustrating that page elements in the home page of the website a are displayed in a configuration page of the background of the buried point in an embedded manner, and if a control "browse mode" in the configuration page is clicked, the contents in a thick-line box in fig. 14, which are the contents in the home page of the website a, may be displayed. As shown in fig. 14, two display modes for performing page elements in a terminal page are provided in a page of a background of a buried point, which are a buried point mode and a browsing mode, respectively, and in the browsing mode, each page element in the displayed terminal page can be browsed, where fig. 14 is a schematic display diagram of each page element in the terminal page in the browsing mode.

In the embedded point mode, a data analyst can perform embedded point configuration on page elements in a displayed terminal page, and a configuration page of an 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 is a schematic diagram illustrating highlighted circled page elements in the home page of the a website in the background of the buried point, as shown in fig. 15, the circled page elements in the home page of the a website are highlighted in the page of the background of the buried point, so that the user can quickly know which page elements are circled page elements. In fig. 15, the page elements that are darkened within the bold line boxes are highlighted page elements.

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, for a page element in a home page of a website a displayed in a background of a buried point, as shown in fig. 16, in the buried point mode, if a page element of "chinese" displayed text content is clicked, that is, the page element triggers a circling operation, the page element may be correspondingly circled. In this embodiment, for a page element in the first page of the website a displayed in the site burying background, if a page element is a circled page element, the circled page element is clicked, so that the site burying detail data for the circled page element shown in fig. 17 can be displayed. As shown in fig. 17, the buried point detail data includes an event name, a page rule, a buried point type, and an element data trend, etc. corresponding to the page element.

Embodiments of the apparatus of the present application are described below, which may be used to perform the methods of the above-described embodiments of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the above-described embodiments of the method of the present application.

Fig. 18 is a block diagram of an apparatus for generating a buried point event code according to an embodiment, which may be disposed in the terminal shown in fig. 1, and as shown in fig. 18, the apparatus for generating a buried point event code 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 takes a page element of a specified element tag as a root node; a conversion module 1820, configured to convert the initial path to obtain a 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; the code generating module 1830 is configured to generate a buried event code corresponding to a target page element according to the path character string and the page address corresponding to the target page.

In some embodiments of the present application, the initial path obtaining module 1810 includes: the triggered coordinate information acquisition unit is used for acquiring triggered coordinate information of the target page element; the father page element searching unit is used for searching father page elements step by step according to the triggered coordinate information until the element tag corresponding to the searched father page element is a specified element tag; and the initial path generating 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 found father page element, wherein the element information at least comprises an element tag and an 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 device for reporting the embedded point event 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 type of the embedded point to which the target page element belongs to obtain a path character string.

In some embodiments of the present application, the buried point types include a first type and a second type, the page elements attributed to the first type are heterogeneous elements, and the page elements attributed to the second type are homogeneous elements;

in the step of converting the initial path according to the conversion mode corresponding to the type of the embedded point 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 number corresponding to each page element extracted from the initial path with the corresponding element tag according to the arrangement sequence of each page element in the initial path to obtain a path character string; and if the embedded point type of the target page element is the second type, combining the element serial number and the element tag corresponding to the page element extracted from the initial path as the intermediate node and the element tag 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 at least two controls are included in page elements belonging to the first subtype; the code generation module 1830 includes: the pre-coding character string generating unit is used for generating a pre-coding 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 embedded point type of the target page element; when the type of the embedded point to which the target page element belongs is a first subtype, the additional information further 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 buried point event code corresponding to the target page element.

In some embodiments of the present application, the page elements after the root node in the initial path are nested page elements of multiple layers of the same element tag, and the apparatus for generating 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 element information corresponding to the page element as the root node is omitted, the page element as the intermediate node is identified by the corresponding element serial number, and the target page element is identified by the corresponding element tag 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 embedded point event code.

Fig. 19 is a block diagram illustrating a device for processing a buried point event, which may be configured in the buried point background shown in fig. 7, according to an embodiment, and as shown in fig. 19, the device for processing a buried point event 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, and the buried point event code of the buried point page element is generated according to the method for generating the buried point event code shown in any one of the embodiments; a storage module 1920, configured to store 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 when the page element in the displayed page is triggered, the terminal generates a corresponding buried point event code according to the method for generating the buried point event code and reports the buried point event code.

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

and 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 which is embedded and displayed in the embedded point element configuration page.

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

and the appointed display module is used for displaying the page elements of the buried points in the embedded displayed first target page according to an appointed display mode.

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

And the path backtracking module is used for reconstructing a path 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 buried point page element in the embedded and displayed first target page according to the path information of the buried point page element.

FIG. 20 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment 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 bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 20, the computer system 2000 includes a Central Processing Unit (CPU)2001, which can perform various appropriate actions and processes, such as executing 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 (RAM) 2003. In the RAM 2003, various programs and data necessary for system operation are also stored. The CPU 2001, ROM 2002, and RAM 2003 are connected to each other via 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 portion 2006 including a keyboard, a mouse, and the like; an output section 2007 including a Cathode Ray Tube (CRT), a 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. Drive 2010 is also connected to 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 necessary, so that a computer program read out therefrom is mounted in the storage section 2008 as necessary.

In particular, according to embodiments of the application, the processes described above with reference to the flow diagrams 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 illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 2009, and/or installed from the removable medium 2011. When the computer program is executed by the Central Processing Unit (CPU)2001, various functions defined in the system of the present application are executed.

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. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a 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 present application, 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 this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. 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 flowchart 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. 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 described in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable storage medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer-readable storage medium carries computer-readable storage instructions that, when executed by a processor, implement the method in the embodiments described above.

According to an aspect of the present application, there is also provided an electronic device, including: a processor; a memory having computer readable instructions stored thereon 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 the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute 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 invention 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 invention pertains.

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

Claims

1. A method for generating a buried point event code is characterized by comprising 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 specified element tag as a root node;

converting the initial path to obtain a path character string, wherein 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 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 tag corresponding to the searched parent page element is the specified element tag;

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

3. The method of claim 2, wherein the element information includes attribute information of a page element; before the converting the initial path to obtain the path character string, the method further includes:

determining the type of the embedded point to which the target page element belongs according to the attribute information of the target page element;

the converting the initial path to obtain a path character string includes:

and converting the initial path according to a conversion mode corresponding to the type of the embedded point to which the target page element belongs to obtain the path character string.

4. The method of claim 3, wherein the buried point types include a first type and a second type, page elements attributed to the first type being heterogeneous elements, page elements attributed to the second type being homogeneous elements;

the converting the initial path according to the conversion mode corresponding to the type of the embedded point to which the target page element belongs to obtain the path character string includes:

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

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

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

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, including:

generating a pre-coding character string according to the path character string, the page address corresponding to the target page and 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 type of the embedded point to which the target page element belongs 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 a buried point event code corresponding to the target page element.

6. The method of claim 5, wherein before generating the pre-encoding 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 comprises:

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

7. The method according to any one of claims 1-6, further comprising:

and reporting the buried point event code.

8. 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-7;

if the buried point event code reported by the terminal is the buried point event code of the buried point page element, storing the reported buried point event code into an analysis database, and when the page element in the displayed page is triggered, generating and reporting the corresponding buried point event code according to the method of any one of claims 1 to 6 by the terminal.

9. The method of claim 8, wherein prior to obtaining the site configuration information, the method further comprises:

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

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

10. The method of claim 9, wherein after generating the buried point configuration information according to the generated buried point event code, the method further comprises:

11. The method of claim 10, wherein before displaying the embedded page elements in the first target page in the embedded display according to the designated display mode, the method further comprises:

acquiring a path character string of a buried point page element;

performing path reconstruction according to the path character string of the buried point page element to obtain path information of the buried point page element;

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

12. An apparatus for generating a buried event code, the apparatus comprising:

13. A device for processing a buried point event, 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, and the buried point event code of the buried point page element is generated according to the method in any one of claims 1 to 7;

a storage module, configured to store the reported buried point event code in 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 when a page element in a displayed page is triggered, the terminal generates and reports a corresponding buried point event code according to the method of any one of claims 1 to 7.

14. 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 11.

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