Method, device, medium and electronic equipment for querying buried point information

CN116303612BActive Publication Date: 2026-10-20BEIJING YOUZHUJU NETWORK TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202310289497.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-03-22
Publication Date
2026-10-20
Estimated Expiration
2043-03-22

AI Technical Summary

Technical Problem

或者预先建立有各页面元素标识与查询条件(即埋点参数)之间的对应关系表,通过查询该对应关系表来获取查询条件,但需要查询者预先知道所查询元素的标识,并且,对应关系表的维护成本高

Benefits of technology

[0017]在上述技术方案中,用户通过对目标页面中的目标埋点元素进行操作,即可自动获取埋点查询条件,并基于该埋点条件从埋点平台获取目标元素的埋点信息,并将埋点信息进行可视化展现。这样,当用户需要查询目标页面中任一埋点元素的埋点信息时,通过对相应埋点元素进行可视化操作即可获取到埋点信息,获取埋点信息的方式更加便捷、直观,提高了埋点信息的查询效率。另外,通过本公开提供的埋点信息查询方法,即使是非技术人员也能够轻松地进行埋点信息查询,而无需记忆页面元素的埋点参数或页面元素标识,也无需预先建立页面元素标识与查询条件(即埋点参数)之间的对应关系表,避免了对应关系表的维护工作。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116303612B_ABST
    Figure CN116303612B_ABST
Patent Text Reader

Abstract

The present disclosure relates to a method and device for querying buried point information, a medium and an electronic device. The method comprises: in response to receiving an operation instruction for a target buried point element in a target page, determining a buried point query condition according to the operation instruction; sending a first query request to a buried point platform, wherein the first query request comprises the buried point query condition; in response to receiving a first response message of the buried point platform for the first query request, displaying the buried point information of the target buried point element according to the first response message. In this way, the buried point information can be obtained by visualizing the buried point element, and the way of obtaining the buried point information is more convenient and intuitive, improving the efficiency of querying the buried point information. In addition, even non-technical personnel can easily query the buried point information without needing to remember the buried point parameters or page element identifiers of the page elements, or needing to pre-establish a corresponding relationship table between the page element identifiers and the query conditions, avoiding the maintenance work of the corresponding relationship table.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically, to a method, apparatus, medium, and electronic device for querying embedded information. Background Technology

[0002] With the development of computer network technology, it is often necessary to set up tracking points in web pages or applications to collect information to track application usage or web page status in order to further optimize the product. The collected information may include, for example, the number of visits, the number of visitors, and the duration of stay.

[0003] Currently, when querying event tracking information, the queryer typically needs to know the parameters of the event tracking corresponding to the element being queried in advance. For example, to view the number of clicks on a "OK" button in module B of page A, the filtering conditions on the event tracking platform need to be set to precise conditions such as: "Page = A, Module = B, Element Name = OK, Element Type = Button". Alternatively, a mapping table between the identifiers of each page element and the query conditions (i.e., event tracking parameters) can be pre-established, and the query conditions can be obtained by querying this mapping table. However, this requires the queryer to know the identifier of the element being queried in advance, and the maintenance cost of the mapping table is high. Summary of the Invention

[0004] This summary section is provided to briefly introduce the concepts, which will be described in detail in the subsequent detailed description section. This summary section is not intended to identify key or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] Firstly, this disclosure provides a method for querying embedded data points, including:

[0006] In response to receiving an operation instruction for a target event tracking element on a target page, determine the event tracking query conditions based on the operation instruction;

[0007] Send a first query request to the event tracking platform to obtain event tracking information of the target event tracking element, wherein the first query request includes the event tracking query conditions;

[0008] In response to receiving a first response message from the event tracking platform for the first query request, the event tracking information of the target event tracking element is displayed according to the first response message, wherein the first response message includes the event tracking information or the identification information of the event tracking information.

[0009] Secondly, this disclosure provides a device for querying embedded information, comprising:

[0010] The first determining module is used to respond to receiving an operation instruction for a target tracking element in the target page, and determine the tracking query conditions according to the operation instruction;

[0011] The sending module is used to send a first query request to the tracking platform to obtain the tracking information of the target tracking element, wherein the first query request includes the tracking query conditions.

[0012] The display module is used to respond to a first response message received from the tracking platform for the first query request, and to display the tracking information of the target tracking element according to the first response message, wherein the first response message includes the tracking information or the identification information of the tracking information.

[0013] Thirdly, this disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processing device, implements the steps of the embedded information query method provided in the first aspect of this disclosure.

[0014] Fourthly, this disclosure provides an electronic device, comprising:

[0015] A storage device on which computer programs are stored;

