CN112286501A

CN112286501A - Method and device for embedding point in page of terminal equipment and storage medium

Info

Publication number: CN112286501A
Application number: CN202011091070.4A
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-10-13
Filing date: 2020-10-13
Publication date: 2021-01-29

Abstract

The application discloses a method and a device for embedding points in a page of terminal equipment and a storage medium. Wherein, the method comprises the following steps: determining page information of a page to be buried, wherein the page information is generated by an SDK integrated by terminal equipment; sending the page information to a server, wherein the server is connected with a client for carrying out embedded point design; receiving embedded point information corresponding to a to-be-embedded point page from a server, wherein the embedded point information is generated by a client according to the page information; and deploying the buried points on the page of the point to be buried of the terminal equipment through the SDK according to the buried point information.

Description

Method and device for embedding point in page of terminal equipment and storage medium

Technical Field

The present application relates to the field of internet point burying technologies, and in particular, to a method, an apparatus, and a storage medium for point burying of a page of a terminal device.

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 click information statistics aiming at the page elements is used for analyzing user interaction and counting user behaviors, and plays a great role in continuous optimization of products. The data acquisition process is approximately to design a buried point, integrate an SDK, trigger the buried point and report a server, and the current data acquisition mode mainly comprises code acquisition, full buried point acquisition, visual acquisition and the like. The code collection rough flow provides data statistics requirements for operators, product personnel design embedded points, developers call SDK collection interfaces to implant the embedded points, new versions are packaged and released again, and the operators analyze the data after reporting. 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. At present, the visualization acquisition technology of commercial SDK mainly comprises visualization based on full-buried points, visualization based on equipment-side selection and visualization based on editor selection. The data volume is large, and the reported data only comprises element clicks and cannot report element related information. The visualization based on equipment end selection is used for operating and embedding points on the mobile phone equipment, the operation difficulty is high, and the complicated point embedding requirements cannot be realized due to the screen size and the interaction mode. Visualization based on editor selection is in the early development stage, and the existing solution only collects element click events and cannot meet the complex requirements.

Aiming at the technical problem that accurate point burying can not be carried out on the terminal equipment when the point burying technology is used for carrying out data acquisition on the terminal equipment in the prior art, an effective solution is not provided at present.

Disclosure of Invention

The embodiment of the disclosure provides a method and a device for embedding points in a page of a terminal device and a storage medium, so as to at least solve the technical problem that accurate point embedding cannot be performed on the terminal device when data acquisition is performed on the terminal device by using a point embedding technology in the prior art.

According to an aspect of the embodiments of the present disclosure, there is provided a method for dotting a page of a terminal device, including: determining page information of a page to be buried, wherein the page information is generated by an SDK integrated by terminal equipment; sending the page information to a server, wherein the server is connected with a client for carrying out embedded point design; receiving embedded point information corresponding to a to-be-embedded point page from a server, wherein the embedded point information is generated by a client according to the page information; and deploying the buried points on the page of the point to be buried of the terminal equipment through the SDK according to the buried point information.

According to another aspect of the embodiments of the present disclosure, there is also provided a method for dotting a page of a terminal device, including: receiving page information sent by terminal equipment, wherein the page information is generated by an SDK (software development kit) integrated by the terminal equipment according to the information of a page of a point to be buried; sending the page information to a client for carrying out embedded point design; receiving embedded point information generated according to page information from a client, wherein the embedded point information is used for embedding points in a to-be-embedded point page; and sending the buried point information to the terminal equipment.

According to another aspect of the embodiments of the present disclosure, there is also provided a method for dotting a page of a terminal device, including: receiving and displaying page information which is sent by a server and needs to be subjected to embedded point design, wherein the page information is page information of terminal equipment communicated with the server, and the page information is generated by an SDK integrated with the terminal equipment; responding to the triggering operation of an operator for editing the embedded points of the page information, and determining the embedded point information corresponding to the page information; and sending the buried point information to a server.

According to another aspect of the embodiments of the present disclosure, there is also provided a storage medium including a stored program, wherein the method of any one of the above is performed by a processor when the program is executed.

According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for dotting a page of a terminal device, including: the page information determining module is used for determining page information of a to-be-buried point page, wherein the page information is generated by an SDK integrated by the terminal equipment; the system comprises a page information sending module, a page information sending module and a server, wherein the page information sending module is used for sending page information to the server, and the server is connected with a client side used for carrying out embedded point design; the embedded point information receiving module is used for receiving embedded point information corresponding to a to-be-embedded point page from a server, wherein the embedded point information is generated by a client according to the page information; and the embedded point deployment module is used for deploying embedded points on the page of the to-be-embedded point of the terminal equipment through the SDK according to the embedded point information.

According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for dotting a page of a terminal device, including: the page information receiving module is used for receiving page information sent by the terminal equipment, wherein the page information is generated by an SDK (software development kit) integrated by the terminal equipment according to the information of the page of the point to be buried; the page information sending module is used for sending the page information to a client side for carrying out embedded point design; the embedded point information receiving module is used for receiving embedded point information generated according to the page information from the client, wherein the embedded point information is used for embedding points in a to-be-embedded point page; and the buried point information sending module is used for sending the buried point information to the terminal equipment.

According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for dotting a page of a terminal device, including: the page information display module is used for receiving and displaying page information which is sent by the server and needs to be subjected to embedded point design, wherein the page information is page information of terminal equipment communicated with the server, and the page information is generated by an SDK integrated with the terminal equipment; the embedded point information editing module is used for responding to the triggering operation of an operator for editing embedded points of the page information and determining embedded point information corresponding to the page information; and the embedded point information sending module is used for sending the embedded point information to the server.

According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for dotting a page of a terminal device, including: a first processor; and a first memory coupled to the first processor for providing instructions to the first processor to process the following processing steps: determining page information of a page to be buried, wherein the page information is generated by an SDK integrated by terminal equipment; sending the page information to a server, wherein the server is connected with a client for carrying out embedded point design; receiving embedded point information corresponding to a to-be-embedded point page from a server, wherein the embedded point information is generated by a client according to the page information; and deploying the buried points on the page of the point to be buried of the terminal equipment through the SDK according to the buried point information.

According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for dotting a page of a terminal device, including: a second processor; and a second memory coupled to the second processor for providing instructions to the second processor to process the following processing steps: receiving page information sent by terminal equipment, wherein the page information is generated by an SDK (software development kit) integrated by the terminal equipment according to the information of a page of a point to be buried; sending the page information to a client for carrying out embedded point design; receiving embedded point information generated according to page information from a client, wherein the embedded point information is used for embedding points in a to-be-embedded point page; and sending the buried point information to the terminal equipment.

