CN112162739A

CN112162739A - Visual point burying method and system based on JS-SDK

Info

Publication number: CN112162739A
Application number: CN202011022932.8A
Authority: CN
Inventors: 于扬
Original assignee: Beijing Analysys Think Tank Network Technology Co ltd
Current assignee: Beijing Analysys Think Tank Network Technology Co ltd
Priority date: 2020-09-25
Filing date: 2020-09-25
Publication date: 2021-01-01

Abstract

The invention discloses a JS-SDK-based visual point burying method, which comprises the following steps: acquiring a page to be embedded by an editor, and activating a visual embedding mode of the page; editing embedded points in the page, and transmitting embedded point information to a server through an editor; acquiring a buried point list which is transmitted from a server and is related to a current buried point through an editor, and binding information in the buried point list to a current page in a non-deployment state; when the editor is switched to a test mode, confirming the embedded point elements to complete the creation of page embedded points; accessing a current page, and acquiring a built-in point in the current page from a server; and binding the created buried point information to the current page, and storing the buried point trigger information in the server after the buried point trigger. The invention solves the problems of complex operation of the embedded point and large reported data quantity, is suitable for the embedded point scheme under the complex service scene, and improves the accuracy of the data analysis result.

Description

Visual point burying method and system based on JS-SDK

Technical Field

The invention relates to the technical field of data acquisition and processing, in particular to a JS-SDK-based visual point burying method and a JS-SDK-based visual point burying system.

Background

Data statistics is an important part in the iterative process of internet products, and mainly comprises two parts, namely data acquisition and data analysis, wherein data acquisition determines a data source, and data are acquired quickly, accurately and uninterruptedly, so that the data statistics is a main challenge facing data acquisition SDK (hereinafter referred to as SDK). The SDK can count the click information of the page elements for analyzing user interaction and user behavior, and plays a great role in continuous optimization of internet products. The data acquisition process is approximately a design embedding point, an integrated SDK, a trigger embedding point and a report server. The existing data acquisition modes mainly include code acquisition, full-buried point acquisition, visual acquisition and the like.

Specifically, a code acquisition rough flow puts forward data statistics requirements for operators, product personnel design embedded points, developers call SDK acquisition interfaces to implant the embedded points, the embedded points are packaged again to release new versions, and the operators analyze the new versions after data is reported. The point burying mode has the advantages of accurate acquisition and small data volume, and has the defect of high labor and time cost. The method has the advantages that the buried points are implanted into all page elements in advance in the full buried point acquisition mode, all the elements report data after being clicked, and operators screen out concerned elements and then perform data statistics. The visual acquisition can be added with acquisition points under the condition of no edition sending, the acquisition is accurate, the reported data volume is small, the advantages of code embedded points and full embedded points are integrated to a certain extent, and the visual acquisition is an important direction for data acquisition development.

Further, the existing SDK visualization acquisition technology mainly comprises visualization based on full-buried points and visualization based on editor selection. The method comprises the steps of acquiring click events of all elements based on visualization of the full-buried point, selecting concerned data in an editor for analysis when analyzing data, and acquiring the full-buried point. Although the technology can visually select the embedded points, the technology is a full embedded point technology essentially, the data volume is large, the reported data only comprises element click information, and the element related information cannot be reported. And (3) based on the visualization of equipment end selection, using an SDK host program running on the equipment when editing the embedded point, and generating an embedded point instruction to be deployed to enable the whole network to take effect. However, the visualization of the technology is used for operating the embedded points on the mobile phone terminal equipment, the operation difficulty is high, and the method is limited by the screen size and the interaction mode, so that the complex embedded point requirement cannot be realized. In addition, the visual acquisition technology based on editor selection uses a single webpage editor to edit the buried points, and the whole network becomes effective after deployment. However, the existing visual acquisition technology based on editor selection is still in the initial development stage, and the existing solution only acquires element click events, and the acquisition requirement under the complex acquisition environment cannot be met.

Disclosure of Invention

In order to solve the technical problem, the invention provides a JS-SDK-based visual point burying method, which comprises the following steps: acquiring a page to be embedded by an editor, and activating a visual embedding mode of the page; editing embedded points in a page, and transmitting embedded point information to a server through the editor; acquiring a buried point list which is transmitted from the server and is related to a current buried point through the editor, and binding information in the buried point list to a current page in a non-deployment state; when the editor is switched to a test mode, confirming the embedded point elements to complete the creation of page embedded points; accessing a current page, and acquiring a built-in point in the current page from the server; and binding the created embedded point information to the current page, and storing the embedded point trigger information in the server after the embedded point trigger.

Preferably, in the step of embedding points in the editing page, editing is performed by circling page elements.

Preferably, the buried point information includes, but is not limited to: the method comprises the steps of identifying a buried point element, the position of the buried point element in a page structure, associated attribute information of the buried point element, the positioning mode of the buried point element, the effective range of the buried point, the effective range of the page and the effective version, wherein the positioning mode of the buried point element is selected from one or a combination of a new _ path positioning mode, an attribute positioning mode and a peer element positioning mode.

Preferably, in the step of binding the created buried point information to the current page, the method includes: analyzing created embedded point information related to a current page, positioning a target embedded point element according to a defined element positioning mode, and acquiring the correlation attribute of the target embedded point element, wherein when the defined element positioning mode is multiple, if the embedded point element positioning result obtained after each positioning process is the same, the element positioning operation of the current page is successful, and the embedded point element positioning result is taken as the target embedded point element; otherwise, it fails.

Preferably, after the step of binding the created buried point information to the current page, the method further comprises: and after the target embedded point element is successfully positioned, adding an event monitor for the target embedded point element.

Preferably, the method further comprises: the method comprises the steps that the server is connected through an editor, and a page information acquisition notice is obtained when a terminal SDK is connected with the server, wherein the page information acquisition notice is sent by the server after the terminal SDK sends page information of a page of a point to be buried to the server; and feeding the page information of the page to be embedded point back to the terminal SDK through the server, so that the terminal SDK puts the page information into the h5 window attribute of the window element of the terminal webpage, and transmitting the new page information to the server.

Preferably, in the process of binding the buried points, the method further comprises: receiving embedded point information containing Hybrid embedded points, and binding pages, wherein the editor identifies the embedded point information, marks the current embedded point as the Hybrid embedded point in the embedded point information when the embedded point information contains the Hybrid embedded points or the embedded point is only bound in a mode of positioning according to attributes, and sends the updated embedded point information to the terminal SDK through the server so as to be sent to the webpage end data collector through the server after the terminal SDK screens out the Hybrid embedded points.