[0016] A processing device is configured to execute the computer program in the storage device to implement the steps of the embedded information query method provided in the first aspect of this disclosure.

[0017] In the above technical solution, users can automatically obtain tracking query conditions by operating on the target tracking elements on the target page, and retrieve the tracking information of the target elements from the tracking platform based on these conditions, then visualize the tracking information. In this way, when a user needs to query the tracking information of any tracking element on the target page, they can obtain the tracking information simply by visually operating on the corresponding tracking element. This makes obtaining tracking information more convenient and intuitive, improving the efficiency of tracking information retrieval. Furthermore, the tracking information query method provided in this disclosure allows even non-technical personnel to easily query tracking information without needing to memorize the tracking parameters or page element identifiers of page elements, or to pre-establish a correspondence table between page element identifiers and query conditions (i.e., tracking parameters), thus avoiding the maintenance work of the correspondence table.

[0018] Other features and advantages of this disclosure will be described in detail in the following detailed description section. Attached Figure Description

[0019] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale. In the drawings:

[0020] Figure 1 This is a flowchart illustrating a method for querying embedded information according to an exemplary embodiment.

[0021] Figure 2 This is a flowchart illustrating a method for querying embedded information according to another exemplary embodiment.

[0022] Figure 3 This is a schematic diagram illustrating a floating layer according to an exemplary embodiment.

[0023] Figure 4 This is a schematic diagram of a page displaying embedded information according to an exemplary embodiment.

[0024] Figure 5 This is a schematic diagram illustrating the addition of multiple target event types according to an exemplary embodiment.

[0025] Figure 6 This is a schematic diagram of a page displaying embedded information according to another exemplary embodiment.

[0026] Figure 7 This is a schematic diagram illustrating a toolbar on a target page according to an exemplary embodiment.

[0027] Figure 8 This is a block diagram illustrating a device for querying embedded information according to an exemplary embodiment.

[0028] Figure 9 This is a schematic diagram of the structure of an electronic device according to an exemplary embodiment. Detailed Implementation

[0029] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0030] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0031] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0032] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0033] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0034] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0035] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0036] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0037] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0038] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0039] Meanwhile, it is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0040] Figure 1 This is a flowchart illustrating a method for querying event tracking information according to an exemplary embodiment. This method can be applied to clients such as personal computers, laptops, and tablets. Figure 1 As shown, the above-mentioned method for querying embedded information may include the following S101 to S103.

[0041] In S101, in response to receiving an operation instruction for the target tracking element in the target page, the tracking query conditions are determined according to the operation instruction.

[0042] In this disclosure, the target page may include one or more tracking elements, where tracking elements are elements on the page with added declarative tags, i.e., tracking elements are declarative tracking elements. Tracking elements can be components such as buttons, text boxes, checkboxes, sliders, etc.

[0043] The target event tracking element is any event tracking element on the target page.

[0044] In S102, a first query request is sent to the event tracking platform to obtain the event tracking information of the target event tracking element. The first query request includes event tracking query conditions.

[0045] In this disclosure, the page obtains user behavior and operations through tracking elements and uploads the obtained data to the tracking platform. In this way, tracking information can be queried on the tracking platform according to the tracking query conditions.

[0046] After receiving the first query request from the client, the event tracking platform queries the event tracking information of the target event tracking element according to the event tracking query conditions.

[0047] In S103, in response to receiving the first response message from the tracking platform for the first query request, the tracking information of the target tracking element is displayed according to the first response message.

[0048] In this disclosure, the first response message may include tracking information or identification information of tracking information (e.g., ID).

[0049] In the above technical solution, users can automatically obtain tracking query conditions by operating on the target tracking elements on the target page, and retrieve the tracking information of the target elements from the tracking platform based on these conditions, then visualize the tracking information. In this way, when a user needs to query the tracking information of any tracking element on the target page, they can obtain the tracking information simply by visually operating on the corresponding tracking element. This makes obtaining tracking information more convenient and intuitive, improving the efficiency of tracking information retrieval. Furthermore, the tracking information query method provided in this disclosure allows even non-technical personnel to easily query tracking information without needing to memorize the tracking parameters or page element identifiers of page elements, or to pre-establish a correspondence table between page element identifiers and query conditions (i.e., tracking parameters), thus avoiding the maintenance work of the correspondence table.

[0050] Furthermore, before users can interact with the event tracking elements on the target page, they need to know which elements on the target page are event tracking elements. Specifically, in one implementation, information about the event tracking elements on the target page can be pre-stored (e.g., stored in a table format). This allows users to determine which elements on the target page are event tracking elements based on the stored information.

