CN113553269B

CN113553269B - Page embedded point reporting method and related device

Info

Publication number: CN113553269B
Application number: CN202110852306.XA
Authority: CN
Inventors: 李瑶; 孟湘琴; 肖改; 郑茹玉
Original assignee: Shenzhen Tencent Domain Computer Network Co Ltd
Current assignee: Shenzhen Tencent Domain Computer Network Co Ltd
Priority date: 2021-07-27
Filing date: 2021-07-27
Publication date: 2024-04-12
Anticipated expiration: 2041-07-27
Also published as: CN113553269A

Abstract

The embodiment of the application provides a method and a related device for reporting a buried point of a page, wherein the method comprises the following steps: adding configuration parameter related information in a software development kit, wherein the configuration parameter related information is used for configuring a manner of reporting operation of a buried point; constructing a hook function provided by a frame according to a preset interface, and constructing a buried point reporting program of the page; adding the embedded point reporting program into the software development kit; embedding the software development kit into the page, so that an access terminal obtains the page embedded with the software development kit when accessing the page, and performing embedded point reporting operation on the page according to embedded point reporting programs and configuration parameter related information in the software development kit. The technical scheme provided by the embodiment of the application can obviously reduce the code quantity and development cost of project development, can rapidly realize the development of the embedded point reporting function aiming at a plurality of embedded point demands and even a plurality of projects, and improves the project development efficiency.

Description

Page embedded point reporting method and related device

Technical Field

The application relates to the technical field of front-end development, in particular to a method and a related device for reporting a buried point of a page.

Background

The embedded point reporting technology has become one of the important means for acquiring the behavior data of the user on the page, and is an important tool for assisting the product operators. Currently, when a front-end page project is constructed, in order to realize a function of reporting a buried point of a page, front-end development engineers are mostly required to manually write corresponding codes in the project according to specific buried point requirements. In this way, codes are manually written according to different projects and even different embedded point requirements, so that the code quantity and cost of project development are high, and the efficiency is quite low.

Disclosure of Invention

The embodiment of the application provides a page embedded point reporting method and a related device, which can reduce code quantity and cost of project development at least to a certain extent and improve project development efficiency.

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

According to an aspect of the embodiments of the present application, there is provided a method for reporting a buried point of a page, where the method includes: adding configuration parameter related information in a software development kit, wherein the configuration parameter related information is used for configuring a manner of reporting operation of a buried point; constructing a hook function provided by a frame according to a preset interface, and constructing a buried point reporting program of the page; adding the embedded point reporting program into the software development kit; embedding the software development kit into the page, so that an access terminal obtains the page embedded with the software development kit when accessing the page, and performing embedded point reporting operation on the page according to embedded point reporting programs and configuration parameter related information in the software development kit.

According to an aspect of the embodiments of the present application, there is provided a device for reporting a buried point of a page, the device including: the first adding unit is used for adding configuration parameter related information in the software development kit, wherein the configuration parameter related information is used for configuring the mode of reporting the embedded point; the construction unit is used for constructing a hook function provided by the framework according to a preset interface and constructing a buried point reporting program of the page; the second adding unit is used for adding the embedded point reporting program into the software development kit; the embedding unit is used for embedding the software development kit into the page so that the access terminal obtains the page embedded with the software development kit when accessing the page, and performs embedded point reporting operation on the page according to embedded point reporting programs and configuration parameter related information in the software development kit.

In some embodiments of the present application, based on the foregoing solution, the first adding unit is configured to: adding a configuration file address in a software development kit; the embedding unit is configured to: embedding the software development kit into the page, so that an access terminal obtains a configuration file according to the configuration file address in the software development kit after obtaining the page embedded with the software development kit, and performing embedded point reporting operation on the page according to the configuration file and the embedded point reporting program in the software development kit.

In some embodiments of the present application, based on the foregoing scheme, the embedding unit is configured to: acquiring embedded point parameter information matched with the embedded point key from the configuration file according to the embedded point key provided by the embedded point reporting program in the software development kit; and carrying out embedded point reporting operation on the page according to the embedded point parameter information and the embedded point reporting program.

In some embodiments of the present application, based on the foregoing scheme, the building unit is configured to: and mounting a hook function provided by a preset interface construction framework on a designated element in the page, and constructing a first embedded point reporting program for detecting clicking behaviors of the designated element.

In some embodiments of the present application, based on the foregoing scheme, the embedding unit is configured to: acquiring buried point parameter information matched with a buried point key from the configuration file according to the buried point key provided by the first buried point reporting program; acquiring click behavior data of the specified element according to the first embedded point reporting program; and packaging and screening the click behavior data according to the embedded point parameter information to obtain result data, and reporting the result data.

In some embodiments of the present application, based on the foregoing scheme, the building unit is further configured to: and mounting a hook function provided by a preset interface construction framework on a designated element in the page, and constructing a second embedded point reporting program for detecting the exposure behavior of the designated element.

In some embodiments of the present application, based on the foregoing solution, the second embedded point reporting program is configured to determine whether the specified element is in a visible area of the page.

In some embodiments of the present application, based on the foregoing solution, the second embedded point reporting program detects an exposure behavior of the specified element according to a change in at least one of data, a state, and an attribute of the specified element.

In some embodiments of the present application, based on the foregoing scheme, the building unit is further configured to: and constructing a third embedded point reporting program for detecting the browsing behavior of the page according to a hook function provided by a preset interface construction framework.

According to an aspect of the embodiments of the present application, there is provided a computer readable medium having stored thereon a computer program, which when executed by a processor, implements a method for reporting a page buried point as described in the above embodiments.

According to an aspect of an embodiment of the present application, there is provided an electronic device including: one or more processors; and the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to realize the page embedded point reporting method in the embodiment.

