Method and device for reporting buried point information, readable storage medium and electronic device

Abstract

The embodiments of the present disclosure relate to a method for reporting buried point information, a reporting device for buried point information, a readable storage medium, and an electronic device, and relate to the field of computer technology. The method for reporting buried point information includes: in response to a resource request of an application client, parsing the return data of the resource request to obtain a buried point transparent transmission rule set, the buried point transparent transmission rule set is used to describe the buried point information of the resources in the return data of the resource request; determining candidate resources according to the resources in the return data of the resource request, associating the buried point transparent transmission rule set with the candidate resources; and reporting buried point information based on the buried point transparent transmission rule set associated with the candidate resources. The present disclosure can realize the transparent transmission of buried point parameters based on the matching of buried point transparent transmission rules, and improve the reporting efficiency and accuracy of buried point information.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of computer technology. More specifically, the embodiments of the present disclosure relate to a method for reporting burial point information, a device for reporting burial point information, a computer-readable storage medium, and an electronic device. Background Art

[0002] This section is intended to provide a background or context to embodiments of the present disclosure, and no description herein is admitted to be prior art by inclusion in this section.

[0003] In data tracking, there is often a lot of information that has nothing to do with the content rendering and operations performed by the front-end, so this information can be reported through parameter transparent transmission, that is, the algorithm and the server merge the content and strategy information that only serves the data tracking into a string. The front-end does not need to parse it, but only needs to assign the value and return it intact.

[0004] The point-of-care transparent transmission solutions in related technologies can be mainly divided into three types. The first is to realize request-level parameter feedback through the request feedback capability of RPC (Remote Procedure Call), and manually bind resources in the client; the second is to realize request resource-level parameter binding feedback in the DTO (Data Transfer Object) of RPC at all levels; the third is that when a request occurs, each RPC service writes the relevant information into a unified server-side log cache or data cache layer with traceid (traceid is used to identify the unique id of a network request) as the key (keyword), and then in the point-of-care processing flow, the previously cached transparent transmission information is retrieved from the cache according to the traceid information reported by the data point-of-care to associate it to obtain the point-of-care transparent transmission information. Summary of the invention

[0005] However, the first solution uses the same binding method for the transparent parameters of all resources in the request, and it is impossible to accurately distinguish the bindings. As a result, all transparent parameters need to be bound to different resource models, and the amount of data transmitted is large. In addition, the subsequent manual distinction is labor-intensive, which reduces the efficiency of reporting the tracking information. At the same time, if there are two RPCs on the request link that use the same keywords in the transparent parameters, they cannot be accurately distinguished, resulting in low accuracy in reporting the tracking information. The second solution requires accurate transparent field conventions in the request and response DTOs of RPCs at all levels on the server, and corresponding assignments in each RPC, which is costly, labor-intensive, and low in accuracy. The third solution results in very high storage costs on the server, and due to the delay in logging points on both the client and server, the timely association success rate is not high, and more secondary and tertiary associations are required, which is inefficient. In addition, due to the existence of delays, in order to ensure the accuracy of tracking information reporting, it can only be used in offline analysis, which cannot meet the actual needs.

[0006] The scenario of data processing.

[0007] Therefore, an improved method for reporting buried point information is urgently needed, which can simultaneously improve the accuracy and efficiency of reporting buried point transparent transmission parameters and reduce the maintenance cost of buried point transparent transmission parameters.

[0008] In this context, the embodiments of the present disclosure are intended to provide a method for reporting burial point information, a device for reporting burial point information, a computer-readable storage medium, and an electronic device.

[0009] According to the first aspect of the embodiment of the present disclosure, a method for reporting burial point information is provided, comprising: in response to a resource request of an application client, parsing the return data of the resource request to obtain a burial point transparent transmission rule set, the burial point transparent transmission rule set being used to describe the burial point information of the resources in the return data of the resource request; determining candidate resources based on the resources in the return data of the resource request, and associating the burial point transparent transmission rule set with the candidate resources; and reporting the burial point information based on the burial point transparent transmission rule set associated with the candidate resources.

[0010] In an optional embodiment, the response to the resource request of the application client, parsing the return data of the resource request to obtain a set of buried point transmission rules, including: responding to the resource request of the application client, parsing the return data of the resource request based on a preset base class to obtain a set of buried point transmission rules; determining candidate resources based on the resources in the return data of the resource request, and associating the set of buried point transmission rules with the candidate resources, including: determining candidate resources based on the resources indicated by the subclass inherited from the base class in the return data of the resource request, and associating the set of buried point transmission rules with the candidate resources.

[0011] In an optional embodiment, associating the burying point transparent transmission rule set with the candidate resources includes: creating a class object for each subclass corresponding to each candidate resource; binding the burying point transparent transmission rule set to the class object corresponding to each subclass of the candidate resource, so as to associate the burying point transparent transmission rule set with the candidate resources.

[0012] In an optional implementation, the tracking point transparent transmission rule set is determined based on one or more of the resource identifier, service identifier, tracking point information, and remote procedure call service information in the return data of the resource request.

[0013] In an optional embodiment, the burying point transparent transmission rule set includes a resource identifier corresponding to the resource in the return data of the resource request; the burying point transparent transmission rule set associated with the candidate resource reports the burying point information, including: in response to a trigger operation in the application client, obtaining a target resource identifier of the burying point object targeted by the trigger operation; matching the target resource identifier with the resource identifier in the burying point transparent transmission rule set associated with the candidate resource to determine the target burying point information of the burying point object based on the matching result; and reporting the burying point information of the burying point object based on the target burying point information.

[0014] In an optional embodiment, the target resource identifier is matched with the resource identifier in the burying point transparent transmission rule set associated with the candidate resource to determine the target burying point information of the burying point object based on the matching result, including: determining the target resource from the candidate resources, the target resource including the candidate resource corresponding to the burying point object; matching the target resource identifier with the resource identifier in the burying point transparent transmission rule set associated with the target resource; determining the target burying point transparent transmission rule according to the burying point transparent transmission rule indicated by the resource identifier in the burying point transparent transmission rule set that successfully matches the target resource identifier; and determining the target burying point information of the burying point object based on the burying point information in the target burying point transparent transmission rule.

[0015] In an optional embodiment, determining the target resource from the candidate resources includes: when the burial point parameters to be reported of the burial point object include burial point transparent transmission parameters, determining the server interface associated with the burial point transparent transmission parameters of the burial point object; and determining the target resource from the candidate resources based on the resources in the return data of the server interface.

[0016] In an optional embodiment, the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the resource identifier that successfully matches the target resource identifier in the burying point transparent transmission rule set, including: when the resource identifier in the burying point transparent transmission rule is a preset resource identifier, if the preset resource identifier is the same as the target resource identifier, then the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the preset resource identifier; when the resource identifier in the burying point transparent transmission rule is a wildcard identifier, the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the wildcard identifier.

[0017] In an optional embodiment, the burying point transparent transmission rule set includes a burying point transparent transmission rule list; the target resource identifier is matched with the resource identifier in the burying point transparent transmission rule set associated with the candidate resource to determine the target burying point information of the burying point object based on the matching result, including: traversing the resource identifiers in the burying point transparent transmission rule list associated with the candidate resource according to a preset order, stopping the traversal when the currently traversed resource identifier matches the target resource identifier, and determining the target burying point information of the burying point object according to the burying point information in the burying point transparent transmission rule indicated by the currently traversed resource identifier.

[0018] In an optional embodiment, the point-of-care transparent transmission rule set includes a point-of-care transparent transmission rule list; in response to the resource request of the application client, the return data of the resource request is parsed to obtain the point-of-care transparent transmission rule set, including: in response to the resource request of the application client, when the preset adding method of the transparent transmission rule corresponding to the resource in the resource request is the first method, the parsed point-of-care transparent transmission rule corresponding to the resource is added to the head of the point-of-care transparent transmission rule list; in response to the resource request of the application client, when the preset adding method of the transparent transmission rule corresponding to the resource in the resource request is the second method, the parsed point-of-care transparent transmission rule corresponding to the resource is added to the tail of the point-of-care transparent transmission rule list.

[0019] In an optional embodiment, in response to the resource request of the application client, the return data of the resource request is parsed to obtain a set of burying point transparent transmission rules, including: in response to the resource request of the application client, the return data of the resource request is parsed based on a preset base class to generate a structured burying point transparent transmission rule; based on the structured burying point transparent transmission rule, the set of burying point transparent transmission rules is obtained.

[0020] In an optional embodiment, the method for reporting the burial point information also includes: in response to a triggering event of calling a server interface, obtaining a burial point transparent transmission parameter value of a server burial point object associated with the called server interface, and reporting the burial point transparent transmission parameter value.

[0021] In an optional embodiment, when the burying point transparent transmission rule set includes the resource identifier corresponding to the resource in the return data of the resource request, the method for reporting the burying point information also includes: when the resource request belongs to a preset resource request to be verified, the burying point transparent transmission parameter rule set corresponding to the resource request is sent to the burying point verification platform, so that the burying point verification platform verifies the burying point reporting information of the resource request; wherein, the way in which the burying point verification platform verifies the burying point reporting information of the resource request includes: obtaining the resource identifier of the burying point object pre-associated with the resource request; matching the resource identifier of the burying point object with the resource identifier in the burying point transparent transmission rule set corresponding to the resource request; determining the verification rule according to the burying point transparent transmission rule indicated by the successfully matched resource identifier in the burying point transparent transmission rule set; and verifying the burying point reporting information of the burying point object based on the verification rule.

[0022] According to the second aspect of the embodiment of the present disclosure, there is provided a reporting device for burying point information, comprising: a parsing module, configured to parse the return data of the resource request in response to the resource request of the application client to obtain a burying point transparent transmission rule set, wherein the burying point transparent transmission rule set is used to describe the burying point information of the resources in the return data of the resource request; a unified resource binding module, configured to determine candidate resources according to the resources in the return data of the resource request, and associate the burying point transparent transmission rule set with the candidate resources; and a reporting module, configured to report the burying point information based on the burying point transparent transmission rule set associated with the candidate resources.