[0051] In another implementation, to help users quickly and intuitively identify which elements on the target page are data tracking elements, these elements can be highlighted. Specifically, for example... Figure 2 As shown, the above method may further include the following S104.

[0052] In S104, when the target page has finished loading, the embedded elements on the target page are highlighted.

[0053] Specifically, the following steps (1) and (2) can be used to highlight the event tracking elements on the target page:

[0054] Step (1): Identify the event tracking elements in the target page.

[0055] In one implementation, when designing page tracking, the attributes of page elements with added declarative tags can be marked. For example, tag information (such as adding prefixes, suffixes, etc.) can be added to the attributes of page elements with added declarative tags. In this way, the tracking elements in the target page can be determined based on the tag information of the attributes of each element in the target page.

[0056] For example, when designing page tracking, add the prefix "data-log" to the attributes of page elements with declarative tags. This way, elements on the target page with the prefix "data-log" can be identified as tracking elements.

[0057] In another implementation, when designing page tracking points, information about page elements with added declarative tags can be stored, that is, information about tracking elements in the target page can be stored in advance, so that tracking elements in the target page can be determined based on this information.

[0058] Step (2): For each tracking element, modify the border style of the tracking element to highlight it.

[0059] In one implementation, the elements on the target page can be highlighted by modifying the color of the borders of each element.

[0060] In another implementation, the tracking elements on the target page can be highlighted by modifying the border lines (e.g., thickening) of each tracking element. Figure 3 The "Confirm" button shown in the image.

[0061] The following is a detailed description of the specific implementation method for responding to the received operation instruction for the target tracking element in the target page and determining the tracking query conditions according to the operation instruction in S101. Specifically, it can be achieved through the following steps [1] and [2]:

[0062] Step [1]: In response to the detection that the cursor is hovering over the target event element, display the overlay corresponding to the target event element.

[0063] In this disclosure, when a user needs to query the tracking information of a tracking element on a target page, the user can hover the mouse over the tracking element. When the client detects that the cursor is hovering over the target tracking element, a corresponding overlay can be displayed near the target tracking element. The overlay includes tracking event type options. If the cursor stays on the tracking element for more than a preset time, it is considered a hover operation.

[0064] For example, such as Figure 3 As shown, the target event element is the "Confirm" button, and its corresponding overlay includes three event types: click event, hover event, and display event.

[0065] Step [2]: In response to receiving the first selection operation for the event type option, determine the event query conditions according to the target event type selected by the first selection operation.

[0066] In this disclosure, users can select one or more event types from the event type options in the floating layer according to their query needs, i.e., target event types. It is evident that the target event type can include one or more of the event types covered by the event type options.

[0067] For example, users can click Figure 3 In the event type option "Click" in the tracking point Select the click event.

[0068] For another example, users can click Figure 3 In the event type options, click the "+" button to the right to select multiple event types simultaneously. This allows users to query multiple event metrics at the same time based on their needs, facilitating comparative analysis.

[0069] The following is a detailed explanation of the specific implementation method for determining the tracking query conditions based on the target tracking event type selected by the first selection operation in step [2] above. Specifically, it can be achieved through the following steps

[21] to

[23] :

[0070] Step

[21] : Determine the query metrics of the target event based on the target event type selected in the first selection operation.

[0071] Specifically, the query metrics corresponding to each target event type selected in the first selection operation can be determined as the query metrics of the target event element.

[0072] For example, if the target event type includes click events, then the query metric for the target event element is the number of clicks.

[0073] For example, if the target event type includes hover events, then the query metric for the target event element is the number of hover events.

[0074] For example, if the target event type includes display events, then the query metric for the target event element is the number of displays (i.e., the number of times the target event element is displayed on the page; however, sometimes the target page can only display a portion of the entire page, and the target event element does not always appear on the target page).

[0075] For example, if the target event types include click events, hover events, and display events, then the query metrics for the target event element include the number of clicks, the number of hovers, and the number of displays.

[0076] Step

[22] : Obtain the attribute information of the target embedded element.

[0077] The attribute information of the target tracking element can include the name of the target tracking element and the module in which the target tracking element is located.

[0078] For example, such as Figure 4 As shown, the attribute information of the target tracking element "Confirm" button is as follows:

[0079] name = Custom list pop-up - Confirm

[0080] module = Search Management List

[0081] Step

[23] : Determine the query indicators and attribute information as the conditions for tracking points.

[0082] For example, if the target event element is a "Confirm" button, and the target event type includes click events, then the event query conditions for the "Confirm" button are as follows: Figure 4 The content between the two horizontal lines in the image, and the corresponding tracking query results are as follows: Figure 4 The line graph shown.

