Method and apparatus for reporting buried point information, medium and electronic device

Abstract

The embodiments of the present disclosure relate to a method and device for reporting buried point information, a computer-readable storage medium, and an electronic device, and relate to the field of computer technologies. The method for reporting buried point information includes: in response to a preset event occurring in an application client, determining a buried point object associated with the preset event; generating a value of a to-be-reported buried point attribution parameter corresponding to the preset event according to the pit position information and content information of the buried point object associated with the preset event; adding the value of the to-be-reported buried point attribution parameter corresponding to the preset event to a first preset storage container based on the occurrence order of the preset events in the application client; determining the value of the target buried point attribution parameter from the first preset storage container according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event; and reporting buried point information for the buried point object exposed by the buried point reporting event based on the value of the target buried point attribution parameter. The present disclosure can improve the accuracy and efficiency of buried point attribution.

Description

Technical Field

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

[0002] This section aims to provide background or context for the embodiments of the present disclosure recited in the claims. The description herein is not admitted to be prior art merely by including it in this section.

[0003] Buried point is to collect some information in specific processes of an application to track the usage of the application, so as to provide data support for subsequent further optimization of the product. By attributing and reporting the buried point data, accurate analysis of user behavior can be carried out to improve the optimization performance of the product.

[0004] In the related art, the methods for buried point attribution are mainly divided into the following three types: The first type is that since the process of reporting buried logs in the client experiences long processes such as request uploading and parsing, the storage order of buried points in the database is inconsistent with the generation order on the client. Therefore, the logs are sorted within a certain time window on the analysis side, and then buried point attribution is carried out; the second type is to use some parameters on the end where the buried point is generated to agree on the source when specific events (such as page exposure, song playing, etc.) occur; the third type is to splice the pit information and content information of the pit where the jump is generated on the routing information of page jump as the source of the generated lower-level page, and accumulate and transfer multiple levels to achieve multi-level attribution. Summary of the Invention

[0005] However, for the first method, for a large amount of data, the resource consumption is large and the efficiency is low. It is impossible to achieve buried point attribution in real time at the log layer. At the same time, when the buried point time interval is long, there may be a situation where attribution cannot be performed because the attribution target exceeds the time window; for the second method, for different links, the parameters that need to be agreed are not completely the same, resulting in a large amount of data maintenance work and easy occurrence of misattribution; for the third method, the splicing of attribution parameters requires manual intervention by business development when generating the route, with a large amount of work and easy omission or error. At the same time, since it only uses the routing information of no more than four levels of "page - sub-page - module - element", the accuracy of buried point attribution is insufficient. In addition, it is only effective for page jumps supported by the route and is difficult to be extended to attribution scenarios of other interactive events, such as playing and other events, and the generality is poor.

[0006] Therefore, there is a great need for an improved method for reporting buried point information, which can improve the accuracy and efficiency of buried point attribution at the same time, make the buried point attribution general, and reduce the later maintenance cost of buried point data.

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

[0008] According to a first aspect of the embodiments of the present disclosure, a method for reporting buried point information is provided, including: in response to a preset event occurring in an application client, determining a buried point object associated with the preset event; generating a value of a to-be-reported buried point attribution parameter corresponding to the preset event according to the pit information and content information of the buried point object associated with the preset event; adding the value of the to-be-reported buried point attribution parameter corresponding to the preset event to a first preset storage container based on the occurrence order of the preset events in the application client; determining the value of the target buried point attribution parameter from the first preset storage container according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event; and reporting buried point information for the buried point object exposed by the buried point reporting event based on the value of the target buried point attribution parameter.

[0009] In an alternative embodiment, the preset event includes one or more of an event of an element in a page being triggered, a page exposure event, and an automatic trigger event; wherein, when the preset event includes a page exposure event, the page exposure event includes a first page exposure event and / or a second page exposure event, the first page exposure event is determined based on an event that causes a page exposure to occur in the application client due to an operation in the application client, and the second page exposure event is determined based on an event that causes a page exposure to occur in the application client due to an operation in a third-party application.

[0010] In an alternative embodiment, the step of, in response to a preset event occurring in an application client, determining a buried point object associated with the preset event includes: when the preset event includes an event of an element in the page being triggered, in response to the event of the element in the page being triggered occurring in the application client, determining the buried point object associated with the preset event according to the triggered element; when the preset event includes the first page exposure event, in response to the first page exposure event occurring in the application client, determining the buried point object associated with the preset event according to the root page of the page where the exposure ends; when the preset event includes the second page exposure event, in response to the second page exposure event occurring in the application client, determining the buried point object associated with the preset event according to the buried point object pre-associated with the second page exposure event; and when the preset event includes the automatic trigger event, in response to the automatic trigger event occurring in the application client, determining the buried point object associated with the preset event according to the buried point object pre-associated with the automatic trigger event.

[0011] In an alternative implementation, generating the to-be-reported buried point attribution parameter value corresponding to the preset event according to the pit position information and content information of the buried point object associated with the preset event includes: generating the to-be-reported buried point attribution parameter value corresponding to the preset event according to the type of the preset event, the occurrence order of the preset event within the exposure period of the page where the preset event is located, the page exposure order corresponding to the page where the preset event occurs, the pit position information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event; wherein, after the application client is started, each time a page is exposed, the value of the page exposure order increases by a unit value, and the value of the page exposure order restarts counting as the application client is restarted.

[0012] In an alternative implementation, generating the to-be-reported buried point attribution parameter value corresponding to the preset event according to the pit position information and content information of the buried point object associated with the preset event includes: generating the to-be-reported buried point attribution parameter value corresponding to the preset event according to the session identifier at the most recent startup of the application client, the pit position information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event.

[0013] In an alternative implementation, the content information of the buried point object associated with the preset event includes a target object identifier, and the target object identifier includes the buried point object identifier of the root page of the page that can be exposed after the buried point object is triggered.

[0014] In an alternative implementation, determining the value of the target buried point attribution parameter from the first preset storage container according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event includes: matching the buried point object identifier of the exposed buried point object with the target object identifiers in each of the to-be-reported buried point attribution parameter values stored in the first preset storage container; and determining the value of the target buried point attribution parameter according to the matching result.

[0015] In an alternative embodiment, determining the value of the target buried point attribution parameter according to the matching result includes: when the matching is successful, determining the value of the target buried point attribution parameter in the following manner: determining a first to-be-reported buried point attribution parameter value according to the to-be-reported buried point attribution parameter value including the target object identifier with successful matching; determining a second to-be-reported buried point attribution parameter value from the first preset storage container, where the second to-be-reported buried point attribution parameter value includes the to-be-reported buried point attribution parameter value corresponding to the most recent page exposure event stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the larger of the generation times of the first to-be-reported buried point attribution parameter value and the second to-be-reported buried point attribution parameter value; when the matching fails, determining the value of the target buried point attribution parameter in the following manner: determining the value of the target buried point attribution parameter according to the most recently added to-be-reported buried point attribution parameter value in the first preset storage container.

[0016] In an alternative embodiment, when the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes a first type; matching the buried point object identifier of the exposed buried point object with the target object identifier in each of the to-be-reported buried point attribution parameter values stored in the first preset storage container includes: when a new page is exposed in the application client, matching the buried point object identifier of the newly exposed page with the target object identifier in each of the to-be-reported buried point attribution parameter values stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result includes: determining the value of the target buried point attribution parameter of the first type according to the matching result; the target buried point attribution parameter of the first type is used to characterize the exposure source of the root page of the page exposed by the buried point reporting event, and the target buried point attribution parameter of the first type is updated when a new page is exposed.

[0017] In an alternative embodiment, when the buried point reporting event includes a page exposure event, the target buried point attribution parameter includes a second type; the matching of the buried point object identifier of the exposed buried point object with the target object identifier among the values of each to-be-reported buried point attribution parameter stored in the first preset storage container includes: when the page exposed in the application client is a newly created page, matching the buried point object identifier of the exposed page with the target object identifier among the values of each to-be-reported buried point attribution parameter stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result includes: determining the value of the target buried point attribution parameter of the second type according to the matching result; the target buried point attribution parameter of the second type is used to characterize the creation source of the root page of the page exposed by the buried point reporting event, and the target buried point attribution parameter of the second type is updated when a new page is created.

[0018] In an alternative embodiment, when the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes a third type and a first type, the determining method of the value of the target buried point attribution parameter of the third type includes: based on the page exposure order in the application client, in response to the occurrence of root page exposure in the application client, adding the value of the target buried point attribution parameter of the first type corresponding to the newly exposed root page to a second preset storage container; when the number of the values of the target buried point attribution parameter of the first type stored in the second preset storage container is greater than a first preset value, deleting the value of the target buried point attribution parameter of the first type with the earliest addition time from the second preset storage container; determining the value of the target buried point attribution parameter of the third type according to the second preset storage container.

[0019] In an alternative embodiment, when the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes a fourth type and a second type, the determining method of the value of the target buried point attribution parameter of the fourth type includes: based on the page exposure order in the application client, in response to the occurrence of root page exposure in the application client, adding the value of the target buried point attribution parameter of the second type corresponding to the newly exposed root page to a third preset storage container; when the number of the values of the target buried point attribution parameter of the second type stored in the third preset storage container is greater than a second preset value, deleting the value of the target buried point attribution parameter of the second type with the earliest addition time from the third preset storage container; determining the value of the target buried point attribution parameter of the fourth type according to the third preset storage container.

[0020] In an alternative embodiment, when the types of the target buried point attribution parameters include the fifth type and the second type, the method for determining the value of the target buried point attribution parameter of the fifth type includes: matching the buried point object identifier of the buried point object exposed by the buried point reporting event with a preset buried point object identifier; when the matching is successful, determining the value of the target buried point attribution parameter of the fifth type according to the value of the buried point attribution parameter of the second type corresponding to the buried point object indicated by the successfully matched preset buried point object identifier; wherein, the preset buried point object identifier includes the buried point object identifier corresponding to the root page of the home page of the application client.

[0021] In an alternative embodiment, when the matching between the buried point object identifier of the buried point object exposed by the buried point reporting event and the preset buried point object identifier fails, the method for determining the value of the target buried point attribution parameter of the fifth type includes: obtaining the buried point object identifier corresponding to the root page of the page where the buried point object exposed by the buried point reporting event is located; matching the buried point object identifier corresponding to the root page with the target object identifier in the to-be-reported buried point attribution parameter values stored in the first preset storage container to determine a target to-be-reported attribution parameter value; matching the buried point object identifier included in the target to-be-reported buried point attribution parameter value with the preset buried point object identifier, and determining the value of the target buried point attribution parameter of the fifth type according to the matching result.

[0022] In an alternative embodiment, the matching between the buried point object identifier corresponding to the root page and the target object identifier in the to-be-reported buried point attribution parameter values stored in the first preset storage container to determine a target to-be-reported attribution parameter value includes: when the matching is successful, determining the target to-be-reported buried point attribution parameter value according to the successfully matched to-be-reported buried point attribution parameter value; when the matching fails, determining the target to-be-reported buried point attribution parameter value according to the to-be-reported buried point attribution parameter value that was most recently added to the first preset storage container.

[0023] In an alternative embodiment, the matching between the buried point object identifier included in the target to-be-reported buried point attribution parameter value and the preset buried point object identifier, and determining the value of the target buried point attribution parameter of the fifth type according to the matching result includes: when the matching is successful, updating the value of the target buried point attribution parameter of the fifth type according to the value of the buried point attribution parameter of the second type corresponding to the buried point object indicated by the successfully matched preset buried point object identifier; when the matching fails, not updating the value of the target buried point attribution parameter of the fifth type.

[0024] In an alternative embodiment, when the buried point reporting event includes an event of adding a list unit to a playlist, the type of the target buried point attribution parameter includes a sixth type; the matching of the buried point object identifier of the exposed buried point object with the target object identifier in each of the to-be-reported buried point attribution parameter values stored in the first preset storage container includes: in response to the application client generating an event of adding a list unit to a playlist, matching the buried point object identifier corresponding to the buried point object exposed by the event of adding a list unit to a playlist with the target object identifier included in the to-be-reported buried point attribution parameter values stored in the first preset storage container; the determining of the value of the target buried point attribution parameter according to the matching result includes: determining the value of the target buried point attribution parameter of the sixth type according to the matching result; wherein, the target buried point attribution parameter of the sixth type is used to characterize the reason for adding the list unit to the playlist.

[0025] In an alternative embodiment, when the buried point reporting event includes an event of playing a list unit of a playlist, the type of the target buried point attribution parameter includes a seventh type; the matching of the buried point object identifier of the exposed buried point object with the target object identifier in each of the to-be-reported buried point attribution parameter values stored in the first preset storage container includes: in response to the application client generating an event of playing a list unit in a playlist, matching the buried point object identifier of the buried point object exposed by the event of playing the list unit with the target object identifier included in the to-be-reported buried point attribution parameter values stored in the first preset storage container; the determining of the value of the target buried point attribution parameter according to the matching result includes: determining the value of the target buried point attribution parameter of the seventh type according to the matching result; wherein, the target buried point attribution parameter of the seventh type is used to characterize the reason for playing the list unit in the playlist.

[0026] In an alternative embodiment, adding the to-be-reported buried point attribution parameter value corresponding to the preset event to the first preset storage container based on the occurrence order of the preset events in the application client includes: adding the to-be-reported buried point attribution parameter value corresponding to the preset event to the first preset storage container based on the occurrence order of the preset events other than the preset to-be-deleted event in the application client; the preset to-be-deleted event is determined according to a preset page exposed in the application client and / or a preset element triggered.

[0027] In an alternative embodiment, the method further includes: when a preset event occurs in the application client, if there is no associated buried point object for the preset event, determining the root page where the element targeted by the preset event is located; determining the value of the buried point attribution parameter to be reported corresponding to the preset event according to the value of the buried point attribution parameter to be reported corresponding to the root page and a preset identification field; wherein, the preset identification field is used to identify that the value of the buried point attribution parameter to be reported is generated after triggering a position without a buried point object in the application client.