Preferably, if the current embedded point is a Hybrid embedded point, the server calls the associated element attribute about the current embedded point stored in the terminal SDK; and if the current embedded point is a non-Hybrid embedded point, after a first notification is obtained, feeding back the embedded point information containing the associated element attribute information of the current embedded point to the terminal SDK through the server, wherein when the terminal SDK detects that the current embedded point is triggered, the server sends the first notification to the webpage data collector.

Preferably, after the step of receiving and binding the Hybrid embedded point, the method further comprises the following steps: and after the current Hybrid embedded point is triggered, transmitting corresponding embedded point triggering information to the server through the terminal SDK.

On the other hand, the invention also provides a visual embedded point system based on JS-SDK, the visual embedded point system executes the method, and the visual embedded point system comprises: the system comprises a webpage end data collector, a server and a server, wherein the webpage end data collector is used for firstly obtaining a page to be embedded by an editor, activating a visual embedded point mode of the page, then editing embedded points in the page, transmitting embedded point information to the server by the editor, then obtaining an embedded point list which is transmitted from the server and is related to a current embedded point by the editor, binding information in the embedded point list to the current page in a non-deployment state, confirming embedded point elements to complete the creation of embedded points of the page when the editor is switched to a test mode, accessing the current page, obtaining the embedded points which are created in the current page from the server, and finally binding the created embedded point information to the current page so as to store embedded point trigger information in the server after the embedded point is triggered; the editor is communicated with the webpage data collector and the server through a PostMessage; and the server is communicated with the webpage data collector in an Http or Http mode and is used for storing and transmitting page information of website pages, created embedded point information in each page and embedded point triggering information of created embedded points in each page.

Compared with the prior art, one or more embodiments in the above scheme can have the following advantages or beneficial effects:

the invention provides a visual point burying method and system based on JS-SDK. According to the method and the system, firstly, the points are buried in a webpage end visual editor selection mode, so that the problems of complex operation of the buried points and large reported data volume are solved; the page elements are positioned by using the attribute positioning mode, so that the problem of positioning failure caused by inconsistent positions of page elements of different versions is solved, the problem of list element point burying is solved by using the same-level point burying technology, and the point burying scheme under a complex service scene can be solved. In addition, the invention can embed the associated attribute information related to the embedded point elements in the embedded point information, can collect richer data at the embedded point, further provides more types of data information for a data analysis stage, and can analyze the data collected by the embedded point from a multidimensional angle, thereby improving the accuracy of a data analysis result. In addition, the invention also provides a complete communication protocol capable of processing Hybrid embedded points, so that the visual embedded point method can be suitable for embedded point schemes under different service occasions (different operating systems).

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:

FIG. 1 is a step diagram of a JS-SDK based visualization embedding method according to an embodiment of the application.

FIG. 2 is a specific flowchart of a JS-SDK based visualization point burying method in a point burying editing stage according to the embodiment of the application.

Fig. 3 is a specific flowchart of the visualization embedding point method based on JS-SDK in the embedding point validation phase according to the embodiment of the present application.

Fig. 4 is an exemplary diagram of an implementation principle of a new _ path positioning method in a buried point validation phase of a visualization buried point method based on JS-SDK according to an embodiment of the present application.

Fig. 5 is an exemplary diagram of an implementation principle of a method for locating peer elements in a buried point effective phase of a JS-SDK-based visual buried point method according to an embodiment of the present application.

Fig. 6 is an exemplary diagram of an implementation effect of acquiring relevant attributes of a target buried point element in a buried point validation phase by using a JS-SDK-based visualization buried point method according to an embodiment of the present application.

FIG. 7 is a scene schematic diagram of embedding an Internet product into an H5 page in the JS-SDK based visualization embedding method according to the embodiment of the application.

Detailed Description

The following detailed description of the embodiments of the present invention will be provided with reference to the drawings and examples, so that how to apply the technical means to solve the technical problems and achieve the technical effects can be fully understood and implemented. It should be noted that, as long as there is no conflict, the embodiments and the features of the embodiments of the present invention may be combined with each other, and the technical solutions formed are within the scope of the present invention.

Additionally, the steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.

The existing SDK visualization acquisition technology mainly comprises visualization based on full-buried points and visualization based on editor selection. The method comprises the steps of acquiring click events of all elements based on visualization of the full-buried point, selecting concerned data in an editor for analysis when analyzing data, and acquiring the full-buried point. Although the technology can visually select the embedded points, the technology is a full embedded point technology essentially, the data volume is large, the reported data only comprises element click information, and the element related information cannot be reported. And (3) based on the visualization of equipment end selection, using an SDK host program running on the equipment when editing the embedded point, and generating an embedded point instruction to be deployed to enable the whole network to take effect. However, the visualization of the technology is used for operating the embedded points on the mobile phone terminal equipment, the operation difficulty is high, and the method is limited by the screen size and the interaction mode, so that the complex embedded point requirement cannot be realized. In addition, the visual acquisition technology based on editor selection uses a single webpage editor to edit the buried points, and the whole network becomes effective after deployment. However, the existing visual acquisition technology based on editor selection is still in the initial development stage, and the existing solution only acquires element click events, and the acquisition requirement under the complex acquisition environment cannot be met.

Therefore, in order to solve the technical problem, the invention provides a visual acquisition method (visual embedded point method) based on JS-SDK, and the method is completed by a visual embedded point system. The visual embedded point system comprises a webpage end data collector, a webpage editor and a server end. Specifically, in a buried point editing stage, firstly, page structure information of a page to be buried is obtained through an editor; then, under a visual embedded point mode, editing the embedded point in a mode of circling page elements by an editor, inputting embedded point information at least comprising target embedded point elements and target element associated attribute information, and storing the current embedded point information by a server; then, acquiring a buried point list containing current buried point information transmitted from the server through an editor; and performing element binding on the current page when the editor is in a non-deployment state, so that when the editor is switched to a test state, a target embedded point element is selected, and the creation task of the embedded point of the page is completed after the embedded point element is confirmed. Further, the visualized embedded point method of the invention needs to enter the embedded point validation stage after the embedded point element is successfully created. In the embedded point effective stage, the webpage end data collector is directly communicated with the server, firstly, when a current page is accessed, embedded points created in the current page are obtained from the server, embedded point information is bound, and after a target embedded point element is triggered and activated, embedded point trigger information corresponding to the current triggered element is sent to the server to be stored.

Therefore, the invention solves the problems of complex operation and large reported data amount of the existing full-buried point data acquisition technology, and enriches the data acquired at the buried point by not only reporting the page elements but also reporting the associated information of the page elements together.