[0083] For example, if the target event element is a "Confirm" button, and the target event types include click events, hover events, and display events, then the event query conditions for the target event element "Confirm" button would be as follows: Figure 5 As shown, or as Figure 6 The content between the two horizontal lines in the image, and the corresponding tracking query results are as follows: Figure 6 The line graph shown.

[0084] The following is a detailed description of the specific implementation method for displaying the embedding information of the target embedding element according to the first response message in S103 above.

[0085] In one implementation, the first response message may include event tracking information. In this case, after the client receives the first response message, it can obtain the event tracking information of the target event tracking element by parsing the first response message. Then, the event tracking information can be displayed directly on the target page or displayed on another page.

[0086] Specifically, after receiving the first query request from the client, the event tracking platform queries the event tracking information of the target event tracking element according to the event tracking query conditions, and then sends a first response message containing the event tracking information of the target event tracking element to the client. After receiving the first response message, the client parses the first response message to obtain the event tracking information of the target event tracking element and displays the event tracking information of the target event tracking element.

[0087] In another implementation, the first response message may include: the first address information of the page containing the tracking information of the target tracking element, such as a Uniform Resource Locator (URL). In this case, after receiving the first response message, the client can obtain the aforementioned first address information by parsing the first response message. Then, the client can jump to the page corresponding to the first address information to display the tracking information of the target tracking element.

[0088] Specifically, after receiving the first query request from the client, the event tracking platform queries the event tracking information of the target event tracking element according to the event tracking query conditions, displays the event tracking information of the target event tracking element through a webpage, and obtains the first address information of the webpage. Then, it sends a first response message containing the first address information to the client. After receiving the first response message, the client parses the first response message to obtain the aforementioned first address information, and then redirects to the page corresponding to the first address information to display the event tracking information of the target event tracking element.

[0089] In another implementation, the first response message may include identification information of the target tracking element's tracking information. In this case, after receiving the first response message, the client can obtain the identification information of the target tracking element's tracking information by parsing the message. Then, the client can first determine the first address information of the page containing the target tracking element's tracking information based on the identification information; then, it can redirect to the page corresponding to the first address information to display the target tracking element's tracking information.

[0090] Specifically, after receiving the first query request from the client, the event tracking platform queries the event tracking information of the target event tracking element according to the event tracking query conditions, and determines the identification information of the event tracking information. Then, it displays the event tracking information of the target event tracking element through a webpage. The first address information of the webpage consists of the domain name of the event tracking platform and the identification information of the event tracking information of the target event tracking element. Next, it sends a first response message containing the identification information of the aforementioned event tracking information to the client. After receiving the first response message, the client parses the first response message to obtain the identification information of the event tracking information of the target event tracking element. Then, it concatenates the domain name of the event tracking platform with the identification information to obtain the first address information of the page containing the event tracking information of the target event tracking element. Finally, it redirects to the page corresponding to the first address information to display the event tracking information of the target event tracking element.

[0091] In addition, to enhance the security of the event tracking information, the event tracking platform needs to authenticate the identity of the initiator of the first query request (i.e., the queryer) before sending the first response message to the client. Only after confirming that the initiator of the first query request has passed the identity authentication will the platform send the first response message to the client.

[0092] Specifically, the aforementioned first query request may also include the authentication information session of the event tracking platform and the cross-site request forgery token (csrf_token). The first response message is sent by the event tracking platform after confirming that the initiator of the first query request has passed identity authentication based on the session and csrf_token.

[0093] The CSRF token is a defense mechanism to prevent users from performing unintended actions on a currently logged-in web application. The event tracking platform authenticates the initiator of the first query request based on the session and CSRF token in the first query request. The specific methods for authentication based on the session and CSRF token are well-known to those skilled in the art and will not be elaborated upon here.

[0094] Furthermore, the aforementioned session and csrf_token are obtained through various methods. In one implementation, if the initiator of the first query request has obtained authorization to read the cookie information of the browser hosting the target page, the session and csrf_token can be obtained by querying the cookie information of the browser hosting the target page. Specifically, the initiator of the first query request has logged into the event tracking platform through the browser hosting the target page, and the aforementioned cookie information includes the event tracking platform's session and csrf_token.

[0095] In another implementation, the session and csrf_token can be obtained through the HTML tag iframe of the target page.

[0096] Here, `iframe` is an HTML tag that acts as a document within a document, or a floating frame. The `iframe` element creates an inline frame (i.e., an inline frame) that contains another document. An inline frame is used to embed another document within the current HTML document. In this disclosure, the `iframe` shares the same domain as the event tracking platform; that is, the `iframe` and the event tracking platform are from the same origin. This allows the client to communicate with the event tracking platform through the `iframe` to obtain the aforementioned session and csrf_token.