[0028] In an alternative embodiment, reporting the buried point information for the buried point object exposed by the buried point reporting event based on the value of the target buried point attribution parameter includes: using the value of the target buried point attribution parameter as the value of the buried point information reporting parameter for the buried point object exposed by the buried point reporting event, so as to report the buried point information for the buried point object exposed by the buried point reporting event.

[0029] According to a second aspect of the embodiments of the present disclosure, there is provided a buried point information reporting device, including: a preset event response module configured to respond to a preset event occurring in an application client and determine the buried point object associated with the preset event; a value generation module of the buried point attribution parameter to be reported configured to generate the value of the buried point attribution parameter to be reported corresponding to the preset event according to the pit position information and content information of the buried point object associated with the preset event; an addition module configured to add the value of the buried point attribution parameter to be reported corresponding to the preset event to a first preset storage container based on the occurrence order of the preset event in the application client; a value determination module of the target buried point attribution parameter configured to determine the value of the target buried point attribution parameter from the first preset storage container according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event; and a buried point information reporting module configured to report the buried point information for the buried point object exposed by the target buried point reporting event based on the value of the target buried point attribution parameter.

[0030] According to a third aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the buried point information reporting method described in the first aspect above is implemented.

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

[0032] According to the method, device, medium and electronic device for reporting buried point information according to the embodiments of the present disclosure, by responding to a preset event occurring in the application client, the buried point object associated with the preset event is determined; according to the pit information and content information of the buried point object associated with the preset event, a to-be-reported buried point attribution parameter value corresponding to the preset event is generated; based on the occurrence order of the preset events in the application client, the to-be-reported buried point attribution parameter value corresponding to the preset event is added to the first preset storage container; according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event, the value of the target buried point attribution parameter is determined from the first preset storage container; based on the value of the target buried point attribution parameter, buried point information reporting is performed on the buried point object exposed by the buried point reporting event. On the one hand, the present disclosure adds the to-be-reported buried point attribution parameter value corresponding to the preset event to the first preset storage container based on the occurrence order of the preset events in the application client, and then performs buried point attribution reporting, which can improve the accuracy of buried point attribution reporting; on the other hand, the present disclosure first generates the to-be-reported buried point attribution parameter value according to the pit information and content information, and then directly determines the value of the target buried point attribution parameter according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event, and then performs automatic buried point attribution reporting, which can improve the efficiency of buried point attribution; on the third hand, according to the type of the target buried point attribution parameter associated with the buried point object reported by the buried point reporting event and the to-be-reported attribution parameter value stored in the first preset storage container, the present disclosure can directly perform buried point attribution reporting without designing too many business private parameters for multiple paths, reducing the maintenance cost of buried point reporting. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] By reading the following detailed description with reference to the accompanying drawings, the above and other objects, features and advantages of the exemplary embodiments of the present disclosure will become readily understood. In the drawings, several embodiments of the present disclosure are shown in an exemplary but not restrictive manner, wherein:

[0034] Figure 1 Shows a schematic diagram of a method for reporting buried point information according to an embodiment of the present disclosure;

[0035] Figure 2 Shows a schematic diagram of an interface for interaction based on operations in the application client according to an embodiment of the present disclosure;

[0036] Figure 3 Shows a schematic diagram of an interface for interaction based on a third-party application according to an embodiment of the present disclosure;

[0037] Figure 4 Shows a schematic diagram of a display page jumped to based on the operation behavior of a user according to an embodiment of the present disclosure;

[0038] Figure 5 Shows a schematic flowchart of a method for determining the value of a target buried point attribution parameter according to an embodiment of the present disclosure;

[0039] Figure 6 Shows a schematic flowchart of a method for determining the value of a target buried point attribution parameter according to the matching result according to an embodiment of the present disclosure;

[0040] Figure 7 Shows a schematic flowchart of a method for matching based on a buried point object identifier to determine the value of a target buried point attribution parameter according to an embodiment of the present disclosure;

[0041] Figure 8 Shows a schematic flowchart of a method for determining the value of a target buried point attribution parameter of a first type according to an embodiment of the present disclosure;

[0042] Figure 9 Shows a schematic flowchart of a method for determining the value of a target buried point attribution parameter of a second type according to an embodiment of the present disclosure;

[0043] Figure 10 Shows a schematic flowchart of another method for determining the value of a target buried point attribution parameter of a first type according to an embodiment of the present disclosure;

[0044] Figure 11 Shows a schematic diagram of the process of a user operation behavior according to an embodiment of the present disclosure;

[0045] Figure 12 Shows a schematic flowchart of a method for determining the value of a target buried point attribution parameter of a third type according to an embodiment of the present disclosure;

[0046] Figure 13 Shows a schematic flowchart of a method for determining the value of a target buried point attribution parameter of a fourth type according to an embodiment of the present disclosure;

[0047] Figure 14 Shows a schematic flowchart of a method for determining the value of a target buried point attribution parameter of a fifth type according to an embodiment of the present disclosure;

[0048] Figure 15 Shows a schematic flowchart of another method for determining the value of a target buried point attribution parameter of a fifth type according to an embodiment of the present disclosure;

[0049] Figure 16 Shows a schematic flowchart of yet another method for determining the value of a target buried point attribution parameter of a fifth type according to an embodiment of the present disclosure;

[0050] Figure 17The figure shows a schematic flowchart of a method for determining the value of the target buried point attribution parameter of the sixth type according to an embodiment of the present disclosure;

[0051] Figure 18 The figure shows a schematic flowchart of a method for determining the value of the target buried point attribution parameter of the seventh type according to an embodiment of the present disclosure;

[0052] Figure 19 The figure shows a schematic diagram of the process of another user operation behavior according to an embodiment of the present disclosure;

[0053] Figure 20 The figure shows a structural diagram of a buried point information reporting device according to an embodiment of the present disclosure;

[0054] Figure 21 The figure shows a structural diagram of an electronic device according to an embodiment of the present disclosure.

[0055] In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts. Detailed Embodiments

[0056] 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 then implement the present disclosure, and do not 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 be able to convey the scope of the present disclosure to those skilled in the art completely.

[0057] Those skilled in the art know that the embodiments of the present disclosure can be implemented as a system, device, equipment, method, or computer program product. Therefore, the present disclosure can be specifically implemented in the following forms: completely hardware, completely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0058] According to an embodiment of the present disclosure, there is provided a method for reporting buried point information, a buried point method, a device for reporting buried point information, a buried point device, a computer-readable storage medium, and an electronic device.

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

[0060] Next, with reference to several representative embodiments of the present disclosure, the principles and spirit of the present disclosure will be elaborated in detail. Summary of the Invention

[0062] The inventors of the present disclosure have found that in some existing data point reporting solutions, it is necessary to sort the data point log data reported within a certain time window. In the case of a large amount of data, the efficiency is low, resource consumption is caused, and there may be a situation where the attribution target exceeds the time window and cannot be attributed; in some other existing data point reporting solutions, there are problems of large maintenance workload of data point attribution data and inaccurate attribution.

[0063] In view of the above, the basic idea of the present disclosure is as follows: to provide a data point information reporting method, a data point information reporting device, a computer-readable storage medium, and an electronic device. By responding to a preset event occurring in an application client, determining a data point object associated with the preset event; generating a to-be-reported data point attribution parameter value corresponding to the preset event according to the pit information and content information of the data point object associated with the preset event; adding the to-be-reported data point attribution parameter value corresponding to the preset event to a first preset storage container based on the occurrence order of the preset event in the application client; determining the value of the target data point attribution parameter from the first preset storage container according to the type of the target data point attribution parameter associated with the data point object exposed by the data point reporting event; and performing data point information reporting on the data point object exposed by the data point reporting event based on the value of the target data point attribution parameter. On the one hand, the present disclosure adds the to-be-reported data point attribution parameter value corresponding to the preset event to the first preset storage container based on the occurrence order of the preset event in the application client, and then performs data point attribution reporting, which can improve the accuracy of data point attribution reporting; on the other hand, the present disclosure first generates the to-be-reported data point attribution parameter value according to the pit information and content information, and then directly determines the value of the target data point attribution parameter according to the type of the target data point attribution parameter associated with the data point object exposed by the data point reporting event, and then performs automatic data point attribution reporting, which can improve the efficiency of data point attribution; on the other hand, according to the type of the target data point attribution parameter associated with the data point object reported by the data point reporting event and the to-be-reported attribution parameter value stored in the first preset storage container, the present disclosure can directly perform data point attribution reporting without designing too many business private parameters for multiple paths, reducing the maintenance cost of data point reporting.

[0064] After introducing the basic principle of the present disclosure, the various non-limiting embodiments of the present disclosure will be specifically introduced below.

[0065] Overview of Application Scenarios

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

[0067] The present disclosure can be applied to scenarios for data collection. For example, the usage data of an application (such as the number of visits, the number of visitors, the stay duration, the number of page views, the reasons for page views, etc.) can be collected using the method for reporting buried point information provided by the present disclosure, and based on this, the usage situation of the application can be analyzed to provide data support for the further optimization of the application. In an information recommendation scenario, the relevant historical behavior data of users can be collected using the method for reporting buried point information provided by the present disclosure, and then a user portrait can be depicted based on the collected historical behavior data of users to recommend information for users.

[0068] Exemplary Method

[0069] In the buried point reporting scheme in the related art, there are problems of low buried point attribution efficiency, insufficient accuracy of buried point attribution, and high maintenance cost of buried point attribution data.

[0070] An exemplary embodiment of the present disclosure first provides a method for reporting buried point information to at least overcome all or part of the above-mentioned defects existing in the related art.

[0071] Figure 1 The method for reporting buried point information in an exemplary embodiment of the present disclosure is shown and may include:

[0072] Step S110: In response to a preset event occurring in the application client, determine the buried point object associated with the preset event;

[0073] Step S120: Generate a value of a buried point attribution parameter to be reported corresponding to the preset event according to the pit position information and content information of the buried point object associated with the preset event;

[0074] Step S130: Add the value of the buried point attribution parameter to be reported corresponding to the preset event to a first preset storage container based on the occurrence order of the preset event in the application client;

[0075] Step S140: Determine the value of the target buried point attribution parameter from the first preset storage container according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event;

[0076] Step S150: Report buried point information for the buried point object exposed by the buried point reporting event based on the value of the target buried point attribution parameter.

[0077] The following will specifically describe each step in Figure 1 respectively.

[0078] In step S110, in response to a preset event occurring in the application client, determine the buried point object associated with the preset event.

[0079] In an exemplary embodiment, the preset event includes one or more of an event that an element in a page is triggered, a page exposure event, and an automatic trigger event.

[0080] Wherein, when the preset event includes a page exposure event, the page exposure event includes a first page exposure event and / or a second page exposure event. The first page exposure event is determined based on an event that page exposure occurs in the application client due to an operation in the application client. The second page exposure event is determined based on an event that page exposure occurs in the application client due to an operation in a third-party application.

[0081] Next, Figures 2 to 4 a further description will be given to the first page exposure event and the second page exposure event. For example, the user can select "Song A" in the history bar of the page as shown in Figure 2 , and then click the search control 21 after the input bar in Figure 2 . Then, according to this series of operations of the user, it can be jumped to the search result page of "Song A" as shown in Figure 4 . At this time, it is jumped to the page as shown in Figure 4 based on the search behavior of the user in the application client. Therefore, in this case, Figure 4 the exposure of the page as shown in Figure 3 can be understood as the first page exposure event. Another example is that the user inputs the song name "Song A" through the keyboard of the terminal device in the page as shown in Figure 3 , and then clicks the search control 31 on the keyboard, and it can also be jumped to the page as shown in Figure 4 . At this time, it is jumped to the page as shown in Figure 4 based on the search behavior of the user in the third-party application, that is, the keyboard of the terminal device. Therefore, in this case, Figure 4 the exposure of the page as shown in Figure 4 can be understood as the above-mentioned second page exposure event.

[0082] Another example is that the user enters the application client through a page shared by others in another social application client, and the event that a certain page in the application client is exposed can also be understood as the above-mentioned second page exposure event. Taking the application client as NetEase Cloud Music as an example, if the user opens the play page of a certain song in NetEase Cloud Music through a page shared by others in another social application client, then the exposure event of the play page can be understood as the second page exposure event.

[0083] In an alternative embodiment, exposure can be understood as the state of a page or element in an application client changing from invisible to visible in the graphical user interface of a terminal device. The corresponding term for exposure is anti-exposure or end exposure, which can be understood as the state of a page or element in an application client changing from visible to invisible in the graphical user interface of a terminal device.

[0084] A page can be understood as a whole 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.; pages are generally used to organize a lot of content for distribution or as the actual functional carrier of a single piece of content. Information such as the turnover exposure and stay duration of a page is of great significance for the analysis of an application. An element can be understood as a UI (User Interface) component and / or unit in a page that can be interacted with by a user, 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 is of analytical significance for the content distribution effect. Buttons are generally used to carry user interactions and are usually mounted on the underlying page of a certain content unit or content function.

[0085] Both pages and elements can be used as data tracking objects. A page can include sub-pages and elements. For a page, the page itself, the sub-pages and elements in the page can all be used as data tracking objects in the page, and users can make custom settings according to their own needs.

[0086] An auto-triggered event can be understood as an event that can occur automatically in an application client without the need for a triggering operation, such as an auto-play event, an auto-switch event, etc. Among them, for an auto-triggered event, only the content displayed in the page changes, without causing the exposure of a new page.

[0087] In an exemplary application scenario, the priority of an element-triggered event is higher than that of a page exposure event. It can be understood that if the triggering of an element in a page causes a page exposure event at the same time, the preset event that occurs this time will be attributed to the element-triggered event rather than the page exposure event.