In addition, the invention also provides a Hybrid embedded point communication protocol, and particularly discloses an implementation flow of the communication protocol in a webpage data collector. The embedded point information of the webpage end data collector is added into an H5 page embedded in a native webpage of the terminal, Hybrid embedded point is realized through data transmission of the terminal SDK and the webpage end data collector, and transmitted data mainly comprise page information (page structure), embedded point information, cross-platform associated attributes and embedded point triggering information. Therefore, the invention realizes the visual Hybrid embedded point function completed through the communication among the webpage data collector, the webpage editor, the server and the terminal SDK through the definition of the communication protocol of the Hybrid embedded point.

Before explaining the visual point burying method, the application environment of the current visual point burying method is explained. In the embodiment of the invention, the visual embedded point method is executed through a visual embedded point system (the visual embedded point method is executed based on the visual embedded point system; and the current visual embedded point system is provided based on the visual embedded point method). Referring to fig. 2 and 3, the visual buried point system according to the present invention includes: the system comprises a web site data collector (the web site data collector is a data collector written by using javascript language), a web site editor (hereinafter referred to as "editor"), and a server (wherein the server is a background server of the web site). In the embedded point editing stage, the editor and the webpage data collector and the editor and the server are communicated through PostMessage interfaces. The server and the webpage data collector communicate in an Http/Http mode.

Further, the communication between the editor and the web page end data collector uses an iframe postMessage communication mode, in the embedded point editing stage, the web page end data collector informs the editor of information of embedded point positions and the like through the postMessage communication mode, after the embedded points are deployed, the embedded point validation stage is entered, and at the moment, the web page end data collector obtains the embedded point information corresponding to the embedded points established on the page from the server through an Http or Http mode.

Further, the webpage end data collector is used for firstly obtaining a page to be embedded by the editor, activating a visual embedded point mode of the page, then editing embedded points in the page, transmitting embedded point information to the server by the editor, then obtaining an embedded point list which is transmitted from the server and is related to the current embedded point by the editor, binding information in the embedded point list to the current page in a non-deployment state, confirming embedded point elements to complete creation of the embedded point of the page when the editor is switched to a test mode, accessing the current page, obtaining the embedded point which is created in the current page from the server, and finally binding the created embedded point information to the current page so as to store embedded point trigger information in the server after embedded point triggering. The server is used for storing and transmitting page structure information of each page in the website, embedded point information (including embedded point related information) of the built embedded point in each page, embedded point trigger information of the built embedded point in each page and the like. In addition, the server is used for generating a corresponding embedded point list according to embedded point information of a current page received from the web page data collector through the editor in the embedded point editing stage, so that the embedded point list is fed back to the web page data collector through the editor to bind embedded point elements of the current page.

FIG. 1 is a step diagram of a JS-SDK based visualization embedding method according to an embodiment of the application. The JS-SDK-based visual embedded point method (i.e. the implementation method of the visual embedded point system) according to the present invention is described in detail below with reference to fig. 1.

As shown in fig. 1, step S110, entering a buried point editing stage, where a web page data collector obtains a page to be buried through an editor, and activates a visual buried point mode of a current page to be buried (i.e., a current page); step S120, the webpage data collector edits the to-be-processed embedded points needing to be configured in the current to-be-embedded point page by using an editor, and transmits embedded point information corresponding to the to-be-processed embedded points to the server end through the editor; step S130, the webpage data collector obtains a buried point list which is transmitted from the server and is related to buried point information corresponding to the current buried point to be processed through the editor, and under the condition that the editor is in a non-deployment state, the information in the buried point list is bound to the current buried point page, so that one or more buried point elements are positioned; step S140, the web page data collector switches the editor to the test mode, and after triggering the final embedded point element, the embedded point is confirmed to be successful and the creation of the page embedded point is completed, at this time, the embedded point editing stage is finished. Thus, the operation of creating page burial points is completed through the above steps S110 to S140.

Continuing to refer to fig. 1, after completing the task of deploying the embedded points of the current page, entering a stage of validating the embedded points, in step S150, using the browser to access the current page again, and acquiring, by the web page data collector, embedded point information corresponding to all the created (deployed) embedded points in the current page from the server; step S160, at the embedding point effective stage, the webpage data collector binds the current page according to the established embedding point information; step S170, after detecting that the deployed buried point is triggered, the web page data collector generates corresponding buried point trigger information, so as to resend the current buried point trigger information to the server for storage by the server. In this way, the deployed buried point is issued to the access website through the steps S150 to S170, and the process of collecting buried point trigger information after the buried point is triggered is completed, so that the visual data collection scheme based on the editor is realized.

FIG. 2 is a specific flowchart of a JS-SDK based visualization point burying method in a point burying editing stage according to the embodiment of the application. The following describes in detail a flow of a buried point editing stage of the visualized buried point method according to an embodiment of the present invention with reference to fig. 1 and fig. 2.

As shown in fig. 2, in step S201, the web page data collector obtains page structure information corresponding to a to-be-buried point page from the server through an editor, and the editor embeds the to-be-buried point page into a current page according to the current page structure information. In step S201, the web page data collector connects to the editor under the operation of the first type of user (the first type of user is located at the web page data collector), opens the embedded point editor, and after the editor obtains the page structure information corresponding to the current page from the server, embeds the current page structure information into the current page to be embedded through the iframe tag, thereby entering step S202.

Step S202 activates the current page to the visual embedded state by the web page data collector. In step S202, the web page data collector sets the SDK in the current page to be embedded as a visual embedded state, and automatically loads the SDK with the visual function, so as to open the SDK in the current page as the visual embedded state, thereby entering step S203.

Further, when a first type of user uses an editor to embed into a current website page through an iframe tag, a webpage data collector receives a visual mode activation instruction sent by the editor, and activates a visual embedded point state of the page after verification is passed, wherein the SDK implementation format in the process is as follows:

the type field is the type of the visualization mode activation instruction, the value of the orgin field is the address in which the iframe is embedded, the value of the boss field is the website address of the parent window, and the isNewvisual field is the latest version of the current visualization edit box. After the instruction check of the web page end data collector is passed, the web page end data collector returns a check result to the editor, and the format of the check result is as follows:

{

“code”：200，

“type”：“INIT”，

“isNewVisual”：true

}

wherein, the type field indicates that the editor is informed that the current verification result information is an initialization message; when the value of the code field is 200, the verification is passed, the visualization embedded point state is activated, and when the value of the code field is 400, the verification is not passed and the current visualization embedded point state is ended; the isNewvisual field indicates that the current visualization SDK is the latest version.

Step S203, the webpage data collector edits the embedded point of the current page in a mode of circling the page element by the editor to generate corresponding embedded point information, and sends the embedded point information to the editor, so that (step S204) the editor sends the current embedded point information to the server, and the server stores the embedded point information of the edited embedded point in the current page. Specifically, in step S203, the editor user edits the embedded point of the current page by using the editor to select the page element, so as to generate corresponding embedded point information, and after the web page data collector stores the embedded point information, sends the current embedded point information to the editor in a PostMessage communication manner.