In the technical scheme provided by some embodiments of the present application, the embedded point reporting operation of the page can be implemented by only adding the embedded point reporting program and the related information of the configuration parameters to the software development kit and embedding the software development kit into the page, so that the implementation mode is simple; the embedded point reporting program constructed for the page is created based on a hook function provided by a preset interface construction frame, and the code quantity is very small; the whole page embedded point reporting function is realized in a software development kit, and partial codes in the software development kit can be easily migrated to other projects. Therefore, the technical scheme provided by the embodiment of the application can realize unification and multiplexing of codes in a plurality of projects, can obviously reduce the code quantity and development cost of project development, can rapidly realize development of a buried point reporting function aiming at a plurality of buried point demands and even a plurality of projects, and improves the project development efficiency.

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

Drawings

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

FIG. 1 is a schematic diagram showing a principle of collecting behavior data on a page in the related art;

FIG. 2 is a schematic diagram showing another principle of collecting behavior data on pages in the related art;

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

FIG. 4 illustrates a flow chart of a method of page buried point reporting according to an embodiment of the present application;

FIG. 5 illustrates a schematic diagram of a method of page buried point reporting according to one embodiment of the present application;

FIG. 6 shows a flowchart of the details of step 410 and step 440 of FIG. 4 according to one embodiment of the present application;

FIG. 7 shows a schematic diagram of a page capable of providing a profile address according to one embodiment of the present application;

FIG. 8 illustrates a schematic diagram of the interaction of the page of FIG. 7, according to one embodiment of the present application;

FIG. 9 illustrates a schematic diagram of a profile address obtained through the page shown in FIG. 7, according to one embodiment of the present application;

FIG. 10 illustrates a flow chart of a buried point reporting operation on a page according to a configuration file and buried point reporting procedure according to one embodiment of the present application;

FIG. 11 is a detailed schematic diagram of a method for reporting a buried point of a page according to an embodiment of the present application;

FIG. 12 illustrates a schematic diagram of exposure behavior reporting of an element according to one embodiment of the present application;

FIG. 13 shows a block diagram of a page buried point reporting device according to an embodiment of the present application;

fig. 14 shows a schematic diagram of a computer system suitable for use in implementing embodiments of the present application.

Detailed Description

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

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

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

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

At present, pages may also be referred to as web pages, which are one of the most important ways for users to obtain information in the internet age. Along with the development of information technology, competition in the internet industry is increasingly intense, and the user preference and browsing habit are known by acquiring behavior data of a user accessing a page, so that the internet business has become an important work for realizing fine operation and improving user experience.

In the related art, the following two schemes are mainly adopted to collect behavior data of a user on a page:

scheme one: no buried point scheme.

The scheme without buried points is realized by the following steps: and accessing a specific toolkit into the front-end page, so that the toolkit can collect all data of a user and send the data to a back-end server corresponding to the page application program. This will produce a large amount of useless data, which will then be processed by the back-end development engineer to obtain the data intended by the data analysis engineer.

Fig. 1 is a schematic diagram showing a principle of collecting behavior data on a page in the related art. Referring to fig. 1, a schematic diagram illustrates a process for collecting behavioral data using a point-less approach. First, a front-end embedded point SDK (Software Development Kit ) is embedded in a Web page, and the front-end embedded point SDK is responsible for collecting all behavior data of a user on the page. Then, the front-end buried point SDK transmits the raw data collected by it to the server. Next, the backend development engineers process, filter the data in the server. And finally, providing the data required by the data analysis engineer obtained through the processing and screening operation to the data analysis engineer.

Therefore, the scheme without embedded points does not realize data collection through embedded point reporting, and a large amount of back-end manpower is required for sorting the data, so that the cost is high.

Scheme II: and (5) a scheme of reporting the buried point is processed fully manually.

Fig. 2 is a schematic diagram showing another principle of collecting behavior data on a page in the related art, which illustrates a process of collecting behavior data through a scheme two. Referring to fig. 2, the scheme for fully manual processing of reporting the buried point is specifically as follows: firstly, a front-end development engineer manually writes codes of a Web page, the operation behavior of a user on the Web page is detected through the codes to obtain corresponding embedded point data, and then the embedded point data can be automatically processed, for example, if elements in the Web page are subjected to exposure and reporting, the embedded point data is realized by a pure native means of implanting the corresponding codes in the Web page; then, the code in the Web page can trigger the reporting operation of the embedded point data, and the data can be sent to the data analysis engineer, wherein the data is the processed effective data, that is, the code in the Web page is written according to the requirement of the data analysis engineer, the data corresponds to the code in the Web page, and finally the data sent to the data analysis engineer is the data required by the data analysis engineer.

Therefore, the scheme of processing the embedded point report by full manual operation also needs to write a large amount of codes according to the requirements of each page and each embedded point report, and the cost is high.

The two schemes for realizing the behavior data collection need to be developed by a development engineer to process the data and judge whether the collected behavior data meets the reporting condition, for example, the scheme one is manually operated by a back-end development engineer, and the scheme two also needs to be manually compiled by a front-end development engineer for a large amount of codes. The page codes developed in the schemes cannot be used universally and cannot be migrated to other page projects, so that the codes cannot be unified and reused, and a large amount of codes are written according to different projects and embedded point reporting requirements, so that the project development cost is particularly high, and the project development efficiency is greatly reduced.

More importantly, in the whole project development, the collection of behavior data does not belong to the actual service development scope, so that a great deal of manpower is required to solve the requirement of collecting the behavior data, and a solution which is not optimal is really realized.

Therefore, the embodiment of the application firstly provides a method for reporting the embedded point of the page, wherein the method for reporting the embedded point of the page is a scheme for detecting the behavior of a user on the page and obtaining corresponding behavior data. The method can at least overcome the defects of the two schemes to a certain extent, can improve the reusability of codes, obviously reduce the code quantity and the development cost of project development, and can improve the project development efficiency.