[0088] In an exemplary embodiment, the specific implementation of step S110 may include: when the preset event includes an event that an element on a page is triggered, in response to the event that an element on a page is triggered in the application client, determining the buried point object associated with the preset event according to the triggered element; when the preset event includes a first page exposure event, in response to the first page exposure event occurring in the application client, determining the buried point object associated with the preset event according to the root page of the page where the exposure ends; when the preset event includes a second page exposure event, in response to the second page exposure event occurring in the application client, determining the buried point object associated with the preset event according to the buried point object associated with the second page exposure event in advance; when the preset event includes an automatic trigger event, in response to the automatic trigger event occurring in the application client, determining the buried point object associated with the preset event according to the buried point object associated with the automatic trigger event in advance.

[0089] For example, for the event that an element on a page is triggered and the first page exposure event, they both belong to the attributable slots in the application client, that is, they can be automatically attributed to the slots within the application client. However, for the above-mentioned second page exposure event and automatic trigger event, it is impossible to automatically determine the buried point objects associated with them. Based on this, in the present disclosure, for the second page exposure event and automatic trigger event, a general buried point attribution capability is provided, which supports automatically generating the to-be-reported buried point attribution parameter values corresponding to custom events and can automatically add them to the following first preset storage container for subsequent buried point information reporting.

[0090] For example, the buried point attribution parameters of custom events can be pre-configured, which may include attribution type refer_type, attribution slot refer_spm, attribution content information refer_scm, etc., and then associate them with a certain buried point object in the application client. In this way, based on the buried point object associated with the custom event that could not be automatically attributed originally, the to-be-reported buried point attribution parameter values of the custom event can be automatically generated to automatically perform buried point attribution on the custom event.

[0091] Taking the event of automatically playing a radio station on the podcast page in NetEase Cloud Music as an example, an automatic play event autoplay can be defined and associated with the radio station card, so as to automatically generate the parameter values of the buried point attribution to be reported corresponding to the automatic play event, such as refer_type == autopaly, refer_spm == the spm of the radio station card, refer_scm == the scm of the radio station card. That is to say, for some events that cannot be automatically attributed, such as the event of opening a certain page in the target application client based on the third application client, or the automatic play event, etc., the buried point objects associated with these events can be specified in advance, and then the occurrence of these events can be automatically attributed to the buried point based on the buried point objects associated with these events in advance.

[0092] Continue to refer to Figure 1 In step S120, according to the pit information and content information of the buried point object associated with the preset event, generate the parameter values of the buried point attribution to be reported corresponding to the preset event.

[0093] Exemplarily, a specific implementation manner of step S120 may include: generating the parameter values of the buried point attribution to be reported corresponding to the preset event according to the type of the preset event, the occurrence order of the preset event within the exposure period of the page where the preset event is located, the page exposure order corresponding to the page where the preset event occurs, the pit information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event; wherein, after the application client is started, each time a page is exposed, the value of the page exposure order increases by a unit value, and the value of the page exposure order restarts counting with the restart of the application client.

[0094] Exemplarily, another specific implementation manner of step S120 may include: generating the parameter values of the buried point attribution to be reported corresponding to the preset event according to the session identifier at the most recent startup of the application client, the pit information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event.

[0095] Exemplarily, yet another specific implementation manner of step S120 may include: generating the parameter values of the buried point attribution to be reported corresponding to the preset event according to the session identifier at the most recent startup of the application client, the type of the preset event, the occurrence order of the preset event within the exposure period of the page where the preset event is located, the page exposure order corresponding to the page where the preset event occurs, the pit information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event.

[0096] Exemplarily, another specific implementation of step S120 may include: generating a to-be-reported buried point attribution parameter value corresponding to the preset event according to the flag bit, the session identifier at the most recent startup of the application client, the type of the preset event, the occurrence order of the preset event within the exposure period of the page where the preset event is located, the page exposure order corresponding to the page where the preset event occurs, the slot information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event

[0097] Taking sessid to represent the session identifier at the most recent startup of the application client, type to represent the type of the preset event, actseq to represent the occurrence order of the preset event within the exposure period of the page where the preset event is located, pgstep to represent the page exposure order corresponding to the page where the preset event occurs, spm to represent the slot information of the buried point object associated with the preset event, and scm to represent the content information of the buried point object associated with the preset event as an example, the to-be-reported buried point attribution parameter value can be represented as [type][actseq][pgstep][spm][scm], or can also be represented as [sessid][spm][scm].

[0098] Among them, the above-mentioned flag bit is used to describe the components and characteristics of the entire to-be-reported buried point attribution parameter value. Its value is calculated by bits. Each piece of information constituting the to-be-reported buried point attribution parameter value occupies a fixed bit. If its value exists, the corresponding bit value in the flag bit is 1. If its value does not exist, the corresponding bit value in the flag bit is 0. Taking option to represent the flag bit and the to-be-reported buried point attribution parameter value represented as [option][type][actseq][pgstep][spm][scm] as an example, when option takes the value of 00111, it means that type and actseq have no values, and pgstep, spm, and scm have values.

[0099] The session identifier seesid at the most recent startup of the application client is used to describe the unique cold start identifier when the attribution event occurs. Its value is a hash value that does not repeat among all users and can be used together with the user identifier to locate any startup of the application client by any user across the network.

[0100] The value of the type of the preset event type can include e, p, a, etc. Among them, e can be understood as the above-mentioned element trigger event, which can be a trigger for an element or some custom events on the element; p can be the above-mentioned page exposure event, which indicates that the event to which it is attributed is a page exposure event; a is used to describe automatic events, such as an automatic play event, etc.

[0101] The occurrence order of preset events within the exposure period of the page where the preset event is located can be represented by the parameter actseq, which can be used to identify the event order within a page exposure. During an exposure of the root page (rootpage), each time an interaction event (click / swipe / drop-down refresh, etc.) occurs, the value of actseq increases by 1 accordingly, and actseq is reset as the pgstep value of the root page of the element corresponding to the interaction event changes. That is, when the interaction event causes the exposed root page to change, pgstep increases by 1, and at the same time, actseq starts counting from 1 again.

[0102] The page exposure order corresponding to the page where the preset event occurs can be represented by the parameter pgstep, which is used to identify the exposure order of pages during a startup of the application client. For example, after a certain startup of the application client, page 1 (usually the home page) is exposed first, and then pages 2, 3, 4, 3, and 5 are exposed in sequence based on a series of user operation behaviors. Then the page exposure order is "Page 1: pgstep = 1; Page 2: pgstep = 2; Page 3: pgstep = 3; Page 4: pgstep = 4; Page 3: pgstep = 5; Page 5: pgstep = 5". During this startup of the client, page 3 is exposed twice, but the two exposures of page 3 have different exposure orders. When the application client is closed and cold-started next time, pgstep starts counting from 1 again.

[0103] In other words, pgstep can record the exposure order of all pages during this startup of the application client. It is for all pages during the current startup of the client. As long as a page is exposed, pgstep increases by 1 unit to indicate which page is the one being exposed after the client startup.

[0104] For example, there are two elements, A1 and A2, on page A; there are two elements, B1 and B2, on page B. After a certain startup of the client, the user operation path is "Enter page A - Click A1 - Click A2 - Enter page B - Click B1 - Click B2 - Return to page A - Click A1 - Click A2". Then the change process of pgstep and actseq is "Page A pgstep = 1 - pgstep = 1 / actseq = 1 - pgstep = 1 / actseq = 2 - Page B pgstep = 2 - pgstep = 2 / actseq = 1 - pgstep = 2 / actseq = 2 - Page A pgstep = 3 - pgstep = 3 / actseq = 1 - pgstep = 3 / actseq = 2".

[0105] Among them, pgstep=1 for page A means that page A is the first page exposed by the client during this period; pgstep=1 / actseq=1 means that clicking element A1 is the first interactive event that occurs in page A when page A is first exposed; pgstep=1 / actseq=2 means that clicking element A2 is the second interactive event that occurs in page A when page A is first exposed; pgstep=2 for page B means that page B is the second page exposed by the client during this period; pgstep=2 / actseq=1 means that in page B that is the second page exposed by the client at this time, clicking element B1 is the second interactive event that occurs in page B this time. pgstep=2 / actseq=2 means that in page B which is the second page exposed by the client this time, clicking element B2 is the second interactive event which occurs in page B this time; pgstep=3 for page A means that page A is the third page exposed after the client is started; pgstep=3 / actseq=1 means that in page A which is the third page exposed by the client this time, clicking element A1 is the first interactive event which is sent in page A this time; pgstep=3 / actseq=2 means that in page A which is the third page exposed by the client this time, clicking element A2 is the second interactive event which occurs in page A this time.

[0106] pgstep and actseq can distinguish between situations where the same page is exposed multiple times and situations where the same triggered interaction event occurs multiple times on the same page. They can also specifically determine which page each interaction event is in and which is the number of the interaction events.

[0107] Furthermore, the parameter actseq representing the event sequence number of the attribution event within the exposure period of the page where it is located can be configured to be reset with the change of the root page of the current interactive element, rather than with the change of the sub-page of the current interactive element. Because the root page is generally a fully blocked bottom page or home page, attribution analysis can be implemented across multiple sub-pages, rather than being limited to attribution analysis within a single sub-page.

[0108] The slot information spm of the buried point object associated with the preset event is composed of the buried point object identifier on the branch from the buried point object to its root page node and the position attribute information of the buried point object with the existence position attribute. The slot can be used to describe a unique position in different pages within the application client, and it has a value when the preset event is an element trigger event or a first page exposure event. For example, if the buried point object identifier of the buried point object associated with the preset event is oid1, its position attribute in the page is pos1, the buried point object identifier of its parent node is oid2, and there is no position attribute information, the parent node of its parent node is the root node, and the buried point object identifier of the root node is oid3, and its position attribute information in the page is pos3, then the slot information of the buried point object oid1 can be described as oid1:pos1|oid2|oid3:pos3.

[0109] The content information of the buried point object associated with the preset event may include a content identifier cid, a content type ctype, a content routing identifier ctraceid, and specific content information ctrp. The specific content information can be represented in the form of key-value pairs. For example, the content information of a certain buried point object can be described as cid1:ctype1:ctraceid1:ctrp1|cid2:ctype2:ctraceid2:ctrp2.

[0110] In step S130, based on the occurrence order of the preset events in the application client, add the to-be-reported buried point attribution parameter values corresponding to the preset events to the first preset storage container.

[0111] For example, according to the order of the preset events that occur successively, add the to-be-reported buried point attribution parameter values corresponding to the preset events to the first preset storage container in sequence. Among them, the first preset storage container may include a first queue.

[0112] In an exemplary implementation manner, it is possible to directly add the to-be-reported buried point attribution parameter values corresponding to each preset event to the queue based on the occurrence order of the preset events in the application client.

[0113] In another exemplary application scenario, during the interaction process of the application client, there may be a situation where the original operation is interrupted midway and then automatically continues to execute after the operation, such as a traffic reminder pop-up window being displayed midway or a reminder login interface being displayed midway due to not being logged in, etc. After the user operates the traffic reminder pop-up window or the reminder login interface and then continues to execute other operations, if these events are not excluded, the other operations that continue to execute will be directly attributed to the button click event of the traffic reminder pop-up window or the button click event of the reminder login interface, and this kind of attribution is obviously unreasonable.

[0114] Therefore, in the present disclosure, an attribution skipping ability for intermediate steps is provided. For example, a traffic reminder pop-up event and a reminder login event can be configured as preset events to be deleted. In this way, the to-be-reported buried point attribution parameter values corresponding to the preset events to be deleted are not stored in the first preset storage container. Then, in subsequent attribution, other events will not be attributed to the preset events to be deleted, thereby improving the accuracy of automatic buried point attribution.

[0115] Based on this, another specific implementation manner of step S130 may include: adding the to-be-reported buried point attribution parameter values corresponding to the preset events to the first preset storage container based on the occurrence order of the preset events other than the preset events to be deleted in the application client; the preset events to be deleted are determined according to the preset pages exposed and / or the preset elements triggered in the application client.

[0116] For example, the preset events to be deleted can be customized according to the user's needs. For example, the above-mentioned traffic reminder page exposure event and reminder login page exposure event can be configured as preset events to be deleted. In this way, when it is determined that the currently occurring preset event is a preset event to be deleted, such as the currently occurring page exposure event is the exposure event of the traffic reminder page, the to-be-reported buried point attribution parameter value of this event can continue to be automatically generated, but it is not added to the first preset storage container, or the to-be-reported buried point attribution parameter value corresponding to this event may not be generated. This exemplary embodiment does not make special limitations on this.

[0117] In an exemplary implementation manner, the first preset storage container may store a preset number of to-be-reported buried point attribution parameter values, where the preset number can be customized according to requirements. For example, the first preset storage container may store the latest 5 generated to-be-reported buried point attribution parameter values. In this way, while ensuring the attribution accuracy, resource space is saved, and the calculation amount in subsequent matching steps is reduced, improving the matching efficiency, and further improving the reporting efficiency of buried point information.

[0118] Continue to refer to Figure 1 , in step S140, according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event, the value of the target buried point attribution parameter is determined from the first preset storage container.

[0119] In an exemplary implementation manner, the buried point reporting event may include one or more of a page exposure event, an event of adding a list unit to a playlist, and an event that a list unit of a playlist is played. That is to say, the buried point reporting event may also be a certain preset event. The buried point reporting event can be customized according to requirements. The user can determine the buried point reporting event according to the event for which they need to perform buried point attribution. This exemplary embodiment does not make special limitations on this.