[0097] In addition, the target page also includes a toolbar (e.g., a scalable toolbar), which includes page metrics options, allowing users to easily and quickly query frequently used page metrics with a single click.

[0098] like Figure 7As shown, the toolbar on the target page includes two page metrics options: PV (Page View) and UV (Unique Visitor). " / pc / home" is the address of the target webpage. PV refers to the number of users viewing the webpage, reflecting the page's traffic. UV refers to the number of unique visitors within a certain period, reflecting the target webpage's popularity.

[0099] At this point, the above method can also include the following three steps:

[0100] In response to receiving a second selection operation for page metric options, determine the metric query conditions based on the target page metric selected in the second selection operation;

[0101] Send a second query request to the event tracking platform to obtain the target page's metrics information, wherein the second query request includes the metrics query conditions;

[0102] Upon receiving a second response message from the event tracking platform regarding the second query request, the system displays the indicator information based on the second response message.

[0103] In this disclosure, users can select one or more page metrics, i.e., target page metrics, from the page metric options in the toolbar according to their query needs. Therefore, the target page metric can include one or more of the page metrics covered by the page metric options.

[0104] For example, users can click Figure 7 The page metrics option "PV" in the middle To select the PV (page view) metric.

[0105] For another example, users can click Figure 7 The "+" button to the right of the "PV" page metric option allows you to select multiple page metrics simultaneously. This enables users to query multiple page metrics at the same time based on their query needs, facilitating comparative analysis.

[0106] The second response message includes indicator information or identifier information of indicator information. In this disclosure, the indicator information can be displayed based on the second response message in a manner similar to that used in S103 above to display the tracking information of the target tracking element based on the first response message; this disclosure will not elaborate further.

[0107] The following is a detailed explanation of the specific implementation method for determining the query conditions based on the target page indicators selected in the second selection operation. Specifically, this can be achieved through the following steps ① and ②:

[0108] Step 1: Obtain the second address information of the target page selected in the second selection operation.

[0109] Step 2: Determine the second address information and the target page metrics as the criteria for metric query.

[0110] In addition, to further enhance the security of the event tracking information, the event tracking platform needs to authenticate the identity of the initiator of the second query request before sending the second response message to the client. Only after confirming that the initiator of the second query request has passed the identity authentication will the platform send the second response message to the client.

[0111] Specifically, the second query request may also include the authentication information session of the event tracking platform and the cross-site request forgery token (csrf_token). The second response message is sent by the event tracking platform after confirming that the initiator of the second query request has passed identity authentication based on the session and csrf_token.

[0112] Figure 8 This is a block diagram illustrating a device for querying embedded information according to an exemplary embodiment. Figure 8 As shown, the device 800 includes:

[0113] The first determining module 801 is used to respond to receiving an operation instruction for a target embedded element in a target page and determine the embedded element query conditions according to the operation instruction.

[0114] The sending module 802 is used to send a first query request to the tracking platform for obtaining tracking information of the target tracking element, wherein the first query request includes the tracking query conditions.

[0115] The display module 803 is used to respond to receiving a first response message from the tracking platform for the first query request, and to display the tracking information of the target tracking element according to the first response message, wherein the first response message includes the tracking information or the identification information of the tracking information.

[0116] In the above technical solution, users can automatically obtain tracking query conditions by operating on the target tracking elements on the target page, and retrieve the tracking information of the target elements from the tracking platform based on these conditions, then visualize the tracking information. In this way, when a user needs to query the tracking information of any tracking element on the target page, they can obtain the tracking information simply by visually operating on the corresponding tracking element. This makes obtaining tracking information more convenient and intuitive, improving the efficiency of tracking information retrieval. Furthermore, the tracking information query method provided in this disclosure allows even non-technical personnel to easily query tracking information without needing to memorize the tracking parameters or page element identifiers of page elements, or to pre-establish a correspondence table between page element identifiers and query conditions (i.e., tracking parameters), thus avoiding the maintenance work of the correspondence table.

[0117] Optionally, the device 800 further includes:

[0118] The highlighting module is used to highlight the tracking elements in the target page when the target page is loaded, wherein the target tracking element is any of the tracking elements in the target page;

[0119] The first determining module 801 includes:

[0120] The display submodule is used to display a floating layer corresponding to the target tracking element in response to the detection that the cursor is hovering over the target tracking element, wherein the floating layer includes tracking event type options;

[0121] The first determining submodule is configured to respond to receiving a first selection operation for the event type option and determine the event query conditions based on the target event type selected by the first selection operation, wherein the target event type includes one or more of the event types involved in the event type option.