Fig. 3 shows a schematic diagram of an exemplary system architecture to which the technical solution of the embodiments of the present application may be applied. As shown in fig. 3, the system architecture 300 may include a computer device 301, a network 302, a server 303, and terminal devices, where the terminal devices may include a notebook 304, a tablet 305, a smart phone 306, and the like, and the computer device 301 and each terminal device may communicate with the server 303 through the network 302. The computer device 301 is used by a user, such as by a front-end development engineer, and an environment for developing Web pages, such as development software, an interface building framework, etc., is deployed on the computer device 301. The server 303 has a web server program deployed thereon. Programs such as a browser capable of accessing Web pages are installed and run on each terminal device. The process of reporting the embedded point of the page by using the system architecture shown in fig. 3 is as follows: first, a user develops a Web page on the computer device 301; then, the user prepares configuration parameter related information in the computer device 301, and writes a buried point reporting program for writing pages using a hook function provided by the interface construction frame; then, establishing an SDK by the user through the configuration parameter related information and the written embedded point reporting program, and embedding the SDK into the Web page; next, the user transmits the Web page embedded with the SDK in the computer device 301 to the server 303 through the network 302; finally, each terminal device may access the server 303 through the network 302 to obtain the Web page embedded with the SDK, and when browsing the Web page, the users of the terminal devices may detect the browsing behavior of the users and report the behavior data, for example, the obtained behavior data may be sent to the server 303. Therefore, the process of reporting the embedded point of the page is realized.

It should be understood that the number of terminal devices, networks, servers, and computer devices in fig. 3 are merely illustrative. There may be any number of terminal devices, networks, servers, and computer devices, as desired for implementation. For example, the server 303 may be a server cluster formed by a plurality of servers.

In some embodiments of the present application, a data embedded platform is further disposed on the server 303, and the user may access the data embedded platform using the computer device 301, and the configuration parameter related information is a configuration file address obtained by the user by accessing the data embedded platform.

In some embodiments of the present application, an SDK embedded in a Web page is able to detect browsing behavior to the Web page, exposure behavior to specified elements in the Web page, and clicking behavior to specified elements in the Web page.

In some embodiments of the present application, when the user reports other Web pages or embedded points of other elements in the Web pages, the user may complete the report by modifying the corresponding code and the relevant information of the configuration parameters in the SDK.

It should be noted that fig. 3 illustrates only one embodiment of the present application. Although in the solution in the embodiment of fig. 3, the Web page embedded with the SDK is sent to the server 303 by the computer device 301 that generates the Web page embedded with the SDK, in other embodiments or specific applications of the present application, the Web page embedded with the SDK may be saved by the terminal device that generates the Web page, and sent to other terminal devices according to access requests of the other terminal devices; although in the solution in the embodiment of fig. 3, the Web page and the SDK are both generated on the computer device 301, in other embodiments of the present application, the Web page and the SDK may be generated on different terminal devices, for example, the Web page may also be stored in advance on a server, and the terminal device that generates the SDK may obtain the Web page from the server; although in the embodiment of the present application, the generating terminal and the browsing terminal of the Web page embedded with the SDK are different terminals, in other embodiments of the present application, both may be the same terminal, for example, a browser may be installed on a computer device, and when a user constructs a Web page embedded with the SDK in the computer device, the user may browse the Web page through the browser on the computer device, so that the function of reporting the embedded point of the page may be tested. The embodiments of the present application should not be limited in any way, nor should the scope of protection of the present application be limited in any way.

It is easy to understand that the method for reporting the embedded point of the page provided in the embodiment of the present application is generally executed by the terminal device, and accordingly, the device for reporting the embedded point of the page is generally disposed in the terminal device. However, in other embodiments of the present application, the server may also have a similar function to the terminal device, so as to execute the scheme for reporting the embedded point of the page provided in the embodiments of the present application.

Therefore, the scheme of the embodiment of the application can be applied to the terminal or the server. The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligent platforms. The terminal may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc. The terminal and the server may be directly or indirectly connected through wired or wireless communication, which is not limited herein.

In some embodiments of the present application, configuration parameter related information for building a software development kit is managed in a blockchain.

Blockchains are novel application modes of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanisms, encryption algorithms, and the like. The Blockchain (Blockchain), which is essentially a decentralised database, is a string of data blocks that are generated by cryptographic means in association, each data block containing a batch of information of network transactions for verifying the validity of the information (anti-counterfeiting) and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.

The blockchain underlying platform may include processing modules for user management, basic services, smart contracts, and operation detection. The user management module is responsible for identity information management of all blockchain participants, including maintenance of public and private key generation (account management), key management, maintenance of corresponding relation between the real identity of the user and the blockchain address (authority management) and the like, and under the condition of authorization, supervision and audit of transaction conditions of certain real identities, and provision of rule configuration (wind control audit) of risk control; the basic service module is deployed on all block chain node devices, is used for verifying the validity of a service request, recording the service request on a storage after the effective request is identified, for a new service request, the basic service firstly analyzes interface adaptation and authenticates the interface adaptation, encrypts service information (identification management) through an identification algorithm, and transmits the encrypted service information to a shared account book (network communication) in a complete and consistent manner, and records and stores the service information; the intelligent contract module is responsible for registering and issuing contracts, triggering contracts and executing contracts, a developer can define contract logic through a certain programming language, issue the contract logic to a blockchain (contract registering), invoke keys or other event triggering execution according to the logic of contract clauses to complete the contract logic, and simultaneously provide a function of registering contract upgrading; the operation detection module is mainly responsible for deployment in the product release process, modification of configuration, contract setting, cloud adaptation and visual output of real-time states in product operation, for example: alarms, detecting network conditions, detecting node device health status, etc.

The platform product service layer provides basic capabilities and implementation frameworks of typical applications, and developers can complete the blockchain implementation of business logic based on the basic capabilities and the characteristics of the superposition business. The application service layer provides the application service based on the block chain scheme to the business participants for use.

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

