Method, device, electronic device and storage medium for processing buried points

Abstract

The present disclosure relates to a method, device, electronic device and storage medium for processing buried points. The method includes: in response to a buried point request in code development, obtaining buried point event association information; the buried point event association information includes a buried point event type, and a page element to be buried point of the target business; determining a target buried point event instruction corresponding to the buried point event type in a buried point plug-in; binding the page element to be buried point with the target buried point event instruction, and generating buried point event information corresponding to the page element to be buried point in the buried point plug-in. According to the technical solution provided by the present disclosure, buried point processing is performed by means of a buried point plug-in, which can provide developers with unified and convenient buried point processing and save development resources; and can also realize the separation of automated buried point business logic, effectively avoid the coupling of buried points with business, and facilitate maintenance.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for processing buried points. Background Art

[0002] With the development of the Internet, the use of the Internet has attracted much attention. Generally, web page information on the Internet is collected through tracking. In related technologies, when developing tracking, the tracking library is usually encapsulated once under each page, which is convenient for directly sending tracking with JS (JavaScript) in the business; or using scroll events (scroll), JS polling, Intersection Observer and other means to detect whether the element is in the visible range to manually report exposure tracking. However, the former will cause each type of tracking to be encapsulated multiple times, with high development and maintenance costs, and does not support exposure tracking; the latter will cause multiple exposures to require repeated code writing, and the code reusability, ease of use and scalability are all poor. Summary of the invention

[0003] The present disclosure provides a method, device, electronic device and storage medium for processing buried points. The technical solution of the present disclosure is as follows:

[0004] According to a first aspect of an embodiment of the present disclosure, a method for processing buried points is provided, including:

[0005] In response to a tracking request in code development, obtaining tracking event association information; the tracking event association information includes a tracking event type and a page element to be tracked of a target business;

[0006] Determine a target tracking event instruction corresponding to the tracking event type in the tracking plug-in;

[0007] The page element to be embedded is bound to the target embedding event instruction, and embedding event information corresponding to the page element to be embedded is generated in the embedding plug-in.

[0008] In a possible implementation, the method further includes:

[0009] Install the tracking plug-in, wherein the tracking plug-in includes at least one tracking event instruction;

[0010] Based on the at least one burying point event instruction, a burying point singleton object is generated, and the burying point singleton object includes multiple burying point request triggering methods.

[0011] In a possible implementation, the multiple tracking request triggering modes include a tracking instruction triggering mode, and the step of obtaining tracking event association information in response to a tracking request in code development includes:

[0012] In the code development, a triggering operation of a tracking instruction is detected, and the tracking request is generated;

[0013] In response to the tracking request, the tracking event association information is obtained.

[0014] In a possible implementation, the multiple tracking request triggering modes include a tracking reference triggering mode, and the step of obtaining tracking event association information in response to a tracking request in code development includes:

[0015] In the code development, a triggering operation of a tracking point reference is detected, and the tracking point request is generated;

[0016] In response to the tracking request, the tracking event association information is obtained.

[0017] In a possible implementation, the target embedding event instruction is an exposure embedding event instruction, and the embedding event information is exposure embedding event information; the step of binding the to-be-embedded page element with the target embedding event instruction and generating the embedding event information corresponding to the to-be-embedded page element in the embedding plug-in includes:

[0018] Initialize the observation object in the first hook function of the embedding plug-in;

[0019] Inserting the exposure embedding event instruction into the first hook function, and registering the observation event of the page element to be embedded;

[0020] Generate an exposure unbinding event of the exposure embedding event instruction in the second hook function;

[0021] Based on the observed object, the observed event and the exposure unbinding event, the exposure embedding event information corresponding to the to-be-embedded page element is generated.

[0022] In a possible implementation, the target embedding event instruction is a click embedding event instruction, and the embedding event information is click embedding event information; the binding process of the to-be-embedded page element with the target embedding event instruction and generating the embedding event information corresponding to the to-be-embedded page element in the embedding plug-in includes:

[0023] Insert the click event instruction into the first hook function to register the click event for the page element to be embedded;

[0024] Generate a click unbinding event of the click embedding event instruction in the second hook function;

[0025] Based on the click event and the click unbinding event, the click embedding event information corresponding to the page element to be embedded is generated.

[0026] In a possible implementation, the tracking point event association information further includes target tracking point reporting mode information, and the method further includes:

[0027] In response to the tracking request, display information of multiple tracking reporting modes in the tracking plug-in;

[0028] Based on a selection instruction for target burying point reporting method information among the multiple burying point reporting method information, the target burying point reporting method information is added to the burying point event information.

[0029] In a possible implementation, the method further includes:

[0030] Monitor the operation of the target business page, and call the target tracking event information corresponding to the target business page in the tracking plug-in;

[0031] The target business page is monitored based on the target embedding event information, and the embedding information is reported.

[0032] In a possible implementation, the target embedding event information is exposure embedding event information; the exposure embedding event information includes an observed object and an observed event; and the monitoring of the target business page based on the target embedding event information and reporting of the embedding information include:

[0033] Determining a first page element corresponding to the observed event;

[0034] Using the observation object to monitor the first page element;

[0035] When it is monitored that the first page element is exposed in the target business page, generating exposure point information;

[0036] Report the exposure tracking information.

