Data burying point and configuration method and system thereof, storage medium and terminal equipment
By obtaining and binding information from the target application's configuration file, the problem of strong code intrusion in existing technologies is solved, and a simplified data tracking process and update method are achieved.
Patent Information
- Application Number
- CN202310558161.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-16
- Publication Date
- 2024-11-22
AI Technical Summary
Existing data tracking methods require embedding a large amount of code into the application product's code, resulting in high costs and frequent code updates, and the update process is complex.
By obtaining the target application's configuration file, determining the node elements of the target application based on the information and location information of the elements to be tracked in the configuration file, and binding them with the tracking information, data collection is achieved, and data tracking is performed in a non-code-intrusive manner.
It simplifies the data tracking process, reduces the need for code modifications to the target application, and simplifies the data tracking update process.
Smart Images

Figure CN119003266A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of information processing technology, and in particular to a data embedding point and a configuration method, system, storage medium and terminal device thereof. Background Art
[0002] Data tracking is a commonly used data collection method. Data product managers, data operations, and data analysts set the pages and locations corresponding to the events of user behavior in the application based on business needs or product needs, and report the statistical data of these pages and locations through collection tools in order to obtain user operations and application usage, promote product optimization or guide operations, and provide important technical support for product operations.
[0003] The existing data embedding is mainly code embedding, which requires writing data embedding code into the code of the application product. This requires implanting a large amount of code in the code of the application product, and the embedding cost is high. In addition, if the data embedding settings need to be updated, the logic of the embedding code needs to be updated and the application product needs to be re-released, resulting in high costs. Summary of the invention
[0004] The embodiments of the present invention provide a data embedding method, a system, a storage medium and a terminal device for configuring the same, which simplify the process of embedding data for a target application.
[0005] An embodiment of the present invention provides a data burying method, including:
[0006] Obtain a configuration file corresponding to the target application, wherein the configuration file includes the tracking information of the elements to be tracked included in at least one application interface in the target application, wherein the tracking information includes information of the application interface to which the elements to be tracked belong, location information of the elements to be tracked in the application interface to which they belong, and information to be collected;
[0007] Determine the node element corresponding to the element to be embedded in the application interface of the target application according to the information and position information of the application interface to which the element to be embedded belongs;
[0008] The determined node element is bound to the burying point information of the element to be buried, so that in response to a triggering operation on the node element, data collection is performed according to the information to be collected in the corresponding burying point information.
[0009] Another aspect of the present invention provides a method for configuring a data embedding point, including:
[0010] Displaying a data embedding interface, wherein the data embedding interface includes an application interface loading control;
[0011] Based on the application interface of the target application imported by the triggering operation of the application interface loading control, displaying a selection interface of at least one application interface of the target application;
[0012] In response to a selection operation on a first application interface among the at least one application interface on the selection interface, displaying a first data burying interface of the first application interface;
[0013] In response to a preset operation on any node element in the first application interface triggered in the first data embedding interface, the any node element is used as a embedding element to be embedded, and a embedding input interface of the embedding element to be embedded is displayed;
[0014] The burying point information of the element to be buried is received from the burying point input interface, and a configuration file of the target application is generated according to the burying point information of the element to be buried, wherein the configuration file is used to bind the burying point information of the element to be buried with the corresponding node element.
[0015] Another aspect of the present invention provides a data tracking system, including:
[0016] A configuration file unit, used to obtain a configuration file corresponding to a target application, wherein the configuration file includes the burying point information of the element to be buried included in at least one application interface in the target application, wherein the burying point information includes the information of the application interface to which the element to be buried belongs, the position information of the element to be buried in the application interface to which it belongs, and the information to be collected;
[0017] A control determination unit, used to determine the node element corresponding to the element to be embedded in the application interface of the target application according to the information and position information of the application interface to which the element to be embedded belongs;
[0018] A binding unit is used to bind the determined node element with the burying point information of the element to be buried, so that when responding to the triggering operation of the node element, data collection is performed according to the information to be collected in the corresponding burying point information.
[0019] Another aspect of the present invention provides a data embedding configuration system, including:
[0020] A data embedding interface unit, used to display a data embedding interface, wherein the data embedding interface includes an application interface loading control;
[0021] A selection unit, configured to display a selection interface of at least one application interface of a target application based on the application interface of the target application imported by the triggering operation of the application interface loading control;
[0022] A selection response unit, configured to display a first data burying interface of the first application interface in response to a selection operation of the first application interface in the selection interface;
[0023] A point burying input unit, configured to respond to a preset operation on any node element in the first application interface triggered on the first data point burying interface, take the any node element as a point burying element to be buried, and display a point burying input interface for the point burying element to be buried;
[0024] A configuration generation unit is used to receive the burying point information of the element to be buried from the burying point input interface, and generate a configuration file of the target application according to the burying point information of the element to be buried, wherein the configuration file is used to bind the burying point information of the element to be buried with the corresponding node element.
[0025] On the other hand, an embodiment of the present invention further provides a computer-readable storage medium, which stores multiple computer programs. The computer programs are suitable for being loaded by a processor and executing the data burying method as described in one aspect of an embodiment of the present invention, or executing the data burying configuration method as described in another aspect of an embodiment of the present invention.
[0026] Another aspect of the embodiment of the present invention further provides a terminal device, including a processor and a memory;
[0027] The memory is used to store multiple computer programs, and the computer programs are used to be loaded by the processor and execute the data embedding method as described in one aspect of an embodiment of the present invention, or execute the data embedding configuration method as described in another aspect of an embodiment of the present invention; the processor is used to implement each computer program among the multiple computer programs.
[0028] It can be seen that in the data burying method of this embodiment, by obtaining the configuration file of the target application, and according to the information of the application interface to which the element to be buried belongs and the position information in the application interface to which it belongs included in the configuration file, the node element corresponding to the element to be buried in the application interface of the target application is determined, and then the determined node element is bound to the burying information of the element to be buried in the above configuration file, so that in response to the triggering operation of the node element, data collection is performed according to the information to be collected in the corresponding burying information. In this data burying process, it is only necessary to bind the information in the configuration file of the target application to the node element of the application interface of the target application, and it is not necessary to perform data burying through the method set in the running code of the target application. This adopts a non-code intrusive method, which simplifies the data burying process for the target application; and when it is necessary to update the data burying of the node element in the target application, it is only necessary to update the configuration file corresponding to the target, and re-bind it according to the updated configuration file, and the update of the data burying is also simplified accordingly. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0030] Figure 1 It is a schematic diagram of a scenario to which a data burying method provided by an embodiment of the present invention is applied;
[0031] Figure 2 It is a flow chart of a data burying method provided by an embodiment of the present invention;
[0032] Figure 3 is a flow chart of a method for generating a configuration file in an embodiment of the present invention;
[0033] Figure 4 It is a schematic diagram of a data burying method in an application embodiment of the present invention;
[0034] Figure 5a is a schematic diagram of a selection interface of an application interface in an application embodiment of the present invention;
[0035] Figure 5b It is a schematic diagram of a data point burying interface in an application embodiment of the present invention;
[0036] Figure 6 This is a schematic diagram of implementing data embedding points on multiple application terminals in an application embodiment of the present invention;
[0037] Figure 7 is a schematic diagram of performing data embedding in a game application in another application embodiment of the present invention;
[0038] Figure 8 is a schematic diagram of a method for configuring data burial points provided in another embodiment of the present invention;
[0039] Fig. 9 It is a logical structure diagram of a data embedding system provided by an embodiment of the present invention;
[0040] Fig.10 It is a logical structure diagram of a data embedding configuration system provided by an embodiment of the present invention;
[0041] Fig.11 It is a schematic diagram of the logical structure of a terminal device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0042] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0043] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0044] The embodiment of the present invention provides a data embedding method, which can be mainly applied to Figure 1 In the scenario shown, data embedding is performed on any node element in any application interface of the target application. The scenario includes: at least one application terminal 11, wherein:
[0045] Any application end 11 among at least one application end 11 is a client of the target application. Any application end 11 can display various application interfaces of the target application. Each application interface includes multiple node elements. Generally, data embedding can be performed for the following types of node elements among all node elements as needed: user operation controls, web page access links, exposure locations, locations with pop-up boxes, etc.
[0046] Among them, the user operation control can be a button that the user can operate to achieve a certain function, such as a plurality of task start buttons included in the user task interface. When the user triggers any task start button, the task execution interface of the corresponding task can be displayed to complete the corresponding task through the task execution interface. The position with a pop-up box means that when a certain position of the application interface is displayed on the application terminal, the target application will pop up another interface, and this position is the position with a pop-up box. The exposure position refers to a position where the application terminal loads and displays the application interface based on user operations (such as refresh, scroll down), and this position is the exposure position, such as a position in an application interface that exceeds the application terminal screen (such as the bottom position). Among them, the position with a pop-up box and the exposure position cannot be directly triggered by the user, while the user operation control and the web page access link can be directly triggered by the user.
[0047] In this embodiment, the application end 11 can obtain the configuration file corresponding to the target application at any time after starting the target application, parse the configuration file to obtain the embedding information of the element to be embedded included in at least one application interface in the target application, and determine the node element corresponding to the element to be embedded in the target application running by the application end 11 based on the embedding information of the element to be embedded, and then perform data embedding on the determined node element to collect relevant information of the determined node element, such as operation information on the node element.
[0048] After data embedding is performed on a determined node element, when a user triggers the node element, operation information related to the node element can be collected and reported, where the operation information may include but is not limited to the following information: the time and frequency of the triggering operation on the node element, whether the triggering operation on the node element is responded to successfully, and other information.
[0049] Furthermore, in the above scenario, the configuration terminal 12 of the data embedding point may also be included to generate configuration files for each application (including the target application), specifically:
[0050] The configuration terminal 12 of the data burying point is used to display the data burying point interface, load the application interface of the target application in the data burying point interface, and through the preset operation of the user in the application interface of the loaded target application, use certain node elements in certain application interfaces of the target application as elements to be buried, and input the burying point information of the elements to be buried into the data burying point interface; after receiving the burying point information of each element to be buried input by the user from the data burying point interface, a configuration file can be generated according to the burying point information. In this way, different configuration files can be generated for different target applications, and multiple different configuration files can also be generated for the same target application.
[0051] It should be noted that the above-mentioned application end 11 and the configuration end 12 of the data embedding point can be deployed to the same physical terminal. For example, the application end 11 can be a separate application installed on the physical terminal, or a small program in a main application of the physical terminal, or a web page displayed by the browser of the physical terminal, and the configuration end 12 of the data embedding point can be a web page displayed by the browser of the physical terminal, or a separate application in the physical terminal; the above-mentioned application end 11 and the configuration end 12 of the data embedding point can also be deployed on different physical terminals. The physical terminal can include but is not limited to any of the following devices: mobile phones, desktop computers, laptops, tablet computers, robot terminals, vehicle-mounted terminal devices, etc.
[0052] Furthermore, in order to implement the above-mentioned data embedding method on the application end 11, the above-mentioned scenario may also include: a data embedding plug-in end 13, which is used to generate a data embedding plug-in for the target application, and send the generated data embedding plug-in to each application end 11 respectively, and the data embedding plug-in is used to obtain the configuration file corresponding to the target application, parse the configuration file to obtain the embedding information of the element to be embedded included in at least one application interface in the target application, and determine the node element corresponding to the element to be embedded in the target application running on the application end 11 according to the embedding information of the element to be embedded, and then perform data embedding on the determined node element to collect the operation information of the corresponding node element.
[0053] Furthermore, in a specific application instance, when any application terminal 11 receives a data embedding plug-in, a user prompt can be given to prompt the user whether to choose to install the data embedding plug-in. If the user chooses to install the data embedding plug-in, the data embedding plug-in will be run; if the user chooses not to install the data embedding plug-in, the data embedding plug-in will not be run, that is, the data embedding operation will not be performed according to the configuration file.
[0054] The above-mentioned application end 11, data embedding configuration end 12 and data embedding plug-in end 13 can be connected through a network.
[0055] Specifically, Figure 2As shown, the application end 11 in this embodiment can implement data embedding through the following steps, including:
[0056] Step 101, obtain a configuration file corresponding to the target application, the configuration file includes the tracking information of the elements to be tracked included in at least one application interface in the target application, the tracking information includes the information of the application interface to which the elements to be tracked belong, the location information of the elements to be tracked in the application interface to which they belong, and the information to be collected.
[0057] It can be understood that the application end 11 can initiate the data tracking process of this embodiment at any time after starting the target application.
[0058] The configuration file obtained here may include the burying information of the elements to be buried included in the application interface of the target application, wherein the elements to be buried are at least one node element included in the application interface, and the burying information of each element to be buried may specifically include: the burying identifier of the element to be buried, the location information of the element to be buried in the application interface to which it belongs, such as coordinate information, and the attribute information of the burying element itself; information of the application interface to which the element to be buried belongs, such as the identifier and type of the application interface; and information to be collected, such as the event type, event name, additional business data corresponding to the element to be buried, and other information that needs to be collected and reported by the application end 11 based on the user operation on the burying element. Further, the burying information of the element to be buried may also include but is not limited to the following information: the platform and burying type (static or dynamic type) on which the application end 11 reports information based on the element to be buried, etc., wherein, if the element to be buried is a fixed user operation control, the burying type is a static type; if the element to be buried is dynamically and cyclically scrolled at a certain position in the application interface, the burying type is dynamic.
[0059] Among them, the burying point identifier in the burying point information can uniquely identify the burying point information of the element to be buried, so that each burying point identifier can correspond to a burying point element to be buried.
[0060] Specifically, the configuration file can be a file of any data format, such as json and other formats. Specifically, the configuration file can be generated by the configuration terminal 12 of the above-mentioned data embedding point, and the configuration file can also include information generated in the process of generating the configuration file, which can specifically include but is not limited to the following information: the identification of the target application, the description of the target application, the screen width and height of the application end to which the target application is applicable, the device pixel ratio of the application end to which the target application is applicable, the operating type, author, version, creation time, etc. applicable to the target application.
[0061] Step 102, determining the node element corresponding to the element to be embedded in the application interface of the target application based on the information and position information of the application interface to which the element to be embedded belongs.
[0062] The location information of the above-mentioned element to be embedded is mainly the coordinate information of the element to be embedded in a certain application interface. In this way, based on the coordinate information and the information of the application interface to which the element to be embedded belongs, it can be located at a specific position in a certain application interface of the target application. The node element at the specific position is the node element determined in this step.
[0063] In this embodiment, the node elements that require data embedding may include but are not limited to user operation controls, web page access links, exposure locations, locations with pop-up boxes, etc.
[0064] Step 103, binding the node element determined in the above step 102 with the burying point information of the element to be buried, so that in response to the triggering operation of the node element, data collection is performed according to the information to be collected in the corresponding burying point information.
[0065] Specifically, the burying point information of each element to be buried includes the burying point identifier of the element to be buried. When binding the node element and the burying point information, the node element can be bound to the corresponding burying point identifier, and when responding to the triggering operation of the node element, the response operation includes: collecting data according to the information to be collected in the burying point information corresponding to the burying point identifier. In this way, when the user triggers the node element, the application end 11 not only needs to execute the corresponding event according to the node element, but also needs to collect and report data based on the node element, and then through the binding between the node element and the burying point information, data burying is realized at the corresponding position of the node element.
[0066] It should be noted that in order to perform data embedding on the application end 11, in an actual application, it can be achieved by running a data embedding plug-in during the process of running the target application on the application end 11. In this way, before executing the above step 101, it is necessary to generate a data embedding plug-in for the target application through the data embedding plug-in end 13. The data embedding plug-in is used to execute the above steps of obtaining the configuration file corresponding to the target application, determining the node element corresponding to the element to be embedded in the target application, and binding the determined node element with the embedding information of the element to be embedded, that is, executing the above steps 101 to 103, and transmitting the generated data embedding plug-in to each application end 11.
[0067] After the application end 11 obtains the data embedding plug-in, it can inject the data embedding plug-in of the target application into the operation of the target application. In this way, during the process of the application end 11 running the target application, the data embedding plug-in can be run, and then by running the data embedding plug-in, data embedding can be achieved at certain node elements of a certain application interface of the target application.
[0068] Among them, since the target application can have multiple running types on the application end 11, for example, the target application runs on the application end 11 as a separate application, or runs as a web page displayed by the browser of the application end 11, or runs through a small program under a main application of the application end 11, etc., in a specific application, target applications under different running types will have different node elements during the running process. Therefore, each running type of target application can correspond to the configuration file under the running type. The application end 11 needs to determine the running type of the currently running target application, and then obtain the configuration file of the target application corresponding to the determined running type when obtaining the configuration file through the data tracking plug-in.
[0069] In other specific applications, if the target applications under different running types have the same node elements during the running process, the same configuration file can be generated for the target applications of any running type. When the application end 11 obtains the configuration file through the data embedding plug-in, it does not need to determine the running type of the target application, but can directly obtain the configuration file of the target application.
[0070] It should also be noted that the application end 11 can also unbind the bound node elements in any application interface. When executing the binding operation of this step 103, if a node element determined in the above step 102 is currently bound to a certain tracking point identifier, in one case, the tracking point identifier bound to the node element can be unbound first, and then the binding of step 103 can be performed for the tracking point information in the configuration file obtained in the above step 101. In this way, each node element in each application interface is bound to only one corresponding tracking point identifier to realize one type of data collection and reporting.
[0071] In another case, when executing the binding operation of step 103, if a node element is currently bound to a certain burying point identifier, in another case, it is not necessary to unbind the burying point identifier bound to the node element, but directly execute the binding of step 103 for the burying point information in the configuration file obtained in the above step 101. In this way, each node element in each application interface can be bound to multiple burying point identifiers, so as to realize multiple types of data collection and reporting under one node element.
[0072] It can be seen that in the data burying method of this embodiment, by obtaining the configuration file of the target application, and according to the information of the application interface to which the element to be buried belongs and the position information in the application interface to which it belongs included in the configuration file, the node element corresponding to the element to be buried in the application interface of the target application is determined, and then the determined node element is bound to the burying information of the element to be buried in the above configuration file, so that in response to the triggering operation of the node element, data collection is performed according to the information to be collected in the corresponding burying information. In this data burying process, it is only necessary to bind the information in the configuration file of the target application to the node element of the application interface of the target application, and it is not necessary to perform data burying through the method set in the running code of the target application. This adopts a non-code intrusive method, which simplifies the data burying process for the target application; and when it is necessary to update the data burying of the node element in the target application, it is only necessary to update the configuration file corresponding to the target, and re-bind it according to the updated configuration file, and the update of the data burying is also simplified accordingly.
[0073] In a specific embodiment, the configuration file obtained in the above step 101 can be mainly generated by the configuration terminal 12 of the data embedding point, such as Figure 3 As shown, when the configuration terminal 12 of the data embedding point generates a configuration file, it can be implemented specifically through the following steps:
[0074] Step 201, displaying the data embedding interface, which includes an application interface loading control.
[0075] It can be understood that the user can operate the configuration terminal 12 of the data embedding point so that the configuration terminal 12 of the data embedding point displays the data embedding point interface. The data embedding point interface may include an application interface loading control. In this way, the user triggers the application interface loading control, and the configuration terminal 12 of the data embedding point can display the application interface import interface, and import all application interfaces of any application (such as the target application) through the application selection import interface.
[0076] Step 202: Based on the application interface of the target application imported by the triggering operation of the application interface loading control, a selection interface of at least one application interface of the target application is displayed.
[0077] In this way, the user can select any application interface (such as the first application interface) in the selection interface, and the configuration terminal 12 of the data burying point can display the first data burying point interface of the first application interface. The first data burying point interface can include the first application interface, and the user can perform preset operations on each node element included in the first application interface to set corresponding burying point information.
[0078] Step 203, in response to a selection operation on a first application interface among at least one application interface in a selection interface, a first data burial point interface of the first application interface is displayed.
[0079] Step 204, in response to a preset operation on any node element in the first application interface triggered in the first data embedding interface, any node element is used as an element to be embedded, and a embedding input interface for the element to be embedded is displayed.
[0080] The tracking point input interface may include input boxes corresponding to multiple tracking point parameters. Users can enter the specific content of a corresponding tracking point parameter in each input box. These tracking point parameters may include but are not limited to the following types of parameters: information about the first application interface to which the node element belongs; attribute information of the node element itself, such as the location information of the node element in the first application interface; information to be collected under the node element, such as the event type and event name corresponding to the node element; reporting platform for the information to be collected; tracking point type, etc.
[0081] In this embodiment, at least one of the above-mentioned multiple burying point parameters can be set by automatic acquisition. Specifically, when the user performs a preset operation (such as clicking, etc.) on any node element in the first application interface in the first data burying point interface, the data burying point configuration terminal 12 can actively obtain the burying point information corresponding to the node element under at least one burying point parameter, and display the burying point information corresponding to at least one burying point parameter in the input box of the corresponding burying point parameter.
[0082] Some of the other tracking point parameters among the above-mentioned multiple tracking point parameters need to be manually selected and input by the user, such as a part of the information to be collected, the reporting platform of the information to be collected, the tracking point type and other tracking point parameters. The user can input the corresponding tracking point information through the input boxes of these tracking point parameters.
[0083] Step 205: receiving the burying point information of the element to be buried from the burying point input interface, and generating a configuration file of the target application according to the burying point information of the element to be buried.
[0084] Specifically, the configuration terminal 12 of the data burying point can generate a corresponding burying point identifier for each element to be buried, and associate the burying point identifier with the burying point information of the element to be buried, generate the burying point information of the associated element to be buried, and then store the burying point information of the associated element to be buried in a configuration file.
[0085] Furthermore, in addition to the tracking information of the above-mentioned elements to be tracked, at least one of the following information can also be stored in the configuration file: information of the target application, screen width and height of the application end to which the target application is applicable, device pixel ratio of the application end to which the target application is applicable, operating type applicable to the target application, author, version, creation time of the configuration file, etc.
[0086] It should be noted that, in a specific embodiment, before the configuration terminal 12 of the data embedding point executes the above step 201, the user can also operate the configuration terminal 12 of the data embedding point, and input the demand for data embedding through the configuration terminal 12 of the data embedding point, so that the above configuration file can be generated based on the demand for data embedding, specifically:
[0087] The configuration terminal 12 of the data burying point can first display the burying point demand input interface, which includes input interfaces for multiple burying point demands. The user can input the corresponding burying point demand in the input interface of each burying point demand. When the configuration terminal 12 of the data burying point receives the input information of each burying point demand from the input interface, it stores the information of each burying point demand.
[0088] Among them, the data tracking requirement information refers to the information that needs to be implemented when performing data tracking in the application interface of the target application, which may include but is not limited to the following information: information of the target application, information of specific node elements of the second application interface that need to perform data tracking in the target application, tracking identifiers of each specific node element, tracking type and information to be collected for each element to be tracked, etc.
[0089] Furthermore, during the process of generating a configuration file and executing the above step 204, the configuration terminal 12 of the data embedding point can directly search for the embedding point information corresponding to any node element under at least one embedding point parameter from the above-mentioned stored embedding point requirement information in response to a preset operation on any node element in the first application interface triggered in the first data embedding point interface, and display the searched embedding point information in the input box of the corresponding embedding point parameter.
[0090] If the tracking requirement information includes information on specific node elements included in the second application interface in the target application, then when executing the above step 202, the second application interface is displayed in a preset prompt method in the selection interface of at least one application interface, and if the user selects the second application interface in the selection interface, in response to the selection operation of the second application interface in the selection interface, the second data tracking interface of the second application interface is displayed, and the specific node elements in the second application interface are displayed in the second data tracking interface according to the preset prompt method.
[0091] Among them, the preset prompt method refers to a more eye-catching display method, such as displaying the second application interface and the name of the specific node elements it includes with specific symbols, such as "*", etc., so that the user can be prompted in an intuitive way that the tracking point information of the specific node elements in the second application interface must be set.
[0092] Furthermore, when the configuration terminal 12 of the data embedding generates the configuration file in the above step 205, the embedding identifier of each element to be embedded can be found from the embedding requirement information stored through the embedding requirement input interface, and then the embedding identifier is associated with the corresponding embedding information and stored in the configuration file. Part of the information in the embedding requirement information can also be stored in the configuration file, such as information of the target application.
[0093] The following is a specific application example to illustrate the data embedding method of the embodiment of the present invention. The data embedding method of this embodiment is mainly applied to Figure 1 In the scenario shown, Figure 4 As shown, it can mainly include the following parts:
[0094] (1) The data embedding point requirement information is stored through the configuration terminal 12 of the data embedding point.
[0095] Specifically, the configuration terminal 12 of the data burying point displays a burying point demand input interface, which includes input interfaces for multiple burying point demands. The user inputs the corresponding burying point demand into the input interface of each burying point demand, and stores the input burying point demand information when it is received from each input interface.
[0096] For example, as shown in Table 1 below, the input interface for tracking point requirements is mainly presented in a document format, and mainly includes the following input boxes for tracking point requirements: the end to which the target application belongs, the project to which it belongs, the application interface, the tracking point type, the tracking point name, the tracking point identifier, the extended reporting field, and the additional carrying field. Among them, the project to which it belongs is used to indicate the running type of the end to which the target application belongs, such as running in the form of a web page; the tracking point type may include clicks, topologies in exposure such as pop-ups, and visits (pv) and other types, among which clicks and visits in certain situations are static types, and visits in other situations are dynamic types; the tracking point name is used to indicate the operation of the node elements of the application interface in the target application for which the data tracking is performed, such as the click operation on the card in the budget center; the extended reporting field is used to indicate the information that needs to be collected and reported by the application end 11 after the data tracking is performed.
[0097]
[0098] Table 1
[0099] (2) Generate a configuration file through the configuration terminal 12 of the data embedding point.
[0100] Specifically, the configuration terminal 12 of the data tracking point can generate a configuration file of the target application according to the method of steps 201 to 205 above. Specifically:
[0101] The configuration terminal 12 of the data embedding point can first display the data embedding point interface, and import all application interfaces of a target application through the application interface loading control of the data embedding point interface, so that the configuration terminal 12 of the data embedding point will display the following Figure 5a The selection interface of the multiple application interfaces may specifically include the following application interface selection interfaces: home page, channel page 1, channel 2, download page, activity page 1 and activity page 2. When a user selects a channel page 1, a data embedding interface 1 of the channel page 1 may be displayed. The data embedding interface 1 includes input boxes corresponding to the channel page 1 and two embedding parameters (i.e., page name and page type) of the channel page 1. The user may enter embedding information of the corresponding embedding parameters in each input box. Among them, the node elements included in the channel page 1 are "receive" buttons corresponding to the four prizes.
[0102] When the user performs a preset operation on a node element in the data embedding interface 1, such as clicking a "receive" button 1 on the channel page 1, the configuration terminal 12 of the data embedding can display the following information: Figure 5b Another data tracking interface 2 of the channel page 1 is shown, and the data tracking interface 2 includes the channel page 1 and input boxes corresponding to the following multiple tracking parameters of the "take" button 1 in the channel page 1: page type (download page), reporting platform (tcss), belonging page (channel page 1), tracking type (static), click-reported parameters including event type (click), event English (Click "take" button), event Chinese (Click to take button) and event description.
[0103] Among them, for the event type, event English, event Chinese, page and page type, when the user clicks the "Receive" button 1, the data burying configuration terminal 12 can automatically obtain the burying information of the "Receive" button 1 under these burying parameters, and display the obtained burying information in the input box of the corresponding burying parameter; the data burying configuration terminal 12 will also obtain the coordinate information of the "Receive" button 1 in the channel page 1, and can also display the coordinate information in the data burying interface 2. The coordinate information is generally based on the coordinate of the top left corner of the channel page 1 as the origin (0, 0). For other burying parameters, such as burying type, event description and reporting platform, users need to enter the corresponding burying information in the input boxes corresponding to other burying parameters.
[0104] Furthermore, when the user clicks another "Receive" button 2 in the data embedding interface 2, the data embedding configuration terminal 12 can display another data embedding interface 3 of the channel page 1. The data embedding interface 3 is similar to the above-mentioned data embedding interface 2, including the channel page 1 and input boxes corresponding to multiple embedding parameters of the "Receive" button 2 in the channel page 1.
[0105] After the user inputs the relevant point-burying information through the input boxes of the point-burying parameters corresponding to the node elements included in the application interface of the target application, a "Generate" button may be included on the data point-burying interface. When the user clicks the Generate button, the data point-burying configuration terminal 12 will treat each node element as a point-burying element to be buried, and generate a configuration file based on the point-burying information of each point-burying element to be buried.
[0106] After the configuration file corresponding to the target application is generated, the configuration file can be stored in the cloud or directly sent to each application terminal 11.
[0107] It should be noted that, according to different operation types of the target application on the application end 11, the configuration end 12 of the data embedding point can generate corresponding different configuration files, or generate the same configuration file.
[0108] (3) Generate a data embedding plug-in through the data embedding plug-in terminal 13.
[0109] Specifically, the data embedding plug-in terminal 13 mainly generates a data embedding plug-in by code generation, and the data embedding plug-in is used to obtain the configuration file corresponding to the target application, determine the node element corresponding to the element to be embedded in the target application, and bind the determined node element with the embedding information of the element to be embedded. The data embedding plug-in can be a software development kit (SDK), etc.
[0110] After the data embedding plug-in is generated, the data embedding plug-in can be sent to the application end 11 of the target application. Figure 6 As shown, the data tracking plug-in can be sent to the application end 11 of the target application of various running types (such as web page type, mini-program or separate application, etc.), and the data tracking plug-in can be run on each application end 11, thereby realizing data tracking on multiple application ends 11.
[0111] (4) Data embedding is performed at the application end 11.
[0112] When the application end 11 starts the target application, if the data embedding plug-in of the target application sent by the data embedding plug-in end 13 is received, the data embedding plug-in is injected into the operation of the target application. In this way, the data embedding plug-in can be run during the operation of the target application. Specifically:
[0113] Obtain the running type of the target application currently running on the application end 11, obtain the configuration file corresponding to the running type, parse the configuration file to obtain the burying point information of each element to be buried, including: information of the application interface to which each element to be buried belongs, location information in the application interface to which it belongs, burying point identifier and information to be collected, etc.
[0114] Furthermore, based on the information and location information of the application interface to which the element to be buried belongs, the node element corresponding to the element to be buried in the application interface of the target application is determined, and then the determined node element is bound to the burying information of the element to be buried, so that when responding to the triggering operation of the node element, data is collected and reported according to the information to be collected in the corresponding burying information.
[0115] It can be seen that in this embodiment, the user can directly generate a configuration file for data tracking in the visual data tracking interface according to the tracking requirements, and then bind the tracking information of each element to be tracked in the configuration file to the corresponding node element in the target application, thereby realizing data tracking under the node element without the need for invasive operations on the code of the target application, thereby simplifying the implementation of data tracking.
[0116] The following is another specific application example to illustrate the data embedding method of the embodiment of the present invention. The data embedding method of this embodiment is mainly applied to Figure 1 In the scenario shown, the application end 11 is mainly a game application end, and the target application running on the game application end is a game application, such as Figure 7 As shown, it can mainly include the following parts:
[0117] (1) Generate a configuration file for a game application through the configuration terminal of the data embedding point.
[0118] Specifically, the configuration end of the data tracking point can generate a configuration file of the game application according to the method of steps 201 to 205 above. Specifically:
[0119] The configuration end of the data embedding can first display the data embedding interface, and import all the game application interfaces of a game application through the application interface loading control of the data embedding interface. In this way, the configuration end of the data embedding will display the selection interface of multiple game application interfaces under the game application. When the user selects a game application interface, a data embedding interface of the game application interface can be displayed. The data embedding interface includes the game application interface and input boxes corresponding to multiple embedding parameters of the game application interface (such as page name and page type, etc.). Users can enter the embedding information of the corresponding embedding parameters in each input box.
[0120] When the user performs a preset operation on a node element in the game application interface, such as clicking a button in the game application interface, the data tracking configuration end can display another data tracking interface of the game application interface. The other data tracking interface includes the game application interface and input boxes corresponding to the following multiple tracking parameters of the button in the game application interface: page type, reporting platform, page to which it belongs, tracking type, parameters reported by click including event type, event English, event Chinese and event description.
[0121] After the user inputs the relevant tracking point information through the input boxes of the tracking point parameters corresponding to the node elements included in the game application interface in the game application, a "Generate" button may be included on the data tracking point interface. When the user clicks the "Generate" button, the data tracking point configuration end will treat each node element as a tracking point element to be tracked, and generate a configuration file based on the tracking point information of each tracking point element to be tracked. This configuration file is the configuration file of the game application.
[0122] After generating the configuration file corresponding to the game application, the configuration file can be stored in the cloud or directly sent to each game application terminal.
[0123] (2) Generate a data embedding plug-in through the data embedding plug-in terminal.
[0124] Specifically, the data embedding plug-in mainly generates a data embedding plug-in by code generation. The data embedding plug-in is used to obtain the configuration file corresponding to the game application, determine the node element corresponding to the element to be embedded in the game application, and bind the determined node element with the embedding information of the element to be embedded. The data embedding plug-in can be a software development kit (SDK), etc.
[0125] After the data embedding plug-in is generated, the data embedding plug-in can be sent to the game application end of the game application, so that the data embedding plug-in is run on the game application end, thereby realizing data embedding on the game application end.
[0126] (3) Data collection on the game application side.
[0127] When the game application end starts the game application, if the data embedding plug-in of the game application sent by the data embedding plug-in end is received, the data embedding plug-in is injected into the running of the game application. In this way, the data embedding plug-in can be run during the running of the game application. Specifically:
[0128] Get the running type of the game application currently running on the game application end, get the configuration file corresponding to the running type, parse the configuration file to obtain the tracking information of each element to be tracked, including: information of the game application interface to which each element to be tracked belongs, location information on the game application interface to which it belongs, tracking identifier and information to be collected, etc.
[0129] The embodiment of the present invention also provides a method for configuring a data embedding point, which is mainly a method executed by the configuration terminal 12 of the data embedding point, such as Figure 8 As shown, the following steps may be specifically included:
[0130] Step 301, displaying the data embedding interface, which includes an application interface loading control.
[0131] It can be understood that the data tracking interface is a visual interface provided to users to set tracking information. The data tracking interface can include an application interface loading control, so that when the user triggers the application interface loading control, the application interface import interface can be displayed, and all application interfaces of any application (such as the target application) can be imported through the application selection import interface.
[0132] Step 302: Based on the application interface of the target application imported by the triggering operation of the application interface loading control, a selection interface of at least one application interface of the target application is displayed.
[0133] In this way, the user can select any application interface (such as the first application interface) in the selection interface, so that the first data burying point interface of the first application interface can be displayed to set corresponding burying point information for each node element included in the first application interface.
[0134] Step 303, in response to a selection operation on a first application interface among at least one application interface in a selection interface, a first data burial point interface of the first application interface is displayed.
[0135] Step 304, in response to a preset operation on any node element in the first application interface triggered in the first data embedding interface, any node element is used as an element to be embedded, and a embedding input interface for the element to be embedded is displayed.
[0136] The tracking point input interface may include input boxes corresponding to multiple tracking point parameters. Users can enter the specific content of a corresponding tracking point parameter in each input box. These tracking point parameters may include but are not limited to the following types of parameters: information about the first application interface to which the node element belongs; attribute information of the node element itself, such as the location information of the node element in the first application interface; information to be collected under the node element, such as the event type and event name corresponding to the node element; reporting platform for the information to be collected; tracking point type, etc.
[0137] In this embodiment, at least one of the above multiple burying point parameters can be set by automatic acquisition. Specifically, when the user performs a preset operation (such as clicking, etc.) on any node element in the first application interface in the first data burying point interface, the burying point information corresponding to the node element under at least one burying point parameter can be actively obtained, and the burying point information corresponding to at least one burying point parameter can be displayed in the input box of the corresponding burying point parameter. Other burying point parameters among the above multiple burying point parameters need to be manually selected and input by the user, such as a part of the information to be collected, the reporting platform of the information to be collected, the burying point type and other burying point parameters. The user can enter the corresponding burying point information through the input boxes of these burying point parameters.
[0138] Step 305, receiving the burying point information of the element to be buried from the burying point input interface, and generating a configuration file of the target application according to the burying point information of the element to be buried. The configuration file is used to bind the burying point information of the element to be buried with the corresponding node element to realize data burying operation under the node element.
[0139] Specifically, when generating a configuration file, a corresponding burying point identifier can be generated for each element to be buried, and the burying point identifier can be associated with the burying point information of the element to be buried, to generate the burying point information of the associated element to be buried, and then the burying point information of the associated element to be buried can be stored in a configuration file. Furthermore, in addition to the burying point information of each of the above-mentioned elements to be buried, at least one of the following information can also be stored in the configuration file: information of the target application, screen width and height of the application end to which the target application is applicable, device pixel ratio of the application end to which the target application is applicable, running type applicable to the target application, author, version, creation time of the configuration file, etc.
[0140] It should be noted that, in a specific embodiment, before executing the above step 301, the configuration terminal 12 of the data embedding point can also first display the embedding point demand input interface, which includes multiple embedding point demand input interfaces, and the user can input the corresponding embedding point demand in each embedding point demand input interface. When the configuration terminal 12 of the data embedding point receives the input of each embedding point demand information from the input interface, it stores each embedding point demand information. Among them, the embedding point demand information can specifically include but is not limited to the following information: information of the target application, information of specific node elements of the second application interface that needs to be embedded in the target application, embedding point identifiers of each specific node element, embedding point type and information to be collected of each embedding point element, etc.
[0141] In this way, when generating a configuration file, the tracking point identifiers of each element to be tracked can be found from the tracking point requirement information stored through the tracking point requirement input interface, and then the tracking point identifiers can be associated with the corresponding tracking point information and stored in the configuration file. Part of the tracking point requirement information can also be stored in the configuration file, such as information about the target application.
[0142] It can be seen that in this embodiment, through the visual data tracking interface, the tracking information under the node elements of the application interface in the target application can be intuitively set according to the product requirements of the target application.
[0143] The embodiment of the present invention also provides a data embedding system, the structural diagram of which is shown in FIG. Fig. 9 As shown, it may specifically include:
[0144] The configuration file unit 20 is used to obtain a configuration file corresponding to the target application, wherein the configuration file includes the burying information of the elements to be buried included in at least one application interface in the target application, wherein the burying information includes the information of the application interface to which the elements to be buried belong, the location information of the elements to be buried in the application interface to which they belong, and the information to be collected.
[0145] The control determination unit 21 is used to determine the node element corresponding to the element to be embedded in the application interface of the target application based on the information and position information of the application interface to which the element to be embedded belongs obtained by the configuration file unit 20.
[0146] The binding unit 22 is used to bind the node element determined by the control determination unit 21 with the burying point information of the element to be buried, so that when responding to the triggering operation of the node element, data collection is performed according to the corresponding information to be collected in the burying point information.
[0147] The binding unit 22 is specifically used to bind the node element to the burying point identifier, and the response to the triggering operation of the node element includes: collecting data according to the information to be collected in the burying point information corresponding to the burying point identifier.
[0148] Furthermore, before binding the node element with the burying point identifier, the binding unit 22 is also used to unbind the burying point identifier bound to the determined node element if the determined node element is currently bound to a burying point identifier.
[0149] In a specific embodiment, the above-mentioned configuration file unit 20 is specifically used to display a data burying point interface, which includes an application interface loading control; based on the application interface of the target application imported by the trigger operation of the application interface loading control, a selection interface of at least one application interface of the target application is displayed; in response to the selection operation of the first application interface in the at least one application interface in the selection interface, a first data burying point interface of the first application interface is displayed; in response to a preset operation on any node element in the first application interface triggered in the first data burying point interface, the any node element is used as a burying point element to be buried, and a burying point input interface of the burying point element to be buried is displayed; the burying point information of the burying point element to be buried is received from the burying point input interface, and the configuration file of the target application is generated according to the burying point information of the burying point element to be buried.
[0150] Among them, the burying point input interface includes input boxes for multiple burying point parameters; the configuration file unit 20 responds to a preset operation on any node element in the first application interface triggered by the first data burying point interface, obtains the burying point information corresponding to any node element under at least one burying point parameter, and displays the burying point information corresponding to the at least one burying point parameter in the input box of the corresponding burying point parameter.
[0151] Furthermore, before displaying the data burying point interface, the configuration file unit 20 is also used to display a burying point requirement input interface, and the burying point requirement input interface includes an input interface for multiple burying point requirements; when receiving each item of burying point requirement information input from the input interface, the each item of burying point requirement information is stored; when obtaining the burying point information corresponding to each of the node elements under at least one burying point parameter, it is specifically used to search for the burying point information corresponding to each of the node elements under at least one burying point parameter from the each item of burying point requirement information.
[0152] Among them, the tracking point requirement information includes information on specific node elements included in the second application interface of the target application; then in the selection interface of at least one application interface, the configuration file unit 20 will display the second application interface in a preset prompt manner; and in response to the selection operation of the second application interface in the selection interface, the second data tracking point interface of the second application interface is displayed, and the specific node elements in the second application interface are displayed in the second data tracking point interface according to the preset prompt manner.
[0153] Furthermore, when generating a configuration file, the configuration file unit 20 is specifically used to generate a corresponding burying point identifier for the element to be buried, associate the burying point identifier with the burying point information of the element to be buried, and generate the burying point information of the associated element to be buried; and store the burying point information of the associated element to be buried in a configuration file.
[0154] In another specific embodiment, when acquiring the configuration file corresponding to the target application, the configuration file unit 20 is specifically used to determine the running type of the target application; and acquire the configuration file of the target application corresponding to the running type.
[0155] Furthermore, the data tracking system may also include:
[0156] The plug-in unit 23 is used to obtain the data burying plug-in of the target application, and the data burying plug-in is used to execute the steps of obtaining the configuration file corresponding to the target application, determining the node element corresponding to the element to be buried in the target application, and binding the determined node element with the burying information of the element to be buried; injecting the data burying plug-in of the target application into the operation of the target application.
[0157] In this way, during the data tracking process, you only need to bind the information in the configuration file of the target application to the node elements of the application interface in the target application. There is no need to perform data tracking through methods set in the running code of the target application. This uses a non-code intrusive method to simplify the data tracking process for the target application. When the data tracking of the node elements in the target application needs to be updated, you only need to update the configuration file corresponding to the target and re-bind it according to the updated configuration file. The update of data tracking is also simplified accordingly.
[0158] The embodiment of the present invention also provides a data embedding configuration system, the structural diagram of which is as follows: Fig.10 As shown, it may specifically include:
[0159] The data embedding interface unit 30 is used to display a data embedding interface, and the data embedding interface includes an application interface loading control.
[0160] The selection unit 31 is used to display a selection interface of at least one application interface of the target application based on the application interface of the target application imported by the triggering operation of the application interface loading control displayed by the embedding interface unit 30.
[0161] The selection response unit 32 is used to display a first data burial point interface of the first application interface in response to a selection operation of the first application interface in the at least one application interface on the selection interface displayed by the selection unit 31.
[0162] The point-burying input unit 33 is used to respond to a preset operation on any node element in the first application interface triggered by the first data point-burying interface displayed in the selection response unit 32, take any node element as a point-burying element to be buried, and display the point-burying input interface of the point-burying element to be buried.
[0163] The configuration generation unit 34 is used to receive the burying point information of the element to be buried from the burying point input interface displayed by the burying point input unit 33, and generate a configuration file of the target application according to the burying point information of the element to be buried, wherein the configuration file is used to bind the burying point information of the element to be buried with the corresponding node element.
[0164] The configuration generation unit 34 is specifically used to generate a corresponding burying point identifier for the element to be buried, associate the burying point identifier with the burying point information of the element to be buried, and generate the burying point information of the associated element to be buried; and store the burying point information of the associated element to be buried in a configuration file.
[0165] Among them, the burying point input interface includes input boxes for multiple burying point parameters, and the burying point input unit 33 obtains the burying point information corresponding to any node element under at least one burying point parameter in response to a preset operation on any node element in the first application interface triggered in the first data burying point interface; and displays the burying point information corresponding to the at least one burying point parameter in the input box of the corresponding burying point parameter.
[0166] Furthermore, the data tracking configuration system of this embodiment may also include:
[0167] The demand unit 35 is used to display the burying point demand input interface, which includes an input interface for multiple burying point demands; when receiving the input of each item of burying point demand information from the input interface, the each item of burying point demand information is stored; then the above-mentioned burying point input unit 33 is specifically used to search for the burying point information corresponding to any node element under at least one burying point parameter from the each item of burying point demand information when obtaining the burying point information corresponding to any node element under at least one burying point parameter.
[0168] Among them, the tracking point requirement information includes information on specific node elements included in the second application interface of the target application; then the above-mentioned selection unit 31 displays the second application interface in the selection interface of at least one application interface according to a preset prompt method; when responding to the selection operation of the second application interface in the selection interface, the above-mentioned selection response unit 32 is also used to display the second data tracking point interface of the second application interface, and display the specific node elements in the second application interface in the second data tracking point interface according to the preset prompt method.
[0169] It can be seen that in this embodiment, through the visual data tracking interface, the tracking information under the node elements of the application interface in the target application can be intuitively set according to the product requirements of the target application.
[0170] The embodiment of the present invention further provides a terminal device, the structural diagram of which is shown in FIG. Fig.11 As shown, the terminal device may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPU) 40 (for example, one or more processors) and memory 41, and one or more storage media 42 (for example, one or more mass storage devices) storing application programs 421 or data 422. Among them, the memory 41 and the storage medium 42 can be short-term storage or permanent storage. The program stored in the storage medium 42 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the terminal device. Furthermore, the central processing unit 40 can be configured to communicate with the storage medium 42 to execute a series of instruction operations in the storage medium 42 on the terminal device.
[0171] Specifically, the application 421 stored in the storage medium 42 includes a data embedding application, and the program may include the configuration file unit 20, the control determination unit 21, the binding unit 22 and the plug-in unit 23 in the above-mentioned data embedding system, which will not be described in detail here. Furthermore, the central processor 40 can be configured to communicate with the storage medium 42 and execute a series of operations corresponding to the data embedding application stored in the storage medium 42 on the terminal device.
[0172] The terminal device may also include one or more power supplies 43, one or more wired or wireless network interfaces 44, one or more input and output interfaces 45, and / or one or more operating systems 423, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, FreeBSD TM, etc.
[0173] The steps performed by the data embedding system in the above method embodiment can be based on the Fig.11 The structure of the terminal device shown.
[0174] Furthermore, the embodiment of the invention also provides another terminal device, whose structure is as described above. Fig.11 The structure of the terminal device shown in the embodiment is:
[0175] Specifically, the application stored in the storage medium includes an application for configuring data embedding points, and the program may include the embedding point interface unit 30, the selection unit 31, the selection response unit 32, the embedding point input unit 33, the configuration generation unit 34 and the demand unit 35 in the above-mentioned data embedding point configuration system, which are not described in detail here. Furthermore, the central processing unit can be configured to communicate with the storage medium and execute a series of operations corresponding to the application for configuring data embedding points stored in the storage medium on the terminal device. And the steps performed by the data embedding point configuration system described in the above-mentioned method embodiment can be based on the terminal device of this embodiment.
[0176] Furthermore, on the other hand, an embodiment of the present invention also provides a computer-readable storage medium, which stores multiple computer programs, and the computer programs are suitable for being loaded by a processor and executing a data embedding method such as that executed by the above-mentioned data embedding system, or executing a data embedding configuration method such as that executed by the above-mentioned data embedding configuration system.
[0177] Another aspect of the embodiment of the present invention further provides a terminal device, including a processor and a memory;
[0178] The memory is used to store multiple computer programs, and the computer programs are used to be loaded by the processor and execute the data embedding method executed by the above-mentioned data embedding system, or execute the data embedding configuration method executed by the above-mentioned data embedding configuration system; the processor is used to implement each computer program among the multiple computer programs.
[0179] In addition, according to one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the data embedding method or the data embedding configuration method provided in the above-mentioned various optional implementations.
[0180] A person skilled in the art may understand that all or part of the steps in the various methods of the above-mentioned embodiments may be completed by instructing the relevant hardware through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.
[0181] The above is a detailed introduction to a data embedding point and its configuration method, system, storage medium and terminal device provided by an embodiment of the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.
Claims
1. A data embedding method, characterized in that: include: Obtain a configuration file corresponding to the target application, wherein the configuration file includes the tracking information of the elements to be tracked included in at least one application interface in the target application, wherein the tracking information includes information of the application interface to which the elements to be tracked belong, location information of the elements to be tracked in the application interface to which they belong, and information to be collected; Determine the node element corresponding to the element to be embedded in the application interface of the target application according to the information and position information of the application interface to which the element to be embedded belongs; The determined node element is bound to the burying point information of the element to be buried, so that in response to a triggering operation on the node element, data collection is performed according to the information to be collected in the corresponding burying point information.
2. The method according to claim 1, characterized in that The obtaining of the configuration file corresponding to the target application specifically includes: Displaying a data embedding interface, wherein the data embedding interface includes an application interface loading control; Based on the application interface of the target application imported by the triggering operation of the application interface loading control, displaying a selection interface of at least one application interface of the target application; In response to a selection operation on a first application interface among the at least one application interface on the selection interface, displaying a first data burying interface of the first application interface; In response to a preset operation on any node element in the first application interface triggered in the first data embedding interface, the any node element is used as a embedding element to be embedded, and a embedding input interface of the embedding element to be embedded is displayed; The burying point information of the element to be buried is received from the burying point input interface, and a configuration file of the target application is generated according to the burying point information of the element to be buried.
3. The method according to claim 2, characterized in that The embedding point input interface includes an input box for multiple embedding point parameters; In response to a preset operation on any node element in the first application interface triggered in the first data burying interface, acquiring burying information corresponding to each of the node elements under at least one burying parameter; The burying point information corresponding to at least one burying point parameter is displayed in the input box of the corresponding burying point parameter.
4. The method according to claim 3, characterized in that Before displaying the data embedding interface, the method further includes: Displaying a point-of-care demand input interface, wherein the point-of-care demand input interface includes input interfaces for multiple point-of-care demands; When receiving various items of tracking point demand information input from the input interface, storing the various items of tracking point demand information; Then the obtaining of the burying point information corresponding to any node element under at least one burying point parameter specifically includes: searching for the burying point information corresponding to any node element under at least one burying point parameter from the various burying point requirement information.
5. The method according to claim 4, characterized in that The tracking point requirement information includes information about specific node elements included in the second application interface of the target application; On the selection interface of the at least one application interface, displaying the second application interface in a preset prompting manner; In response to a selection operation on the second application interface in the selection interface, a second data embedding interface of the second application interface is displayed, and specific node elements in the second application interface are displayed in the second data embedding interface according to the preset prompt method.
6. The method according to claim 2, characterized in that The generating the configuration file of the target application according to the embedding information of the element to be embedded specifically includes: Generate a corresponding burying point identifier for the element to be buried, associate the burying point identifier with the burying point information of the element to be buried, and generate the associated burying point information of the element to be buried; The tracking point information of the associated elements to be tracked is stored in a configuration file.
7. The method according to claim 1, characterized in that The obtaining of the configuration file corresponding to the target application specifically includes: Determine the operation type of the target application; and obtain a configuration file of the target application corresponding to the operation type.
8. The method according to any one of claims 1 to 7, characterized in that The burying point information of the element to be buried includes a burying point identifier, and the step of binding the determined node element with the burying point information of the element to be buried specifically includes: The node element is bound to the burying point identifier, and the response to the triggering operation of the node element includes: data collection according to the information to be collected in the burying point information corresponding to the burying point identifier.
9. The method according to any one of claims 1 to 7, characterized in that: Before binding the determined node element with the embedding information of the element to be embedded, the method further includes: If the determined node element is currently bound to a burying point identifier, the burying point identifier bound to the determined node element is unbound.
10. The method according to any one of claims 1 to 7, characterized in that: Before obtaining the configuration file corresponding to the target application, the method further includes: Obtaining a data burying plug-in for the target application, the data burying plug-in is used to execute the steps of obtaining a configuration file corresponding to the target application, determining a node element corresponding to the element to be buried in the target application, and binding the determined node element to the burying information of the element to be buried; Inject the data embedding plug-in of the target application into the operation of the target application.
11. A method for configuring a data embedding point, characterized in that: include: Displaying a data embedding interface, wherein the data embedding interface includes an application interface loading control; Based on the application interface of the target application imported by the triggering operation of the application interface loading control, displaying a selection interface of at least one application interface of the target application; In response to a selection operation on a first application interface among the at least one application interface on the selection interface, displaying a first data burying interface of the first application interface; In response to a preset operation on any node element in the first application interface triggered in the first data embedding interface, the any node element is used as a embedding element to be embedded, and a embedding input interface of the embedding element to be embedded is displayed; The burying point information of the element to be buried is received from the burying point input interface, and a configuration file of the target application is generated according to the burying point information of the element to be buried, wherein the configuration file is used to bind the burying point information of the element to be buried with the corresponding node element.
12. A data embedding system, characterized in that: include: A configuration file unit, used to obtain a configuration file corresponding to a target application, wherein the configuration file includes the burying point information of the element to be buried included in at least one application interface in the target application, wherein the burying point information includes the information of the application interface to which the element to be buried belongs, the position information of the element to be buried in the application interface to which it belongs, and the information to be collected; A control determination unit, used to determine the node element corresponding to the element to be embedded in the application interface of the target application according to the information and position information of the application interface to which the element to be embedded belongs; A binding unit is used to bind the determined node element with the burying point information of the element to be buried, so that when responding to the triggering operation of the node element, data collection is performed according to the information to be collected in the corresponding burying point information.
13. A data embedding configuration system, characterized in that: include: A data embedding interface unit, used to display a data embedding interface, wherein the data embedding interface includes an application interface loading control; A selection unit, configured to display a selection interface of at least one application interface of a target application based on the application interface of the target application imported by the triggering operation of the application interface loading control; A selection response unit, configured to display a first data burying interface of the first application interface in response to a selection operation of the first application interface in the selection interface; A point burying input unit, configured to respond to a preset operation on any node element in the first application interface triggered on the first data point burying interface, take the any node element as a point burying element to be buried, and display a point burying input interface for the point burying element to be buried; A configuration generation unit is used to receive the burying point information of the element to be buried from the burying point input interface, and generate a configuration file of the target application according to the burying point information of the element to be buried, wherein the configuration file is used to bind the burying point information of the element to be buried with the corresponding node element.
14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores multiple computer programs, and the computer programs are suitable for being loaded by a processor and executing the data burying method as described in any one of claims 1 to 10, or executing the data burying configuration method as described in claim 11.
15. A terminal device, characterized in that: including a processor and a memory; The memory is used to store multiple computer programs, and the computer programs are used to be loaded by the processor and execute the data embedding method as described in any one of claims 1 to 10, or execute the data embedding configuration method as described in claim 11; the processor is used to implement each computer program among the multiple computer programs.