FIG. 4 illustrates a flow diagram of a method of embedded point reporting that may be performed by any device with communication and data processing capabilities, where a development environment for a front-end page project may be deployed, and where a page building framework may be deployed, according to one embodiment of the present application. The devices can be local computer devices, cloud devices such as cloud servers and cloud server clusters. Referring to fig. 4, the method for reporting the embedded point of the page at least includes the following steps:

in step 410, configuration parameter related information is added to the software development kit, and the configuration parameter related information is used to configure the manner in which the embedded point reporting operation is performed.

Configuration parameter related information can be used to provide configuration parameters. This step corresponds to the creation of a software development kit using configuration parameter related information.

Software development kits are typically a collection of development tools that some software engineers create application software for a particular software package, software framework, hardware platform, operating system, or the like. Software development tools broadly refer to a collection of related documents, examples, and tools that facilitate the development of a certain class of software.

In the embodiment of the application, the software development kit is an SDK for realizing the function of reporting the embedded point of the page.

In step 420, a buried point reporting program of the page is constructed according to the hook function provided by the preset interface construction framework.

The page here is a Web page, which may be an HTML (HyperText Markup Language ) page, for example. The Web page may be constructed prior to constructing the embedded point reporting program for the page. The Web page may include a plurality of elements, the Web page being defined in effect by the elements. In a Web page, the types of elements may be various, such as elements may be forms, buttons, etc., and elements may even be a paragraph.

In one embodiment of the present application, the page is an access page of a game community.

The game community is a forum in which game players communicate with each other, wherein the game players can share game attack, game experience, and the like, and can also feed back the game problems.

In one embodiment of the present application, a buried point reporting program is used to detect access behavior of a user to a specified tile in a game community's access page.

In particular, the gaming community may be a complex community that includes a plurality of game pieces, one for each game, and upon entering each game piece, the user is able to post a post corresponding to that game piece. By detecting the access behaviors of the user to one or more game plates, the game preference of the user can be known, so that game information which can better meet the taste of the user is provided for the user, and the fine operation of a game community is realized.

In one embodiment of the present application, the preset interface building frame is Vue.

Vue (pronunciation/vju:/, similar to view) is a set of progressive frameworks for building user interfaces. Unlike other large frameworks, vue is designed to be applied layer by layer from bottom up.

In one embodiment of the present application, the hook function provided by the preset interface building framework is a hook function provided by the direct instruction of the Vue framework.

Directive instructions are an instruction property in the Vue framework.

The hook function refers to a function that automatically triggers at various times during the life cycle. And a lifecycle refers to a process from mounting on a page to being destroyed.

When the embedded point reporting is realized on one element in the page, the embedded point reporting problem of the element can be solved by only writing a line of codes by only adding a corresponding embedded point reporting instruction in the hook function bound with the element.

The instruction properties in the Vue framework provide a hook function for multiple lifecycles. Aiming at different elements in a page and different embedded point requirements on the elements, embedded point reporting programs can be established by using different hook functions respectively.

For example, the instruction properties in the Vue framework provide the following hook functions:

1. a binding function, which is a lifecycle function in which an element is mounted, which can be triggered when the element is rendered on a page.

2. An updateComponent function, which is an attribute and state update function that is triggered when the data, state, and attributes of an element change.

3. A destroyer function, the destroyer function being a destroy function, the destroyer function being triggered when an element is destroyed from the page.

Of course, the instruction properties in the Vue framework may also provide other hook functions, which may also be used to construct embedded point reporting programs; and, as the Vue frame version is iteratively updated, the hook functions provided by the instruction features will also change, and the names and functions of the hook functions will also change, so that when the embedded point reporting is realized based on the hook functions provided by the instruction features in the Vue frame, different hook functions will be used. In addition, it is not excluded that other frameworks can provide similar functions, so that the solutions of the embodiments of the present application can also be performed.

In step 430, the embedded point reporting program is added to the software development kit.

Step 430 is actually a process of encapsulating the written buried point reporting program into an SDK (software development kit).

In step 440, the software development kit is embedded in the page, so that the access terminal obtains the page in which the software development kit is embedded when accessing the page, and performs embedded point reporting operation on the page according to the embedded point reporting program and the configuration parameter related information in the software development kit.

The access terminal can conduct browsing access operation through a browser deployed on the access terminal. When the access terminal sends an access request and requests to access the page, the page embedded with the software development kit is returned to the access terminal according to the access request. After the browser obtains the page embedded with the software development kit, the user browses the page in the browser, the browser detects the operation behaviors of the user by running the software development kit to obtain corresponding behavior data, and then buried point list-up operation is carried out.

The terminal devices of the access terminal and the page buried point reporting method provided by the embodiment of the application can be the same terminal device or different terminal devices. The access terminal may be any terminal device capable of accessing a page, for example, a smart phone, a desktop computer, a notebook computer, a tablet computer, and the like.

Fig. 5 shows a schematic diagram of a method for reporting a buried point of a page according to an embodiment of the present application. Referring to fig. 5, the principle of the page buried point reporting method is as follows: firstly, a front-end development engineer firstly establishes a web page of a Vue environment; then, according to the elements for reporting the embedded points in the web page, a front-end development engineer writes a corresponding embedded point reporting program by using a hook function provided by a direct instruction of a Vue frame, and the front-end development engineer can also obtain relevant information of configuration parameters; then, the front-end development engineer encapsulates the written embedded point reporting program and the obtained configuration parameter related information to obtain a SlugReport SDK, wherein the SlugReport SDK is a software development kit for realizing the page embedded point reporting function; then, leading the generated SlugReport SDK into a web page of a Vue environment by a front-end development engineer, and collecting buried point data by using a Vue instruction by the SlugReport SDK; then, when the access terminal accesses the web page, the introduced SlugReport SDK in the web page detects the access behavior to obtain corresponding behavior data, and in addition, the SlugReport SDK can also perform processing operations such as filtering and screening on the obtained behavior data to finally obtain effective data; finally, the SlugReport SDK performs buried point data reporting operation and sends effective data to a data development engineer.