[0037] In a possible implementation, the target burying point event information is click burying point event information, and the click burying point event information includes a click event; the monitoring of the target business page based on the target burying point event information and reporting of the burying point information include:

[0038] Determine a second page element corresponding to the click event;

[0039] Monitoring the second page element in the target business page;

[0040] When it is detected that the second page element in the target business page is clicked, click point information is generated;

[0041] Report the click point information.

[0042] According to a second aspect of an embodiment of the present disclosure, a buried point processing device is provided, including:

[0043] An acquisition module is configured to execute a response to a tracking request in code development and acquire tracking event association information; the tracking event association information includes a tracking event type and a page element to be tracked of a target business;

[0044] A target burying point event instruction determination module is configured to execute a target burying point event instruction corresponding to the burying point event type in the burying point plug-in;

[0045] The embedding event information generation module is configured to execute the binding process of the page element to be embedded with the target embedding event instruction, and generate the embedding event information corresponding to the page element to be embedded in the embedding plug-in.

[0046] In a possible implementation manner, the device further includes:

[0047] An installation module is configured to execute the installation of the tracking plug-in, wherein the tracking plug-in includes at least one tracking event instruction;

[0048] The tracing point singleton object generation module is configured to execute based on the at least one tracing point event instruction to generate a tracing point singleton object, wherein the tracing point singleton object includes multiple tracing point request triggering methods.

[0049] In a possible implementation, the multiple tracking request triggering modes include a tracking instruction triggering mode, and the acquisition module includes:

[0050] A first trigger unit is configured to execute a trigger operation of detecting a tracking instruction in the code development and generate the tracking request;

[0051] The first acquisition unit is configured to execute in response to the burying point request and acquire the burying point event association information.

[0052] In a possible implementation, the multiple tracking point request triggering modes include a tracking point reference triggering mode, and the acquisition module includes:

[0053] A second trigger unit is configured to execute a trigger operation of detecting a tracking reference in the code development and generate the tracking request;

[0054] The second acquisition unit is configured to execute and respond to the burying point request to acquire the burying point event association information.

[0055] In a possible implementation, the target embedding event instruction is an exposure embedding event instruction, and the embedding event information is exposure embedding event information; and the embedding event information generating module includes:

[0056] An observation object initialization unit is configured to execute initialization of the observation object in the first hook function of the tracking plug-in;

[0057] An observation event registration unit is configured to execute inserting the exposure embedding event instruction into the first hook function to register the observation event of the page element to be embedded;

[0058] An exposure unbinding unit, configured to execute an exposure unbinding event that generates the exposure embedding event instruction in the second hook function;

[0059] The exposure embedding event information generating unit is configured to generate the exposure embedding event information corresponding to the to-be-embedded page element based on the observed object, the observed event and the exposure unbinding event.

[0060] In a possible implementation, the target embedding event instruction is a click embedding event instruction, and the embedding event information is click embedding event information; the embedding event information generating module includes:

[0061] A click event registration unit is configured to execute inserting the click embedding event instruction into the first hook function to register a click event for the page element to be embedded;

[0062] A click unbinding unit is configured to execute a click unbinding event that generates the click embedding event instruction in the second hook function;

[0063] The click-point burying event information generating unit is configured to generate the click-point burying event information corresponding to the page element to be buried based on the click event and the click unbinding event.

[0064] In a possible implementation, the tracking event association information further includes target tracking reporting method information, and the device further includes:

[0065] A display module, configured to respond to the tracking request and display information of multiple tracking reporting modes in the tracking plug-in;

[0066] The reporting method adding module is configured to execute a selection instruction based on the target burying point reporting method information among the multiple burying point reporting method information, and add the target burying point reporting method information to the burying point event information.

[0067] In a possible implementation manner, the device further includes:

[0068] The monitoring module is configured to monitor the operation of the target business page and call the target tracking event information corresponding to the target business page in the tracking plug-in;

[0069] The tracking point information reporting module is configured to monitor the target business page based on the target tracking point event information and report the tracking point information.

[0070] In a possible implementation, the target embedding event information is exposure embedding event information; the exposure embedding event information includes an observed object and an observed event; and the embedding information reporting module includes:

[0071] A first page element determining unit, configured to determine a first page element corresponding to the observed event;

[0072] A first monitoring unit is configured to monitor the first page element using the observation object;

[0073] an exposure embedding point information generating unit, configured to generate exposure embedding point information when monitoring that the first page element is exposed in the target business page;

[0074] The first reporting unit is configured to report the exposure point information.

[0075] In a possible implementation, the target embedding event information is click embedding event information, and the click embedding event information includes a click event; and the embedding information reporting module includes:

[0076] A second page element determining unit, configured to determine a second page element corresponding to the click event;

[0077] A second monitoring unit is configured to monitor the second page element in the target business page;

[0078] A click burying point information generating unit is configured to generate click burying point information when it is detected that the second page element in the target business page is clicked;

[0079] The second reporting unit is configured to execute and report the click-point information.

[0080] According to a third aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement a method as described in any one of the above-mentioned first aspects.

[0081] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute any method described in the first aspect of the embodiment of the present disclosure.

[0082] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, comprising computer instructions, which, when executed by a processor, enable a computer to execute any one of the methods described in the first aspect of an embodiment of the present disclosure.