It should be noted that, in the embodiment of the present invention, the first-class user sets the embedded point information, and also sets other information, such as associated attribute information and an embedded point element positioning manner, associated with the embedded point element. Specifically, after the edit of the embedded point is completed, the data collector at the web page end generates corresponding embedded point information. At this time, the generated buried point information includes, but is not limited to: the method comprises the following steps of identifying one or more buried point elements, the position of each buried point element in a page structure, the associated attribute of each buried point element (the associated attribute information comprises the associated element positioning information, attribute type information, attribute content information and the like, for example, the current buried point element is an A label in a page, and the associated attribute can be other content attributes related to the A label, such as the text content of the A label), the type of each buried point element, the positioning mode of the buried point element, the nearest parent element triggering the buried point element and the associated element, a buried point effective range, a page effective range and an effective version of the SDK. The positioning method of the embedded point element is selected from one or a combination of several of new _ path positioning, attribute positioning and sibling element positioning.

Further, in the embodiment of the present invention, the association attribute may support one or a combination of several of a boolean type, a character string type, a number type, and a text type.

Further, in the embodiment of the present invention, the associated attribute of the element is regular expression screening supporting user-definition.

Therefore, the embedded point information generated by the embodiment of the invention not only contains page element information, but also contains various other types of information, so that the embedded point can acquire more abundant types of acquired data at the embedded point after being created, and wider-range data information is provided for the subsequent data analysis process based on the embedded point acquisition result, and more accurate user requirements are analyzed.

In step S204, after the editor receives the current buried point information, the editor sends a buried point information saving notification containing the current buried point information to the server, so that the editor notifies the server to save the current buried point information into the database. In addition, in step S204, after the server receives the buried point information saving notification, the current buried point is marked as a non-deployed state.

After the editor transmits the buried point information storage notification to the server, the process proceeds to step S205. In step S205, the editor requests the server for the embedded point list, and in step S206, after the editor receives the embedded point list, the current embedded point list is sent to the web page data collector in a postMessage communication manner, so that the web page data collector receives the embedded point list transmitted from the server through the editor. It should be noted that, in the embodiment of the present invention, the buried point list is a set containing all the buried point information edited in step S204.

After the web page data collector receives the current list of the nodes, the process proceeds to step S207. In step S207, the web page data collector analyzes the currently received buried point list to obtain buried point information (one or more pieces of information input from the editor), so as to bind the current buried point information to the buried point elements of the current page. In step S207, the binding process binds the page elements according to the embedded point element positioning manner set by the user in step S203, at this time, a plurality of positioned embedded point elements are obtained, and finally, the positioned embedded point elements are displayed by the web data collector, thereby entering step S208.

Step S208 is to notify the editor to switch to the test mode after the webpage data collector generates the embedded point element binding result, so that after the embedded point element binding result is switched to the test mode, the first-class user screens out a part of target embedded point elements from the displayed embedded point elements, and then the process proceeds to step S209. When screening the displayed buried point elements, selecting a part of buried point elements from all the buried point elements displayed in the current page to be buried point by a first-class user as target buried point elements to click, thereby selecting the target buried point elements.

In step S209, the web page data collector displays the buried point trigger information related to the current target buried point element near the target buried point element, and prompts that the buried point operation is successful by displaying the buried point trigger information that the buried point operation is successful to the user, thereby entering step S210. It should be noted that, in the embodiment of the present invention, the buried point trigger information includes current buried point information, and a correspondence between all buried point elements that are matched by the current buried point information and can trigger the buried point, and the like.

Step S210, after the data collector at the web page end generates the buried point trigger information, the data collector at the web page end sends the buried point trigger information containing the notification of the changed buried point deployment state to the server end through the editor, so that the server end converts the current state of the buried point from the non-deployment state to the deployment state after receiving the notification of the changed buried point deployment state. In one embodiment, after the webpage data collector generates the buried point trigger information and sends the buried point trigger information to the editor, when the editor receives the notification of changing the buried point deployment state, a user of the editor controls the editor to send the current buried point deployment state notification to the server by clicking a deployment button of the editor. At this time, after receiving the current buried point deployment state notification, the server side converts the state of the current buried point from the non-deployment state to the deployment state.

Thus, the entire buried point editing stage is completed through the above steps S201 to S210.

Fig. 3 is a specific flowchart of the visualization embedding point method based on JS-SDK in the embedding point validation phase according to the embodiment of the present application. The following describes in detail a flow of a buried point validation phase of the visualized buried point method according to an embodiment of the present invention with reference to fig. 1 and fig. 3. It should be noted that, in the embedded point validation phase, the data collector at the web page end can directly communicate with the server.

As shown in fig. 3, in step S301, a browser is used to re-access or refresh the web page of the website where the current page is located, and the web page data collector obtains, from the server end, the buried point information corresponding to the buried point that has been deployed (created) in the current page stored in the server database in the Http mode or the Http mode, so as to enter step S302.

Step S302, the webpage data collector binds the current embedded point information to the current page according to the received embedded point information corresponding to the embedded point created in the current page.

In step S302, the created buried point information related to the current page is first analyzed (step S3021, not shown), that is, the received buried point information is analyzed, and then (step S3022, not shown) the target buried point element is located according to the defined element locating manner in the buried point information, and the related attribute of the target buried point element is obtained.

The following first describes a method for implementing a process of parsing the embedded point information of the web page data collector. After the editor enables the server to store the embedded point trigger information containing the embedded point information, the server sends all the embedded point information which is created in the stored current page to the editor, and further the editor sends the current embedded point information to the webpage end data collector in a postMessage communication mode. The embedded point information comprises the following fields: id represents a buried point element identifier representing the identity of the buried point element; the new _ path field indicates the position of the buried point element in the page structure; a related field represents the corresponding associated attribute of the buried point element, the field is an array and can represent a plurality of attributes, and each data bit represents one attribute; the prop _ name field is used to indicate the content of the associated attribute, i.e. to identify which associated attribute is; the pro _ type field indicates an attribute type of the associated attribute; the key field indicates that the attribute (namely the triggered mark of the embedded point element) is identified in the reported data after the embedded point is triggered; the target field represents the positioning information of the attribute of the associated element, and is a parent element with the closest triggering buried element and the associated element; the step field represents the backtracking step number of the buried trigger element to the parent element, and the step field positions the associated element through the new _ path field after the backtracking to the parent element; the tips _ binding field indicates that the element is positioned by attribute; the binding _ range field represents the effective range of the specified buried point; the pages field indicates the active page; the versions field indicates the validated version of the SDK.