In one embodiment of the present application, adding configuration parameter related information in a software development kit includes: adding a configuration parameter interface in a software development kit; embedding the software development kit into the page so that the access terminal obtains the page embedded with the software development kit when accessing the page, and performing embedded point reporting operation on the page according to the embedded point reporting program and the configuration parameter related information in the software development kit, wherein the embedded point reporting operation comprises the following steps: embedding the software development kit into the page so that the access terminal obtains the page embedded with the software development kit when accessing the page, and performing embedded point reporting operation on the page according to an embedded point reporting program and a configuration parameter interface in the software development kit.

In one embodiment of the present application, performing a buried point reporting operation on a page according to a buried point reporting program and a configuration parameter interface in a software development kit includes: obtaining buried point parameter information by calling a configuration parameter interface; and carrying out embedded point reporting operation on the page according to the embedded point reporting program and the embedded point parameter information.

Fig. 6 shows a flowchart of the details of step 410 and step 440 of fig. 4 according to one embodiment of the present application. Referring to fig. 6, the method specifically includes the following steps:

In step 410', a profile address is added to the software development kit.

The profile address is similar to the interface address. The profile address may also be referred to as a profile link or a profile link, and the profile may be obtained by accessing the profile address.

FIG. 7 shows a schematic diagram of a page capable of providing a profile address according to one embodiment of the present application; FIG. 8 illustrates a schematic diagram of the interaction of the page of FIG. 7, according to one embodiment of the present application; FIG. 9 illustrates a schematic diagram of a profile address obtained through the page shown in FIG. 7, according to one embodiment of the present application.

Referring to fig. 7-9, the profile address may be obtained as follows: firstly, the configuration files of all the items are stored in the embedded data platform, the configuration file addresses corresponding to the configuration files can be generated, the names of the items are input in the page shown in fig. 7, the designated items can be queried, and then the operation is performed on the page shown in fig. 7, so that the configuration file addresses of the designated items can be obtained. Next, when the user clicks the "generate configuration" button in the presentation card for a certain item in fig. 7, a window pops up in the page asking the user if an online link is generated, as shown in fig. 8. Finally, when the user clicks the "ok" button in the pop-up window of fig. 8, a corresponding link window is displayed in the page, as shown in fig. 9, in which a "duplicate link" button is set, and when the user clicks the "duplicate link" button, a corresponding project embedded point configuration link may be obtained and copied to the project, for example, may be added to the SDK.

In step 440', the software development kit is embedded in the page, so that the access terminal obtains the configuration file according to the configuration file address in the software development kit after obtaining the page in which the software development kit is embedded, and performs the embedded point reporting operation on the page according to the configuration file and the embedded point reporting program in the software development kit.

In this step, the access terminal may perform the following operations: obtaining a configuration file according to the configuration file address in the software development kit; and carrying out embedded point reporting operation on the page according to the configuration file and the embedded point reporting program in the software development kit.

Metadata information for performing embedded point reporting operation on each element can be included in the configuration file, and a front-end development engineer decides which element in the page is subjected to embedded point reporting operation according to an embedded point reporting program in a software development kit actually written by the element to be detected.

By the embodiments shown in fig. 6-9, the front-end development engineer needs to perform the embedded point reporting operation in what manner, does not need to write corresponding codes, only needs to obtain the corresponding configuration file address from the embedded point data platform and introduce the configuration file address into the SDK, thereby greatly improving the efficiency of implementing the page embedded point reporting.

FIG. 10 illustrates a flow chart of a buried point reporting operation for a page according to a configuration file and buried point reporting program, according to one embodiment of the present application. As shown in fig. 10, the method comprises the following steps:

in step 1010, the embedded point parameter information matched with the embedded point key is obtained from the configuration file according to the embedded point key provided by the embedded point reporting program in the software development kit.

Although in the embodiments of the present application, the embedded point parameter information is obtained from the configuration file, in other embodiments of the present application, the embedded point parameter information may be directly obtained from the configuration file address.

The configuration file and the buried point parameter information located therein may be previously set by the product operator in the buried point data platform shown in fig. 7 to 9.

The buried point key is an identification uniquely corresponding to the buried point, and the buried point key is generally uniquely corresponding to an element in the page, and thus, the buried point key may also be an identification of the element.

The embedded point key is arranged in an embedded point reporting program by a front-end development engineer and is used for acquiring corresponding embedded point parameter information from a configuration file according to the embedded point to be detected.

In step 1020, the embedded point reporting operation is performed on the page according to the embedded point parameter information and the embedded point reporting program.

The embedded point parameter information records the manner of embedded point reporting operation required to be used, the embedded point reporting program contains elements required to report the embedded point, the embedded point reporting operation can be actually carried out, and the embedded point reporting program can also analyze the embedded point parameter information, so that the embedded point reporting operation of the page can be realized based on the embedded point parameter information and the embedded point reporting program.

The types of embedded point reporting operations on elements in a page can be varied.

In one embodiment of the present application, a program for reporting a buried point of a page is constructed according to a hook function provided by a preset interface construction framework, including: and mounting the hook function provided by the preset interface construction frame on the appointed element in the page, and constructing a first embedded point reporting program for detecting the clicking action of the appointed element.

The first embedded point reporting program is established using a hook function that is mounted to the specified element.

For example, the designated element may be a button element, and when the user clicks the button element, the first embedded point reporting program may detect the button element and generate corresponding embedded point data, so that the clicking behavior data of the user on the button element may be collected by using the first embedded point reporting program.

The first embedded point reporting program may be constructed based on the binding function provided by the instruction feature of the Vue framework described above.