[0083] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0084] The tracking event information is generated through the tracking plug-in, that is, the tracking can be performed through the tracking plug-in, providing developers with unified and convenient tracking processing, avoiding repeated packaging and code writing of tracking points, saving development resources, and being compatible with different types of tracking points; and realizing automated tracking to improve tracking efficiency; and the automated tracking can be separated from the business logic, effectively avoiding the coupling of tracking points with the business, facilitating maintenance, and having good scalability in application scenarios.

[0085] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0087] Figure 1 It is a schematic diagram of an application environment according to an exemplary embodiment.

[0088] Figure 2 The present invention is a flowchart of a method for processing buried points according to an exemplary embodiment.

[0089] Figure 3 It is a schematic diagram showing a method of generating embedding event information corresponding to a page element to be embedded in a embedding plug-in according to an exemplary embodiment.

[0090] Figure 4 It is a flow chart of a method for obtaining tracking event association information in response to a tracking request in code development according to an exemplary embodiment.

[0091] Figure 5 It is a flow chart of a method for obtaining tracking event association information in response to a tracking request in code development according to an exemplary embodiment.

[0092] Figure 6 It is a flow chart of a method for reporting buried point information in buried point processing according to an exemplary embodiment.

[0093] Figure 7 The figure is a block diagram of a buried point processing device according to an exemplary embodiment.

[0094] Figure 8 The present invention is a block diagram of an electronic device for point embedding processing according to an exemplary embodiment.

[0095] Fig. 9 The present invention is a block diagram of an electronic device for point embedding processing according to an exemplary embodiment. DETAILED DESCRIPTION

[0096] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0097] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0098] See also Figure 1 , Figure 1 is a schematic diagram of an application environment according to an exemplary embodiment. Figure 1 As shown, the application environment may include a server 01 and a terminal 02 .

[0099] In an optional embodiment, server 01 can be used to receive tracking point reporting information, which can be tracking point reporting information for a target business-related page, and can analyze the tracking point reporting information. Among them, the target business-related page can be used to display the relevant functions of the target business. Specifically, server 01 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0100] In an optional embodiment, terminal 02 can be used for point-of-sale processing to implement point-of-sale for each business page. Optionally, the point-of-sale processing can be synchronized to server 01 associated with the target business, so that server 01 can receive point-of-sale reporting information. The terminal 02 can be a terminal used by code developers. Specifically, terminal 02 can include but is not limited to smart phones, desktop computers, tablet computers, laptops, smart speakers, digital assistants, augmented reality (AR) / virtual reality (VR) devices, smart wearable devices and other types of electronic devices. Optionally, the operating system running on the electronic device may include but is not limited to Android system, IOS system, Linux, Windows, etc.

[0101] In addition, it should be noted that Figure 1 What is shown is only one application environment of the buried point processing method provided by the present disclosure.

[0102] In the embodiments of this specification, the server 01 and the terminal 02 may be directly or indirectly connected via wired or wireless communication, and this application does not impose any limitation thereto.

[0103] It should be noted that the following figure shows a possible order of steps, which is not actually limited to this order. Some steps can be executed in parallel without relying on each other. The 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 display, training data, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0104] Figure 2 FIG. 1 is a flow chart of a method for processing buried points according to an exemplary embodiment. Figure 2 As shown, the following steps may be included.

[0105] In step S201, in response to a burying point request in code development, burying point event association information is obtained; the burying point event association information includes a burying point event type and a page element to be burying point of a target business.

[0106] In the embodiments of this specification, code development may refer to the process of writing the buried point code (burying point code development), wherein the writing environment of the buried point code may be independent of the code writing environment of the target business, that is, the buried point code and the code of the target business may be independently developed. The code developer may trigger the buried point request through the buried point request triggering method, and the present disclosure does not limit the buried point request triggering method. In response to the buried point request, buried point event association information may be obtained, for example, the buried point event type and the target business's to-be-buried point page element may be obtained from the buried point request. Among them, the buried point event type may include but is not limited to exposure events and click events, and the exposure events here may include page exposure events and page element exposure events. The to-be-buried point page element may be at least one page associated with the target business, or may be at least one page element in at least one page of the association. The page element may include a list, text, picture, video, animation, virtual object, etc. in the page. The page here may be a web page (web page), or may be a page of an application, and the present disclosure does not limit this.

[0107] In actual applications, for example, code developers need to collect exposure information of page H (the page element to be buried) associated with the target business based on demand. Based on this, any burying request triggering method can be selected to trigger the burying request. Furthermore, in response to the burying request, burying event association information can be obtained, where the burying event type can be a page exposure event, and the page element to be buried can be page H associated with the target business.

[0108] In step S203, a target tracking event instruction corresponding to the tracking event type is determined in the tracking plug-in.

[0109] In actual applications, the target embedding event instruction corresponding to the embedding event type in the embedding plug-in can be determined. For example, if the embedding event type is a click embedding event, the target embedding event instruction corresponding to the embedding event type in the embedding plug-in can be determined to be a click embedding event instruction.

[0110] In the embodiment of this specification, when the tracking plug-in is used for the first time, it can be installed and initialized first, for example Figure 3 The initialization phase shown may correspond to the installation of plug-ins in the life cycle. For example, a tracking plug-in may be installed, and the tracking plug-in may include at least one tracking event instruction; thus, based on at least one tracking event instruction, a tracking singleton object may be generated to implement the initialization of the tracking plug-in, and the tracking singleton object may include a variety of tracking request triggering methods. It should be noted that in order to avoid errors caused by multiple initializations, initialization may be performed here once, and no initialization is performed after the first use, and the tracking singleton object used for the first time may be used subsequently.