[0023] In an optional embodiment, the parsing module is specifically configured to: respond to a resource request from an application client, parse the return data of the resource request based on a preset base class to obtain a set of point-of-care transmission rules; the unified resource binding module is configured to: determine candidate resources based on the resources indicated by the subclass inherited from the base class in the return data of the resource request, and associate the set of point-of-care transmission rules with the candidate resources.

[0024] In an optional embodiment, associating the burying point transparent transmission rule set with the candidate resources includes: creating a class object for each subclass corresponding to each candidate resource; binding the burying point transparent transmission rule set to the class object corresponding to each subclass of the candidate resource, so as to associate the burying point transparent transmission rule set with the candidate resources.

[0025] In an optional implementation, the tracking point transparent transmission rule set is determined based on one or more of the resource identifier, service identifier, tracking point information, and remote procedure call service information in the return data of the resource request.

[0026] In an optional embodiment, the point-of-sale transmission rule set includes a resource identifier corresponding to the resource in the return data of the resource request; the reporting module is configured to: in response to a trigger operation in the application client, obtain a target resource identifier of the point-of-sale object targeted by the trigger operation; match the target resource identifier with the resource identifier in the point-of-sale transmission rule set associated with the candidate resource, so as to determine the target point-of-sale information of the point-of-sale object based on the matching result, and report the point-of-sale information of the point-of-sale object according to the target point-of-sale information.

[0027] In an optional embodiment, the target resource identifier is matched with the resource identifier in the burying point transparent transmission rule set associated with the candidate resource to determine the target burying point information of the burying point object based on the matching result, including: determining the target resource from the candidate resources, the target resource including the candidate resource corresponding to the burying point object; matching the target resource identifier with the resource identifier in the burying point transparent transmission rule set associated with the target resource; determining the target burying point transparent transmission rule according to the burying point transparent transmission rule indicated by the resource identifier in the burying point transparent transmission rule set that successfully matches the target resource identifier; and determining the target burying point information of the burying point object based on the burying point information in the target burying point transparent transmission rule.

[0028] In an optional embodiment, determining the target resource from the candidate resources includes: when the burial point parameters to be reported of the burial point object include burial point transparent transmission parameters, determining the server interface associated with the burial point transparent transmission parameters of the burial point object; and determining the target resource from the candidate resources based on the resources in the return data of the server interface.

[0029] In an optional embodiment, the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the resource identifier that successfully matches the target resource identifier in the burying point transparent transmission rule set, including: when the resource identifier in the burying point transparent transmission rule is a preset resource identifier, if the preset resource identifier is the same as the target resource identifier, then the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the preset resource identifier; when the resource identifier in the burying point transparent transmission rule is a wildcard identifier, the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the wildcard identifier.

[0030] In an optional embodiment, the burying point transparent transmission rule set includes a burying point transparent transmission rule list; the target resource identifier is matched with the resource identifier in the burying point transparent transmission rule set associated with the candidate resource to determine the target burying point information of the burying point object based on the matching result, including: traversing the resource identifiers in the burying point transparent transmission rule list associated with the candidate resource according to a preset order, stopping the traversal when the currently traversed resource identifier matches the target resource identifier, and determining the target burying point information of the burying point object according to the burying point information in the burying point transparent transmission rule indicated by the currently traversed resource identifier.

[0031] In an optional embodiment, the set of burying point transparent transmission rules includes a list of burying point transparent transmission rules; the parsing module is specifically configured to: in response to a resource request of an application client, when the preset adding method of the transparent transmission rules corresponding to the resources in the resource request is a first method, add the parsed burying point transparent transmission rules corresponding to the resources to the head of the list of burying point transparent transmission rules; in response to a resource request of an application client, when the preset adding method of the transparent transmission rules corresponding to the resources in the resource request is a second method, add the parsed burying point transparent transmission rules corresponding to the resources to the tail of the list of burying point transparent transmission rules.

[0032] In an optional embodiment, the parsing module is specifically configured to: respond to a resource request from an application client, parse the return data of the resource request based on a preset base class to generate structured point-of-care transmission rules; and obtain the point-of-care transmission rule set based on the structured point-of-care transmission rules.

[0033] In an optional embodiment, the reporting device for the burial point information also includes a server interface call event reporting module, which is configured to: in response to triggering a call to a server interface event, obtain the burial point transparent transmission parameter value of the server burial point object associated with the called server interface, and report the burial point transparent transmission parameter value.

[0034] In an optional embodiment, when the burying point transparent transmission rule set includes a resource identifier corresponding to the resource in the return data of the resource request, the reporting device of the burying point information also includes a verification module, which is configured to: when the resource request belongs to a preset resource request to be verified, send the burying point transparent transmission parameter rule set corresponding to the resource request to the burying point verification platform, so that the burying point verification platform verifies the burying point reporting information of the resource request; wherein, the way in which the burying point verification platform verifies the burying point reporting information of the resource request includes: obtaining the resource identifier of the burying point object pre-associated with the resource request; matching the resource identifier of the burying point object with the resource identifier in the burying point transparent transmission rule set corresponding to the resource request; determining the verification rule according to the burying point transparent transmission rule indicated by the successfully matched resource identifier in the burying point transparent transmission rule set; and verifying the burying point reporting information of the burying point object based on the verification rule.

[0035] According to a third aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for reporting the burial point information described in the first aspect is implemented.

[0036] According to the fourth aspect of the implementation of the present disclosure, an electronic device is provided, including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the method for reporting burial point information described in the first aspect above by executing the executable instructions.

[0037] According to the method for reporting burial point information, the device for reporting burial point information, the computer-readable storage medium and the electronic device of the embodiments of the present disclosure, in response to the resource request of the application client, the return data of the resource request is parsed to obtain a burial point transparent transmission rule set, and the burial point transparent transmission rule set is used to describe the burial point information of the resources in the return data of the resource request; candidate resources are determined according to the resources in the return data of the resource request, and the burial point transparent transmission rule set is associated with the candidate resources; and the burial point information is reported based on the burial point transparent transmission rule set associated with the candidate resources. On the one hand, by parsing all resources in the resource request at the time of request to obtain a set of buried point transparent transmission rules, and then matching and associating from the buried point transparent transmission rules when reporting, automatic binding of resources is achieved, thereby improving the reporting efficiency of buried point transparent transmission information; on the other hand, based on the buried point transparent transmission rule set, the buried point transparent transmission parameters in the buried point information report can be accurately determined, thereby improving the accuracy of the buried point information reporting; on the other hand, based on the buried point transparent transmission rule set associated with the candidate resources, real-time upload of the buried point transparent transmission parameters can be achieved, which can be applied to scenarios where real-time analysis and processing of the buried point transparent transmission parameters are required. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The above and other objects, features and advantages of the exemplary embodiments of the present disclosure will become readily understood by reading the detailed description below with reference to the accompanying drawings. In the accompanying drawings, several embodiments of the present disclosure are shown in an exemplary and non-limiting manner, in which:

[0039] Figure 1 A schematic diagram showing a method for reporting buried point information according to an embodiment of the present disclosure is shown;

[0040] Figure 2 A flow chart of a method for obtaining a set of buried point transparent transmission rules according to an embodiment of the present disclosure is shown;

[0041] Figure 3 A schematic diagram of a method for associating a set of tracking point transparent transmission rules with candidate resources according to an embodiment of the present disclosure is shown;

[0042] Figure 4 A flow chart of a method for reporting tracking point information based on a tracking point transparent transmission rule set associated with candidate resources according to an embodiment of the present disclosure is shown;

[0043] Figure 5 A schematic diagram of a process for determining target burial point information according to an embodiment of the present disclosure is shown;

[0044] Figure 6 A diagram of a configuration interface of a tracking point parameter according to an embodiment of the present disclosure is shown;

[0045] Figure 7 A schematic diagram showing a process of transparent transmission of a point embedding parameter according to an embodiment of the present disclosure is shown;

[0046] Figure 8 A flow chart showing a method for verifying the reported information of a buried point according to an embodiment of the present disclosure is shown;

[0047] Fig. 9 A structural diagram showing a device for reporting buried point information according to an embodiment of the present disclosure;

[0048] Fig.10 A structural diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0049] In the drawings, the same or corresponding reference numerals represent the same or corresponding parts. DETAILED DESCRIPTION

[0050] The principles and spirit of the present disclosure will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present disclosure, and are not intended to limit the scope of the present disclosure in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0051] Those skilled in the art will appreciate that the embodiments of the present disclosure may be implemented as a system, device, apparatus, method or computer program product. Therefore, the present disclosure may be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0052] According to an embodiment of the present disclosure, a method for reporting burial point information, a device for reporting burial point information, a computer-readable storage medium, and an electronic device are provided.

[0053] In this document, any number of elements in the drawings is used for illustration rather than limitation, and any naming is used only for distinction and does not have any limiting meaning.

[0054] The principle and spirit of the present disclosure are explained in detail below with reference to several representative embodiments of the present disclosure. SUMMARY OF THE INVENTION

[0056] The inventors of the present invention have discovered that in some existing point-of-care transparent transmission parameter schemes, all transparent transmission parameters need to be bound to different resource models, the amount of data transmitted is very large, and the point-of-care transparent transmission parameters associated with different resource models need to be manually distinguished, which results in a large workload and reduces the efficiency of determining the point-of-care information. At the same time, if there are two RPCs on the request link that use the same keywords in the transparent transmission parameters, they cannot be accurately distinguished, resulting in low accuracy in reporting the point-of-care information and being unable to meet the real-time analysis scenario of the point-of-care transparent transmission parameters.