[0120] Within the application programming interface, for the stability of interface performance, often only a small amount of necessary information, such as resource IDs, etc., is selected for distribution in the external flow of the page. When a user operation is to open the corresponding underlying page, often a request needs to be sent first to obtain more information to support the jump or playback. At this time, the user can still click on other elements. Then, when the interface returns and a real page jump or playback occurs, if directly attributed automatically according to the order of event occurrence, it often goes wrong, resulting in incorrect attribution.

[0121] Therefore, in the present disclosure, a toid (target object identifier) attribute is added to the content information of the buried point object, which is used to identify the buried point object identifier oid of the target page to be opened by the current element, that is, the oid of the target page that can be opened after triggering the current element. In this way, when looking back for click events from the exposure of the target page, it can be accurately searched by matching according to the toid, improving the accuracy of buried point attribution.

[0122] Based on this, in an exemplary embodiment, the content information of the buried point object associated with the preset event includes a target object identifier, and the target object identifier includes the buried point object identifier of the root page of the page that can be exposed after triggering the buried point object associated with the preset event.

[0123] As described above, the buried point identifier of the buried point object exposed by the buried point reporting event can be matched with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container, so as to determine the value of the target buried point attribution parameter from the first preset storage container according to the matching result, and then attribute the buried point reporting event based on the value of the target buried point attribution parameter.

[0124] Figure 5 The flowchart shows a method for determining the value of the target buried point attribution parameter according to an embodiment of the present disclosure. Refer to Figure 5 This method may include steps S510 to S520.

[0125] In step S510, the buried point object identifier of the buried point object exposed by the buried point reporting event is matched with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container.

[0126] For example, as described above, the to-be-reported buried point attribution parameter value is generated according to the pit information and content information of the buried point object, and the content information of the buried point object includes a target object identifier. Therefore, the to-be-reported buried point attribution parameter value also includes a target object identifier. Therefore, the buried point object identifier of the buried point object reported by the buried point reporting event can be matched with the target object identifier included in each to-be-reported buried point attribution parameter value stored in the first preset storage container.

[0127] In step S520, based on the matching result, the value of the target buried point attribution parameter is determined.

[0128] Exemplarily, in combination with Figure 6 , the specific implementation manner of step S520 is further described. Figure 6 The flowchart shows a method for determining the value of the target buried point attribution parameter according to the matching result according to an embodiment of the present disclosure. Refer to Figure 6 , the method may include step S610 to step S650. Among them: in step S610, it is determined whether the matching is successful. If so, go to step S620 to step S640; otherwise, go to step S650; in step S620, based on the value of the buried point attribution parameter to be reported including the target object identifier with successful matching, the first value of the buried point attribution parameter to be reported is determined; in step S630, the second value of the buried point attribution parameter to be reported is determined from the first preset storage container; wherein, the second value of the buried point attribution parameter to be reported includes the value of the buried point attribution parameter to be reported corresponding to the most recent page exposure event stored in the first preset storage container; in step S640, based on the larger of the generation times of the first value of the buried point attribution parameter to be reported and the second value of the buried point attribution parameter to be reported, the value of the target buried point attribution parameter is determined; in step S650, based on the value of the buried point attribution parameter to be reported that was most recently added to the first preset storage container, the value of the target buried point attribution parameter is determined.

[0129] For example, when the matching is successful, the value of the buried point attribution parameter to be reported including the target object identifier with successful matching can be used as the first value of the buried point attribution parameter to be reported. Then, the value of the buried point attribution parameter to be reported corresponding to the most recent page exposure event stored in the first preset storage container is determined as the second value of the buried point attribution parameter to be reported. Based on the value of the buried point attribution parameter to be reported that was generated later among the first buried point attribution parameter value and the second buried point attribution parameter value, the value of the target buried point attribution parameter is determined.

[0130] Taking the case where a page 2 exposure event has occurred currently and the most recently added page exposure event in the first preset storage container is a page 1 exposure event as an example, page 2 is just about to start exposure, so the value of the to-be-reported buried point attribution parameter corresponding to the page 2 exposure event has not been added to the first preset storage container yet. In order to attribute the exposure event of page 2, the buried point object identifier of the root page of page 2 can be matched with the target object identifier included in the value of the to-be-reported buried point attribution parameter stored in the first preset storage container. If a certain value of the to-be-reported buried point attribution parameter is successfully matched, but its generation time is earlier than the value of the to-be-reported buried point attribution parameter corresponding to the page 1 exposure event, it means that a page 1 exposure event has occurred between the preset event indicated by the successfully matched value of the to-be-reported buried point attribution parameter and the page 2 exposure event. Then, the exposure event of page 2 should be attributed to the exposure event of page 1, rather than the preset event indicated by the successfully matched value of the to-be-reported buried point attribution parameter. Based on this, in order to accurately perform buried point attribution, when a match is successful, it is necessary to compare the generation time of the first successfully matched to-be-reported buried point attribution parameter value with the generation time of the second to-be-reported buried point attribution parameter value corresponding to the most recently added page exposure event in the first preset storage container, and use the preset event indicated by the to-be-reported buried point attribution parameter value with the later generation time to attribute the current buried point reporting event.

[0131] When the match fails, the value of the target buried point attribution parameter can be directly determined according to the value of the to-be-reported buried point attribution parameter that was most recently added to the first preset storage container.

[0132] Next, in combination with Figure 7 , the method for determining the value of the target buried point attribution parameter in the present disclosure will be further described. Referring to Figure 7 , the method for determining the value of the target buried point attribution parameter based on the buried point object identifier through matching may include steps S710 to S760. Among them: in step S710, in response to the occurrence of a root page exposure event, the buried point object identifier of the root page is matched with the target object identifier in the value of the to-be-reported buried point attribution parameter in the first preset storage container; in step S720, it is determined whether the match is successful. If the match is successful, go to step S730, otherwise go to step S760; in step S730, the second to-be-reported buried point attribution parameter value corresponding to the page exposure event that was most recently added to the first preset storage container is obtained; in step S740, the generation times in the first successfully matched to-be-reported buried point attribution parameter value and the second to-be-reported buried point attribution parameter value are compared;

[0133] In step S750, determine the value of the target buried point attribution parameter as the larger of the generation times of the first to-be-reported buried point attribution parameter value and the second to-be-reported buried point attribution parameter value; in step S760, determine the value of the target buried point attribution parameter according to the to-be-reported buried point attribution parameter value that was most recently added to the first preset storage container.

[0134] In an exemplary implementation, the type of the target buried point attribution parameter includes one or more of the first type, the second type, the third type, the fourth type, the fifth type, the sixth type, and the seventh type. Of course, the target buried point attribution parameter may also include other types, which can be custom-configured according to user needs, and this exemplary implementation does not make special limitations on this.

[0135] Among them, the target buried point attribution parameter of the first type is used to describe the exposure source of the root page of the page exposed by the buried point reporting event; the target buried point attribution parameter of the second type is used to describe the creation source of the root page of the page exposed by the buried point reporting event; the target buried point attribution parameter of the third type is used to describe the page exposure sources of multiple pages before the current page is exposed; the target buried point attribution parameter of the fourth type is used to describe the page creation sources of multiple pages before the current page is exposed; the target buried point attribution parameter of the fifth type is used to describe which page of the home page of the application client the current event occurs from; the target buried point attribution parameter of the sixth type is used to describe the source when a list unit is added to a playlist, such as the source when a song is added to a song playing category; the target buried point attribution parameter of the seventh type is used to describe the operation source of the content of the list unit in the playlist being played, such as the source when a song in the playlist starts playing.

[0136] In an exemplary implementation, when the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes the first type. In other words, when the buried point reporting event is a page exposure event, the type of the target buried point attribution parameter associated with the buried point object exposed by the page exposure event includes the first type.

[0137] Figure 8 shows a flowchart of a method for determining the value of the target buried point attribution parameter of the first type according to an embodiment of the present disclosure. Refer to Figure 8 , this method may include steps S810 to S820. Among them: in step S810, when a new page is exposed in the application client, match the buried point object identifier of the exposed new page with the target object identifiers in each to-be-reported buried point attribution parameter value stored in the first preset storage container; in step S820, determine the value of the target buried point attribution parameter of the first type according to the matching result.

[0138] For example, as described above, the target buried point attribution parameter of the first type is used to characterize the exposure source of the root page of the page exposed by the buried point reporting event, that is, the target buried point attribution parameter of the first type is updated when a new page is exposed. In other words, when a new root page is exposed, the target buried point attribution parameter value of the first type can be determined in the first preset storage container according to the buried point object identifier of the newly exposed root page, and the target buried point attribution parameter value of the first type is reported, so as to determine the exposure source of the newly exposed page based on the target buried point attribution parameter value of the first type, so as to attribute the source of the exposure of the new page.

[0139] Among them, the specific implementation manner of the above step S820 can refer to the specific implementation manner of the above step S520, and will not be elaborated here.

[0140] In an exemplary implementation manner, when the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter may also include a second type. In other words, when the buried point reporting event is a page exposure event, the type of the target buried point attribution parameter associated with the buried point object exposed by the page exposure event may include one or more of the first type and the second type.

[0141] Figure 9 The flowchart shows a method for determining the value of the target buried point attribution parameter of the second type according to an embodiment of the present disclosure. Refer to Figure 9 , the method may include step S910 to step S920. Among them: in step S910, when the page exposed in the application client is a newly created page, the buried point object identifier of the exposed page is matched with the target object identifier in each buried point attribution parameter value to be reported stored in the first preset storage container; in step S920, according to the matching result, the value of the target buried point attribution parameter of the second type is determined.

[0142] For example, as described above, the target buried point attribution parameter of the second type is used to characterize the creation source of the root page of the page exposed by the buried point reporting event, that is, the target buried point attribution parameter of the second type is updated when a new page is created. In other words, when an event of creating a new root page occurs, the value of the target buried point attribution parameter of the second type can be determined in the first preset storage container according to the buried point object identifier of the newly created root page, and the value of the target buried point attribution parameter of the second type is reported, so as to determine the source of the newly created root page based on the value of the target buried point attribution parameter of the second type, such as which element was clicked on which page to cause the creation of the current new root page, so as to attribute the creation of the newly created root page.

[0143] Among them, the specific implementation of the above step S920 can refer to the above step S520, and will not be elaborated here.

[0144] Figure 10 FIG. shows a flowchart of another method for determining the value of the target buried point attribution parameter of the first type according to an embodiment of the present disclosure. Refer to Figure 10 , the method may include steps S1010 to S1060. Among them: in step S1010, it is judged whether there is a new root page exposure currently. If so, go to step S1020; otherwise, go to step S1060. In step S1020, the buried point object identifier of the newly exposed root page is obtained. In step S1030, based on the buried point object identifier of the root page, the value of the target buried point attribution parameter is selected in the first preset storage container. In step S1040, the selected value of the target buried point attribution parameter is determined as the value of the buried point attribution parameter of the first type of the currently exposed root page. In step S1050, a to-be-reported buried point attribution parameter value corresponding to the root page to be exposed is generated and added to the first preset storage container, and then go to step S1060. In step S1060, the exposure is executed.

[0145] Among them, the specific implementation of selecting the value of the target buried point attribution parameter in the first preset storage container based on the buried point object identifier of the root page can refer to the above Figure 5 and Figure 6 shown process, and will not be elaborated here.

[0146] Similarly, the value of the target buried point attribution parameter of the second type can also be determined by the method shown above. Replace the above step S1010 with "judging whether there is a new root page created currently", and the rest of the steps remain unchanged, and will not be elaborated here. Figure 10 In the present disclosure, the target buried point attribution parameter of the first type and the target buried point attribution parameter of the second type are used to characterize the source of the currently exposed root page, and can be used to analyze which pit position was clicked on the previous page when a page switching event occurs, resulting in the exposure of the current page. Among them, the target buried point attribution parameter of the first type characterizes the exposure source of the currently exposed page, and it will be updated after the page returns from entering the lower-level page. The target buried point attribution parameter of the second type characterizes the creation source of the currently exposed page, and it will not be updated after entering the lower-level page and then returning.

[0147] Next, the above-mentioned target buried point attribution parameter of the first type and the target buried point attribution parameter of the second type will be further described in conjunction with

[0148] Next, in conjunction with Figure 11 the above-mentioned target buried point attribution parameter of the first type and the target buried point attribution parameter of the second type will be further described. As Figure 11As shown, the user clicks on Playlist 1 on Page 1, resulting in the first exposure of Page 2. Then, the user clicks on Playlist Card 2 on Page 2, leading to the first exposure of Page 3. Subsequently, the user clicks on Return Button 111 on Page 3, causing the second exposure of Page 2.

[0149] For the first exposure event of Page 2, the values of the target buried point attribution parameters of the first type and the second type are the same, both being the to-be-reported buried point attribution parameter values corresponding to the event of clicking on Playlist 1 on Page 1. That is, the exposure source and the creation source of Page 2 are both the event of clicking on Playlist 1 on Page 1. For the first exposure event of Page 3, the values of the target buried point attribution parameters of the first type and the second type are also the same, both being the to-be-reported buried point attribution parameter values corresponding to the event of clicking on Playlist Card 2 on Page 2.

[0150] However, for the second exposure event of Page 2, the values of the target buried point attribution parameters of the first type and the second type are different. The value of the target buried point attribution parameter of the first type is the to-be-reported buried point attribution parameter value corresponding to the event of clicking on Return Button 111 on Page 3. For the target buried point attribution parameter of the second type, since it is only updated when creating a new page and is not updated when returning from a lower-level page, the value of the target buried point attribution parameter of the second type during the second exposure of Page 2 is the same as that during the first exposure of Page 2, both being the to-be-reported buried point attribution parameter value corresponding to the event of clicking on Playlist 1 on Page 1 when creating Page 2.

[0151] In an exemplary implementation, when the buried point reporting event includes a page exposure event and the type of the target buried point attribution parameter includes the first type, the type of the target buried point attribution parameter can also include a third type.

[0152] Exemplarily, Figure 12 shows a flowchart of a method for determining the value of the target buried point attribution parameter of the third type according to an embodiment of the present disclosure. Referring to Figure 12 the method for determining the value of the target buried point attribution parameter of the third type may include steps S1210 to S1230. Among them:

[0153] In step S1210, based on the page exposure order in the application client, in response to the exposure of the root page in the application client, the value of the target buried point attribution parameter of the first type corresponding to the newly exposed root page is added to the second preset storage container; in step S1220, when the number of values of the target buried point attribution parameter of the first type stored in the second preset storage container is greater than the first preset value, the value of the target buried point attribution parameter of the first type with the earliest addition time in the second preset storage container is deleted from the second preset storage container; in step S1230, the value of the target buried point attribution parameter of the third type is determined according to the second preset storage container.

[0154] For example, the target buried point attribution parameter of the third type can be used to save the behavior links of multiple root page exposures before the current root page exposure. A queue with a length of N can be maintained, that is, the above-mentioned second preset storage container can include a second queue, and the first preset value can be N. When a new root page is exposed, the value of the target buried point attribution parameter of the first type determined according to the new root page exposure event is pushed to the top layer of the second queue. When the length of the second queue exceeds N, the value of the target buried point attribution parameter of the first type at the bottom of the second queue is popped out, so as to determine the value of the target buried point attribution parameter of the third type according to the second queue.

[0155] In other words, the value of the target buried point attribution parameter of the third type can be used to analyze the user behavior path that leads to the exposure of the current root page.

[0156] In an exemplary implementation manner, when the buried point reporting event includes a page exposure event and the type of the target buried point attribution parameter includes the second type, the type of the target buried point attribution parameter may also include the fourth type.

[0157] Exemplarily, Figure 13 shows a flowchart of a method for determining the value of the target buried point attribution parameter of the fourth type according to an embodiment of the present disclosure. Refer to Figure 13 and this method may include steps S1310 to S1330. Among them:

[0158] In step S1310, based on the page exposure order in the application client, in response to the exposure of the root page in the application client, the value of the target buried point attribution parameter of the second type corresponding to the newly exposed root page is added to the third preset storage container; in step S1320, when the number of values of the target buried point attribution parameter of the second type stored in the third preset storage container is greater than the second preset value, the value of the target buried point attribution parameter of the second type with the earliest addition time in the third preset storage container is deleted from the third preset storage container; in step S1330, the value of the target buried point attribution parameter of the fourth type is determined according to the third preset storage container.

[0159] For example, the target buried point attribution parameter of the fourth type can be used to save the behavior links created by multiple root pages before the exposure of the current root page. A queue with a length of M can be maintained. That is, the above-mentioned third preset storage container can include a third queue, and the second preset value can be M. When a new root page is exposed, the value of the target buried point attribution parameter of the second type determined according to the new root page exposure event is pushed to the top layer of the third queue. When the length of the third queue exceeds M, the value of the target buried point attribution parameter of the second type at the bottom of the third queue is popped out, so as to determine the value of the target buried point attribution parameter of the fourth type according to the third queue.

[0160] In other words, the value of the target buried point attribution parameter of the fourth type can be used to analyze the creation paths of multiple root pages before the creation of the current root page.

[0161] Taking the length of the third queue as 3, and the page exposure order after opening the application client being page 1, page 2, page 3, page 4, and the values of the target buried point attribution parameters of the second type determined at the time of page 1 exposure, page 2 exposure, page 3 exposure, and page 4 exposure being psrefer1, psrefer2, psrefer3, psrefer4 respectively as an example, at the time of page 1 exposure, the value of the third queue is [psrefer1]; at the time of page 2 exposure, the values stored in the third queue are [psrefer1, psrefer2]; at the time of page 3 exposure, the value of the third queue is [psrefer1, psrefer2, psrefer3]; at the time of page 4 exposure, the value of the third queue is [psrefer2, psrefer3, psrefer4].

[0162] By automatically generating the above-mentioned values of the target buried point attribution parameters of the third type and the fourth type, the operation paths that cause page exposure and the operation paths that cause page creation in the application client can be automatically attributed and analyzed, improving the accuracy and efficiency of page source analysis.

[0163] As can be seen from the foregoing analysis, based on the values of the target buried point attribution parameters of the foregoing first type or second type, the reasons for the current page exposure or creation can be analyzed. Based on the values of the target buried point attribution parameters of the foregoing third type or fourth type, multiple steps can be analyzed forward to obtain the behavior path that leads to the current page exposure or creation. However, in some scenarios, the user's behavior goes deeper continuously, resulting in an overly long attributable chain that can be traced as a whole. Moreover, the structure of the home page of an application client has a great impact on the user's perception and operations. Therefore, in certain cases, it is crucial for attribution analysis to consider the consumption depth and accumulation generated on the home page of the application client, and any number of steps of behavior after the home page should be attributable to a certain page on the home page.

[0164] Based on this, in the present disclosure, a fifth type of target buried point attribution parameter is provided. Through the value of the fifth type of target buried point attribution parameter, the source of any number of steps of behavior after the home page in the home page can be analyzed, that is, which page in the home page leads to any behavior after the home page.

[0165] In an exemplary implementation, when the target buried point attribution parameter includes the fifth type and the foregoing second type, the value of the fifth type of target buried point attribution parameter can be determined by Figure 14 the method shown. Referring to Figure 14 , this method may include step S1410 to step S1420.

[0166] In step S1410, the buried point object identifier of the buried point object exposed by the buried point reporting event is matched with a preset buried point object identifier.

[0167] Among them, the preset buried point object identifier includes the buried point object identifier corresponding to the root page of the home page of the application client. For example, Figure 11 page 1 in Figure 11 is the home page of a certain application client, which includes 7 root pages of "Comprehensive, Single Song, Playlist, Video, Lyrics, Sound, Podcast",

[0168] Continuing to refer to Figure 14 , in step S1420, according to the matching result, the value of the fifth type of target buried point attribution parameter is determined.

[0169] In an exemplary implementation, when the identifier of the buried point object exposed in the buried point reporting event matches the preset buried point object identifier, the value of the fifth type of target buried point attribution parameter can be determined according to the value of the second type of buried point attribution parameter corresponding to the buried point object indicated by the successfully matched preset buried point object identifier.

[0170] If the identifier of the buried point object exposed in the buried point reporting event matches the preset buried point object identifier, it indicates that the buried point object exposed in the current buried point reporting event is the buried point object corresponding to a certain root page of the home page. The value of the fifth type of target buried point attribution parameter can be directly updated according to the value of the second type of target buried point attribution parameter corresponding to the successfully matched root page, that is, the value of the fifth type of target buried point attribution parameter corresponding to the current buried point reporting event is determined to be the value of the second type of target buried point attribution parameter corresponding to the successfully matched root page.

[0171] In another exemplary implementation, when the identifier of the buried point object exposed in the buried point reporting event fails to match the preset buried point object identifier, the value of the fifth type of target buried point attribution parameter can be determined by Figure 15 the method shown. Referring to Figure 15 , when the identifier of the buried point object exposed in the buried point reporting event fails to match the preset buried point object identifier, the method for determining the value of the fifth type of target buried point attribution parameter may include steps S1510 to S1530. Among them:

[0172] In step S1510, when the identifier of the buried point object exposed in the buried point reporting event fails to match the preset buried point object identifier, obtain the identifier of the buried point object corresponding to the root page of the page where the buried point object exposed in the buried point reporting event is located.

[0173] For example, if the identifier of the buried point object exposed in the buried point reporting event fails to match the preset buried point object identifier, it indicates that the buried point object currently exposed in the buried point reporting event is not a certain root page of the home page and may be a sub-page of a certain root page. In order to attribute it to the root page, the identifier of the buried point object corresponding to the root page of the page where the buried point object exposed in the buried point reporting event is located can be obtained, and then the value of the fifth type of target buried point attribution parameter can be determined according to the subsequent steps S1520 and S1530.

[0174] In step S1520, match the identifier of the buried point object corresponding to the root page with the target object identifier in the value of the buried point attribution parameter to be reported stored in the first preset storage container to determine the target value of the buried point attribution parameter to be reported.

[0175] Exemplarily, a specific implementation of step S1520 may include: when the buried point object identifier corresponding to the root page matches the target object identifier in the to-be-reported buried point attribution parameter value stored in the first preset storage container, determining the target to-be-reported buried point attribution parameter value according to the successfully matched to-be-reported buried point attribution parameter value; when the buried point object identifier corresponding to the root page fails to match the target object identifier in the to-be-reported buried point attribution parameter value stored in the first preset storage container, determining the target to-be-reported buried point attribution parameter value according to the to-be-reported buried point attribution parameter value that was most recently added to the first preset storage container.

[0176] Next, in step S1530, the buried point object identifier included in the target to-be-reported attribution parameter value is matched with the preset buried point object identifier, and the value of the target buried point attribution parameter of the fifth type is determined according to the matching result.

[0177] Exemplarily, a specific implementation of step S1530 may include: when the buried point object identifier included in the target to-be-reported attribution parameter value matches the preset buried point object identifier, updating the value of the target buried point attribution parameter of the fifth type according to the value of the buried point attribution parameter of the second type corresponding to the buried point object indicated by the successfully matched preset buried point object identifier; when the buried point object identifier included in the target to-be-reported attribution parameter value fails to match the preset buried point object identifier, not updating the value of the target buried point attribution parameter of the fifth type.

[0178] For example, if the buried point object identifier included in the target to-be-reported attribution parameter value matches the preset buried point object identifier, it means that the current buried point reporting event can be attributed to the root page of the home page corresponding to the successfully matched preset buried point object identifier, so the value of the target buried point attribution parameter of the fifth type can be updated. If the match fails, it means that the current operation may not be performed on the new root page, so the value of the target buried point attribution parameter of the fifth type is not updated, that is, the value of the target buried point attribution parameter of the fifth type corresponding to the current buried point reporting event is the same as the value of the target buried point attribution parameter of the fifth type corresponding to the previous buried point reporting event.

[0179] In another exemplary implementation, the technical term "value of the target buried point attribution parameter of the second type" in the method for determining the value of the target buried point attribution parameter of the fifth type described above may also be replaced with "value of the target buried point attribution parameter of the first type", and other implementation processes remain unchanged, so as to determine the value of the target buried point attribution parameter of the fifth type based on the value of the target buried point attribution parameter of the first type corresponding to the root page of the home page, which will not be elaborated here.

[0180] Figure 16The flowchart shows another method for determining the value of the target buried point attribution parameter of the fifth type according to an embodiment of the present disclosure. Refer to Figure 16 , this method may include steps S1610 to S1680. Among them: in step S1610, match the buried point object identifier of the buried point object exposed by the buried point reporting event with the preset buried point object identifier; in step S1620, determine whether the matching is successful. If the matching is successful, go to step S1630, otherwise, go to step S1640; in step S1630, determine the value of the target buried point attribution parameter of the fifth type according to the value of the buried point attribution parameter of the second type corresponding to the buried point object indicated by the successfully matched preset buried point object identifier, and go to steps S1670 to S1680; in step S1640, obtain the buried point object identifier corresponding to the root page of the page where the buried point object exposed by the buried point reporting event is located; in step S1650, determine the target buried point attribution parameter value to be reported from the first preset storage container according to the buried point object identifier corresponding to the root page; in step S1660, determine whether the target buried point attribution parameter value to be reported passes the verification. If the verification passes, go to step S1670, otherwise go to step S1680; in step S1670, update the value of the target buried point attribution parameter of the fifth type in the common parameters of the buried point reporting; in step S1680, perform the exposure.

[0181] Among them, the specific implementation of step S1650 above may refer to the specific implementation of step S1520 above, and the specific implementation of step S1660 above may refer to the specific implementation of step S1530 above, which will not be elaborated here. It should be noted that the verification passing in step S1660 can be understood as that the buried point object identifier included in the target buried point attribution parameter value to be reported matches the preset buried point object identifier successfully, and the verification failure can be understood as that the buried point object identifier included in the target buried point attribution parameter value to be reported does not match the preset buried point object identifier.

[0182] In an exemplary scenario, list playback is an accompanying function, and the generation of its events may not require the user to keep operating and triggering. Taking song playback as an example, when the user clicks on a certain song in the playlist to play, all the songs in the entire playlist may be added to the song playback list, such as Figure 11 when clicking on playlist 1 on page 1, all the songs in playlist 1 are added to Figure 11in the song playlist displayed on page 2. In the auto-play scenario, when the played song ends after being clicked, without any operation by the user, the new song in the playlist can be played continuously, thus automatically generating a new play event. Through the values of one or more target buried point attribution parameters of the above-mentioned first type, second type, third type, fourth type, and fifth type, the attribution of the clicked song event can be accurately extracted. However, when a candidate auto-play event occurs, it is very likely that the user has generated other operation behaviors. At this time, attributing the auto-play event based on the values of the buried point attribution parameters to be reported corresponding to each operation behavior during auto-play is surely inaccurate.

[0183] To ensure the accuracy of auto-play event attribution, in the present disclosure, the event of a list unit being added to the playlist can be attributed through the target buried point attribution parameter of the sixth type, and the play event of the list unit in the playlist can be attributed through the target buried point attribution parameter of the seventh type.

[0184] Based on this, in an exemplary implementation manner, the buried point reporting event can include the event of adding a list unit to the playlist. When the buried point reporting event includes the event of adding a list unit to the playlist, the type of the target buried point attribution parameter can also include the sixth type, where the target buried point attribution parameter of the sixth type is used to characterize the reason for the list unit being added to the playlist.

[0185] Figure 17 shows a schematic flowchart of a method for determining the value of the target buried point attribution parameter of the sixth type according to an embodiment of the present disclosure. Refer to Figure 17 , this method may include steps S1710 to step S1720. Among them:

[0186] In step S1710, in response to the event of adding a list unit to the playlist occurring in the application client, the buried point object identifier corresponding to the buried point object exposed by the event of adding a list unit to the playlist is matched with the target object identifier included in the values of the buried point attribution parameters to be reported stored in the first preset storage container;

[0187] In step S1720, according to the matching result, the value of the target buried point attribution parameter of the sixth type is determined.

[0188] For example, when the event reported by data logging includes the event of adding a list unit to a playlist, a specific implementation of the above step S510 may include step S1710, and a specific implementation of the above step S520 may include step S1720. Among them, the specific implementation of step S1720 may refer to the specific implementation of the above step S520, and only need to replace the technical term "value of the target data logging attribution parameter" in the specific implementation of step S520 with "value of the target data logging attribution parameter of the sixth type", which will not be elaborated here.

[0189] In other words, the type of the target data logging attribution parameter associated with the data logging object exposed by the event of adding a list unit to a playlist includes the sixth type. The target data logging attribution parameter of the sixth type can be pre-associated with the data logging objects that may be exposed by the event of adding a list unit to a playlist. In this way, when the event of adding a list unit to a playlist occurs in the application client, the value of the target data logging attribution parameter of the sixth type can be directly determined based on the target data logging attribution parameter of the sixth type pre-associated with the data logging object exposed by this event, based on the above steps S1710 to S1720.

[0190] It should be noted that for the above first type, second type, third type, fourth type, and fifth type of target data logging attribution parameters, they can also be pre-associated with the data logging objects exposed by the corresponding data logging reporting events. In this way, when the corresponding events occur in the application client, the values of the target data logging attribution parameters of the corresponding types can be directly determined according to the types of the target data logging attribution parameters associated with the corresponding events.

[0191] The source of the list unit added to the playlist can be attributed by the value of the target data logging attribution parameter of the sixth type determined. For example, when the playlist is a song playlist, the reason why a certain song is added to the song playlist can be analyzed.

[0192] In an exemplary implementation, the data logging reporting event may further include the event that a list unit of a playlist is played. When the data logging reporting event includes the event that a list unit of a playlist is played, the type of the target data logging attribution parameter includes the seventh type. Among them, the target data logging attribution parameter of the seventh type is used to characterize the reason why the list unit in the playlist is played.

[0193] Exemplarily, Figure 18 shows a flowchart of a method for determining the value of the target data logging attribution parameter of the seventh type according to an embodiment of the present disclosure. Refer to Figure 18 and this method may include steps S1810 to S1820. Among them:

[0194] In step S1810, in response to the event that a list unit in the playlist is played by the application client, match the identifier of the buried point object exposed by the event that the list unit is played with the target object identifier included in the value of the buried point attribution parameter to be reported stored in the first preset storage container;

[0195] In step S1820, determine the value of the target buried point attribution parameter of the seventh type according to the matching result.

[0196] For example, in the case where the buried point reporting event includes the event that a list unit of the playlist is played, a specific implementation manner of the above step S510 may include step S1810, and a specific implementation manner of the above step S520 may include step S1820. Among them, the specific implementation manner of step S1820 may refer to the specific implementation manner of the above step S520, and only need to replace the technical term "value of the target buried point attribution parameter" in the specific implementation manner of step S520 with "value of the target buried point attribution parameter of the seventh type", and details will not be elaborated here.

[0197] In other words, the type of the target buried point attribution parameter associated with the buried point object exposed by the event that a list unit in the playlist is played includes the seventh type. The target buried point attribution parameter of the seventh type can be associated with the buried point object that may be exposed by the event that a list unit in the playlist is played in advance. In this way, when the event that a list unit in the playlist is played occurs in the application client, the value of the target buried point attribution parameter of the seventh type pre-associated with the buried point object exposed by this event can be directly used to determine the value of the target buried point attribution parameter of the seventh type based on the above steps S1810 to S1820.

[0198] The value of the target buried point attribution parameter of the seventh type determined can be used to attribute the event that the content in any list unit in the playlist is played. For example, when the playlist is a song playlist, the origin of the operation of starting to play a song can be analyzed, that is, analyze the reason why a certain song is played.

[0199] Next, taking Figure 19 the process schematic diagram of the user operation behavior in an exemplary embodiment of the present disclosure shown as an example, the values of the target buried point attribution parameters of the sixth type and the seventh type will be further described. Refer to Figure 19 , in page 1, that is, the search result page, a song list is displayed. Click on the song unit song_2, add 6 songs to the playlist, and start playing from song_2. At the same time, enter Figure 19Page 2 in it, which is the playing page. At this time, for Page 2, the value of the buried point attribution parameter of the first type is the value of the buried point attribution parameter to be reported corresponding to the click event of the song unit of song_2 in the song list on the search result page.

[0200] Take the case where actseq = 1 and pgstep = 3 for the search result page event in Figure 19 as an example. When clicking on song_2 on the search result page, the corresponding actseq = 2 and pgstep = 3 for this event. The pit information of the buried point object exposed is song2|search result page. Clicking on song_2 on the search result page can cause 6 songs on the search result page to be added to the playlist and open the playing page (such as Figure 9 Page 2 in it). Then, start playing song_2 on the playing page. At this time, actseq = 1 and pgstep = 4.

[0201] After clicking on song_2 on the search result page and adding 6 songs to the playlist, the songs in the playlist can be automatically played starting from song_2. When the song is automatically played to song_4, the user clicks on Figure 19 the control 191 for playing the next song on Page 2 of Figure 19 so that the playing song switches to song_5. The corresponding actseq = 2 and pgstep = 4 for the event of clicking on control 191. Then, during the playing of song_5, the user clicks on Figure 19 song_x2 on Page 3 of Figure 19 thus adding song_x2 to the playlist behind the currently playing song song_5. The generated new playlist is as shown in Page 4 of Figure 19 . Take the case where actseq = 1 and pgstep = 10 when the user opens Page 3. When the user clicks on song_x2, actseq = 2 and pgstep = 11.

[0202] For songs song_1, song_2, song_3, song_4, song_5, and song_6, they are all added to the playlist when clicking on song_2 on the search result page. The values of the target buried point attribution parameters of the sixth type corresponding to them are the same and can all be expressed as [e][2][3][song_2|search result page]. For song_x2, it is added to the playlist when clicked on the personal homepage. Therefore, the value of the target buried point attribution parameter of the sixth type corresponding to it can be expressed as [e][2]

[11] [song_x2|personal homepage].

[0203] For the playback of song song_2, the direct cause is the click on song_2 in the search result page. The value of the target buried point attribution parameter of the corresponding seventh type can be expressed as [e][2][3][song_2|search result page]. For the playback of song_3 and song_4, it is that the player automatically switches to the next song. Therefore, the values of the target buried point attribution parameter of the seventh type corresponding to the playback events of song_3 and song_4 can both be auto_next. For song song_5, it is played when the "play next" control is clicked on the playback page. The value of the target buried point attribution parameter of the corresponding seventh type can be expressed as [e][2][4][play next control|playback page].

[0204] Through the above-mentioned target buried point attribution parameters of the first type, second type, third type, fourth type, fifth type, sixth type, and seventh type, various behaviors in the application client can be automatically attributed. Furthermore, the values of the target buried point attribution parameters of the corresponding types can be reported to improve the efficiency of buried point attribution.

[0205] Next, continue to refer to Figure 1 , in step S150, based on the value of the target buried point attribution parameter, buried point information reporting is performed on the buried point object exposed by the buried point reporting event.

[0206] Exemplarily, a specific implementation manner of step S150 may include: using the value of the target buried point attribution parameter as the value of the buried point information reporting parameter of the buried point object exposed by the buried point reporting event to perform buried point information reporting on the buried point object exposed by the buried point reporting event.

[0207] For example, corresponding buried point information reporting parameters can be pre-configured for different buried point objects. The configured buried point information reporting parameters may include the above-mentioned target buried point attribution parameters. In this way, when a buried point reporting event occurs in the application client, causing the corresponding buried point object to be exposed, the value of the target buried point attribution parameter corresponding to the exposed buried point object can be used as one of the buried point information reporting parameters to report the buried point information. The business side can directly obtain the cause of the event that occurred in the application client based on the reported buried point information, improving the efficiency of buried point attribution analysis. Moreover, the attribution is performed during the buried point information reporting process. Compared with the method of performing attribution after sorting on the analysis side, since there is no delay in buried point data, the accuracy of buried point attribution can be improved.

[0208] In an exemplary scenario, for an application with a large historical inventory, it is often difficult to ensure that all interactive and meaningful slots are instrumented. When some slots are not covered by instrumentation (i.e., the oid identifier is not set, i.e., unknown), when a new page exposure or other event occurs upon clicking on such a slot, since the slot is not configured with an oid identifier, it is impossible to automatically attribute it based on the above method. In this way, the event information on the current slot will be lost, and the new page exposure caused by the current event will be attributed to other events before the current event, resulting in attribution errors. To solve this problem, a preset identification field is introduced in the present disclosure for identification, and the attribution of events occurring on slots without instrumentation is downgraded to the page where the slot is located. Among them, the preset identification field can be customized according to requirements. For example, the preset identification field can be the undefined-xpath field. Of course, it can also be other fields, and this exemplary embodiment does not make special limitations on this.

[0209] Based on this, the method for reporting instrumentation information in the present disclosure may further include: when a preset event occurs in the application client, if there is no associated instrumentation object for the preset event, determine the root page where the element targeted by the preset event is located; according to the instrumentation attribution parameter value to be reported corresponding to the root page and the preset identification field, determine the instrumentation attribution parameter value to be reported corresponding to the preset event; where the preset identification field is used to mark that the instrumentation attribution parameter value to be reported is the value generated after triggering a position in the application client without an instrumentation object.

[0210] For example, no instrumentation object identifier is configured for the element e1 in page A, that is, there is no instrumentation at the position where the element e1 in page A is located. However, when the user operates in the application client and clicks on the element e1 in page A, since no instrumentation object identifier is configured for it, that is, there is no instrumentation at the position of the element e1 in page A, the slot information at this position cannot be characterized, and the instrumentation attribution parameter value to be reported for this position cannot be automatically generated. At this time, the instrumentation attribution parameter value corresponding to the exposure of the root page A where the element e1 is located can be obtained, and the instrumentation attribution parameter value and the preset identification field are concatenated to obtain the instrumentation attribution parameter value corresponding to the click event of the element e1 in page A, and it is stored in the first preset storage container.

[0211] Taking the example that the exposure of page B is caused by the click of element e1 on page A, when attributing the exposure event of page B, there may be two successfully matched to-be-reported buried point attribution parameter values in the first preset storage container. One is the to-be-reported buried point attribution parameter value 1 corresponding to the exposure event of page A, and the other is the to-be-reported buried point attribution parameter value 2 corresponding to the click event of element e1 on page A. The to-be-reported buried point attribution parameter value with the latest generation time can be determined as the target buried point attribution parameter value corresponding to the exposure event of page B. Certainly, there is the exposure event of page A first, and then the click event of element e1 on page A. So the value of the target buried point attribution parameter corresponding to the exposure event of page B is the to-be-reported buried point attribution parameter value 2. If there is no successful match, then directly determine the most recently added to-be-reported buried point attribution parameter value 2 as the target buried point attribution parameter value corresponding to the exposure event of page B, so as to attribute the exposure event of page B to a relatively accurate position. Although there is no accurate pit information to represent the attributed position, at least it can be known from the attribution result that the exposure of page B is not the exposure of page A, but the click event at a non-buried point position on page A.

[0212] In other words, when subsequently troubleshooting the buried points, it is possible to directly know from the preset identification field that there is a non-buried point position on page A and this position has been triggered by the user, so that business personnel can quickly find the non-buried point position in subsequent analysis and determine whether it is necessary to set a buried point at this position.

[0213] In the present disclosure, based on the general attribution ability and attribution format for buried point objects, to-be-reported buried point attribution parameter values are generated to automatically generate and record user behavior buried points, and then in various complex business scenarios, automatic attribution of buried point reporting events can be realized, improving the efficiency of buried point attribution.

[0214] At the same time, based on the general attribution ability and attribution format, to-be-reported buried point attribution parameter values are generated to automatically attribute the buried point reporting events by matching the target object identifier included in the to-be-reported buried point attribution parameter values and the buried point object identifier of the exposed buried point reporting event, which can improve the accuracy of buried point attribution. And based on the general buried point attribution ability, the maintenance cost of buried point attribution can be reduced.

[0215] Furthermore, in the present disclosure, by considering situations such as the exposure event of the second page and the automatic trigger event, accurate attribution can be performed on the entry from a third-party application to the application client, the automatic playback event in the application client, etc., ensuring the accuracy of automatic buried point attribution.

[0216] In addition, in the present disclosure, different events in the application client can be accurately attributed from different aspects based on the values of target buried point attribution parameters of multiple types.

[0217] Exemplary Device

[0218] An exemplary embodiment of the present disclosure also provides a buried point information reporting device. Refer to Figure 20 As shown, the buried point information reporting device 2000 may include a preset event response module 2010, a to-be-reported buried point attribution parameter value generation module 2020, an addition module 2030, a target buried point attribution parameter value determination module 2040, and a buried point information reporting module 2050, where:

[0219] The preset event response module 2010 is configured to, in response to the occurrence of a preset event in the application client, determine the buried point object associated with the preset event; the to-be-reported buried point attribution parameter value generation module 2020 is configured to generate the to-be-reported buried point attribution parameter value corresponding to the preset event according to the pit information and content information of the buried point object associated with the preset event; the addition module 2030 is configured to add the to-be-reported buried point attribution parameter value corresponding to the preset event to a first preset storage container based on the occurrence order of the preset event in the application client; the target buried point attribution parameter value determination module 2040 is configured to determine the value of the target buried point attribution parameter from the first preset storage container according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event; the buried point information reporting module 2050 is configured to perform buried point information reporting on the buried point object exposed by the target buried point reporting event based on the value of the target buried point attribution parameter.