[0111] Optionally, the tracking plug-in can be pre-packaged, for example, SDK (Software Development Kit) packaging of the web page tracking library. It may include tracking event instructions corresponding to different tracking event types and life cycle information of tracking event instructions. The tracking plug-in may also include some hook functions for implementing the instantiation of tracking event instructions, information on multiple tracking reporting methods, and an exposure event processing flow based on IntersectionObserver. As an example, each parameter in the tracking event instruction can also add type script information, namely TS (TypeScript, Typed JavaScript at Any Scale) type information. Based on this, in code development, prompt information of type script information can be displayed to improve development efficiency, and compatibility of pages and devices can be achieved. As an example, the tracking plug-in can be a Vue plug-in, so that responsive reporting of tracking can be provided.

[0112] In step S205, the page element to be embedded is bound to the target embedding event instruction, and embedding event information corresponding to the page element to be embedded is generated in the embedding plug-in.

[0113] In the embodiment of this specification, the page element to be embedded can be bound to the target embedding event instruction, and the embedding event information corresponding to the page element to be embedded can be generated in the embedding plug-in. Figure 3 , corresponding to different stages (running, reset, and destruction) in the life cycle include instruction insertion, instruction update, and instruction unbinding. The embedding plug-in can generate embedding event information corresponding to the page element to be embedded based on the life cycle information (life cycle) of the embedding event instruction. Taking the click embedding event as an example, the click embedding event instruction can be inserted into a hook function to generate a click event for the page element to be embedded, thereby realizing the binding of the page element to be embedded with the target embedding event instruction. And according to the monitoring, click reporting, and unbinding of click events based on click events in the life cycle, the corresponding click embedding event information of the page element to be embedded in the entire life cycle can be generated. Subsequently, based on the click embedding event information, the monitoring, reporting, and uninstallation monitoring of the page element to be embedded can be realized. Among them, the uninstallation monitoring can be triggered when the page element to be embedded does not exist, and the present disclosure does not limit this.

[0114] Optionally, the tracking plug-in may also include multiple tracking reporting method information. Based on this, the method may also include: in response to the tracking request, displaying the multiple tracking reporting method information for code developers to choose from, thereby improving the convenience and efficiency of tracking code writing. Based on the selection instruction for the target tracking reporting method information in the multiple tracking reporting method information, the target tracking reporting method information is added to the tracking event information. By displaying multiple tracking reporting method information and including the target tracking reporting method information in the tracking event association information, tracking reporting can be more flexible and convenient.

[0115] The tracking event information is generated through the tracking plug-in, that is, the tracking can be performed through the tracking plug-in, providing developers with unified and convenient tracking processing, avoiding repeated packaging and code writing of tracking points, saving development resources, and being compatible with different types of tracking points; and realizing automated tracking to improve tracking efficiency; and the automated tracking can be separated from the business logic, effectively avoiding the coupling of tracking points with the business, facilitating maintenance, and having good scalability in application scenarios.

[0116] Figure 4 The present invention is a flow chart of a method for obtaining information associated with a tracking event in response to a tracking request in code development according to an exemplary embodiment. In one possible implementation, the multiple tracking request triggering methods may include a tracking instruction triggering method. Figure 4 As shown, the above step S201 may include:

[0117] In step S401, during code development, a triggering operation of a tracking instruction is detected, and a tracking request is generated;

[0118] In step S403, in response to the tracking request, the tracking event association information is obtained.

[0119] In the embodiment of the present specification, in the burying point instruction trigger mode, a burying point request can be triggered by using a burying point instruction. The burying point instruction can be a pre-configured, unified instruction, for example, it can have a preset format. As an example, the burying point instruction can include a click instruction and an exposure instruction. Among them, the click instruction can be as follows:

[0120] <div v-log-click＝”{action:’log_click’,params:pi:’pi’}> ;

[0121] The above-mentioned 'log_click' can characterize the type of embedding event as a click embedding event. params:PI:'PI' can be the page element to be embedded. When it is detected that the click instruction is written during the code development process, it can be determined that the trigger operation of the embedding instruction is detected, and the embedding request can be generated based on the parameters in the embedding instruction. In response to the embedding request, the embedding event association information can be obtained from the parameters of the embedding instruction. In other words, the page element that needs to be clicked can be notified to the embedding plug-in through the click instruction.

[0122] Among them, the exposure instruction can be as follows:

[0123] <div v-log-show＝”{action:’log_show’,params:pi:’pi’}> ;

[0124] The above-mentioned 'log_click' can characterize the type of embedding event as an exposure embedding event. params:PI:'PI' can be the page element to be embedded. When it is detected that the exposure instruction is written during the code development process, it can be determined that the trigger operation of the embedding instruction is detected, and the embedding request can be generated based on the parameters in the embedding instruction. In response to the embedding request, the embedding event association information can be obtained from the parameters of the embedding instruction. In other words, the page elements that need to be exposed and embedded can be notified to the embedding plug-in through the exposure instruction.

[0125] By combining the above-mentioned tracking instructions with the tracking plug-in, tracking of tracking page elements can be implemented, which can isolate tracking from business logic and save the development cost of tracking code, and the tracking processing is more standardized and unified.