[0057] In view of the above content, the basic technical solution of the present disclosure is to: provide a method for reporting burial point information, a reporting device for burial point information, a computer-readable storage medium and an electronic device, in response to a resource request of an application client, parse the return data of the resource request to obtain a burial point transparent transmission rule set, the burial point transparent transmission rule set is used to describe the burial point information of the resources in the return data of the resource request; determine candidate resources based on the resources in the return data of the resource request, and associate the burial point transparent transmission rule set with the candidate resources; report the burial point information based on the burial point transparent transmission rule set associated with the candidate resources. On the one hand, by parsing all resources in the resource request at the time of request to obtain a set of buried point transparent transmission rules, and then matching and associating from the buried point transparent transmission rules when reporting, automatic binding of resources is achieved, thereby improving the reporting efficiency of buried point transparent transmission information; on the other hand, based on the buried point transparent transmission rule set, the buried point transparent transmission parameters in the buried point information report can be accurately determined, thereby improving the accuracy of the buried point information reporting; on the other hand, based on the buried point transparent transmission rule set associated with the candidate resources, real-time uploading of the buried point transparent transmission parameters can be achieved, so as to be applied to scenarios where real-time analysis and processing of the buried point transparent transmission parameters are required.

[0058] After introducing the basic principles of the present disclosure, various non-limiting embodiments of the present disclosure are described in detail below.

[0059] Application Scenario Overview

[0060] It should be noted that the following application scenarios are only shown to facilitate understanding of the spirit and principle of the present disclosure, and the embodiments of the present disclosure are not limited in this respect. On the contrary, the embodiments of the present disclosure can be applied to any applicable scenario.

[0061] The present disclosure can be applied to scenarios where data is collected. For example, the method for reporting tracking information provided by the present disclosure can be used to collect application usage data (such as the number of visits, the number of visitors, the length of stay, the number of page views, etc.), and based on this, the application usage can be tracked to provide data support for further optimization of the application; in the message recommendation scenario, the method for reporting tracking information provided by the present disclosure can be used to collect historical data of the object, and then based on the collected historical data, structured data can be constructed, and historical data and / or structured data can be used to perform multi-scenario analysis, thereby providing accurate decision-making information for the corresponding business.

[0062] Exemplary Methods

[0063] In data tracking, there is often a lot of information that has nothing to do with content rendering and operations on the front end, such as: algorithm information (recall strategy, sorting strategy, intervention strategy, etc.), delivery strategy, content experiment bucket information, recommendation reasons, etc.; and there are other content or products that carry mutable information, such as the number of comments, whether it is collected, tags, author attention status, etc., which can be associated with pseudo-table information stored on the server after uploading the tracking on the client. However, due to the delay in tracking reporting and the lag in data processing, when the data is finally processed, the associated status may no longer be the actual situation at the time, so the associated information is biased.

[0064] Taking the common audio and video APP (Application) as an example, in addition to the main illustrations, titles and other information in the page card, there will be a lot of upper and lower superscripts, such as the superscript used to display the playback volume of the content represented by the page card, the superscript used to display the user permissions of the content represented by the page card, etc. The existence of the superscript can attract the user's attention and prompt the user to pay attention to some important information. It can be seen that the display of the superscript will also affect the user's click situation to a certain extent. Therefore, in the buried point information, it is necessary to accurately know the specific value and label type of the superscript in the clicked page card when the user clicks on the page card in the client. However, for the display of the client, the meaning of different superscripts is not important, it is just a different display effect of the view. If you want to report information in the buried point, you need to make clear protocols and model agreements. Sending information that does not perceive the specific content in the client and performing targeted parameter buried points will bring additional workload, and the work link is long and cannot be effective online at any time, which is not flexible enough.

[0065] Based on this, by adding point-of-sale transparent transmission information to the point-of-sale reporting information, the algorithm and the server can merge the content and strategy information that only serves the data point-of-sale into a string. The front end does not need to parse it and can only assign the value and return it intact, thereby achieving maximum flexibility and accuracy, minimum dependence and workload, and realizing the transparent transmission of point-of-sale parameters.

[0066] Taking the resource tracking requirements of the playlist recommendation module and the song recommendation module on the homepage of a common audio and video APP as an example, for the relevant fields in the playlist and song request in a request, the server's multi-layer RPC request needs to have the ability to transmit this information. Therefore, it is necessary to invade the overall server and client code architecture to a large extent, which brings relatively high costs.

[0067] The tracking point parameter transparent transmission schemes in related technologies can be mainly divided into three types. The first is to realize request-level parameter feedback through the request feedback capability of RPC, and manually bind resources in the client; the second is to realize request resource-level parameter binding feedback in the DTO of RPC at all levels; the third is that when a request occurs, each RPC service writes the relevant information into a unified server-side log cache or data cache layer with traceid as the key, and then in the tracking point processing flow, the previously cached transparent transmission information is retrieved from the cache according to the traceid information reported by the data tracking point for association to obtain the tracking point transparent transmission information.

[0068] However, for the first solution, the transparent transmission parameters are treated equally for all resources in the request and cannot be accurately bound and distinguished (for example, in the transparent transmission parameters, k1=v1 is only required for the playlist resource; k2=v2 is only required for the song resource, but it cannot be distinguished). This will result in the need to bind all transparent transmission parameters to different resource models, and the amount of data transmitted is very large. And for the request transparent transmission parameters, the information in the interface return often exists in an independent data node of the Body (the actual data content of the request result), or is unified in the Header of the request, rather than directly bound to each specific content resource model. Therefore, this solution requires the client to manually bind one by one to assign resources in the parsing request response packet, which requires a large amount of work, resulting in low efficiency in determining the embedded transparent transmission parameters. And because it is first uniformly bound and then manually distinguished, if there are two RPCs on the request link that use the same key in the transparent transmission parameters, it is impossible to distinguish which RPC the transparent transmission parameters should belong to, resulting in low accuracy in determining the embedded transparent transmission parameters.

[0069] For the second solution, it is necessary to make accurate transparent field agreements in the request and response DTOs of each level of RPC on the server side, and assign corresponding values ​​in each RPC. Therefore, its R&D cost and maintenance cost are very high, and it is difficult to fully cover all levels of RPC requests.

[0070] For the third solution, on the one hand, it leads to very high storage costs on the server side; on the other hand, due to the latency of both client and server log points, the timely association success rate is low, and more secondary and tertiary associations are required. And due to the latency, it can only serve offline analysis and cannot meet the needs of real-time data processing.

[0071] The exemplary embodiments of the present disclosure first provide a method for reporting buried point information to at least overcome all or part of the above-mentioned defects existing in the related art.

[0072] Figure 1 A method for reporting tracking point information in an exemplary embodiment of the present disclosure is shown, and the method may include:

[0073] Step S110, in response to the resource request of the application client, parsing the return data of the resource request to obtain a tracking point transparent transmission rule set, where the tracking point transparent transmission rule set is used to describe the tracking point information of the resource in the return data of the resource request;

[0074] Step S120, determining candidate resources according to the resources in the return data of the resource request, and associating the embedding point transparent transmission rule set with the candidate resources;

[0075] Step S130: reporting the tracking point information based on the tracking point transparent transmission rule set associated with the candidate resources.

[0076] The following are Figure 1 Provide detailed instructions for each step.

[0077] In step S110, in response to the resource request of the application client, the return data of the resource request is parsed to obtain a set of embedding point transparent transmission rules.

[0078] For example, when a user opens an application client or performs an operation in the application client, the application client may send a resource request to its corresponding server to request the server for content to be displayed in a page of the application client.

[0079] In other words, resources can be understood as the display content of the front-end page. Resource request is to request the display content of the front-end page from the server, and the return data of the resource request includes the determined display content of the front-end page.

[0080] Taking a music-type application client as an example, the application client can send a resource request to the server to determine the recommended playlist and / or recommended songs displayed in the application client based on the return data of the resource request.

[0081] In an exemplary implementation, the resource request may include an RPC request, ie, a Remote Procedure Call (RPC) request.

[0082] Exemplarily, step S110 may be executed in the server, that is, the server sends return data to the application client in response to the resource request of the application client, and parses the return data sent to the application client to obtain a set of buried point transmission rules. Step S110 may also be executed in the application client, that is, in response to the resource request of the application client, the application client parses the return data of the resource request to obtain a set of buried point transmission rules. Step S110 may also be jointly executed by the server and the application client, such as when the application client sends a resource request to the server, the server determines the return data of the resource request, and sends the return data to the application client, and then the application client parses the return data to obtain a set of buried point transmission rules. This exemplary embodiment does not specifically limit this.

[0083] In an exemplary embodiment, the point-burying and transparent transmission rule set is used to describe the point-burying information of resources in the return data of the resource request. In other words, the point-burying and transparent transmission rule set includes the point-burying information of all resources in the return data of the resource request. In other words, the point-burying and transparent transmission rules can be understood as telling the application client how to bury points, that is, which transparent transmission parameters need to be buried in which resources.

[0084] In an exemplary embodiment, the set of tracking point transparent transmission rules is determined based on one or more of the resource identifier, business identifier, tracking point information, and remote procedure call service information in the return data of the resource request. Among them, the resource identifier may include one or more of the resource type and the resource identity identifier. In other words, the tracking point transparent transmission rules can be determined based on one or more of the resource identifier, business identifier, tracking point information, and remote procedure call service information.

