CN113254315A

CN113254315A - Reporting method of embedded point information, embedded point method, device, medium and electronic equipment

Info

Publication number: CN113254315A
Application number: CN202110629381.XA
Authority: CN
Inventors: 曹偲; 董津津; 其他发明人请求不公开姓名
Original assignee: Hangzhou Netease Cloud Music Technology Co Ltd
Current assignee: Hangzhou Netease Cloud Music Technology Co Ltd
Priority date: 2021-06-07
Filing date: 2021-06-07
Publication date: 2021-08-13
Anticipated expiration: 2041-06-07
Also published as: CN113254315B

Abstract

The disclosed embodiments relate to a reporting method, a point burying method, a device, a medium and an electronic device for point burying information, and relate to the technical field of computers. The reporting method of the embedded point information comprises the following steps: responding to a trigger operation aiming at a client, and determining a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation; determining pit position information of the buried point object in the buried point object tree according to the parent-child relationship in the buried point object tree; and acquiring a buried point information reporting parameter value of the buried point object contained in the pit bit information of the buried point object aiming at each buried point object in the buried point object tree so as to report the buried point information of each buried point object. The efficiency and accuracy of reporting the buried point information can be improved based on the buried point object tree.

Description

Reporting method of embedded point information, embedded point method, device, medium and electronic equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a reporting method of embedded point information, a reporting device of embedded point information, an embedded point method, an embedded point device, a computer-readable storage medium, and an electronic device.

Background

This section is intended to provide a background or context to the embodiments of the disclosure recited in the claims and the description herein is not admitted to be prior art by inclusion in this section.

The buried point is a process specific in the application that collects some information to track the usage of the application to provide data support for further optimizing the product.

The point burying schemes in the prior art are mainly divided into the following 3 types: the first is limited abstract buried point design and pre-management facing to pit positions, namely, all reported parameters are directly subjected to repeated enumeration constraint on the buried points or the final pit positions; the second is a non-embedded point scheme, also called as a fully embedded point, that is, the original user interface hierarchical structure of the client is utilized to describe the pit position, fully report the embedded point information, and the fully reported embedded point information is selectively used at the later stage according to the requirement; the third is a circle selection buried point scheme, namely a post selection buried point scheme which is closely combined with the layout of the client side is adopted.

Disclosure of Invention

However, in the first point burying scheme, because a pit description method with no more than four levels of 'page-subpage-module-element' is adopted, when the buried point data is in a complex hierarchical structure, the pit description of the scheme per se has information loss, so that the problem that the pit information description of the buried point is not accurate enough exists, the accuracy of reporting the buried point information is low, and the problem that the later maintenance and management cost of the buried point is high exists; the second and third point burying schemes have the problems of unstable pit position description of the buried points and high later maintenance cost, that is, the client of each version needs to reselect the pit position, and different types of clients may have different pit position descriptions, so that the later maintenance and management cost of the buried points is high, and the efficiency of reporting the buried point information is low.

Therefore, an improved method for reporting the information of the embedded point is highly needed, which can simultaneously improve the accuracy of reporting the information of the embedded point and the efficiency of reporting the information of the embedded point, and reduce the later maintenance cost of the embedded point.

In this context, embodiments of the present disclosure desirably provide a reporting method of embedded point information, a reporting apparatus of embedded point information, an embedded point method, an embedded point apparatus, a computer-readable storage medium, and an electronic device.

According to a first aspect of the embodiments of the present disclosure, a method for reporting buried point information is provided, including: responding to a trigger operation aiming at a client, and determining a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation; determining pit position information of the buried point object in the buried point object tree according to the parent-child relationship in the buried point object tree; and acquiring a buried point information reporting parameter value of the buried point object contained in the pit bit information of the buried point object aiming at each buried point object in the buried point object tree so as to report the buried point information of each buried point object.

In an optional implementation manner, the determining a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation includes: and determining a buried point object tree corresponding to a buried point object in the target display page exposed by the trigger operation according to the preset interface parent-child relationship of the target display page.

In an optional embodiment, the method further comprises: determining a preset interface parent-child relationship of an operable user interface in the target display page and/or a user interface bearing user distribution content based on a user interface component of the target display page, so that the client generates the target display page according to the preset interface parent-child relationship; and determining a buried point object tree corresponding to a buried point object in the target display page according to the preset interface parent-child relationship of the target display page, so that the client buries points in a corresponding user interface according to the buried point object in the buried point object tree.

In an optional implementation manner, the determining, according to the parent-child relationship in the buried point object tree, the pit bit information of the buried point object in the buried point object tree includes: performing the following for each buried object in the buried object tree: determining a buried point object identification chain from the buried point object to a root object in the buried point object tree based on the parent-child relationship in the buried point object tree and a buried point object identification configured for the buried point object in the buried point object tree in advance; and adding the position attribute information of the buried point object in the buried point object identification chain to obtain the pit bit information of the buried point object.

In an optional implementation manner, the obtaining a buried point information reporting parameter value of a buried point object included in the pit bit information of the buried point object includes: according to the sequence of the buried point object identifier contained in the pit bit information of the buried point object in the buried point object identifier chain, traversing the buried point object corresponding to the buried point object identifier in the pit bit information of the buried point object to obtain a buried point information reporting parameter value of the buried point object contained in the pit bit information of the buried point object.

In an optional implementation manner, the buried point information reporting parameter value includes at least one of a device type corresponding to the client, a session identifier corresponding to the client, version information of the client, a user identifier corresponding to the client, a buried point object identifier, a buried point object name, and a buried point object content identifier.

In an optional implementation manner, the reporting parameter value of the buried point information includes a first buried point attribution parameter value, where the first buried point attribution parameter value is determined by: when the type of the current embedded point object corresponding to the trigger operation is a page, determining a first embedded point attribution parameter value of the embedded point object in a target display page exposed by the trigger operation according to a page exposure sequence of the page where the current embedded point object is located after the client is started, a page exposure sequence of the page where a root object of the current embedded point object is located after the client is started and pit bit information of the current embedded point object, wherein the unit value is increased for the page exposure sequence every time page exposure occurs after the client is started, and the value of the page exposure sequence restarts counting along with the restart of the client; when the type of the current embedded point object corresponding to the triggering operation is an element, determining a first embedded point attribution parameter value of the embedded point object in a target display page exposed by the triggering operation according to the triggered sequence of the element in the page where the element is located, the page exposure sequence of the page where the root object of the current embedded point object is located and the pit bit information of the current embedded point object, wherein in the page where the element is located, each time the element triggering operation occurs, the triggered sequence value of the element in the page where the element is located increases by a unit numerical value, and the triggered sequence value of the element in the page where the element is located restarts counting along with the change of the page exposure sequence of the page where the root object of the current embedded point object is located.

In an optional embodiment, the method further comprises: determining an original buried point object for which an original trigger operation of the target display page is created; determining a second buried point attribution parameter value of the buried point object in the target display page according to the type of the original buried point object aimed at by the original trigger operation, and reporting the second buried point attribution parameter value; wherein the second buried point attribution parameter value is determined by: when the type of an original embedded point object aimed at by the original trigger operation is a page, determining a second embedded point attribution parameter value of the embedded point object in the target display page according to a page exposure sequence of the page where the original embedded point object is located after the client is started, a page exposure sequence of the page where a root object of the original embedded point object is located after the client is started and pit bit information of the original embedded point object, wherein after the client is started, each time page exposure occurs, the value of the page exposure sequence is increased by a unit value, and the value of the page exposure sequence restarts counting along with the restart of the client; when the type of the original embedded point object corresponding to the original triggering operation is an element, determining a second embedded point attribution parameter value of the embedded point object in the target display page according to the triggered sequence of the element in the page where the element is located, the exposure sequence of the page where the root object of the original embedded point object is located and the pit bit information of the original embedded point object, wherein the triggered sequence value of the element in the page where the element is located increases by a unit numerical value every time the element triggering operation occurs, and the triggered sequence value of the element in the page where the element is located restarts counting along with the change of the page exposure sequence of the page where the root object of the original embedded point object is located.

In an optional embodiment, the method further comprises: and determining a third buried point attribution parameter value of the buried point object in the target display page according to the session identifier when the client is started for the last time, and reporting the third buried point attribution parameter value.

In an optional embodiment, the method further comprises: the method further comprises the following steps: determining a server end buried point object pre-associated with the triggering operation; reporting a fourth buried point attribution parameter value corresponding to the server end buried point object; wherein the fourth buried point attribution parameter value is determined by: when the type of the current embedded point object corresponding to the trigger operation is a page, determining a fourth embedded point attribution parameter value of the embedded point object in a target display page exposed by the trigger operation according to the page exposure sequence of the page where the current embedded point object is located after the client is started, the page exposure sequence of the page where the root object of the current embedded point object is located after the client is started and the pit bit information of the current embedded point object, wherein the unit value is increased for the value of the page exposure sequence every time the page exposure occurs after the client is started, and the value of the page exposure sequence restarts counting along with the restart of the client; when the type of the current embedded point object corresponding to the triggering operation is an element, determining a fourth embedded point attribution parameter value of the embedded point object in the target display page exposed by the triggering operation according to the triggered sequence of the element in the page where the element is located, the exposure sequence of the page where the root object of the current embedded point object is located and the pit bit information of the current embedded point object, wherein in the page where the element is located, each time the element triggering operation occurs, the triggered sequence value of the element in the page where the element is located increases by a unit numerical value, and the triggered sequence value of the element in the page where the element is located restarts counting along with the change of the page exposure sequence of the page where the root object of the current embedded point object is located.