[0122] Optionally, the first determining submodule includes:

[0123] The second determining submodule is used to determine the query index of the target event element based on the target event type selected in the first selection operation.

[0124] The first acquisition submodule is used to acquire the attribute information of the target embedded element;

[0125] The third determination submodule is used to determine the query indicators and the attribute information as the tracking point query conditions.

[0126] Optionally, the highlighting module includes:

[0127] The fourth determination submodule is used to determine the embedded elements in the target page;

[0128] The modification submodule is used to modify the border style of each of the aforementioned tracking elements to highlight the tracking element.

[0129] Optionally, the first response message includes the identification information of the embedded information;

[0130] The display module 803 includes:

[0131] The fifth determining submodule is used to determine the first address information of the page containing the target embedding element based on the identification information of the embedding information;

[0132] The jump module is used to jump to the page corresponding to the first address information to display the embedded information.

[0133] Optionally, the first query request may further include the authentication information session of the event tracking platform and the cross-site forgery request-token csrf_token, wherein the first response message is sent by the event tracking platform after confirming that the initiator of the first query request has passed identity authentication based on the session and the csrf_token.

[0134] Optionally, the device 800 further includes:

[0135] The first acquisition module is used to obtain the session and the csrf_token by querying the cookie information of the browser where the target page is located, wherein the initiator of the first query request has logged into the event tracking platform through the browser; or

[0136] The second acquisition module is used to acquire the session and the csrf_token through the HTML tag iframe of the target page, wherein the iframe has the same domain name as the tracking platform.

[0137] Optionally, the target page further includes a toolbar, wherein the toolbar includes page indicator options;

[0138] The device 800 further includes:

[0139] The second determining module is configured to respond to receiving a second selection operation for the page indicator option, and determine indicator query conditions based on the target page indicator selected by the second selection operation, wherein the target page indicator includes one or more of the page indicators involved in the page indicator option.

[0140] The third acquisition module is used to send a second query request to the tracking platform to obtain the indicator information of the target page indicator, wherein the second query request includes the indicator query conditions;

[0141] The display module 803 is further configured to respond to receiving a second response message from the data tracking platform for the second query request, and display the indicator information according to the second response message, wherein the second response message includes the indicator information or the identifier information of the indicator information.

[0142] Optionally, the second determining module includes:

[0143] The second acquisition submodule is used to acquire the second address information of the target page;

[0144] The sixth determination submodule is used to determine the second address information and the target page index as the index query conditions.

[0145] The following is for reference. Figure 9 The diagram illustrates a structural schematic of an electronic device (e.g., a terminal device) 600 suitable for implementing embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 9 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0146] like Figure 9 As shown, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. Processing device 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0147] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 9 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0148] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, it performs the functions defined in the methods of embodiments of this disclosure.

[0149] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0150] In some implementations, the client can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed networks.

[0151] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0152] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: in response to receiving an operation instruction for a target tracking element in a target page, determine tracking query conditions according to the operation instruction; send a first query request to a tracking platform for obtaining tracking information of the target tracking element, wherein the first query request includes the tracking query conditions; and in response to receiving a first response message from the tracking platform for the first query request, display the tracking information of the target tracking element according to the first response message, wherein the first response message includes the tracking information or identification information of the tracking information.

[0153] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0154] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0155] The modules described in the embodiments of this disclosure can be implemented in software or in hardware. The names of the modules are not necessarily limiting in certain circumstances; for example, a sending module can also be described as "a module that sends a first query request to the tracking platform to obtain tracking information of the target tracking element."

[0156] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0157] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0158] According to one or more embodiments of this disclosure, Example 1 provides a method for querying embedded information, including:

[0159] In response to receiving an operation instruction for a target event tracking element on a target page, determine the event tracking query conditions based on the operation instruction;

[0160] Send a first query request to the event tracking platform to obtain event tracking information of the target event tracking element, wherein the first query request includes the event tracking query conditions;

[0161] In response to receiving a first response message from the event tracking platform for the first query request, the event tracking information of the target event tracking element is displayed according to the first response message, wherein the first response message includes the event tracking information or the identification information of the event tracking information.

[0162] According to one or more embodiments of this disclosure, Example 2 provides the method of Example 1, the method further comprising: highlighting a tracking element in the target page when the target page is loaded, wherein the target tracking element is any one of the tracking elements in the target page; the step of determining tracking query conditions in response to receiving an operation instruction for the target tracking element in the target page, according to the operation instruction, includes: displaying a floating layer corresponding to the target tracking element in response to detecting that the cursor is hovering over the target tracking element, wherein the floating layer includes tracking event type options; and determining tracking query conditions in response to receiving a first selection operation for the tracking event type options, according to the target tracking event type selected by the first selection operation, wherein the target tracking event type includes one or more of the tracking event types involved in the tracking event type options.