[0085] For example, the transparent transmission protocol of the embedded point transparent transmission parameters can be pre-defined, such as the transparent transmission protocol of the embedded point transparent transmission parameters can be defined as "${ctype}::${cid}::${kv_str}::${rpcinfo}". Among them, ctype represents the resource type, which can be uniformly defined by the embedded point platform. CID identifies the resource identity, and the value of CID can be a wildcard or a specified value. If the value of CID is a wildcard, it means that all resources are effective. If the value of CID is a specified value, it can be the CID array corresponding to the specified value. Kv_str represents the specific embedded point information. For example, if three business parties have embedded points in the pit corresponding to the same resource, there are three groups of KV, namely K1v1, K2v2, and K3v3, which are spliced ​​into m_k1_v1-n_k2_v2-q_k3_v3, where m, n, and q are business identifiers defined by the business party. rpcinfo indicates the information of the rpc service that currently inserts the embedding point transparent transmission parameters, which is used to troubleshoot and locate problems on the entire link. It can be automatically obtained based on the rpc context.

[0086] The business party can configure the corresponding tracking point transparent transmission rules for its business resources in advance according to the above protocol and its own needs. For example, according to the above protocol, the tracking point information kv can be embedded to determine that it is effective for all resources of this request, that is, the tracking point transparent transmission rule is ctype and cid with wildcards, kv_str is its own tracking point information, and "*" represents the wildcard as an example, then the tracking point transparent transmission rule that is effective for all resources of this request can include "*::*::kv*". It is also possible to embed the tracking point information kv according to the above protocol to determine that it is effective for all resources under the specified resource type, that is, specify the resource type, and the resource identity identifier takes a wildcard. For example, the tracking point transparent transmission rule that is effective for all resources under the specified resource type can include "ctype::*::kv*", where ctype is the specified resource type. According to the above-mentioned protocol, the embedding point information kv can also be embedded to ensure that it is effective for the specified resource type and resource identity. At this time, the embedding point transmission rule can include "ctype::cid::kv*", where ctype is the specified resource type and cid is the specified resource identity.

[0087] When the service identifier is included in the point-of-sale transparent transmission rule, the point-of-sale transparent transmission rule disclosed in the present invention can not only determine the resource scope to be bound to the transparently transmitted point-of-sale information kv, but also effectively distinguish the keywords set for each business by using the service identifier as the kv prefix, thereby avoiding parameter overlap between multi-level services and improving the accuracy of point-of-sale parameter transparent transmission.

[0088] Exemplarily, a specific implementation of step S110 may include: in response to a resource request from an application client, parsing the return data of the resource request based on a preset base class to obtain a resource request from the application client.

[0089] Get the set of buried point transparent transmission rules.

[0090] Taking the example of using ctrp to represent the point-of-entry transparent transmission rules, a unified base class resource model BaseData can be defined, so that resource models that need to parse the transparent transmission parameters inherit from BaseData. BaseData provides the point-of-entry transparent transmission parameter parsing method parseCTrp to parse the ctrp in the return data of the resource request, provides a method for storing ctrp data to save the parsed ctrp data, and provides a method for obtaining ctrp data to obtain the parsed ctrp data. All business data classes that need to perform point-of-entry transparent transmission can inherit from the base class BaseData, call the parseCTrp method to parse the ctrp data from the return data, and call the getCTrp method to obtain the ctrp corresponding to the class object of the current business data class, so as to bind the ctrp and the class object of the current business data class.

[0091] For example, each business data class can pre-customize the tracking point transmission rules for its own resources based on the above-mentioned tracking point transmission protocol, such as determining that the tracking point transmission information is effective for all resources, determining that the tracking point transmission information is effective for resources of a specified type, etc. In response to the resource request of the application client, the business party can provide the return data of the resource request, and the return data includes the ctrp data of the business party. The return data may include multiple resources, which corresponds to multiple ctrp data. The base class resource model BaseData can parse the return data of the resource request to obtain the tracking point transmission rules corresponding to each resource in the return data of the resource request, thereby generating a set of tracking point transmission rules.

[0092] Exemplarily, another specific implementation of step S110 may include: in response to a resource request from an application client, parsing the return data of the resource request based on a preset base class to generate a structured point-of-care transmission rule; and obtaining the point-of-care transmission rule set based on the structured point-of-care transmission rule.

[0093] For example, the parsed ctrp data can be directly saved as structured data, such as storing the parsed ctrp data as data of a map structure. Map is a dictionary data structure. A dictionary structure is a hash structure used to store non-repeating keys. A dictionary uses key-value pairs to store data. For example, during the front-end json (JavaScript Object Notation, JS object notation, a lightweight data exchange format) parsing process, the ctrp data in the returned data can be parsed first, and then the parsed ctrp data can be directly converted into data of a map structure, so as to save the data of the map structure into the above-mentioned BaseData object.

[0094] In an exemplary implementation, moshi (a deserialization library for Android clients) will parse each field in turn according to the order of the fields in json, so you can pre-agree with the server to put the ctrp data first in json, so that you can parse the ctrp data first. When parsing, the life cycle of the JsonReader parser is the same as a parsing process. You can inherit the default JsonReader to add storage fields as the content of word parsing to implement the storage and access of the map result data corresponding to the ctrp in a single parsing process. In this way, you can reuse the map structure data corresponding to the ctrp obtained in the previous parsing process in the subsequent parsing process. That is, each level of ctrp can be parsed into the corresponding map structure data. In this way, when the subsequent levels are parsed, there is no need to parse the ctrp repeatedly, and it can be directly obtained from the map. This is also the reason why the ctrp data is converted into map data for storage, which can improve the ctrp data.

[0095] The efficiency of data analysis.

[0096] Moshi can match in the order added at construction time, use the first matching JsonAdapter.Factory method to create a JsonAdapter, and support combining JsonAdapters by proxy. Based on this feature, you can implement the logic of converting ctrp data into map format and storing it in a custom JsonReader during parsing, as well as obtaining the map structure data corresponding to ctrp from the custom JsonReader to store it in the parsed BaseData object.

[0097] In an exemplary embodiment, the set of buried point transparent transmission rules includes a buried point transparent transmission rule list. That is, the parsed buried point transparent transmission rules can be stored in the buried point transparent transmission rule list. Based on this, Figure 2 A flow chart of a method for obtaining a set of tracking point transparent transmission rules according to an embodiment of the present disclosure is shown. Figure 2 , the method may include steps S210 to S230.

[0098] In step S210, in response to a resource request from an application client, a preset adding method of a transparent transmission rule corresponding to a resource in the resource request is determined.

[0099] For example, for a resource request, multiple business parties may give return data. For example, the request first reaches business party 1, and business party 1 recommends playlist 1 based on its own recommendation strategy, and business party 2 recommends 10 songs based on its own recommendation strategy. Because it is unknown whether the client user will click on playlist 1 or a song in the 10 songs, the tracking point transparent transmission rules corresponding to playlist 1 and the tracking point transparent transmission rules corresponding to the 10 songs need to be added to the tracking point transparent transmission rule set, such as being added to the tracking point transparent transmission rule list.

[0100] In an exemplary embodiment, it can be pre-determined that the head of the buried point transparent transmission rule list has the highest priority, and the priority decreases in sequence thereafter. Of course, it can also be pre-determined that the head of the buried point transparent transmission rule list has the lowest priority, and the priority increases in sequence thereafter. This exemplary embodiment does not make any special limitation on this. The priority is used to determine whether the buried point transparent transmission rule is added to the head or the tail of the buried point transparent transmission rule list, that is, it is used to indicate the method of adding the buried point transparent transmission rule to the buried point transparent transmission rule list. For the buried point transparent transmission parameters of the server side, after the downstream service receives the buried point transparent transmission parameter rule list sent by the upstream service, it only adds to the list without making any modification or deletion. That is, after the downstream service receives the buried point transparent transmission rule list sent by the upstream service, it can add the buried point transparent transmission rules of its own resources to the buried point transparent transmission rule list.

[0101] Taking the head of the point-to-point transparent transmission rule list as an example, if the preset adding method of the transparent transmission rule pre-configured for a resource is the adding method with the highest priority, the point-to-point transparent transmission rule corresponding to the resource will be added to the head of the point-to-point transparent transmission rule list; if the preset adding method of the point-to-point transparent transmission rule pre-configured for a resource is the adding method with the lowest priority, the point-to-point transparent transmission rule corresponding to the resource will be added to the tail of the point-to-point transparent transmission rule list.

[0102] In step S220, when the preset adding method of the transparent transmission rule corresponding to the resource in the resource request is the first method, the buried point transparent transmission rule corresponding to the resource is parsed and added to the head of the buried point transparent transmission rule list.

[0103] For example, when the priority of the head of the buried point transparent transmission rule list is the highest, the first method is the above-mentioned adding method with the highest priority, so that the buried point transparent transmission rule corresponding to the parsed resource will be added to the head of the buried point transparent transmission rule list. When the priority of the head of the buried point transparent transmission rule list is the lowest, the first method is the above-mentioned adding method with the lowest priority, so that the buried point transparent transmission rule corresponding to the parsed resource will be added to the head of the buried point transparent transmission rule list.

[0104] In step S230, when the preset adding method of the transparent transmission rule corresponding to the resource in the resource query is the second method, the buried point transparent transmission rule corresponding to the parsed resource is added to the end of the buried point transparent transmission rule list.

[0105] For example, when the priority of the head of the buried point transparent transmission rule list is the highest, the second method is the above-mentioned adding method with the lowest priority, so that the buried point transparent transmission rule corresponding to the parsed resource will be added to the end of the buried point transparent transmission rule list. When the priority of the head of the buried point transparent transmission rule list is the lowest, the second method is the above-mentioned adding method with the highest priority, so that the buried point transparent transmission rule corresponding to the parsed resource will be added to the end of the buried point transparent transmission rule list.

