Method, device, electronic device and computer-readable storage medium for processing buried points

Abstract

The present application provides a method, device, electronic device and computer-readable storage medium for processing buried points, and relates to the field of the Internet. The method includes: in response to a selection instruction for a target area in a target image, displaying at least one buried point type and at least one reported content; the target image is a page image of the current display page of the cloud application to be buried, and the target area is the area corresponding to any component in the current display page; in response to a buried point type selection instruction, displaying a target buried point type determined from at least one buried point type, and, in response to a reported content selection instruction, displaying a target reported content determined from at least one reported content; receiving a generation instruction, so that in response to the generation instruction, a buried point request is generated based on the target buried point type and the target reported content, and the buried point request is sent to the cloud, and the cloud performs buried points on any component based on the buried point request; the cloud application runs in the cloud. The present application improves the efficiency of setting buried points.

Description

Technical Field

[0001] The present application relates to the field of Internet technology. Specifically, the present application relates to a method, device, electronic device and computer-readable storage medium for processing buried points. Background Art

[0002] Android applications cannot make functional changes in the released version, including adding tracking points, modifying tracking points, etc. Because adding a tracking point will bring additional traffic costs, it is impossible for developers to add tracking points to the application indefinitely. This will bring a problem: if the developer misses a tracking point for a component on a page in the application, the data generated by this tracking point may affect the data analysis of the current application version (the source of business tracking point data, and this tracking point may be a key analysis node). At this time, the only way is to re-send the package, but re-sending the package is a very costly thing for both users and developers. Moreover, the excessive reliance on developers to add and modify tracking points will also lead to low efficiency in setting tracking points. Summary of the invention

[0003] The present application provides a method, device, electronic device and computer-readable storage medium for processing buried points, which can solve the problems of high cost and low efficiency in existing buried point settings. The technical solution is as follows:

[0004] On the one hand, a method for processing buried points is provided, the method comprising:

[0005] In response to a selection instruction for a target area in a target image, at least one type of buried point and at least one reported content are displayed; the target image is a page image of a current display page of a cloud application to be buried, and the target area is an area corresponding to any component in the current display page;

[0006] In response to the tracing type selection instruction, display the target tracing type determined from the at least one tracing type, and in response to the reporting content selection instruction, display the target reporting content determined from the at least one reporting content;

[0007] Receive a generation instruction to generate a tracking request based on the target tracking type and the target reported content in response to the generation instruction, and send the tracking request to the cloud, and the cloud performs tracking on any of the components based on the tracking request; the cloud application runs in the cloud.

[0008] On the other hand, a method for processing buried points is provided, the method comprising:

[0009] Acquire a target image of a cloud application to be embedded, and send the target image to a front end, so that the front end generates the embedding request based on the target image;

[0010] In response to the tracking request, obtaining a tracking configuration file;

[0011] Based on the tracking configuration file, the original component to be tracked is tracked to obtain the target component after tracking;

[0012] The tracking point configuration file is updated based on the target component to obtain an updated tracking point configuration file.

[0013] On the other hand, a method for processing buried points is provided, the method comprising:

[0014] When the target component is triggered, obtaining the component identifier of the target component;

[0015] When there is a match between the component identifier and at least one component identifier in the tracking configuration file, obtaining target reporting content corresponding to the match;

[0016] Report the target content at the target point.

[0017] Preferably, before the target component in the cloud application is triggered, the method further includes:

[0018] In response to the start instruction, a request for obtaining a tracking configuration file is sent to the cloud;

[0019] When the burying point configuration file is successfully obtained, the burying point configuration file is stored.

[0020] On the other hand, a device for processing buried points is provided, the device comprising:

[0021] A display module, for displaying at least one type of buried point and at least one reported content in response to a selection instruction for a target area in a target image; the target image is a page image of a current display page of a cloud application to be buried, and the target area is an area corresponding to any component in the current display page; and,

[0022] In response to the tracing type selection instruction, display the target tracing type determined from the at least one tracing type, and in response to the reporting content selection instruction, display the target reporting content determined from the at least one reporting content;

[0023] A receiving module, used for receiving a generating instruction;

[0024] A first generating module, configured to generate a tracking request based on the target tracking type and the target reporting content in response to the generating instruction;

[0025] The first sending module is used to send the tracking request to the cloud, and the cloud performs tracking on any of the components based on the tracking request; the cloud application runs in the cloud.

[0026] On the other hand, a device for processing buried points is provided, the device comprising:

[0027] A target image acquisition module is used to acquire the target image of the cloud application of the point to be buried;

[0028] A second sending module, used for sending the target image to the front end, so that the front end generates the burying point request based on the target image;

[0029] A tracking configuration file acquisition module, used to obtain a tracking configuration file in response to the tracking request;

[0030] A tracking processing module is used to track the original component to be tracked based on the tracking configuration file to obtain the target component after tracking;

[0031] An update module is used to update the tracking point configuration file based on the target component to obtain an updated tracking point configuration file.

[0032] Preferably, the tracking configuration file acquisition module includes:

[0033] The parsing submodule is used to parse the tracking request to obtain tracking configuration data;

[0034] The serialization submodule is used to serialize the tracking configuration data to obtain the tracking configuration file.

[0035] Preferably, the tracking point configuration file includes a target tracking point type and a target reporting content;

[0036] The buried point processing module includes:

[0037] A replacement submodule, used to replace the original component with a target component having the target burial point type;

[0038] The first adding submodule is used to add the target reporting content to the target attribute information of the target component to obtain the target component after the embedding point.

[0039] Preferably, the buried point processing module includes:

[0040] The original attribute information acquisition submodule is used to acquire the original attribute information of the original component;

[0041] The second adding submodule is used to add the target reporting content to the original attribute information to obtain the target component after the embedding point.

[0042] Preferably, the update module includes:

[0043] A first processing submodule is used to obtain a component identifier of the target component and establish a first association relationship between the component identifier and a target tracking point type and a target reporting content;

[0044] The second processing submodule is used to add the component identifier and the first association relationship to the tracking point configuration file to obtain the updated tracking point configuration file.

[0045] Preferably, it also includes:

[0046] The second generating submodule is used to establish a second association relationship between the updated tracking configuration file and the user identifier.

[0047] Preferably, it also includes:

[0048] A user identification acquisition module, configured to respond to a request for obtaining a tracing configuration file from a cloud application and obtain a user identification from the request;

[0049] A determination module, configured to determine a target tracking configuration file based on the second association relationship;

[0050] The third sending module is used to feed back the target burying point configuration file to the cloud application, so that when the target component in the cloud application is triggered, the burying point reporting is performed based on the target burying point configuration file.

[0051] Preferably, the target image acquisition module is specifically used for:

[0052] The page image of the currently displayed page of the cloud application is captured based on a preset frequency to obtain the target image.

[0053] On the other hand, a device for processing buried points is provided, the device comprising:

[0054] A component identification acquisition module, used for acquiring the component identification of the target component when the target component is triggered;

[0055] A target reporting content acquisition module, used for acquiring target reporting content corresponding to a matching item when a matching item exists between the component identifier and at least one component identifier in the tracking configuration file;

[0056] The reporting module is used to report the target reporting content.

[0057] Preferably, it also includes:

