CN114546377A - Embedded point processing method and device, electronic equipment and storage medium - Google Patents
Embedded point processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114546377A CN114546377A CN202210016282.9A CN202210016282A CN114546377A CN 114546377 A CN114546377 A CN 114546377A CN 202210016282 A CN202210016282 A CN 202210016282A CN 114546377 A CN114546377 A CN 114546377A
- Authority
- CN
- China
- Prior art keywords
- point
- buried
- event
- embedded
- buried point
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims description 7
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000011161 development Methods 0.000 claims abstract description 38
- 238000012545 processing Methods 0.000 claims abstract description 35
- 230000006870 function Effects 0.000 claims description 37
- 230000004044 response Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 11
- 238000000354 decomposition reaction Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 4
- 230000008878 coupling Effects 0.000 abstract description 3
- 238000010168 coupling process Methods 0.000 abstract description 3
- 238000005859 coupling reaction Methods 0.000 abstract description 3
- 238000000926 separation method Methods 0.000 abstract 1
- 238000012544 monitoring process Methods 0.000 description 29
- 238000010586 diagram Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 6
- 238000009434 installation Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 238000009933 burial Methods 0.000 description 4
- 238000005538 encapsulation Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012549 training Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure relates to a method and a device for processing embedded points, an electronic device and a storage medium. The method comprises the following steps: responding to a buried point request in code development, and acquiring buried point event correlation information; the embedded point event associated information comprises an embedded point event type and a to-be-embedded point page element of a target service; determining a target embedded point event instruction corresponding to the embedded point event type in the embedded point plug-in unit; and binding the page element of the point to be buried with the target buried point event instruction, and generating buried point event information corresponding to the page element of the point to be buried in the buried point plug-in unit. According to the technical scheme provided by the disclosure, the embedded point processing is carried out in a embedded point plug-in mode, so that uniform and convenient embedded point processing can be provided for developers, and development resources are saved; and the separation of the service logic of the automatic embedded point service can be realized, the coupling of the embedded point and the service is effectively avoided, and the maintenance is convenient.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for processing a buried point, an electronic device, and a storage medium.
Background
With the development of the internet, the use of the internet is receiving much attention, and the web page information of the internet is generally collected in a buried manner. In the related technology, when a buried point is developed, a buried point library is usually encapsulated under each page, so that JS (JavaScript) can be directly used for sending the buried point in a service; or detecting whether the element is in the visible range by using means of a rolling event (scroll), JS polling, cross observation interaction Observer and the like, and manually reporting the exposure buried point. But the former can cause the repeated encapsulation of each type of embedded point for many times, the development and maintenance cost is higher, and the exposed embedded points are not supported; the latter causes that multiple exposure needs to be repeated for writing codes, and the reusability, the usability and the expandability of the codes are poor.
Disclosure of Invention
The disclosure provides a buried point processing method and device, an electronic device and a storage medium. The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided a buried point processing method, including:
responding to a buried point request in code development, and acquiring buried point event correlation information; the embedded point event associated information comprises an embedded point event type and a to-be-embedded point page element of a target service;
determining a target embedded point event instruction corresponding to the embedded point event type in the embedded point plug-in unit;
and binding the page element of the point to be buried with the target buried point event instruction, and generating buried point event information corresponding to the page element of the point to be buried in the buried point plug-in.
In one possible implementation, the method further includes:
installing the embedded point plug-in unit, wherein the embedded point plug-in unit comprises at least one embedded point event instruction;
and generating a single instance object of the embedded point based on the at least one embedded point event instruction, wherein the single instance object of the embedded point comprises a plurality of embedded point request triggering modes.
In a possible implementation manner, the multiple embedded point request triggering manners include an embedded point instruction triggering manner, and the acquiring embedded point event related information in response to an embedded point request in code development includes:
in the code development, triggering operation of a buried point instruction is detected, and the buried point request is generated;
and responding to the buried point request, and acquiring the buried point event correlation information.
In a possible implementation manner, the multiple embedded point request triggering manners include an embedded point reference triggering manner, and the acquiring embedded point event association information in response to an embedded point request in code development includes:
in the code development, triggering operation of the reference of the embedded point is detected, and the embedded point request is generated;
and responding to the buried point request, and acquiring the buried point event correlation information.
In a possible implementation manner, the target buried point event instruction is an exposure buried point event instruction, and the buried point event information is exposure buried point event information; the binding processing of the page element to be embedded with the target embedded point event instruction and the generation of the embedded point event information corresponding to the page element to be embedded in the embedded point plug-in include:
initializing an observed object in a first hook function of the buried point plug-in;
inserting the exposure buried point event instruction into the first hook function, and registering an observation event of the page element of the point to be buried;
generating an exposure unbinding event of the exposure buried point event instruction in a second hook function;
and generating the exposure buried point event information corresponding to the page element of the point to be buried based on the observation object, the observation event and the exposure decomposition and binding event.
In a possible implementation manner, the target buried point event instruction is a click buried point event instruction, and the buried point event information is click buried point event information; the binding processing of the page element of the point to be buried and the target buried point event instruction is performed, and the generation of the buried point event information corresponding to the page element of the point to be buried in the buried point plug-in unit includes:
inserting the click buried point event instruction into the first hook function, and registering a click event for the page element to be buried;
generating a click unbinding event of the click buried point event instruction in a second hook function;
and generating the click burying point event information corresponding to the page element to be buried based on the click event and the click unbinding event.
In a possible implementation manner, the buried point event correlation information further includes target buried point reporting manner information, and the method further includes:
responding to the embedded point request, and displaying information of a plurality of embedded point reporting modes in the embedded point plug-in;
and adding the target buried point reporting mode information into the buried point event information based on a selection instruction of the target buried point reporting mode information in the multiple kinds of buried point reporting mode information.
In one possible implementation, the method further includes:
monitoring the operation of a target service page, and calling target embedded point event information corresponding to the target service page in an embedded point plug-in;
and monitoring the target service page based on the target embedded point event information, and reporting the embedded point information.
In one possible implementation manner, the target buried point event information is exposure buried point event information; the exposure buried point event information comprises an observation object and an observation event; the monitoring the target service page based on the target embedded point event information and reporting the embedded point information includes:
determining a first page element corresponding to the observation event;
monitoring the first page element with the observation object;
when it is monitored that the first page element is exposed in the target service page, exposure buried point information is generated;
and reporting the exposure buried point information.
In a possible implementation manner, the target buried point event information is click buried point event information, and the click buried point event information includes a click event; the monitoring the target service page based on the target embedded point event information and reporting the embedded point information includes:
determining a second page element corresponding to the click event;
monitoring the second page element in the target business page;
when it is monitored that the second page element in the target service page is clicked, click embedded point information is generated;
and reporting the click buried point information.
According to a second aspect of embodiments of the present disclosure, there is provided a buried point processing apparatus including:
the acquisition module is configured to execute and respond to a buried point request in code development to acquire buried point event related information; the embedded point event associated information comprises an embedded point event type and a to-be-embedded point page element of a target service;
the target buried point event instruction determining module is configured to execute a target buried point event instruction which is used for determining the type of the buried point event in the buried point plug-in;
and the embedded point event information generating module is configured to perform binding processing on the page element to be embedded and the target embedded point event instruction, and generate embedded point event information corresponding to the page element to be embedded in the embedded point plug-in.
In one possible implementation, the apparatus further includes:
the installation module is configured to execute installation of the buried point plug-in unit, and the buried point plug-in unit comprises at least one buried point event instruction;
and the buried point singleton object generating module is configured to execute the at least one buried point event instruction and generate a buried point singleton object, wherein the buried point singleton object comprises a plurality of buried point request triggering modes.
In a possible implementation manner, the multiple types of embedded point request triggering manners include an embedded point instruction triggering manner, and the obtaining module includes:
the first trigger unit is configured to execute a trigger operation of detecting a buried point instruction in the code development and generate the buried point request;
a first obtaining unit configured to perform obtaining the buried point event related information in response to the buried point request.
In a possible implementation manner, the multiple types of embedded point request triggering manners include an embedded point reference triggering manner, and the obtaining module includes:
the second trigger unit is configured to execute a trigger operation of detecting the reference of the buried point in the code development and generate the buried point request;
a second obtaining unit configured to perform obtaining the buried point event related information in response to the buried point request.
In a possible implementation manner, the target buried point event instruction is an exposure buried point event instruction, and the buried point event information is exposure buried point event information; the buried point event information generation module comprises:
an observation object initialization unit configured to perform initialization of an observation object in a first hook function of the buried point plug-in;
an observation event registering unit, configured to insert the exposure buried point event instruction into the first hook function, and register an observation event of the page element to be buried;
an exposure unbinding unit configured to execute an exposure unbinding event that generates the exposure buried point event instruction in a second hook function;
and the exposure buried point event information generating unit is configured to execute generation of the exposure buried point event information corresponding to the page element to be buried based on the observation object, the observation event and the exposure binding event.
In a possible implementation manner, the target buried point event instruction is a click buried point event instruction, and the buried point event information is click buried point event information; the buried point event information generation module comprises:
the click event registration unit is configured to insert the click buried point event instruction into the first hook function and register a click event for the page element to be buried;
the click unbinding unit is configured to execute a click unbinding event for generating the click buried point event instruction in a second hook function;
and the click buried point event information generating unit is configured to execute the click event and the click unbinding event and generate the click buried point event information corresponding to the page element to be buried.
In a possible implementation manner, the buried point event correlation information further includes target buried point reporting manner information, and the apparatus further includes:
the display module is configured to respond to the embedded point request and display the information of the multiple embedded point reporting modes in the embedded point plug-in;
and the reporting mode adding module is configured to execute a selection instruction based on target buried point reporting mode information in the multiple kinds of buried point reporting mode information, and add the target buried point reporting mode information in the buried point event information.
In one possible implementation, the apparatus further includes:
the monitoring module is configured to monitor the running of a target service page and call target embedded point event information corresponding to the target service page in an embedded point plug-in;
and the buried point information reporting module is configured to monitor the target service page based on the target buried point event information and report the buried point information.
In one possible implementation manner, the target buried point event information is exposure buried point event information; the exposure buried point event information comprises an observation object and an observation event; the buried point information reporting module comprises:
a first page element determination unit configured to perform determination of a first page element corresponding to the observation event;
a first monitoring unit configured to perform monitoring of the first page element with the observation object;
the exposure buried point information generating unit is configured to generate exposure buried point information when the exposure of the first page element in the target service page is monitored;
and the first reporting unit is configured to report the exposure buried point information.
In a possible implementation manner, the target buried point event information is click buried point event information, and the click buried point event information includes a click event; the buried point information reporting module comprises:
the second page element determining unit is configured to execute determining of a second page element corresponding to the click event;
a second monitoring unit configured to perform monitoring on the second page element in the target business page;
the click embedded point information generating unit is configured to execute the step of generating click embedded point information when the second page element in the target service page is monitored to be clicked;
and the second reporting unit is configured to report the click burial point information.
According to a third aspect of the embodiments of the present disclosure, there is provided an electronic apparatus including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the method of any of the first aspects above.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein instructions, when executed by a processor of an electronic device, enable the electronic device to perform the method of any one of the first aspects of the embodiments of the present disclosure.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising computer instructions which, when executed by a processor, cause a computer to perform the method of any one of the first aspects of the embodiments of the present disclosure.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
the embedded point event information is generated through the embedded point plug-in, namely, the embedded point can be realized in a embedded point plug-in mode, so that uniform and convenient embedded point processing is provided for developers, repeated encapsulation and code compiling of the embedded point are avoided, development resources are saved, and different types of embedded points can be compatible; automatic point burying is realized, and the point burying efficiency is improved; the automatic embedded point can be separated from the service logic, so that the coupling of the embedded point and the service is effectively avoided, the maintenance is convenient, and the expansibility of the application scene is good.
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 disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
FIG. 1 is a schematic diagram illustrating an application environment in accordance with an exemplary embodiment.
FIG. 2 is a flow chart illustrating a method of landfill disposal in accordance with an exemplary embodiment.
Fig. 3 is a schematic diagram illustrating generation of buried point event information corresponding to a to-be-buried point page element in a buried point plug-in according to an exemplary embodiment.
Fig. 4 is a flowchart illustrating a method for obtaining information associated with a buried point event in response to a buried point request in code development, according to an example embodiment.
Fig. 5 is a flowchart illustrating a method for obtaining information associated with a buried point event in response to a buried point request in code development, according to an example embodiment.
Fig. 6 is a flowchart illustrating a method for reporting embedded point information in embedded point processing according to an exemplary embodiment.
FIG. 7 is a block diagram illustrating a buried point processing device according to an exemplary embodiment.
FIG. 8 is a block diagram illustrating an electronic device for landfill disposal in accordance with an exemplary embodiment.
FIG. 9 is a block diagram illustrating an electronic device for landfill disposal in accordance with an exemplary embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating an application environment according to an exemplary embodiment, which may include a server 01 and a terminal 02, as shown in fig. 1.
In an optional embodiment, the server 01 may be configured to receive the buried point report information, where the buried point report information may be the buried point report information for the target service association page, and may analyze the buried point report information. The target service association page can be used for displaying related functions of the target service. Specifically, the server 01 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 basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a Network service, cloud communication, a middleware service, a domain name service, a security service, a Content Delivery Network (CDN), a big data and artificial intelligence platform, and the like.
In an optional embodiment, the terminal 02 may be used for the site burying processing, so as to implement the site burying for each service page. Optionally, the site process may be synchronized to the server 01 associated with the target service, so that the server 01 may receive the site report information. The terminal 02 may be a terminal used by a code developer. Specifically, the terminal 02 may include, but is not limited to, a smart phone, a desktop computer, a tablet computer, a notebook computer, a smart speaker, a digital assistant, an Augmented Reality (AR)/Virtual Reality (VR) device, a smart wearable device, and other types of electronic devices. Optionally, the operating system running on the electronic device may include, but is not limited to, an android system, an IOS system, linux, windows, and the like.
In addition, it should be noted that fig. 1 illustrates only one application environment of the method for buried point processing provided by the present disclosure.
In the embodiment of the present specification, the server 01 and the terminal 02 may be directly or indirectly connected by a wired or wireless communication method, and the present application is not limited herein.
It should be noted that the following figures show a possible sequence of steps, and in fact do not limit the order that must be followed. Some steps may be performed in parallel without being dependent on each other. User information (including but not limited to user device information, user personal information, user behavior information, etc.) and data (including but not limited to data for presentation, training, etc.) to which the present disclosure relates are both information and data that are authorized by the user or sufficiently authorized by various parties.
FIG. 2 is a flow chart illustrating a method of landfill disposal in accordance with an exemplary embodiment. As shown in fig. 2, the following steps may be included.
In step S201, in response to a buried point request in code development, acquiring buried point event related information; the embedded point event correlation information comprises an embedded point event type and a to-be-embedded point page element of a target service.
In the embodiment of the present specification, the code development may be in a writing process of a buried point code (in the buried point code development), where a writing environment of the buried point code may be independent of a code writing environment of a target service, that is, the buried point code and a code of the target service may be developed independently. The code developer may trigger the embedded point request through the embedded point request triggering mode, and the embedded point request triggering mode is not limited by the disclosure. In response to the buried point request, the information related to the buried point event may be obtained, for example, the type of the buried point event and the page element to be buried of the target service may be obtained from the buried point request. The type of the buried point event may include, but is not limited to, an exposure event and a click event, where the exposure event may include a page exposure event and a page element exposure event. The to-be-buried point page element may be at least one page associated with the target service or may be at least one page element in the at least one page associated. The page elements may include lists, text, pictures, videos, animations, virtual objects, etc. in the page. The page may be a web page (web page) or may be a page of an application, which is not limited by the present disclosure.
In practical applications, for example, a code developer needs to collect exposure information of a page H (to-be-buried point page element) associated with a target business based on requirements. Based on this, any buried point request triggering manner can be selected to trigger the buried point request. Further, in response to the buried point request, the information related to the buried point event may be obtained, where the type of the buried point event may be a page exposure event, and the page element to be buried point may be a page H related to the target service.
In step S203, a target buried point event command corresponding to the buried point event type in the buried point plug-in is determined.
In practical application, a target buried point event instruction corresponding to the buried point event type in the buried point plug-in unit can be determined. For example, if the buried point event type is a click buried point event, it may be determined that a target buried point event instruction corresponding to the buried point event type in the buried point plug-in is a click buried point event instruction.
In the embodiment of the present disclosure, when the embedded plug-in is used for the first time, the embedded plug-in may be installed and initialized first, for example, in the initialization stage shown in fig. 3, which may correspond to the plug-in installation in the life cycle. For example, a buried point plug-in may be installed, which may include at least one buried point event instruction therein; therefore, the method can generate the buried point singleton object to realize the initialization of the buried point plug-in based on at least one buried point event instruction, and the buried point singleton object can comprise a plurality of buried point request triggering modes. It should be noted that, in order to avoid errors caused by multiple initializations, initialization may be performed once, and after the initial use, initialization is not performed any more, and the first-time buried-point singleton object may be used subsequently.
Alternatively, the buried point plug-in may be pre-packaged, such as SDK (Software Development Kit) packaging of a web page buried point library. The embedded point event instruction and the life cycle information of the embedded point event instruction corresponding to different embedded point event types can be included. The embedded point plug-in unit also comprises hook functions for realizing embedded point event instruction instantiation, information of a plurality of embedded point reporting modes and an exposure event processing flow based on the interaction observer. As an example, each parameter in the buried point event instruction may also add type script information, that is, TS (TypeScript, typewritten JavaScript at Any Scale) type information. Based on the method, in code development, prompt information of type script information can be displayed so as to improve development efficiency and realize compatibility of pages and equipment. As an example, the buried point plug-in may be an Vue plug-in, which may provide responsive reporting of the buried point.
In step S205, the page element to be buried is bound with the target buried event instruction, and buried event information corresponding to the page element to be buried is generated in the buried plug-in.
In this embodiment of the present specification, a to-be-buried point page element and a target buried point event instruction may be bound, and buried point event information corresponding to the to-be-buried point page element is generated in a buried point plug-in. For example, referring to fig. 3, corresponding to different phases (running, reset, destroy) in the lifecycle include instruction insertion, instruction update, and instruction unbinding. The buried point plug-in can generate the buried point event information corresponding to the page element to be buried based on the life cycle information (life cycle) of the buried point event instruction. Taking a click buried point event as an example, the click buried point event instruction can be inserted into a hook function to generate a click event of the page element to be buried, so that the binding between the page element to be buried and the target buried point event instruction is realized. And click buried event information corresponding to the page elements of the points to be buried and in the whole life cycle can be correspondingly generated according to monitoring based on click events, click reporting and unbinding of the click events in the life cycle. Subsequently, based on the click buried point event information, monitoring, reporting and unloading monitoring of page elements to be buried points can be realized. The uninstalling snooping may be triggered when the page element of the to-be-buried point does not exist, which is not limited by the present disclosure.
Optionally, the embedded point plug-in may further include information about a plurality of embedded point reporting modes. Based on this, the method may further comprise: and responding to the buried point request, displaying the information of the multiple buried point reporting modes for code developers to select, and improving the convenience and efficiency of writing the buried point codes. And adding target buried point reporting mode information in the buried point event information based on a selection instruction of the target buried point reporting mode information in the multiple kinds of buried point reporting mode information. Through the display of the multiple buried point reporting mode information and the fact that the buried point event correlation information also comprises the target buried point reporting mode information, buried point reporting can be more flexible and convenient.
The embedded point event information is generated through the embedded point plug-in, namely, the embedded point can be realized in a embedded point plug-in mode, so that uniform and convenient embedded point processing is provided for developers, repeated encapsulation and code compiling of the embedded point are avoided, development resources are saved, and different types of embedded points can be compatible; automatic point burying is realized, and the point burying efficiency is improved; the automatic embedded point can be separated from the service logic, so that the coupling of the embedded point and the service is effectively avoided, the maintenance is convenient, and the expansibility of the application scene is good.
Fig. 4 is a flowchart illustrating a method for obtaining information associated with a buried point event in response to a buried point request in code development, according to an example embodiment. In one possible implementation, the plurality of buried point request triggering manners may include a buried point instruction triggering manner. As shown in fig. 4, the step S201 may include:
in step S401, in code development, a trigger operation of a buried point instruction is detected, and a buried point request is generated;
in step S403, in response to the buried point request, buried point event related information is acquired.
In the embodiment of the present specification, in the buried point instruction triggering manner, the buried point request may be triggered by using the buried point instruction. The buried point instruction may be a preconfigured, unified instruction, for example, may have a preset format. As one example, the buried point instruction may include a click instruction and an exposure instruction. Wherein, the click command can be as follows:
<div v-log-click＝”{action:’log_click’,params:PI:’PI’}><div>；
the 'log _ click' described above may characterize the type of buried point event as a click buried point event. 'PI' may be a to-be-buried point page element. The click instruction is written in the process of detecting code development, the trigger operation of detecting the buried point instruction can be determined, and the buried point request can be generated based on parameters in the buried point instruction. In response to the buried point request, buried point event related information may be obtained from parameters of the buried point instruction. That is, the page element needing to click the buried point can be notified to the buried point plug-in through the click command.
Among them, the exposure instruction may be as follows:
<div v-log-show＝”{action:’log_show’,params:PI:’PI’}><div>；
the 'log _ click' described above may characterize the buried point event type as an exposure buried point event. 'PI' may be a to-be-buried point page element. The exposure instruction is written in the process of detecting code development, the trigger operation of detecting the buried point instruction can be determined, and the buried point request can be generated based on the parameters in the buried point instruction. In response to the buried point request, buried point event related information may be obtained from parameters of the buried point instruction. That is, the page element needing to expose the buried point can be notified to the buried point plug-in through the exposure instruction.
The embedded point instruction is combined with the embedded point plug-in, so that the embedded point of the page element to be embedded is realized, the embedded point and service logic isolation can be realized, the development cost of the embedded point code is saved, and the embedded point processing is more standard and uniform.
Correspondingly, in the buried point instruction triggering mode, if the target buried point event instruction is an exposure buried point event instruction, the step S205 may include:
initializing an observation object in a first hook function of a buried point plug-in;
inserting an exposure buried point event instruction into a first hook function, and registering an observation event of a page element of a point to be buried;
generating an exposure unbinding event of the exposure buried point event instruction in the second hook function;
and generating exposure buried point event information corresponding to the page element of the point to be buried based on the observation object, the observation event and the exposure binding event.
The initialized Observer object can be obtained by initializing the Observer instance based on the IntersectionObserver, that is, initializing the Observer instance to obtain the Observer, so as to monitor the exposure of the page element of the point to be buried in the observation event. Optionally, a snoop exposure function may be declared. Inserting an exposure buried point event instruction into a first hook function, and registering an observation event of a page element of a point to be buried so as to represent the starting of monitoring exposure; and the observation event can comprise a page element to be buried, which needs to be monitored by the buried point. And unloading of the exposure buried point event may be registered, for example an exposure unbundling event of the exposure buried point event instruction may be generated in the second hook function, which may include an exposure unbundling condition. The end of this snoop can then be controlled based on the exposure-unbinding condition. Optionally, the exposure unbinding event may further include an observation object destruction event, so that the observation object may be destroyed when the exposure monitoring is finished.
Optionally, as shown in fig. 3, an exposure data reconfiguration and a responsive exposure switch may be further added, wherein the exposure data reconfiguration may perform deduplication on the monitored exposure data (exposure buried point information); the responsive exposure switch may control the on and off of the responsive exposure function. It should also be noted that the observation event may be re-registered for an updated exposure of a page element. For example, if a list slides to the viewable area, an exposure may be recorded, and if some data in the list changes, then if it is still desired to listen to the exposure of the updated list, the observation event may be re-registered for re-listening to the exposure of the updated list.
Further, exposure buried point event information corresponding to the page element of the point to be buried can be generated based on the observation object, the observation event and the exposure decomposition and binding event. For example, the observation object, the observation event and the exposure binding event may be associated with a page element of the point to be buried, and the exposure buried point event information corresponding to the page element of the point to be buried is generated.
Correspondingly, in the buried point instruction triggering mode, if the target buried point event instruction is a click buried point event instruction, the step S205 may include:
inserting a click buried point event instruction into a first hook function, and registering a click event for a page element to be buried;
generating a click unbinding event of the click buried point event instruction in the second hook function;
and generating click burying point event information corresponding to the page elements to be buried based on the click event and the click unbinding event.
Similar to the exposure buried-point event instruction, the click buried-point event instruction can be inserted into the first hook function to register the click event. And a click unbinding event of the click buried point event instruction can be generated in the second hook function. Therefore, click buried event information corresponding to the to-be-buried page element can be generated based on the click event and the click unbundling event, for example, the click event, the click unbundling event and the to-be-buried page element can be associated to clarify the page element targeted by the click event and the click unbundling event. The click event can include a page element needing click monitoring, and the click unbinding event can include a click unbinding condition for subsequently controlling ending processing of the click monitoring.
The hook function is arranged in the buried point plug-in unit, so that the hook function can be used for carrying out specific buried point processing, and the buried point plug-in unit can flexibly realize exposure buried point processing and point-click buried point processing.
Fig. 5 is a flowchart illustrating a method for obtaining information associated with a buried point event in response to a buried point request in code development, according to an example embodiment. In one possible implementation, the plurality of buried point request triggers include a buried point reference trigger. As shown in fig. 5, the step S201 may include:
in step S501, in code development, a trigger operation for a buried point reference is detected, and a buried point request is generated;
in step S503, in response to the buried point request, buried point event related information is acquired.
In the embodiment of the present specification, in the buried point reference triggering manner, a triggering operation of the buried point reference may be utilized to generate the buried point request. The embedded point reference may refer to an embedded point event instruction in an embedded point plug-in referenced in the embedded point code, so that the embedded point event related information may be transmitted to the embedded point plug-in as a parameter. As an example, the buried point references may be as follows:
page exposure buried point referencing: sendPV ('demo _ pv', { p1: 'p1' });
click buried point reference: SendClick ({ action: 'send _ click', params: { p1: 'p1' });
page element exposure buried point referencing: sendShow ({ action: 'send _ show', params: { p1: 'p1' }).
Wherein, the buried point reference can be sent in accordance with JS (JavaScript). 'demo _ pv', 'send _ click', 'send _ show' can indicate that the type of the buried point event is a page exposure buried point event, a click buried point event, a page element exposure buried point event, respectively. 'p1' may refer to identification information of a to-be-buried point page element.
The embedded point of the page element to be embedded is realized by combining the embedded point reference mode with the embedded point plug-in, and the flexibility of the embedded point is further improved on the basis of saving the embedded point code development cost and more standard and uniform embedded point processing.
Fig. 6 is a flowchart illustrating a method for reporting embedded point information in embedded point processing according to an exemplary embodiment. In one possible implementation, the method may include:
in step S601, the operation of the target service page is monitored, and target embedded point event information corresponding to the target service page in the embedded point plug-in is called.
The target service page can be any page associated with the target service. After the embedding of the target page is carried out, the page related to the target service is monitored. If the operation of the target service page is monitored, target buried point event information corresponding to the target service page in the buried point plug-in can be called, so that buried point monitoring can be conveniently executed based on the target buried point event information. Here, the terminal for operating the target service page may include a terminal used when the user browses the target service page and a terminal for performing embedded processing, and generally, refers to a terminal used when the user browses the target service page.
In step S603, the target service page is monitored based on the target embedded point event information, and embedded point information is reported.
As one example, when the target buried-point event information is exposure buried-point event information, the exposure buried-point event information may include an observation object and an observation event; this step S603 can be realized by:
determining a first page element corresponding to an observation event;
monitoring the first page element by using an observation object;
when it is monitored that the first page element is exposed in the target service page, exposure buried point information is generated;
and reporting exposure buried point information.
The first page element may refer to a page element that needs exposure monitoring and corresponds to the exposure buried point event information. Optionally, reporting mode information may also be obtained, so that the exposure buried point information may be reported based on the reporting mode information.
As another example, when the target buried point event information is click buried point event information, the click buried point event information may include a click event; this step S603 can be realized by:
determining a second page element corresponding to the click event;
monitoring the second page element in the target service page;
when it is monitored that a second page element in the target service page is clicked, click embedded point information is generated;
and reporting click buried point information.
The first page element may be a page element corresponding to the click burial point event information and needing click monitoring. Optionally, reporting mode information may also be acquired, so that click burial point information may be reported based on the reporting mode information.
When a target service page runs, calling target embedded point event information corresponding to the target service page in the embedded point plug-in; and monitoring a target service page based on the target embedded point event information, reporting the embedded point information, and realizing the automatic embedded point reporting based on the embedded point plug-in. And through the division of the exposure buried point event information and the click buried point event information, the exposure and the click can be flexibly monitored, and the buried point reporting efficiency is improved.
FIG. 7 is a block diagram illustrating a buried point processing device according to an exemplary embodiment. Referring to fig. 7, the apparatus may include:
an obtaining module 701 configured to execute, in response to a buried point request in code development, obtaining buried point event related information; the embedded point event associated information comprises an embedded point event type and a to-be-embedded point page element of a target service;
a target buried point event instruction determining module 703 configured to execute a target buried point event instruction that determines a type of the buried point event in a buried point plug-in;
a buried point event information generating module 705, configured to perform binding processing on the to-be-buried point page element and the target buried point event instruction, and generate buried point event information corresponding to the to-be-buried point page element in the buried point plug-in.
In one possible implementation, the apparatus may further include:
the installation module is configured to execute installation of the buried point plug-in unit, and the buried point plug-in unit comprises at least one buried point event instruction;
and the buried point singleton object generating module is configured to execute the at least one buried point event instruction and generate a buried point singleton object, wherein the buried point singleton object comprises a plurality of buried point request triggering modes.
In a possible implementation manner, the multiple embedded point request triggering manners include an embedded point instruction triggering manner, and the obtaining module 701 may include:
the first trigger unit is configured to execute a trigger operation of detecting a buried point instruction in the code development and generate the buried point request;
a first obtaining unit configured to perform obtaining the buried point event related information in response to the buried point request.
In a possible implementation manner, the multiple types of embedded point request triggering manners include an embedded point reference triggering manner, and the obtaining module includes:
the second trigger unit is configured to execute a trigger operation of detecting the reference of the buried point in the code development and generate the buried point request;
a second obtaining unit configured to perform obtaining the buried point event related information in response to the buried point request.
In a possible implementation manner, the target buried point event instruction is an exposure buried point event instruction, and the buried point event information is exposure buried point event information; the buried point event information generating module 705 may include:
an observation object initialization unit configured to perform initialization of an observation object in a first hook function of the buried point plug-in;
an observation event registering unit, configured to insert the exposure buried point event instruction into the first hook function, and register an observation event of the page element to be buried;
an exposure unbinding unit configured to execute an exposure unbinding event that generates the exposure buried point event instruction in a second hooking function;
and the exposure buried point event information generating unit is configured to execute generation of the exposure buried point event information corresponding to the page element to be buried based on the observation object, the observation event and the exposure binding event.
In a possible implementation manner, the target buried point event instruction is a click buried point event instruction, and the buried point event information is click buried point event information; the buried point event information generating module 705 may include:
the click event registration unit is configured to insert the click buried point event instruction into the first hook function and register a click event for the page element to be buried;
the click unbinding unit is configured to execute a click unbinding event for generating the click buried point event instruction in a second hook function;
and the click buried point event information generating unit is configured to execute the click event and the click unbinding event and generate the click buried point event information corresponding to the page element to be buried.
In a possible implementation manner, the buried point event correlation information further includes target buried point reporting manner information, and the apparatus may further include:
the display module is configured to respond to the embedded point request and display the information of a plurality of embedded point reporting modes in the embedded point plug-in;
and the reporting mode adding module is configured to execute a selection instruction based on target buried point reporting mode information in the multiple kinds of buried point reporting mode information and add the target buried point reporting mode information to the buried point event information.
In one possible implementation, the apparatus may further include:
the monitoring module is configured to monitor the running of a target service page and call target embedded point event information corresponding to the target service page in an embedded point plug-in;
and the buried point information reporting module is configured to monitor the target service page based on the target buried point event information and report the buried point information.
In one possible implementation manner, the target buried point event information is exposure buried point event information; the exposure buried point event information comprises an observation object and an observation event; the buried point information reporting module may include:
a first page element determination unit configured to perform determination of a first page element corresponding to the observation event;
a first monitoring unit configured to perform monitoring of the first page element with the observation object;
the exposure buried point information generating unit is configured to generate exposure buried point information when the exposure of the first page element in the target service page is monitored;
and the first reporting unit is configured to report the exposure buried point information.
In a possible implementation manner, the target buried point event information is click buried point event information, and the click buried point event information includes a click event; the buried point information reporting module may further include:
the second page element determining unit is configured to execute determining of a second page element corresponding to the click event;
a second monitoring unit configured to perform monitoring on the second page element in the target business page;
the click embedded point information generating unit is configured to execute the step of generating click embedded point information when the second page element in the target service page is monitored to be clicked;
and the second reporting unit is configured to report the click burial point information.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Fig. 8 is a block diagram illustrating an electronic device for buried point processing, which may be a terminal, according to an exemplary embodiment, and an internal structure thereof may be as shown in fig. 8. The electronic device comprises a processor, a memory, a network interface, a display screen and an input device which are connected through a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the electronic equipment comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the electronic device is used for connecting and communicating with an external terminal through a network. The computer program is executed by a processor to implement a method of buried point processing. The display screen of the electronic equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the electronic equipment, an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 8 is a block diagram of only a portion of the structure associated with the disclosed aspects and does not constitute a limitation on the electronic devices to which the disclosed aspects apply, and that a particular electronic device may include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.
Fig. 9 is a block diagram illustrating an electronic device for landfill disposal, which may be a server, according to an exemplary embodiment, and an internal structure thereof may be as shown in fig. 9. The electronic device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the electronic equipment comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the electronic device is used for connecting and communicating with an external terminal through a network. The computer program is executed by a processor to implement a method of buried point processing.
Those skilled in the art will appreciate that the architecture shown in fig. 9 is merely a block diagram of some of the structures associated with the disclosed aspects and does not constitute a limitation on the electronic devices to which the disclosed aspects apply, as a particular electronic device may include more or less components than those shown, or combine certain components, or have a different arrangement of components.
In an exemplary embodiment, there is also provided an electronic device including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement a buried point processing method as in embodiments of the present disclosure.
In an exemplary embodiment, there is also provided a computer-readable storage medium in which instructions, when executed by a processor of an electronic device, enable the electronic device to perform a buried point processing method in the embodiments of the present disclosure. The computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, a computer program product containing instructions that, when executed on a computer, cause the computer to perform the method of buried point processing in embodiments of the present disclosure is also provided.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by hardware instructions of a computer program, which may be stored in a non-volatile computer-readable storage medium, and when executed, the computer program may include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method of landfill disposal, comprising:
responding to a buried point request in code development, and acquiring buried point event correlation information; the embedded point event associated information comprises an embedded point event type and a to-be-embedded point page element of a target service;
determining a target embedded point event instruction corresponding to the embedded point event type in the embedded point plug-in unit;
and binding the page element of the point to be buried with the target buried point event instruction, and generating buried point event information corresponding to the page element of the point to be buried in the buried point plug-in.
2. The method of claim 1, further comprising:
installing the embedded point plug-in unit, wherein the embedded point plug-in unit comprises at least one embedded point event instruction;
and generating a single instance object of the embedded point based on the at least one embedded point event instruction, wherein the single instance object of the embedded point comprises a plurality of embedded point request triggering modes.
3. The method according to claim 2, wherein the plurality of types of embedded point request triggering manners include an embedded point instruction triggering manner, and the acquiring embedded point event related information in response to the embedded point request in code development includes:
in the code development, triggering operation of a buried point instruction is detected, and the buried point request is generated;
and responding to the buried point request, and acquiring the buried point event correlation information.
4. The method according to claim 2, wherein the plurality of types of embedded point request triggering manners include an embedded point reference triggering manner, and the acquiring embedded point event related information in response to the embedded point request in code development includes:
in the code development, triggering operation of the reference of the embedded point is detected, and the embedded point request is generated;
and responding to the buried point request, and acquiring the buried point event correlation information.
5. The method according to claim 3, wherein the target buried-point event command is an exposure buried-point event command, and the buried-point event information is exposure buried-point event information; the binding processing of the page element of the point to be buried and the target buried point event instruction is performed, and the generation of the buried point event information corresponding to the page element of the point to be buried in the buried point plug-in unit includes:
initializing an observed object in a first hook function of the buried point plug-in;
inserting the exposure buried point event instruction into the first hook function, and registering an observation event of the page element of the point to be buried;
generating an exposure unbinding event of the exposure buried point event instruction in a second hook function;
and generating the exposure buried point event information corresponding to the page element of the point to be buried based on the observation object, the observation event and the exposure decomposition and binding event.
6. The method according to claim 3 or 5, wherein the target buried point event command is a click buried point event command, and the buried point event information is click buried point event information; the binding processing of the page element to be embedded with the target embedded point event instruction and the generation of the embedded point event information corresponding to the page element to be embedded in the embedded point plug-in include:
inserting the click buried point event instruction into the first hook function, and registering a click event for the page element to be buried;
generating a click unbinding event of the click buried point event instruction in a second hook function;
and generating the click burying point event information corresponding to the page element to be buried based on the click event and the click unbinding event.
7. A buried point processing apparatus, comprising:
the acquisition module is configured to execute and respond to a buried point request in code development to acquire buried point event related information; the embedded point event associated information comprises an embedded point event type and a to-be-embedded point page element of a target service;
the target buried point event instruction determining module is configured to execute a target buried point event instruction which is used for determining the type of the buried point event in the buried point plug-in;
and the embedded point event information generating module is configured to perform binding processing on the page element to be embedded and the target embedded point event instruction, and generate embedded point event information corresponding to the page element to be embedded in the embedded point plug-in.
8. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the buried point processing method of any one of claims 1 to 6.
9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of buried point processing of any of claims 1 to 6.
10. A computer program product comprising computer instructions, wherein the computer instructions, when executed by a processor, implement the method of buried point processing of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210016282.9A CN114546377A (en) | 2022-01-07 | 2022-01-07 | Embedded point processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210016282.9A CN114546377A (en) | 2022-01-07 | 2022-01-07 | Embedded point processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114546377A true CN114546377A (en) | 2022-05-27 |
Family
ID=81670426
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210016282.9A Pending CN114546377A (en) | 2022-01-07 | 2022-01-07 | Embedded point processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114546377A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117873887A (en) * | 2024-01-04 | 2024-04-12 | 书行科技(北京)有限公司 | Buried point processing method and device, electronic equipment and storage medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108304176A (en) * | 2017-12-14 | 2018-07-20 | 广东数果科技有限公司 | Point methods are buried in a kind of visualization of cross-platform mobile terminal |
| CN111159600A (en) * | 2019-12-27 | 2020-05-15 | 北京达佳互联信息技术有限公司 | Method and device for reporting information of elements on page, electronic equipment and storage medium |
| CN111435298A (en) * | 2019-01-11 | 2020-07-21 | 北京京东尚科信息技术有限公司 | Point burying method and device, electronic equipment and storage medium |
| CN112162740A (en) * | 2020-09-25 | 2021-01-01 | 北京易观智库网络科技有限公司 | Visual data acquisition method and system based on IOS-SDK |
| CN112256701A (en) * | 2020-10-22 | 2021-01-22 | 广东万唯计算机服务有限公司 | Dynamic buried point data acquisition system and use method thereof |
| CN112306487A (en) * | 2019-08-21 | 2021-02-02 | 北京字节跳动网络技术有限公司 | Buried point data reporting method, device, equipment and storage medium |
| CN112527414A (en) * | 2020-12-23 | 2021-03-19 | 平安普惠企业管理有限公司 | Front-end-based data processing method, device, equipment and storage medium |
| CN113206869A (en) * | 2021-04-13 | 2021-08-03 | 上海哔哩哔哩科技有限公司 | Data acquisition method and device, storage medium and electronic equipment |
| CN113553269A (en) * | 2021-07-27 | 2021-10-26 | 深圳市腾讯网域计算机网络有限公司 | Page buried point reporting method and related device |
| CN113656102A (en) * | 2021-08-17 | 2021-11-16 | 杭州网易云音乐科技有限公司 | Data point burying method and device, storage medium and electronic equipment |
-
2022
- 2022-01-07 CN CN202210016282.9A patent/CN114546377A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108304176A (en) * | 2017-12-14 | 2018-07-20 | 广东数果科技有限公司 | Point methods are buried in a kind of visualization of cross-platform mobile terminal |
| CN111435298A (en) * | 2019-01-11 | 2020-07-21 | 北京京东尚科信息技术有限公司 | Point burying method and device, electronic equipment and storage medium |
| CN112306487A (en) * | 2019-08-21 | 2021-02-02 | 北京字节跳动网络技术有限公司 | Buried point data reporting method, device, equipment and storage medium |
| CN111159600A (en) * | 2019-12-27 | 2020-05-15 | 北京达佳互联信息技术有限公司 | Method and device for reporting information of elements on page, electronic equipment and storage medium |
| CN112162740A (en) * | 2020-09-25 | 2021-01-01 | 北京易观智库网络科技有限公司 | Visual data acquisition method and system based on IOS-SDK |
| CN112256701A (en) * | 2020-10-22 | 2021-01-22 | 广东万唯计算机服务有限公司 | Dynamic buried point data acquisition system and use method thereof |
| CN112527414A (en) * | 2020-12-23 | 2021-03-19 | 平安普惠企业管理有限公司 | Front-end-based data processing method, device, equipment and storage medium |
| CN113206869A (en) * | 2021-04-13 | 2021-08-03 | 上海哔哩哔哩科技有限公司 | Data acquisition method and device, storage medium and electronic equipment |
| CN113553269A (en) * | 2021-07-27 | 2021-10-26 | 深圳市腾讯网域计算机网络有限公司 | Page buried point reporting method and related device |
| CN113656102A (en) * | 2021-08-17 | 2021-11-16 | 杭州网易云音乐科技有限公司 | Data point burying method and device, storage medium and electronic equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117873887A (en) * | 2024-01-04 | 2024-04-12 | 书行科技(北京)有限公司 | Buried point processing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108108205B (en) | Application page surface treatment method and apparatus | |
| CN107783795B (en) | Application program starting method and device, computer equipment and storage medium | |
| CN109901834B (en) | Document page generation method, device, computer equipment and storage medium | |
| CN107391114B (en) | Page visual rendering method and device | |
| CN110297635B (en) | Page display method, device, equipment and storage medium | |
| CN109101425B (en) | Index point burying method and device for dynamic page AB test | |
| CN113055702B (en) | Method, system and client for displaying business components | |
| CN107957941B (en) | Method and device for processing memory leakage of mobile terminal | |
| CN110597595A (en) | Method for providing multi-language information, method for configuring multi-language information, device, equipment and medium | |
| WO2020207232A1 (en) | Sub-application development method, apparatus, computer device, and storage medium | |
| CN110688598A (en) | Service parameter acquisition method and device, computer equipment and storage medium | |
| CN113467855B (en) | Webpage request processing method and device, electronic equipment and storage medium | |
| KR20090024401A (en) | Method and appratus for supplying mashup service | |
| CN103530338A (en) | Frame for carrying out page rendering on calculation equipment and page generation method | |
| CN113420268A (en) | Watermark adding method, device, equipment and storage medium | |
| CN114546377A (en) | Embedded point processing method and device, electronic equipment and storage medium | |
| CN108228266B (en) | Method and device for starting Fragment component between different plug-ins under Android plug-in framework | |
| CN111488286A (en) | Method and device for independently developing Android module | |
| CN111124627A (en) | Method, device, terminal and storage medium for determining application program caller | |
| CN111078215B (en) | Software product application method and device, storage medium and electronic equipment | |
| CN114547523A (en) | Method, device, equipment and storage medium for performing activity navigation in live broadcast room | |
| CN112051952A (en) | Picture dynamic browsing method and device, electronic equipment and readable storage medium | |
| CN109634636B (en) | Application processing method, device, equipment and medium | |
| CN111880775A (en) | Multi-module layered architecture implementation method and device, electronic equipment and storage medium | |
| CN114924782B (en) | Service update processing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |