Method and device for real-time analysis of buried point information, storage medium and electronic device

Abstract

The application discloses a method and device for real-time analysis of buried point information, a storage medium and electronic equipment. The method comprises the following steps: generating a json statement corresponding to a buried point event based on parameters corresponding to the buried point event and format specifications of a third-party tool; determining a query statement supported by the third-party tool based on the json statement, and obtaining buried point information corresponding to the buried point event based on a query interface of the third-party tool. The method can obtain the buried point information recorded in the third-party tool in real time, and save a query event for obtaining information corresponding to the buried point event based on the information recorded in the third-party tool. The execution of the buried point event can be analyzed based on the third-party tool, in particular, whether the buried point event can be normally executed.

Description

Technical Field

[0001] This invention relates to the field of data processing, and in particular to methods, apparatus, storage media, and electronic devices for real-time analysis of embedded data points. Background Technology

[0002] As the company's business grows, to track application or webpage usage for further product optimization or to provide data support for future work, event tracking is implemented in specific application processes and webpage components to collect information. The collected information is broadly categorized into page statistics and user behavior statistics, such as the number of visits, visitors, dwell time, page views, and bounce rate. Page statistics track page views (PV), unique visitors (UV), and duration of visits, as well as the flow of data between pages. User behavior statistics typically involve user-defined event tracking to record user actions on applications and webpages, including detailed information about these actions. User actions on applications and webpages are diverse, including clicks and other similar behaviors.

[0003] There are two common ways to set up event tracking: one is for developers to inject tracking code during code development, and the other is to use third-party analytics tools, such as Umeng, Sensors Data, Talkingdata, and GrowingIO. The principle behind third-party analytics tools is to standardize the collection and management of underlying user behavior data, establish a dedicated data warehouse, and provide visualization and analysis capabilities. When using the event tracking information obtained from third-party analytics tools, for example, testers or analysts might use the data analysis functions of these tools to customize query metrics and configure parameters in an environment independent of the third-party tool. These configured parameters are then passed to the third-party analytics tool to filter the event tracking information obtained from it. Furthermore, data fields can be set in an environment independent of the third-party tool, meaning that the required data fields can be viewed in an environment independent of the third-party tool, and the information corresponding to the queried event tracking can be obtained from the event tracking information. For example, if the query metric is determined to be the total number of element exposures, the following configuration can be made in an environment independent of the third-party tool: Operating System = Android, Application Unique Identifier = com.yeqin.enterpriseservice, etc., and the application version, operating system, etc., can be configured in the viewing fields. In an environment independent of third-party tools, the corresponding fields of the tracking information obtained by the third-party tools can be viewed. Parameter configuration is as follows: Figure 1 As shown, the displayed data fields are as follows: Figure 2As shown. Taking the R&D side and the testing side as an example, the testing side needs to test the event tracking. The testing side uses the event tracking analysis function of a third-party tool to configure the event tracking name, indicators, global filtering of event tracking, and other configurations. The test cases execute the event tracking, and then the test side can view the specific information corresponding to the event tracking recorded in the third-party tool according to the configured fields.

[0004] However, third-party tools have specific refresh mechanisms that require a certain buffer time, causing data to not be synchronized in real time. This results in the tracking information for changed tracking events not being displayed immediately, requiring a waiting period before it can be obtained. For example, if developers adjust the code for a button's tracking event on a page, the specific data synchronization mechanism in third-party tools means that even if the tracking event is executed on the page, the testing side cannot simultaneously query the tracking information recorded by the third-party tool. A certain amount of time is often required before the tracking information recorded by the third-party tool can be found.

[0005] It is evident that the event tracking information recorded in third-party tools is not instantaneous or real-time. It takes a long time to obtain updated event tracking information, resulting in a waste of time and reduced efficiency for users who call third-party tools. Summary of the Invention