After analyzing the current embedded point information, the webpage data collector can perform page embedded point element positioning processing on the current page according to an element positioning mode in the embedded point information, so as to obtain a corresponding target embedded point element. In the embodiment of the present invention, since the element location mode is a combination of one or more location modes, if the element location mode analyzed by the web page data collector is only one, the page embedded point element is located by using a new _ path location mode, or an attribute location mode, or a peer element location mode, so as to obtain a location result in a corresponding mode, that is, a target embedded point element.

In addition, if the element positioning modes analyzed by the web page end data acquisition device are multiple, the embedded point elements of the current page are positioned by utilizing corresponding defined modes, and the element positioning operation of the current page is successful when the embedded point element positioning results obtained after each positioning process are the same, so that the embedded point element positioning result is used as the target embedded point element. In addition, when the positioning results of the embedded point elements obtained after each positioning process are inconsistent, the element positioning operation of the current page fails, and at this time, a corresponding prompt needs to be performed on the user to perform embedded point editing again.

Fig. 4 is an exemplary diagram of an implementation principle of a new _ path positioning method in a buried point validation phase of a visualization buried point method based on JS-SDK according to an embodiment of the present application. Referring to fig. 4, a description is provided below of an implementation principle of a new _ path positioning manner in a web page data collector in the embodiment of the present invention.

The new _ path positioning is to position the page element by matching the topological position, and abstract the page structure of the current page into a tree structure, as shown in the left diagram of fig. 4, the page structure of the current page is a page tree structure. As shown in the right diagram of fig. 4, a new _ path field contained in the buried point information indicates a preset positioning mode defined as the current buried point in the new _ path positioning mode.

As shown in fig. 4, when searching for the page element specified by the new _ path field, the web page data collector matches the element 1 from the root node of the page tree (compare the attribute of the page element with the response information of the child element in the new _ path array, where the attributes of the page element, such as the element type name tagName, the location index/row in the parent element, etc., in the direct child element under the parent element, if there is no identical element, it is identified as index, and if there is an identical element, it is identified as row), continues the following matching in a manner of precedent traversal, if there is an unmatched node midway, i.e., the matching fails, until the last node 5 in the new _ path is successfully matched, at this time, it locates the final buried point element (the buried point element locating result of the current new _ path locating manner).

The following refers to a description of an implementation principle of a data collector at a web page in an attribute positioning manner in the embodiment of the present invention.

Whether the page element binding mode preselects and defines a positioning mode according to attributes is determined according to a tips _ binding field in the embedded point information, the positioning mode ignores the position of the element in a page structure, and the specific implementation method of the tips _ binding field in the webpage data collector is as follows:

when the webpage end data collector locates the elements, the whole page structure tree needs to be traversed in a way of preorder traversal from the root node of the page, and if the type (class) of the current element is panel-title, the matching is successful. In the location by attribute approach, there may be multiple page elements that match successfully, so clicking on these elements triggers the buried point. Wherein, the value of the field prop _ name is an enumeration type, and a specific example of the field is as follows:

the above example shows that all the elements with text content of "ok" on the current page are matched successfully, and the elements with "ok" trigger the current buried point. At this time, these elements that are "determined" are the positioning results of the current buried point elements according to the attribute positioning mode.

Further, in an embodiment, if two positioning modes, namely, a new _ path positioning mode and an attribute positioning mode, are simultaneously specified in the embedded point information, the web page data collector executes the two positioning algorithms simultaneously, and the positioning of the page is not successful until all element positioning results obtained in each mode are matched.

The algorithm for positioning according to the new _ path has the advantages of accurate positioning and capability of uniquely positioning a target element, and has the defect that the page structure cannot be matched after being changed, such as: page reprinting can result in unsuccessful buried point triggering. Location by attribute can solve this problem, and regardless of the location of the element, location can be successful as long as the attribute (type, text) is not changed, with the disadvantage that multiple elements can be located (not if the user just wishes to locate multiple elements). Therefore, when the embedded point is edited, the two positioning modes are flexibly used, and a complex service scene can be met.

Fig. 5 is an exemplary diagram of an implementation principle of a method for locating peer elements in a buried point effective phase of a JS-SDK-based visual buried point method according to an embodiment of the present application. The same level element positioning mode is used to satisfy the buried point requirement of the list type element. FIG. 5 shows a typical list class element with a fixed number of sub-elements, and a page structure with the same layout but different contents is used when sliding or switching the list. If the user wants to count the click condition of item 1 in the list or the click condition of all items (distinguished by associated names or prices), the peer positioning function needs to be used.

Referring to fig. 5, a description is provided below of an implementation principle of a web page data collector of a peer element location manner in the embodiment of the present invention. In the same-level element positioning method, the positioning results of the located buried point elements include two types: the list is fixed with row buried points and the list is the same level buried points.

In list fixed row burial, referring to fig. 5, for example: the user wants to bury the point on the first item (i.e. model one), and if the second item (model two) in the list is clicked, the point buried set by the first item is not triggered. In this case, a row field in a new _ path field in the embedded point information issued by the server is used, that is, a row sequence number indicating a binding row in the page, and at this time, the data collector at the web page end determines that the embedded point is related to the list element through the row field and determines that the first item needs to be bound.

In the list same-level buried point, if a user wants to mark all the items of the list class as buried points and report the title of each item, the only difference between the new _ path in the buried point information sent by the server and the buried point of the list fixed line is that no row field exists. At this time, the web page data collector can identify that the row field is absent in the embedded point information, so as to determine all positions in the binding list, which are matched with the new _ path field, and use elements corresponding to the positions as the embedded point element positioning result of the current same-level element positioning mode. And after all the buttons are clicked, triggering the current embedded point, positioning the element position associated with the line according to the related field in the embedded point information, and acquiring the title attribute.

In addition, after the target buried point element is successfully located, in step S302, the embodiment of the present invention further obtains the associated attribute information of the target buried point element. The embedded point element association attribute is stored in a related field in the embedded point information, taking the previous list of the same-level embedded points as an example, if the embedded point element is a local row button, the associated attribute of the embedded point element is a title of the local row, and at this time, a specific example of the related field is as follows:

fig. 6 is an exemplary diagram of an implementation effect of acquiring relevant attributes of a target buried point element in a buried point validation phase by using a JS-SDK-based visualization buried point method according to an embodiment of the present application. As shown in fig. 6, if the buried point trigger element is the second item (type two) in the list, the web page data collector may trace up to its parent element a according to the step field in the buried point information, and then find the buried point element "type two" according to the h5_ path field, so as to obtain, through the function textContent, the associated attribute of the buried point element: text.