[0126] Accordingly, in the tracking point instruction trigger mode, if the target tracking point event instruction is an exposure tracking point event instruction, the above step S205 may include:

[0127] Initialize the observation object in the first hook function of the tracking plug-in;

[0128] Insert the exposure embedding event instruction into the first hook function and register the observation event of the element on the page to be embedded;

[0129] Generate an exposure unbinding event of the exposure embedding event instruction in the second hook function;

[0130] Based on the observed object, observed event and exposure unbinding event, the exposure embedding event information corresponding to the page element to be embedded is generated.

[0131] Among them, the initialization observation object can be obtained by initializing the observer instance based on IntersectionObserver, that is, the Observer is initialized to monitor the exposure of the page element to be buried in the observation event. Optionally, a monitoring exposure function can be declared. Insert the exposure burying event instruction into the first hook function, register the observation event of the page element to be buried, to represent the start of the monitoring exposure; and the observation event can include the page element to be buried that needs to be buried and monitored. And the uninstallation of the exposure burying event can be registered, for example, an exposure unbinding event of the exposure burying event instruction can be generated in the second hook function, and the exposure unbinding event can include an exposure unbinding condition. The end of the monitoring can be controlled based on the exposure unbinding condition later. Optionally, the exposure unbinding event can also include an observation object destruction event, so that the observation object can be destroyed when the exposure monitoring ends.

[0132] Alternatively, if Figure 3 As shown, you can also add exposure data deduplication configuration and responsive exposure switch, where the exposure data deduplication configuration can deduplicate the monitored exposure data (exposure tracking information); the responsive exposure switch can control the opening and closing of the responsive exposure function. It should also be noted that the observation event can be re-registered for the updated exposure of a page element. For example, when a list slides to the visible area, an exposure can be recorded. If a certain data in the list changes, if you still want to monitor the exposure of the updated list, you can re-register the observation event to re-monitor the exposure of the updated list.

[0133] Furthermore, based on the observed object, observed event, and exposure unbinding event, the exposure buried point event information corresponding to the page element to be buried can be generated. For example, the observed object, observed event, and exposure unbinding event can be associated with the page element to be buried, and the exposure buried point event information corresponding to the page element to be buried can be generated.

[0134] Accordingly, in the tracking instruction trigger mode, if the target tracking event instruction is a click tracking event instruction, the above step S205 may include:

[0135] Insert the click event instruction into the first hook function to register the click event for the page element to be embedded;

[0136] Generate a click unbinding event of the click embedding event instruction in the second hook function;

[0137] Based on the click event and the click unbinding event, the click event information corresponding to the element on the page to be embedded is generated.

[0138] Similar to the above-mentioned exposure embedding event instruction, the click embedding event instruction can be inserted into the first hook function to realize the registration of the click event. And the click unbinding event of the click embedding event instruction can be generated in the second hook function. Therefore, the click embedding event information corresponding to the page element to be embedded can be generated based on the click event and the click unbinding event. For example, the click event, the click unbinding event and the page element to be embedded can be associated to clarify the page elements targeted by the click event and the click unbinding event. Among them, the click event can include the page element that needs to be click-monitored, and the click unbinding event can include a click unbinding condition for subsequent control of the end processing of the click monitoring.

[0139] By setting a hook function in the tracking point plug-in, the hook function can be used to perform specific tracking point processing, so that the tracking point plug-in can flexibly implement exposure tracking point processing and click tracking point processing.

[0140] Figure 5 The present invention is a flowchart of a method for obtaining information related to a tracking event in response to a tracking request in code development according to an exemplary embodiment. In one possible implementation, the multiple tracking request triggering methods include a tracking reference triggering method. Figure 5 As shown, the above step S201 may include:

[0141] In step S501, during code development, a triggering operation of a tracking reference is detected, and a tracking request is generated;

[0142] In step S503, in response to the tracking point request, the tracking point event association information is obtained.

[0143] In the embodiment of this specification, in the burying point reference trigger mode, the trigger operation of the burying point reference can be used to generate a burying point request. Among them, the burying point reference can refer to the burying point event instruction in the burying point plug-in in the burying point code, so that the burying point event association information can be passed as a parameter to the burying point plug-in. As an example, the burying point reference can be as follows:

[0144] Page exposure tracking point reference: sendPV('demo_pv',{p1:'p1'});

[0145] Click embed reference: sendClick({action:'send_click',params:{p1:'p1'}});

[0146] Page element exposure tracking point reference: sendShow({action:'send_show',params:{p1:'p1'}}).

[0147] Among them, the embedding reference can be adapted to JS (JavaScript) for sending. 'demo_pv', 'send_click', and 'send_show' can respectively indicate that the embedding event types are page exposure embedding events, click embedding events, and page element exposure embedding events. 'p1' can refer to the identification information of the page element to be embedded.

[0148] By combining the tracking point reference method with the tracking point plug-in, the tracking point of the tracking point page elements can be realized, which further improves the flexibility of the tracking point while saving the cost of tracking point code development and making the tracking point processing more standardized and unified.

[0149] Figure 6 This is a flow chart of a method for reporting buried point information in buried point processing according to an exemplary embodiment. In a possible implementation, it may include:

[0150] In step S601, the operation of the target business page is monitored, and the target tracking event information corresponding to the target business page in the tracking plug-in is called.

[0151] Among them, the target business page can be any page associated with the target business. After performing the above-mentioned tracking of the target page, the page associated with the target business will be monitored. If the operation of the target business page is monitored, the target tracking event information corresponding to the target business page in the tracking plug-in can be called to perform tracking monitoring based on the target tracking event information. The terminal running the target business page here can include the terminal used when the user browses the target business page and the terminal for tracking processing. Usually, it refers to the terminal used when the user browses the target business page.

[0152] In step S603, the target business page is monitored based on the target burying point event information, and the burying point information is reported.

[0153] As an example, when the target embedding event information is exposure embedding event information, the exposure embedding event information may include an observed object and an observed event; step S603 may be implemented by the following steps:

[0154] Determine a first page element corresponding to the observed event;

[0155] Using the observation object to monitor the first page element;

[0156] When it is detected that the first page element is exposed in the target business page, exposure tracking point information is generated;

[0157] Report exposure point information.

[0158] The first page element may refer to a page element corresponding to the exposure embedding event information and requiring exposure monitoring. Optionally, reporting method information may also be obtained, so that the exposure embedding information may be reported based on the reporting method information.

[0159] As another example, when the target embedding event information is click embedding event information, the click embedding event information may include a click event; step S603 may be implemented by the following steps:

[0160] Determine the second page element corresponding to the click event;

[0161] Monitoring the second page element in the target business page;

[0162] When it is detected that the second page element in the target business page is clicked, click tracking information is generated;

[0163] Report click point information.

[0164] The first page element may refer to a page element corresponding to the click embedding event information and requiring click monitoring. Optionally, reporting method information may also be obtained, so that the click embedding information may be reported based on the reporting method information.

[0165] When the target business page is running, the target tracking event information corresponding to the target business page in the tracking plug-in is called; the target business page is monitored based on the target tracking event information, and the tracking information is reported to realize automatic tracking reporting based on the tracking plug-in. In addition, by dividing the exposure tracking event information and the click tracking event information, the exposure and click can be monitored flexibly to improve the tracking reporting efficiency.

[0166] Figure 7 FIG. 1 is a block diagram of a buried point processing device according to an exemplary embodiment. Figure 7 , the device may include:

[0167] The acquisition module 701 is configured to execute in response to the tracking request in the code development, and obtain tracking event association information; the tracking event association information includes the tracking event type and the target business's tracking page element;

[0168] The target burying event instruction determination module 703 is configured to execute and determine the target burying event instruction corresponding to the burying event type in the burying plug-in;

[0169] The embedding event information generating module 705 is configured to execute binding processing between the page element to be embedded and the target embedding event instruction, and generate embedding event information corresponding to the page element to be embedded in the embedding plug-in.

[0170] In a possible implementation, the device may further include:

[0171] An installation module is configured to execute the installation of the tracking plug-in, wherein the tracking plug-in includes at least one tracking event instruction;

[0172] The tracing point singleton object generation module is configured to execute based on the at least one tracing point event instruction to generate a tracing point singleton object, wherein the tracing point singleton object includes multiple tracing point request triggering methods.

[0173] In a possible implementation, the multiple tracking request triggering modes include a tracking instruction triggering mode, and the acquisition module 701 may include:

[0174] A first trigger unit is configured to execute a trigger operation of detecting a tracking instruction in the code development and generate the tracking request;

[0175] The first acquisition unit is configured to execute in response to the burying point request and acquire the burying point event association information.

[0176] In a possible implementation, the multiple tracking point request triggering modes include a tracking point reference triggering mode, and the acquisition module includes:

[0177] A second trigger unit is configured to execute a trigger operation of detecting a tracking reference in the code development and generate the tracking request;

[0178] The second acquisition unit is configured to execute and respond to the burying point request to acquire the burying point event association information.

[0179] In a possible implementation, the target embedding event instruction is an exposure embedding event instruction, and the embedding event information is exposure embedding event information; the embedding event information generating module 705 may include:

[0180] An observation object initialization unit is configured to execute initialization of the observation object in the first hook function of the tracking plug-in;

[0181] An observation event registration unit is configured to execute inserting the exposure embedding event instruction into the first hook function to register the observation event of the page element to be embedded;

[0182] An exposure unbinding unit, configured to execute an exposure unbinding event that generates the exposure embedding event instruction in the second hook function;

[0183] The exposure embedding event information generating unit is configured to generate the exposure embedding event information corresponding to the to-be-embedded page element based on the observed object, the observed event and the exposure unbinding event.

[0184] In a possible implementation, the target embedding event instruction is a click embedding event instruction, and the embedding event information is click embedding event information; the embedding event information generating module 705 may include:

[0185] A click event registration unit is configured to execute inserting the click embedding event instruction into the first hook function to register a click event for the page element to be embedded;

[0186] A click unbinding unit is configured to execute a click unbinding event that generates the click embedding event instruction in the second hook function;

[0187] The click-point burying event information generating unit is configured to generate the click-point burying event information corresponding to the page element to be buried based on the click event and the click unbinding event.

[0188] In a possible implementation, the tracking event association information further includes target tracking reporting method information, and the device may further include:

[0189] A display module is configured to respond to the tracking request and display information of multiple tracking reporting modes in the tracking plug-in;