[0106] Because when the buried point information is reported in the subsequent step S130, it is matched in the buried point transparent transmission rule list in order of priority from high to low, and if a buried point transparent transmission rule that matches successfully is encountered, the matching will not continue. Therefore, taking the head of the buried point transparent transmission rule list as an example, if the preset adding method of the transparent transmission rule pre-configured for a certain resource is the highest priority adding method, then the buried point transparent transmission rule will overwrite other buried point transparent transmission rules that have the same resource identifier as the corresponding resource and have been added to the buried point transparent transmission rule list before. If the preset adding method of the transparent transmission pre-configured for a certain resource is the lowest priority adding method, then the buried point transparent transmission rule will not overwrite other buried point transparent transmission rules that have the same resource identifier as the corresponding resource and have been added to the buried point transparent transmission rule list before.

[0107] Continue to refer Figure 1 In step S120, candidate resources are determined based on the resources in the return data of the resource request, and the point-of-use transmission rule set is associated with the candidate resources.

[0108] Exemplarily, an implementation of step S120 may include: determining candidate resources based on the resources indicated by the subclass inherited from the above-mentioned base class in the return data of the resource request, and associating the embedding point transparent transmission rule set with the candidate resources.

[0109] For example, as mentioned above, all resource models that need to parse the transparent parameters can be inherited from the base class resource model in advance. In other words, the resources indicated by the subclass inherited from the base class can be the resources in the whitelist, wherein the whitelist can be customized. After obtaining the return data of the resource request, the resources in the return data of the resource request and the resources in the whitelist can be matched, and the successfully matched resources can be determined as candidate resources. That is, the candidate resources include the resources indicated by the subclass inherited from the base class in the return data of the resource request. After the candidate resources are determined, the set of buried point transparent transmission rules determined in the above step S110 can be associated with each determined candidate resource respectively.

[0110] For example, Figure 3 A schematic diagram of a method for associating a set of tracking point transparent transmission rules with candidate resources according to an embodiment of the present disclosure is shown. Figure 3 The method may include steps S310 to S320. In step S310, a class object is created for each subclass corresponding to each candidate resource; in step S320, a set of point-of-sale transparent transmission rules is bound to the class object corresponding to each subclass of the candidate resource, so as to associate the set of point-of-sale transparent transmission rules with the candidate resource.

[0111] For example, for each candidate resource, a new class object may be created for a subclass representing the candidate resource, and then the burying point transparent transmission rule determined in step S110 is bound to the class object to associate the burying point transparent transmission rule set with the candidate resource.

[0112] Continue to refer Figure 1 In step S130, the burying point information is reported based on the burying point transparent transmission rule set associated with the candidate resources.

[0113] In an exemplary embodiment, as described above, the set of tracking point transparent transmission rules includes the resource identifier corresponding to the resource in the return data of the resource request. Based on this, Figure 4 The flowchart of a method for reporting tracking point information based on a tracking point transparent transmission rule set associated with candidate resources according to an embodiment of the present disclosure is shown. Figure 4 , the method may include steps S410 to S430.

[0114] In step S410, in response to a trigger operation in the application client, a target resource identifier of the tracking object targeted by the trigger operation is obtained.

[0115] For example, the application client displays content in a graphical user interface based on the return data of the resource request. For example, the return data of the resource request includes a recommended song list 1 and 10 recommended songs. Then, the display page of the application client will display the recommended song list 1 and 10 songs. Based on the display content of the application client, the user can select the content of interest, such as the user can play song list 1 or any of the 10 songs. Of course, the user can also trigger other content, and this exemplary embodiment does not specifically limit this.

[0116] When a trigger operation occurs in the application client, the target resource identifier of the tracking object targeted by the trigger operation can be obtained. Among them, the tracking object targeted by the trigger operation can be understood as the element or page targeted by the trigger operation. In other words, when a trigger operation occurs in the application client, the target resource identifier corresponding to the element or page targeted by the trigger operation can be obtained.

[0117] A page can be understood as an entire area that is exclusively displayed at a certain user interface level, such as a newly opened underlying page, a TAB (tab bar / tab), a channel, etc.; a page is generally used to organize a lot of content for distribution or as the actual function carrier of a single content. Information such as page flow exposure and dwell time is of great significance for application analysis. An element can be understood as a UI (User Interface) component and / or unit that can be interacted with by users on a page, such as a list unit, a button, a slidable content module, etc. Lists and modules are generally used to carry content distribution, and their click-through rate has analytical significance for the content distribution effect. Buttons are generally used to carry user interaction, and buttons are usually mounted on the underlying page of a content unit or content function.

[0118] Both pages and elements can be used as tracking objects. A page can include subpages and elements. For a page, the page itself, the subpages and elements in the page can be used as tracking objects in the page. Users can customize the settings according to their needs.

[0119] In an exemplary embodiment, in response to a trigger operation occurring in an application client, it can be determined whether the object targeted by the trigger operation is a buried point object. Wherein, it can be determined whether the object targeted by the trigger operation is a buried point object according to whether the object is configured with a buried point object identifier oid. If the buried point object identifier is configured, the object is determined to be a buried point object. If the buried point object identifier is not configured, the object is determined not to be a buried point object.

[0120] If the object targeted by the trigger operation is not a buried point object, it means that there is no need to report buried point information at this time, and no processing can be performed. If the object targeted by the trigger operation is a buried point object, the target resource identifier of the resource indicated by the buried point object can be obtained.

[0121] In step S420, the target resource identifier is matched with the resource identifier in the burying point transparent transmission rule set associated with the candidate resource to determine the target burying point information of the burying point object based on the matching result.

[0122] For example, a specific implementation of step S420 may be as follows: Figure 5 shown. Figure 5 A flow chart of a method for determining target burial point information according to an embodiment of the present disclosure is shown.

[0123] refer to Figure 5 , the method may include steps S510 to S540. Wherein:

[0124] In step S510, a target resource is determined from candidate resources.

[0125] In an exemplary embodiment, the target resource includes the candidate resource corresponding to the tracking point object determined in step S410.

[0126] Exemplarily, a specific implementation of step S510 may include: when the burial point parameters to be reported of the burial point object include burial point transparent transmission parameters, determining the server interface associated with the burial point transparent transmission parameters of the burial point object; and determining the target resource from the candidate resources based on the resources in the return data of the server interface.

[0127] For example, for the server-side embedding, its embedding object is HTTP (Hyper Text Transfer Protocol) or RPC interface. What needs to be defined is the parameter value that the service needs to set in the embedding transparent transmission parameters under the corresponding interface and the server-side embedding information that needs to be typed separately. In other words, the server-side embedding object parameters become embedding transparent transmission parameter management, that is, the task service needs to add the parameter value of the embedding transparent transmission parameter agreed in the interface to the RPC embedding transparent transmission parameters in order to call the HTTP or RPC interface set by the embedding object. For the server-side embedding object, its embedding parameters can be directly agreed upon in the event that the server-side interface is called, that is, when a service interface is called, the parameter value of the embedding parameter of the interface is uploaded. After the management and guarantee of the embedding transparent transmission parameters are implemented through the service object, in the front-end embedding object, the target embedding parameter that represents the embedding transparent transmission parameter of the embedding object can be bound to the value of the target embedding parameter and the embedding transparent transmission parameter of the corresponding server by association to describe the assignment of the target embedding parameter. For example Figure 6 As shown, the value of the target burying point parameter s_ctrp representing the burying point transparent transmission parameters in the burying point reporting parameters of the burying point object can be configured as the server interface / api / v1 / resource / comments / add, so as to associate the target burying point parameter representing the burying point transparent transmission parameters in the burying point parameters to be reported with the burying point transparent transmission parameters in the server interface, thereby realizing the management of the burying point transparent transmission parameters.

[0128] Since the target burying point parameters are pre-associated with the server interface, when it is determined that the burying point parameters to be reported of the burying point object include the target burying point parameters representing the burying point transparent transmission parameters, the candidate resource corresponding to the burying point object can be determined through the return data of the server interface pre-associated with the target burying point parameters, and the resource can be used as the target resource. In other words, the candidate resource to which the burying point object belongs can be determined as the target resource.

[0129] In step S520, the target resource identifier is matched with the resource identifier in the point-of-use transparent transmission rule set associated with the target resource.

[0130] For example, the point-of-care transparent transmission rule set associated with each candidate resource includes the point-of-care transparent transmission rules of all candidate resources, so the target resource identifier can be matched with the resource identifier in the point-of-care transparent transmission rule set associated with the target resource to determine the target point-of-care transparent transmission rule based on the matching result, and then the value of the point-of-care transparent transmission parameter of the point-of-care object targeted by the trigger operation can be determined based on the point-of-care information in the target point-of-care transparent transmission rule.

[0131] In step S530, the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the resource identifier that successfully matches the target resource identifier in the burying point transparent transmission rule set.

[0132] Exemplarily, a specific implementation of step S530 may include: when the resource identifier in the burial point transparent transmission rule is a preset resource identifier, if the preset resource identifier is the same as the target resource identifier, then the target burial point transparent transmission rule is determined according to the burial point transparent transmission rule indicated by the preset resource identifier; when the resource identifier in the burial point transparent transmission rule is a wildcard identifier, then the target burial point transparent transmission rule is determined according to the burial point transparent transmission rule indicated by the wildcard identifier.

[0133] For example, as mentioned above, the point-burying transparent transmission rule can be effective for resources of a specified type, for specified resources, or for all resources requested this time. Therefore, the resource identifier in the point-burying transparent transmission rule is a preset resource identifier, which means that the point-burying information in the point-burying transparent transmission rule where the preset resource identifier is located is effective for the specified resource. Then, if the target resource identifier is the same as the preset resource identifier, the match is successful, and the target point-burying transparent transmission rule can be determined based on the point-burying transparent transmission rule indicated by the same preset resource identifier. In the case where the resource identifier in the point-burying transparent transmission rule is a wildcard, the target resource identifier can be directly matched with the wildcard, that is, the target point-burying transparent transmission rule can be determined based on the point-burying transparent transmission rule indicated by the wildcard.

[0134] In step S540, the target burying point information of the burying point object is determined based on the burying point information in the target burying point transparent transmission rule.

[0135] For example, after determining the target burying point transparent transmission rule, the burying point information in the target burying point transparent transmission rule can be determined as the parameter value of the burying point transparent transmission parameter of the burying point object, thereby determining the target burying point information of the target burying point object based on the parameter value.

[0136] Through the above-mentioned steps S510 to S540, the burying point transparent transmission parameters of the burying point object can be automatically determined, thereby realizing automatic reporting of the burying point transparent transmission parameters.

[0137] In an exemplary embodiment, the point-of-entry transparent transmission rule set includes a point-of-entry transparent transmission rule list. Based on this, a specific implementation of step S420 may include: traversing the resource identifiers in the point-of-entry transparent transmission rule list associated with the candidate resource according to a preset order, and stopping the traversal when the currently traversed resource identifier and the target resource identifier match successfully, and determining the target point-of-entry information of the point-of-entry object based on the point-of-entry information in the point-of-entry transparent transmission rule indicated by the currently traversed resource identifier.

[0138] Among them, the preset order may include the order of the priority of the buried point transparent transmission rules from high to low. For example, when the buried point transparent transmission rule at the head of the buried point transparent transmission rule list has the highest priority, the buried point transparent transmission rule list can be traversed from the head. In other words, the buried point transparent transmission rule list can be traversed in order from high to low according to the priority of the buried point transparent transmission rule. When the currently traversed resource identifier and the target resource identifier match successfully, the traversal can be stopped, and then the target buried point information of the buried point object can be determined based on the buried point information in the currently matched successfully buried point transparent transmission rule.

[0139] It is precisely because the traversal is stopped when the match is successful that, as mentioned above, if the head of the buried point transparent transmission rule list has the highest priority, if the preset adding method of the transparent transmission rule pre-configured for a certain resource is the highest priority adding method, then the buried point transparent transmission rule will overwrite other buried point transparent transmission rules that have the same resource identifier as its corresponding resource and have been added to the buried point transparent transmission rule list before. If the preset adding method of the transparent transmission pre-configured for a certain resource is the lowest priority adding method, then the buried point transparent transmission rule will not overwrite other buried point transparent transmission rules that have the same resource identifier as its corresponding resource and have been added to the buried point transparent transmission rule list before. In this way, there will be no situation where the buried point transparent transmission parameters cannot be distinguished due to the use of the same keywords.

[0140] In an exemplary implementation, if the list of embedding point transparent transmission rules is traversed and no embedding point transparent transmission rule that successfully matches the target resource identifier is found, it is determined that the currently triggered object has no embedding point transparent transmission parameters that need to be reported.

[0141] Continue to refer Figure 4 In step S430, the burying point information is reported for the burying point object according to the target burying point information.

[0142] After determining the target burying point information, the target burying point information can be used as the burying point transparent transmission value of the burying point transparent transmission parameter configured for the burying point object, thereby reporting the burying point information.

[0143] In the present disclosure, when the application client needs to update the content displayed on the page, it can send a resource request to the server. For example, when the client needs to recommend the content displayed on the page, it can send a service request to the server. The server can call different service interfaces to generate the return data of the service request. For example, the server first calls service interface 1 to obtain the recommended song list 1, then calls service interface 2 to obtain the recommended song list 2, and then continues to call service interface 3 to obtain the recommended 10 songs. Then, the return data of the service request includes song list 1, song list 2 and 10 songs, thereby generating a display page based on song list 1, song list 2 and 10 songs.

[0144] Since each server has pre-configured the corresponding tracking point transparent transmission rules according to the above tracking point transparent transmission protocol, after determining the return data of the service request, the returned data can be parsed to obtain the tracking point transparent transmission rules corresponding to playlist 1, playlist 2 and 10 songs respectively, thereby determining the tracking point transparent transmission rule set. In the case that the resource models corresponding to playlist 1, playlist 2 and 10 songs all inherit the base resource model, it means that the resource models corresponding to playlist 1, playlist 2 and 10 songs all need to perform tracking point parameter transparent transmission, and because it is not known how the user will operate on the page at this time, the tracking point transparent transmission rule set can be bound to playlist 1, playlist 2 and 10 songs respectively.

[0145] When the user performs a trigger operation in the client, such as clicking on playlist 1, the target resource identifier corresponding to the playlist 1 clicked by the user can be obtained, and the target resource identifier can be matched with the resource identifier in the embedding point transmission rule in the embedding point transmission rule set bound to playlist 1. According to the embedding information in the successfully matched resource identifier, the parameter value of the embedding point transmission parameter of the embedding point object triggered by the user's trigger operation is determined, and the parameter value of the embedding point transmission parameter is reported to realize automatic parsing and binding of the embedding point transmission parameter to the resource model, thereby improving the efficiency and accuracy of the embedding point parameter transmission.

[0146] For example, Figure 7 A schematic diagram showing a process of transparent transmission of tracking point parameters according to an embodiment of the present disclosure is shown. Figure 7 , further illustrating the point-of-care parameter transparent transmission process in the present disclosure. In the present disclosure, a fixed parameter ctrp can be transparently transmitted based on the request parameter transparent transmission capability between the server-side RPCs. The value of the fixed parameter is the above-mentioned point-of-care transparent transmission rule set. When the point-of-care transparent transmission rule set is a point-of-care transparent transmission rule list, an ordered point-of-care transparent transmission rule list can be maintained through ctrp. Each point-of-care transparent transmission rule in the point-of-care transparent transmission rule list can be used to describe a point-of-care information kv and the resource scope it uses, such as the above-mentioned effective for all resources, effective for resources of a specified type, or effective for specified resources.

[0147] When parsing the JSON data returned by the service request, each front-end can perform whitelist matching based on the class description information of each serialization framework during the traversal process, so as to uniformly bind the ctrp corresponding to the service request in the network library of the application client, such as Figure 7As shown, it is determined whether the returned resource is in the configured whitelist ClassType. If so, ctrp is bound to the resource, thereby realizing the unified resource automatic binding of ctrp. Specifically, the json data returned by the service request can be parsed. For example, if the current json level is bound to resources, modules, sub-pages, etc., a new class object can be created through the incoming meta information Metainfo and part of the json string to assign ctrp to the class object, thereby realizing the binding of ctrp and resources.

[0148] So far, in the parsing process of the network request return, ctrp has been automatically and uniformly bound to the subclass resource model that inherits the base class resource model. By utilizing the request-level parameter transparent transmission capability of RPC, resource-level parameter transparent transmission is realized, and there is no need to perform layer-by-layer DTO extension coverage on the server side. The maintenance cost of the embedded point transparent transmission parameters is low and easy to fully cover. However, at this time, ctrp includes the transparent transmission parameters required by all resources in this request. When the embedded point is reported, if this full amount of embedded point transparent transmission parameters is returned, on the one hand, it will cause too much data volume, and on the other hand, it will bring pressure when matching data later, and the matching error rate will be high.

[0149] Therefore, in the present disclosure, when reporting the burying point information, the resource identifier of the triggered burying point object can be matched with the resource identifier of the burying point transparent transmission rule in ctrp to extract the burying point information related only to the current resource, and then it is combined with the burying point type and burying point identity of the current resource to form the resource content of the current resource. That is, according to the stored full burying point parameter transparent transmission rule ctrp, the resource type or resource identity corresponding to the resource triggered by the user is matched to extract the parameter value of the burying point transparent transmission parameter s_ctrp of the resource itself triggered by the user, so as to realize the timely and accurate automatic transparent transmission of the burying point parameters.

[0150] In an exemplary embodiment, the method for reporting burial point information in the present disclosure may also include: in response to a triggering event of calling a server interface, obtaining the burial point transparent parameter value of the server burial point object associated with the called server interface, and reporting the burial point transparent parameter value.

[0151] As mentioned above, for the server-side embedding object, the embedding parameter of the server-side embedding object can be agreed upon in the event that the server-side interface is called, that is, the embedding parameter value of the server-side embedding object is pre-associated with the server-side interface. In this way, when the server-side interface is called, the embedding parameter value of the server-side embedding object associated with the interface can be obtained. The embedding parameter value here is pre-set by each server-side interface according to its business needs, so as to

[0152] Click to report the parameter value.

[0153] In an exemplary embodiment, when the burying point transparent transmission rule set includes a resource identifier corresponding to a resource in the return data of a resource request, the method for uploading burying point information in the present disclosure may further include: when the resource request belongs to a preset resource request to be verified, sending the burying point transparent transmission parameter rule set corresponding to the resource request to the burying point verification platform, so that the burying point verification platform verifies the burying point reporting information of the resource request.

[0154] For example, it is possible to predetermine which resource requests need to be verified, thereby determining a preset set of resource requests to be verified. Then, the identifiers of the current resource request and the resource requests in the preset set of resource requests to be verified can be matched to determine whether the current resource request belongs to the preset resource request to be verified. In the case where the current resource request is a preset resource request, the set of buried point transmission rules for the resource request can be uploaded to the buried point verification platform to verify the buried point transmission parameter values ​​in the buried point reporting information of the resource request.

[0155] For example, Figure 8 A flow chart of a method for verifying the reported information of a tracking point according to an embodiment of the present disclosure is shown. Figure 8 , the method may include steps S810 to S840. Wherein: in step S810, the resource identifier of the burying point object pre-associated with the resource request is obtained; in step S820, the resource identifier of the burying point object is matched with the resource identifier in the burying point transparent transmission rule set corresponding to the resource request; in step S830, according to the burying point transparent transmission rule indicated by the successfully matched resource identifier in the burying point transparent transmission rule set, a verification rule is determined; in step S840, based on the verification rule, the burying point reporting information of the burying point object is verified.