According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for dotting a page of a terminal device, including: a third processor; and a third memory coupled to the third processor for providing instructions to the third processor to process the following processing steps: receiving and displaying page information which is sent by a server and needs to be subjected to embedded point design, wherein the page information is page information of terminal equipment communicated with the server, and the page information is generated by an SDK integrated with the terminal equipment; responding to the triggering operation of an operator for editing the embedded points of the page information, and determining the embedded point information corresponding to the page information; and sending the buried point information to a server.

In the embodiment of the disclosure, page information of a page to be buried on a terminal device is determined first, and then a buried point designer may design a buried point for the page information at a client by using an editor and generate buried point information. And finally, the terminal equipment deploys the buried points on the page of the point to be buried according to the buried point information. Therefore, compared with the prior art, when the design of the embedded points is carried out on the page on the terminal equipment, the embedded points can be accurately designed according to the page information according to the scheme, the embedded points do not need to be completely embedded, and therefore the data collection amount can be reduced. In addition, the embedded point can be visually designed for the page information through an editor of the client, and the embedded point can be positioned more accurately. Therefore, the technical effect of accurately embedding points on the terminal equipment is achieved. And then solved the utilization among the prior art and buried a technical problem that some technique can't carry out the accurate technical problem that buries a little on terminal equipment when carrying out data acquisition on terminal equipment.

Drawings

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the disclosure and together with the description serve to explain the disclosure and not to limit the disclosure. In the drawings:

fig. 1 is a hardware block diagram of a computing device for implementing the method according to embodiment 1 of the present disclosure;

fig. 2 is a schematic diagram of a system for dotting a page of a terminal device according to embodiment 1 of the present disclosure;

FIG. 3 is a schematic diagram of a system interaction process according to embodiment 1 of the present disclosure;

fig. 4 is a schematic flowchart of a method for dotting a page of a terminal device according to a first aspect of embodiment 1 of the present disclosure;

fig. 5 is a schematic diagram of an interaction process between a terminal device and a server according to embodiment 1 of the present disclosure;

fig. 6 is a schematic diagram of a tree structure of a page element according to embodiment 1 of the present disclosure;

fig. 7 is a schematic diagram of a page structure according to embodiment 1 of the present disclosure;

fig. 8 is a schematic diagram of a page structure having H5 according to embodiment 1 of the present disclosure;

fig. 9 is a flowchart illustrating a method for dotting a page of a terminal device according to a second aspect of embodiment 1 of the present disclosure;

fig. 10 is a flowchart illustrating a method for dotting a page of a terminal device according to a third aspect of embodiment 1 of the present disclosure;

fig. 11 is a schematic diagram of an apparatus for dotting a page of a terminal device according to a first aspect of embodiment 2 of the present disclosure;

fig. 12 is a schematic diagram of an apparatus for dotting a page of a terminal device according to a second aspect of embodiment 2 of the present disclosure;

fig. 13 is a schematic diagram of an apparatus for dotting a page of a terminal device according to a third aspect of embodiment 2 of the present disclosure;

fig. 14 is a schematic diagram of an apparatus for dotting a page of a terminal device according to a first aspect of embodiment 3 of the present disclosure;

fig. 15 is a schematic diagram of an apparatus for dotting a page of a terminal device according to a second aspect of embodiment 3 of the present disclosure; and

fig. 16 is a schematic diagram of an apparatus for dotting a page of a terminal device according to a third aspect of embodiment 3 of the present disclosure.

Detailed Description

In order to make those skilled in the art better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure. It is to be understood that the described embodiments are merely exemplary of some, and not all, of the present disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example 1

According to the present embodiment, there is also provided an embodiment of a method for dotting a page of a terminal device, it should be noted that the steps illustrated in the flowchart of the drawings may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.