In one embodiment of the present application, obtaining, from a configuration file, embedded point parameter information matched with an embedded point key according to the embedded point key provided by an embedded point reporting program in a software development kit, includes: acquiring buried point parameter information matched with a buried point key from a configuration file according to the buried point key provided by the first buried point reporting program; performing embedded point reporting operation on the page according to the embedded point parameter information and the embedded point reporting program, including: acquiring click behavior data of the specified element according to a first embedded point reporting program; and packaging and screening the clicking behavior data according to the embedded point parameter information to obtain result data, and reporting the result data.

In the embodiment of the present application, the click behavior data may include multiple types of data, and the embedded point parameter information in the configuration file indicates a manner of packaging and filtering the click behavior data, such as what format the data is packaged in, what type of data is filtered out, and so on. Of course, in other embodiments of the present application, the embedded point parameter information may also indicate other ways to further process the click behavior data, for example, statistics may be performed on the click behavior data, and so on.

In one embodiment of the present application, a program for reporting a buried point of a page is constructed according to a hook function provided by a preset interface construction framework, including: and mounting the hook function provided by the preset interface construction frame on the appointed element in the page, and constructing a second embedded point reporting program for detecting the exposure behavior of the appointed element.

The element appears in a viewable area of the user's screen, referred to as an exposure.

In one embodiment of the present application, the embedded point parameter information is used to indicate whether the second embedded point reporting program reports the exposure behavior of the specified element.

In this embodiment of the present application, the embedded point parameter information defines a manner of reporting an exposure behavior of an element, specifically, it determines whether to report an exposure behavior of an element, where a data type of the embedded point parameter information may be boolean.

In one embodiment of the present application, the second embedded point reporting program is configured to determine whether the specified element is within the visible area of the page.

The second embedded point reporting program determines whether the specified element is in the visible area of the page according to the position of the specified element relative to the user screen, and the specific process will be described below.

In one embodiment of the present application, the second embedded point reporting program detects exposure behavior to the specified element according to changes in at least one of data, status, and attributes of the specified element.

As described above, the updateComponent function provided by the instruction feature of the Vue frame is triggered when the data, state and attribute of the element change, so that the second embedded point reporting program can be constructed based on the updateComponent function provided by the instruction feature of the Vue frame.

In one embodiment of the present application, a program for reporting a buried point of a page is constructed according to a hook function provided by a preset interface construction framework, including: and constructing a third embedded point reporting program for detecting the browsing behavior of the page according to a hook function provided by a preset interface construction framework.

The third embedded point reporting program can detect whether the user browses the page or not, and even can detect whether the user browses a certain element in the page or not.

The browsing behavior and the exposure behavior reporting may be implemented in a similar manner, and the third embedded point reporting program may also be constructed using an updateComponent function provided by the instruction feature of the Vue framework.

In one embodiment of the present application, the third buried point reporting program determines that the page is browsed according to monitoring the exposure behavior of the element located at the top in the page.

In the embodiment of the application, as long as the element at the top of the page generates the exposure behavior, the browsing behavior of the page is judged to be implemented, and the accuracy of detecting the browsing behavior is improved.

In one embodiment of the present application, the third embedded point reporting program determines that the page is browsed according to monitoring the exposure behavior of the element located at the bottom in the page.

Both embodiments described above enable detection of browsing behaviour of a page by monitoring the exposure behaviour of elements in the page.

In one embodiment of the present application, the third embedded point reporting program determines that the page is browsed according to monitoring that the element at the top and the element at the bottom in the page are both exposed.

In the embodiment of the application, the browsing behavior of the page is determined only if the element positioned at the top and the element positioned at the bottom of the page are exposed, so that the accuracy of embedded point reporting of the page browsing behavior is improved.

Fig. 11 is a detailed schematic diagram of a method for reporting a buried point of a page according to an embodiment of the present application. Next, how the method according to the embodiment of the present application collects click behavior data, browse behavior data, and exposure behavior data of the user will be specifically described with reference to fig. 11.

Referring to fig. 11, a series of actions performed by a user operating a web page can be detected through an SDK embedded in the web page, and corresponding buried point data can be generated. The method comprises the following steps:

1. page browsing reporting

Specifically, when the user opens the web page, the SDK considers that the user browses the web page, and reports and records browsing behavior data of the user browsing the web page.

2. Element click behavior reporting

1. When an element in a web page is rendered, a hook function mounted by the element in the SDK is triggered, and a click event of the element is detected in the hook function.

2. When the clicking event is responded, the user is considered to click the element, and the SDK reads the embedded point parameter information according to the provided embedded point key (key);

3. and packaging and screening the obtained click behavior data according to the embedded point parameter information so as to obtain effective data, and then automatically reporting the effective data to a background database, so that the click behavior data of the user is acquired.

3. Element exposure reporting

1. The reporting of element exposure is relatively complex. Firstly, the SDK judges whether exposure reporting is needed in a hook function of element mounting according to the embedded point parameter information.

2. Then, if the element needs to be exposed, the SDK needs to calculate the position of the element relative to the user screen to determine if the element appears in the viewable area. In this way, exposure behavior data can be acquired.

3. Because the position of the element may change after the data, state and attribute of the element change, the position of the element needs to be recalculated according to the change of the data, state and attribute of the element in the hook function updated by the element, and the data reporting is performed again after the calculation is completed. Thus, the exposure behavior of the element can be dynamically detected in real time.

Specifically, the SDK may obtain the width and height of the visible region according to the DOM object interface in the web standard, and may obtain the coordinates of the element relative to the upper left corner of the visible region and the width and height of the element itself according to the method provided by the DOM (for example, the getbase clientselect () method), so as to calculate whether the element is in the visible region. The DOM (Document Object Model ) here is the programming interface for HTML and XML documents.