[0163] According to one or more embodiments of this disclosure, Example 3 provides the method of Example 2, wherein determining the tracking query conditions based on the target tracking event type selected by the first selection operation includes: determining the query index of the target tracking element based on the target tracking event type selected by the first selection operation; obtaining the attribute information of the target tracking element; and determining the query index and the attribute information as the tracking query conditions.

[0164] According to one or more embodiments of this disclosure, Example 4 provides the method of Example 2, wherein highlighting the tracking elements in the target page includes: determining the tracking elements in the target page; and for each tracking element, modifying the border style of the tracking element to highlight the tracking element.

[0165] According to one or more embodiments of this disclosure, Example 5 provides the method of Example 1, wherein the first response message includes identification information of the tracking information; the step of displaying the tracking information of the target tracking element according to the first response message includes: determining the first address information of the page containing the tracking information of the target tracking element according to the identification information of the tracking information; and jumping to the page corresponding to the first address information to display the tracking information.

[0166] According to one or more embodiments of this disclosure, Example 6 provides the method of Example 1, wherein the first query request further includes the authentication information session of the event tracking platform and the cross-site forgery request-token csrf_token, wherein the first response message is sent by the event tracking platform after confirming that the initiator of the first query request has passed identity authentication based on the session and the csrf_token.

[0167] According to one or more embodiments of this disclosure, Example 7 provides the method of Example 6, wherein the session and the csrf_token are obtained by: querying the cookie information of the browser where the target page is located to obtain the session and the csrf_token, wherein the initiator of the first query request has logged into the tracking platform through the browser; or obtaining the session and the csrf_token through the HTML tag iframe of the target page, wherein the iframe has the same domain name as the tracking platform.

[0168] According to one or more embodiments of this disclosure, Example 8 provides a method of any one of Examples 1-7, wherein the target page further includes a toolbar, wherein the toolbar includes page indicator options; the method further includes: in response to receiving a second selection operation for the page indicator options, determining indicator query conditions based on the target page indicator selected by the second selection operation, wherein the target page indicator includes one or more of the page indicators involved in the page indicator options; sending a second query request to the tracking platform for obtaining indicator information of the target page indicator, wherein the second query request includes the indicator query conditions; in response to receiving a second response message from the tracking platform for the second query request, displaying the indicator information based on the second response message, wherein the second response message includes the indicator information or identification information of the indicator information.

[0169] According to one or more embodiments of this disclosure, Example 9 provides the method of Example 8, wherein determining the index query conditions based on the target page index selected by the second selection operation includes: obtaining second address information of the target page; and determining the second address information and the target page index as the index query conditions.

[0170] According to one or more embodiments of this disclosure, Example 10 provides a tracking information query device, comprising: a first determining module, configured to determine tracking query conditions according to the operation instruction received for a target tracking element in a target page; a sending module, configured to send a first query request to a tracking platform for obtaining tracking information of the target tracking element, wherein the first query request includes the tracking query conditions; and a display module, configured to display the tracking information of the target tracking element according to the first response message received from the tracking platform for the first query request, wherein the first response message includes the tracking information or identification information of the tracking information.

[0171] According to one or more embodiments of the present disclosure, Example 11 provides a computer-readable medium having a computer program stored thereon that, when executed by a processing device, implements the steps of the method described in any one of Examples 1-9.

[0172] According to one or more embodiments of this disclosure, Example 12 provides an electronic device including: a storage device having a computer program stored thereon; and a processing device for executing the computer program in the storage device to implement the steps of any one of Examples 1-9.

[0173] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0174] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0175] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative forms of implementing the claims. Regarding the apparatus in the above embodiments, the specific manner in which the various modules perform their operations has been described in detail in the embodiments relating to the method, and will not be elaborated upon here.

Claims