Finally, in step S302, the web page end data collector further generates corresponding embedded point effective feedback information after successfully positioning the target embedded point element and the associated attribute of the target embedded point element, so as to send the embedded point effective feedback information to the server, so that the embedded point of the web page end data collector takes effect, and at this time, waits for the activated embedded point. Specifically, the webpage data collector encapsulates the embedded point effective feedback information and reports the encapsulated embedded point effective feedback information to the server, and the embedded point effective feedback information includes: and the information of the webpage end user identification code, the activation time, the activated embedded point element, the corresponding event and the like.

In addition, in step S302, after the target embedded point element and the associated attribute of the target embedded point element are successfully located, the web page data collector may generate corresponding embedded point effective feedback information, and add an event listener to the located target embedded point element.

Specifically, after the positioning is successful, an event listener is added to the element through a system function document.

After the page element binding processing in the embedded point validation phase is completed, the process proceeds to step S303 to wait for the current embedded point to be triggered. Step S303, after detecting that the currently effective buried point is triggered, the data collector at the webpage end sends the buried point trigger information corresponding to the current buried point to the server end, and in step S304, the server stores the received buried point trigger information as the data collection result of the current buried point in the database, so that the data content in the database is used as the data basis of the subsequent buried point analysis. In step S303, the web page data collector continuously detects whether the current embedded point is triggered. More specifically, in step S303, it is determined whether the current embedded point is triggered by detecting whether the first type of user clicks the page element of the embedded point that has come into effect in the website, and after the target embedded point element corresponding to the current target embedded point is clicked, the current embedded point is triggered; without a click, the current buried point is not triggered.

Therefore, the invention completes the visual embedded point based on JS-SDK formed among the three ends of the webpage end data collector, the website end editor and the server through the steps S201 to S210 and the steps S301 to S304.

In addition, in order to meet more service scenes, the invention also provides a Hybrid embedded point communication protocol, and the communication process not only needs the participation of a terminal (such as a mobile phone) SDK, but also needs to add embedded point information of a webpage end data collector into an H5 page embedded in a terminal native webpage.

More and more internet products are now embedded with the H5 page. FIG. 7 is a scene schematic diagram of embedding an Internet product into an H5 page in the JS-SDK based visualization embedding method according to the embodiment of the application. FIG. 7 shows an application scenario of embedding an Internet product (e.g., IOS native interface, Android native interface) into an H5 page.

The Android/IOS native page and the H5 page (the Android WebView element is taken as a container or the IOS WKWebView element is taken as a container) are not in the same page structure, development languages are different, the scenes also have buried point statistical requirements, and the buried point of the Android/IOS native page embedded with the H5 page is called Hybrid buried point.

In order to meet the requirement of Hybrid embedded points, the Android/iOS end SDK is required to support, JS-SDK is also required to be added into an H5 page, the Hybrid embedded points are realized through data transmission of the SDKs at the two ends, transmitted data mainly comprise page structures, embedded point information, cross-platform correlation attributes and embedded point trigger information, and a data transmission protocol is executed by adopting a system interface provided by Android View/IOS WKWebView. Therefore, the visual Hybrid embedded point function completed by the communication among the webpage data collector, the webpage editor, the server and the terminal SDK is realized through the definition of the communication protocol of the Hybrid embedded point.

In the Hybrid embedded point embodiment described in the embodiment of the present invention, first, a data transmission communication flow of an embedded point editing process in the visual embedded points at four ends is described.

(1) Opening a buried point editor, and connecting a terminal SDK to a server side by the editor in a ws (WebSocket) mode;

(2) starting a program of the terminal SDK, triggering the terminal SDK to be connected to a server side in a ws mode, and reporting equipment information;

(3) the server side sends the equipment information reported by the terminal SDK to an editor;

(4) the editor displays the equipment information, and after a user of the editor selects the current terminal equipment, the selected equipment information is sent to the server side;

(5) the server side sends an instruction for acquiring the page structure information to the selected equipment;

(6) the terminal SDK generates a current page picture and a current page structure (page information for short in the following) and sends the current page picture and the current page structure to the server;

(7) the server side sends the page information to an editor, and the editor displays the page information;

(8) the editor embeds a page needing to be embedded into a webpage end data collector through an iframe label according to the page information (refer to step S201);

(9) the web page data collector starts a visual embedded point state of a current embedded point page (refer to step S202);

(10) editing the buried points by a user through an editor in a mode of circling page elements, and sending current buried point information to the editor (refer to step S203);

(11) the editor sends a buried point information storage notice containing current buried point information to the server, and then the server side stores the buried point information in a database, marks the buried point as a non-deployment state and sends the current buried point information to the terminal SDK (refer to step S204);

(12) binding currently received embedded point information to a current page element by the terminal SDK;

(13) the terminal SDK user clicks page elements of embedded points in a page to trigger the embedded points, and the terminal SDK sends embedded point triggering information to the server side;

(14) the server side sends the received embedded point trigger information to an editor;

(15) the editor displays the buried point triggering information and confirms that the buried point is successful;

(16) and the editor sends embedded point trigger information containing a notification for changing the embedded point deployment state to the server side, so that the embedded point editing stage of the terminal SDK is completed.

(17) The editor requests a buried point list from the server (refer to step S205);

(18) the editor sends the embedded point list to the webpage data collector in a postMessage communication mode (refer to step S206);

(19) the web page data collector binds the embedded point information in the current embedded point list to the current page element (refer to step S207);

(20) the editor is switched to a test mode, and the webpage data collector selects the elements of the bound buried points in the buried point page (refer to step S208);

(21) the web page data collector shows the buried point trigger information and shows the prompt information that the buried point is successful in the vicinity of the element showing the currently screened buried point (refer to step S209);

(22) the web page end data collector sends a notification of changing the deployment state of the buried point to the server end through the editor, thereby completing the buried point editing stage of the web page end data collector (refer to step S210).

Further, in the Hybrid embedded point embodiment described in the embodiment of the present invention, a data transmission communication flow of an embedded point validation process in the visual embedded points at four ends is continuously described.

The process of the embedded point validation of the web page data collector has been described in the foregoing, and therefore, is not described herein again.

The effective process of the terminal SDK in the visual embedded point is a process of issuing the deployed embedded point to the whole network terminal, and the implementation flow is as follows:

A. the method comprises the steps that a program integrated with an SDK on a terminal is cold started, and the terminal SDK obtains buried point information corresponding to deployed buried points from a server through Http/Http;

B. the terminal SDK analyzes the obtained embedded point information according to the obtained embedded point information, and binds the embedded point information to a terminal webpage, so that an event trigger mechanism corresponding to the embedded point is intercepted;