The method embodiments provided by the present embodiment may be executed in a mobile terminal, a computer terminal, a server or a similar computing device. Fig. 1 shows a hardware block diagram of a computing device for implementing a method for dotting a page of a terminal device. As shown in fig. 1, the computing device may include one or more processors (which may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory for storing data, and a transmission device for communication functions. Besides, the method can also comprise the following steps: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a power source, and/or a camera. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration and is not intended to limit the structure of the electronic device. For example, the computing device may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

It should be noted that the one or more processors and/or other data processing circuitry described above may be referred to generally herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part in software, hardware, firmware, or any combination thereof. Further, the data processing circuitry may be a single, stand-alone processing module, or incorporated in whole or in part into any of the other elements in the computing device. As referred to in the disclosed embodiments, the data processing circuit acts as a processor control (e.g., selection of a variable resistance termination path connected to the interface).

The memory may be configured to store a software program and a module of application software, such as a program instruction/data storage device corresponding to the method for dotting a page of a terminal device in the embodiment of the present disclosure, and the processor executes various functional applications and data processing by running the software program and the module stored in the memory, that is, implements the method for dotting a page of a terminal device of the application program. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory located remotely from the processor, which may be connected to the computing device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device is used for receiving or transmitting data via a network. Specific examples of such networks may include wireless networks provided by communication providers of the computing devices. In one example, the transmission device includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

The display may be, for example, a touch screen type Liquid Crystal Display (LCD) that may enable a user to interact with a user interface of the computing device.

It should be noted here that in some alternative embodiments, the computing device shown in fig. 1 described above may include hardware elements (including circuitry), software elements (including computer code stored on a computer-readable medium), or a combination of both hardware and software elements. It should be noted that FIG. 1 is only one example of a particular specific example and is intended to illustrate the types of components that may be present in a computing device as described above.

Fig. 2 is a schematic diagram of a system for dotting a page of a terminal device according to this embodiment. Referring to fig. 2, the system includes: the system comprises a server 200, a terminal device 210 and a client 220, wherein the number of the terminal devices can be multiple, the server 200 is respectively communicated with the terminal device 210 and the client 220, the client 220 runs an editor for buried point design, and the page of the terminal device 210 can be visually designed for buried points. It should be noted that the server 200, the terminal device 210, and the client 220 in the system may all be adapted to the above-described hardware structure.

In practical applications, the system of the terminal device 210 is, for example, an Android system, and is integrated with an SDK. The above system requires three-terminal support: the system comprises a server (server 200), a web page editor (client 220) and an SDK (terminal device 210), wherein the communication between the server and the editor, and the communication between the server and the SDK use a visual communication data protocol, when a buried point is edited (hereinafter referred to as an editing stage), the terminals use a WebSocket (hereinafter referred to as ws) mode to communicate, and after the buried point is deployed (hereinafter referred to as an effective stage), the SDK obtains the buried point from the server in an Http mode.

Referring to fig. 3, the main task of the editing phase is to create a buried point, and the operation flow is as follows:

1. opening a buried point editor, connecting the editor to a server through ws, and reporting editor information; 2. opening a program integrating the SDK in the mobile phone, shaking the mobile phone to trigger the SDK to be connected to a server through ws, and reporting equipment information; 3. the server side sends the equipment information reported by the SDK to an editor; 4. the editor displays the equipment information, and after the user selects the equipment, the editor sends the selected equipment information to the server; 5. and the server sends an instruction for acquiring the page structure information to the selected equipment. The 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 a server; 7. the server side sends the page information to an editor, and the editor displays the page information; 8. the user edits the embedded points in a mode of circling page elements, and the embedded point information is sent to the server after being stored; 9. the server side stores the embedded point in a database, marks the embedded point as a non-deployment state and simultaneously sends the embedded point to the SDK; binding the embedded point information to a current page element by the SDK; 11. the user clicks page elements of the embedded points in the mobile phone program, the embedded points are triggered, and embedded point triggering information is sent to the server; 12. the server side sends the embedded point triggering information to an editor; 13. the editor displays prompt information of triggering the buried point, and a user confirms that the buried point is successful through the prompt information; 14. and clicking a deployment button by the user to inform the server that the buried point is in a deployment state.

In addition, referring to fig. 5, the validation phase is a process of issuing the deployed burial point to the terminal device in the whole network, and the flow is as follows: 1. the method comprises the steps that a program integrated with an SDK on a mobile phone is cold started, and the SDK obtains deployed buried points from a server through Http; binding the embedded point information to a current page element by the SDK; 3. the user clicks page elements of the embedded points in the mobile phone program, the embedded points are triggered, and embedded point information is sent to the server; 4. the server side stores the information as an acquisition result to a database for data analysis.

In the operating environment, according to the first aspect of the present embodiment, a method for dotting a page of a terminal device is provided, and the method is implemented by the terminal device 210 shown in fig. 2. Fig. 4 shows a flow diagram of the method, which, with reference to fig. 4, comprises:

s402: determining page information of a page to be buried, wherein the page information is generated by an SDK integrated by terminal equipment;

s404: sending the page information to a server, wherein the server is connected with a client for carrying out embedded point design;

s406: receiving embedded point information corresponding to a to-be-embedded point page from a server, wherein the embedded point information is generated by a client according to the page information; and

s408: and according to the embedded point information, deploying the embedded points on the page of the to-be-embedded point of the terminal equipment through the SDK.

As described in the background art, the current data collection methods mainly include code collection, full-buried point collection, visual collection, and the like. The code collection rough flow provides data statistics requirements for operators, product personnel design embedded points, developers call SDK collection interfaces to implant the embedded points, new versions are packaged and released again, and the operators analyze the data after reporting. 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. At present, the visualization acquisition technology of commercial SDK mainly comprises visualization based on full-buried points, visualization based on equipment-side selection and visualization based on editor selection. The data volume is large, and the reported data only comprises element clicks and cannot report element related information. The visualization based on equipment end selection is used for operating and embedding points on the mobile phone equipment, the operation difficulty is high, and the complicated point embedding requirements cannot be realized due to the screen size and the interaction mode. Visualization based on editor selection is in the early development stage, and the existing solution only collects element click events and cannot meet the complex requirements.

For the technical problem in the background art, in step S402, the terminal device 210 according to the technical solution of the present embodiment first determines page information of a page to be buried. The page of the to-be-buried point is, for example, an APP or a webpage on the terminal device 210, and in order to acquire data generated by the page, the page of the to-be-buried point that needs to be buried is determined first. The terminal device 210 is preferably a terminal device of an Android system, such as a smart phone or a tablet, and the page information may be generated through an SDK integrated on the terminal device 210. In a preferred example, the page information includes, for example, information such as a picture of the page, a page structure, and the like, and may also include other page information, which is not specifically limited herein.

In one embodiment, the page information format is as follows:

the type field tells the server that the message is page information, pages are arrays, each array element represents one page (there may be multiple page presentations at present, for example, a dialog box pops up in a current Activity page, two pages are provided), page _ name is a page name, picture is data corresponding to a page picture, views is an array, represents all page elements below the current page, each array element contains a plurality of attribute information of the corresponding page element, for example, id is used for identifying an element, clickable represents whether a click event can be triggered, visible is visible or not, x _ page, y _ page represents x and y coordinates of the element in the page, and x and y represent x, y coordinates in a parent element, w and h are width and height. child _ id is a child element, text is text content, and classes is a class inheritance relationship. location indicates how to locate the element in the page. location is an array, which is also used in the buried point binding, and each array element represents a page element, from bottom to top, the element and the parent element of the element, through to the root element. The whole page structure can be imagined as a tree topology, representing the parent-child relationships between elements.

Further, in step S404, the terminal device 210 transmits the page information generated by the SDK to the server 200. The server 200 is connected to the client 220, the server 200 can send the page information to the client 220, an editor for designing buried points is run on the client 220, and buried point designers can design buried points for the page information by using the editor.

Further, in step S406, after the client 220 performs the buried point design according to the page information, the buried point information is generated, and then the client 220 feeds back the buried point information to the server 200, so that the server 200 sends the buried point information to the terminal device 210. In this case, the terminal device 210 may receive the burial point information corresponding to the to-be-buried point page from the server 200.

In one embodiment, the format of the buried point information is as follows:

the id uniquely identifies the buried point, event _ type is a buried point type, location is the position of a buried point element in a page structure, and related attributes reported when the buried point is triggered are an array, which means that multiple attributes can be reported. The prop _ name is used for identifying which attribute is, the prop _ type is an attribute type, the key is used for triggering the buried point and then reporting data to identify the attribute, the target is used for positioning the associated element, the triggering buried element and the associated element have the nearest parent element, step is the number of steps of the buried point triggering element for backtracking to the parent element, and the step is used for positioning the associated element through the location field after backtracking to the parent element. The props _ binding indicates that the element is located by attribute, as distinguished from location, which will be described in detail later. binding _ range specifies the range of buried point effects, pages indicate which pages are effective, and versions indicate which versions are effective.

Finally, in step S408, the terminal device 210 may deploy the buried point on the page of the terminal device to be buried point through the SDK according to the buried point information. Namely, the buried point is deployed on the page of the to-be-buried point.

Therefore, in this way, firstly, the page information of the page to be buried on the terminal device is determined, and then, a buried point designer can design buried points for the page information by using an editor at a client side and generate buried point information. And finally, the terminal equipment deploys the buried points on the page of the point to be buried according to the buried point information. Therefore, compared with the prior art, when the design of the embedded points is carried out on the page on the terminal equipment, the embedded points can be accurately designed according to the page information according to the scheme, the embedded points do not need to be completely embedded, and therefore the data collection amount can be reduced. In addition, the embedded point can be visually designed for the page information through an editor of the client, and the embedded point can be positioned more accurately. Therefore, the technical effect of accurately embedding points on the terminal equipment is achieved. And then solved the utilization among the prior art and buried a technical problem that some technique can't carry out the accurate technical problem that buries a little on terminal equipment when carrying out data acquisition on terminal equipment.

Optionally, before determining the page information of the page to be buried, the method further includes: determining equipment information of the terminal equipment through the SDK, and sending the equipment information to a server; and receiving an acquisition instruction for acquiring the page information of the page of the to-be-buried point from the server, wherein the acquisition instruction is generated by the server according to the confirmation information of the selection equipment sent by the client.

Specifically, in the present solution, before determining the page information, the terminal device 210 further needs to determine the device information of the terminal device 210 through the SDK, for example: device model, version number, and the like. Further, the terminal device 210 transmits the device information to the server 200. Further, the terminal device 210 receives an obtaining instruction for obtaining the page information of the to-be-buried-point page from the server 200, where the obtaining instruction is generated by the server 200 according to the confirmation information of the selected device sent by the client 220, for example: the format of the fetch instruction is as follows:

the type field specifies the instruction type, the value of the page _ config field is an array, each array element represents a page element, specifies which information of the page element needs to be obtained, and by what method. The above example is to obtain clickable attribute of an android. In actual operation, the server 200, after receiving the device information, sends the device information to the client 220, where the device information, which may be a plurality of terminal devices, is sent to the client 220. The site burying personnel can select terminal equipment capable of performing site burying from a plurality of pieces of equipment information, such as: the selected terminal device is the terminal device 210, and then the selected device information (terminal device 210 information) is transmitted to the server 200. Then, the server 200 may generate an acquisition instruction to acquire the page information according to the selected device information, and transmit the acquisition instruction to the terminal device 210. In this case, the terminal device 210 may receive the acquisition instruction and generate the page information by the SDK according to the acquisition instruction. Therefore, the device information is firstly reported to the client, then the designer can select the terminal device for the embedded point design, and finally the instruction for acquiring the page information is sent to the selected terminal device. Therefore, the terminal equipment for embedding the points can be selectively determined according to the equipment information, and time and cost are saved.

Optionally, deploying a buried point on a to-be-buried point page of the terminal device through the SDK according to the buried point information, including: binding the embedded point information with the page elements of the page to be embedded point through the SDK; responding to a first trigger operation of a user for testing a buried point, determining first trigger information and sending the first trigger information to a server; receiving a deployment instruction from a server, wherein the deployment instruction is generated by the server according to prompt information sent by a client, and the prompt information is used for indicating that a buried point corresponding to first trigger information is successful; and deploying the buried points on the page of the point to be buried of the terminal equipment according to the deployment instruction.

Specifically, in the operation of deploying the embedded point on the to-be-embedded point page of the terminal device through the SDK according to the embedded point information, the terminal device 210 firstly binds the embedded point information with the page element of the to-be-embedded point page through the SDK. For example: if the embedded point information indicates that the page element 1 is embedded, the SDK may bind the embedded point information and the page element 1, and the binding operation may be regarded as a preliminary deployment embedded point. Further, after the information of the embedded point is bound to the page element of the page to be embedded, it is required to test whether the embedded point is successfully detected, where the test may be performed in a manner that a user of the terminal device 210 triggers "page element 1" on the page to be embedded (first triggering operation). In this case, the terminal device 210 may determine first trigger information (e.g., data generated after triggering) and transmit the first trigger information to the server 200 in response to a first trigger operation of the user for testing the buried site. After the server 200 receives the first trigger information, the information needs to be fed back to the client 220, and the site designer determines whether the site is successfully buried according to the first trigger information. After determining that the burial point is successful, the client 220 may send a prompt message to the server 200, where the prompt message is used to indicate that the burial point is successful, and then the server 200 may feed the prompt message back to the terminal device 210. Therefore, the user can complete the deployment of the buried point according to the prompt message, for example: and clicking a deployment button by a user to inform the server that the embedded point is in a deployment state, thereby completing the embedded point operation. Therefore, the buried point needs to be tested before being deployed, and therefore the reliability of the buried point can be improved.

Optionally, binding the embedding point information with the page element of the page to be embedded through the SDK includes: determining position information contained in the embedded point information, wherein the position information is used for indicating the position of a page element needing embedded points in a page to be embedded; determining the positions of the page elements according to the position information; and binding the buried point information with the page element according to the determined position.

In the operation of binding the embedded point information with the page element of the page to be embedded through the SDK, a location positioning (location positioning) mode may be adopted. Specifically, the terminal device 210 first determines the position information included in the buried point information, where the position information is used to indicate the position of the page element that needs to be buried in the page to be buried. And then, determining the position of the page element according to the position information, and finally binding the embedded point information with the page element according to the determined position. In a specific example, the page element is located according to the location, that is, by matching the topological location, the page structure can be abstracted to a tree structure, as shown in fig. 6, the left side is the page tree structure, and the right side is the corresponding location field. When searching for the page element specified by the location field, the SDK matches the element 1 from the root node of the page tree (compare the attributes of the page element, such as the name of the element, the location index, the type of the element, etc., in the parent element with the response information of the child element in the location array), continues the following matching in a way of preorder traversal, and reports that the matching fails in the midway until the last node 5 in the location is successfully matched, that is, locates the final buried point element, and then binds the buried point information with the buried point element (located page element).

Optionally, binding the embedding point information with the page element of the page to be embedded through the SDK includes: determining attribute information contained in the embedded point information, wherein the attribute information is used for indicating the attribute of a page element needing embedded points in a page to be embedded; and determining page elements according to the attribute information, and binding the embedded point information with the determined page elements.

Specifically, in the operation of binding the embedded point information with the page element of the page to be embedded through the SDK, an attribute positioning mode can also be adopted. Specifically, the terminal device 210 first determines attribute information (i.e., a tips _ binding field) included in the embedded point information, where the attribute information is used to indicate an attribute of a page element that needs to be embedded in the to-be-embedded point page, then determines the page element according to the attribute information, and binds the embedded point information with the determined page element. In one embodiment, per attribute positioning is according to the prop _ binding field, so the position of elements in the page structure can be ignored, referring to the following format:

the SDK traverses the whole page structure tree in a way of sequencing traversal from a page root node when positioning elements, if the type (class) of the current element is android, appCompat, widget, AppcatButton, matching is successful, and multiple elements can be successfully matched, so that clicking the elements can trigger the buried point. The value of prop _ name is an enumerated type, as follows:

then all elements of the current page whose text content is "ok" will be successfully matched. If two positioning modes according to location and attribute are simultaneously specified in the embedded point information, the SDK can simultaneously execute the two positioning algorithms, and the positioning can be successfully carried out only if all the positioning algorithms are matched. The algorithm for positioning according to location 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, and the embedded point triggering is unsuccessful if the page is subjected to page reprinting. 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). The two positioning modes are flexibly used when the embedded point is edited, so that a complex service scene can be met. The element is positioned by using an attribute positioning mode, and the problem of positioning failure caused by inconsistent positions of page elements of different versions is solved.