According to a second aspect of an embodiment of the present disclosure, there is provided a method of burying a point, including: determining a preset buried point object tree of a display page of a point to be buried according to a preset interface parent-child relationship of the display page of the point to be buried; configuring a buried point object identifier and a buried point information reporting parameter for each buried point object in the preset buried point object tree; and for each embedded point object in the preset embedded point object tree, embedding points in an interface corresponding to the embedded point object according to the embedded point object identification and the embedded point information reporting parameter, so that after a client receives a triggering operation of exposing the display page of the to-be-embedded point, the embedded point information is reported according to the preset embedded point object tree determined by the preset interface parent-child relationship.

In an optional implementation manner, the preset interface parent-child relationship of the to-be-buried point display page is determined by: and determining a preset interface parent-child relationship of an operable user interface in the display page of the point to be buried and/or a user interface bearing user distribution content based on the user interface component of the display page of the point to be buried.

According to a third aspect of the embodiments of the present disclosure, there is provided a reporting apparatus for reporting embedded point information, including: the buried point object tree determining module is configured to respond to a trigger operation aiming at a client and determine a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation; a pit position information determining module configured to determine pit position information of a buried point object in the buried point object tree according to a parent-child relationship in the buried point object tree; and the buried point information reporting module is configured to acquire a buried point information reporting parameter value of the buried point object contained in the pit bit information of the buried point object for each buried point object in the buried point object tree, so as to report the buried point information of each buried point object.

In an optional implementation manner, the reporting apparatus of the buried point information further includes a pre-buried point module, where the pre-buried point module is configured to: determining a preset interface parent-child relationship of an operable user interface in the target display page and/or a user interface bearing user distribution content based on a user interface component of the target display page, so that the client generates the target display page according to the preset interface parent-child relationship; and determining a buried point object tree corresponding to a buried point object in the target display page according to the preset interface parent-child relationship of the target display page, so that the client buries points in a corresponding user interface according to the buried point object in the buried point object tree.

In an optional implementation, the pit bit information determining module is further specifically configured to: performing the following for each buried object in the buried object tree: determining a buried point object identification chain from the buried point object to a root object in the buried point object tree based on the parent-child relationship in the buried point object tree and a buried point object identification configured for the buried point object in the buried point object tree in advance; and adding the position attribute information of the buried point object in the buried point object identification chain to obtain the pit bit information of the buried point object.

In an optional implementation manner, the buried point information reporting module is further specifically configured to: according to the sequence of the buried point object identifier contained in the pit bit information of the buried point object in the buried point object identifier chain, traversing the buried point object corresponding to the buried point object identifier in the pit bit information of the buried point object to obtain a buried point information reporting parameter value of the buried point object contained in the pit bit information of the buried point object.

In an optional implementation manner, the reporting apparatus of the buried point information further includes a second buried point attribution parameter value reporting module, configured to: determining an original buried point object for which an original trigger operation of the target display page is created; determining a second buried point attribution parameter value of the buried point object in the target display page according to the type of the original buried point object aimed at by the original trigger operation, and reporting the second buried point attribution parameter value; wherein the second buried point attribution parameter value is determined by: when the type of an original embedded point object aimed at by the original trigger operation is a page, determining a second embedded point attribution parameter value of the embedded point object in the target display page according to a page exposure sequence of the page where the original embedded point object is located after the client is started, a page exposure sequence of the page where a root object of the original embedded point object is located after the client is started and pit bit information of the original embedded point object, wherein after the client is started, each time page exposure occurs, the value of the page exposure sequence is increased by a unit value, and the value of the page exposure sequence restarts counting along with the restart of the client; when the type of the original embedded point object corresponding to the original triggering operation is an element, determining a second embedded point attribution parameter value of the embedded point object in the target display page according to the triggered sequence of the element in the page where the element is located, the exposure sequence of the page where the root object of the original embedded point object is located and the pit bit information of the original embedded point object, wherein the triggered sequence value of the element in the page where the element is located increases by a unit numerical value every time the element triggering operation occurs, and the triggered sequence value of the element in the page where the element is located restarts counting along with the change of the page exposure sequence of the page where the root object of the original embedded point object is located.

In an optional implementation manner, the apparatus for reporting buried point information further includes a third buried point attribution parameter value reporting module, where the third buried point attribution parameter value reporting module is specifically configured to: and determining a third buried point attribution parameter value of the buried point object in the target display page according to the session identifier when the client is started for the last time, and reporting the third buried point attribution parameter value.

In an optional implementation manner, the apparatus for reporting buried point information further includes a fourth buried point attribution parameter value reporting module, where the module is specifically configured to: determining a server end buried point object pre-associated with the triggering operation; reporting a fourth buried point attribution parameter value corresponding to the server end buried point object; wherein the fourth buried point attribution parameter value is determined by: when the type of the current embedded point object corresponding to the trigger operation is a page, determining a fourth embedded point attribution parameter value of the embedded point object in a target display page exposed by the trigger operation according to the page exposure sequence of the page where the current embedded point object is located after the client is started, the page exposure sequence of the page where the root object of the current embedded point object is located after the client is started and the pit bit information of the current embedded point object, wherein the unit value is increased for the value of the page exposure sequence every time the page exposure occurs after the client is started, and the value of the page exposure sequence restarts counting along with the restart of the client; when the type of the current embedded point object corresponding to the triggering operation is an element, determining a fourth embedded point attribution parameter value of the embedded point object in the target display page exposed by the triggering operation according to the triggered sequence of the element in the page where the element is located, the exposure sequence of the page where the root object of the current embedded point object is located and the pit bit information of the current embedded point object, wherein in the page where the element is located, each time the element triggering operation occurs, the triggered sequence value of the element in the page where the element is located increases by a unit numerical value, and the triggered sequence value of the element in the page where the element is located restarts counting along with the change of the page exposure sequence of the page where the root object of the current embedded point object is located.

According to a fourth aspect of embodiments of the present disclosure, there is provided a buried point device comprising: the preset embedded point object tree determining module is configured to determine a preset embedded point object tree of a display page to be embedded according to a preset interface parent-child relationship of the display page to be embedded; a buried point reporting parameter configuration module configured to configure a buried point object identifier and a buried point information reporting parameter for each buried point object in the preset buried point object tree; and the point burying module is configured to bury points in an interface corresponding to the buried point object according to the buried point object identifier and the buried point information reporting parameter for each buried point object in the preset buried point object tree, so that the client reports the buried point information according to the preset buried point object tree after receiving the triggering operation of exposing the display page of the to-be-buried point.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements any one of the above reporting methods and/or the above embedding methods for embedding point information.

According to a sixth aspect of the disclosed embodiments, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; the processor is configured to execute any one of the above reporting methods and/or the above embedding methods of the embedding information by executing the executable instructions.

According to the embedded point information reporting method, the embedded point information reporting device, the embedded point method, the embedded point device, the medium and the electronic device of the embodiment of the disclosure, the embedded point object tree corresponding to the embedded point object in the target display page exposed by the trigger operation aiming at the client is determined, the pit position information of each embedded point object in the embedded point object tree can be determined according to the parent-child relationship in the embedded point object tree, and then the embedded point information can be reported according to the pit position information of the embedded point object. On one hand, the pit bit information of the buried point object is determined based on the parent-child relationship in the buried point object tree, so that the buried point can be prevented from having different pit bit descriptions at different clients, the stability of the description of the pit bit information of the buried point is improved, the maintenance cost of the buried point is reduced, and the reporting efficiency of the buried point information is improved; on the other hand, the method and the device can report the embedded point information according to the determined embedded point object tree by determining the embedded point object tree corresponding to the embedded point object in the target display page exposed by the trigger operation, and can provide accurate pit description for each embedded point object and improve the accuracy of reporting the embedded point information because the determined embedded point object tree corresponds to the embedded point object in the target display page exposed by the trigger operation.

Drawings

The above and other objects, features and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which:

fig. 1 is a schematic diagram illustrating a reporting method of embedded point information according to an embodiment of the present disclosure;

FIG. 2 illustrates a schematic diagram of a method for performing a dot burying in a target display page according to an embodiment of the present disclosure;

FIG. 3A illustrates a page according to an embodiment of the present disclosure;

FIG. 3B illustrates a schematic diagram of a tree structure of an actual user interface hierarchy implementation of the page in FIG. 3A;

FIG. 3C shows a schematic diagram of a buried object tree of the page in FIG. 3A;

4A, 4B, 4C, 4D, 4E are schematic diagrams illustrating a buried object tree as a function of a display page of a client according to an embodiment of the present disclosure;

fig. 5 is a schematic diagram illustrating a method for determining pit bit information of a buried object according to an embodiment of the disclosure;

FIG. 6 illustrates a buried object management interface according to an embodiment of the present disclosure;

FIG. 7 illustrates a display interface of a buried object tree according to an embodiment of the present disclosure;

FIG. 8 illustrates a schematic diagram of the actual interface level and buried object tree of a display page exposed by a trigger operation according to an embodiment of the present disclosure;

FIG. 9 is a schematic diagram illustrating a variation of an exposed display page corresponding to a series of operations performed by a user according to an embodiment of the present disclosure;

FIG. 10 shows a schematic diagram of a method of burying a point in accordance with an embodiment of the present disclosure;

fig. 11 is a block diagram illustrating a device for reporting buried point information according to the disclosed embodiment;

FIG. 12 illustrates a block diagram of a buried point device according to an embodiment of the present disclosure;

FIG. 13 shows a block diagram of an electronic device according to an embodiment of the disclosure.

In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

Detailed Description

The principles and spirit of the present disclosure will be described with reference to a number of exemplary embodiments. It is understood that these embodiments are given solely for the purpose of enabling those skilled in the art to better understand and to practice the present disclosure, and are not intended to limit the scope of the present disclosure in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

As will be appreciated by one skilled in the art, embodiments of the present disclosure may be embodied as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