[0220] In an optional embodiment, the preset event includes one or more of an event that an element on a page is triggered, a page exposure event, and an automatic trigger event; wherein, when the preset event includes a page exposure event, the page exposure event includes a first page exposure event and / or a second page exposure event, the first page exposure event is determined based on an event that causes page exposure in the application client due to an operation in the application client, and the second page exposure event is determined based on an event that causes page exposure in the application client due to an operation in a third-party application.

[0221] In an alternative embodiment, the preset event response module 2010 may be specifically configured as follows: when the preset event includes the event that an element in the page is triggered, in response to the occurrence of the event that an element in the page is triggered in the application client, determine the buried point object associated with the preset event according to the triggered element; when the preset event includes the first page exposure event, in response to the occurrence of the first page exposure event in the application client, determine the buried point object associated with the preset event according to the root page of the page where the exposure ends; when the preset event includes the second page exposure event, in response to the occurrence of the second page exposure event in the application client, determine the buried point object associated with the preset event according to the buried point object pre-associated with the second page exposure event; when the preset event includes the automatic trigger event, in response to the occurrence of the automatic trigger event in the application client, determine the buried point object associated with the preset event according to the buried point object pre-associated with the automatic trigger event.

[0222] In an alternative embodiment, based on the foregoing embodiment, the to-be-reported buried point attribution parameter value generation module 2020 may be specifically configured as follows: generate the to-be-reported buried point attribution parameter value corresponding to the preset event according to the type of the preset event, the occurrence order of the preset event within the exposure period of the page where the preset event is located, the page exposure order corresponding to the page where the preset event occurs, the slot information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event; wherein, after the application client is started, each time a page is exposed, the value of the page exposure order increases by a unit value, and the value of the page exposure order restarts counting with the restart of the application client.

[0223] In an alternative embodiment, based on the foregoing embodiment, the to-be-reported buried point attribution parameter value generation module 2020 may also be configured as follows: generate the to-be-reported buried point attribution parameter value corresponding to the preset event according to the session identifier at the most recent startup of the application client, the slot information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event.

[0224] In an alternative embodiment, based on the foregoing embodiment, the content information of the buried point object associated with the preset event in the to-be-reported buried point attribution parameter value generation module 2020 includes a target object identifier, and the target object identifier includes the buried point object identifier of the root page of the page that can be exposed after the buried point object is triggered.

[0225] In an alternative embodiment, based on the foregoing embodiment, the target buried point attribution parameter value determination module 2040 may be specifically configured to: match the buried point object identifier of the exposed buried point object with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container; and determine the value of the target buried point attribution parameter according to the matching result.

[0226] In an alternative embodiment, determining the value of the target buried point attribution parameter according to the matching result includes: when the matching is successful, determining the value of the target buried point attribution parameter in the following manner: determining a first to-be-reported buried point attribution parameter value according to the to-be-reported buried point attribution parameter value including the successfully matched target object identifier; determining a second to-be-reported buried point attribution parameter value from the first preset storage container, where the second to-be-reported buried point attribution parameter value includes the to-be-reported buried point attribution parameter value corresponding to the most recent page exposure event stored in the first preset storage container; and determining the value of the target buried point attribution parameter according to the one with the larger generation time among the first to-be-reported buried point attribution parameter value and the second to-be-reported buried point attribution parameter value; when the matching fails, determining the value of the target buried point attribution parameter in the following manner: determining the value of the target buried point attribution parameter according to the to-be-reported buried point attribution parameter value that was most recently added to the first preset storage container.

[0227] In an alternative embodiment, based on the foregoing embodiment, when the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes a first type; matching the buried point object identifier of the exposed buried point object with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container includes: when a new page is exposed in the application client, matching the buried point object identifier of the newly exposed page with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result includes: determining the value of the target buried point attribution parameter of the first type according to the matching result; the target buried point attribution parameter of the first type is used to characterize the exposure source of the root page of the page exposed by the buried point reporting event, and the target buried point attribution parameter of the first type is updated when a new page is exposed.

[0228] In an alternative embodiment, based on the foregoing embodiment, when the buried point reporting event includes a page exposure event, the target buried point attribution parameter includes a second type; matching the buried point object identifier of the exposed buried point object with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container includes: when the page exposed in the application client is a newly created page, matching the buried point object identifier of the exposed page with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result includes: determining the value of the target buried point attribution parameter of the second type according to the matching result; the target buried point attribution parameter of the second type is used to characterize the creation source of the root page of the page exposed by the buried point reporting event, and the target buried point attribution parameter of the second type is updated when a new page is created.

[0229] In an alternative embodiment, based on the foregoing embodiment, when the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes a third type and a first type, the method for determining the value of the target buried point attribution parameter of the third type includes: based on the page exposure order in the application client, in response to the occurrence of root page exposure in the application client, adding the value of the target buried point attribution parameter of the first type corresponding to the newly exposed root page to a second preset storage container; when the number of values of the target buried point attribution parameter of the first type stored in the second preset storage container is greater than a first preset value, deleting the value of the target buried point attribution parameter of the first type with the earliest addition time from the second preset storage container; determining the value of the target buried point attribution parameter of the third type according to the second preset storage container.

[0230] In an alternative embodiment, based on the foregoing embodiment, when the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes a fourth type and a second type, the method for determining the value of the target buried point attribution parameter of the fourth type includes: based on the page exposure order in the application client, in response to the occurrence of root page exposure in the application client, adding the value of the target buried point attribution parameter of the second type corresponding to the newly exposed root page to a third preset storage container; when the number of values of the target buried point attribution parameter of the second type stored in the third preset storage container is greater than a second preset value, deleting the value of the target buried point attribution parameter of the second type with the earliest addition time from the third preset storage container; determining the value of the target buried point attribution parameter of the fourth type according to the third preset storage container.

[0231] In an alternative embodiment, based on the foregoing embodiment, when the types of the target buried point attribution parameters include the fifth type and the second type, the method for determining the value of the target buried point attribution parameter of the fifth type includes: matching the buried point object identifier of the buried point object exposed by the buried point reporting event with a preset buried point object identifier; when the matching is successful, determining the value of the target buried point attribution parameter of the fifth type according to the value of the buried point attribution parameter of the second type corresponding to the buried point object indicated by the successfully matched preset buried point object identifier; wherein, the preset buried point object identifier includes the buried point object identifier corresponding to the root page of the home page of the application client.

[0232] In an alternative embodiment, based on the foregoing embodiment, when the matching between the buried point object identifier of the buried point object exposed by the buried point reporting event and the preset buried point object identifier fails, the method for determining the value of the target buried point attribution parameter of the fifth type includes: obtaining the buried point object identifier corresponding to the root page of the page where the buried point object exposed by the buried point reporting event is located; matching the buried point object identifier corresponding to the root page with the target object identifier in the to-be-reported buried point attribution parameter values stored in the first preset storage container to determine a target to-be-reported attribution parameter value; matching the buried point object identifier included in the target to-be-reported attribution parameter value with the preset buried point object identifier, and determining the value of the target buried point attribution parameter of the fifth type according to the matching result.

[0233] In an alternative embodiment, based on the foregoing embodiment, the matching between the buried point object identifier corresponding to the root page and the target object identifier in the to-be-reported buried point attribution parameter values stored in the first preset storage container to determine a target to-be-reported attribution parameter value includes: when the matching is successful, determining the target to-be-reported buried point attribution parameter value according to the successfully matched to-be-reported buried point attribution parameter value; when the matching fails, determining the target to-be-reported buried point attribution parameter value according to the to-be-reported buried point attribution parameter value that was most recently added to the first preset storage container.

[0234] In an alternative embodiment, based on the foregoing embodiment, the matching between the buried point object identifier included in the target to-be-reported buried point attribution parameter value and the preset buried point object identifier, and determining the value of the target buried point attribution parameter of the fifth type according to the matching result includes:

[0235] when the matching is successful, updating the value of the target buried point attribution parameter of the fifth type according to the value of the buried point attribution parameter of the second type corresponding to the buried point object indicated by the successfully matched preset buried point object identifier; when the matching fails, not updating the value of the target buried point attribution parameter of the fifth type.

[0236] In an alternative embodiment, based on the foregoing embodiment, when the buried point reporting event includes the event of adding a list unit to a playlist, the type of the target buried point attribution parameter includes a sixth type; the matching of the buried point object identifier of the exposed buried point object with the target object identifier in each of the to-be-reported buried point attribution parameter values stored in the first preset storage container includes: in response to the application client generating an event of adding a list unit to a playlist, matching the buried point object identifier corresponding to the buried point object exposed by the event of adding a list unit to a playlist with the target object identifier included in the to-be-reported buried point attribution parameter values stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result includes: determining the value of the target buried point attribution parameter of the sixth type according to the matching result; wherein, the target buried point attribution parameter of the sixth type is used to characterize the reason for adding the list unit to the playlist.

[0237] In an alternative embodiment, based on the foregoing embodiment, when the buried point reporting event includes the event that a list unit of a playlist is played, the type of the target buried point attribution parameter includes a seventh type; the matching of the buried point object identifier of the exposed buried point object with the target object identifier in each of the to-be-reported buried point attribution parameter values stored in the first preset storage container includes: in response to the application client generating an event that a list unit in a playlist is played, matching the buried point object identifier of the buried point object exposed by the event that the list unit is played with the target object identifier included in the to-be-reported buried point attribution parameter values stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result includes: determining the value of the target buried point attribution parameter of the seventh type according to the matching result; wherein, the target buried point attribution parameter of the seventh type is used to characterize the reason for playing the list unit in the playlist.

[0238] In an alternative embodiment, based on the foregoing embodiment, the adding module 2030 may be specifically configured to: based on the occurrence order of preset events other than the preset to-be-deleted event in the application client, add the to-be-reported buried point attribution parameter values corresponding to the preset events to the first preset storage container; the preset to-be-deleted event is determined according to a preset page exposed in the application client and / or a preset element triggered.

[0239] In an alternative embodiment, based on the foregoing embodiment, the buried point information reporting device 2100 may further include a buried point attribution parameter value generation module for positions without buried points to be reported, which may be specifically configured to: when a preset event occurs in the application client, if there is no associated buried point object for the preset event, determine the root page where the element targeted by the preset event is located, and determine the buried point attribution parameter value to be reported corresponding to the preset event according to the buried point attribution parameter value to be reported corresponding to the root page and a preset identification field; wherein, the preset identification field is used to identify that the buried point attribution parameter value to be reported is generated after triggering a position without a buried point object in the application client.

[0240] In an alternative embodiment, based on the foregoing embodiment, the buried point information reporting module 2050 may be specifically configured to: use the value of the target buried point attribution parameter as the value of the buried point information reporting parameter of the buried point object exposed by the buried point reporting event, so as to report the buried point information of the buried point object exposed by the buried point reporting event.

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

[0242] Exemplary Storage Medium

[0243] The storage medium of the exemplary embodiment of the present disclosure will be described below.

[0244] In this exemplary embodiment, any of the above methods can be implemented by a program product. For example, a portable compact disc read-only memory (CD-ROM) can be used and includes 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. In this document, a readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device.

[0245] The program product can adopt any combination of one or more readable media. The readable media can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0246] A computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The readable signal medium may also be any readable medium other than a readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0247] The program code contained on the readable medium can be transmitted by any appropriate medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0248] The program code for performing the operations of the present disclosure can be written in any combination of one or more programming languages. The programming languages include object-oriented programming languages such as Java, C++, etc., and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user computing device and partially on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can 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 can be connected to an external computing device (e.g., by connecting through the Internet using an Internet service provider).

[0249] Exemplary Electronic Device

[0250] Reference Figure 21 An electronic device according to an exemplary embodiment of the present disclosure will be described. The electronic device can be a client or a server.

[0251] Figure 21 The displayed electronic device 2100 is merely an example and should not impose any limitation on the functions and usage scope of the embodiments of the present disclosure.

[0252] As Figure 21 shown, the electronic device 2100 is presented in the form of a general-purpose computing device. The components of the electronic device 2100 may include but are not limited to: at least one processing unit 2110, at least one storage unit 2120, a bus 2130 connecting different system components (including the storage unit 2120 and the processing unit 2110), and a display unit 2140. Among them, the storage unit stores program code, and the program code can be executed by the processing unit 2110, so that the processing unit 2110 executes the steps according to various exemplary embodiments of the present disclosure described in the "Exemplary Method" section of this specification. For example, the processing unit 2110 can execute asFigure 1 , Figures 5 to 10 , Figures 12 to 18 The method steps shown in the above, etc.

[0253] The storage unit 2120 may include volatile storage units, such as a random access memory (RAM) 1321 and / or a cache storage unit 2122, and may further include a read-only memory (ROM) 2123.

[0254] The storage unit 2120 may also include a program / utilities 2124 having a set (at least one) of program modules 2125. Such program modules 2125 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment.

[0255] The bus 2130 may include a data bus, an address bus, and a control bus.

[0256] The electronic device 2100 may also communicate with one or more external devices 2200 (such as a keyboard, a pointing device, a Bluetooth device, etc.). Such communication may be performed through an input / output (I / O) interface 1350. The electronic device 2100 further includes a display unit 2140, which is connected to the input / output (I / O) interface 2150 for display. Also, the electronic device 2100 may communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 2160. As shown in the figure, the network adapter 1360 communicates with other modules of the electronic device 2100 through the bus 1330. 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 2100, 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.

[0257] It should be noted that although several modules or sub-modules of the device are mentioned in the above detailed description, such a 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 of the above-described units / modules may be embodied in one unit / module. Conversely, the features and functions of one unit / module described above may be further divided and embodied by multiple units / modules.