[0190] The reporting method adding module is configured to execute a selection instruction based on the target burying point reporting method information among the multiple burying point reporting method information, and add the target burying point reporting method information to the burying point event information.

[0191] In a possible implementation manner, the device may further include:

[0192] The monitoring module is configured to monitor the operation of the target business page and call the target tracking event information corresponding to the target business page in the tracking plug-in;

[0193] The tracking point information reporting module is configured to monitor the target business page based on the target tracking point event information and report the tracking point information.

[0194] In a possible implementation, the target embedding event information is exposure embedding event information; the exposure embedding event information includes an observed object and an observed event; and the embedding information reporting module may include:

[0195] A first page element determining unit, configured to determine a first page element corresponding to the observed event;

[0196] A first monitoring unit is configured to monitor the first page element using the observation object;

[0197] an exposure embedding point information generating unit, configured to generate exposure embedding point information when monitoring that the first page element is exposed in the target business page;

[0198] The first reporting unit is configured to report the exposure point information.

[0199] In a possible implementation, the target burying point event information is click burying point event information, and the click burying point event information includes a click event; the burying point information reporting module may further include:

[0200] A second page element determining unit, configured to determine a second page element corresponding to the click event;

[0201] A second monitoring unit is configured to monitor the second page element in the target business page;

[0202] A click burying point information generating unit is configured to generate click burying point information when it is detected that the second page element in the target business page is clicked;

[0203] The second reporting unit is configured to execute and report the click-point information.

[0204] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0205] Figure 8 is a block diagram of an electronic device for point-of-use processing according to an exemplary embodiment. The electronic device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 8 As shown. The electronic device includes a processor, a memory, a network interface, a display screen and an input device connected via a system bus. Among them, the processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile 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 the operating system and the computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for buried point processing is implemented. The display screen of the electronic device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the housing of the electronic device, or an external keyboard, touchpad or mouse, etc.

[0206] Those skilled in the art will understand that Figure 8 The structure shown in the figure is merely a block diagram of a partial structure related to the scheme of the present disclosure, and does not constitute a limitation on the electronic device to which the scheme of the present disclosure is applied. The specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0207] Fig. 9 is a block diagram of an electronic device for point-of-use processing according to an exemplary embodiment. The electronic device may be a server, and its internal structure diagram may be as shown in FIG. Fig. 9 As shown. The electronic device includes a processor, a memory and a network interface connected via a system bus. Among them, the processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile 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 the operating system and the computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for buried point processing is implemented.

[0208] Those skilled in the art will understand that Fig. 9 The structure shown in the figure is merely a block diagram of a partial structure related to the scheme of the present disclosure, and does not constitute a limitation on the electronic device to which the scheme of the present disclosure is applied. The specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0209] In an exemplary embodiment, an electronic device is also provided, including: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the buried point processing method as in the embodiment of the present disclosure.

[0210] In an exemplary embodiment, a computer-readable storage medium is also provided, and when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the method for processing buried points in the embodiment 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.

[0211] In an exemplary embodiment, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute the method for burying point processing in the embodiment of the present disclosure.

[0212] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0213] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0214] It should be understood that the present disclosure is not limited to the exact structures that have been 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

1. A method for processing buried points, characterized in that: include: Install a tracking plug-in; the tracking plug-in includes at least one tracking event instruction and life cycle information of the tracking event instruction; the life cycle information includes instruction insertion, instruction update and instruction unbinding; Based on the at least one burying event instruction, a burying singleton object is generated; the burying singleton object includes multiple burying request triggering modes; the multiple burying request triggering modes include a burying instruction triggering mode and a burying reference triggering mode; In response to any of the triggering methods of the tracking request in code development, generating a tracking request; Based on the tracking request, obtain tracking event association information; the tracking event association information includes tracking event type, target service to be tracked page elements and multiple tracking reporting method information; Determine a target tracking event instruction corresponding to the tracking event type in the tracking plug-in; Binding the page element to be embedded with the target embedding event instruction, and generating embedding event information corresponding to the page element to be embedded in the embedding plug-in based on the life cycle information; Based on the embedding event information, monitor, report or uninstall the embedding page element; The method further comprises: In response to the tracking request, display the multiple tracking reporting mode information in the tracking plug-in; Based on a selection instruction for target burying point reporting method information among the multiple burying point reporting method information, the target burying point reporting method information is added to the burying point event information.

2. The method according to claim 1, characterized in that The target embedding event instruction is an exposure embedding event instruction, and the embedding event information is exposure embedding event information; the binding process of the to-be-embedded page element and the target embedding event instruction, and generating embedding event information corresponding to the to-be-embedded page element in the embedding plug-in based on the life cycle information, includes: Initialize the observation object in the first hook function of the embedding plug-in; Inserting the exposure embedding event instruction into the first hook function, and registering the observation event of the page element to be embedded; Generate an exposure unbinding event of the exposure embedding event instruction in the second hook function; Based on the observed object, the observed event and the exposure unbinding event, the exposure embedding event information corresponding to the to-be-embedded page element is generated.