[0006] In view of this, the present invention provides a method, apparatus, storage medium and electronic device for real-time analysis of tracking information, which can solve the technical problems of real-time acquisition of tracking information recorded in third-party tools and storage of query events corresponding to tracking events based on information recorded in third-party tools.

[0007] To address the aforementioned technical problems, this invention provides a method for real-time analysis of embedded data points, the method comprising:

[0008] Step S1: Based on the parameters corresponding to the event tracking and the format specifications of the third-party tool, generate a JSON statement corresponding to the event tracking;

[0009] Step S2: Based on the JSON statement, determine the query statement supported by the third-party tool, and use the query statement to obtain the tracking information corresponding to the tracking event through the query interface of the third-party tool.

[0010] Optionally, generating the JSON statement corresponding to the event tracking includes:

[0011] Set the corresponding parameters of the event tracking in the third-party tool, and obtain the browser URL corresponding to the parameters generated in the third-party tool;

[0012] Parse the fields in the browser URL and generate a JSON statement corresponding to the event tracking based on the fields in the browser URL.

[0013] Optionally, determining the query statements supported by the third-party tool based on the JSON statement, and using the query statements to obtain the tracking information corresponding to the tracking event through the query interface of the third-party tool, includes:

[0014] The JSON statement is parsed using the Java language and converted into a query statement supported by the third-party tool.

[0015] The query interface of the third-party tool is invoked to directly access the underlying data of the third-party tool, and the tracking information corresponding to the tracking event is obtained from the underlying data.

[0016] Optionally, the method further includes storing the query event corresponding to the query statement in a local database, wherein the query event includes the query statement corresponding to the query, the JSON statement corresponding to the query statement, and the retrieved data points.

[0017] Optionally, the method further includes managing the query events through the local database, wherein the management includes at least adding, deleting, modifying, querying, reusing individually or in batches the query events.

[0018] Optionally, an automation tool is constructed that supports the automatic generation of query statements and the management of query events corresponding to the query statements.

[0019] Optionally, the automation tool includes a front-end framework, a back-end framework, and a database; the front-end framework is used to receive parameters corresponding to the tracking events input by the user, the back-end framework is used to receive parameters corresponding to the tracking events transmitted by the front-end framework, and access the query interface of the third-party tool; the database stores the query events.

[0020] Preferably, the query event is executed, and the tracking event corresponding to the query event is analyzed to determine whether it is abnormal.

[0021] This invention provides a device for real-time analysis of embedded data information, comprising:

[0022] JSON conversion module: Configured to generate JSON statements corresponding to the event tracking points based on the parameters corresponding to the event tracking points and the format specifications of third-party tools;

[0023] Query module: Configured to determine the query statements supported by the third-party tool based on the JSON statement, and use the query statements to obtain the tracking information corresponding to the tracking event through the query interface of the third-party tool.

[0024] The present invention provides a computer-readable storage medium storing a plurality of instructions; the plurality of instructions are configured to be loaded by a processor and executed as described above.

[0025] The present invention provides an electronic device, characterized in that the electronic device includes: a processor for executing multiple instructions; and a memory for storing multiple instructions; wherein the multiple instructions are stored in the memory and loaded by the processor for execution as described above.

[0026] Technical effects:

[0027] This invention can acquire event tracking information recorded in third-party tools in real time and save query events that retrieve information corresponding to event tracking based on the information recorded in the third-party tools. It can also automate the detection and monitoring of these third-party tools. This improves the efficiency of regression testing for event tracking, reduces waiting time during event tracking testing, and increases overall testing efficiency.

[0028] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0029] The above and other objects, features, and advantages of the present invention will become more apparent from the more detailed description of the embodiments of the invention in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of the invention and form part of the specification. They are used together with the embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same parts or steps.

[0030] Figure 1 This is a schematic diagram illustrating the configuration method of calling third-party tools to obtain information corresponding to event tracking in existing technologies;

[0031] Figure 2 This is a diagram illustrating how to view information corresponding to event tracking points obtained using third-party tools in existing technologies.

[0032] Figure 3 This is a flowchart illustrating a method for real-time analysis of embedded information provided in an exemplary embodiment of the present invention.

[0033] Figure 4 This is a schematic diagram illustrating a method for adding query events according to an exemplary embodiment of the present invention;

[0034] Figure 5 This is a schematic diagram illustrating a method for maintaining query events according to an exemplary embodiment of the present invention;

[0035] Figure 6 This is a schematic diagram illustrating the editing method of a query event according to an exemplary embodiment of the present invention;

[0036] Figure 7 This is a schematic diagram illustrating the execution method of a query event according to an exemplary embodiment of the present invention;

[0037] Figure 8 is a schematic diagram of a batch execution method for query events according to an exemplary embodiment of the present invention;

[0038] Figure 9 This is a schematic diagram of the structure of a device for real-time analysis of embedded information provided in an exemplary embodiment of the present invention;

[0039] Figure 10 This is the structure of an electronic device provided in an exemplary embodiment of the present invention. Detailed Implementation

[0040] Hereinafter, exemplary embodiments according to the present invention will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments of the present invention. It should be understood that the present invention is not limited to the exemplary embodiments described herein.

[0041] It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of the invention.

[0042] Those skilled in the art will understand that the terms "first," "second," etc., in the embodiments of the present invention are only used to distinguish different steps, devices, or modules, and do not represent any specific technical meaning, nor do they indicate a necessary logical order between them.

[0043] It should also be understood that in the embodiments of the present invention, "multiple" can refer to two or more, and "at least one" can refer to one, two or more.

[0044] It should also be understood that any component, data or structure mentioned in the embodiments of the present invention can generally be understood as one or more unless explicitly defined or given contrary instructions in the context.

[0045] Furthermore, the term "and / or" in this invention is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this invention generally indicates that the preceding and following related objects have an "or" relationship.

[0046] It should also be understood that the description of the various embodiments in this invention emphasizes the differences between the various embodiments, and the similarities or similarities can be referred to each other. For the sake of brevity, they will not be described in detail.

[0047] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0048] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the invention or its application or use.

[0049] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, they should be considered part of the specification.

[0050] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0051] The embodiments of this invention can be applied to electronic devices such as terminal devices, computer systems, and servers, and can operate together with a wide range of other general-purpose or special-purpose computing system environments or configurations. Well-known examples of terminal devices, computing systems, environments, and / or configurations suitable for use with electronic devices such as terminal devices, computer systems, and servers include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments including any of the above systems, etc.

[0052] Electronic devices such as terminal devices, computer systems, and servers can be described in the general context of computer system executable instructions (such as program modules) executed by a computer system. Typically, program modules can include routines, programs, object programs, components, logic, data structures, etc., which perform specific tasks or implement specific abstract data types. Computer systems / servers can be implemented in distributed cloud computing environments, where tasks are executed by remote processing devices linked through communication networks. In distributed cloud computing environments, program modules can reside on local or remote computing system storage media, including storage devices.

[0053] Exemplary methods

[0054] Figure 3 This is a flowchart illustrating a method for real-time analysis of embedded information provided in an exemplary embodiment of the present invention. This embodiment can be applied to electronic devices, such as… Figure 3 As shown, it includes the following steps:

[0055] In this embodiment, the third-party tool is a data analysis tool that provides tracking information.

[0056] Step S1: Based on the parameters corresponding to the event tracking and the format specifications of the third-party tool, generate a JSON statement corresponding to the event tracking, wherein:

[0057] Taking the event tracking as a click event of a button within an application as an example, the parameter corresponding to this event tracking is the number of clicks. Therefore, the parameters corresponding to this event tracking are the application's identifier (AppId) and the number of clicks (time). Based on the format specifications of the third-party tool and the parameters corresponding to this event tracking, a JSON statement corresponding to the event tracking is generated. A convenient way to generate the JSON statement is to set the parameters corresponding to the event tracking in the third-party tool, obtain the browser URL corresponding to the parameters generated by the third-party tool, parse the fields in the browser URL (which incorporate the format specifications of the third-party tool), and generate the JSON statement corresponding to the event tracking based on the fields in the browser URL.

[0058] Step S2: Based on the JSON statement, determine the query statements supported by the third-party tool, and based on the parameters corresponding to the event, obtain the event tracking information corresponding to the event tracking through the query interface of the third-party tool.

[0059] The JSON statement is parsed using Java and converted into a query statement supported by the third-party tool. For example, if the third-party tool supports SQL, the JSON statement is converted into an SQL statement. The query interface of the third-party tool refers to an API that can directly access the underlying data of the third-party tool. By calling the query interface API of the third-party tool, the API can directly access the underlying data of the third-party tool, eliminating the need to wait for buffering and refreshing. This allows direct access to the data stored by the third-party tool, i.e., obtaining the tracking information corresponding to the tracking event, and directly displaying the tracking information corresponding to the tracking event retrieved from the third-party tool. For example, if the button is clicked num times in an application (i.e., the tracking event is a single click event), the click count (time) corresponding to this single click event in the underlying database of the third-party tool is the original value (time1) plus num. If the query interface of the third-party tool is used, since the query data is not updated in real time, the click count obtained through the query interface is time1, while the click count obtained through the query interface API is time1 + num.

[0060] Direct queries via the third-party tool's query interface eliminate the need to configure viewing metrics for the event tracking, providing detailed information on each piece of data for accurate analysis. Since the event tracking information is obtained through the third-party tool's API, it's equivalent to directly querying the tool's underlying database, allowing for real-time data querying and display without waiting for the tool's buffering and refresh. In contrast, using the third-party tool's query interface requires configuring viewing metrics and is limited by its data synchronization mechanism, requiring waiting for buffering and refresh, and thus cannot obtain the event tracking information in real-time, requiring a waiting period.

[0061] This invention utilizes the third-party tool's analysis function for event tracking, transforming the configuration parameters corresponding to the event tracking into query statements supported by the third-party tool. The tracking information corresponding to the event tracking is then obtained based on the query interface API of the third-party tool. The configuration parameters include, for example, configuration metrics and global filtering methods, and the query statements supported by the third-party tool satisfy the parameter conditions required by the query interface API of the third-party tool.

[0062] Furthermore, the query events corresponding to the query statement are stored in a local database. These query events are the query interfaces of the third-party tool accessed based on the query statement. For example, the query events corresponding to the query statement are stored in a local MySQL database.

[0063] The local database manages and maintains the query events. The local database reuses the query events individually or in batches. One or more query events form a query event list, which is managed and maintained by the local database.

[0064] The query interface of the third-party tool is used to obtain the tracking information corresponding to the tracking events. Each query corresponds to a query event, which includes the query statement, the JSON statement corresponding to the query statement, and the retrieved tracking information. The query events are stored in a local database. For example, a table (tracking) in a local MySQL database is used, which stores information such as the tracking event name, tracking event conditions, and tracking event type corresponding to the query event.

[0065] A query event list is composed of one or more query events stored in a local database. This list can be managed and maintained, including adding, deleting, modifying, and querying the query events. The management and maintenance of the query events themselves allows for the addition, deletion, modification, querying, and reuse of specific query events. For query events stored in the local database, both single query event execution and batch execution of multiple query events are possible. By executing these query events, they can be reused without reconfiguring the event parameters.

[0066] Furthermore, an automation tool is constructed that supports the automatic generation of query statements and the management of query events corresponding to those statements. For example... Figure 4 As shown, by clicking the "Auto-to-JSON" button, a JSON statement suitable for the third-party tool can be automatically generated based on the parameters corresponding to the input event tracking.

[0067] Furthermore, the automation tool belongs to a web system and includes a front-end framework, a back-end framework, and a database. The front-end framework receives parameters corresponding to the event tracking points input by the user, and the back-end framework receives these parameters from the front-end framework and accesses the query interface of the third-party tool. The database stores the query events. For example, using Bootstrap + jQuery as the front-end framework, it receives the parameters corresponding to the event tracking points input by the user and is used for page display and interaction with the back-end framework interface. Using Spring Boot + MyBatis as the back-end framework, it receives the parameters corresponding to the event tracking points input by the front-end framework and accesses the query interface of the third-party tool. The back-end framework interacts with the front-end framework's page and with the MySQL database, using MySQL as the database for storing data.

[0068] The query events are stored in the tracking table of a MySQL database by calling the MyBatis framework through Spring Boot.

[0069] Furthermore, the automation tool includes query event list management and maintenance. A query event list consists of one or more query events. Managing and maintaining the query event list includes adding, deleting, modifying, and querying the query events. For example, managing and maintaining the query events involves adding, deleting, modifying, querying, and reusing a specific query event. Figure 5 As shown, select items from the database based on certain filtering criteria. Figure 5 The query event list shown includes an event identifier (id), event name, event filter criteria, event verification content, event type, and operation. The operation refers to actions that can be performed on the query event, including editing and execution. The event filter criteria correspond to the JSON statements associated with the event. For example... Figure 6 As shown, editing of the query event is supported; for example, editing of the tracking conditions corresponding to the tracking event for the query event. Figure 7 As shown, the system supports the execution of the query events. For example, a query event to be executed can be obtained from the query event list. If the "execute" operation is performed on the query event to be executed, a new page will be launched. On the new page, the corresponding conditions can be selected, such as selecting the execution platform (online / test), entering the app version number and the occurrence time of the query event. After the query event to be executed is executed, the tracking data corresponding to the query event will be output in the text box below.

[0070] The automation tool supports batch execution of multiple query events. It identifies multiple query events to be executed and performs batch execution on them. The execution results are then marked as success or failure. Figures 8A-8B As shown, input filtering conditions are used, which are then converted into SQL statements with parameters matching the query interface of the third-party tool via Java code. For example, the filtering conditions may include the event name, the event occurrence time, and the event type. Based on these conditions, query events in the MySQL database that meet the criteria are filtered out. The filtering conditions are then converted into SQL statements with parameters matching the query interface of the third-party tool via Java code. By calling the query interface of the third-party tool, the event tracking information is returned.

[0071] Furthermore, the filtering conditions include the location of the event tracking, the type of the event tracking, and the name of the query event. The location of the event tracking is, for example, the platform or project where it is embedded; the type of the event tracking is, for example, web, app, or h5; and the name of the query event supports fuzzy matching and is not required. The filtering conditions allow you to retrieve a list of query events corresponding to those conditions. The list of query events includes the following information: the name of the event tracking, the filtering conditions for the query event, and the execution result, which can be expanded. Both the names of the query events and the event tracking can be customized. The filtering conditions for the query event are the JSON statements corresponding to the event tracking. The execution result includes success and failure. If a query event has no event tracking information, it is marked as failed. If a query event has event tracking data, it is marked as successful. The expand function allows you to view the event tracking information returned by the query event.

[0072] Further, the query event is executed to analyze whether the corresponding tracking event is abnormal. By executing the query event, the tracking information of the tracking event corresponding to the query event is obtained. By analyzing the tracking information, it is determined whether the tracking event is abnormal. For example, if a query event is marked as failed, it may be because the database of the third-party tool does not have a record of the tracking event corresponding to the query event being executed. In this case, the corresponding location can be found manually based on the configured tracking event name (such as browsing / clicking / exposure), and then the query event can be executed. If there is corresponding tracking data, the tracking event corresponding to the query event is normal. If there is no corresponding tracking data, the tracking event corresponding to the query event is abnormal. It is possible that the tracking code corresponding to the tracking event was overwritten during version iteration, and it is possible to detect whether the tracking event has been overwritten.

[0073] This invention stores query events in a local MySQL database, supporting batch calls. It eliminates the need to manually configure each query event in third-party tools, improving efficiency during regression testing and allowing the identification of data lacking event tracking at specific times, thus determining if code overwriting occurred due to version iterations. Furthermore, the system displays the retrieved event tracking information by calling the query interface of the third-party tools, supporting real-time data retrieval without waiting. This saves waiting time during testing, and the data returned by the system's query interface is more detailed, providing a clear view of the event's occurrence time and attributes, eliminating the need for configuring numerous metrics and facilitating the differentiation of various information.

[0074] Exemplary device

[0075] Figure 9 This is a schematic diagram of the structure of a device for real-time analysis of embedded point information provided in an exemplary embodiment of the present invention. Figure 9 As shown, the device includes a JSON conversion module 91 and a query module 92.

[0076] JSON conversion module: Configured to generate JSON statements corresponding to the event tracking points based on the parameters corresponding to the event tracking points and the format specifications of third-party tools;

[0077] Query module: Configured to determine the query statements supported by the third-party tool based on the JSON statement, and use the query statements to obtain the tracking information corresponding to the tracking event through the query interface of the third-party tool.

[0078] Exemplary electronic devices

[0079] Figure 10 This is the structure of an electronic device 10 provided in an exemplary embodiment of the present invention. The electronic device may be either or both of a first device and a second device, or a standalone device independent of them, which may communicate with the first device and the second device to receive acquired input signals from them. Figure 10 A block diagram of an electronic device according to an embodiment of the present disclosure is shown. Figure 10 As shown, the electronic device includes one or more processors 101 and memory 102.

[0080] The processor 101 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device to perform desired functions.

[0081] The memory 102 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 101 may execute the program instructions to implement the method for real-time analysis of embedded information of the software program in the various embodiments of this disclosure described above, and / or other desired functions. In one example, the electronic device may also include an input device 103 and an output device 104, which are interconnected via a bus system and / or other forms of connection mechanisms (not shown).

[0082] In addition, the input device 103 may also include, for example, a keyboard, a mouse, etc.

[0083] The output device 104 can output various information to the outside. The output device 104 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0084] Of course, for the sake of simplicity, Figure 10 Only some of the components of the electronic device relevant to this disclosure are shown, omitting components such as buses, input / output interfaces, etc. In addition, the electronic device may include any other suitable components depending on the specific application.

[0085] Exemplary computer program products and computer-readable storage media

[0086] In addition to the methods and devices described above, embodiments of this disclosure may also be computer program products, including computer program instructions that, when executed by a processor, cause the processor to perform the steps of the methods for real-time analysis of embedded information according to various embodiments of this disclosure as described in the "Exemplary Methods" section of this specification.

[0087] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this disclosure. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0088] Furthermore, embodiments of this disclosure may also be computer-readable storage media storing computer program instructions thereon, which, when executed by a processor, cause the processor to perform the steps in the methods for real-time analysis of embedded information according to various embodiments of this disclosure as described in the "Exemplary Methods" section above.

[0089] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0090] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0091] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For system embodiments, since they largely correspond to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0092] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0093] The methods and apparatus of this disclosure may be implemented in many ways. For example, they may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order of steps for the methods is for illustrative purposes only, and the steps of the methods of this disclosure are not limited to the order specifically described above unless otherwise specifically stated. Furthermore, in some embodiments, this disclosure may also be implemented as a program recorded on a recording medium, the program including machine-readable instructions for implementing the methods according to this disclosure. Thus, this disclosure also covers recording media storing programs for performing the methods according to this disclosure.

[0094] It should also be noted that in the apparatus, devices, and methods of this disclosure, the components or steps are decomposable and / or recombinable. Such decomposition and / or recombination should be considered equivalent to the present disclosure. The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0095] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

Claims