Optionally, binding the embedding point information with the page element of the page to be embedded through the SDK includes: determining page elements through the same-level element positioning according to the embedded point information; and binding the buried point information with the page elements.

Specifically, in the operation of binding the embedded point information with the page element of the page to be embedded through the SDK, a peer element positioning function may also be adopted. Specifically, the terminal device 210 first determines the page element through peer element positioning according to the embedded point information, and further binds the embedded point information with the page element. In a specific example, referring to fig. 7, fig. 7 is a typical list class element, the number of sub-elements may not be fixed, the underlying implementation in sliding the list employs an element multiplexing technique (i.e. removing invisible elements, modifying the appearance of the elements, and adding the elements into the list, so as to implement the visual effect of sliding, such elements currently supported include ListView, cycleview, and ViewPager, and sub-class elements of these elements), and if the user wants to count the click condition of "button 1", the click condition of row 1, or the click condition of all rows (distinguished by associated title or msg info), the peer positioning function needs to be used. The technical details of the list fixed row burial point and the list same-level burial point are described below.

The list fixes the row burial, such as the user wishes to bury on the button in the first row (i.e., "button 0"), and if the list slides resulting in the first row being removed, the row in which "button 2" is located in the visual field becomes the first row and the burial cannot be triggered. In this case, the format of the buried point location issued by the server is as follows:

the row field of the fourth row indicates the binding of the row (starting from 0), the SDK determines that the embedded point is related to the list class element for the ListView through the class field of the third row, and determines that the first row needs to be bound through the row field of the fourth row.

And (3) burying points at the same level of the list, if a user wants to bury all buttons of the list class and report titles in the same line with the buttons, in this case, the only difference between the location issued by the server and the above is that no row field exists, and the SDK determines to bind all buttons matched with the location under the list according to the lack of the row field. And triggering the buried point after all the buttons are clicked, positioning the buried point to the position of the associated element of the line according to the related field, and acquiring the title attribute. After the positioning is successful, an event monitor is added to the element through a system function setaccessinitydelegate, and the SDK can acquire the event after the user clicks the element to complete the deployment of the buried point.

Optionally, after the embedding point is deployed on the page of the point to be embedded of the terminal device through the SDK, the method further includes: responding to a second trigger operation of the user for testing the buried point, and determining second trigger information, wherein the second trigger information is used for indicating the buried point triggered by the user; and sending the second trigger information to the server.

Specifically, after the embedded point is deployed on the page of the terminal device to be embedded point through the SDK, that is, after the embedded point is successfully deployed, the terminal device 210 may determine the second trigger information in response to a second trigger operation of the user for testing the embedded point. Since the buried point is already deployed, in a case where the user triggers an element of the buried point in the page of the buried point, the terminal device 210 may determine second trigger information, that is, information triggering the page element of the buried point, in response to a trigger operation (second trigger operation) of the user. Referring to fig. 5, the terminal device 210 sends the second trigger information to the server 200 for storage and data analysis.

Optionally, the determining, in response to a second trigger operation of the user for testing the buried point, second trigger information includes: responding to a second trigger operation of the user for testing the buried point, and determining the triggered buried point; determining element attribute information related to the page element corresponding to the triggered buried point; and determining second trigger information according to the triggered buried point and the element attribute information.

Specifically, the page elements in the page correspond to element attribute information, after the triggered buried point is determined, element attribute information related to the page element corresponding to the triggered buried point can also be determined, and finally, second trigger information is determined according to the triggered buried point and the element attribute information. In a specific example, for example, the embedded point related attribute is stored in a related field, taking the previous list of the same-level embedded points as an example, the embedded point element is a local row button, the associated element is a local row title, and the related field is:

referring to fig. 7, for example: the second trigger operation is "button 1", and the element attribute information corresponding to the button 1 is title1, the SDK traces up to its parent element linear layout according to the step field, then finds the element "title 1" according to the location field, and obtains its text (i.e., the element attribute information) through the function getText. Therefore, the second trigger information can contain element attribute information, and the technical problem that the collected data is not rich can be solved.

In addition, for example, the data format reported to the service server 200 is as follows:

optionally, determining page information of the page to be buried, further comprising: and determining the page information of the page of the point to be buried according to the page elements of the dialogue frame type contained in the page of the point to be buried.

Specifically, the visualization embedding tool in the market only supports Activity type page embedding, and besides, non-Activity pages such as Dialog boxes (Dialog), PopupWindow and the like are widely used and need to be compatible. Pages in the Android system are called Window when being realized at the bottom layer, whether Activity, Dialog, PopupWindow and the like are realized through Window, the class for managing the Windows is called Window manager Global, the class has a list for storing the pages corresponding to the Windows, the list is replaced by a Java reflection method, the function of monitoring the change of the list is realized, the display and exit of the pages are sensed, then related page information is sent to a server, and finally an editor displays the page information, so that the selection and binding of page elements are realized. The scheme can also determine the page information of the page to be buried according to the page elements of the dialogue frame type contained in the page to be buried, namely: and (5) carrying out dotting on the page elements of the dialog box type. Therefore, the technical problem of embedding points of non-Activity pages such as Dialog boxes (Dialog), Popup Window and the like is solved by modifying the system type WindowManagerGlobal.

Optionally, the to-be-buried point page includes H5 page, and determining page information of the to-be-buried point page includes: determining first page information of a page of the terminal equipment through an SDK (software development kit) of the terminal equipment, and determining second page information of an H5 page through a JavaScript SDK; and determining the page information of the page to be buried according to the first page information and the second page information.