[0156] For example, the information maintenance of the acquisition interface can be performed through the buried point transparent transmission parameter type, and then in the process of buried point real-time testing, when it is determined that the current resource request belongs to the preset resource request to be verified, a to-be-verified mark can be added to the current resource request, and the buried point transparent transmission rule set ctrp of the current resource request is transmitted back to the buried point platform through the gateway. In this way, in the buried point platform, the buried point transparent transmission parameter value can be verified for the resource request with the to-be-verified mark added. Specifically, the resource identifier pre-configured by the buried point object pre-associated with the marked resource request can be obtained, and then the resource identifier in the buried point transparent transmission rule set ctrp of the resource request can be matched, and the correct buried point transparent transmission parameter value is determined according to the buried point transparent transmission rule that is matched successfully, that is, the buried point information in the buried point transparent transmission parameter value that is matched successfully is the correct buried point transparent transmission parameter value, and the correct buried point transparent transmission parameter value is used as the verification rule, and the buried point transparent transmission parameter value in the buried point reporting information is matched with the verification rule, and according to the matching result, the automatic verification of the information in the transparent transmission parameter is realized. In the case of successful matching, the verification passes, otherwise the verification fails.

[0157] Through the above-mentioned steps S810 to S840, it is possible to test whether the value of the burying point transparent transmission parameter s_ctrp in the burying point reporting information and the content of the burying point transparent transmission rule set ctrp issued by the service request match each other, thereby ensuring the accuracy of information transmission of the entire link, realizing automatic verification of the server-side burying point transparent transmission parameters, and automatically verifying the accuracy of the value of the server-side burying point transparent transmission parameters, thereby improving the quality of the server-side burying point transparent transmission parameter verification.

[0158] The method for reporting the tracking point information disclosed in the present invention can realize conflict-free resource-level request parameter transparent transmission between microservices at all levels of the service request link, thereby improving the efficiency and accuracy of the tracking point parameter transparent transmission. In addition, through the method for reporting the tracking point information disclosed in the present invention, the automatic parsing and binding of the transparent transmission parameters to the resource model can be realized only through a tracking point transparent transmission rule set parameter, thereby ensuring the accuracy of the tracking point information transparent transmission while reducing the maintenance cost of the tracking point transparent transmission parameters.

[0159] In addition, the method for reporting the tracking point information disclosed in the present invention can also automatically verify the tracking point transparent transmission parameters, thereby ensuring the upload quality of the tracking point transparent transmission parameters.

[0160] Exemplary Devices

[0161] The exemplary embodiment of the present disclosure also provides a device for reporting buried point information, referring to Fig. 9 The device 900 for reporting the buried point information may include a parsing module 910, a uniform resource binding module 920 and a reporting module 930. Among them:

[0162] The parsing module 910 is configured to parse the return data of the resource request in response to the resource request of the application client to obtain a set of tracking point transparent transmission rules, wherein the set of tracking point transparent transmission rules is used to describe the tracking point information of the resource in the return data of the resource request;

[0163] The unified resource binding module 920 is configured to determine candidate resources according to the resources in the return data of the resource request, and associate the embedding point transparent transmission rule set with the candidate resources;

[0164] The reporting module 930 is configured to report the tracking point information based on the tracking point transparent transmission rule set associated with the candidate resources.

[0165] In an optional implementation, based on the aforementioned embodiment, the above-mentioned parsing module 910 can be specifically configured as follows: in response to a resource request from an application client, the return data of the resource request is parsed based on a preset base class to obtain a set of point-of-use transparent transmission rules. Based on this, the above-mentioned unified resource binding module 920 can be specifically configured as follows: according to the resources indicated by the subclass inherited from the base class in the return data of the resource request, candidate resources are determined, and the set of point-of-use transparent transmission rules is associated with the candidate resources.

[0166] In an optional implementation, based on the aforementioned embodiment, associating the buried point transmission rule set with the candidate resources includes: creating a class object for each subclass corresponding to each candidate resource; binding the buried point transmission rule set to the class object corresponding to each subclass of the candidate resource, so as to associate the buried point transmission rule set with the candidate resources.

[0167] In an optional implementation, based on the aforementioned embodiment, the tracking point transparent transmission rule set is determined according to one or more of the resource identifier, service identifier, tracking point information, and remote procedure call service information in the return data of the resource request.

[0168] In an optional implementation, based on the aforementioned embodiment, the burying point transmission rule set includes a resource identifier corresponding to the resource in the return data of the resource request; based on this, the reporting module 930 can be specifically configured to: in response to a trigger operation in the application client, obtain the target resource identifier of the burying point object targeted by the trigger operation; match the target resource identifier with the resource identifier in the burying point transmission rule set associated with the candidate resource to determine the target burying point information of the burying point object based on the matching result; and report the burying point information of the burying point object according to the target burying point information.

[0169] In an optional implementation, based on the aforementioned embodiment, the target resource identifier is matched with the resource identifier in the burying point transparent transmission rule set associated with the candidate resource to determine the target burying point information of the burying point object based on the matching result, including: determining the target resource from the candidate resources, the target resource including the candidate resource corresponding to the burying point object; matching the target resource identifier with the resource identifier in the burying point transparent transmission rule set associated with the target resource; determining the target burying point transparent transmission rule according to the burying point transparent transmission rule indicated by the resource identifier in the burying point transparent transmission rule set that successfully matches the target resource identifier; determining the target burying point information of the burying point object based on the burying point information in the target burying point transparent transmission rule.

[0170] In an optional implementation, based on the aforementioned embodiment, determining the target resource from the candidate resources includes: when the burial point parameters to be reported of the burial point object include burial point transparent transmission parameters, determining the server interface associated with the burial point transparent transmission parameters of the burial point object; and determining the target resource from the candidate resources based on the resources in the return data of the server interface.

[0171] In an optional implementation, based on the aforementioned embodiment, the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the resource identifier that successfully matches the target resource identifier in the burying point transparent transmission rule set, including: when the resource identifier in the burying point transparent transmission rule is a preset resource identifier, if the preset resource identifier is the same as the target resource identifier, then the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the preset resource identifier; when the resource identifier in the burying point transparent transmission rule is a wildcard identifier, the target burying point transparent transmission rule is determined according to the burying point transparent transmission rule indicated by the wildcard identifier.

[0172] In an optional implementation, based on the aforementioned embodiment, the burying point transparent transmission rule set includes a burying point transparent transmission rule list; the target resource identifier is matched with the resource identifier in the burying point transparent transmission rule set associated with the candidate resource to determine the target burying point information of the burying point object based on the matching result, including: traversing the resource identifiers in the burying point transparent transmission rule list associated with the candidate resource according to a preset order, stopping the traversal when the currently traversed resource identifier matches the target resource identifier successfully, and determining the target burying point information of the burying point object according to the burying point information in the burying point transparent transmission rule indicated by the currently traversed resource identifier.

[0173] In an optional implementation, based on the aforementioned embodiment, the set of burying point transparent transmission rules includes a list of burying point transparent transmission rules; the parsing module 910 may also be specifically configured as: in response to a resource request of an application client, when the preset adding method of the transparent transmission rule corresponding to the resource in the resource request is the first method, the parsed burying point transparent transmission rule corresponding to the resource is added to the head of the list of burying point transparent transmission rules; in response to a resource request of an application client, when the preset adding method of the transparent transmission rule corresponding to the resource in the resource request is the second method, the parsed burying point transparent transmission rule corresponding to the resource is added to the tail of the list of burying point transparent transmission rules.

[0174] In an optional implementation, based on the aforementioned embodiment, the parsing module 910 may also be specifically configured as follows: in response to a resource request from an application client, parsing the return data of the resource request based on a preset base class to generate a structured point-of-care transmission rule; and based on the structured point-of-care transmission rule, obtaining the point-of-care transmission rule set.

[0175] In an optional implementation, based on the aforementioned embodiment, the device 900 for reporting the burial point information may further include a server interface call event reporting module, which may be specifically configured to: in response to triggering a call to a server interface event, obtain the burial point transparent transmission parameter value of the server burial point object associated with the called server interface, and report the burial point transparent transmission parameter value.

[0176] In an optional implementation, based on the foregoing embodiment, when the burying point transparent transmission rule set includes a resource identifier corresponding to the resource in the return data of the resource request, the device 900 may further include a verification module, and the verification module may be specifically configured to: when the resource request belongs to a preset resource request to be verified, send the burying point transparent transmission parameter rule set corresponding to the resource request to the burying point verification platform, so that the burying point verification platform verifies the burying point reporting information of the resource request;

[0177] In an optional implementation, based on the aforementioned embodiment, the method by which the burying point verification platform verifies the burying point reporting information of the resource request includes: obtaining the resource identifier of the burying point object pre-associated with the resource request; matching the resource identifier of the burying point object with the resource identifier in the burying point transparent transmission rule set corresponding to the resource request; determining a verification rule based on the burying point transparent transmission rule indicated by the successfully matched resource identifier in the burying point transparent transmission rule set; and verifying the burying point reporting information of the burying point object based on the verification rule.

[0178] In addition, other specific details of the embodiments of the present disclosure have been described in detail in the inventive implementation of the above method and will not be repeated here.

[0179] Exemplary Storage Media

[0180] The storage medium according to the exemplary embodiment of the present disclosure is described below.

[0181] In this exemplary embodiment, the above method can be implemented by a program product, such as a portable compact disk read-only memory (CD-ROM) and including program code, and can be run on a device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus, or a device.

[0182] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0183] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0184] The program code contained on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RE, etc., or any suitable combination of the foregoing.

[0185] Program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user computing device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0186] Exemplary Electronic Devices

[0187] refer to Fig.10 An electronic device according to an exemplary embodiment of the present disclosure is described. The electronic device may be a client or a server.

[0188] Fig.10 The electronic device 1000 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0189] like Fig.10 As shown, the electronic device 1000 is in the form of a general computing device. The components of the electronic device 1000 may include, but are not limited to: at least one processing unit 1010, at least one storage unit 1020, a bus 1030 connecting different system components (including the storage unit 1020 and the processing unit 1010), and a display unit 1040.