According to an embodiment of the present disclosure, a reporting method of embedded point information, an embedded point method, a reporting device of embedded point information, an embedded point device, a computer-readable storage medium, and an electronic device are provided.

In this document, any number of elements in the drawings is by way of example and not by way of limitation, and any nomenclature is used solely for differentiation and not by way of limitation.

The principles and spirit of the present disclosure are explained in detail below with reference to several representative embodiments of the present disclosure.

Summary of The Invention

The inventor of the present disclosure finds that, in some existing embedded point schemes, for clients of different versions or clients corresponding to different operating systems, there is a problem that description of pit location information of embedded points is inconsistent, so that description of pit location information of embedded points is unstable, and when a new version of a client is updated, pit location information needs to be comprehensively checked and reselected each time, which results in high cost for later maintenance of embedded points and low efficiency for reporting embedded point information; in other existing point burying schemes, the problem that the description of the pit bit information of the buried point is inaccurate exists, so that the accuracy of reporting the buried point information is low.

In view of the above, the basic idea of the present disclosure is: the method comprises the steps of determining a buried point object tree corresponding to a buried point object in a target display page exposed by trigger operation, determining pit position information of each buried point object in the buried point object tree according to the parent-child relationship in the buried point object tree, and reporting the buried point information according to the pit position information of the buried point object. On one hand, the pit bit information of the buried point object is determined based on the parent-child relationship in the buried point object tree, so that the buried point can be prevented from having different pit bit descriptions at different clients, the stability of the description of the pit bit information of the buried point is improved, the maintenance cost of the buried point is reduced, and the reporting efficiency of the buried point information is improved; on the other hand, the method and the device can report the embedded point information according to the determined embedded point object tree by determining the embedded point object tree corresponding to the embedded point object in the target display page exposed by the trigger operation, and can provide accurate pit description for each embedded point object and improve the accuracy of reporting the embedded point information because the determined embedded point object tree corresponds to the embedded point object in the target display page exposed by the trigger operation.

Having described the general principles of the present disclosure, various non-limiting embodiments of the present disclosure are described in detail below.

Application scene overview

It should be noted that the following application scenarios are merely illustrated to facilitate understanding of the spirit and principles of the present disclosure, and embodiments of the present disclosure are not limited in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.

The present disclosure may be applied to scenarios where data is collected, for example: the embedded point information reporting method provided by the disclosure can be used for collecting the use data (such as access number, visitor number, dwell time, page browsing number and the like) of the application, and tracking the use condition of the application based on the use data so as to provide data support for further optimization of the application; in an information recommendation scene, the relevant historical behavior data of a user can be collected by using the buried point information reporting method provided by the disclosure, and then the user portrait can be described based on the collected historical behavior data of the user so as to recommend information to the user.

Exemplary method

In the point burying scheme in the related art, for clients of different versions or clients corresponding to different operating systems, the problem of inconsistent description of the pit information of the buried points exists, so that the description of the pit information of the buried points is unstable, and the pit information needs to be comprehensively checked and reselected each time a new version of the client is updated, so that the later maintenance cost of the buried points is high, and the reporting efficiency of the buried point information is low; and the problem of inaccurate pit bit information description of the buried point exists, so that the reporting accuracy of the buried point information is low.

The exemplary embodiment of the present disclosure first provides a reporting method of buried point information, so as to overcome at least all or part of the above-mentioned drawbacks in the related art.

Fig. 1 shows a reporting method of embedded point information in an exemplary embodiment of the present disclosure, which may include:

step S110, responding to the trigger operation aiming at the client, and determining a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation;

step S120, determining pit position information of the buried point object in the buried point object tree according to the parent-child relationship in the buried point object tree;

step S130, for each buried point object in the buried point object tree, acquiring a buried point information reporting parameter value of the buried point object included in the pit bit information of the buried point object, so as to report the buried point information of each buried point object.

Each step in fig. 1 will be described in detail below.

Step S110, in response to a trigger operation for a client, determining a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation.

In an alternative embodiment, the triggering operation may include clicking in the client, sliding, or performing a gesture operation with respect to the client. An exposure may be understood as a state in which a page or element is not visible in the graphical user interface of the client. The target display page may include any display page in the client, which corresponds to the trigger operation, for example, if the user clicks the button 1 in the client, the page displayed in the client jumps from the page 1 before the click to the page 2, and the page 2 is the target display page exposed by the trigger operation of clicking the button 1.

A page may be understood as a whole area displayed exclusively at a certain user interface level, such as a newly opened underlying page, a TAB (TAB), a channel, etc.; the page is generally used for organizing a plurality of contents to distribute or used as an actual function bearing of a single content, and information such as circulation exposure and dwell time of the page has great significance for analysis of the application. An element may be understood as a UI (User Interface) component and/or element in a page that may be interacted with by a User, such as a list element, a button, a slideable content module, etc. The lists and modules are generally used for carrying content distribution, the click rate of the lists and modules has analytical significance on content distribution effects, the buttons are generally used for carrying user interaction, and the buttons are generally mounted on a certain content unit or a bottom page of a content function.

Both pages and elements can be considered as buried point objects. One page can comprise sub-pages and elements, for one page, the page itself, the sub-pages and the elements in the page can be used as buried point objects in the page, and a user can perform self-defined setting according to the needs of the user.

For example, before determining the buried point object tree corresponding to the buried point object in the target display page exposed by the trigger operation, the buried point may be performed in the target display page. Fig. 2 shows a schematic diagram of a method for embedding points in a target display page according to an embodiment of the present disclosure. Referring to fig. 2, the method may include steps S210 to S220.

In step S210, based on the user interface component of the target display page, a preset interface parent-child relationship of the user interface operable in the target display page and/or the user interface carrying the content distributed by the user is determined, so that the client generates the target display page according to the preset interface parent-child relationship.

The component can be understood as a module which is formed by splitting, summarizing and combining each function point of the product according to the functions of the product, the local parts of the page, the user behaviors and the like, has standard specifications and can be repeatedly used.

In an alternative embodiment, the operable user interface may include an interface hierarchy for carrying user interaction, such as a user interface hierarchy at which buttons are located, and the user interface for carrying user distribution content may include an interface hierarchy at which pages or elements capable of distributing user content, such as pages, lists, modules, etc., are located. The operable user interface can also comprise an interface hierarchy in which the operable user interface components are located, and the interface for carrying the user content distribution can also comprise an interface hierarchy in which the user interface components for carrying the user content distribution are located.

In an optional implementation manner, based on the idea of the user interface component, the reusable user interface component in the target display page may be regarded as an interface hierarchy, that is, the interface hierarchies where each element or page in the user interface component is located belong to the same interface hierarchy, and then, according to the requirement of the buried point, the parent-child relationship of the operable user interface hierarchy in the target display page and/or the user interface hierarchy bearing the distribution of the user content is customized to determine the preset interface parent-child relationship of the operable user interface in the target display page and/or the user interface bearing the distribution of the content. Therefore, a front-end developer can perform development layout of a front-end page according to the preset interface parent-child relationship, and further, when the client displays the page, a target display page can be generated by rendering according to the preset interface parent-child relationship.

Next, in step S220, a buried point object tree corresponding to the buried point object in the target display page is determined according to the preset interface parent-child relationship of the target display page, so that the client performs the buried point on the corresponding user interface according to the buried point object in the buried point object tree.

In an optional implementation manner, a page or an element corresponding to each interface level in a preset interface parent-child relationship of an interface level of a target display page may be used as a buried point object, so that the parent-child relationship of each buried point object is determined based on the preset interface parent-child relationship, and a buried point object tree corresponding to the buried point object in the target display page is further determined, so that a client may perform buried point corresponding to a user interface level where each buried point object in the buried point object tree is located.

Through the steps S210 to S220, the buried point object tree can be determined according to the preset interface parent-child relationship of the target display page, so that the developer develops the page according to the preset interface parent-child relationship and performs corresponding buried points according to the interface level where the buried point object tree is located.

In an alternative embodiment, the determining that the trigger operation exposes the buried point object tree corresponding to the buried point object in the target display page in step S110 may include: and determining a buried point object tree corresponding to the buried point object in the target display page exposed by the trigger operation according to the preset interface parent-child relationship of the target display page.

The embedded point object tree is determined based on the preset interface parent-child relationship, then the client side carries out embedded point on the user interface level corresponding to the embedded point object based on the embedded point object tree, and meanwhile the client side carries out rendering on the target display page according to the preset interface parent-child relationship. Therefore, according to the preset interface parent-child relationship of the rendered target display page, the parent-child relationship of the embedded point object of the target display page can be determined, and further the embedded point object tree corresponding to the embedded point object in the target display page is determined.

Next, taking the page in fig. 3A as an example, the above steps S210 to S220 are more intuitively explained by combining the schematic diagram of the tree structure implemented by the actual user interface hierarchy of the page in fig. 3A shown in fig. 3B and the schematic diagram of the buried object tree of the page in fig. 3A shown in fig. 3C.

In fig. 3B and 3C, P1 is a home page, P2 is yuncun TAB, P3 is a channel of interest, E8 is an expansion button, E9 is a release button, E2 is a user card, E13 is a reference microblog, E7 is a microblog link, E1 is a microblog unit, E3 is a microblog picture, E4 is a forward button, E5 is a comment button, E6 is a like button, E10 is a Mini play bar (i.e., a Mini play bar), E11 is a play button, and E12 is a play list button. The Recycler View in FIG. 3B is a component of the android operating system, specifically a fixed-size View (View Container), but can display many data controls, which can be implemented by scrolling through a list. Viewmanager can be understood as a view container used to slide left and right.