[0058] A fourth sending module is used to send a request for obtaining a tracking configuration file to the cloud in response to a start instruction before the target component in the cloud application is triggered;

[0059] A storage module is used to store the burying point configuration file when the burying point configuration file is successfully obtained.

[0060] In another aspect, an electronic device is provided, the electronic device comprising:

[0061] processor, memory, and bus;

[0062] The bus is used to connect the processor and the memory;

[0063] The memory is used to store operation instructions;

[0064] The processor is used to call the operation instruction, and the executable instruction enables the processor to perform the operation corresponding to the processing method of the buried point shown in the first aspect, the second aspect, and the third aspect of the present application.

[0065] On the other hand, a computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the method for processing buried points shown in the first, second, and third aspects of the present application is implemented.

[0066] The beneficial effects of the technical solution provided by this application are:

[0067] In an embodiment of the present invention, an application client for setting displays at least one burying point type and at least one reporting content in response to a selection instruction for a target area in a target image; the target image is a page image of a currently displayed page of a cloud application to be buried, and the target area is an area corresponding to any component in the currently displayed page, and then in response to a burying point type selection instruction, a target burying point type determined from the at least one burying point type is displayed, and in response to a reporting content selection instruction, a target reporting content determined from the at least one reporting content is displayed, and when a generation instruction is received, a burying point request is generated based on the target burying point type and the target reporting content in response to the generation instruction, and the burying point request is sent to the cloud, and the cloud burys any one of the components based on the burying point request; the cloud application runs in the cloud. In this way, even personnel who do not have R&D capabilities can set tracking points for any component in the cloud application through the above-mentioned configuration method in the application client. This not only liberates R&D productivity and realizes the principle of "whoever needs it, sets it", so that anyone can set tracking points, thereby greatly reducing the threshold for setting tracking points. It also solves the problem of the need to re-send packages when setting tracking points in the prior art, greatly improving the efficiency of setting tracking points. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0069] Figure 1 A schematic diagram of an application environment of a method for processing a buried point provided by an embodiment of the present application;

[0070] Figure 2 A flowchart of a method for processing a buried point provided in one embodiment of the present application;

[0071] Figure 3A-3B This is a schematic diagram of the settings page of the application client for this application;

[0072] Figure 4 A flowchart of a method for processing a buried point provided in another embodiment of the present application;

[0073] Figure 5 A flowchart of a method for processing a buried point provided in another embodiment of the present application;

[0074] Figure 6 A structural diagram of a method for processing buried points provided in another embodiment of the present application;

[0075] Figure 7 A schematic diagram of the structure of a buried point processing device provided in one embodiment of the present application;

[0076] Figure 8 A schematic diagram of the structure of a buried point processing device provided in another embodiment of the present application;

[0077] Fig. 9 A schematic diagram of the structure of a buried point processing device provided in another embodiment of the present application;

[0078] Fig.10 A schematic diagram of the structure of an electronic device for processing buried points provided in accordance with another embodiment of the present application. DETAILED DESCRIPTION

[0079] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present invention.

[0080] It will be understood by those skilled in the art that, unless expressly stated, the singular forms "one", "said", and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. It should be understood that when we refer to an element as being "connected" or "coupled" to another element, it may be directly connected or coupled to the other element, or there may be an intermediate element. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.

[0081] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0082] The method, device, electronic device and computer-readable storage medium for processing buried points provided in this application are intended to solve the above-mentioned technical problems in the prior art.

[0083] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0084] The embodiment of the present invention provides an application environment of a method for processing a buried point, see Figure 1 , the application environment includes: a first device 101, a second device 102 and a cloud 103. The first device 101 and the cloud 103 are connected via a network, and the second device 102 and the cloud 103 are also connected via a network. Among them, the first device 101 is a front end, which can be a device with an application client installed for setting a tracking point for a cloud application, and the cloud application runs in the cloud 103; the second device 102 is an access device, which can be a terminal for accessing the cloud application, and the terminal can have the following characteristics:

[0085] (1) In terms of hardware system, the device has a central processing unit, memory, input components and output components, that is, the device is often a microcomputer device with communication function. In addition, it can also have multiple input methods, such as keyboard, mouse, touch screen, microphone and camera, and the input can be adjusted as needed. At the same time, the device often has multiple output methods, such as receiver, display screen, etc., which can also be adjusted as needed;

[0086] (2) In terms of software system, the device must have an operating system, such as Windows Mobile, Symbian, Palm, Android, iOS, etc. At the same time, these operating systems are becoming more and more open, and personalized applications developed based on these open operating system platforms are emerging in an endless stream, such as address books, calendars, notepads, calculators, and various games, which greatly meet the needs of personalized users;

[0087] (3) In terms of communication capabilities, the device has flexible access methods and high-bandwidth communication performance, and can automatically adjust the selected communication method according to the selected service and the environment, so as to facilitate user use. The device should support 5G SA (Stand Alone independent networking) access to ensure that the device side supports network slicing, not only voice services, but also a variety of wireless data services;

[0088] (4) In terms of functional use, the equipment pays more attention to humanization, personalization and multi-functionality. With the development of computer technology, the equipment has moved from a "device-centric" model to a "people-centric" model, integrating embedded computing, control technology, artificial intelligence technology and biometric authentication technology, fully reflecting the people-oriented purpose. Due to the development of software technology, the equipment can adjust the settings according to personal needs and become more personalized. At the same time, the equipment itself integrates a lot of software and hardware, and its functions are becoming more and more powerful.

[0089] In the first device (i.e., the front end) of the above application environment, a method for processing buried points can be executed, such as Figure 2 As shown, the method includes:

[0090] Step S201, in response to a selection instruction for a target area in a target image, display at least one type of buried point and at least one reported content; the target image is a page image of a current display page of a cloud application to be buried, and the target area is an area corresponding to any component in the current display page;

[0091] Specifically, an application client for setting tracking points for cloud applications can be installed in the front end. When the operator uses the application client to set tracking points, when the application client receives a selection instruction initiated by the operator for a target area in a target image, the setting page of the application client is displayed. Figure 3A shown.

[0092] 301 is the target image, which is the page image of the currently displayed page when the cloud application to be embedded is running, that is, the page currently seen by the user when the cloud application is running.

[0093] 302 is a configurable tracking type, which includes but is not limited to: exposure reporting and click reporting. Among them, exposure reporting is a passive trigger. For example, when the cloud application is running, the page shown in 301 is displayed. Assuming that the tracking type of the entire page is exposure reporting, then when the cloud application displays the page, the exposure reporting is triggered, and the preset reporting content can be reported. Click reporting is an active trigger. For example, when the cloud application is running, the page shown in 301 is displayed. Assuming that "Confirm Payment" is a click reporting, then when the cloud application is running, when the user (non-operating personnel) using the cloud application clicks Confirm Payment, it triggers click reporting, and the preset reporting content can be reported.

[0094] 303 is the configurable reporting content, which includes but is not limited to: text content and custom content. Among them, the text content can be unified content of a certain tracking point type. For example, the exposure report can be uniformly set to "display the tracking point processing page", so when the cloud application is running, when the exposure report is triggered, the cloud application reports "display the tracking point processing page", and the click report can be uniformly set to "click the tracking point processing button", so when the cloud application is running, when the click report is triggered, the cloud application reports "click the tracking point processing button"; the custom content can be personalized for the target area. For example, assuming that the tracking point type is set to "click report" in 301, and the custom content is set to "12345", then when the cloud application is running, the user clicks "confirm payment", triggering the click report, and the report content of the cloud application is "12345".

[0095] Furthermore, the target area is an area corresponding to any component in the current display page. For example, when the cloud application is actually running, "Confirm Payment" corresponds to a component, and in 301, the area corresponding to "Confirm Payment" is the target area.

[0096] Step S202: In response to the burying point type selection instruction, display a target burying point type determined from at least one burying point type, and in response to the reporting content selection instruction, display a target reporting content determined from at least one reporting content;

[0097] Specifically, when the application client receives a tracking point type selection instruction initiated by the operator, the target tracking point type selected from at least one tracking point type can be displayed in the application client, and when the reporting content selection instruction is received, the target reporting content selected from at least one reporting content can be displayed in the application client, such as Figure 3B shown.

[0098] Step S203, receiving a generation instruction, so as to generate a tracking request based on the target tracking type and the target reporting content in response to the generation instruction, and send the tracking request to the cloud, and the cloud performs tracking on any component based on the tracking request; the cloud application runs in the cloud.

[0099] Specifically, the settings page of the application client also has a button for generating tracking points, such as Figure 3A In the "Confirm" button, when the operator clicks the button, the application client responds to the generation instruction and generates a tracking request based on the target tracking type and target reporting content, and sends the tracking request to the cloud. The cloud can track the corresponding components in the cloud application based on the tracking request. For example, when the operator clicks Figure 3A The application client generates a tracking request and sends the tracking request to the cloud. The cloud then tracks the "Confirm Payment" in 301 based on the tracking request.

[0100] It should be noted that in the embodiment of the present invention, the application client displays the page image currently displayed by the cloud application during operation, not the page, that is, the operator cannot interact with the page image. Figure 3A 301 in the figure is an image, and the operator clicking "Confirm Payment" does not actually perform the payment operation. Of course, in addition to the operator, the personnel who set the embedding point can also be other personnel who manage the cloud application. In actual application, it can be adjusted according to actual needs, and the embodiment of the present invention does not limit this.

[0101] In an embodiment of the present invention, the application client for setting displays at least one type of tracking point and at least one reported content in response to a selection instruction for a target area in a target image; the target image is a page image of the current display page of the cloud application to be tracked, and the target area is an area corresponding to any component in the current display page, and then in response to the tracking point type selection instruction, the target tracking point type determined from at least one tracking point type is displayed, and in response to the reported content selection instruction, the target reported content determined from at least one reported content is displayed, and when a generation instruction is received, a tracking point request is generated based on the target tracking point type and the target reported content in response to the generation instruction, and the tracking point request is sent to the cloud, and the cloud performs tracking on any component based on the tracking point request; the cloud application runs in the cloud. In this way, even personnel who do not have R&D capabilities can set tracking points for any component in the cloud application in the application client through the above-mentioned configuration method, which not only liberates R&D productivity and realizes "who needs, who sets", so that any personnel can set tracking points, thereby greatly reducing the threshold for setting tracking points, but also solves the problem of needing to re-send packages in the prior art for setting tracking points, greatly improving the efficiency of setting tracking points.

[0102] In the cloud of the above application environment, a method for processing tracking points can be executed, such as Figure 4 As shown, the method includes:

[0103] Step S401, obtaining a target image of a cloud application to be buried, and sending the target image to a front end, so that the front end generates a burying request based on the target image;

[0104] When the operator initiates an instruction to start the cloud application to be buried in the application client, the instruction is sent to the cloud through the front end. The cloud starts the cloud application to be buried, then obtains the target image of the cloud application, and sends the target image to the front end, so that the application client in the front end generates a burial request based on the target image. The process of the application client generating the burial request can refer to steps S201 to S203, which will not be repeated here.

[0105] In a preferred embodiment of the present invention, obtaining a target image of a cloud application of a point to be buried includes:

[0106] The page image of the current display page of the cloud application is captured based on a preset frequency to obtain the target image.

[0107] Specifically, a virtual machine is set up in the cloud, and the cloud application runs in the virtual machine. When the cloud receives the startup instruction, it starts the cloud application in the virtual machine, establishes a communication channel with the front end through a long connection, and then captures the page image of the current display page of the cloud application based on a preset frequency to obtain the target image.

[0108] Step S402, in response to the tracking request, obtaining a tracking configuration file;

[0109] After receiving the tracking request, the cloud parses the tracking request to obtain the tracking configuration data, and then serializes the tracking configuration data to obtain the tracking configuration file. The tracking configuration file includes but is not limited to the target tracking type and target reporting content, that is, the target tracking type and target reporting content set by the operator in the front end.

[0110] Serialization is the process of converting the state information of an object into a form that can be stored or transmitted. During serialization, the object writes its current state to a temporary or persistent storage area. Later, the object can be recreated by reading or deserializing the state of the object from the storage area. Applied to the embodiment of the present invention, the data parsed from the buried point request is a memory object. To persist the memory object as a file object, serialization is required. Without serialization, it cannot be stored as a file.

[0111] Step S403, burying the original component to be buried based on the burying configuration file to obtain the target component after burying;

[0112] After obtaining the tracking configuration file, you can track the original component to be tracked based on the tracking configuration file to obtain the target component after tracking. The original component to be tracked is the component corresponding to the target area determined by the operator in the front end, for example Figure 3A In the shown 301, the component corresponding to the "Confirm Payment" area is the original component to be buried.

[0113] There are two ways to track points. One is to replace the original components of the system with components with reporting functions.

[0114] In a preferred embodiment of the present invention, burying the original component to be buried based on the burying configuration file to obtain the target component after burying includes:

[0115] Replace the original component with the target component of the target embedding type;

[0116] Add the target reporting content to the target attribute information of the target component to obtain the target component after the tracking point is obtained.

[0117] Specifically, in the embodiment of the present invention, the component can report the tracking point when it is triggered, but under normal circumstances, the original component of the system cannot report the tracking point. In response to this situation, the embodiment of the present invention replaces the original component of the system with a target component with "reporting content". Of course, in addition to having "reporting content", the target component also has a target tracking point type, that is, the target component has preset the triggered target tracking point type and the reporting content that needs to be reported after being triggered.

[0118] The relationship between the target component and the original component of the system is an inheritance relationship. That is, the target component inherits all the capabilities of the original component and also has the ability to report points.

[0119] Furthermore, both the original component and the target component have corresponding attribute information. Since the target component and the original component have an inheritance relationship, the target component, in addition to all the attribute information of the original component, also has an attribute information that the original component does not have - the reported content. Therefore, after the target component is used to replace the original component, the content that needs to be reported (that is, the target reported content) can be added to the "reported content" to obtain the target component after the embedding. In other words, the "reported content" is a parameter in the attribute information of the target component, and the "target reported content" is the parameter value of this parameter.

[0120] For example, the original attribute information of the original component Button corresponding to "Confirm Payment" is as follows:

[0121] <Button

[0122] android:id="@+id / appinit_continuebtn"

[0123] android:textSize="@dimen / wx54sp"

[0124] android:textColor="#FFFFFF"

[0125] android:background="@drawable / appinit_continue_bg"

[0126] android:text="Confirm payment"

[0127] android:layout_marginTop="@dimen / wx40dp"

[0128] android:layout_width="@dimen / wx455dp"

[0129] android:layout_height="@dimen / wx160dp"

[0130] android:layout_marginBottom="@dimen / wx250dp"

[0131] app:layout_constraintBottom_toBottomOf="parent"

[0132] app:layout_constraintLeft_toLeftOf="parent"

[0133] app:layout_constraintRight_toRightOf="parent" / >.

[0134] The Button does not have "reporting content", so it cannot be used for tracking reporting. In order to allow the original component Button to report tracking, you can preset a target component ReportButton. ReportButton inherits all the capabilities of Button and also adds a target attribute information: report:report_data. Then replace the Button with ReportButton. The target attribute information of ReportButton is as follows:

[0135] <ReportButton

[0136] android:id="@+id / appinit_continuebtn"

[0137] report:report_data = "Clicked the confirm payment button"

[0138] android:textSize="@dimen / wx54sp"

[0139] android:textColor="#FFFFFF"

[0140] android:background="@drawable / appinit_continue_bg"

[0141] android:text="Confirm payment"

[0142] android:layout_marginTop="@dimen / wx40dp"

[0143] android:layout_width="@dimen / wx455dp"

[0144] android:layout_height="@dimen / wx160dp"

[0145] android:layout_marginBottom="@dimen / wx250dp"

[0146] app:layout_constraintBottom_toBottomOf="parent"

[0147] app:layout_constraintLeft_toLeftOf="parent"

[0148] app:layout_constraintRight_toRightOf="parent" / >.

[0149] Among them, "report:report_data" is the "report content", and "'Clicked the confirmation payment button'" is the parameter value of the "report content".

[0150] In actual applications, multiple target components with reporting capabilities can be preset, and the required target components can be selected when setting the tracking points; the target components can also be set when setting the tracking points, and used immediately after the setting is completed; the target components can also be set in other ways. In actual applications, adjustments can be made according to actual needs, and the embodiments of the present invention are not limited to this.

[0151] Another way to track points is to add new reporting content to the property information of system components.

[0152] In a preferred embodiment of the present invention, burying the original component to be buried based on the burying configuration file to obtain the target component after burying includes:

[0153] Get the original attribute information of the original component;

[0154] Add the target reporting content to the original attribute information to obtain the target component after the tracking point.

[0155] Specifically, since the original component of the system itself has attribute information (that is, original attribute information), it is also possible to obtain the original attribute information of the original component, and then add the target reporting content to the original attribute information to obtain the target component after the embedding.

[0156] For example, first obtain the original attribute information of Button, and then add "report:report_data = 'Clicked the confirmation payment button'" to the original attribute information, so as to obtain a Button with reporting capability. The original attribute information of Button is the same as the original attribute information mentioned above, so it will not be repeated here; the modified original attribute information is substantially the same as the target attribute information mentioned above, so it will not be repeated here.

[0157] Step S404, updating the tracking configuration file based on the target component to obtain an updated tracking configuration file;

[0158] Specifically, after obtaining the target component, the component identifier of the target component can be obtained. Specifically, the component identifier can be generated based on the preset tracking point rules, where the tracking point rules can be: Pagename / ContainerName / ViewPath / BehaviorViewName / Id. Then establish a first association relationship between the component identifier and the target tracking point type and the target reported content, so that the component identifier, the target tracking point type, and the target reported content are one-to-one corresponding to each other. Then add the component identifier and the first association relationship to the tracking point configuration file to obtain an updated tracking point configuration file.

[0159] Step S405, establishing a second association relationship between the updated tracking configuration file and the user identifier;

[0160] Among them, the user identifier can be a merchant number. In actual applications, each user has a one-to-one corresponding merchant number, each merchant number has a one-to-one corresponding configuration file path in the cloud, each merchant number corresponds to a large number of hardware devices, and each hardware device can obtain the burying point configuration file from the cloud when starting the cloud application. Therefore, after obtaining the updated burying point configuration file, a second association relationship between the updated burying point configuration file and the user identifier can be established. Specifically, the cloud stores the updated burying point configuration file to a certain path, and then writes the path to the configuration file path corresponding to the merchant number. In this way, when a request to obtain the burying point configuration file from the cloud application is received, the updated burying point configuration file can be sent to the cloud application.

[0161] Step S406, in response to the request for obtaining the tracking configuration file of the cloud application, obtaining the user identifier from the request for obtaining the tracking configuration file;

[0162] Specifically, each time the cloud application is started, it can send a request to the cloud for obtaining a tracking configuration file, and the request includes a user ID. When the cloud receives the request for obtaining a tracking configuration file, it can obtain the user ID from the request.

[0163] Step S407, determine the target burying point configuration file based on the second association relationship, and feed the target burying point configuration file back to the cloud application, so that when the target component in the cloud application is triggered, the burying point is reported based on the target burying point configuration file.

[0164] After obtaining the user identifier, the target burying point configuration file corresponding to the user identifier can be determined based on the second association relationship, and then the target burying point configuration file is fed back to the cloud application. In this way, when the target component in the cloud application is triggered, the burying point report can be performed based on the target reporting content in the target burying point configuration file.

[0165] Among them, when the cloud determines the target burying point configuration file, it can first query whether there is a path to the target burying point configuration file under the configuration file path corresponding to the user identifier. If so, it obtains the target burying point configuration file from the path and feeds back the target burying point configuration file to the cloud application; if not, it means that the user identifier does not have a target burying point configuration file.

[0166] Further, when the path of the burying configuration file is found under the configuration file path corresponding to the user identifier, the path can also be sent to the cloud application, and the cloud application can obtain the target burying configuration file from the path. In actual applications, it can be set according to actual needs, and the embodiment of the present invention does not limit this.

[0167] In an embodiment of the present invention, the cloud obtains the target image of the cloud application to be buried, and sends the target image to the front end, so that the front end generates a burying request based on the target image; in response to the burying request, a burying configuration file is obtained, and then the original component to be buried is buried based on the burying configuration file to obtain the target component after burying, and then the burying configuration file is updated based on the target component to obtain the updated burying configuration file. In this way, even personnel who do not have R&D capabilities can configure the burying in the front end, and the cloud generates the final burying configuration file based on the configuration, which not only liberates R&D productivity and realizes "whoever needs, whoever sets", so that any person can set the burying, thereby greatly reducing the threshold for setting the burying, but also solves the problem of the need to re-send the package in the prior art to set the burying, greatly improving the efficiency of setting the burying.

[0168] In another embodiment, a method for processing buried points is provided, such as Figure 5 As shown, the method is executed by a cloud application, and the method includes:

[0169] Step S501, when a target component is triggered, obtaining a component identifier of the target component;

[0170] Specifically, when the target component in the cloud application is triggered by the target tracking type, the component identifier of the target component can be obtained. Among them, obtaining the component identifier can be obtaining the component identifier generated based on the above tracking rules. For example, when the user sees the page shown in 301 in Figure 3 in the terminal, when the user clicks "Confirm Payment", the target component is triggered. At this time, the cloud application can obtain the component identifier of the target component.

[0171] It should be noted that what the user sees in the terminal is also the target image. When the user clicks on a certain position in the target image, an interaction instruction is generated based on the coordinates of the position in the target image, and then the interaction instruction is sent to the cloud application. The cloud application extracts the coordinates from the interaction instruction and maps the coordinates to the page currently displayed by the cloud application, thereby determining the specific location on the page where the user actually clicked.

[0172] Step S502: when there is a match between the component identifier and at least one component identifier in the tracking configuration file, obtaining target reporting content corresponding to the match;

[0173] After obtaining the component identifier of the target component, match the component identifier with at least one component identifier in the configuration file. If there is a match, obtain the target reporting content corresponding to the match. Specifically, the target reporting content corresponding to the component identifier of the match can be determined based on the first association relationship; if there is no match, it means that the target component has no tracking point set.

[0174] Step S503, reporting the target reporting content.

[0175] After obtaining the target report content, you can report the target report content, that is, send the target report content to the cloud.

[0176] In a preferred embodiment of the present invention, before the target component in the cloud application is triggered, the method further includes:

[0177] In response to the start instruction, a request for obtaining a tracking configuration file is sent to the cloud;

[0178] When the tracking configuration file is obtained successfully, the tracking configuration file is stored.

[0179] Specifically, since the cloud application runs in the cloud and not in the user's terminal, the user initiates the startup instruction to start the cloud application in the terminal, and then the terminal sends it to the cloud application. The cloud application starts running in response to the startup instruction and sends a request to the cloud for obtaining the tracking configuration file. The cloud can directly feedback the tracking configuration file or feedback the path where the tracking configuration file is stored. The cloud application obtains the tracking configuration file from the path by itself.

[0180] When the tracking configuration file is successfully obtained, the configuration file is stored in the local space of the cloud application on the one hand, and the configuration file is converted into a memory object and stored in the memory on the other hand, so that the cloud application can match the user ID during runtime.

[0181] Furthermore, in addition to sending a request to the cloud for the tracking configuration file when starting up, the cloud application can also poll the cloud through the heartbeat service at a preset time interval to obtain the tracking configuration file. For example, the cloud application sends a heartbeat to the cloud every 5 minutes to obtain the tracking configuration file.

[0182] In an embodiment of the present invention, when a target component in a cloud application is triggered, the component identifier of the target component is obtained; when there is a match between the component identifier and at least one component identifier in the tracking configuration file, the target reporting content corresponding to the match is obtained, and the target reporting content is tracked. In this way, even personnel who do not have R&D capabilities can configure tracking in the front end, and the cloud generates the final tracking configuration file based on the configuration. During the use of the cloud application, the user can obtain the tracking configuration file from the cloud based on the user identifier, and track the target component based on the tracking configuration file. This not only liberates R&D productivity and realizes "whoever needs it, sets it", so that any person can set tracking, thereby greatly reducing the threshold for setting tracking, but also solves the problem of the need to re-send packages in the prior art for setting tracking, greatly improving the efficiency of setting tracking.

[0183] The present invention provides a framework structure diagram of a method for processing buried points, see Figure 6 , including front-end and cloud.

[0184] The front end includes visualization layer, data acquisition layer and network layer.

[0185] The visualization layer is used to visualize the application client that sets the tracking point, obtain a visualized setting page, and then display the visualized setting page and the target image to the user, such as Figure 3A , 3B shown.

[0186] The data acquisition layer is used to obtain various configuration information set in the settings page after confirmation by the operator, encapsulate various configuration information, generate a tracking request; and obtain the target image from the network layer and pass the target image to the visualization layer.

[0187] The network layer is used to send tracking requests to the cloud; and receive target images sent by the cloud.

[0188] The cloud layer includes a parsing layer, a configuration file layer, and a virtual machine.

[0189] The parsing layer is used to receive and parse the tracking request to obtain various configuration information; and send the acquired target image to the front end.

[0190] The configuration file layer is used to generate configuration files based on various configuration information.

[0191] The virtual machine includes a detection layer, a network layer, an interface layer, and a tracking point reporting layer.

[0192] The detection layer is used to poll the configuration file layer for the existence of the configuration file through a heartbeat method.

[0193] The network layer includes a receiving interface and a storage interface. The receiving interface is used to obtain the configuration file from the configuration file layer; the storage interface is used to serialize and store the obtained configuration file.

[0194] The interface layer is used to pass the stored configuration files to the tracking point reporting layer.

[0195] The point-of-care reporting layer includes point-of-care interface 1 and point-of-care interface 2. Point-of-care interface 1 is used to generate the target component after point-of-care by "replacing the original component with a target component with a target point-of-care type; adding the target report content to the target attribute information of the target component to obtain the target component after point-of-care"; point-of-care interface 2 is used to generate the target component after point-of-care by "obtaining the original attribute information of the original component; adding the target report content to the original attribute information to obtain the target component after point-of-care" (of course, the two methods can be interchanged); and, when the target component is triggered during the user's use of the cloud application, the target report content corresponding to the target component is reported to the cloud.

[0196] Figure 7 A structural diagram of a processing device for embedding points provided in another embodiment of the present application is shown as follows: Figure 7 As shown, the device of this embodiment may include:

[0197] The display module 701 is used to display at least one type of buried point and at least one reported content in response to a selection instruction for a target area in a target image; the target image is a page image of a current display page of a cloud application to be buried, and the target area is an area corresponding to any component in the current display page; and,

[0198] In response to the tracing type selection instruction, displaying a target tracing type determined from at least one tracing type, and in response to the reporting content selection instruction, displaying a target reporting content determined from at least one reporting content;

[0199] A receiving module 702, used for receiving a generating instruction;

[0200] The first generating module 703 is used to generate a tracking point request based on the target tracking point type and the target reporting content in response to the generating instruction;

[0201] The first sending module 704 is used to send the tracking request to the cloud, and the cloud performs tracking on any component based on the tracking request; the cloud application runs in the cloud.

[0202] The buried point processing device of this embodiment can execute the buried point processing method shown in the first embodiment of the present application. The implementation principle is similar and will not be repeated here.

[0203] In an embodiment of the present invention, the application client for setting displays at least one type of tracking point and at least one reported content in response to a selection instruction for a target area in a target image; the target image is a page image of the current display page of the cloud application to be tracked, and the target area is an area corresponding to any component in the current display page, and then in response to the tracking point type selection instruction, the target tracking point type determined from at least one tracking point type is displayed, and in response to the reported content selection instruction, the target reported content determined from at least one reported content is displayed, and when a generation instruction is received, a tracking point request is generated based on the target tracking point type and the target reported content in response to the generation instruction, and the tracking point request is sent to the cloud, and the cloud performs tracking on any component based on the tracking point request; the cloud application runs in the cloud. In this way, even personnel who do not have R&D capabilities can set tracking points for any component in the cloud application in the application client through the above-mentioned configuration method, which not only liberates R&D productivity and realizes "who needs, who sets", so that any personnel can set tracking points, thereby greatly reducing the threshold for setting tracking points, but also solves the problem of needing to re-send packages in the prior art for setting tracking points, greatly improving the efficiency of setting tracking points.

[0204] Figure 8 A structural diagram of a processing device for embedding points provided in another embodiment of the present application is shown as follows: Figure 8 As shown, the device of this embodiment may include:

[0205] The target image acquisition module 801 is used to acquire the target image of the cloud application of the point to be buried;

[0206] The second sending module 802 is used to send the target image to the front end, so that the front end generates a tracking request based on the target image;

[0207] The tracking configuration file acquisition module 803 is used to obtain the tracking configuration file in response to the tracking request;

[0208] The tracking processing module 804 is used to track the original component to be tracked based on the tracking configuration file to obtain the target component after tracking;

[0209] The update module 805 is used to update the tracking point configuration file based on the target component to obtain an updated tracking point configuration file.

[0210] In a preferred embodiment of the present invention, the tracking configuration file acquisition module includes:

[0211] The parsing submodule is used to parse the tracking request and obtain the tracking configuration data;

[0212] The serialization submodule is used to serialize the tracking configuration data to obtain the tracking configuration file.

[0213] In a preferred embodiment of the present invention, the tracking point configuration file includes a target tracking point type and a target reporting content;

[0214] The buried point processing module includes:

[0215] A replacement submodule is used to replace the original component with a target component having a target tracking point type;

[0216] The first adding submodule is used to add the target reporting content to the target attribute information of the target component to obtain the target component after the embedding.

[0217] In a preferred embodiment of the present invention, the buried point processing module includes:

[0218] The original attribute information acquisition submodule is used to obtain the original attribute information of the original component;

[0219] The second adding submodule is used to add the target reporting content to the original attribute information to obtain the target component after the embedding point.

[0220] In a preferred embodiment of the present invention, the update module includes:

[0221] A first processing submodule is used to obtain a component identifier of a target component and establish a first association relationship between the component identifier and a target tracking point type and a target reporting content;

[0222] The second processing submodule is used to add the component identifier and the first association relationship to the tracking point configuration file to obtain an updated tracking point configuration file.

[0223] In a preferred embodiment of the present invention, it also includes:

[0224] The second generating submodule is used to establish a second association relationship between the updated tracking configuration file and the user identifier.

[0225] In a preferred embodiment of the present invention, it also includes:

[0226] A user identification acquisition module, used to respond to a tracking configuration file acquisition request from a cloud application and acquire a user identification from the tracking configuration file acquisition request;

[0227] A determination module, used to determine a target tracking configuration file based on the second association relationship;

[0228] The third sending module is used to feed back the target burying point configuration file to the cloud application, so that when the target component in the cloud application is triggered, the burying point reporting is performed based on the target burying point configuration file.

[0229] In a preferred embodiment of the present invention, the target image acquisition module is specifically used for:

[0230] The page image of the current display page of the cloud application is captured based on a preset frequency to obtain the target image.

[0231] The buried point processing device of this embodiment can execute the buried point processing method shown in the second embodiment of the present application. The implementation principle is similar and will not be repeated here.

[0232] In an embodiment of the present invention, the cloud obtains the target image of the cloud application to be buried, and sends the target image to the front end, so that the front end generates a burying request based on the target image; in response to the burying request, a burying configuration file is obtained, and then the original component to be buried is buried based on the burying configuration file to obtain the target component after burying, and then the burying configuration file is updated based on the target component to obtain the updated burying configuration file. In this way, even personnel who do not have R&D capabilities can configure the burying in the front end, and the cloud generates the final burying configuration file based on the configuration, which not only liberates R&D productivity and realizes "whoever needs, whoever sets", so that any person can set the burying, thereby greatly reducing the threshold for setting the burying, but also solves the problem of the need to re-send the package in the prior art to set the burying, greatly improving the efficiency of setting the burying.

[0233] Fig. 9 A structural diagram of a processing device for embedding points provided in another embodiment of the present application is shown as follows: Fig. 9 As shown, the device of this embodiment may include:

[0234] The component identification acquisition module 901 is used to acquire the component identification of the target component when the target component is triggered;

[0235] The target reporting content acquisition module 902 is used to acquire the target reporting content corresponding to the matching item when there is a matching item between the component identifier and at least one component identifier in the tracking configuration file;

[0236] The reporting module 903 is used to report the target reporting content.

[0237] In a preferred embodiment of the present invention, it also includes:

[0238] A fourth sending module is used to send a request for obtaining a tracking configuration file to the cloud in response to a start instruction before the target component in the cloud application is triggered;

[0239] The storage module is used to store the tracking configuration file when the tracking configuration file is successfully obtained.

[0240] The buried point processing device of this embodiment can execute the buried point processing method shown in the third embodiment of the present application. The implementation principle is similar and will not be repeated here.

[0241] In an embodiment of the present invention, when a target component in a cloud application is triggered, the component identifier of the target component is obtained; when there is a match between the component identifier and at least one component identifier in the tracking configuration file, the target reporting content corresponding to the match is obtained, and the target reporting content is tracked. In this way, even personnel who do not have R&D capabilities can configure tracking in the front end, and the cloud generates the final tracking configuration file based on the configuration. During the use of the cloud application, the user can obtain the tracking configuration file from the cloud based on the user identifier, and track the target component based on the tracking configuration file. This not only liberates R&D productivity and realizes "whoever needs it, sets it", so that any person can set tracking, thereby greatly reducing the threshold for setting tracking, but also solves the problem of the need to re-send packages in the prior art for setting tracking, greatly improving the efficiency of setting tracking.

[0242] In another embodiment of the present application, an electronic device is provided, which includes: a memory and a processor; at least one program, stored in the memory, for being executed by the processor, compared with the prior art, it can achieve: in an embodiment of the present invention, the application client for setting responds to a selection instruction for a target area in a target image, displays at least one burying point type and at least one reporting content; the target image is a page image of the current display page of the cloud application to be buried, and the target area is an area corresponding to any component in the current display page, and then responds to the burying point type selection instruction, displays a target burying point type determined from at least one burying point type, and responds to the reporting content selection instruction, displays a target reporting content determined from at least one reporting content, and when a generation instruction is received, a burying point request is generated based on the target burying point type and the target reporting content in response to the generation instruction, and the burying point request is sent to the cloud, and the cloud burys any component based on the burying point request; the cloud application runs in the cloud. In this way, even personnel who do not have R&D capabilities can set tracking points for any component in the cloud application through the above-mentioned configuration method in the application client. This not only liberates R&D productivity and realizes the principle of "whoever needs it, sets it", so that anyone can set tracking points, thereby greatly reducing the threshold for setting tracking points. It also solves the problem of the need to re-send packages when setting tracking points in the prior art, greatly improving the efficiency of setting tracking points.

[0243] In an alternative embodiment, an electronic device is provided, such as Fig.10 As shown, Fig.10The electronic device 10000 shown includes: a processor 10001 and a memory 10003. The processor 10001 and the memory 10003 are connected, such as through a bus 10002. Optionally, the electronic device 10000 may also include a transceiver 10004. It should be noted that in actual applications, the transceiver 10004 is not limited to one, and the structure of the electronic device 10000 does not constitute a limitation on the embodiments of the present application.

[0244] Processor 10001 may be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 10001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0245] The bus 10002 may include a path to transmit information between the above components. The bus 10002 may be a PCI bus or an EISA bus, etc. The bus 10002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.10 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0246] Memory 10003 can be ROM or other types of static storage devices that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or it can be EEPROM, CD-ROM or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0247] The memory 10003 is used to store application code for executing the solution of the present application, and the execution is controlled by the processor 10001. The processor 10001 is used to execute the application code stored in the memory 10003 to implement the content shown in any of the above method embodiments.

[0248] Among them, electronic devices include but are not limited to: mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc.

[0249] Another embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and when it is run on a computer, the computer can execute the corresponding content in the aforementioned method embodiment. Compared with the prior art, in the embodiment of the present invention, the application client for setting responds to the selection instruction for the target area in the target image, displays at least one type of buried point and at least one reported content; the target image is the page image of the current display page of the cloud application to be buried, and the target area is the area corresponding to any component in the current display page, and then responds to the buried point type selection instruction, displays the target buried point type determined from at least one buried point type, and, responds to the reported content selection instruction, displays the target reported content determined from at least one reported content, when receiving the generation instruction, so that in response to the generation instruction, a buried point request is generated based on the target buried point type and the target reported content, and the buried point request is sent to the cloud, and the cloud performs buried points on any component based on the buried point request; the cloud application runs in the cloud. In this way, even personnel who do not have R&D capabilities can set tracking points for any component in the cloud application through the above-mentioned configuration method in the application client. This not only liberates R&D productivity and realizes the principle of "whoever needs it, sets it", so that anyone can set tracking points, thereby greatly reducing the threshold for setting tracking points. It also solves the problem of the need to re-send packages when setting tracking points in the prior art, greatly improving the efficiency of setting tracking points.

[0250] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0251] The above descriptions are only some embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for processing buried points, characterized in that: include: In response to a selection instruction for a target area in a target image, display at least two types of buried points and at least two types of reported contents; The target image is a page image of the current display page of the cloud application to be embedded, and the target area is an area corresponding to any component in the current display page; The at least two types of reporting contents include a preset custom reporting content setting area and at least one preset copy content corresponding to each tracking point type; In response to the tracing point type selection instruction, displaying a target tracing point type determined from the at least two tracing point types, and in response to the reporting content selection instruction, displaying a target reporting content determined from the at least two reporting contents; receiving a generation instruction, so that in response to the generation instruction, a tracking request is generated based on the target tracking type and the target reported content, and the tracking request is sent to the cloud; the cloud obtains a tracking configuration file in response to the tracking request, and tracks any of the components based on the tracking configuration file to obtain any of the components after tracking; the cloud application runs in the cloud; The step of displaying the target report content determined from the at least two report contents in response to the report content selection instruction includes: In response to a report content selection instruction for the custom report content setting area, receiving a custom content setting operation for the custom report content setting area, and using the text content corresponding to the custom content setting operation as the target report content; Any component after the embedding point is obtained based on the following method: Determine the target tracking point type and target reporting content from the tracking point configuration file; Replacing any of the components with a target component having the target tracking point type, wherein the attribute information of the target component includes the attribute information of any of the components; Add the target reporting content to the attribute information of the target component to obtain any component after the embedding point.

2. A method for processing buried points, characterized in that: include: Acquire a target image of a cloud application to be embedded, and send the target image to a front end, so that the front end generates the embedding request based on the target image; In response to the tracking request, a tracking configuration file is obtained; the tracking configuration file includes a target tracking type and a target reporting content; Replace the original component to be buried with a target component having the target burying type, wherein the attribute information of the target component includes the attribute information of the original component; add the target reporting content to the attribute information of the target component to obtain the target component after burying; The tracking configuration file is updated based on the target component to obtain an updated tracking configuration file; The tracking request is generated in the front end in the following way: In response to a selection instruction for a target area in a target image, at least two types of burying points and at least two types of reporting contents are displayed; the at least two types of reporting contents include a preset custom reporting content setting area and at least one preset copy content corresponding to each burying point type; In response to the tracing point type selection instruction, displaying a target tracing point type determined from the at least two tracing point types, and in response to the reporting content selection instruction, displaying a target reporting content determined from the at least two reporting contents; receiving a generation instruction, so that in response to the generation instruction, a tracking request is generated based on the target tracking type and the target reporting content; The step of displaying the target report content determined from the at least two report contents in response to the report content selection instruction includes: In response to a report content selection instruction for the custom report content setting area, a custom content setting operation for the custom report content setting area is received, and the text content corresponding to the custom content setting operation is used as the target report content.

3. The method for processing buried points according to claim 2, characterized in that: The step of obtaining a tracking configuration file in response to the tracking request includes: Parsing the tracking request to obtain tracking configuration data; The burying point configuration data is serialized to obtain the burying point configuration file.

4. The method for processing buried points according to claim 2, characterized in that: The updating of the tracking configuration file based on the target component to obtain an updated tracking configuration file includes: Obtaining a component identifier of the target component, and establishing a first association relationship between the component identifier, a target embedding point type, and a target reporting content; The component identifier and the first association relationship are added to the tracking point configuration file to obtain the updated tracking point configuration file.

5. The method for processing buried points according to claim 2 or 4, characterized in that: Also includes: A second association relationship between the updated tracking configuration file and the user identifier is established.

6. The method for processing buried points according to claim 5, characterized in that: Also includes: In response to a request for obtaining a tracking configuration file of a cloud application, obtaining a user identifier from the request for obtaining the tracking configuration file; A target burying point configuration file is determined based on the second association relationship, and the target burying point configuration file is fed back to the cloud application, so that when the target component in the cloud application is triggered, the burying point is reported based on the target burying point configuration file.

7. The method for processing buried points according to claim 2, characterized in that: The step of obtaining a target image of a cloud application of a point to be buried comprises: The page image of the current display page of the cloud application is captured based on a preset frequency to obtain the target image.

8. A method for processing buried points, characterized in that: include: When the target component is triggered, obtaining the component identifier of the target component; When there is a match between the component identifier and at least one component identifier in the tracking configuration file, obtaining target reporting content corresponding to the match; Report the target reporting content as a point; The tracking configuration file is obtained by the cloud in response to the tracking request sent by the front end, and the tracking request is generated by the front end in the following way: In response to a selection instruction for a target area in a target image, at least two types of tracking points and at least two types of reporting contents are displayed; the at least two types of reporting contents include a preset custom reporting content setting area and at least one preset copy content corresponding to each tracking point type; the target image is a page image of a current display page of a cloud application to be tracked, and the target area is an area corresponding to any component in the current display page; In response to the tracing point type selection instruction, displaying a target tracing point type determined from the at least two tracing point types, and in response to the reporting content selection instruction, displaying a target reporting content determined from the at least two reporting contents; receiving a generation instruction, so that in response to the generation instruction, a tracking request is generated based on the target tracking type and the target reporting content, and the tracking request is sent to the cloud; The step of displaying the target report content determined from the at least two report contents in response to the report content selection instruction includes: In response to a report content selection instruction for the custom report content setting area, receiving a custom content setting operation for the custom report content setting area, and using the text content corresponding to the custom content setting operation as the target report content; The tracking point configuration file includes the target tracking point type and the target reporting content; The target component is embedded in the following way: Replacing the original component with a target component having the target tracking point type; wherein the attribute information of the target component includes the attribute information of the original component; Add the target reporting content to the attribute information of the target component to obtain the target component after the embedding point.

9. The method for processing buried points according to claim 8, characterized in that: Before the target component in the cloud application is triggered, it also includes: In response to the start instruction, a request for obtaining a tracking configuration file is sent to the cloud; When the burying point configuration file is successfully obtained, the burying point configuration file is stored.

10. A buried point processing device, characterized in that: include: A display module, configured to display at least two types of buried points and at least two types of reported contents in response to a selection instruction for a target area in a target image; The target image is a page image of the current display page of the cloud application to be embedded, and the target area is an area corresponding to any component in the current display page; The at least two types of reporting contents include a preset custom reporting content setting area and at least one preset copy content corresponding to each tracking point type; In response to the tracing point type selection instruction, displaying a target tracing point type determined from the at least two tracing point types, and in response to the reporting content selection instruction, displaying a target reporting content determined from the at least two reporting contents; A receiving module, used for receiving a generating instruction; A first generating module, configured to generate a tracking request based on the target tracking type and the target reporting content in response to the generating instruction; A first sending module is used to send the tracking request to the cloud, the cloud obtains a tracking configuration file in response to the tracking request, and tracks any component based on the tracking configuration file to obtain any component after tracking; the cloud application runs in the cloud; When the display module displays the target report content determined from the at least two report contents in response to the report content selection instruction, it is specifically used to: In response to a report content selection instruction for the custom report content setting area, receiving a custom content setting operation for the custom report content setting area, and using the text content corresponding to the custom content setting operation as the target report content; Any component after the embedding point is obtained based on the following method: Determine the target tracking point type and target reporting content from the tracking point configuration file; Replace any of the components with a target component having the target tracking point type; wherein the attribute information of the target component includes the attribute information of any of the components; Add the target reporting content to the attribute information of the target component to obtain any component after the embedding point.

11. A buried point processing device, characterized in that: include: A target image acquisition module is used to acquire the target image of the cloud application of the point to be buried; A second sending module, used for sending the target image to the front end, so that the front end generates the burying point request based on the target image; A tracking point configuration file acquisition module is used to obtain a tracking point configuration file in response to the tracking point request; the tracking point configuration file includes a target tracking point type and a target reporting content; A tracking point processing module, used for replacing the original component to be tracked with a target component having the target tracking point type, wherein the attribute information of the target component includes the attribute information of the original component; adding the target reporting content to the attribute information of the target component to obtain the target component after tracking; An updating module, used to update the tracking configuration file based on the target component to obtain an updated tracking configuration file; The tracking request is generated in the front end in the following way: In response to a selection instruction for a target area in a target image, at least two types of burying points and at least two types of reporting contents are displayed; the at least two types of reporting contents include a preset custom reporting content setting area and at least one preset copy content corresponding to each burying point type; In response to the tracing point type selection instruction, displaying a target tracing point type determined from the at least two tracing point types, and in response to the reporting content selection instruction, displaying a target reporting content determined from the at least two reporting contents; receiving a generation instruction, so that in response to the generation instruction, a tracking request is generated based on the target tracking type and the target reporting content; The step of displaying the target report content determined from the at least two report contents in response to the report content selection instruction includes: In response to a report content selection instruction for the custom report content setting area, a custom content setting operation for the custom report content setting area is received, and the text content corresponding to the custom content setting operation is used as the target report content.

12. The buried point processing device according to claim 11, characterized in that: When the tracing configuration file acquisition module obtains the tracing configuration file in response to the tracing request, it is specifically used to: Parsing the tracking request to obtain tracking configuration data; The burying point configuration data is serialized to obtain the burying point configuration file.

13. The buried point processing device according to claim 11, characterized in that: When the updating module updates the tracking configuration file based on the target component to obtain the updated tracking configuration file, it is specifically used to: Obtaining a component identifier of the target component, and establishing a first association relationship between the component identifier, a target embedding point type, and a target reporting content; The component identifier and the first association relationship are added to the tracking point configuration file to obtain the updated tracking point configuration file.

14. The buried point processing device according to claim 11 or 13, characterized in that: Also includes: The second generating submodule is used to establish a second association relationship between the updated tracking configuration file and the user identifier.

15. The buried point processing device according to claim 14, characterized in that: Also includes: A user identification acquisition module, configured to respond to a request for obtaining a tracing configuration file from a cloud application and obtain a user identification from the request; A determination module, configured to determine a target tracking configuration file based on the second association relationship; The third sending module is used to feed back the target burying point configuration file to the cloud application, so that when the target component in the cloud application is triggered, the burying point reporting is performed based on the target burying point configuration file.

16. The buried point processing device according to claim 11, characterized in that: When acquiring the target image of the cloud application of the point to be buried, the target image acquisition module is specifically used to: The page image of the current display page of the cloud application is captured based on a preset frequency to obtain the target image.

17. A buried point processing device, characterized in that: include: A component identification acquisition module, used for acquiring the component identification of the target component when the target component is triggered; A target reporting content acquisition module, used for acquiring target reporting content corresponding to a matching item when a matching item exists between the component identifier and at least one component identifier in the tracking configuration file; A reporting module, used for reporting the target reporting content; The tracking configuration file is obtained by the cloud in response to the tracking request sent by the front end, and the tracking request is generated by the front end in the following way: In response to a selection instruction for a target area in a target image, at least two types of tracking points and at least two types of reporting contents are displayed; the at least two types of reporting contents include a preset custom reporting content setting area and at least one preset copy content corresponding to each tracking point type; the target image is a page image of a current display page of a cloud application to be tracked, and the target area is an area corresponding to any component in the current display page; In response to the tracing point type selection instruction, displaying a target tracing point type determined from the at least two tracing point types, and in response to the reporting content selection instruction, displaying a target reporting content determined from the at least two reporting contents; receiving a generation instruction, so that in response to the generation instruction, a tracking request is generated based on the target tracking type and the target reporting content, and the tracking request is sent to the cloud; The step of displaying the target report content determined from the at least two report contents in response to the report content selection instruction includes: In response to a report content selection instruction for the custom report content setting area, receiving a custom content setting operation for the custom report content setting area, and using the text content corresponding to the custom content setting operation as the target report content; The tracking point configuration file includes the target tracking point type and the target reporting content; The target component is embedded in the following way: Replacing the original component with a target component having the target tracking point type; wherein the attribute information of the target component includes the attribute information of the original component; Add the target reporting content to the attribute information of the target component to obtain the target component after the embedding point.

18. The buried point processing device according to claim 17, characterized in that: Also includes: A fourth sending module is used to send a request for obtaining a tracking configuration file to the cloud in response to a start instruction before the target component in the cloud application is triggered; A storage module is used to store the burying point configuration file when the burying point configuration file is successfully obtained.

19. An electronic device, characterized in that: It includes: processor, memory, and bus; The bus is used to connect the processor and the memory; The memory is used to store operation instructions; The processor is used to execute the method for processing the buried point described in any one of claims 1 to 9 by calling the operation instruction.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images