[0190] The storage unit stores program codes, which can be executed by the processing unit 1010, so that the processing unit 1010 performs the steps according to various exemplary embodiments of the present disclosure described in the above “Exemplary Method” section of this specification. For example, the processing unit 1010 can perform the following steps: Figure 1 The method steps shown, etc.

[0191] The storage unit 1020 may include a volatile storage unit, such as a random access storage unit (RAM) 1021 and / or a cache storage unit 1022 , and may further include a read-only storage unit (ROM) 1023 .

[0192] The storage unit 1020 may also include a program / utility 1024 having a set (at least one) of program modules 1025, such program modules 1025 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0193] The bus 1030 may include a data bus, an address bus, and a control bus.

[0194] The electronic device 1000 may also communicate with one or more external devices 1100 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), and such communication may be performed via an input / output (I / O) interface 1050. The electronic device 1000 also includes a display unit 1040, which is connected to the input / output (I / O) interface 1050 for display. Furthermore, the electronic device 1000 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 1060. As shown, the network adapter 1060 communicates with other modules of the electronic device 1000 via a bus 1030. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1000, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0195] It should be noted that, although several modules or submodules of the device are mentioned in the above detailed description, such division is merely exemplary and not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided into multiple units / modules to be embodied.

[0196] In addition, although the operations of the disclosed method are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0197] Although the spirit and principle of the present disclosure have been described with reference to several specific embodiments, it should be understood that the present disclosure is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present disclosure is intended to cover various modifications and equivalent arrangements included in the spirit and scope of the attached claims.

Claims

1. A method for reporting buried point information, characterized in that: include: In response to a resource request from an application client, the return data of the resource request is parsed to obtain a set of point-of-sale transparent transmission rules, wherein the set of point-of-sale transparent transmission rules is used to describe the point-of-sale information of the resources in the return data of the resource request, and the point-of-sale transparent transmission rules are used to indicate the resources in which the application client needs to embed point-of-sale transparent transmission parameters; Determine candidate resources according to the resources in the return data of the resource request, and associate the embedding point transparent transmission rule set with the candidate resources; Reporting tracking point information based on the tracking point transparent transmission rule set associated with the candidate resources; The step of parsing the return data of the resource request in response to the resource request of the application client to obtain a set of point-of-use transparent transmission rules includes: In response to a resource request from an application client, the return data of the resource request is parsed based on a preset base class to obtain a set of embedding point transparent transmission rules; The determining of candidate resources according to the resources in the return data of the resource request, and associating the embedding point transparent transmission rule set with the candidate resources, includes: According to the resources indicated by the subclass inherited from the base class in the return data of the resource request, candidate resources are determined, and the embedding point transparent transmission rule set is associated with the candidate resources.

2. The method for reporting buried point information according to claim 1, characterized in that: The associating the tracking point transparent transmission rule set with the candidate resource includes: Create class objects for each subclass corresponding to each candidate resource; The set of buried point transparent transmission rules is bound to the class object corresponding to the subclass of each candidate resource respectively, so as to associate the set of buried point transparent transmission rules with the candidate resource.

3. The method for reporting buried point information according to claim 1, characterized in that: The set of tracking point transparent transmission rules is determined based on one or more of the resource identifier, service identifier, tracking point information, and remote procedure call service information in the return data of the resource request.

4. The method for reporting buried point information according to claim 1, characterized in that: The set of tracking point transparent transmission rules includes a resource identifier corresponding to the resource in the return data of the resource request; The step of reporting the tracking point information based on the tracking point transparent transmission rule set associated with the candidate resource includes: In response to a trigger operation in the application client, obtaining a target resource identifier of a tracking object targeted by the trigger operation; Matching the target resource identifier with the resource identifier in the tracking point transparent transmission rule set associated with the candidate resource, so as to determine the target tracking point information of the tracking point object based on the matching result; According to the target burying point information, the burying point information of the burying point object is reported.

5. The method for reporting buried point information according to claim 4, characterized in that: The step of matching the target resource identifier with a resource identifier in a tracking point transparent transmission rule set associated with the candidate resource to determine the target tracking point information of the tracking point object based on the matching result includes: Determine a target resource from the candidate resources, where the target resource includes the candidate resource corresponding to the tracking object; Matching the target resource identifier with a resource identifier in a set of embedding point transparent transmission rules associated with the target resource; Determine the target burying point transparent transmission rule according to the burying point transparent transmission rule indicated by the resource identifier that successfully matches the target resource identifier in the burying point transparent transmission rule set; Based on the burying point information in the target burying point transparent transmission rule, the target burying point information of the burying point object is determined.

6. The method for reporting buried point information according to claim 5, characterized in that: The step of determining a target resource from the candidate resources includes: In a case where the burying point parameters to be reported of the burying point object include burying point transparent transmission parameters, determining a server interface associated with the burying point transparent transmission parameters of the burying point object; According to the resources in the return data of the server interface, a target resource is determined from the candidate resources.

7. The method for reporting buried point information according to claim 5, characterized in that: The step of determining the target burying point transparent transmission rule according to the burying point transparent transmission rule indicated by the resource identifier that successfully matches the target resource identifier in the burying point transparent transmission rule set includes: In the case where the resource identifier in the embedding point transparent transmission rule is a preset resource identifier, if the preset resource identifier is the same as the target resource identifier, the target embedding point transparent transmission rule is determined according to the embedding point transparent transmission rule indicated by the preset resource identifier; When the resource identifier in the embedding point transparent transmission rule is a wildcard identifier, the target embedding point transparent transmission rule is determined according to the embedding point transparent transmission rule indicated by the wildcard identifier.

8. The method for reporting buried point information according to claim 4, characterized in that: The point-of-sale transparent transmission rule set includes a point-of-sale transparent transmission rule list; the target resource identifier is matched with a resource identifier in the point-of-sale transparent transmission rule set associated with the candidate resource to determine the target point-of-sale information of the point-of-sale object based on the matching result, including: According to the preset order, the resource identifiers in the list of burying point transparent transmission rules associated with the candidate resources are traversed. When the currently traversed resource identifier and the target resource identifier match successfully, the traversal is stopped, and the target burying point information of the burying point object is determined based on the burying point information in the burying point transparent transmission rule indicated by the currently traversed resource identifier.

9. The method for reporting buried point information according to claim 1, characterized in that: The buried point transparent transmission rule set includes a buried point transparent transmission rule list; The responding to the resource request of the application client and parsing the return data of the resource request to obtain a set of tracking point transparent transmission rules include: In response to a resource request from an application client, when the preset adding method of the transparent transmission rule corresponding to the resource in the resource request is the first method, the parsed point transparent transmission rule corresponding to the resource is added to the head of the point transparent transmission rule list; In response to a resource request from an application client, when the preset adding method of the transparent transmission rules corresponding to the resources in the resource request is the second method, the parsed point transparent transmission rules corresponding to the resources are added to the end of the point transparent transmission rule list.

10. The method for reporting buried point information according to claim 1, characterized in that: The responding to the resource request of the application client and parsing the return data of the resource request to obtain a set of tracking point transparent transmission rules include: In response to a resource request from an application client, the return data of the resource request is parsed based on a preset base class to generate a structured tracking point transparent transmission rule; Based on the structured point-of-sale transparent transmission rule, the point-of-sale transparent transmission rule set is obtained.

11. The method for reporting buried point information according to claim 1, characterized in that: The method further comprises: In response to triggering a call to a server interface event, a burying point transparent transmission parameter value of a server burying point object associated with the called server interface is obtained, and the burying point transparent transmission parameter value is reported.

12. The method for reporting buried point information according to claim 1, characterized in that: In the case where the set of tracking point transparent transmission rules includes a resource identifier corresponding to a resource in the return data of the resource request, the method further includes: In the case where the resource request belongs to a preset resource request to be verified, the burying point transparent transmission parameter rule set corresponding to the resource request is sent to the burying point verification platform, so that the burying point verification platform verifies the burying point reporting information of the resource request; The method in which the tracking point verification platform verifies the tracking point reporting information of the resource request includes: Obtaining a resource identifier of a tracking point object pre-associated with the resource request; Matching the resource identifier of the tracking point object with the resource identifier in the tracking point transparent transmission rule set corresponding to the resource request; Determine a verification rule according to the tracking point transparent transmission rule indicated by the successfully matched resource identifier in the tracking point transparent transmission rule set; Based on the verification rules, the burial point reporting information of the burial point object is verified.

13. A device for reporting buried point information, characterized in that: include: A parsing module is configured to parse the return data of the resource request in response to the resource request of the application client to obtain a set of burying point transparent transmission rules, wherein the set of burying point transparent transmission rules is used to describe the burying point information of the resource in the return data of the resource request, and the burying point transparent transmission rules are used to indicate the resources in which the application client needs to bury the burying point transparent transmission parameters; A unified resource binding module is configured to determine candidate resources according to the resources in the return data of the resource request, and associate the embedding point transparent transmission rule set with the candidate resources; A reporting module, configured to report tracking point information based on a tracking point transparent transmission rule set associated with the candidate resource; The step of parsing the return data of the resource request in response to the resource request of the application client to obtain a set of point-of-use transparent transmission rules includes: In response to a resource request from an application client, the return data of the resource request is parsed based on a preset base class to obtain a set of embedding point transparent transmission rules; The determining of candidate resources according to the resources in the return data of the resource request, and associating the embedding point transparent transmission rule set with the candidate resources, includes: According to the resources indicated by the subclass inherited from the base class in the return data of the resource request, candidate resources are determined, and the embedding point transparent transmission rule set is associated with the candidate resources.

14. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 12 is implemented.

15. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the method according to any one of claims 1 to 12.

Images