It can be known from fig. 3B and 3C that some of the actual user interface levels of the page in fig. 3A are ignored in the buried point object tree (fig. 3B also only shows a part of the user interface levels of the page in fig. 3A, and does not fully show all the user interface levels of the page in fig. 3A, and is more complicated in actual implementation), and the levels corresponding to the dotted circles such as "bottom bar, discovery button, blog button, my button, K song button, and cloudsun button" in fig. 3B are ignored in the buried point object tree in fig. 3C, while the operable user interface level and the interface level carrying the distribution of the user content are retained when determining the buried point object tree, and the page level where the page or element in some reusable user interface components is located is taken as one user interface level.

It should be noted that, when a developer develops a target display page, the developer needs to layout the target display page according to the parent-child relationship in the buried point object tree, that is, the parent-child relationship of the interface hierarchy where each buried point object in the buried point object tree is located needs to be consistent with the parent-child relationship of the buried point object in the buried point object tree, and on this premise, some other elements or child pages or user interface components may be added to the target display page according to the actual page display needs. For example, a developer may perform the layout of the pages in FIG. 3A according to the buried point object tree in FIG. 3C, and some other elements or sub-pages or user interface components may be added to the actual interface hierarchy to form the tree structure of the actual user interface hierarchy in FIG. 3B. It can also be seen from fig. 3B and 3C that the parent-child relationship of each node in the buried point object tree in fig. 3C remains unchanged in fig. 3B, as in fig. 3B and 3C where P1 is the root node of P2 and E10.

Therefore, by determining the preset interface parent-child relationship of the operable user interface and/or the user interface for bearing content distribution in the target display page, the tree structure for reporting the buried point can be constructed based on the parent-child relationship of the visual user interface component, and the actual user interface level of the client is ignored, so that the stability and the accuracy of the description of the buried point pit are improved, meanwhile, the problem that the description of the buried point pit is inconsistent in different versions or different types of clients can be solved, the later maintenance cost of the buried point is reduced, and the reporting efficiency of the buried point is improved.

After the buried object tree is constructed, the page change and circulation conditions of the client can be described based on the change conditions of the buried object tree. Fig. 4A through 4E show schematic diagrams of a buried object tree as a function of a display page of a client according to an embodiment of the present disclosure.

In fig. 4A, 4A1, 4A2, 4A3, and 4A4 are all video cards, but they correspond to different video contents, i.e., all belong to the video card hierarchy, but they have different position attribute information. The dynamic 1 in fig. 4C represents the dynamic 1 specifically issued by the user AAA, i.e., this dynamic with respect to "positive energy". Dynamic 1 and dynamic 2 in fig. 4D and 4E are two dynamics with different contents issued by the user AAA.

As can be seen from fig. 4A to 4E, when a page changes, the buried point object tree also changes. The buried point objects in the dotted line frame of the buried point object tree in fig. 4A to 4E indicate buried point objects whose exposure is ended after the exposure is ended on the page. For example, when the page jumps from fig. 4A to fig. 4B, the exposure of the buried object corresponding to the "recommendation, navigation, video card" in the buried object tree of fig. 4A is ended, the buried object corresponding to the "focus, microblog, user card, cloud circle entry" in fig. 4B is newly added, and then the buried object tree in fig. 4B is generated, and when the page jumps from fig. 4B to fig. 4C, the exposure of the buried object in the entire buried object tree in fig. 4B is ended, and then the buried object tree in fig. 4C is generated, so are the changes from fig. 4C to fig. 4D and the changes from fig. 4D to fig. 4E, which are not repeated. Wherein ending an exposure may be understood as a switching of a page or element from a visible to an invisible state in a graphical user interface of a client.

The change of the buried object tree can describe the change of the page, so that the buried information can be reported based on the buried object tree. Therefore, in step S110, in response to the trigger operation for the client, the buried point object tree corresponding to the buried point object in the display page exposed by the trigger operation can be determined. And then, combining the subsequent step S120 and step S130, reporting the embedded point information is realized.

With continued reference to fig. 1, in step S120, pit-bit information of the buried point object in the buried point object tree is determined according to the parent-child relationship in the buried point object tree.

The pit bit can be understood as the only one position which can be described in the client application, the pit bit can be a page or an element, and the complete information of the pit bit can contain object information corresponding to a plurality of levels. The parameter field of the pit bit in the reporting of the buried point information can be represented by Super Position Model (SPM).

In an alternative embodiment, the steps shown in fig. 5 may be performed for each buried object in the buried object tree to determine pit bit information for each buried object in the buried object tree. Fig. 5 is a schematic diagram illustrating a method for determining pit bit information of a buried object according to an embodiment of the present disclosure, and referring to fig. 5, the method may include steps S510 to S520.

Step S510 determines a buried point object identification chain of a buried point object to a root object in the buried point object tree based on the parent-child relationship in the buried point object tree and the buried point object identification previously configured for the buried point object in the buried point object tree.

The buried Object identifier (Object Id, abbreviated as oid) is the identity of the page or element of the buried point on the client, and the same oid can be used to characterize the same UI style, the same content unit, the same interactive form, or a specific location UI on the client.

In an optional implementation manner, when a developer performs development, an identity may be configured for each page and each element, and if a certain page or element is buried, the identity of the page or element is the corresponding buried object identifier. For example, the identity "oid: user _ card _ hoe ", which indicates that the object identifier of the user card is" user _ card _ hoe ", if the embedding is performed at the interface level where the user card is located, the embedding object identifier of the interface level where the user card is located is" user _ card _ hoe ".

In another alternative embodiment, a buried object identifier may be configured for each buried object in the buried object tree in advance, and a developer may configure an identity according to the configured buried object identifier as a corresponding page or element when developing, for example, the buried object identifier in the buried object tree is weibo _ card1, which corresponds to a certain element a of a certain page, and then may configure an identity "oid: weibo _ card1 ".

Based on the parent-child relationships in the buried object tree and the buried object identifiers previously configured for the buried objects in the buried object tree, a chain of buried object identifiers for the current buried object to the root object in the buried object tree may be obtained. Taking the buried point object P3 in the buried point object tree in fig. 3C as an example, the buried point object identification chain corresponding to the buried point object P3 is "oid _ P3| oid _ P2| oid _ P1", where oid _ P3 is the buried point object identification of the buried point object P3, oid _ P2 is the buried point object identification of the buried point object P2, and oid _ P1 is the buried point object identification of the buried point object P1.

In step S520, the location attribute information of the buried object is added to the buried object id chain to obtain the pit bit information of the buried object.

Considering the case that some repeated type elements have the same hierarchy within the page, for example, the object id of each list element in the list multiplexing unit is the same and all belong to the same hierarchy, that is, the object id of each list element in the list multiplexing unit is the object id of the list unit, and the hierarchy of each list element is the hierarchy of the list unit, in this case, if the pit bit information of the buried point object is represented by the buried point object id chain only, it is impossible to distinguish the current exposure from the bottom element in the list unit, and the accuracy of reporting the buried point information is affected.

To solve this problem, in an alternative embodiment, the location attribute information of the buried object may be added to the buried object identification chain to obtain the pit bit information of the buried object. For example, the buried object identification chain corresponding to the buried object a in a certain buried object tree is _ oid1| _ oid2| _ oid3| _ oid4| _ oid5, where the position attribute information of _ oid2 is pos2, the position attribute information of _ oid5 is pos5, and the pit bit information of the buried object a is _ oid1| _ oid2| _ pos2| _ oid3| _ oid4| _ oid 5| _ pos5, that is, the spm of the buried object a is _ oid1| _ oid2| _ pos2| _ oid3| _ oid4| _ oid 5| _ pos 5.

In the above steps S510 to S520, since the buried object identifier chain is determined by the buried object tree, and in order to solve the problem that the description of the pit bit is not accurate due to different instances of the same buried object identifier in the page, the position attribute information of the buried object is added to the buried object identifier chain, so that the accurate pit bit information of each buried object in the buried object tree can be obtained, and the accuracy of reporting the buried object information is improved.

Next, with continuing reference to fig. 1, in step S130, for each of the buried point objects in the buried point object tree, a buried point information reporting parameter value of the buried point object included in the pit bit information of the buried point object is obtained, so as to perform buried point information reporting on each of the buried point objects.

In an optional implementation manner, the reporting parameter value of the buried point information may include at least one of a device type corresponding to the client, a session identifier corresponding to the client, version information of the client, a user identifier corresponding to the client, a buried point object identifier, a buried point object name, and a buried point object content identifier.

In an optional implementation manner, the buried point information reporting parameters may be managed and configured on the basis of objects such as terminals, events, pages, elements, and the like on the visual buried point management platform. Meanwhile, the parent-child relationship of the page and the elements can be configured in the visual embedded point management platform through the operable user interface hierarchy in the page and/or the preset interface parent-child relationship of the user interface hierarchy for bearing user content distribution, so that the embedded point object tree is maintained and generated, and therefore developers can intuitively and conveniently develop the interface hierarchy of the front-end page and embed points in the corresponding interface hierarchy according to the parent-child relationship and the embedded point reporting parameters in the embedded point object tree maintained in the embedded point management platform.

FIG. 6 illustrates a buried object management interface according to an embodiment of the present disclosure. In fig. 6, it can be known that the reporting parameters of the buried point information of the buried point object may include standard parameters and service parameters, and the change of the parameters may be associated with the requirement, the client version, and the required event. And storing the parameter constraint (whether the parameter is necessary or not, the value range constraint of the parameter and the like) corresponding to the version. Meanwhile, the interface shown in fig. 6 also has a function of maintaining a blood relationship, each buried object may maintain its "parent-child" object (i.e., establish a blood relationship with its next-level child object), and the information of the whole buried object tree in the page may be obtained by associating the buried objects layer by layer, and fig. 7 shows a display interface of a buried object tree according to the root public embodiment.

In an optional implementation manner, the buried point reporting parameter value may further include a standard parameter and a service parameter of a buried point object configured in the buried point management platform, and the determined pit bit information of the buried point object.