[0258] Moreover, although the operations of the methods of the present disclosure are depicted in the figures in a particular order, this is not a requirement or implication that the operations must be performed in that particular order, or that all of the illustrated operations must be performed to achieve the desired results. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step and performed, and / or one step may be decomposed into multiple steps and performed.

[0259] Although the spirit and principles 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 specific embodiments disclosed, and the division of each aspect does not mean that the features in these aspects cannot be combined for benefits. Such division is only for convenience of expression. The present disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A method for reporting buried point information, characterized in that, Including: In response to a preset event occurring in the application client, determining the buried point object associated with the preset event; Generating a to-be-reported buried point attribution parameter value corresponding to the preset event according to the pit position information and content information of the buried point object associated with the preset event; Based on the occurrence order of the preset events in the application client, adding the to-be-reported buried point attribution parameter value corresponding to the preset event to the first preset storage container; According to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event, determining the value of the target buried point attribution parameter from the first preset storage container; Based on the value of the target buried point attribution parameter, reporting buried point information for the buried point object exposed by the buried point reporting event; Wherein, the content information of the buried point object associated with the preset event includes a target object identifier, and the target object identifier includes the buried point object identifier of the root page of the page that can be exposed after triggering the buried point object; The determining the value of the target buried point attribution parameter from the first preset storage container according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event includes: matching the buried point object identifier of the exposed buried point object with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container; When the matching is successful, determining the value of the target buried point attribution parameter in the following manner: determining a first to-be-reported buried point attribution parameter value according to the to-be-reported buried point attribution parameter value including the successfully matched target object identifier; determining a second to-be-reported buried point attribution parameter value from the first preset storage container, where the second to-be-reported buried point attribution parameter value includes the to-be-reported buried point attribution parameter value corresponding to the most recent page exposure event stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the larger one of the generation times in the first to-be-reported buried point attribution parameter value and the second to-be-reported buried point attribution parameter value; When the matching fails, determining the value of the target buried point attribution parameter in the following manner: determining the value of the target buried point attribution parameter according to the most recently added to-be-reported buried point attribution parameter value in the first preset storage container; 2. The method for reporting buried point information according to claim 1, wherein, The preset event includes one or more of an event that an element in a page is triggered, a page exposure event, and an automatic trigger event; Wherein, when the preset event includes a page exposure event, the page exposure event includes a first page exposure event and / or a second page exposure event. The first page exposure event is determined based on an event that causes a page exposure in the application client due to an operation in the application client, and the second page exposure event is determined based on an event that causes a page exposure in the application client due to an operation in a third-party application; 3. The method for reporting buried point information according to claim 2, wherein The responding to a preset event occurring in the application client and determining the buried point object associated with the preset event includes: When the preset event includes the event that an element in the page is triggered, in response to the occurrence of the event that an element in the page is triggered in the application client, determine the buried point object associated with the preset event according to the triggered element; When the preset event includes the first page exposure event, in response to the occurrence of the first page exposure event in the application client, determine the buried point object associated with the preset event according to the root page of the page where the exposure ends; When the preset event includes the second page exposure event, in response to the occurrence of the second page exposure event in the application client, determine the buried point object associated with the preset event according to the buried point object pre-associated with the second page exposure event; When the preset event includes the automatic trigger event, in response to the occurrence of the automatic trigger event in the application client, determine the buried point object associated with the preset event according to the buried point object pre-associated with the automatic trigger event.

4. The method for reporting buried point information according to claim 1, wherein Generating the to-be-reported buried point attribution parameter value corresponding to the preset event according to the pit position information and content information of the buried point object associated with the preset event includes: Generating the to-be-reported buried point attribution parameter value corresponding to the preset event according to the type of the preset event, the occurrence order of the preset event within the exposure period of the page where the preset event is located, the page exposure order corresponding to the page where the preset event occurs, the pit position information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event; Wherein, after the application client is started, each time a page is exposed, the value of the page exposure order increases by a unit value, and the value of the page exposure order restarts counting with the restart of the application client.

5. The method for reporting buried point information according to claim 1, wherein Generating the to-be-reported buried point attribution parameter value corresponding to the preset event according to the pit position information and content information of the buried point object associated with the preset event includes: Generating the to-be-reported buried point attribution parameter value corresponding to the preset event according to the session identifier at the most recent startup of the application client, the pit position information of the buried point object associated with the preset event, and the content information of the buried point object associated with the preset event.

6. The method for reporting buried point information according to claim 1, wherein When the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes the first type; Matching the buried point object identifier of the exposed buried point object with the target object identifier in each of the to-be-reported buried point attribution parameter values stored in the first preset storage container includes: When a new page is exposed in the application client, matching the buried point object identifier of the newly exposed page with the target object identifier in each of the to-be-reported buried point attribution parameter values stored in the first preset storage container; Determine the value of the target buried point attribution parameter of the first type according to the matching result; The target buried point attribution parameter of the first type is used to characterize the exposure source of the root page of the page exposed by the buried point reporting event, and the target buried point attribution parameter of the first type is updated when a new page is exposed.

7. The method for reporting buried point information according to claim 1, wherein, When the buried point reporting event includes a page exposure event, the target buried point attribution parameter includes a second type; The matching of the buried point object identifier of the exposed buried point object with the target object identifiers in each to-be-reported buried point attribution parameter value stored in the first preset storage container includes: When the page exposed in the application client is a newly created page, matching the buried point object identifier of the exposed page with the target object identifiers in each to-be-reported buried point attribution parameter value stored in the first preset storage container; Based on the matching result, determining the value of the target buried point attribution parameter of the second type; The target buried point attribution parameter of the second type is used to characterize the creation source of the root page of the page exposed by the buried point reporting event, and the target buried point attribution parameter of the second type is updated when a new page is created.

8. The method for reporting buried point information according to claim 6, wherein When the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes a third type and a first type, the determining method of the value of the target buried point attribution parameter of the third type includes: Based on the page exposure order in the application client, in response to the exposure of the root page in the application client, adding the value of the target buried point attribution parameter of the first type corresponding to the newly exposed root page to a second preset storage container; When the number of the values of the target buried point attribution parameter of the first type stored in the second preset storage container is greater than a first preset value, deleting the value of the target buried point attribution parameter of the first type with the earliest addition time from the second preset storage container; Based on the second preset storage container, determining the value of the target buried point attribution parameter of the third type; 9. The method for reporting buried point information according to claim 7, wherein When the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes a fourth type and a second type, the determining method of the value of the target buried point attribution parameter of the fourth type includes: Based on the page exposure order in the application client, in response to the exposure of the root page in the application client, adding the value of the target buried point attribution parameter of the second type corresponding to the newly exposed root page to a third preset storage container; When the number of the values of the target buried point attribution parameter of the second type stored in the third preset storage container is greater than a second preset value, deleting the value of the target buried point attribution parameter of the second type with the earliest addition time from the third preset storage container; Based on the third preset storage container, determining the value of the target buried point attribution parameter of the fourth type; The target buried point attribution parameter of the fourth type is used to describe the page creation sources of multiple pages before the current page exposure.

10. The method for reporting buried point information according to claim 7, wherein When the type of the target buried point attribution parameter includes a fifth type and a second type, the determining method of the value of the target buried point attribution parameter of the fifth type includes: Matching the buried point object identifier of the buried point object exposed by the buried point reporting event with a preset buried point object identifier; When the matching is successful, determine the value of the target attribution parameter of the fifth type according to the value of the attribution parameter of the second type corresponding to the attribution object indicated by the successfully matched preset attribution object identifier; Among them, the preset attribution object identifier includes the attribution object identifier corresponding to the root page of the home page of the application client; The target attribution parameter of the fifth type is used to describe the home page of the application client from which the current event occurs.

11. The method for reporting buried point information according to claim 10, wherein, When the attribution object identifier of the attribution object exposed in the attribution reporting event fails to match the preset attribution object identifier, the method for determining the value of the target attribution parameter of the fifth type includes: Obtain the attribution object identifier corresponding to the root page of the page where the attribution object exposed in the attribution reporting event is located; Match the attribution object identifier corresponding to the root page with the target object identifier in the to-be-reported attribution parameter values stored in the first preset storage container to determine the target to-be-reported attribution parameter value; Match the attribution object identifier included in the target to-be-reported attribution parameter value with the preset attribution object identifier, and determine the value of the target attribution parameter of the fifth type according to the matching result.

12. The method for reporting buried point information according to claim 11, wherein The matching the attribution object identifier corresponding to the root page with the target object identifier in the to-be-reported attribution parameter values stored in the first preset storage container to determine the target to-be-reported attribution parameter value includes: When the matching is successful, determine the target to-be-reported attribution parameter value according to the successfully matched to-be-reported attribution parameter value; When the matching fails, determine the target to-be-reported attribution parameter value according to the to-be-reported attribution parameter value that was most recently added to the first preset storage container.

13. The method for reporting buried point information according to claim 11, wherein The matching the attribution object identifier included in the target to-be-reported attribution parameter value with the preset attribution object identifier and determining the value of the target attribution parameter of the fifth type according to the matching result includes: When the matching is successful, update the value of the target attribution parameter of the fifth type according to the value of the attribution parameter of the second type corresponding to the attribution object indicated by the successfully matched preset attribution object identifier; When the matching fails, do not update the value of the target attribution parameter of the fifth type.

14. The method for reporting buried point information according to claim 1, wherein When the attribution reporting event includes an event of adding a list unit to a playlist, the type of the target attribution parameter includes the sixth type; The matching the attribution object identifier of the exposed attribution object with the target object identifier in each of the to-be-reported attribution parameter values stored in the first preset storage container includes: In response to the application client generating an event of adding a list unit to a playlist, match the attribution object identifier corresponding to the attribution object exposed by the event of adding a list unit to a playlist with the target object identifier included in the to-be-reported attribution parameter values stored in the first preset storage container; Determine the value of the target attribution parameter of the sixth type according to the matching result; Among them, the target buried point attribution parameter of the sixth type is used to characterize the reason why the list unit is added to the playlist.

15. The method for reporting buried point information according to claim 1, wherein, In the case where the buried point reporting event includes the event that the list unit of the playlist is played, the type of the target buried point attribution parameter includes the seventh type; The matching of the buried point object identifier of the exposed buried point object with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container includes: In response to the event that the list unit in the playlist is played in the application client, matching the buried point object identifier of the buried point object exposed by the event that the list unit is played with the target object identifier included in the to-be-reported buried point attribution parameter value stored in the first preset storage container; According to the matching result, determine the value of the target buried point attribution parameter of the seventh type; Among them, the target buried point attribution parameter of the seventh type is used to characterize the reason why the list unit in the playlist is played.

16. The method for reporting buried point information according to claim 1, wherein The adding of the to-be-reported buried point attribution parameter value corresponding to the preset event to the first preset storage container based on the occurrence order of the preset events in the application client includes: Based on the occurrence order of the preset events in the application client except the preset to-be-deleted event, adding the to-be-reported buried point attribution parameter value corresponding to the preset event to the first preset storage container; The preset to-be-deleted event is determined according to the preset page exposed in the application client and / or the preset element triggered.

17. The method for reporting buried point information according to claim 1, wherein The method further includes: When a preset event occurs in the application client, if there is no associated buried point object for the preset event, determine the root page where the element targeted by the preset event is located; According to the to-be-reported buried point attribution parameter value corresponding to the root page and the preset identification field, determine the to-be-reported buried point attribution parameter value corresponding to the preset event; Among them, the preset identification field is used to identify that the to-be-reported buried point attribution parameter value is the to-be-reported buried point attribution parameter value generated after triggering a position in the application client where there is no buried point object.

18. The method for reporting buried point information according to claim 1, wherein The reporting of the buried point information for the buried point object exposed by the buried point reporting event based on the value of the target buried point attribution parameter includes: Taking the value of the target buried point attribution parameter as the value of the buried point information reporting parameter of the buried point object exposed by the buried point reporting event, so as to report the buried point information for the buried point object exposed by the buried point reporting event.

19. A device for reporting buried point information, characterized in that, Includes: A preset event response module, configured to determine the buried point object associated with the preset event in response to the occurrence of the preset event in the application client; A to-be-reported buried point attribution parameter value generation module, configured to generate the to-be-reported buried point attribution parameter value corresponding to the preset event according to the slot information and content information of the buried point object associated with the preset event; An adding module, configured to add the to-be-reported buried point attribution parameter value corresponding to the preset event to the first preset storage container based on the occurrence order of the preset events in the application client; A target buried point attribution parameter value determination module, configured to determine the value of the target buried point attribution parameter according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event from the first preset storage container; A buried point information reporting module, configured to report the buried point information of the buried point object exposed by the buried point reporting event based on the value of the target buried point attribution parameter; Wherein, the content information of the buried point object associated with the preset event includes a target object identifier, and the target object identifier includes the buried point object identifier of the root page of the page that can be exposed after the buried point object is triggered; The determining the value of the target buried point attribution parameter from the first preset storage container according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event includes: matching the buried point object identifier of the exposed buried point object with the target object identifier in each to-be-reported buried point attribution parameter value stored in the first preset storage container; When the matching is successful, the value of the target buried point attribution parameter is determined by the following method: determining a first to-be-reported buried point attribution parameter value according to the to-be-reported buried point attribution parameter value including the successfully matched target object identifier; determining a second to-be-reported buried point attribution parameter value from the first preset storage container, and the second to-be-reported buried point attribution parameter value includes the to-be-reported buried point attribution parameter value corresponding to the most recent page exposure event stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the one with the larger generation time among the first to-be-reported buried point attribution parameter value and the second to-be-reported buried point attribution parameter value; When the matching fails, the value of the target buried point attribution parameter is determined by the following method: determining the value of the target buried point attribution parameter according to the to-be-reported buried point attribution parameter value added most recently in the first preset storage container.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer program, when executed by a processor, implements the method according to any one of claims 1 to 18.

21. An electronic device, characterized in that, Including: One or more processors; A storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 18.

Images