As can be seen from fig. 11, the reported key (buried point key) is sent both when the element exposure report and the element click action report are performed, and in practice, the key may be reported when the page browsing report is performed, and the key may indicate what element buried point data is reported when the element click action report is performed.

The page buried point reporting scheme in fig. 11 is performed by a Report instruction, which may be a piece of code of a buried point reporting program located in the SDK. The Report instruction can Report the key, and the Report instruction specifically can include a pageviewerreport (), a clickReport () and a popReport () instruction, where the pageviewerreport () instruction can be used to Report the browsing behavior data of the user browsing the web page, the clickReport () instruction can be used to Report the clicking behavior data of the user on the element in the web page, and the popReport () instruction can be used to Report the exposure behavior data of the element in the web page.

Fig. 12 shows a schematic diagram of exposure behavior reporting of an element according to one embodiment of the present application. Referring to fig. 12, both dom1 and dom2 are elements in the page, where the coordinates of dom1 with respect to the upper left corner of the view area are (100, 50) and the coordinates of dom2 with respect to the upper left corner of the view area are (320, 20), it is apparent that dom1 appears in the view area and dom2 is not in the view area. If the element dom1 is detected to be located in the visible area in the above manner, the element is exposed and reported.

The original front-end development engineer needs to write a large amount of embedded point reporting codes, needs to report the clicking action of the user and the browsing of the page by the user manually, and also needs to calculate whether a module on the page appears in a visible area of the user so as to calculate whether reporting is needed or not, and the like. The above operations are complex, and repeated processing of these actions is required in each project, so that not only is a great deal of repeated work caused, and the cost is high, but also the development efficiency of the project is reduced, and the whole project may be delayed.

By adopting the scheme provided by the embodiment of the application, the problem of embedded point reporting is solved by uniformly using the instruction characteristics provided by the Vue based on the projects of the Vue environment, and all logic codes are extracted from the actual service codes and packaged. The embedded point configuration is only needed to be generated in the embedded point management background, the configuration and the SlugReport SDK are introduced into the project, whether an element is clicked, exposed, browsed and the like can be automatically processed by binding the Vue instruction code on the element to be calculated, the problem of embedded point reporting is really solved by using one line of codes, and in actual project development, service developers do not need to input excessive cost in embedded point reporting, meanwhile, development time is greatly saved, and embedded point demand development becomes simple and rapid.

Compared with the prior buried point development scheme, the prior buried point processing is needed by one element, at least 20 lines of code quantity is needed to be written, and the problem can be solved by only one line of code at present, so that the service development efficiency is substantially improved.

In summary, according to the method for reporting the embedded point of the page provided by the embodiment of the application, the embedded point reporting operation of the page can be realized by only adding the embedded point reporting program and the related information of the configuration parameters into the software development kit and embedding the software development kit into the page, so that the implementation mode is simple; the embedded point reporting program constructed for the page is created based on a hook function provided by a preset interface construction frame, and the code quantity is very small; the whole page embedded point reporting function is realized in a software development kit, and partial codes in the software development kit can be easily migrated to other projects. Therefore, the technical scheme provided by the embodiment of the application can realize unification and multiplexing of codes in a plurality of projects, can obviously reduce the code quantity and development cost of project development, can rapidly realize development of a buried point reporting function aiming at a plurality of buried point demands and even a plurality of projects, and improves the project development efficiency.

The following describes an embodiment of the apparatus of the present application, which may be used to execute the method for reporting the embedded point of the page in the foregoing embodiment of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method for reporting a buried point of a page described in the present application.

FIG. 13 shows a block diagram of a page buried point reporting device according to an embodiment of the present application.

Referring to fig. 13, a device 1300 for reporting a buried point of a page according to an embodiment of the present application includes: a first adding unit 1310, a constructing unit 1320, a second adding unit 1330, and an embedding unit 1340.

The first adding unit 1310 adds configuration parameter related information in a software development kit, where the configuration parameter related information is used to configure a manner of reporting the embedded point; the construction unit 1320 is configured to construct a hook function provided by the framework according to a preset interface, and construct a buried point reporting program of the page; the second adding unit 1330 is configured to add the embedded point reporting program to the software development kit; the embedding unit 1340 is configured to embed the software development kit into the page, so that the access terminal obtains the page in which the software development kit is embedded when accessing the page, and performs embedded point reporting operation on the page according to the embedded point reporting program and the configuration parameter related information in the software development kit.

In some embodiments of the present application, based on the foregoing scheme, the first adding unit 1310 is configured to: adding a configuration file address in a software development kit; the embedding unit 1340 is configured to: embedding the software development kit into the page, so that an access terminal obtains a configuration file according to the configuration file address in the software development kit after obtaining the page embedded with the software development kit, and performing embedded point reporting operation on the page according to the configuration file and the embedded point reporting program in the software development kit.

In some embodiments of the present application, based on the foregoing, embedded unit 1340 is configured to: acquiring embedded point parameter information matched with the embedded point key from the configuration file according to the embedded point key provided by the embedded point reporting program in the software development kit; and carrying out embedded point reporting operation on the page according to the embedded point parameter information and the embedded point reporting program.

In some embodiments of the present application, based on the foregoing scheme, the construction unit 1320 is configured to: and mounting a hook function provided by a preset interface construction framework on a designated element in the page, and constructing a first embedded point reporting program for detecting clicking behaviors of the designated element.

In some embodiments of the present application, based on the foregoing, embedded unit 1340 is configured to: acquiring buried point parameter information matched with a buried point key from the configuration file according to the buried point key provided by the first buried point reporting program; acquiring click behavior data of the specified element according to the first embedded point reporting program; and packaging and screening the click behavior data according to the embedded point parameter information to obtain result data, and reporting the result data.

In some embodiments of the present application, based on the foregoing scheme, the building unit 1320 is further configured to: and mounting a hook function provided by a preset interface construction framework on a designated element in the page, and constructing a second embedded point reporting program for detecting the exposure behavior of the designated element.