For example, the obtaining of the buried point information reporting parameter value of the buried point object included in the pit bit information of the buried point object in step S130 includes: according to the sequence of the buried point object identifier contained in the pit bit information of the buried point object in the buried point object identifier chain, traversing the buried point object corresponding to the buried point object identifier in the pit bit information of the buried point object to obtain a buried point information reporting parameter value of the buried point object contained in the pit bit information of the buried point object.

Taking the actual interface level and the buried object tree of the target display page exposed by the trigger operation as an example as shown in fig. 8, the buried points are performed in the interface levels P1, P2, P3, e4, e5, e6 of the target display page, that is, the preset interface parent-child relationship is the parent-child relationship among the interface levels P1, P2, P3, e4, e5, e6, and the parent-child relationship among the interface levels P1, P2, P3, e4, e5, e6 and other interface levels (shown as 81) represented by the dashed circles form the actual interface level of the target display page. As can also be seen from the comparison between the actual interface hierarchy relationship and the buried point object tree in fig. 8, the actual interface hierarchy relationship is much more complex than the interface hierarchy relationship corresponding to the buried point object tree, and the parent-child relationship of the interface hierarchy in which the buried point object is located in the actual interface hierarchy is consistent with the parent-child relationship in the buried point object tree, so that the buried point object tree corresponding to the buried point object in the target display page can be determined according to the parent-child relationship of the interface hierarchy in which the buried point object is located in the target display page.

In fig. 8, for example, the corresponding buried point objects P1, P2, P3, e4, e5 and e6 are identified as P1, P2, P3, e4, e5 and e6, where e4 is the first element in the list multiplexing unit and the position attribute information pos = 1. The pit bit information of P1 is P1, the pit bit information of P2 is P2| P1, the pit bit information of P3 is P3| P2| P1, the pit bit information of e4 is e4:1| P3| P2| P1, the pit bit information of e5 is e5| e4:1| P3| P2| P1, and the pit bit information of e6 is e6| e4:1| P3| P2| P1.

When reporting the embedded point information, for the embedded point object P1, directly reporting the embedded point information reporting parameter value of the embedded point object P1; for the buried point object P2, traversing the corresponding buried point object according to the sequence of P2-P1 to obtain a buried point information reporting parameter value of the corresponding buried point object for reporting, that is, reporting the buried point information reporting parameter value of the buried point object P2 first, and then reporting the buried point information reporting parameter value of the buried point object P1; for a buried point object P3, traversing the corresponding buried point object according to the sequence of P3-P2-P1 to obtain a buried point information reporting parameter value of the corresponding buried point object for reporting, namely reporting the buried point information reporting parameter value of the buried point object P3, reporting the buried point information reporting parameter value of the buried point object P2, and reporting the buried point information reporting parameter value of the buried point object P3; similar reporting of the embedded point information is also performed for the embedded point objects e4, e5 and e6, and details are not described here.

For each embedded point object, when reporting the embedded point information parameter value, reporting the embedded point information reporting parameter value of the embedded point object, finding a father node of the embedded point object according to the parent-child relationship in the embedded point object tree, reporting the embedded point information reporting parameter value of the father node, finding the father node of the father node by the father node, repeating the steps until finding a root node, and finally reporting the embedded point information reporting parameter value of the root node, thereby completing the reporting of the embedded point information parameter value of the embedded point object.

In an optional implementation manner, the buried point attribution parameter may be further determined, and a buried point information reporting parameter value may be further reported based on the buried point attribution parameter, so as to facilitate subsequent buried point attribution analysis.

For any client, such as any APP (application) client or browser client, there are often the following situations: different users can start to enter the client, the same user can also start the client repeatedly, meanwhile, the user can enter and exit for multiple times or open multiple same pages simultaneously in one start, and multiple click behaviors can be generated on an interactive object in one page.

In order to strictly and accurately express and position the accurate position and time of a certain buried point event, when the buried point is subjected to attribution, the condition needs to be considered, a unique index of a buried point information reporting parameter value can be established in a database of the buried point information reporting parameter value through the buried point attribution parameter, and then the accurate buried point information reporting parameter value can be found according to the unique index so as to accurately attribute and analyze the user behavior.

In an alternative embodiment, different users may be distinguished according to the device identifiers used by the users or the user identifiers of the users themselves, and the unique identifier capable of distinguishing different users may be represented as userid.

For a certain start of the client, it can be identified by a session identification Sessionid corresponding to a single start. In particular, a unique Seesionid value may be generated with the timestamp of the time of the boot, thereby distinguishing between different boots.

Since a single user of the same page may repeatedly enter, multiple same pages may also be opened at the same time (i.e., multiple instances of the same page object may occur, and multiple exposures of the same instance may occur). In order to distinguish different pages, in an alternative embodiment, a specific certain exposure of a certain page buried object may be identified by using a depth of use of page exposure, and the depth of use of page exposure may be represented by a parameter "pgstep", which takes a value of an exposure sequence of pages after a client cold starts. That is, after the client is cold started, the value of the use depth parameter pgstep of the page exposure is increased by 1 every time a page exposure occurs, even if the page exposure enters into rollback, or if the page exposure is switched between foreground and background, the value of the use depth parameter pgstep is correspondingly increased by self, and the page exposure is reset along with the change of the Seessionid and is counted from 1 every time.

The same page has different exposure sequences in different exposures. For example, after a client is started up, page 1 (typically the first page) is exposed first, and then page 2, page 3, page 4, page 3, and page 5 are exposed in sequence based on a series of operation behaviors of a user, so that the exposure sequence of the pages is "page 1: pgstep = 1; page 2: pgstep = 2; page 3: pgstep = 3; page 4: pgstep = 4; page 3: pgstep = 5; page 5: pgstep =5 ". During this client startup, page 3 is exposed twice, but the two exposures of page 3 have different exposure sequences. When the next cold boot occurs after the client shuts down, pgstep starts counting again from 1. In other words, pgstep may record the exposure order of all pages during this client startup, which is for all pages during the current client startup, and as soon as page exposure occurs, pgstep increases by unit 1 to indicate that the currently exposed page is the page that was exposed the next after the client startup.

Since multiple interaction events may occur within the same page. In order to distinguish multiple interaction events in the same page, sequence numbers of the interaction events in a single page are used for identifying the interaction events in different times, the sequence numbers can be represented by a parameter 'actseq', in one exposure of a root page (rootpage), each time an interaction event (clicking/sliding/pull-down refreshing and the like) occurs, the value of the actseq is correspondingly increased by 1, and the actseq is reset along with the change of pgstep values of the root page of elements corresponding to the interaction events, namely when the interaction events enable the exposed root page to change, the pgstep is increased by 1, and meanwhile, the actseq is counted again from 1.

For example, there are two elements A1, A2 in the A page; the page B comprises two elements B1 and B2; after a certain client startup, the user operation path is "enter a page-click a 1-click a 2-enter B page-click B1-click B2-return a page-click a 1-click a 2", then the change process of pgstep and actionseq is "a page pgstep = 1-pgstep = 1/actionseq = 2-B page pgstep = 2-pgstep = 2/actionseq = 1-pgstep = 2/actionseq = 2-a page step = 3-step = 3/actionseq = 1-pgstep = 3/actionseq = 2".

Wherein, a page pgstep =1 indicates that the a page is the page exposed first during the starting of the client at this time; pgstep = 1/actseq =1 indicates that click element a1 is the first interaction event that occurs in the a page at the first exposure of the a page; pgstep = 1/actseq =2 indicates that click element a2 is two interactive events that occur in the a page at the first exposure of the a page; b page pgstep =2 indicates that the B page is now the page of the second exposure during the client's startup; pgstep = 2/actseq =1 indicates that in page B, which is the second exposure of the client at this time, click element B1 is the first interaction event that occurs in page B this time; pgstep = 2/actseq =2 indicates that in page B, which is the second exposure of the client at this time, click element B2 is the second interaction event that occurs in page B this time; the a page pgstep =3 indicates that the page a is the page exposed at the 3 rd time after the client starts; pgstep = 3/actseq =1 indicates that in the third page a exposed by the client at this time, click element a1 is the first interaction event sent in page a this time; pgstep = 3/actseq =2 indicates that in the third page a exposed by the client at this time, click element a2 is the second interaction event that occurred in page a this time.

From the above analysis, pgstep and actseq can distinguish the case where the same page is exposed for multiple times and the same trigger interaction event occurs for multiple times in the same page, and can specifically determine the page in which each interaction event is the second interaction event in the second exposure.

Further, by configuring the parameter actseq representing the sequence number of the occurrence of the interaction event in the sub-page of the current interaction element to be reset with the change of the root page of the current interaction element, rather than with the change of the sub-page of the current interaction element, because the root page is generally a fully-blocked bottom or top page, attribution analysis across multiple sub-pages can be realized, rather than being limited to a single sub-page.

Through the analysis, for the user log of the client, a unique interaction event can be indexed through the user id, the Seesionid, the spm (pit bit information), the pgstep of the root page and the actionseq; the unique position of the object during the cold start of the client can be accurately determined through the combination of userid, Seesionid, spm (pit bit information) and pgstep of the root page.

During a single user launch, "userid + Seesionid" is left unchanged, and can be obtained directly from the buried point attributed to the starting point, e.g., page 1 is currently exposed, and when the exposure of page 1 is attributed (i.e., when it is determined what action or event caused page 1 to be exposed), page 1 is the buried point attributed to the starting point.

Further, for three information, namely "spm (pit bit information)", "pgstep of root page" and "actseq", when interacting with the current element, the three parameter information of the current element are acquired and transmitted together to the next page exposed by the interaction event, so that the embedded point attribution parameter is determined by the three parameter information transmitted, and the attribution analysis is performed on the page exposure so as to determine the source of the page exposure.