C. the terminal SDK acquires trigger information, wherein the trigger information is selected from one of modes such as gesture action, click signal and the like;

D. after detecting that the currently effective buried point is triggered, the terminal SDK sends buried point triggering information (in an effective stage) corresponding to the currently triggered buried point to the server;

E. and the server side takes the buried point triggering information (in the effective stage) as a data acquisition result after the buried point is triggered, and stores the data acquisition result in a database for data analysis.

In the actual application process, the web page end data collector, the web page editor, the server and the terminal SDK respectively carry out embedded point editing and validation operations on the web page end data collector and the terminal SDK according to the flows corresponding to the embedded point editing stage and the embedded point validation stage. Further, in the editing and validation process based on the four-end Hybrid embedded point, a complete communication protocol for solving the Hybrid embedded point problem can be formed by improving part of the steps in the whole process implementation process.

Further, when the page structure information in the page information is transmitted among the web page data collector, the web page editor, the server and the terminal SDK, before the terminal SDK edits the embedded point, the page information (including the page structure) needs to be sent to the server, and if the current page information includes an H5 page, the H5 page information needs to be merged into the current page.

Specifically, first, the web page data collector is connected to the server side through the editor, and when the terminal SDK is successfully connected to the server side and the server receives the page information sent by the terminal SDK, the web page data collector receives a page information acquisition notification (sent by the editor). The page information acquisition notice is sent by the server through the editor after the terminal SDK sends the page information of the page of the point to be buried to the server. Then, the webpage data collector feeds the page information of the page to be embedded back to the terminal SDK through the server, so that the terminal SDK puts the page information into the h5 window attribute of the terminal webpage window element, and new page information is transmitted to the server. In this way, the web page information stored by the current server is the page information containing the H5 page, so that the updated page information can be subsequently acquired by the web page data collector.

For example:

1. the terminal SDK calls a window, analytic agent, get visual DomList () function of the JS-SDK to inform the JS-SDK to acquire page information (page structure), and the JS-SDK calls an analytic Agenthybrid, onvisual DomList (string) function of the terminal SDK to return the page information (page structure) of the current website;

2. the terminal SDK puts the page information (page structure) into the h5_ view attribute of the WebView element, and uploads it to the server.

Further, when the embedded point information is transmitted among the web page end data collector, the web page editor, the server and the terminal SDK, and when the embedded point information is analyzed and the page is bound, if the current embedded point includes a Hybrid embedded point or the embedded point is bound according to the attribute, the terminal SDK needs to transmit the embedded point information to the JS-SDK, and the JS-SDK performs the binding of the H5 element.

Specifically, the web page data collector or the terminal SDK receives, through the editor, embedded point information containing Hybrid embedded points sent by the server, and binds the current page according to the current embedded point information (related to the above steps (12), (19), and B, S302). The method comprises the steps that embedded point information edited by a user is identified by an editor, page information obtained from a server is combined, when it is determined that the embedded point information contains Hybrid embedded points or the current embedded points are only bound in an attribute positioning mode, the current embedded points are marked to be Hybrid embedded points in the current embedded point information, updated embedded point information is sent to a terminal SDK through the server, the updated embedded point information is sent to a webpage end data collector through the server and the editor after the terminal SDK screens the Hybrid embedded points, and the embedded point information obtained by the webpage end data collector is information which is marked whether the embedded points are Hybrid embedded points or not.

For example:

1. when the editor stores the Hybrid embedded point, an is _ Hybrid field is added into an embedded point structure corresponding to the embedded point information and set to be 1, the embedded point structure is stored to a server, and then the server issues the embedded point structure to a terminal SDK;

2. and after screening the Hybrid embedded points, the terminal SDK sends the updated embedded point information to the JS-SDK (the JS-SDK judges whether the current embedded point is the Hybrid embedded point according to whether the is _ Hybrid field in the embedded point information is 1 or whether the embedded point is only bound in an attribute mode). The terminal SDK calls the window analysis agent oneventlist (event _ list) function of the JS-SDK to transfer the burial point information containing the Hybrid burial point. In addition, after the H5 page of the terminal SDK is loaded, the JS-SDK also calls an analysagenthybrid of the terminal SDK geteventlist () interface function to obtain the embedded point information containing the Hybrid embedded point.

Further, when the embedded point information is transmitted among the web page data collector, the web page editor, the server and the terminal SDK, after the embedded point information is analyzed and the page binding is completed, if the current embedded point is a Hybrid embedded point, the associated attribute of the terminal page element needs to be associated, and if the current embedded point is a non-Hybrid embedded point, the associated attribute of the H5 page element needs to be associated.