In some embodiments of the present application, based on the foregoing scheme, the building unit 1320 is further configured to: and constructing a third embedded point reporting program for detecting the browsing behavior of the page according to a hook function provided by a preset interface construction framework.

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

As shown in fig. 14, the computer system 1400 includes a central processing unit (Central Processing Unit, CPU) 1401, which can perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 1402 or a program loaded from a storage section 1408 into a random access Memory (Random Access Memory, RAM) 1403, for example, performing the methods described in the above embodiments. In the RAM 1403, various programs and data required for system operation are also stored. The CPU 1401, ROM 1402, and RAM 1403 are connected to each other through a bus 1404. An Input/Output (I/O) interface 1405 is also connected to bus 1404.

The following components are connected to the I/O interface 1405: an input section 1406 including a keyboard, a mouse, and the like; an output portion 1407 including a Cathode Ray Tube (CRT), a liquid crystal display (Liquid Crystal Display, LCD), and a speaker; a storage section 1408 including a hard disk or the like; and a communication section 1409 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 1409 performs communication processing via a network such as the internet. The drive 1410 is also connected to the I/O interface 1405 as needed. Removable media 1411, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memory, and the like, is installed as needed on drive 1410 so that a computer program read therefrom is installed as needed into storage portion 1408.

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

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

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

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

As an aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer-readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to implement the methods described in the above embodiments.

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

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

According to the related data collection and processing scheme, the implementation is carried out by obtaining the informed consent or independent consent of the personal information body (or having the legal basis specified by the legal regulations of the related country) strictly according to the requirements of the legal regulations of the related country, and developing the subsequent data use and processing behaviors within the authorized range of the legal regulations and the personal information body.

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

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

Claims

1. A method for reporting a buried point of a page is characterized by comprising the following steps:

adding a configuration file address in a software development kit, wherein the configuration file address is used for configuring a manner of reporting operation of a buried point, the configuration file address is a configuration file address of a specified item obtained by a user through operating on a page provided by a buried point data platform, the configuration file address is generated by the buried point data platform, and configuration files of a plurality of items are stored in the buried point data platform;

Constructing a hook function provided by a frame according to a preset interface, and constructing a buried point reporting program of the page;

adding the embedded point reporting program into the software development kit;

embedding the software development tool package into the page, so that an access terminal obtains a configuration file according to the configuration file address in the software development tool package after obtaining the page embedded with the software development tool package, and performing embedded point reporting operation on the page according to embedded point parameter information in the configuration file and the embedded point reporting program in the software development tool package.

2. The method for reporting a buried point on a page according to claim 1, wherein the performing a buried point reporting operation on the page according to the buried point parameter information in the configuration file and the buried point reporting program in the software development kit includes:

acquiring embedded point parameter information matched with the embedded point key from the configuration file according to the embedded point key provided by the embedded point reporting program in the software development kit;

and carrying out embedded point reporting operation on the page according to the embedded point parameter information and the embedded point reporting program.

3. The method for reporting the embedded point of the page according to claim 2, wherein the constructing the embedded point reporting program of the page according to the hook function provided by the preset interface construction frame includes:

and mounting a hook function provided by a preset interface construction framework on a designated element in the page, and constructing a first embedded point reporting program for detecting clicking behaviors of the designated element.

4. The method for reporting a buried point on a page according to claim 3, wherein the acquiring, from the configuration file, the buried point parameter information matched with the buried point key according to the buried point key provided by the buried point reporting program in the software development kit includes:

acquiring buried point parameter information matched with a buried point key from the configuration file according to the buried point key provided by the first buried point reporting program;

the operation of reporting the buried point of the page according to the buried point parameter information and the buried point reporting program comprises the following steps:

acquiring click behavior data of the specified element according to the first embedded point reporting program;

and packaging and screening the click behavior data according to the embedded point parameter information to obtain result data, and reporting the result data.

5. The method for reporting the embedded point of the page according to claim 2, wherein the constructing the embedded point reporting program of the page according to the hook function provided by the preset interface construction frame includes:

and mounting a hook function provided by a preset interface construction framework on a designated element in the page, and constructing a second embedded point reporting program for detecting the exposure behavior of the designated element.

6. The method of claim 5, wherein the second embedded point reporting program is configured to determine whether the specified element is in a visible area of the page.

7. The method according to claim 5, wherein the second embedded point reporting program detects exposure behavior of the specified element according to a change in at least one of data, status, and attribute of the specified element.

8. The method for reporting the embedded point of the page according to claim 2, wherein the constructing the embedded point reporting program of the page according to the hook function provided by the preset interface construction frame includes:

and constructing a third embedded point reporting program for detecting the browsing behavior of the page according to a hook function provided by a preset interface construction framework.

9. A device for reporting a buried page, the device comprising:

the first adding unit is used for adding a configuration file address in the software development kit, wherein the configuration file address is used for configuring the manner of reporting the embedded point, the configuration file address is a configuration file address of a specified item obtained by a user through operating on a page provided by the embedded point data platform, the configuration file address is generated by the embedded point data platform, and the configuration files of a plurality of items are stored in the embedded point data platform;

the construction unit is used for constructing a hook function provided by the framework according to a preset interface and constructing a buried point reporting program of the page;

the second adding unit is used for adding the embedded point reporting program into the software development kit;

the embedding unit is used for embedding the software development kit into the page, so that the access terminal obtains a configuration file according to the configuration file address in the software development kit after obtaining the page embedded with the software development kit, and performs embedded point reporting operation on the page according to embedded point parameter information in the configuration file and the embedded point reporting program in the software development kit.

10. A computer readable medium on which a computer program is stored, characterized in that the computer program, when executed by a processor, implements the method of reporting a buried page as claimed in any one of claims 1 to 8.

11. 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 implement the method of embedded point reporting as claimed in any one of claims 1 to 8.