3. The method according to claim 1, characterized in that The target embedding event instruction is a click embedding event instruction, and the embedding event information is click embedding event information; the binding process of the to-be-embedded page element and the target embedding event instruction, and the generation of embedding event information corresponding to the to-be-embedded page element in the embedding plug-in based on the life cycle information, includes: Insert the click event instruction into the first hook function to register the click event for the page element to be embedded; Generate a click unbinding event of the click embedding event instruction in the second hook function; Based on the click event and the click unbinding event, the click embedding event information corresponding to the page element to be embedded is generated.

4. The method according to claim 1, characterized in that: The method further comprises: Monitor the operation of the target business page, and call the target tracking event information corresponding to the target business page in the tracking plug-in; The target business page is monitored based on the target embedding event information, and the embedding information is reported.

5. The method according to claim 4, characterized in that The target buried point event information is the exposure buried point event information; the exposure buried point event information includes the observed object and the observed event; The monitoring of the target business page based on the target tracking event information and reporting of the tracking information includes: Determining a first page element corresponding to the observed event; Using the observation object to monitor the first page element; When it is monitored that the first page element is exposed in the target business page, generating exposure point information; Report the exposure tracking information.

6. The method according to claim 4, characterized in that The target burying point event information is click burying point event information, and the click burying point event information includes a click event; the monitoring of the target business page based on the target burying point event information and reporting of the burying point information include: Determine a second page element corresponding to the click event; Monitoring the second page element in the target business page; When it is detected that the second page element in the target business page is clicked, click point information is generated; Report the click point information.

7. A buried point processing device, characterized in that: include: An installation module is configured to execute the installation of a tracking plug-in; the tracking plug-in includes at least one tracking event instruction and life cycle information of the tracking event instruction; the life cycle information includes instruction insertion, instruction update, and instruction unbinding; A burying point singleton object generation module is configured to execute based on the at least one burying point event instruction to generate a burying point singleton object; the burying point singleton object includes multiple burying point request triggering modes; the multiple burying point request triggering modes include a burying point instruction triggering mode and a burying point reference triggering mode; An acquisition module is configured to generate a tracking request in response to any of the tracking request triggering modes in code development; Based on the tracking request, obtain tracking event association information; the tracking event association information includes tracking event type, target service to be tracked page elements and multiple tracking reporting method information; A target burying point event instruction determination module is configured to execute and determine a target burying point event instruction corresponding to the burying point event type in the burying point plug-in; A burying point event information generating module is configured to execute a binding process of the page element to be buried with the target burying point event instruction, and generate burying point event information corresponding to the page element to be buried based on the life cycle information in the burying point plug-in; Based on the embedding event information, monitor, report or uninstall the embedding page element; The device also includes: A display module, configured to execute, in response to the tracking request, displaying the multiple tracking reporting mode information in the tracking plug-in; The reporting method adding module is configured to execute a selection instruction based on the target burying point reporting method information among the multiple burying point reporting method information, and add the target burying point reporting method information to the burying point event information.

8. The device according to claim 7, characterized in that The target embedding event instruction is an exposure embedding event instruction, and the embedding event information is exposure embedding event information; the embedding event information generating module includes: An observation object initialization unit is configured to execute initialization of the observation object in the first hook function of the tracking plug-in; An observation event registration unit is configured to execute inserting the exposure embedding event instruction into the first hook function to register the observation event of the page element to be embedded; An exposure unbinding unit, configured to execute an exposure unbinding event that generates the exposure embedding event instruction in the second hook function; The exposure embedding event information generating unit is configured to generate the exposure embedding event information corresponding to the to-be-embedded page element based on the observed object, the observed event and the exposure unbinding event.

9. The device according to claim 7, characterized in that The target embedding event instruction is a click embedding event instruction, and the embedding event information is a click embedding event information; The embedding event information generation module includes: A click event registration unit is configured to execute inserting the click embedding event instruction into the first hook function to register a click event for the page element to be embedded; A click unbinding unit is configured to execute a click unbinding event that generates the click embedding event instruction in the second hook function; The click-point burying event information generating unit is configured to generate the click-point burying event information corresponding to the page element to be buried based on the click event and the click unbinding event.

10. The device according to claim 7, characterized in that The device also includes: The monitoring module is configured to monitor the operation of the target business page and call the target tracking event information corresponding to the target business page in the tracking plug-in; The tracking point information reporting module is configured to monitor the target business page based on the target tracking point event information and report the tracking point information.

11. The device according to claim 10, characterized in that The target buried point event information is the exposure buried point event information; the exposure buried point event information includes the observed object and the observed event; The tracking point information reporting module includes: A first page element determining unit, configured to determine a first page element corresponding to the observed event; A first monitoring unit is configured to monitor the first page element using the observation object; an exposure embedding point information generating unit, configured to generate exposure embedding point information when monitoring that the first page element is exposed in the target business page; The first reporting unit is configured to report the exposure point information.

12. The device according to claim 10, characterized in that The target embedding event information is click embedding event information, and the click embedding event information includes a click event; The tracking point information reporting module includes: A second page element determining unit, configured to determine a second page element corresponding to the click event; A second monitoring unit is configured to monitor the second page element in the target business page; A click burying point information generating unit is configured to generate click burying point information when it is detected that the second page element in the target business page is clicked; The second reporting unit is configured to execute and report the click-point information.

13. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; Wherein, the processor is configured to execute the instructions to implement the buried point processing method as described in any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the buried point processing method as described in any one of claims 1 to 6.

15. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by the processor, the buried point processing method described in any one of claims 1 to 6 is implemented.

Images