Specifically, in one embodiment, (which relates to the above steps (12), (19), and B, S302), (if it is determined that the buried point is a Hybrid buried point (JS-SDK determines whether the current buried point is a Hybrid buried point according to whether the is _ Hybrid field in the buried point information is 1 or whether the buried point is bound only in an attribute manner) when the buried point of the current page is bound, the associated element attribute stored in the terminal SDK about the current buried point will be called by the server side to take the associated element attribute containing the H5 page element as the associated element attribute of the current buried point.

For example: and if the current buried point is Hybrid, associating the attribute of the element of the terminal SDK. The child node of the related field contains a location field, the JS-SDK judges the attribute related to the terminal page element through the location field, and when an event is triggered, the AnysAgenthybrid-getProperty function of the terminal SDK is called to obtain the attribute of the related element of the current JS-SDK triggering buried point.

In another embodiment, (referring to the above steps (12), (19), and B, S302), (if it is determined that the buried point is a non-Hybrid buried point (JS-SDK determines whether the current buried point is a Hybrid buried point according to whether the is _ Hybrid field in the buried point information is 1 or whether the buried point is only bound in an attribute manner) when the buried point of the current page is bound, after the JS-SDK obtains the first notification, the buried point information including the attribute information of the current buried point associated element is fed back to the terminal SDK through the server side. When the terminal SDK detects that the current embedded point is triggered, a first notice is sent to the webpage data collector through the server.

For example: if the current buried point is non-Hybrid, the H5 page element needs to be associated. The related field child node contains H5_ path field, the terminal SDK judges the attribute related to the H5 page element through the field, when the event is triggered, the window, analysis, etc. of the JS-SDK is called to inform the terminal SDK of needing to obtain the related element attribute of the current buried point, and the JS-SDK calls the analysis, etc. on property interface function of the terminal SDK to return the related attribute value.

Further, when the transmission of the embedded point information is performed among the web page data collector, the web page editor, the server and the terminal SDK, the transmission protocol of the embedded point triggering information is improved for the four-terminal-based communication flow (involving the steps (14), (16), (21) and D, S203). Specifically, after the data collector at the webpage end detects that the current Hybrid embedded point is triggered, the corresponding embedded point triggering information is transmitted to the server through the terminal SDK.

For example: after the JS-SDK acquires the embedded point information corresponding to the Hybrid embedded point, the binding of the page elements and the embedded point information is executed, after the event is triggered, the JS-SDK calls an analysagentTrack interface function of the terminal SDK to transmit the embedded point triggering information, and at the moment, the terminal SDK reports the embedded point triggering information to the server side. In the Hybrid mode, the terminal SDK is used as a main body for sending the embedded point trigger information, the JS-SDK transmits the embedded point trigger information to the terminal SDK, and the terminal SDK performs supplementary processing again and then reports the information to the server side.

The invention discloses a visual point burying method and system based on JS-SDK. According to the method and the system, firstly, the points are buried in a webpage end visual editor selection mode, so that the problems of complex operation of the buried points and large reported data volume are solved; the page elements are positioned by using the attribute positioning mode, so that the problem of positioning failure caused by inconsistent positions of page elements of different versions is solved, the problem of list element point burying is solved by using the same-level point burying technology, and the point burying scheme under a complex service scene can be solved. In addition, the invention can embed the associated attribute information related to the embedded point elements in the embedded point information, collect richer data at the embedded points, further provide more types of data information for the data analysis stage, and simultaneously analyze the data collected by the embedded points from a multidimensional angle, thereby improving the accuracy of the data analysis result. In addition, the invention also provides a complete communication protocol capable of processing Hybrid embedded points, so that the visual embedded point method can be suitable for embedded point schemes under different service occasions (different operating systems).

The above description is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

It is to be understood that the disclosed embodiments of the invention are not limited to the particular structures, process steps, or materials disclosed herein but are extended to equivalents thereof as would be understood by those ordinarily skilled in the relevant arts. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting.

Reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. Thus, the appearances of the phrase "one embodiment" or "an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment.

Although the embodiments of the present invention have been described above, the above descriptions are only for the convenience of understanding the present invention, and are not intended to limit the present invention. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A visual point burying method based on JS-SDK comprises the following steps:

acquiring a page to be embedded by an editor, and activating a visual embedding mode of the page;

editing embedded points in a page, and transmitting embedded point information to a server through the editor;

acquiring a buried point list which is transmitted from the server and is related to a current buried point through the editor, and binding information in the buried point list to a current page in a non-deployment state;

when the editor is switched to a test mode, confirming the embedded point elements to complete the creation of page embedded points;

accessing a current page, and acquiring a built-in point in the current page from the server;

and binding the created embedded point information to the current page, and storing the embedded point trigger information in the server after the embedded point trigger.

2. A visual point burying method as claimed in claim 1, wherein in the point burying step in the editing page, editing is performed by circling page elements.

3. A visual embedding method according to claim 1 or 2, characterized in that the embedding information includes but is not limited to: the method comprises the steps of identifying a buried point element, the position of the buried point element in a page structure, associated attribute information of the buried point element, the positioning mode of the buried point element, the effective range of the buried point, the effective range of the page and the effective version, wherein the positioning mode of the buried point element is selected from one or a combination of a new _ path positioning mode, an attribute positioning mode and a peer element positioning mode.

4. The visual burying method of claim 3, wherein in the step of binding the created burying point information to the current page, comprising:

analyzing the created buried point information related to the current page, positioning the target buried point element according to a defined element positioning mode, and acquiring the correlation attribute of the target buried point element, wherein,

when the defined element positioning modes are multiple, if the embedded point element positioning results obtained after each positioning treatment are the same, the element positioning operation of the current page is successful, and the embedded point element positioning result is used as the target embedded point element; otherwise, it fails.

5. The visual buried point method according to any one of claims 1-4, characterized in that after the step of binding the created buried point information to the current page, the method further comprises:

and after the target embedded point element is successfully positioned, adding an event monitor for the target embedded point element.

6. A visual embedding method as claimed in any one of claims 1 to 5, wherein the method further comprises:

the method comprises the steps that the server is connected through an editor, and a page information acquisition notice is obtained when a terminal SDK is connected with the server, wherein the page information acquisition notice is sent by the server after the terminal SDK sends page information of a page of a point to be buried to the server;

and feeding the page information of the page to be embedded point back to the terminal SDK through the server, so that the terminal SDK puts the page information into the h5 window attribute of the window element of the terminal webpage, and transmitting the new page information to the server.

7. The visual embedding method of claim 6, wherein in the embedding binding process, the method further comprises:

receiving embedded point information containing Hybrid embedded points, and binding pages, wherein the editor identifies the embedded point information, marks the current embedded point as the Hybrid embedded point in the embedded point information when the embedded point information contains the Hybrid embedded points or the embedded point is only bound in a mode of positioning according to attributes, and sends the updated embedded point information to the terminal SDK through the server so as to be sent to the webpage end data collector through the server after the terminal SDK screens out the Hybrid embedded points.

8. The visual embedding method of claim 7,

if the current embedded point is a Hybrid embedded point, calling the associated element attribute about the current embedded point stored in the terminal SDK through the server;

and if the current embedded point is a non-Hybrid embedded point, after a first notification is obtained, feeding back the embedded point information containing the associated element attribute information of the current embedded point to the terminal SDK through the server, wherein when the terminal SDK detects that the current embedded point is triggered, the server sends the first notification to the webpage data collector.

9. The visual embedding method of claim 7 or 8, wherein after the step of receiving and binding the Hybrid embedding point, the method further comprises the following steps:

and after the current Hybrid embedded point is triggered, transmitting corresponding embedded point triggering information to the server through the terminal SDK.

10. A JS-SDK based visual point burying system, which is characterized by performing the method of any one of claims 1-9, and comprises:

the system comprises a webpage end data collector, a server and a server, wherein the webpage end data collector is used for firstly obtaining a page to be embedded by an editor, activating a visual embedded point mode of the page, then editing embedded points in the page, transmitting embedded point information to the server by the editor, then obtaining an embedded point list which is transmitted from the server and is related to a current embedded point by the editor, binding information in the embedded point list to the current page in a non-deployment state, confirming embedded point elements to complete the creation of embedded points of the page when the editor is switched to a test mode, accessing the current page, obtaining the embedded points which are created in the current page from the server, and finally binding the created embedded point information to the current page so as to store embedded point trigger information in the server after the embedded point is triggered;

the editor is communicated with the webpage data collector and the server through a PostMessage; and

and the server is communicated with the webpage data collector in an Http or Http mode and is used for storing and transmitting page information of website pages, created embedded point information in each page and embedded point triggering information of created embedded points in each page.