In an alternative embodiment, the type of the current buried object corresponding to the trigger operation may have different forms of buried-point attribution parameters, where the buried-point attribution parameters may be identified by refer.

Specifically, when the current buried point object corresponding to the trigger operation is a page, the buried point attribution parameter refer may be represented as: [ p ] [ pgstep (subpage) ] [ pgstep (rootpage) ] [ spm (subpage) ]; wherein, p represents that the current embedded point object is a page type, and pgstep (subpage) can be understood as the pgstep of the current page, that is, the current page is the page exposed for the second time (or the third time) after the client is started; the pgstep (rootpage) can be understood as the pgstep of the root page of the current page, that is, the root page of the current page is the page exposed for the second time (or for the second time) after the client starts, and spm (subpage) is the pit bit information of the current page.

When the current buried point object corresponding to the trigger operation is an element, the buried point attribution parameter refer may be expressed as [ e ] [ actseq ] [ pgstep (rootpage) ] [ spm (element) ]. e represents that the current embedded point object is of an element type, and the actseq can be understood as the interaction event occurring in the root page of the current element when the current element is triggered; the pgstep (rootpage) can be understood as the pgstep of the root page of the page where the current element is located, that is, the root page of the page where the current element is located is the page exposed for the second time (or the third time) after the client is started, and spm (element) is the pit bit information of the element corresponding to the current trigger operation.

It should be noted that [ ] in the above representation of refer is merely exemplary, and it is within the scope of the present disclosure that the buried point reporting parameter value includes the information in the refer.

The current embedded point object corresponding to the trigger operation may be understood as a page that is triggered for the embedded point page of the client, and the current embedded point object corresponding to the trigger operation may be understood as an element that is triggered for the embedded point element of the client. For example, if element 1 in page 1 of the click client jumps to page 2 (i.e., the target display page exposed by the trigger operation of click element 1 is page 2), then the current buried point object corresponding to the trigger operation is element 1. And returning to the page 1 from the page 2 (namely, the target display page exposed by the return operation in the page 2 is the page 1), then the current buried point object corresponding to the trigger operation is the page 2.

Based on the buried point attribution parameters, different forms of buried point attribution parameter values can be determined according to different buried point attribution requirements, and different buried point attribution analysis scenes are further adapted.

In an optional implementation manner, a first buried point attribution parameter value may be determined based on the buried point attribution parameter, and the first buried point attribution parameter value is reported as a buried point information reporting parameter value, that is, the buried point information reporting parameter value may include the first buried point attribution parameter value.

Specifically, the first buried point attribution parameter value may be determined by:

when the type of a current embedded point object corresponding to a trigger operation is a page, determining a first embedded point attribution parameter value of the embedded point object in a target display page exposed by the trigger operation according to a page exposure sequence of the page where the current embedded point object is located after the client is started, a page exposure sequence of the page where a root object of the current embedded point object is located after the client is started and pit bit information of the current embedded point object, wherein the unit value is increased by the value of the page exposure sequence every time page exposure occurs after the client is started, and the value of the page exposure sequence restarts counting along with the restart of the client;

when the type of the current embedded point object corresponding to the triggering operation is an element, determining a first embedded point attribution parameter value of the embedded point object in a target display page exposed by the triggering operation according to the triggered sequence of the element in the page where the element is located, the page exposure sequence of the page where the root object of the current embedded point object is located and the pit bit information of the current embedded point object, wherein in the page where the element is located, each time the element triggering operation occurs, the triggered sequence value of the element in the page where the element is located increases by a unit numerical value, and the triggered sequence value of the element in the page where the element is located restarts counting along with the change of the page exposure sequence of the page where the root object of the current embedded point object is located.

For example, the value of the page exposure order may be understood as the value of pgstep described above. When the current type of the buried point object corresponding to the current trigger operation is a page, the first buried point attribution parameter value may include 3 pieces of parameter information, which are a pgstep of the page where the current buried point object is located, a pgstep of the page where the root object of the current buried point object is located, and pit bit information of the current buried point object, respectively. When the current type of the current embedded point object corresponding to the current trigger operation is an element, the first embedded point attribution parameter value may also include 3 pieces of parameter information, which are respectively the value of the actseq of the current element, the value of the pgstep of the page where the root object of the current element is located, and the pit bit information of the current element.

And reporting the relevant information of the current embedded point object as a first embedded point parameter value of a target display page exposed by triggering operation, and determining the exposure source of each embedded point object in the target display page through the first embedded point attribution parameter value. The first embedded point attribution parameter value can record all operation paths of the user, and two entering processes of the user entering a certain page and returning to the same page can be well distinguished, so that the accuracy of embedded point attribution can be improved.

In an optional embodiment, the method further comprises: determining an original buried point object for which an original trigger operation of the target display page is created; determining a second buried point attribution parameter value of the buried point object in the target display page according to the type of the original buried point object aimed at by the original trigger operation, and reporting the second buried point attribution parameter value;

wherein the second buried point attribution parameter value is determined by:

when the type of an original embedded point object aimed at by the original trigger operation is a page, determining a second embedded point attribution parameter value of the embedded point object in the target display page according to a page exposure sequence of the page where the original embedded point object is located after the client is started, a page exposure sequence of the page where a root object of the original embedded point object is located after the client is started and pit bit information of the original embedded point object, wherein after the client is started, each time page exposure occurs, the value of the page exposure sequence is increased by a unit value, and the value of the page exposure sequence restarts counting along with the restart of the client;

when the type of the original embedded point object corresponding to the original triggering operation is an element, determining a second embedded point attribution parameter value of the embedded point object in the target display page according to the triggered sequence of the element in the page where the element is located, the exposure sequence of the page where the root object of the original embedded point object is located and the pit bit information of the original embedded point object, wherein the triggered sequence value of the element in the page where the element is located increases by a unit numerical value every time the element triggering operation occurs, and the triggered sequence value of the element in the page where the element is located restarts counting along with the change of the page exposure sequence of the page where the root object of the original embedded point object is located.

For example, the value of the page exposure order of the second buried point attribution parameter value may be understood as the value of pgstep described above. When the original buried object type corresponding to the original trigger operation is a page, the first buried attribution parameter value may include 3 pieces of parameter information, which are pgstep of the page where the original buried object is located, pgstep of the page where the root object of the original buried object is located, and pit bit information of the original buried object, respectively. When the original buried point object type corresponding to the original trigger operation is an element, the first buried point attribution parameter value may also include 3 pieces of parameter information, which are respectively the value of actseq of the element corresponding to the original buried point object, the value of pgstep of the page where the root object of the element corresponding to the original buried point object is located, and the pit bit information of the element corresponding to the original buried point object.

In an exemplary embodiment, the original trigger operation may be understood as a trigger operation that creates a target display page, and a buried point object corresponding to the original trigger operation is an original buried point object. For example, for page 2, click element A on page 1 into page 2, click element B on page 2 into page 3, exit from page 3 back to page 2. In the whole process, the page 2 is exposed for 2 times, wherein the operation of exposing the page 2 for the first time, namely the operation of clicking the element A, is the original trigger operation, the element A is the original buried point object, and the return operation of exposing the page 2 for the second time does not belong to the original trigger operation. That is, the second buried-point attribution parameter value is the same in both exposures of page 2.

In other words, unlike the first buried point attribution parameter value, the second buried point attribution parameter value may only record the actual created open source of the page, ignoring the deeper incoming and returning paths of the page. The cross-page attribution for the same user may be made during a single client boot by the first buried point attribution parameter value and the second buried point attribution parameter value.

Fig. 9 is a schematic diagram illustrating a change of an exposed display page corresponding to a series of operations performed by a user according to an embodiment of the present disclosure. Next, the first buried point attribution parameter value and the second buried point attribution parameter value are further explained by taking fig. 9 as an example.

In FIG. 9, the user has clicked song list 1 in page 1, which action exposes page 2; the user clicks the play all in page 2 again, and the action exposes page 3 (i.e. play page); the user performs a return operation in page 3 to return to page 2 again, causing page 2 to be exposed a second time.

In fig. 9, for the first buried point attribution parameter value of the page 2, at the time of the first exposure of the page 2, it is a buried point attribution parameter refer for clicking an element in the page 1, that is, refer when the current buried point object is an element type, which may specifically include: the actseq of the song list 1, namely the sequence value of the song list 1 clicked in the current exposure of the root page of the page where the song list 1 is located, the exposure sequence of the root page of the page where the song list 1 is located after the client is started and the pit position information of the song list 1. In the second exposure of the page 2, the first buried point attribution parameter value of the page 2 is refer of the page 3, that is, the refer when the current buried point object is the page type, which may specifically include: the exposure sequence value of the page 3 after the client is started, the exposure sequence value of the root page of the page 3 after the client is started, and the pit bit information of the page 3.

For the second buried point attribution parameter values of the page 2 in the two exposures, which are both buried point attribution parameters refer for clicking elements in the page 1, that is, both refer when the current buried point object is an element type, specifically, the following may be included: the actseq of the song list 1, namely the sequence value of the song list 1 clicked in the current exposure of the root page of the page where the song list 1 is located, the exposure sequence of the root page of the page where the song list 1 is located after the client is started and the pit position information of the song list 1. Since the second buried point attribution parameter value records the actual creation open source of the page, the actual opening of page 2 in fig. 9 is the source of clicking song list 1 in page 1.

For example, the third buried point attribution parameter value may be used to store the session identifier Sessionid when the client performs the last cold start, so that the relationship between the client and different cold starts may be established through the third buried point attribution parameter value, and the correlation analysis may be performed on the user behavior between the client and different cold starts.

Further, in the present disclosure, the point may be buried in the client or may be buried in the server. For example, after a certain focus button is clicked in the client, the client reports a click point burying event of the button, but whether an actual server execution result of the focus button is successful or not is often required to be buried in the server.