1. A method for real-time analysis of embedded data points, characterized in that, include: Based on the parameters corresponding to the event tracking and the format specifications of third-party tools, generate JSON statements corresponding to the event tracking. Based on the JSON statement, determine the query statements supported by the third-party tool, and use the query statements to obtain the tracking information corresponding to the tracking event through the query interface of the third-party tool; The step of generating the JSON statement corresponding to the event tracking point includes: Set the corresponding parameters of the event tracking in the third-party tool, and obtain the browser URL corresponding to the parameters generated in the third-party tool; Parse the fields in the browser URL, which incorporate the format specifications of the third-party tool, and generate a JSON statement corresponding to the event tracking based on the fields in the browser URL; The step of determining the query statements supported by the third-party tool based on the JSON statement, and using the query statements to obtain the tracking information corresponding to the tracking event through the query interface of the third-party tool, includes: The JSON statement is parsed using the Java language and converted into a query statement supported by the third-party tool. The query interface of the third-party tool is called to directly access the underlying data of the third-party tool, bypassing the query interface and data synchronization mechanism of the third-party tool. There is no need to wait for the buffering and refreshing of the third-party tool, and the tracking information corresponding to the tracking event is obtained from the underlying data. The tracking information corresponding to the tracking event can be directly obtained based on the query interface of the third-party tool, without the need to configure the viewing metrics of the tracking event.

2. The method as described in claim 1, characterized in that, The method further includes storing the query event corresponding to the query statement in a local database, wherein the query event includes the query statement corresponding to the query, the JSON statement corresponding to the query statement, and the queried data points.

3. The method as described in claim 2, characterized in that, The method further includes managing the query events through the local database, wherein the management includes at least adding, deleting, modifying, querying, reusing individually or in batches the query events.

4. The method as described in claim 2, characterized in that, Build an automation tool that supports the automatic generation of query statements and the management of query events corresponding to the query statements.

5. The method as described in claim 4, characterized in that, The automation tool includes a front-end framework, a back-end framework, and a database; the front-end framework is used to receive parameters corresponding to the tracking events input by the user, the back-end framework is used to receive parameters corresponding to the tracking events transmitted by the front-end framework, and access the query interface of the third-party tool; the database stores the query events.

6. The method as described in claim 2, characterized in that, Execute the query event and analyze whether the corresponding tracking event is abnormal.

7. A device for real-time analysis of embedded data points, characterized in that, include: JSON conversion module: Configured to generate JSON statements corresponding to the event tracking points based on the parameters corresponding to the event tracking points and the format specifications of third-party tools; Query module: Configured to determine the query statements supported by the third-party tool based on the JSON statement, and use the query statements to obtain the tracking information corresponding to the tracking event through the query interface of the third-party tool; The JSON conversion module is also used for: Set the corresponding parameters of the event tracking in the third-party tool, and obtain the browser URL corresponding to the parameters generated in the third-party tool; Parse the fields in the browser URL, which incorporate the format specifications of the third-party tool, and generate a JSON statement corresponding to the event tracking based on the fields in the browser URL; The query module is also used for: The JSON statement is parsed using the Java language and converted into a query statement supported by the third-party tool. The query interface of the third-party tool is called to directly access the underlying data of the third-party tool, bypassing the query interface and data synchronization mechanism of the third-party tool. There is no need to wait for the buffering and refreshing of the third-party tool, and the tracking information corresponding to the tracking event is obtained from the underlying data. The tracking information corresponding to the tracking event can be directly obtained based on the query interface of the third-party tool, without the need to configure the viewing metrics of the tracking event.

8. A computer-readable storage medium storing a plurality of instructions for being loaded by a processor and executing the method of any one of claims 1-6.

9. An electronic device, characterized in that, The electronic device includes: A processor is used to execute multiple instructions; Memory, used to store multiple instructions; The plurality of instructions are to be stored in the memory and loaded by the processor and executed as described in any one of claims 1-6.

Images