Specifically, referring to fig. 8, the Android native page and the H5 page (with the Android WebView element as a container) are not in the same page structure, development languages are different, such scenes also have a buried point statistical requirement, and such a buried point is referred to herein as a Hybrid buried point. In the operation of determining the page information of the to-be-buried point page, the terminal device 210 may determine, through the SDK of the terminal device, first page information of the page of the terminal device, and determine, through the JavaScript SDK, second page information of the H5 page. And then, determining the page information of the page to be buried according to the first page information and the second page information. In the concrete implementation, in order to meet the Hybrid demand, not only the Android SDK needs to be supported, but also a JavaScript SDK (JS SDK for short) needs to be added to the H5 page. Hybrid embedded points are realized through data transmission of SDKs at two ends, transmitted data mainly comprise page structures, embedded point information, cross-platform correlation attributes and embedded point trigger information, and a system interface provided by Android WebView is adopted for data transmission. Before editing a buried point, firstly, sending a page structure to a server (step 6 in an editing stage), and if a current page contains an H5 page, merging H5 page information into the current page, which is specifically implemented as follows:

1. the Android SDK calls a window, analysis agent, get visual domlist () of the jssdk to notify that a page structure is to be obtained, and the jssdk calls an analysis agent hybrid, onvisual domlist (string) of the Android SDK to return the page structure;

2. and the Android SDK puts the page structure into the h5_ view attribute of the WebView element and uploads the page structure to the server.

Transmitting buried point information: the previous step 10 of the editing phase and the previous step 2 of the validation phase are processes for binding the burial points, if the current burial point includes a Hybrid burial point, or the burial point is bound according to attributes, the Android SDK needs to transmit the burial point information to the JS SDK, and the JS SDK performs the binding of the H5 element:

1. when the editor stores the Hybrid embedded point, an is _ Hybrid field is added into the embedded point structure and is set to be 1, the embedded point structure is stored to the server side, and the server side issues the Android SDK;

2. and the Android SDK screens the Hybrid embedded point and sends the Hybrid embedded point to the JS SDK (judging according to the fact that the is _ Hybrid is 1 or the embedded point only contains attribute binding). The Android SDK calls the window, analysis agent, oneeventlist (event _ list) of the jssdk to transfer the Hybrid buried point, and in addition, after the H5 page is loaded, the jssdk calls the analysis agent, runtime () interface of the Android SDK to obtain the Hybrid buried point.

Transmitting cross-platform associated attribute information: the protocol is used for solving the problem of the attribute of a Hybrid embedded point associated Android page element or the attribute of a non-Hybrid embedded point associated H5 page element, and the specific protocol is as follows (whether the embedded point is a Hybrid embedded point is determined by an is _ Hybrid field): if the embedded point is the Hybrid-associated Android, a related field child node comprises a location field, the JS SDK judges the attribute associated with the Android page element through the location field, and the analyzed entity Hybrid-getProperty (related) of the Android SDK is called to obtain the attribute of the associated element when an event is triggered; if the embedded point is non-Hybrid associated H5, a related field child node comprises an H5_ path field, the Android SDK judges the attribute associated with the H5 page element through the field, the window analysis agent getProperty interface of the JS SDK is called to inform that the associated element attribute is to be acquired when an event is triggered, and the JS SDK calls the analysis agent Hybrid on Property interface of the Android SDK to return the attribute value.

Transmitting buried point trigger information: after the JS SDK acquires the Hybrid embedded point information, 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 of the Android SDK to send the embedded point triggering information, and the Android SDK replaces the Android SDK to report to the server side.

Further, according to a second aspect of the present embodiment, there is provided a method for dotting a page of a terminal device, which is implemented by the server 200 shown in fig. 2. Fig. 9 shows a flow diagram of the method, and referring to fig. 9, the method comprises:

s902: receiving page information sent by terminal equipment, wherein the page information is generated by an SDK (software development kit) integrated by the terminal equipment according to the information of a page of a point to be buried;

s904: sending the page information to a client for carrying out embedded point design;

s906: receiving embedded point information generated according to page information from a client, wherein the embedded point information is used for embedding points in a to-be-embedded point page; and

s908: and sending the buried point information to the terminal equipment.

Specifically, the server 200 first receives the page information sent by the terminal device 210, where the page information is generated by the SDK integrated by the terminal device 210 according to the information of the page to be buried. Then, the server 200 receives, from the client 220, the buried point information generated from the page information, where the buried point information is used for performing buried point on the page to be buried. Further, after the burial point designer designs the burial point for the page information using the editor at the client 220, the burial point information is transmitted to the server 200. in this case, the server 200 receives the burial point information generated from the page information from the client 220, wherein the burial point information is used for the burial point at the page to be buried. Finally, the server 200 transmits the burial point information to the terminal device 210, so that the terminal device 210 can deploy the burial point according to the burial point information.

Furthermore, according to a third aspect of the present embodiment, a method for dotting a page of a terminal device is provided, and the method is implemented by the client 220 shown in fig. 2. Fig. 10 shows a flow diagram of the method, and referring to fig. 10, the method comprises:

s1002: receiving and displaying page information which is sent by a server and needs to be subjected to embedded point design, wherein the page information is page information of terminal equipment communicated with the server, and the page information is generated by an SDK integrated with the terminal equipment;

s1004: responding to the triggering operation of an operator for editing the embedded points of the page information, and determining the embedded point information corresponding to the page information; and

s1006: and sending the buried point information to a server.

Specifically, the client 220 first receives and displays the page information that needs to be subjected to the site design and is sent by the server 200, wherein the page information is page information of the terminal device 210 communicating with the server 200, and the page information is generated by the SDK integrated with the terminal device 210. Then, an operator (a buried point designer) can visually design the buried points of the page information, in a specific example, the operator edits the buried points in the page by a way of circling and selecting page elements, and uses a webpage end visual editor to circle and select the buried points, so that the problems of complex operation of the buried points and large reported data amount are solved. Thus, the client 220 may determine the buried point information corresponding to the page information in response to a trigger operation (page circled element) of the operator editing the buried point for the page information. Finally, the buried point information is transmitted to the server 200.

Further, referring to fig. 1, according to a fourth aspect of the present embodiment, there is provided a storage medium. The storage medium comprises a stored program, wherein the method of any of the above is performed by a processor when the program is run.

In addition, it should be added that:

1. the embedded point binding technology used in the technical scheme of the embodiment is realized by searching a page structure tree, and an event listener is added in an element object after the element is positioned to sense the embedded point event trigger. There is also a method that can achieve the same effect: and (3) adding event listeners for all elements during code compiling by using an ASM Java byte code modification technology, traversing all the information of the existing embedded points after an event is triggered, comparing the current trigger element with various attributes (position, type, text) and the like, and determining whether the element is the embedded point element. The disadvantage of this method is that it needs a separate bytecode modification plug-in support, listens to various events of all elements, is highly invasive and cannot exhaust all events.

2. The same-level embedded point only supports ListView, RecylerView and ViewPager, and the SDK determines whether the embedded point is the same as the class by the class name or not and determines the element positions of the same-level embedded point and the same-level container when the embedded point is realized, and another mode can be adopted: if the container element is the same-level embedded point, the editor adds a container element location field in the same-level embedded point information, and the SDK determines the position of the container element in the same level through the field.

Therefore, according to the embodiment, firstly, the page information of the page to be buried on the terminal device is determined, and then, a buried point designer can design buried points for the page information by using an editor at a client side and generate buried point information. And finally, the terminal equipment deploys the buried points on the page of the point to be buried according to the buried point information. Therefore, compared with the prior art, when the design of the embedded points is carried out on the page on the terminal equipment, the embedded points can be accurately designed according to the page information according to the scheme, the embedded points do not need to be completely embedded, and therefore the data collection amount can be reduced. In addition, the embedded point can be visually designed for the page information through an editor of the client, and the embedded point can be positioned more accurately. Therefore, the technical effect of accurately embedding points on the terminal equipment is achieved. And then solved the utilization among the prior art and buried a technical problem that some technique can't carry out the accurate technical problem that buries a little on terminal equipment when carrying out data acquisition on terminal equipment.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

Example 2

Fig. 11 shows an apparatus 1100 for dotting a page of a terminal device according to the first aspect of the present embodiment, the apparatus 1100 corresponding to the method according to the first aspect of embodiment 1. Referring to fig. 11, the apparatus 1100 includes: the page information determining module 1110 is configured to determine page information of a to-be-buried point page, where the page information is generated by an SDK integrated with a terminal device; the page information sending module 1120 is used for sending the page information to a server, wherein the server is connected with a client for carrying out embedded point design; a buried point information receiving module 1130, configured to receive, from a server, buried point information corresponding to a to-be-buried point page, where the buried point information is generated by a client according to page information; and a buried point deployment module 1140, configured to deploy buried points on the to-be-buried point page of the terminal device through the SDK according to the buried point information.

Optionally, the apparatus 1100 further comprises: the device information determining module is used for determining the device information of the terminal device through the SDK and sending the device information to the server; and the acquisition instruction receiving module is used for receiving an acquisition instruction for acquiring the page information of the page of the point to be buried from the server, wherein the acquisition instruction is generated by the server according to the confirmation information of the selection equipment sent by the client.

Optionally, the buried site deployment module 1140, comprises: the binding submodule is used for binding the embedded point information with the page elements of the page to be embedded through the SDK; the first trigger submodule is used for responding to a first trigger operation of a user for testing a buried point, determining first trigger information and sending the first trigger information to the server; the deployment instruction receiving submodule is used for receiving a deployment instruction from the server, wherein the deployment instruction is generated by the server according to prompt information sent by the client, and the prompt information is used for indicating that the embedding point corresponding to the first trigger information is successful; and the deployment submodule is used for deploying the embedded point on the page of the to-be-embedded point of the terminal equipment according to the deployment instruction.

Optionally, the binding submodule includes: the device comprises a position information determining unit, a position information determining unit and a position information acquiring unit, wherein the position information determining unit is used for determining position information contained in embedded point information, and the position information is used for indicating the position of a page element needing embedded points in a page to be embedded; the first element positioning unit is used for determining the position of the page element according to the position information; and the first binding unit is used for binding the embedded point information and the page elements according to the determined position.

Optionally, the binding submodule includes: the attribute information determining unit is used for determining attribute information contained in the embedded point information, wherein the attribute information is used for indicating the attribute of a page element needing embedded points in a page to be embedded; and the second binding unit is used for determining the page elements according to the attribute information and binding the embedded point information with the determined page elements.

Optionally, the binding submodule includes: the same-level element positioning unit is used for positioning and determining page elements through the same-level elements according to the embedded point information; and the third binding unit is used for binding the embedded point information with the page elements.

Optionally, the apparatus 1100 further comprises: the second trigger module is used for responding to a second trigger operation of the user for testing the buried point and determining second trigger information, wherein the second trigger information is used for indicating the buried point triggered by the user; and the second trigger information sending module is used for sending the second trigger information to the server.

Optionally, the second triggering module includes: the second trigger submodule is used for responding to a second trigger operation of a user for testing the buried point and determining the triggered buried point; the element attribute information determining submodule is used for determining element attribute information related to the page element corresponding to the triggered buried point; and the second trigger information determining submodule is used for determining second trigger information according to the triggered buried point and the element attribute information.

Optionally, the page information determining module 1110 includes: and the dialog box information determining submodule is used for determining the page information of the page of the point to be buried according to the page elements of the dialog box type contained in the page of the point to be buried.

Optionally, the to-be-buried point page includes a H5 page, and the page information determining module 1110 includes: the first page information determining submodule is used for determining first page information of a page of the terminal equipment through an SDK (software development kit) of the terminal equipment and determining second page information of an H5 page through a JavaScript SDK; and the second page information determining submodule is used for determining the page information of the page of the point to be buried according to the first page information and the second page information.

Furthermore, fig. 12 shows an apparatus 1200 for dotting a page of a terminal device according to the second aspect of the present embodiment, where the apparatus 1200 corresponds to the method according to the second aspect of embodiment 1. Referring to fig. 12, the apparatus 1200 includes: the page information receiving module 1210 is configured to receive page information sent by a terminal device, where the page information is generated by an SDK integrated with the terminal device according to information of a page to be buried; a sending module 1220 for sending the page information to a client for performing the embedded point design; the slave client receiving module 1230 is configured to receive, from the client, embedded point information generated according to the page information, where the embedded point information is used for embedding points in a to-be-embedded point page; and a device sending module 1240 for sending the buried point information to the terminal device.

Furthermore, fig. 13 shows an apparatus 1300 for dotting a page of a terminal device according to the third aspect of the present embodiment, where the apparatus 1300 corresponds to the method according to the third aspect of embodiment 1. Referring to fig. 13, the apparatus 1300 includes: a page information display module 1310, configured to receive and display page information that needs to be subjected to embedded point design and is sent by a server, where the page information is page information of a terminal device that communicates with the server, and the page information is generated by an SDK integrated with the terminal device; a buried point information editing module 1320, configured to determine buried point information corresponding to the page information in response to a trigger operation of an operator for editing a buried point of the page information; and a sending module 1330 configured to send the buried point information to the server.