Based on this, according to the data analysis requirement, the network request of the client may be associated with a certain interactive object (the interactive object may be a page or an element), specifically, the network request of the client may be directly agreed through the API protocol to associate the interactive object, when a certain trigger operation occurs, the server embedded point object pre-associated with the network request corresponding to the trigger operation may be determined, and then the embedded point attribution parameter of the server embedded point object is reported.

In an optional embodiment, the method further comprises: determining a server end buried point object pre-associated with the triggering operation; reporting a fourth buried point attribution parameter value corresponding to the server end buried point object;

wherein the fourth buried point attribution parameter value is determined by:

when the type of the current embedded point object corresponding to the trigger operation is a page, determining a fourth embedded point attribution parameter value of the embedded point object in a target display page exposed by the trigger operation according to the page exposure sequence of the page where the current embedded point object is located after the client is started, the page exposure sequence of the page where the root object of the current embedded point object is located after the client is started and the pit bit information of the current embedded point object, wherein the unit value is increased for the value of the page exposure sequence every time the page exposure occurs after the client is started, and the value of the page exposure sequence restarts counting along with the restart of the client;

when the type of the current embedded point object corresponding to the triggering operation is an element, determining a fourth embedded point attribution parameter value of the embedded point object in the target display page exposed by the triggering operation according to the triggered sequence of the element in the page where the element is located, the exposure sequence of the page where the root object of the current embedded point object is located and the pit bit information of the current embedded point object, wherein in the page where the element is located, each time the element triggering operation occurs, the triggered sequence value of the element in the page where the element is located increases by a unit numerical value, and the triggered sequence value of the element in the page where the element is located restarts counting along with the change of the page exposure sequence of the page where the root object of the current embedded point object is located.

Compared with the related art, the method and the device can realize the cross-page and cross-start buried point attribution analysis and improve the accuracy of the buried point attribution analysis. Meanwhile, different buried point attribution parameter values are provided for different attribution analysis scenes, so that the data volume during buried point attribution analysis can be reduced, and the efficiency of buried point attribution analysis is improved.

According to the method for reporting the buried point information, the consistency description of the pit position information of the buried point can be realized in different clients (Android/Ios/pc/mac/H5/ReactNative/Flutter and the like), and the stability and the accuracy of the pit position information of the buried point can be ensured. Meanwhile, through the visual management of the buried points based on the objects, the maintenance cost of the buried points can be greatly reduced, and the rapid acquisition of the parameters of the buried points can be promoted; and because the definition of the embedded point object is a visual UI page or component oriented to the product, the embedded point object can be easily butted with a routing system, a UI component system and the like, and the communication cost, the maintenance cost and the development cost in the embedded point process are further reduced.

Furthermore, through the reported different types of buried point attribution parameters, the cross-starting and cross-page complex accurate attribution logic can be realized, the accuracy of buried point attribution analysis is improved, the workload of data analysis of the buried point attribution is greatly reduced, and the efficiency of the buried point attribution analysis is improved.

Next, the present disclosure also provides a point burying method. Fig. 10 shows a schematic diagram of a method of burying a point according to an embodiment of the present disclosure. Referring to fig. 10, the dotting method may include steps S1010 to S1030.

Step S1010, determining a preset buried point object tree of the display page of the point to be buried according to the preset interface parent-child relationship of the display page of the point to be buried.

Step S1020, configuring a buried point object identifier and a buried point information reporting parameter for each buried point object in the preset buried point object tree.

Step S1030, for each embedded point object in the preset embedded point object tree, embedding a point in an interface corresponding to the embedded point object according to the embedded point object identifier and the embedded point information reporting parameter, so that the client reports the embedded point information according to the preset embedded point object tree determined by the preset interface parent-child relationship after receiving the trigger operation of exposing the display page of the to-be-embedded point.

Each step in fig. 10 will be specifically described below.

The display page of the to-be-buried point can be any display page in the client, and can be determined in a user-defined mode according to the demand of the buried point. The display page of the to-be-buried point can be understood as a page which is not really displayed on a client side, and is only based on the page at the time of UI design, and a developer does not really realize the display page.

In an optional implementation manner, the preset interface parent-child relationship of the to-be-buried point display page is determined by the following method: and determining a preset interface parent-child relationship of an operable user interface in the display page of the point to be buried and/or a user interface bearing user distribution content based on a user interface component of the display page of the point to be buried.

For example, the method for determining the preset interface parent-child relationship of the to-be-buried point display page may refer to the description of step S210, and the technical term "target display page" in the description of step S210 may be replaced by "to-be-buried point display page", which is not described herein again.

In an optional implementation manner, a page or an element corresponding to each interface level in a preset interface parent-child relationship of the interface level of the to-be-buried point display page may be used as a buried point object, so that the parent-child relationship of each buried point object in the to-be-buried point display page is determined based on the preset interface parent-child relationship, and then the preset buried point object tree of the to-be-buried point display page is determined.

In an alternative embodiment, the blood-related relationship of each display page or element in the above-mentioned buried point management platform may be configured according to the preset interface parent-child relationship, so as to generate the preset buried point object tree in the buried point management platform. As mentioned above, each page or element establishes a connection with its "parent-child" object, i.e. child node using itself as parent node, through the relationship between blood factors, and after associating layer by layer, the buried object tree of the page to be displayed can be obtained.

After the preset buried point object tree of the display page to be buried is determined, referring to step S1020 in fig. 10, a buried point object identifier and a buried point information reporting parameter are configured for each buried point object in the preset buried point object tree.

In an alternative embodiment, the buried point management platform may configure the buried point object identifier and the buried point information reporting parameter for each buried point object in the preset buried point object tree. An exemplary display interface for a landfill management platform may be as described above with respect to FIG. 6. In the buried point management platform, each buried point object corresponds to a first buried point detail page, so that the relevant information of the buried point object is configured in the buried point detail page. For example, the buried point object id _ iod, the buried point information reporting parameter, etc., where the buried point information reporting parameter may include at least one of a device type corresponding to the client of the buried point, a session id corresponding to the client, version information of the client, a user id corresponding to the client, a buried point object name, a buried point object content id, pit information, the first buried point attribution parameter, the second buried point attribution parameter, the third buried point attribution parameter, and the fourth buried point attribution parameter.

Next, in step S1030, for each buried point object in the preset buried point object tree, performing buried point embedding in an interface corresponding to the buried point object according to the buried point object identifier and the buried point information reporting parameter, so that after receiving a trigger operation for exposing the display page of the to-be-buried point, the client performs buried point information reporting according to the preset buried point object tree determined by the preset interface parent-child relationship.

In an optional implementation manner, a developer may perform embedding on a corresponding interface level of a client according to embedded point object tree information and embedded point reporting parameter information in the embedded point management platform, or associate a trigger operation of the client with an embedded point of a server to perform embedding on the server.

Meanwhile, a developer can develop the page according to the preset interface relationship, so that the client can render the page to be displayed according to the preset interface relationship.

Therefore, after receiving the trigger operation of exposing the display page of the to-be-buried point, the client can determine the buried point object tree (namely the preset buried point object tree) of the display page of the to-be-buried point according to the parent-child relationship of the preset interface, then determine the pit bit information of the buried point object according to the parent-child relationship of the buried point object tree, and report the buried point information based on the pit bit information. That is, after receiving the trigger operation of exposing the display page of the to-be-buried point, the client may execute the above steps shown in fig. 1 to report the buried point information.

According to the point burying method, the preset point burying object tree determined based on the preset interface parent-child relationship can avoid the problem that the information of the pit positions of the buried points in different versions and different types of clients is inconsistent, the difference of the buried points at different ends is reduced, the maintenance and management cost of the buried points is further reduced, and the development efficiency of the buried points is improved.

Exemplary devices

The exemplary embodiment of the present disclosure further provides a reporting device of the embedded point information. Referring to fig. 11, the apparatus 1100 for reporting the burial point information may include:

a buried point object tree determining module 1110, configured to determine, in response to a trigger operation for a client, a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation;

a pit-bit-information determining module 1120 configured to determine pit bit information of a buried point object in the buried point object tree according to a parent-child relationship in the buried point object tree;

a buried point information reporting module 1130, configured to obtain, for each buried point object in the buried point object tree, a buried point information reporting parameter value of the buried point object included in the pit bit information of the buried point object, so as to report the buried point information of each buried point object.

In an alternative embodiment, the buried point object tree determination module 1110 is further specifically configured to: and determining a buried point object tree corresponding to a buried point object in the target display page exposed by the trigger operation according to the preset interface parent-child relationship of the target display page.

In an optional implementation manner, the reporting apparatus 1100 of the burial point information further includes a pre-burial point module, where the pre-burial point module is configured to:

determining a preset interface parent-child relationship of an operable user interface in the target display page and/or a user interface bearing user distribution content based on a user interface component of the target display page, so that the client generates the target display page according to the preset interface parent-child relationship;

and determining a buried point object tree corresponding to a buried point object in the target display page according to the preset interface parent-child relationship of the target display page, so that the client buries points in a corresponding user interface according to the buried point object in the buried point object tree.

In an optional implementation, the pit bit information determining module 1120 is further specifically configured to:

performing the following for each buried object in the buried object tree:

determining a buried point object identification chain from the buried point object to a root object in the buried point object tree based on the parent-child relationship in the buried point object tree and a buried point object identification configured for the buried point object in the buried point object tree in advance;

and adding the position attribute information of the buried point object in the buried point object identification chain to obtain the pit bit information of the buried point object.

In an optional implementation manner, the buried point information reporting module 1130 is further specifically configured to:

according to the sequence of the buried point object identifier contained in the pit bit information of the buried point object in the buried point object identifier chain, traversing the buried point object corresponding to the buried point object identifier in the pit bit information of the buried point object to obtain a buried point information reporting parameter value of the buried point object contained in the pit bit information of the buried point object.

In an optional implementation manner, the reporting parameter value of the buried point information includes a first buried point attribution parameter value, where the first buried point attribution parameter value is determined by:

when the type of the current embedded point object corresponding to the trigger operation is a page, determining a first embedded point attribution parameter value of the embedded point object in a target display page exposed by the trigger operation according to a page exposure sequence of the page where the current embedded point object is located after the client is started, a page exposure sequence of the page where a root object of the current embedded point object is located after the client is started and pit bit information of the current embedded point object, wherein the unit value is increased for the page exposure sequence every time page exposure occurs after the client is started, and the value of the page exposure sequence restarts counting along with the restart of the client;

In an optional implementation manner, the reporting apparatus 1100 of the buried point information further includes a second buried point attribution parameter value reporting module, configured to:

determining an original buried point object for which an original trigger operation of the target display page is created;

determining a second buried point attribution parameter value of the buried point object in the target display page according to the type of the original buried point object aimed at by the original trigger operation, and reporting the second buried point attribution parameter value;

wherein the second buried point attribution parameter value is determined by: when the type of an original embedded point object aimed at by the original trigger operation is a page, determining a second embedded point attribution parameter value of the embedded point object in the target display page according to a page exposure sequence of the page where the original embedded point object is located after the client is started, a page exposure sequence of the page where a root object of the original embedded point object is located after the client is started and pit bit information of the original embedded point object, wherein after the client is started, each time page exposure occurs, the value of the page exposure sequence is increased by a unit value, and the value of the page exposure sequence restarts counting along with the restart of the client;

In an optional implementation manner, the apparatus 1100 for reporting buried point information further includes a third buried point attribution parameter value reporting module, which is specifically configured to:

and determining a third buried point attribution parameter value of the buried point object in the target display page according to the session identifier when the client is started for the last time, and reporting the third buried point attribution parameter value.

In an optional implementation manner, the apparatus 1100 for reporting buried point information further includes a fourth buried point attribution parameter value reporting module, which is specifically configured to:

determining a server end buried point object pre-associated with the triggering operation; reporting a fourth buried point attribution parameter value corresponding to the server end buried point object;

wherein the fourth buried point attribution parameter value is determined by:

The exemplary embodiment of the present disclosure also provides a buried point device 1200, as shown in fig. 12, the buried point device 1200 may include:

a preset buried point object tree determining module 1210, configured to determine a preset buried point object tree of a to-be-buried point display page according to a preset interface parent-child relationship of the to-be-buried point display page;

a buried point reporting parameter configuring module 1220 configured to configure a buried point object identifier and a buried point information reporting parameter for each buried point object in the preset buried point object tree;

the point burying module 1230 is configured to bury points in an interface corresponding to the buried point object according to the buried point object identifier and the buried point information reporting parameter for each buried point object in the preset buried point object tree, so that the client reports the buried point information according to the preset buried point object tree after receiving the trigger operation of exposing the display page of the to-be-buried point.

In addition, other specific details of the embodiments of the present disclosure have been described in detail in the embodiments of the invention of the above method, and are not described herein again.

Exemplary storage Medium

The storage medium of the exemplary embodiment of the present disclosure is explained below.

In the present exemplary embodiment, the above-described method may be implemented by a program product, such as a portable compact disc read only memory (CD-ROM) and including program code, and may be executed on a device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RE, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Exemplary electronic device

An electronic device of an exemplary embodiment of the present disclosure is explained with reference to fig. 13. The electronic device may be a client or a server.

The electronic device 1300 shown in fig. 13 is only an example and should not bring any limitations to the function and scope of use of the embodiments of the present disclosure.

As shown in fig. 13, the electronic device 1300 is in the form of a general purpose computing device. The components of the electronic device 1300 may include, but are not limited to: at least one processing unit 1310, at least one memory unit 1320, a bus 1330 connecting different system components including the memory unit 1320 and the processing unit 1310, a display unit 1340.

Where the memory unit stores program code, the program code may be executed by the processing unit 1310 to cause the processing unit 1310 to perform the steps according to various exemplary embodiments of the present disclosure described in the above section "exemplary methods" of this specification. For example, processing unit 1310 may perform the method steps shown in fig. 1, and so on.

The memory unit 1320 may include volatile memory units, such as a random access memory unit (RAM) 1321 and/or a cache memory unit 1322, and may further include a read only memory unit (ROM) 1323.

Storage 1320 may also include a program/utility 1324 having a set (at least one) of program modules 1325, such program modules 1325 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 1330 may include a data bus, an address bus, and a control bus.

The electronic device 1300 may also communicate with one or more external devices 1400 (e.g., keyboard, pointing device, bluetooth device, etc.) via an input/output (I/O) interface 1350. The electronic device 1300 also includes a display unit 1340 connected to the input/output (I/O) interface 1350 for display. Also, the electronic device 1300 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) through the network adapter 1360. As shown, the network adapter 1360 communicates with other modules of the electronic device 1300 via the bus 1330. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with the electronic device 1300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

It should be noted that although in the above detailed description several modules or sub-modules of the apparatus are mentioned, such division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the units/modules described above may be embodied in one unit/module, in accordance with embodiments of the present disclosure. Conversely, the features and functions of one unit/module described above may be further divided into embodiments by a plurality of units/modules.

Further, while the operations of the disclosed methods are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

While the spirit and principles of the present disclosure have been described with reference to several particular embodiments, it is to be understood that the present disclosure is not limited to the particular embodiments disclosed, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A reporting method of embedded point information is characterized by comprising the following steps:

responding to a trigger operation aiming at a client, and determining a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation;

determining pit position information of the buried point object in the buried point object tree according to the parent-child relationship in the buried point object tree;

and acquiring a buried point information reporting parameter value of the buried point object contained in the pit bit information of the buried point object aiming at each buried point object in the buried point object tree so as to report the buried point information of each buried point object.

2. A method as claimed in claim 1, wherein the determining a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation includes:

and determining a buried point object tree corresponding to a buried point object in the target display page exposed by the trigger operation according to the preset interface parent-child relationship of the target display page.

3. A reporting method of the embedded point information as claimed in claim 2, wherein the method further comprises:

4. A reporting method of embedded point information as claimed in claim 1, wherein the determining the pit bit information of the embedded point object in the embedded point object tree according to the parent-child relationship in the embedded point object tree includes:

performing the following for each buried object in the buried object tree:

5. The method according to claim 4, wherein the obtaining of the value of the buried point information reporting parameter of the buried point object included in the pit bit information of the buried point object comprises:

6. The reporting method of the buried point information according to any one of claims 1 to 5, wherein the buried point information reporting parameter value includes at least one of a device type corresponding to the client, a session identifier corresponding to the client, version information of the client, a user identifier corresponding to the client, a buried point object identifier, a buried point object name, and a buried point object content identifier.

7. A reporting method as claimed in claim 1, wherein the reporting parameter value of the buried point information includes a first buried point attribution parameter value, and the first buried point attribution parameter value is determined by:

8. A reporting method of the embedded point information as claimed in claim 1, wherein the method further comprises:

wherein the second buried point attribution parameter value is determined by:

9. A reporting method of the embedded point information as claimed in claim 1, wherein the method further comprises:

10. A reporting method of the embedded point information as claimed in claim 1, wherein the method further comprises:

determining a server end buried point object pre-associated with the triggering operation;

reporting a fourth buried point attribution parameter value corresponding to the server end buried point object;

wherein the fourth buried point attribution parameter value is determined by:

11. A method of burying a point, comprising:

determining a preset buried point object tree of a display page of a point to be buried according to a preset interface parent-child relationship of the display page of the point to be buried;

configuring a buried point object identifier and a buried point information reporting parameter for each buried point object in the preset buried point object tree;

and for each embedded point object in the preset embedded point object tree, embedding points in an interface corresponding to the embedded point object according to the embedded point object identification and the embedded point information reporting parameter, so that after a client receives a triggering operation of exposing the display page of the to-be-embedded point, the embedded point information is reported according to the preset embedded point object tree determined by the preset interface parent-child relationship.

12. The point burying method of claim 11, wherein the preset interface parent-child relationship of the display page of the point to be buried is determined by:

and determining a preset interface parent-child relationship of an operable user interface in the display page of the point to be buried and/or a user interface bearing user distribution content based on the user interface component of the display page of the point to be buried.

13. A reporting device of embedded point information is characterized by comprising:

the buried point object tree determining module is configured to respond to a trigger operation aiming at a client and determine a buried point object tree corresponding to a buried point object in a target display page exposed by the trigger operation;

a pit position information determining module configured to determine pit position information of a buried point object in the buried point object tree according to a parent-child relationship in the buried point object tree;

and the buried point information reporting module is configured to acquire a buried point information reporting parameter value of the buried point object contained in the pit bit information of the buried point object for each buried point object in the buried point object tree, so as to report the buried point information of each buried point object.

14. A point burying device, comprising:

the preset embedded point object tree determining module is configured to determine a preset embedded point object tree of a display page to be embedded according to a preset interface parent-child relationship of the display page to be embedded;

a buried point reporting parameter configuration module configured to configure a buried point object identifier and a buried point information reporting parameter for each buried point object in the preset buried point object tree;

and the point burying module is configured to bury points in an interface corresponding to the buried point object according to the buried point object identifier and the buried point information reporting parameter for each buried point object in the preset buried point object tree, so that the client reports the buried point information according to the preset buried point object tree after receiving the triggering operation of exposing the display page of the to-be-buried point.

15. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, carries out the method according to any one of claims 1 to 12.

16. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out the method of any one of claims 1 to 12.