1. A method for querying embedded information, characterized in that, include: In response to receiving an operation instruction for a target event tracking element on a target page, determine the event tracking query conditions based on the operation instruction; Send a first query request to the event tracking platform to obtain event tracking information of the target event tracking element, wherein the first query request includes the event tracking query conditions; In response to receiving a first response message from the tracking platform for the first query request, the tracking information of the target tracking element is displayed according to the first response message, wherein the first response message includes the tracking information or the identification information of the tracking information; When the target page finishes loading, the tracking element in the target page is highlighted, wherein the target tracking element is any of the tracking elements in the target page; The response to receiving an operation instruction for a target tracking element on a target page, and determining tracking query conditions based on the operation instruction, includes: In response to detecting that the cursor is hovering over the target event element, a floating layer corresponding to the target event element is displayed, wherein the floating layer includes event type options; In response to receiving a first selection operation for the event type option, the event tracking query conditions are determined according to the target event type selected by the first selection operation, wherein the target event type includes one or more of the event types involved in the event type option. The step of determining the tracking point query conditions based on the target tracking point event type selected in the first selection operation includes: Based on the target event type selected in the first selection operation, determine the query metrics of the target event element; Obtain the attribute information of the target tracking element, including the name of the target tracking element and the module in which the target tracking element is located; The query indicators and the attribute information are determined as the data tracking query conditions; Wherein, if the first response message includes the identifier information of the tracking information, the step of displaying the tracking information of the target tracking element according to the first response message includes: Based on the identifier information of the tracking information, determine the first address information of the page containing the tracking information of the target tracking element; jump to the page corresponding to the first address information to display the tracking information.

2. The method according to claim 1, characterized in that, The highlighted elements on the target page include: Identify the event tracking elements in the target page; For each of the aforementioned tracking elements, modify the border style of that tracking element to highlight it.

3. The method according to claim 1, characterized in that, The first query request also includes the authentication information session of the event tracking platform and the cross-site forgery request-token csrf_token. The first response message is sent by the event tracking platform after confirming that the initiator of the first query request has passed identity authentication based on the session and the csrf_token.

4. The method according to claim 3, characterized in that, The session and the csrf_token are obtained in the following ways: The session and CSRF token are obtained by querying the cookie information of the browser where the target page is located, wherein the initiator of the first query request has logged into the event tracking platform through the browser; or The session and the csrf_token are obtained through the HTML tag iframe of the target page, wherein the iframe has the same domain name as the event tracking platform.

5. The method according to any one of claims 1-4, characterized in that, The target page also includes a toolbar, wherein the toolbar includes page metrics options; The method further includes: In response to receiving a second selection operation for the page indicator option, the indicator query conditions are determined according to the target page indicator selected by the second selection operation, wherein the target page indicator includes one or more of the page indicators involved in the page indicator option. Send a second query request to the event tracking platform to obtain the indicator information of the target page indicator, wherein the second query request includes the indicator query conditions; In response to receiving a second response message from the data tracking platform for the second query request, the indicator information is displayed based on the second response message, wherein the second response message includes the indicator information or the identifier information of the indicator information.

6. The method according to claim 5, characterized in that, The step of determining the metric query conditions based on the target page metric selected by the second selection operation includes: Obtain the second address information of the target page; The second address information and the target page index are determined as the index query conditions.

7. A device for querying embedded information, characterized in that, include: The first determining module is used to respond to receiving an operation instruction for a target tracking element in the target page, and determine the tracking query conditions according to the operation instruction; The sending module is used to send a first query request to the tracking platform to obtain the tracking information of the target tracking element, wherein the first query request includes the tracking query conditions. The display module is used to respond to a first response message received from the tracking platform for the first query request, and to display the tracking information of the target tracking element according to the first response message, wherein the first response message includes the tracking information or the identification information of the tracking information; The highlighting module is used to highlight the tracking elements in the target page when the target page is loaded, wherein the target tracking element is any of the tracking elements in the target page; The first determining module includes: The display submodule is used to display a floating layer corresponding to the target tracking element in response to the detection that the cursor is hovering over the target tracking element, wherein the floating layer includes tracking event type options; The first determining submodule is configured to respond to receiving a first selection operation for the event type option and determine the event query conditions based on the target event type selected by the first selection operation. The target event type includes one or more of the event types involved in the event type option. The step of determining the tracking point query conditions based on the target tracking point event type selected in the first selection operation includes: Based on the target event type selected in the first selection operation, determine the query metrics of the target event element; Obtain the attribute information of the target tracking element, including the name of the target tracking element and the module in which the target tracking element is located; The query indicators and the attribute information are determined as the data tracking query conditions; Wherein, if the first response message includes the identification information of the tracking information, the display module is used to: determine the first address information of the page containing the tracking information of the target tracking element based on the identification information of the tracking information; and jump to the page corresponding to the first address information to display the tracking information.

8. A computer-readable medium having a computer program stored thereon, characterized in that, When executed by the processing device, the program implements the steps of the method according to any one of claims 1-6.

9. An electronic device, characterized in that, include: A storage device on which computer programs are stored; A processing device for executing the computer program in the storage device to implement the steps of the method according to any one of claims 1-6.

Citation Information

Patent Citations

  • Data displaying method and device

    CN108334525A