Therefore, according to the embodiment, firstly, the page information of the to-be-buried point on the terminal device is determined, then, a buried point designer can design the buried point for the page information by using an editor at the client side and generate the buried point information, and finally, the terminal device deploys the buried point on the to-be-buried point page according to the buried point information. Therefore, compared with the prior art, when the design of the embedded points is carried out on the page on the terminal equipment, the embedded points can be buried according to the accurate design of the page information according to the scheme, the embedded points do not need to be completely buried, so that the data acquisition amount can be reduced, in addition, the embedded points can be visually designed for the page information through an editor of the client, and the embedded points can be more accurately located. Therefore, the technical effect of accurately embedding points on the terminal equipment is achieved. And then solved the utilization among the prior art and buried a technical problem that some technique can't carry out the accurate technical problem that buries a little on terminal equipment when carrying out data acquisition on terminal equipment.

Example 3

Fig. 14 shows an apparatus 1400 for dotting a page of a terminal device according to the first aspect of the present embodiment, where the apparatus 1400 corresponds to the method according to the first aspect of embodiment 1. Referring to fig. 14, the apparatus 1400 includes: a first processor 1410; and a first memory 1420 coupled to the first processor 1410 for providing the first processor 1410 with instructions to process the following steps: determining page information of a page to be buried, wherein the page information is generated by an SDK integrated by terminal equipment; sending the page information to a server, wherein the server is connected with a client for carrying out embedded point design; receiving embedded point information corresponding to a to-be-embedded point page from a server, wherein the embedded point information is generated by a client according to the page information; and deploying the buried points on the page of the point to be buried of the terminal equipment through the SDK according to the buried point information.

Furthermore, fig. 15 shows an apparatus 1500 for dotting a page of a terminal device according to the second aspect of the present embodiment, which apparatus 1500 corresponds to the method according to the second aspect of embodiment 1. Referring to fig. 15, the apparatus 1500 includes: a second processor 1510; and a second memory 1520, coupled to the second processor 1510, for providing instructions to the second processor 1510 to process the following process steps: receiving page information sent by terminal equipment, wherein the page information is generated by an SDK (software development kit) integrated by the terminal equipment according to the information of a page of a point to be buried; sending the page information to a client for carrying out embedded point design; receiving embedded point information generated according to page information from a client, wherein the embedded point information is used for embedding points in a to-be-embedded point page; and sending the buried point information to the terminal equipment.

Furthermore, fig. 16 shows an apparatus 1600 for dotting a page of a terminal device according to the third aspect of the present embodiment, where the apparatus 1600 corresponds to the method according to the third aspect of embodiment 1. Referring to fig. 16, the apparatus 1600 includes: a third processor 1610; and a third memory 1620, connected to the third processor 1610, for providing the third processor 1610 with instructions to process the following steps: receiving and displaying page information which is sent by a server and needs to be subjected to embedded point design, wherein the page information is page information of terminal equipment communicated with the server, and the page information is generated by an SDK integrated with the terminal equipment; responding to the triggering operation of an operator for editing the embedded points of the page information, and determining the embedded point information corresponding to the page information; and sending the buried point information to a server.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

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

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims

1. A method for embedding points in a page of a terminal device is characterized by comprising the following steps:

determining page information of a page to be buried, wherein the page information is generated by an SDK integrated by a terminal device;

sending the page information to a server, wherein the server is connected with a client for carrying out embedded point design;

receiving buried point information corresponding to the page to be buried from the server, wherein the buried point information is generated by the client according to the page information; and

and deploying the buried points on the page of the terminal equipment to be buried points through the SDK according to the buried point information.

2. The method of claim 1, wherein prior to determining page information for a to-be-buried-point page, further comprising:

determining the equipment information of the terminal equipment through the SDK, and sending the equipment information to the server; and

and receiving an acquisition instruction for acquiring the page information of the page of the point to be buried from the server, wherein the acquisition instruction is generated by the server according to the confirmation information of the selected equipment sent by the client.

3. The method of claim 1, wherein deploying the embedded point on the page to be embedded of the terminal device through the SDK according to the embedded point information comprises:

binding the embedded point information with the page elements of the page to be embedded through the SDK;

responding to a first trigger operation of a user for testing a buried point, determining first trigger information and sending the first trigger information to the server;

receiving a deployment instruction from the server, wherein the deployment instruction is generated by the server according to prompt information sent by the client, and the prompt information is used for indicating that the buried point corresponding to the first trigger information is successful; and

and deploying the buried points on the page of the point to be buried of the terminal equipment according to the deployment instruction.

4. The method of claim 3, wherein binding the burial point information with the page elements of the to-be-buried point page through the SDK comprises:

determining position information contained in the embedded point information, wherein the position information is used for indicating the position of a page element needing embedded points in the page to be embedded;

determining the position of the page element according to the position information; and

and binding the buried point information with the page element according to the determined position.

5. The method of claim 3, wherein binding the burial point information with the page elements of the to-be-buried point page through the SDK comprises:

determining attribute information contained in the embedded point information, wherein the attribute information is used for indicating attributes of page elements needing embedded points in the page to be embedded; and

and determining the page elements according to the attribute information, and binding the embedded point information with the determined page elements.

6. The method of claim 3, wherein binding the burial point information with the page elements of the to-be-buried point page through the SDK comprises:

determining the page elements through the same-level element positioning according to the embedded point information; and

and binding the buried point information with the page element.

7. The method of claim 1, after deploying the burial point on the to-be-buried point page of the terminal device through the SDK, further comprising:

responding to a second trigger operation of a user for testing a buried point, determining element attribute information related to a page element corresponding to the triggered buried point, and determining second trigger information according to the triggered buried point and the element attribute information, wherein the second trigger information is used for indicating the buried point triggered by the user; and

and sending the second trigger information to the server.

8. The method of claim 1, wherein determining page information for a to-be-buried point page further comprises:

and determining the page information of the page of the point to be buried according to the page elements of the dialogue frame type contained in the page of the point to be buried.

9. The method of claim 1, wherein the point-to-be-buried page comprises H5 pages, and determining page information for the point-to-be-buried page comprises:

determining first page information of a page of the terminal equipment through an SDK (software development kit) of the terminal equipment, and determining second page information of the H5 page through a JavaScript SDK; and

and determining the page information of the page to be embedded according to the first page information and the second page information.

10. A storage medium comprising a stored program, wherein the method of any one of claims 1 to 9 is performed by a processor when the program is run.