CN115576772A - Method and device for reporting embedded point information, medium and electronic equipment - Google Patents

Method and device for reporting embedded point information, medium and electronic equipment Download PDF

Info

Publication number
CN115576772A
CN115576772A CN202211167977.3A CN202211167977A CN115576772A CN 115576772 A CN115576772 A CN 115576772A CN 202211167977 A CN202211167977 A CN 202211167977A CN 115576772 A CN115576772 A CN 115576772A
Authority
CN
China
Prior art keywords
buried point
event
page
preset
target
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211167977.3A
Other languages
Chinese (zh)
Inventor
陈锦海
曹偲
丁立
余英豪
张腾飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Netease Cloud Music Technology Co Ltd
Original Assignee
Hangzhou Netease Cloud Music Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou Netease Cloud Music Technology Co Ltd filed Critical Hangzhou Netease Cloud Music Technology Co Ltd
Priority to CN202211167977.3A priority Critical patent/CN115576772A/en
Publication of CN115576772A publication Critical patent/CN115576772A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

The disclosed embodiment relates to a method and a device for reporting embedded point information, a computer readable storage medium and electronic equipment, and relates to the technical field of computers. The method for reporting the buried point information comprises the following steps: responding to a preset event in an application program client, and determining a buried point object associated with the preset event; generating an attribution parameter value of a buried point to be reported corresponding to a preset event according to the pit position information and the content information of the buried point object associated with the preset event; adding a buried point attribution parameter value to be reported corresponding to a preset event in a first preset storage container based on the occurrence sequence of the preset event in the application program client; determining the value of the target buried point attribution parameter from a 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 the embedded point information of the embedded point object exposed by the embedded point reporting event based on the value of the target embedded point attribution parameter. The method and the device can improve accuracy and efficiency of buried point attribution.

Description

Method and device for reporting embedded point information, medium and electronic equipment
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for reporting buried point information, a computer-readable storage medium, and an electronic device.
Background
This section is intended to provide a background or context to the embodiments of the disclosure recited in the claims and the description herein is not admitted to be prior art by inclusion in this section.
The burial point is that certain information is collected by a specific process in the application and is used for tracking the use condition of the application so as to provide data support for further optimizing the product. By attributing and reporting the buried point data, the user behavior can be accurately analyzed, and the optimization performance of the product is improved.
The methods for performing buried point attribution in the related art are mainly classified into the following 3 methods: the first is that the embedded log in the client needs to undergo long request uploading, analysis processing and other processes, so that the sequence of the embedded points stored in the database is inconsistent with the generation sequence of the client, and the logs are sorted by a certain time window at the analysis side, so as to attribute the embedded points; the second is to select the source when the specific event (such as page exposure, song playing, etc.) occurs, which is appointed by some parameters on the end of the buried point generation; and the third is that the pit bit information and the content information of the jump pit bit are generated on the routing information of the page jump in a splicing way and are used as the source of the generation of the lower-level page, and the multi-level attribution is realized by accumulating and transmitting the multi-level.
Disclosure of Invention
However, for massive data, the first method has high resource consumption and low efficiency, and cannot realize the buried point attribution in real time in the log layer, and meanwhile, when the buried point time interval is long, the attribution target may exceed the time window and cannot be attributed; in the second mode, for different links, the parameters required to be agreed are not completely consistent, so that the data maintenance workload is large and error attribution is easy to occur; the third method is characterized in that the splicing of attribution parameters requires manual intervention of service development when a route is generated, the workload is large, omission or errors are easy to occur, meanwhile, the accuracy of attribution of a buried point is insufficient because only the routing information of no more than four levels of page-subpage-module-element is adopted, in addition, the third method is only effective to page jump supported by the route, is difficult to expand to attribution scenes of other interaction events, such as playing and other events, and has poor universality.
Therefore, an improved method for reporting the buried point information is very needed, which can simultaneously improve the accuracy and efficiency of the attribution of the buried points, so that the attribution of the buried points has universality and the later maintenance cost of the data of the buried points is reduced.
In this context, embodiments of the present disclosure desirably provide a buried point information reporting method, a buried point information reporting apparatus, a computer-readable storage medium, and an electronic device.
According to a first aspect of the embodiments of the present disclosure, a method for reporting buried point information is provided, including: responding to a preset event in an application program client, and determining a buried point object associated with the preset event; generating an attribution parameter value of a buried point to be reported corresponding to a preset event according to the pit position information and the content information of the buried point object associated with the preset event; adding a buried point attribution parameter value to be reported corresponding to a preset event in a first preset storage container based on the occurrence sequence of the preset event in the application program client; determining the value of the target buried point attribution parameter from a 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 the embedded point information of the embedded point object exposed by the embedded point reporting event based on the value of the target embedded point attribution parameter.
In an optional embodiment, the preset event includes one or more of a triggered event, a page exposure event, and an automatic triggering event of an element in a page; the page exposure event comprises a first page exposure event and/or a second page exposure event, the first page exposure event is determined based on an event which causes the page exposure to occur in the application client due to the operation in the application client, and the second page exposure event is determined based on an event which causes the page exposure to occur in the application client due to the operation in the third-party application.
In an alternative embodiment, the determining, in response to a preset event occurring in an application client, a buried object associated with the preset event includes: under the condition that the preset event comprises an element triggered event in the page, in response to the occurrence of the element triggered event in the page in an application client, determining a buried point object associated with the preset event according to the triggered element; under the condition that the preset event comprises the first page exposure event, responding to the first page exposure event in an application program client, and determining a buried point object associated with the preset event according to a root page of a page which finishes exposure; under the condition that the preset event comprises the second page exposure event, responding to the second page exposure event occurring in the application program client, and determining a buried point object associated with the preset event according to a buried point object associated with the second page exposure event in advance; and under the condition that the preset event comprises the automatic triggering event, responding to the automatic triggering event in the application program client, and determining a buried point object associated with the preset event according to the buried point object associated with the automatic triggering event in advance.
In an optional implementation manner, the generating, according to the pit bit information and the content information of the buried point object associated with the preset event, an attribution parameter value of the buried point to be reported corresponding to the preset event includes: generating an attribution parameter value of a buried point to be reported corresponding to the preset event according to the type of the preset event, the occurrence sequence of the preset event in the exposure period of the page where the preset event is located, the page exposure sequence 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; after the application client is started, each time page exposure occurs, the value of the page exposure sequence is increased by a unit numerical value, and the value of the page exposure sequence restarts counting along with the restart of the application client.
In an optional implementation manner, the generating, according to the pit bit information and the content information of the buried point object associated with the preset event, an attribution parameter value of the buried point to be reported corresponding to the preset event includes: and generating a buried point attribution parameter value to be reported corresponding to the preset event according to the session identifier when the application program client is started last time, the pit bit 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.
In an optional implementation manner, the content information of the buried point object associated with the preset event includes a target object identifier, where the target object identifier includes a buried point object identifier of a root page of a page that can be exposed after the buried point object is triggered.
In an optional implementation manner, the determining, according to the type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event, a value of the target buried point attribution parameter from the first preset storage container includes: matching the buried point object identifier of the exposed buried point object with a target object identifier in attribution parameter values of each buried point to be reported stored in the first preset storage container; and determining the value of the attribution parameter of the target buried point according to the matching result.
In an optional implementation manner, the determining, according to the matching result, a value of the target buried point attribution parameter includes: when the matching is successful, determining the value of the attribution parameter of the target buried point by the following method: determining a first buried point attribution parameter value to be reported according to the buried point attribution parameter value to be reported containing the successfully matched target object identifier; determining a second buried point attribution parameter value to be reported from the first preset storage container, wherein the second buried point attribution parameter value to be reported comprises a buried point attribution parameter value to be reported corresponding to the latest page exposure event stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the larger generation time of the first buried point attribution parameter value to be reported and the second buried point attribution parameter value to be reported; when the matching fails, determining the attribution parameter value of the target buried point by the following method: and determining the value of the target buried point attribution parameter according to the buried point attribution parameter value to be reported which is added in the first preset storage container last time.
In an optional implementation manner, in a case that the buried point reporting event includes a page exposure event, the type of the target buried point attribution parameter includes a first type; the matching of the exposed buried point object identifier of the buried point object with the target object identifier in the attribution parameter values of the buried points to be reported stored in the first preset storage container includes: when a new page is exposed in the application program client, matching the embedded point object identifier of the exposed new page with a target object identifier in attribution parameter values of each to-be-reported embedded point stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result, wherein the determining comprises the following steps: determining the value of the attribution parameter of the first type of target buried point according to the matching result; the first type of target buried point attribution parameter is used for representing an exposure source of a root page of a page exposed by a buried point reporting event, and the first type of target buried point attribution parameter is updated when a new page exposure occurs.
In an optional implementation manner, in a case that 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 object identifier of the exposed buried object with the target object identifier in the attribution parameter values of the buried points to be reported stored in the first preset storage container includes: under the condition that the exposed page in the application program client is a newly created page, matching the embedded object identifier of the exposed page with the target object identifier in the attribution parameter value of each embedded point to be reported stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result, wherein the determining comprises the following steps: determining the value of the attribution parameters of the second type of target buried points according to the matching result; the second type of target buried point attribution parameter is used for representing a creation source of a root page of a page exposed by a buried point reporting event, and the second type of target buried point attribution parameter is updated when a new page is created.
In an optional implementation manner, in a case that the buried point reporting event includes a page exposure event, and the types of the target buried point attribution parameter include a third type and the first type, the determining manner of the value of the third type of the target buried point attribution parameter includes: responding to the root page exposure in the application program client based on the page exposure sequence in the application program client, and adding the value of the first type target buried point attribution parameter corresponding to the newly exposed root page into a second preset storage container; when the number of the values of the first type of target buried point attribution parameter stored in the second preset storage container is larger than a first preset value, deleting the value of the first type of target buried point attribution parameter with the earliest adding time in the second preset storage container from the second preset storage container; and determining the value of the attribution parameter of the third type of target buried point according to the second preset storage container.
In an optional implementation manner, when the buried point reporting event includes a page exposure event, and the type of the target buried point attribution parameter includes a fourth type and the second type, the determining manner of the value of the fourth type of the target buried point attribution parameter includes: responding to the root page exposure in the application program client based on the page exposure sequence in the application program client, and adding the value of the second type target buried point attribution parameter corresponding to the newly exposed root page into a third preset storage container; when the number of the values of the second type of target buried point attribution parameters stored in the third preset storage container is larger than a second preset value, deleting the value of the second type of target buried point attribution parameter with the earliest adding time in the third preset storage container from the third preset storage container; and determining the value of the attribution parameter of the fourth type of target buried point according to the third preset storage container.
In an alternative embodiment, in a case where the types of the target buried point attribution parameter include a fifth type and the second type, the determining 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, determining the value of the attribution parameter of the target embedded point of the fifth type according to the value of the attribution parameter of the embedded point of the second type corresponding to the embedded point object indicated by the preset embedded point object identifier which is successfully matched; the preset buried object identifier comprises a buried object identifier corresponding to a root page of a home page of the application client.
In an optional implementation manner, when the buried point object identifier of the buried point object exposed by the buried point reporting event fails to match with the preset buried point object identifier, the determining manner of the value of the target buried point attribution parameter of the fifth type includes: acquiring a buried point object identifier corresponding to a root page of a page where a buried point object exposed by the buried point reporting event is located; matching the buried point object identifier corresponding to the root page with a target object identifier in the buried point attribution parameter values to be reported stored in the first preset storage container to determine target attribution parameter values to be reported; and matching the buried point object identifier contained in the attribution parameter value to be reported of the target with the preset buried point object identifier, and determining the value of the attribution parameter of the target of the fifth type according to a matching result.
In an optional implementation manner, the matching the buried 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 includes: when the matching is successful, determining the attribution parameter value of the target buried point to be reported according to the attribution parameter value of the buried point to be reported successfully matched; and when the matching fails, determining the attribution parameter value of the target buried point to be reported according to the attribution parameter value of the buried point to be reported which is added to the first preset storage container for the last time.
In an optional implementation manner, the matching the buried point object identifier included in the target buried point attribution parameter value to be reported with the preset buried point object identifier, and determining the value of the target buried point attribution parameter of the fifth type according to a 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 second type of buried point attribution parameter corresponding to the buried point object indicated by the preset buried point object identification which is successfully matched; when the matching fails, the values of the fifth type of target buried point attribution parameters are not updated.
In an optional implementation manner, in a case that the buried point reporting event includes an add list unit to playlist event, the type of the target buried point attribution parameter includes a sixth type; the matching of the exposed buried point object identifier of the buried point object with the target object identifier in the attribution parameter values of the buried points to be reported stored in the first preset storage container includes: responding to an event that the application program client adds a list unit to the playlist, and matching a buried object identifier corresponding to a buried object exposed by the event that the list unit is added to the playlist with a target object identifier included in a buried point attribution parameter value to be reported, which is stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result, wherein the determining comprises the following steps: determining the value of the attribution parameter of the sixth type of target buried point according to the matching result; wherein the sixth type of target buried point attribution parameter is used to characterize a reason why a list unit is added to a playlist.
In an optional implementation manner, in a case that the buried point reporting event includes a playlist unit played event of a playlist, the type of the target buried point attribution parameter includes a seventh type; the matching of the exposed buried point object identifier of the buried point object with the target object identifier in the attribution parameter values of the buried points to be reported stored in the first preset storage container includes: in response to the occurrence of a played event of a list unit in a play list by the application program client, matching a buried object identifier of a buried object exposed by the played event of the list unit with a target object identifier included in an attribution parameter value of a buried point to be reported stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the matching result, wherein the determining comprises the following steps: determining the value of the attribution parameters of the seventh type of target buried points according to the matching result; wherein the seventh type of target buried point attribution parameter is used for characterizing a reason why a list unit in a play list is played.
In an optional implementation manner, the adding, based on an occurrence sequence of a preset event in the application client, the to-be-reported buried point attribution parameter value corresponding to the preset event in a first preset storage container includes: adding the attribution parameter values of the buried points to be reported corresponding to the preset events in the first preset storage container based on the occurrence sequence of the preset events except the preset events to be deleted in the application program client; and the preset event to be deleted is determined according to a preset page exposed in the application program client and/or a triggered preset element.
In an optional embodiment, the method further comprises: when a preset event occurs in an application program client, if the preset event does not have a related buried object, determining a root page where an element aimed at by the preset event is located; determining the attribution parameter value of the buried point to be reported corresponding to the preset event according to the attribution parameter value of the buried point to be reported corresponding to the root page and a preset identification field; the preset identification field is used for identifying the buried point attribution parameter value to be reported as the buried point attribution parameter value to be reported generated after the position of the buried point object in the application program client is triggered.
In an optional implementation manner, the reporting, based on the value of the target buried point attribution parameter, of the buried point information of the buried point object exposed by the buried point reporting event includes: and taking the value of the attribution parameter of the target buried point 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.
According to a second aspect of the embodiments of the present disclosure, there is provided a device for reporting embedded point information, including: the system comprises a preset event response module, a data processing module and a data processing module, wherein the preset event response module is configured to respond to a preset event in an application program client and determine a buried point object associated with the preset event; a to-be-reported buried point attribution parameter value generating module configured to generate a to-be-reported buried point attribution parameter value corresponding to the preset event according to the pit bit information and the content information of the buried point object associated with the preset event; the adding module is configured to add the buried point attribution parameter values to be reported corresponding to the preset events in a first preset storage container based on the occurrence sequence of the preset events in the application program 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 the buried point information reporting module is configured to report the buried point information of the buried point object exposed by the target buried point reporting event based on the value of the target buried point attribution parameter.
According to a third aspect of the disclosed embodiments, a computer-readable storage medium is provided, where a computer program is stored, and when the computer program is executed by a processor, the embedded point information reporting method of the first aspect is implemented.
According to a fourth aspect of the disclosed embodiments, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; the processor is configured to execute the executable instructions to perform the above-mentioned method for reporting the buried point information according to the first aspect.
According to the embedded point information reporting method, the embedded point information reporting device, the medium and the electronic equipment, a embedded point object associated with a preset event is determined by responding to the preset event occurring in an application program client; generating an attribution parameter value of a buried point to be reported corresponding to a preset event according to the pit position information and the content information of the buried point object associated with the preset event; adding a buried point attribution parameter value to be reported corresponding to a preset event in a first preset storage container based on the occurrence sequence of the preset event in the application program client; determining the value of the target buried point attribution parameter from a 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 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. On one hand, the embedded point attribution reporting method is based on the occurrence sequence of the preset events in the application program client, the embedded point attribution parameter values to be reported corresponding to the preset events are added into the first preset storage container, and then embedded point attribution reporting is carried out, so that the accuracy of embedded point attribution reporting can be improved; on the other hand, according to the method, firstly, a buried point attribution parameter value to be reported is generated according to pit bit information and content information, then, according to the type of a target buried point attribution parameter associated with a buried point object exposed by a buried point reporting event, the value of the target buried point attribution parameter can be directly determined, then, automatic buried point attribution reporting is carried out, and the efficiency of buried point attribution can be improved; on the other hand, according to the type of the target buried point attribution parameter associated with the buried point object of the buried point reporting event report and the attribution parameter value to be reported stored in the first preset storage container, the buried point attribution report can be directly carried out, excessive service private parameters are not required to be designed for various paths, and the maintenance cost of the buried point report is reduced.
Drawings
The above and other objects, features and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which:
fig. 1 shows a schematic diagram of a method for reporting embedded point information according to an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of an interface for interaction based on operations in an application client, according to an embodiment of the present disclosure;
FIG. 3 illustrates an interface diagram for interaction based on a third-party application according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram illustrating a display page jumped to based on a user's operational behavior according to an embodiment of the present disclosure;
FIG. 5 shows a schematic flow diagram of a method of determining a value of a target buried point attribution parameter according to an embodiment of the present disclosure;
FIG. 6 is a schematic flow chart diagram illustrating a method for determining a value of a target buried point attribution parameter according to a matching result, according to an embodiment of the present disclosure;
FIG. 7 shows a schematic flow chart diagram of a method for matching based on a buried object identifier to determine a value of a target buried cause parameter in accordance with an embodiment of the present disclosure;
FIG. 8 illustrates a flow chart diagram of a method of determining a value of a first type of target buried point attribution parameter, according to an embodiment of the present disclosure;
FIG. 9 shows a schematic flow diagram of a method of determining a value of a second type of target buried point attribution parameter, according to an embodiment of the present disclosure;
FIG. 10 shows a schematic flow diagram of another method of determining a value of a first type of target buried point attribution parameter, according to an embodiment of the present disclosure;
FIG. 11 illustrates a process diagram of a user action in accordance with an embodiment of the present disclosure;
FIG. 12 illustrates a flow chart diagram of a method of determining a value of a third type of target buried point attribution parameter, according to an embodiment of the present disclosure;
FIG. 13 illustrates a schematic flow chart diagram of a method of determining a value of a fourth type of target buried point attribution parameter, according to an embodiment of the present disclosure;
FIG. 14 shows a schematic flow diagram of a method of determining a value of a fifth type of target buried point attribution parameter, according to an embodiment of the present disclosure;
FIG. 15 illustrates a schematic flow chart diagram of another method of determining a value of a fifth type of target buried point attribution parameter, according to embodiments of the present disclosure;
FIG. 16 illustrates a flow chart diagram of yet another method of determining a value of a fifth type of target buried point attribution parameter, according to embodiments of the present disclosure;
FIG. 17 illustrates a flow chart diagram of a method of determining a value of a sixth type of target buried point attribution parameter, according to an embodiment of the present disclosure;
FIG. 18 shows a schematic flow diagram of a method of determining a value of a seventh type of target buried point attribution parameter, according to an embodiment of the present disclosure;
FIG. 19 shows a process diagram of another user action in accordance with an embodiment of the present disclosure;
fig. 20 is a block diagram illustrating a buried point information reporting apparatus according to the disclosed embodiment;
fig. 21 shows a block diagram of an electronic device according to an embodiment of the present disclosure.
In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.
Detailed Description
The principles and spirit of the present disclosure will be described below with reference to several exemplary embodiments. It is understood that these embodiments are given solely for the purpose of enabling those skilled in the art to better understand and to practice the present disclosure, and are not intended to limit the scope of the present disclosure in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As will be appreciated by one skilled in the art, embodiments of the present disclosure may be embodied as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
According to an embodiment of the present disclosure, a reporting method of embedded point information, an embedded point method, a reporting device of embedded point information, an embedded point device, a computer-readable storage medium, and an electronic device are provided.
In this document, any number of elements in the drawings is by way of example and not by way of limitation, and any nomenclature is used solely for differentiation and not by way of limitation.
The principles and spirit of the present disclosure are explained in detail below with reference to several representative embodiments of the present disclosure.
Summary of The Invention
The inventor of the present disclosure finds that, in some existing buried point reporting schemes, log sorting of reported buried point log data needs to be performed in a certain time window, and when the data volume is large, the efficiency is low, resource consumption is caused, and a situation that attribution cannot be performed due to the fact that a target exceeds the time window may exist; in other existing buried point reporting schemes, the problems that the data attribution of the buried points is large in maintenance workload and inaccurate in attribution exist.
In view of the above, the basic idea of the present disclosure is: the method comprises the steps of providing a buried point information reporting method, a buried point information reporting device, a computer readable storage medium and electronic equipment, and determining a buried point object associated with a preset event by responding to the preset event in an application program client; generating an attribution parameter value of a buried point to be reported corresponding to a preset event according to the pit position information and the content information of the buried point object associated with the preset event; adding a buried point attribution parameter value to be reported corresponding to a preset event in a first preset storage container based on the occurrence sequence of the preset event in the application program client; determining the value of the attribution parameters of the target buried points from a first preset storage container according to the types of the attribution parameters of the target buried points associated with the buried point objects exposed by the buried point reporting events; and reporting 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. On one hand, the embedded point attribution reporting method is based on the occurrence sequence of the preset events in the application program client, the embedded point attribution parameter values to be reported corresponding to the preset events are added into the first preset storage container, and then embedded point attribution reporting is carried out, so that the accuracy of embedded point attribution reporting can be improved; on the other hand, according to the method, firstly, a buried point attribution parameter value to be reported is generated according to pit bit information and content information, then, according to the type of a target buried point attribution parameter associated with a buried point object exposed by a buried point reporting event, the value of the target buried point attribution parameter can be directly determined, then, automatic buried point attribution reporting is carried out, and the efficiency of buried point attribution can be improved; on the other hand, according to the type of the target buried point attribution parameter associated with the buried point object of the buried point reporting event report and the attribution parameter value to be reported stored in the first preset storage container, the buried point attribution report can be directly carried out, excessive service private parameters are not needed to be designed for various paths, and the maintenance cost of the buried point report is reduced.
Having described the basic principles of the present disclosure, various non-limiting embodiments of the present disclosure are described in detail below.
Application scene overview
It should be noted that the following application scenarios are merely illustrated to facilitate understanding of the spirit and principles of the present disclosure, and embodiments of the present disclosure are not limited in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.
The present disclosure may be applied to scenarios where data is collected, such as: the embedded point information reporting method provided by the disclosure can be used for collecting the use data (such as access number, visitor number, dwell time, page browsing number, page browsing reason and the like) of the application, and analyzing the use condition of the application based on the use data to provide data support for further optimization of the application; in an information recommendation scene, the relevant historical behavior data of a user can be collected by using the buried point information reporting method provided by the disclosure, and then the user portrait can be described based on the collected historical behavior data of the user so as to recommend information to the user.
Exemplary method
According to a buried point reporting scheme in the related art, the problems that buried point attribution efficiency is low, buried point attribution accuracy is insufficient, and the buried point attribution data maintenance cost is high exist.
The exemplary embodiment of the present disclosure first provides a method for reporting buried point information, so as to overcome at least all or part of the above-mentioned drawbacks in the related art.
Fig. 1 shows a method for reporting embedded point information in an exemplary embodiment of the present disclosure, which may include:
step S110, responding to a preset event in an application program client, and determining a buried point object associated with the preset event;
step S120, generating a buried point attribution parameter value to be reported corresponding to the preset event according to the pit bit information and the content information of the buried point object associated with the preset event;
step S130, adding a buried point attribution parameter value to be reported corresponding to a preset event in a first preset storage container based on the occurrence sequence of the preset event in the application program client;
step S140, determining the value of the target buried point attribution parameter from a 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 S150, reporting 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.
Each step in fig. 1 will be described in detail below.
In step S110, in response to a preset event occurring in the application client, a buried point object associated with the preset event is determined.
In an exemplary embodiment, the preset event includes one or more of an element triggered event, a page exposure event, and an automatic trigger event in the page.
The page exposure event comprises a first page exposure event and/or a second page exposure event, the first page exposure event is determined based on the event which causes the page exposure in the application client terminal caused by the operation in the application client terminal, and the second page exposure event is determined based on the event which causes the page exposure in the application client terminal caused by the operation in the third-party application program.
The first page exposure event and the second page exposure event are further described below in conjunction with fig. 2-4. For example, if the user can select "Song A" in the history column of the page shown in FIG. 2 and then click on the post-entry column search control 21 in FIG. 2, then the user can jump to the search results page of "Song A" shown in FIG. 4 according to the series of operations. At this time, the page shown in fig. 4 is skipped based on the search behavior of the user at the application client, so in this case, the exposure of the page shown in fig. 4 can be understood as the first page exposure event. For another example, the user may enter the song name "song a" in the page shown in fig. 3 through the keyboard of the terminal device, and then click the search control 31 in the keyboard to jump to the page shown in fig. 4. At this time, the page shown in fig. 4 is skipped based on the search behavior of the user at the third party application, i.e., the keyboard of the terminal device, so in this case, the exposure of the page shown in fig. 4 can be understood as the second page exposure event described above.
For another example, the event that the user exposes a certain page in the application client by entering the application client through a page shared by others in other social application clients may also be understood as the second page exposure event. Taking the application client as the internet access cloud music as an example, if a user opens a playing page of a certain song in the internet access cloud music through a page in the internet access cloud music shared by other people in other social application clients, an exposure event of the playing page can be understood as a second page exposure event.
In an alternative embodiment, exposure may be understood as the state in which a page or element in the application client is not visible in the graphical user interface of the terminal device. What corresponds to an exposure is called a back exposure or an end exposure, which may be understood as a state in which a page or element in the application client is visible to invisible in the graphical user interface of the terminal device.
A page may be understood as a whole area displayed exclusively at a certain user interface level, such as a newly opened underlying page, a TAB (TAB/TAB), a channel, etc.; the page is generally used for organizing a plurality of contents to distribute or used as an actual function bearing of a single content, and information such as circulation exposure and dwell time of the page has great significance for analysis of the application. An element may be understood as a UI (User Interface) component and/or element in a page that may be interacted with by a User, such as a list element, a button, a slideable content module, etc. The lists and modules are generally used for carrying content distribution, the click rate of the lists and modules has analytical significance on content distribution effects, the buttons are generally used for carrying user interaction, and the buttons are generally mounted on a certain content unit or a bottom page of a content function.
Both pages and elements can be buried point objects. One page can comprise sub-pages and elements, for one page, the page itself, the sub-pages and the elements in the page can be used as buried point objects in the page, and a user can perform self-defined setting according to the needs of the user.
An automatic triggering event may be understood as an event that may occur automatically in the application client without a triggering operation, such as an automatic play event, an automatic switch event, and the like. Wherein the automatic triggering event is only that the content displayed in the page has changed without causing exposure of a new page.
In an exemplary application scenario, the element triggered event has a higher priority than the page exposure event, and it is understood that if the element in the page is triggered and causes the page exposure event, the preset event occurred at this time is attributed to the element triggered event rather than the page exposure event.
In an exemplary embodiment, the specific implementation of step S110 may include: under the condition that the preset event comprises an element triggered event in the page, in response to the occurrence of the element triggered event in the page in the application client, determining a buried point object associated with the preset event according to the triggered element; under the condition that the preset event comprises a first page exposure event, responding to the first page exposure event in the application program client, and determining a buried point object associated with the preset event according to a root page of a page which finishes exposure; under the condition that the preset event comprises a second page exposure event, responding to the second page exposure event in the application program client, and determining a buried point object associated with the preset event according to a buried point object associated with the second page exposure event in advance; and under the condition that the preset event comprises an automatic triggering event, responding to the automatic triggering event occurring in the application program client, and determining the embedded point object associated with the preset event according to the embedded point object associated with the automatic triggering event in advance.
For example, for the triggered event of the element in the page and the first page exposure event, both belong to the assignable pit bit in the application client, that is, the attributable pit bit in the application client can be automatically attributed. However, for the second page exposure event and the automatic trigger event, the associated buried point object cannot be automatically determined. Based on this, in the disclosure, for the second page exposure event and the automatic trigger event, a general embedded point attribution capability is provided, the automatic generation of the embedded point attribution parameter value to be reported corresponding to the custom event is supported, and the embedded point attribution parameter value to be reported can be automatically added to the first preset storage container described below to report subsequent embedded point information.
For example, a buried point attribution parameter of the custom event may be configured in advance, which may include an attribution type refer _ type, an attribution pit bit refer _ spm, an attribution content information refer _ scm, and the like, and then, the buried point attribution parameter is associated with a certain buried point object in the application client, so that, based on the buried point object associated with the custom event that cannot be automatically attributed originally, a value of the buried point attribution parameter to be reported of the custom event may be automatically generated, so as to automatically perform buried point attribution the custom event.
Taking an event of clicking a radio station in a podcast page in the internet cloud music for automatic playing as an example, an automatic playing event autoplay may be defined, and the automatic playing event autoplay is associated with a television card, so as to realize automatic generation of an attribution parameter value of a buried point to be reported corresponding to the automatic playing event, for example, refer _ type = = autoplay, refer _ spm = = spm of the television card, and refer _ scm = = scm of the television card. That is, for some events that cannot be automatically attributed, such as an event based on a third application client opening a certain page in the target application client, or an automatically playing event, associated buried point objects may be specified in advance for the events, and the occurrence of the events may be automatically attributed by buried point based on the buried point objects pre-associated with the events.
Referring to fig. 1, in step S120, an attribution parameter value of a buried point to be reported corresponding to the preset event is generated according to the pit bit information and the content information of the buried point object associated with the preset event.
For example, a specific implementation of step S120 may include: generating an attribution parameter value of a buried point to be reported corresponding to the preset event according to the type of the preset event, the occurrence sequence of the preset event in the exposure period of the page where the preset event is located, the page exposure sequence 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; after the application client is started, each time page exposure occurs, the value of the page exposure sequence is increased by a unit numerical value, and the value of the page exposure sequence restarts counting along with the restart of the application client.
For example, another specific implementation of step S120 may include: and generating an attribution parameter value of the buried point to be reported corresponding to the preset event according to the session identifier when the application program client is started for the last time, 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.
For example, another specific implementation of step S120 may include: and generating an attribution parameter value of the buried point to be reported corresponding to the preset event according to the session identification when the client of the application program is started last time, the type of the preset event, the occurrence sequence of the preset event in the exposure period of the page where the preset event is located, the page exposure sequence corresponding to the page where the preset event occurs, the pit bit 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.
For example, another specific implementation of step S120 may include: generating a buried point attribution parameter value to be reported corresponding to a preset event according to a flag bit, a session identifier when an application program client is started last time, the type of the preset event, the occurrence sequence of the preset event in an exposure period of a page where the preset event is located, the page exposure sequence corresponding to the page where the preset event occurs, pit bit information of a buried point object associated with the preset event and content information of the buried point object associated with the preset event
Taking the example that sesid represents a session identifier when the application client is started last time, type represents a type of a preset event, actseq represents an occurrence sequence of the preset event in an exposure period of a page where the preset event is located, pgstep represents a page exposure sequence corresponding to the page where the preset event occurs, spm represents pit information of a buried point object associated with the preset event, and scm represents content information of the buried point object associated with the preset event, an attribution parameter value of the buried point to be reported may be represented as [ type ] [ actseq ] [ pgstep ] [ spm ], or [ sesid ] [ spm ].
The flag bit is used for describing the components and characteristics of the whole attribution parameter value of the buried point to be reported, the value of the flag bit is calculated through bits, each piece of information forming the attribution parameter value of the buried point to be reported occupies a fixed value, if the value exists, the value of the corresponding bit in the flag bit is 1, if the value does not exist, the value corresponding to the flag bit is 0, if the option represents the flag bit, the attribution parameter value of the buried point to be reported is represented as [ option ] [ type ] [ actseq ] [ pgstep ] [ spm ] [ scm ], for example, when the option value is 00111, the type and the actseq do not have values, and the pgstep, the spm and the scm have values.
The session identifier seesid of the application client when the application client is started last time is used for describing a unique cold start identifier when an attribution event occurs, the value of the unique cold start identifier is a hash value which does not repeat among all users, and the unique cold start identifier and the user identifier can position the start of any application client of any user in the whole network.
The value of the type of the preset event may include e, p, a, and the like. Wherein, e can be understood as the above-mentioned element triggered event, which may be a trigger to an element, or some self-defined event on an element; p may be a page exposure event as described above, indicating that the attributed event is a page exposure event; a is used for describing automatic events, such as automatic playing events and the like.
The occurrence order of the preset events in the exposure period of the page where the preset events are located may be represented by a parameter actseq, which may be used to identify the order of events in one page exposure. Within one exposure of a root page (rootpage), each time an interaction event (click/slide/pull-down refresh, etc.) occurs, the value of actseq is correspondingly increased by 1, and the actseq is reset along with the change of the pgstep value of the root page of the element corresponding to the interaction event, that is, when the interaction event causes the exposed root page to change, pgstep is increased by 1, and at the same time, actseq is recounted from 1.
The page exposure sequence corresponding to the page where the preset event occurs may be represented by a parameter pgstep, which is used to identify the exposure sequence of the page during one start of the application client. For example, after an application client is started for a certain time, page 1 (typically the first page) is exposed first, and then page 2, page 3, page 4, page 3, and page 5 are exposed in sequence based on a series of operation behaviors of the user, so that the page exposure sequence 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 client startup, page 3 is exposed twice, but the two exposures of page 3 have a different exposure order. When the next cold start after the application client shuts down, pgstep starts counting again from 1.
In other words, pgstep may record the exposure order of all pages during this application client launch, which is for all pages during the current client launch, and as soon as page exposure occurs, pgstep increases by unit 1 to indicate that the currently exposed page is the page that was exposed the next time the client was launched.
For example, there are two elements A1 and A2 in the A page; the page B comprises two elements B1 and B2; after a certain client is started, the user operation path is "enter a page-click A1-click A2-enter B page-click B1-click B2-return a page-click A1-click A2", then the change process of pgstep and actueq is "a page pgstep = 1-pgstep = 1/actueq = 2-B page pgstep = 2-pgstep = 2/actueq = 1-pgstep = 2/actueq = 2-a page pgstep = 3-pgstep = 3/actueq = 1-pgstep = 3/actueq =2".
Wherein, a page pgstep =1 indicates that the a page is the page exposed first during this time by the client; pgstep =1/actseq =1 indicates that click element A1 is the first interaction event that occurs in the a page at the first exposure of the a page; pgstep =1/actseq =2 indicates that click element A2 is two interactive events that occur in the a page at the first exposure of the a page; b page pgstep =2 indicates that the B page is now the page of the client that was exposed the second time during this time; pgstep = 2/actionseq =1 indicates that in page B, which is the second exposure of the client at this time, the click element B1 is the first interaction event that occurs in page B this time; pgstep =2/actseq =2 indicates that in page B of this second exposure of the client, the click element B2 is the second interaction event that occurs in page B this time; the a page pgstep =3 indicates that the page a is the page exposed at the 3 rd time after the client starts; pgstep =3/actseq =1 indicates that in the third page a exposed by the client at this time, the click element A1 is the first interaction event sent in page a this time; pgstep =3/actseq =2 indicates that in the third page a exposed by the client at this time, the click element A2 is the second interaction event that occurred in page a this time.
pgstep and actseq can distinguish between multiple exposures of the same page and multiple occurrences of the same trigger interaction event in the same page, and can specifically determine in which page of the several exposures each interaction event is the second interaction event.
Further, the parameter actseq representing the sequence number of the event attributed to the event within the exposure period of the page in which the event is located may be configured to be reset with a change of the root page of the current interactive element, rather than with a change of the sub-page of the current interactive element. Because the root page is typically a fully-blocked bottom or top page, attribution analysis may be implemented across multiple sub-pages, rather than being limited to within a single sub-page.
The pit bit information spm of the embedded point object associated with the preset event consists of an embedded point object identifier from the embedded point object to a root page node branch of the embedded point object and position attribute information of the embedded point object with a position attribute, the pit bit can be used for describing a unique position in different pages in the application client, and the pit bit has a value when the preset event is an element triggered event or a first page exposure event. If the buried object of the buried object associated with the preset event is identified as oid1, the location attribute of the buried object in the page is pos1, the buried object of the parent node is identified as oid2, no location attribute information exists, the parent node of the parent node is the root node, the buried object of the root node is identified as oid3, and the location attribute information of the buried object in the page is pos3, the pit location information of the buried object oid1 can be described as oid1: pos1| oid2| oid3: pos3.
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, and the specific content information may be represented in a key-value pair manner. For example, the content information of a certain buried point object can be described as cid1: ctype1: ctraceid1: ctrp1| cid2: ctype2: ctraceid2: ctrp2.
In step S130, based on the occurrence sequence of the preset events in the application client, adding the to-be-reported buried point attribution parameter value corresponding to the preset event in the first preset storage container.
For example, according to the sequence of the preset events occurring in sequence, the attribution parameter values of the buried points to be reported corresponding to the preset events may be sequentially added to the first preset storage container. Wherein the first predetermined storage container may include a first queue.
In an exemplary embodiment, the to-be-reported buried point attribution parameter value corresponding to each preset event may be added to the queue directly based on the occurrence sequence of the preset events in the application client.
In another exemplary application scenario, during an interaction process of an application client, a situation may occur in which an original operation is interrupted halfway, and the execution is automatically continued after the operation, for example, a situation in which a flow reminding popup is displayed halfway or a reminding login interface is displayed halfway due to no login, and a situation in which a user continues to execute other operations after operating the flow reminding popup or the reminding login interface, if these events are not eliminated, the other operations that are continuously executed may be directly attributed to a button click event of the flow reminding popup or a button click event of the reminding login interface, and such attribution is obviously unreasonable.
Therefore, in the disclosure, an attribution skipping capability for intermediate steps is provided, for example, a flow reminding popup event and a reminding login event can be configured as a preset event to be deleted, so that a to-be-reported buried point attribution parameter value corresponding to the preset event to be deleted is not stored in a first preset storage container, and then other events are not attributed to the preset event to be deleted during subsequent attribution, thereby improving accuracy of automatic buried point attribution.
Based on this, another specific implementation of step S130 may include: adding a buried point attribution parameter value to be reported corresponding to a preset event in a first preset storage container based on the occurrence sequence of the preset event except the preset event to be deleted in an application program client; the preset event to be deleted is determined according to a preset page exposed in the application program client and/or a triggered preset element.
For example, the preset event to be deleted may be customized according to a requirement of a user, for example, the flow reminding page exposure event and the reminding log-in page exposure event may be configured as the preset event to be deleted, so that when it is determined that the current preset event is the preset event to be deleted, if the current page exposure event is the exposure event of the flow reminding page, the buried point attribution parameter value to be reported of the event may be continuously and automatically generated, but is not added to the first preset storage container, or the buried point attribution parameter value to be reported corresponding to the event may not be generated, which is not specially limited in the exemplary embodiment.
In an exemplary embodiment, a first preset storage container may store a preset number of to-be-reported buried point attribution parameter values, where the preset number may be customized according to a requirement, for example, the first preset storage container may store newly generated 5 to-be-reported buried point attribution parameter values. Therefore, the resource space is saved while the attribution accuracy is ensured, the calculated amount in the subsequent step of matching is reduced, the matching efficiency is improved, and the efficiency of reporting the buried point information is improved.
With continued reference to fig. 1, in step S140, a value of a target buried point attribution parameter is determined from a first preset storage container according to a type of the target buried point attribution parameter associated with the buried point object exposed by the buried point reporting event.
In an exemplary embodiment, the buried point reporting event may include one or more of a page exposure event, an event of adding a list element to a playlist, and an event of a list element of a playlist being played. That is to say, the buried point reporting event may also be a certain preset event, the buried point reporting event may be customized according to a requirement, and the user may determine the buried point reporting event according to an event attributed to the buried point according to the requirement.
In an application program interface, only a small amount of necessary information such as resource id is often selected to be issued in external stream distribution of a page for stability of interface performance. When a user operates to open a corresponding bottom page, a request is often sent to acquire more information to support jumping or playing, and at the moment, the user also clicks other elements, so when the interface returns and real page jumping or playing occurs, if direct attribution is automatically performed according to the sequence of events, errors often occur, and attribution errors are caused.
Therefore, in the present disclosure, a toid (target object identifier) attribute is added to content information of a buried point object, and is used to identify a buried point object identifier oid of a target page to be opened by a current element, that is, the oid of the target page that can be opened after the current element is triggered, so that when the target page is exposed and a click event is found back, matching can be performed according to the toid to perform accurate search, and accuracy of buried point attribution is improved.
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 a buried point object identifier of a root page of the page that can be exposed after the buried point object associated with the preset event is triggered.
As described above, the embedded point identifier of the embedded point object exposed by the embedded point reporting event may be matched with the target object identifier in the to-be-reported embedded point attribution parameter values stored in the first preset storage container, so as to determine the value of the target embedded point attribution parameter from the first preset storage container according to the matching result, and then attributing the embedded point reporting event based on the value of the target embedded point attribution parameter.
Fig. 5 shows a schematic flow diagram of a method of determining a value of a target buried point attribution parameter according to an embodiment of the present disclosure. Referring to fig. 5, the method may include steps S510 to S520.
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 the attribution parameter value of each to-be-reported buried point stored in the first preset storage container.
For example, as described above, the buried point attribution parameter value to be reported is generated according to the pit bit information and the content information of the buried point object, and the content information of the buried point object includes the target object identifier, so the buried point attribution parameter value to be reported also includes the target object identifier. Therefore, the buried point object identifier of the buried point object reported by the buried point report event can be matched with the target object identifier included in the attribution parameter value of each buried point to be reported stored in the first preset storage container.
In step S520, a value of the target buried point attribution parameter is determined according to the matching result.
For example, the following describes a specific implementation of step S520 with reference to fig. 6. Fig. 6 shows a flow chart of a method for determining a value of a target buried point attribution parameter according to a matching result according to an embodiment of the present disclosure. Referring to fig. 6, the method may include steps S610 to S650. Wherein: 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, determining a first buried point attribution parameter value to be reported according to the buried point attribution parameter value to be reported containing the successfully matched target object identifier; in step S630, determining a second to-be-reported buried point attribution parameter value from the first preset storage container; the second buried point attribution parameter value to be reported comprises a buried point attribution parameter value to be reported corresponding to the latest page exposure event stored in the first preset storage container; in step S640, determining a value of the target buried point attribution parameter according to a larger generation time of the first to-be-reported buried point attribution parameter value and the second to-be-reported buried point attribution parameter value; in step S650, a value of the target buried point attribution parameter is determined according to the buried point attribution parameter value to be reported that is added in the first preset storage container last time.
For example, when matching is successful, the to-be-reported buried point attribution parameter value including the successfully-matched target object identifier may be used as a first to-be-reported buried point attribution parameter value, then, the to-be-reported buried point attribution parameter value corresponding to the latest page exposure event stored in the first preset storage container is determined as a second to-be-reported buried point attribution parameter value, and a value of the target buried point attribution parameter is determined according to the to-be-reported buried point attribution parameter value generated later in the first to-be-reported buried point attribution parameter value and the second to-be-reported buried point attribution parameter value.
Taking the current page 2 exposure event and the page exposure event added last time in the first preset storage container as the page 1 exposure event as an example, the page 2 just starts to be exposed, so the attribution parameter value of the buried point to be reported corresponding to the page 2 exposure event is not added into the first preset storage container yet. In order to attribute the exposure event of the page 2, the buried object identifier of the root page of the page 2 may be matched with the target object identifier included in the buried point attribution parameter value to be reported stored in the first preset storage container, and if a certain buried point attribution parameter value to be reported is successfully matched but the generation time of the certain buried point attribution parameter value to be reported is earlier than the buried point attribution parameter value to be reported corresponding to the exposure event of the page 1, it indicates that the exposure event of the page 1 still occurs between the preset event indicated by the buried point attribution parameter value to be reported which is successfully matched and the exposure event of the page 2, and the exposure event of the page 2 should be the exposure event attributed to the page 1, but not the preset event indicated by the buried point attribution parameter value to be reported which is successfully matched. Therefore, in order to accurately perform buried point attribution, when matching is successful, generation time of a first buried point attribution parameter value to be reported which is successfully matched and generation time of a second buried point attribution parameter value to be reported which corresponds to a page exposure event added last time in a first preset storage container need to be compared, and a preset event indicated by the buried point attribution parameter value to be reported after the generation time is used for attributing a current buried point reporting event.
And when the matching fails, determining the value of the target buried point attribution parameter directly according to the buried point attribution parameter value to be reported, which is added in the first preset storage container for the last time.
Next, a method for determining a target buried point attribution parameter value in the present disclosure will be further described with reference to fig. 7. Referring to fig. 7, the method of matching based on the buried point object identification to determine the target buried point attribution parameter value may include steps S710 to S760. Wherein: in step S710, in response to the occurrence of the root page exposure event, matching the buried object identifier of the root page with the target object identifier in the to-be-reported buried point attribution parameter value in the first preset storage container; in step S720, determining whether the matching is successful, if so, going to step S730, otherwise going to step S760; in step S730, a second to-be-reported buried point attribution parameter value corresponding to the page exposure event that was added to the first preset storage container most recently is obtained; in step S740, the generation time of the successfully matched first to-be-reported buried point attribution parameter value and the successfully matched second to-be-reported buried point attribution parameter value is compared;
in step S750, the larger generation time of the first to-be-reported buried point attribution parameter value and the second to-be-reported buried point attribution parameter value is determined as the value of the target buried point attribution parameter; in step S760, a value of the target buried point attribution parameter is determined according to the to-be-reported buried point attribution parameter value that is recently added to the first preset storage container.
In an exemplary embodiment, the types of the target buried point attribution parameters include one or more of a first type, a second type, a third type, a fourth type, a fifth type, a sixth type, and a seventh type. Of course, the target buried point attribution parameter may also include other types, which may be configured by user-defined according to the requirement of the user, and this exemplary embodiment is not limited to this.
The first type of target buried point attribution parameter is used for describing an exposure source of a root page of a page exposed by a buried point reporting event; the second type of target buried point attribution parameter is used for describing a creation source of a root page of a page exposed by a buried point reporting event; the third type of target buried point attribution parameter is used for describing page exposure sources of a plurality of pages before the current page exposure; the fourth type of target buried point attribution parameter is used for describing page creation sources of a plurality of pages before the current page is exposed; a fifth type of target buried point attribution parameter is used for describing which page of the first page of the application client the occurrence of the current event originates from; a sixth type of target buried point attribution parameter is used for describing a source when a list unit is added to a playlist, such as a source when a song is added to a song playing category; the seventh type of target buried point attribution parameter is used to describe the operation source of the content of the list unit in the playlist, such as the source when the song in the playlist starts playing.
In one exemplary embodiment, where the buried point reporting event comprises a page exposure event, the type of the target buried point attribution parameter comprises a 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 a first type.
Fig. 8 shows a flow chart of a method of determining a value of a first type of target buried point attribution parameter according to an embodiment of the present disclosure, and referring to fig. 8, the method may include steps S810 to S820. Wherein: in step S810, when a new page is exposed in the application client, matching the embedded object identifier of the exposed new page with the target object identifier in the attribution parameter values of the embedded points to be reported stored in the first preset storage container; in step S820, a value of the first type of target buried point attribution parameter is determined according to the matching result.
For example, as described above, the first type of target buried point attribution parameter is used to characterize the exposure source of the root page of the page exposed by the buried point reporting event, i.e. the first type of target buried point attribution parameter is updated when a new page exposure occurs. In other words, when a new root page is exposed, a first type target buried point attribution parameter value can be determined in the first preset storage container according to the buried point object identifier of the newly exposed root page, and the first type target buried point attribution parameter value is reported, so that an exposure source of the exposed new page is determined based on the first type target buried point attribution parameter value, and the exposure of the new page is attributed to the source.
The above-mentioned specific implementation of step S820 may refer to the above-mentioned specific implementation of step S520, and is not described herein again.
In an exemplary embodiment, where the buried point reporting event comprises a page exposure event, the type of the target buried point attribution parameter may also comprise 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.
Fig. 9 shows a schematic flow diagram of a method of determining a value of a second type of target buried point attribution parameter, according to an embodiment of the present disclosure. Referring to fig. 9, the method may include steps S910 to S920. Wherein: in step S910, in a case that the page exposed in the application client is a newly created page, matching the buried object identifier of the exposed page with the target object identifier in the attribution parameter values of the to-be-reported buried points stored in the first preset storage container; in step S920, according to the matching result, a value of the second type target buried point attribution parameter is determined.
For example, as described above, the second type of target buried-point attribution parameter is used to characterize a creation source of a root page of a page exposed by a buried-point reporting event, that is, the second type of target buried-point attribution parameter is updated when a new page is created. In other words, when an event of creating a new root page occurs, a value of a second type of target buried point attribution parameter may be determined in the first preset storage container according to a buried point object identifier of the created new root page, and the value of the second type of target buried point attribution parameter may be reported, so as to determine a source of the created new root page based on the value of the second type of target buried point attribution parameter, for example, which element is clicked on which page to cause a current new root page to be created, so as to create an attribution for the created new root page.
For a specific implementation of the step S920, reference may be made to the step S520, which is not described herein again.
Figure 10 shows a schematic flow diagram of another method of determining a value of a first type of target buried point attribution parameter, according to embodiments of the present disclosure. Referring to fig. 10, the method may include steps S1010 to S1060. Wherein: in step S1010, it is determined whether a new root page is currently exposed, if so, go to step S1020, otherwise, go to step S1060; in step S1020, a buried object identifier of the newly exposed root page is obtained; in step S1030, selecting a value of a target buried point attribution parameter in a first preset storage container based on the buried point object identifier of the root page; in step S1040, determining the value of the selected target buried point attribution parameter as the value of the first type of buried point attribution parameter of the currently exposed root page; in step S1050, generating an attribution parameter value of a buried point to be reported corresponding to the root page to be exposed, adding the attribution parameter value to the first preset storage container, and going to step S1060; in step S1060, exposure is performed.
For a specific implementation of selecting a value of an attribution parameter of a target embedded point in a first preset storage container based on an embedded point object identifier of a root page, reference may be made to the processes shown in fig. 5 and fig. 6, which are not described herein again.
Similarly, the value of the second type target buried point attribution parameter may also be determined by the method shown in fig. 10, and the step S1010 is replaced by "determining whether a new root page is created at present", and the remaining steps are not changed, and are not described again here.
In the present disclosure, the first type of target buried point attribution parameter and the second type of target buried point attribution parameter are used to characterize the source of the currently exposed root page, which can be used to analyze which pit bit was clicked in the previous page to cause the exposure of the current page when a page switch event occurred. The first type of target embedded point attribution parameter represents an exposure source of a currently exposed page and is updated after the page enters a lower-level page and returns, and the second type of target embedded point attribution parameter represents a creation source of the currently exposed page and is not updated after the page enters the lower-level page and returns.
The first type of target buried point attribution parameter and the second type of target buried point attribution parameter will be further described with reference to fig. 11. As shown in fig. 11, the user clicks on the song form 1 in page 1 resulting in a first exposure of page 2, then clicks on the song form card 2 in page 2 resulting in a first exposure of page 3, and clicks on the back button 111 in page 3 resulting in a second exposure of page 2.
For the first exposure event of the page 2, the value of the first type of target buried point attribution parameter is the same as the value of the second type of target buried point attribution parameter, and the values of the target buried point attribution parameter to be reported are all the buried point attribution parameter values corresponding to the clicking song list 1 event in the page 1, that is, the exposure source and the creation source of the page 2 are both the events of clicking song list 1 in the page 1. For the first exposure event of the page 3, the values of the target buried point attribution parameters of the first type and the second type are also the same, and the values of the to-be-reported buried point attribution parameters corresponding to the event of clicking the singing sheet card 2 in the page 2 are both the same.
However, for the second exposure event of the page 2, the value of the first type of target buried point attribution parameter is different from the value of the second type of target buried point attribution parameter, the value of the first type of target buried point attribution parameter is the value of the buried point attribution parameter to be reported corresponding to the event of clicking the return button 111 in the page 3, and for the second type of target buried point attribution parameter, the value of the second type of target buried point attribution parameter at the second exposure of the page 2 is the same as the value of the second type of target buried point attribution parameter at the first exposure of the page 2, and both are the values of the buried point attribution parameter to be reported corresponding to the event of clicking the song list 1 in the page 1 at the time of creating the page 2, because the value of the first type of target buried point attribution parameter is updated only when a new page is created.
In an exemplary embodiment, in the case that the buried point reporting event comprises a page exposure event and the type of the target buried point attribution parameter comprises a first type, the type of the target buried point attribution parameter may also comprise a third type.
For example, fig. 12 shows a flow chart diagram of a method for determining a value of a third type of target buried point attribution parameter according to an embodiment of the present disclosure. Referring to fig. 12, the method of determining the value of the third type of target buried point attribution parameter may include steps S1210 to S1230. Wherein:
in step S1210, based on the page exposure sequence in the application client, in response to the root page exposure occurring in the application client, adding the value of the first type of target buried point attribution parameter corresponding to the newly exposed root page to a second preset storage container; in step S1220, when the number of values of the first type of target buried point attribution parameter stored in the second preset storage container is greater than the first preset value, deleting the value of the first type of target buried point attribution parameter added with the earliest time in the second preset storage container from the second preset storage container; in step S1230, a value of a third type of target buried point attribution parameter is determined according to a second preset storage container.
For example, the third type of target buried point attribution parameter may be used to store behavior links of multiple root page exposures before the current root page exposure, a queue with a length of N may be maintained, that is, the second preset storage container may include a second queue, the first preset value may be N, when a new root page is exposed, the value of the first type of target buried point attribution parameter determined according to the new root page exposure event is pushed to the topmost layer of the second queue, and when the length of the second queue exceeds N, the value of the first type of target buried point attribution parameter at the bottommost in the second queue is pushed out, so that the value of the third type of target buried point attribution parameter is determined according to the second queue.
In other words, the values of the third type of target buried point attribution parameter may be used to analyze the user behavior path that resulted in the exposure of the current root page.
In an exemplary embodiment, in the case that the buried point reporting event includes a page exposure event and the type of the target buried point attribution parameter includes a second type, the type of the target buried point attribution parameter may also include a fourth type.
For example, fig. 13 shows a schematic flow chart of a method for determining a value of a fourth type of target buried point attribution parameter according to an embodiment of the present disclosure. Referring to fig. 13, the method may include steps S1310 to S1330. Wherein:
in step S1310, based on the page exposure order in the application client, in response to the root page exposure occurring in the application client, adding the value of the second type of target buried point attribution parameter corresponding to the newly exposed root page to a third preset storage container; in step S1320, when the number of the values of the second-type target buried point attribution parameter stored in the third preset storage container is greater than the second preset value, deleting the value of the second-type target buried point attribution parameter with the earliest addition time in the third preset storage container from the third preset storage container; in step S1330, a value of a fourth type of target buried point attribution parameter is determined according to a third preset storage container.
For example, the fourth type of target buried point attribution parameter may be used to store behavior links created by a plurality of root pages before the current root page is exposed, and a queue with a length of M may be maintained, that is, the third preset storage container may include a third queue, and the second preset value may be M, when a new root page is exposed, the value of the second type of target buried point attribution parameter determined according to the new root page exposure event is pushed to the topmost layer of the third queue, and when the length of the third queue exceeds M, the value of the second type of target buried point attribution parameter at the bottommost in the third queue is pushed out, so that the value of the fourth type of target buried point attribution parameter is determined according to the third queue.
In other words, the values of the fourth type of target buried point attribution parameter may be used to analyze a creation path of a plurality of root pages before a current root page is created.
Taking the length of the third queue as 3, the page exposure sequence after the application client is opened is page 1, page 2, page 3 and page 4, and the values of the second type of target buried point attribution parameters respectively determined at the time of page 1 exposure, page 2 exposure, page 3 exposure and page 4 exposure are psrefer1, psrefer2, psrefer3 and psrefer4 as examples, where the value of the third queue is [ psrefer1] at the time of page 2 exposure, the values stored in the third queue are [ psrefer1 and psrefer2] at the time of page 1 exposure, the values of the third queue are [ psrefer1, psrefer2 and psrefer3] at the time of page 3 exposure, and the values of the third queue are [ psrefer2, refer3 and psrefer4] at the time of page 4 exposure.
By automatically generating the values of the attribution parameters of the target buried points of the third type and the fourth type, attribution analysis can be automatically performed on the operation path causing page exposure and the operation path causing page creation in the application client, and the accuracy and the efficiency of page source analysis are improved.
As can be seen from the foregoing analysis, the cause of the current page exposure or creation may be analyzed based on the values of the first type or second type of target buried point attribution parameters, and the cause of the current page exposure or creation may be analyzed based on the values of the third type or fourth type of target buried point attribution parameters, which are analyzed in multiple steps, so as to obtain the behavior path causing the current page exposure or creation. In some scenarios, however, there are situations where the user's behavior is in depth all the time, resulting in an overall traceable attribution link that is too long. The structure of the top page of an application client has a great influence on the cognition and operation of a user, so that in some cases, the consumption depth and accumulation condition required to be generated from the top page of the application client are crucial to attribution analysis, and any multi-step behavior after the top page is required to be attributed to a certain page of the top page.
Based on this, a fifth type of target-buried-point attribution parameter is provided in the present disclosure, by which the source of any multi-step behavior after the top page in the top page can be analyzed, i.e., on which page in the top page any behavior after the top page is caused.
In an exemplary embodiment, in a case where the target buried point attribution parameter includes a fifth type and the second type described above, the value of the target buried point attribution parameter of the fifth type may be determined by the method illustrated in fig. 14. Referring to fig. 14, the method may include steps S1410 through S1420.
In step S1410, the buried object identifier of the buried object exposed by the buried reporting event is matched with the preset buried object identifier.
The preset buried object identifier comprises a buried object identifier corresponding to a root page of a head page of the application client. For example, page 1 in fig. 11 is the home page of an application client, which includes 7 root pages of "synthesis, single song, song list, video, lyrics, sound, and podcast", and the root page "song list" page is shown in fig. 11. For the application client, the preset buried object id may include buried object ids corresponding to 7 root pages of "composition, single song, song list, video, lyrics, voice, and podcast".
With continued reference to fig. 14, in step S1420, values of the fifth type of target buried point attribution parameter are determined according to the matching result.
In an exemplary embodiment, in a case that the matching between the buried object identifier of the buried object exposed by the buried reporting event and the preset buried object identifier is successful, the value of the target buried point attribution parameter of the fifth type may be determined according to the value of the second type of the buried point attribution parameter corresponding to the buried object indicated by the preset buried object identifier that is successfully matched.
If the buried point object identifier of the buried point object exposed by the buried point reporting event is successfully matched with the preset buried point object identifier, it indicates that the buried point object exposed by the current buried point reporting event is the buried point object corresponding to a certain root page of the home page, and the value of the target buried point attribution parameter of the fifth type can be updated directly according to the value of the target buried point attribution parameter of the second type corresponding to the root page successfully matched, that is, the value of the target buried point attribution parameter of the fifth type corresponding to the current buried point reporting event is determined as the value of the target buried point attribution parameter of the second type corresponding to the root page successfully matched.
In another exemplary embodiment, in a case that the matching between the buried object identifier of the buried object exposed by the buried reporting event and the preset buried object identifier fails, the value of the attribution parameter of the fifth type of the target buried point may be determined by the method shown in fig. 15. Referring to fig. 15, in the case that the matching between the buried object identifier of the buried object exposed by the buried reporting event and the preset buried object identifier fails, the method for determining the value of the target buried parameter of the fifth type may include steps S1510 to S1530. Wherein:
in step S1510, under the condition that the matching between the buried object identifier of the buried object exposed by the buried reporting event and the preset buried object identifier fails, the buried object identifier corresponding to the root page of the page where the buried object exposed by the buried reporting event is located is obtained.
For example, if the matching between the buried object identifier of the exposed buried object of the buried reporting event and the preset buried object identifier fails, it indicates that the presently exposed buried object of the buried reporting event is not a certain root page of the top page, and may be a sub-page of a certain root page, and in order to attribute the presently exposed buried object of the buried reporting event to the root page, the buried object identifier corresponding to the root page of the page where the buried object exposed by the buried reporting event is located may be obtained, and then the value of the target buried object attribution parameter of the fifth type is determined according to the subsequent steps S1520 and S1530.
In step S1520, the buried object identifier corresponding to the root page is matched with the target object identifier in the to-be-reported buried-point attribution parameter values stored in the first preset storage container, so as to determine the target to-be-reported attribution parameter value.
For example, one specific implementation of step S1520 may include: under the condition that the buried object identifier corresponding to the root page is successfully matched with the target object identifier in the buried point attribution parameter values to be reported stored in the first preset storage container, determining a target buried point attribution parameter value to be reported according to the buried point attribution parameter value to be reported which is successfully matched; and under the condition that matching between the embedded point object identifier corresponding to the root page and the target object identifier in the embedded point attribution parameter values to be reported stored in the first preset storage container fails, determining the target embedded point attribution parameter values to be reported according to the embedded point attribution parameter values to be reported which are added to the first preset storage container for the last time.
Next, in step S1530, the buried point object id included in the attribution parameter value to be reported by the target is matched with the preset buried point object id, and the value of the target buried point attribution parameter of the fifth type is determined according to the matching result.
For example, a specific implementation of step S1530 may include: under the condition that the matching between the embedded point object identifier contained in the attribution parameter value to be reported by the target and the preset embedded point object identifier is successful, updating the value of the attribution parameter of the target embedded point of the fifth type according to the value of the attribution parameter of the embedded point of the second type corresponding to the embedded point object indicated by the preset embedded point object identifier which is successfully matched; and under the condition that the matching between the buried point object identifier contained in the attribution parameter value to be reported by the target and the preset buried point object identifier fails, the value of the attribution parameter of the target of the fifth type is not updated.
For example, if the buried point object identifier included in the attribution parameter value to be reported by the target is successfully matched with the preset buried point object identifier, it indicates that the current buried point reporting event can be attributed to the root page of the top page corresponding to the successfully matched preset buried point object identifier, so that the value of the attribution parameter of the target buried point of the fifth type can be updated. If the matching fails, it indicates that no operation is currently performed in the new root page, so the value of the fifth-type target buried point attribution parameter is not updated, that is, the value of the fifth-type target buried point attribution parameter corresponding to the current buried point reporting event is the same as the value of the fifth-type target buried point attribution parameter corresponding to the previous buried point reporting event.
In another exemplary embodiment, the technical term "the value of the second type of target buried point attribution parameter" in the method for determining the value of the fifth type of target buried point attribution parameter may also be replaced with "the value of the first type of target buried point attribution parameter", and other implementation processes are not changed, so as to determine the value of the fifth type of target buried point attribution parameter based on the value of the first type of target buried point attribution parameter corresponding to the root page of the top page, which is not described herein again.
Fig. 16 shows a schematic flow chart of yet another method of determining a value of a fifth type of target buried point attribution parameter according to an embodiment of the present disclosure. Referring to fig. 16, the method may include steps S1610 to S1680. Wherein: in step S1610, a buried point object identifier of a buried point object exposed by a buried point reporting event is matched with a preset buried point object identifier; in step S1620, determining whether the matching is successful, if so, going to step S1630, otherwise, going to step S1640; in step S1630, 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, determining a value of a fifth type of target buried point attribution parameter, and going to step S1670 to step S1680; in step S1640, a buried point object identifier corresponding to a root page of a page where a buried point object exposed by the buried point reporting event is located is obtained; in step S1650, determining an attribution parameter value of a target buried point to be reported from a first preset storage container according to the buried point object identifier corresponding to the root page; in step S1660, determining whether the attribution parameter value of the buried point to be reported is verified, if so, going to step S1670, otherwise going to step S1680; in step S1670, the value of the attribution parameter of the target buried point of the fifth type is updated in the public parameter reported by the buried point; in step S1680, exposure is performed.
The step S1650 may refer to a specific implementation of the step S1520, and the step S1660 may refer to the step S1530, which is not described herein again. It should be noted that, the verification in step S1660 may be understood that the matching between the buried object identifier included in the attribution parameter value to be reported and the preset buried object identifier is successful, and the verification failure may be understood as the matching between the buried object identifier included in the attribution parameter value to be reported and the preset buried object identifier being failed.
In an exemplary scenario, the playlist playing is an accompanying function, and the event may not require the user to operate the trigger all the time, for example, when the user clicks a certain song in the playlist to play, the song of the entire playlist may be added to the playlist, such as clicking the playlist 1 on page 1 in fig. 11, and all the songs in the playlist 1 are added to the playlist displayed on page 2 in fig. 11. In the automatic playing scene, after the played clicked song is finished, the new song in the playlist can be continuously played without any operation of the user, so that a new playing event is automatically generated. The attribution of the event of the song clicking can be accurately extracted through the values of the attribution parameters of one or more target buried points in the first type, the second type, the third type, the fourth type and the fifth type, but when a candidate automatic playing event occurs, a user is likely to generate other operation behaviors, and the attribution of the automatic playing event according to the attribution parameter values of the buried points to be reported corresponding to each operation behavior during automatic playing is inevitably inaccurate.
To ensure accuracy of auto-play event attribution, events in which a list unit is added to a playlist may be attributed by a sixth type of target buried point attribution parameter and list unit play events in the playlist may be attributed by a seventh type of target buried point attribution parameter in the present disclosure.
Based on this, in an exemplary embodiment, the buried point reporting event may be and include an event that adds a list element to the playlist. In the case that the buried point reporting event includes an add list unit to playlist event, the types of the target buried point attribution parameter may also include a sixth type, where the sixth type of target buried point attribution parameter is used to characterize a reason why a list unit is added to a playlist.
Fig. 17 shows a schematic flow diagram of a method of determining a value of a sixth type of target buried point attribution parameter, according to an embodiment of the present disclosure. Referring to fig. 17, the method may include steps S1710 to S1720. Wherein:
in step S1710, in response to the occurrence of an event of adding a list unit to a playlist by the application client, matching a buried object identifier corresponding to a buried object exposed by the event of adding the list unit to the playlist with a target object identifier included in buried object attribution parameter values to be reported stored in a first preset storage container;
in step S1720, according to the matching result, a value of a sixth type of target buried point attribution parameter is determined.
For example, in a case that the buried point reporting event includes an add list element to playlist event, an embodiment of the step S510 may include the step S1710, and an embodiment of the step S520 may include the step S1720. For a specific implementation of step S1720, reference may be made to the above-mentioned specific implementation of step S520, and the technical term "value of the target buried point attribution parameter" in the specific implementation of step S520 may be replaced with "value of the sixth type of target buried point attribution parameter", which is not described herein again.
In other words, the types of target buried-point attribution parameters associated with the buried point objects exposed by the playlist-add-list-unit event include a sixth type, and the target buried-point attribution parameters of the sixth type may be associated with the buried point objects possibly exposed by the playlist-add-list-unit event in advance, so that when the playlist-add-list-unit event occurs in the application client, the values of the target buried-point attribution parameters of the sixth type may be determined based on the above-mentioned steps S1710 to S1720 directly according to the target buried-point attribution parameters of the sixth type previously associated with the buried point objects exposed by the event.
It should be noted that, for the target buried point attribution parameters of the first type, the second type, the third type, the fourth type and the fifth type, the target buried point attribution parameters may be associated with the buried point objects exposed by the corresponding buried point reporting events in advance, so that when the corresponding event occurs in the application client, the value of the target buried point attribution parameter of the corresponding type may be determined directly according to the type of the target buried point attribution parameter associated with the corresponding event.
The source from which the list unit is added to the playlist may be attributed by determining the value of the sixth type of target buried point attribution parameter, e.g., when the playlist is a playlist of songs, the reason why a certain song is added to the playlist of songs may be analyzed.
In an exemplary embodiment, the buried point reporting event may further include a playlist unit played event of the playlist. In a case that the buried point reporting event includes a playlist unit played event of a playlist, the type of the target buried point attribution parameter includes a seventh type. Wherein the seventh type of target buried point attribution parameter is used for characterizing a reason why a list unit in the playlist is played.
For example, fig. 18 shows a flow chart diagram of a method for determining a value of a target buried point attribution parameter of a seventh type according to an embodiment of the present disclosure. Referring to fig. 18, the method may include steps S1810 to S1820. Wherein:
in step S1810, in response to a play event of a list unit in a play list occurring at the application client, matching a buried object identifier of a buried object exposed by the play event of the list unit with a target object identifier included in a buried-point attribution parameter value to be reported stored in the first preset storage container;
in step S1820, a value of the seventh type of target buried point attribution parameter is determined according to the matching result.
For example, in a case that the buried point reporting event includes a playlist unit played event of a playlist, the step S510 may include the step S1810, and the step S520 may include the step S1820. In the specific implementation of step S1820, reference may be made to the above specific implementation of step S520, and the technical term "value of the target buried point attribution parameter" in the specific implementation of step S520 may be replaced by "value of the seventh type of target buried point attribution parameter", which is not described herein again.
In other words, the types of the target buried point attribution parameters associated with the buried point objects exposed by the play events of the list elements in the play list include a seventh type, and the seventh type of the target buried point attribution parameters may be associated with the buried point objects possibly exposed by the play events of the list elements in the play list in advance, so that when the play events of the list elements in the play list occur in the application client, the values of the seventh type of the target buried point attribution parameters may be determined based on the steps S1810 to S1820 described above directly according to the seventh type of the target buried point attribution parameters associated with the buried point objects exposed by the events in advance.
The determined value of the seventh type target buried point attribution parameter can be used for attributing an event that the content in any list unit in the playlist is played, for example, when the playlist is a song playlist, the operation origin of starting playing of the song can be analyzed, namely, the reason why a certain song is played is analyzed.
The sixth type and the seventh type of target buried point attribution parameter values are further described below by taking a process schematic diagram of user operation behaviors in an exemplary embodiment of the present disclosure shown in fig. 19 as an example. Referring to fig. 19, a song list is displayed in a page 1, i.e., a search result page, a song _2 unit is clicked, 6 songs are added to the playlist, and play is started from song _2 while a page 2, i.e., a play page, in fig. 19 is entered. At this time, for the page 2, the value of the first type of buried point attribution parameter is the value of the buried point attribution parameter to be reported corresponding to the click event of the song unit of the search result page song list song _ 2.
Taking the example of opening actseq =1, pgstep =3 corresponding to the search result page event in fig. 19, when the song _2 is clicked on the search result page, actseq =2, pgstep =3 corresponding to the event, the pit bit information of the exposed buried dot object is song2| search result page, clicking on the search results page song _2 may cause 6 songs from the search results page to be added to the playlist and the play page (e.g., page 2 in fig. 9) to be opened, and then song _2 begins to be played in the play page, when actseq =1 and pgstep =4.
After clicking song _2 on the search result page to add 6 songs to the playlist, the songs in the playlist may be automatically played from song _2, and when the songs are automatically played to song _4, the user clicks the control 191 for playing the next song on page 2 in fig. 19, the played song is switched to song _5, the action seq =2, and pgstep =4 corresponding to the control 191 event is clicked. Then, during the playing of the song _5, the user again clicks the song _ x2 in page 3 of fig. 19, thereby adding song x2 to the playlist after the currently playing song 5, the generated new playlist is as shown in page 4 in fig. 19, taking action seq =1, pgstep =10 as an example when the user opens page 3, and action seq =2, pgstep =11 when the user clicks song _ x 2.
For songs song _1, song _2, song _3, song _4, song _5, song _6, which are added to the playlist when the search result page clicks on song _2, the values of their corresponding sixth type of target buried point attribution parameters are the same, may be represented as [ e ] [2] [3] [ song _ 2] search result page ], which is added to the playlist upon a personal homepage click for the song _ x2, so the value of its corresponding target buried point attribution parameter of the sixth type may be represented as [ e ] [2] [11] [ song _ x 2] personal homepage ].
For the playback of song _2, the immediate reason is the click of the search result page song _2, whose corresponding value of the seventh type of target buried point attribution argument may be represented as [ e ] [2] [3] [ song _2| search result page ], for the playback of song _3 and song _4, the player automatically switches to the next, so the values of the seventh type of target buried point attribution argument corresponding to the playback events of song _3 and song _4 may both be auto _ next, for song _5, which is played when the playback page clicks to play the next control, and its corresponding value of the seventh type of target buried point attribution argument may be represented as [ e ] [2] [4] [ play the next control | playback page ].
The target embedded point attribution parameters of the first type, the second type, the third type, the fourth type, the fifth type, the sixth type and the seventh type can automatically attribution various behaviors in the application program client, and further values of the target embedded point attribution parameters of the corresponding types can be reported, so that the efficiency of attribution of embedded points is improved.
Next, with continued reference to fig. 1, in step S150, the buried point object exposed by the buried point reporting event is subjected to buried point information reporting based on the value of the target buried point attribution parameter.
For example, a specific implementation of step S150 may include: and taking the value of the attribution parameter of the target buried point 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.
For example, corresponding embedded point information reporting parameters may be configured for different embedded point objects in advance, and the configured embedded point information reporting parameters may include the target embedded point attribution parameters. Therefore, when a buried point reporting event occurs in the application program client to cause exposure of the corresponding buried point object, 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 service end can directly obtain the reason of the event occurring in the application program client according to the reported embedded point information, and the embedded point attribution analysis efficiency is improved. And the attribution is carried out in the process of reporting the buried point information, and compared with the method of carrying out attribution after sequencing on an analysis side, the accuracy of the attribution of the buried points can be improved because the delay of the buried point data does not exist.
In an exemplary scenario, for an application with a large amount of history stock, it is often difficult to ensure that all interactive and meaningful pit bits are buried, when some pit bits are not covered by buried dots (i.e. the oid identifier is not set, i.e. unknown), when a new page exposure or other event is fired at the pit bit, the pit bit cannot be automatically attributed based on the above method because the oid identifier is not configured to the pit bit, and thus, event information on the current pit bit is lost, and a new page exposure caused by the current event is attributed to other events before the current event, thereby causing an attribution error. To solve this problem, a preset identification field is introduced in the present disclosure to identify and downgrade the attribution of events occurring on pit bits without buried dots to the page where the pit bits are located. The preset identification field may be self-defined according to a requirement, for example, the preset identification field may be an undefined-xpath field, and certainly, may also be another field, which is not particularly limited in this exemplary embodiment.
Based on this, the method for reporting the embedded point information in the present disclosure may further include: when a preset event occurs in an application program client, if the preset event does not have a related buried point object, determining a root page where an element corresponding to the preset event is located; determining an attribution parameter value of the buried point to be reported corresponding to a preset event according to the attribution parameter value of the buried point to be reported corresponding to the root page and a preset identification field; the preset identification field is used for marking the buried point attribution parameter value to be reported as the buried point attribution parameter value to be reported generated after the position of the buried point object in the application program client is triggered.
For example, no buried object identifier is configured for the element e1 in the page a, that is, no buried object is performed at the position of the element e1 in the page a. However, when the user operates in the application client, the element e1 in the page a is clicked, and as the embedded point object identifier is not configured for the element e1, that is, the embedded point is not performed at the position of the element e1 in the page a, the pit bit information at the position cannot be represented, and the embedded point attribution parameter value to be reported at the position cannot be automatically generated. At this time, the attribution parameter value of the buried point to be reported corresponding to the exposure of the root page a where the element e1 is located may be obtained, and the attribution parameter value of the buried point to be reported and the preset identification field are spliced to obtain the attribution parameter value of the buried point to be reported corresponding to the clicked event of the element e1 in the page a, and the attribution parameter value of the buried point to be reported is stored in the first preset storage container.
Taking the example that the element e1 in the page a is clicked to cause the exposure of the page B, when the exposure event of the page B is attributed, there may be two to-be-reported buried point attribution parameter values successfully matched in the first preset storage container, one is the to-be-reported buried point attribution parameter value 1 corresponding to the page a exposure event, and the other is the to-be-reported buried point attribution parameter value 2 corresponding to the clicked event of the element e1 in the page a, the to-be-reported buried point attribution parameter value with the most recent generation time can be determined as the target buried point attribution parameter value corresponding to the exposure event of the page B, it is certain that the exposure event of the page a is a previous exposure event, and the element e1 event is clicked in the page a again, so that the value of the target buried point attribution parameter value corresponding to the exposure event of the page B is the to-be-reported buried point attribution parameter value 2, if the matching is not successful, the most recently added to-be-reported buried point attribution parameter value 2 is determined as the target point attribution parameter value corresponding to the exposure event of the page B, and the exposure event of the page B is attributed to a relatively accurate position, although the page a result that the exposure event is not attributed to the page B, the page B is not attributed, but the page B, and the page B, the page B is not attributed.
In other words, when the buried point is subsequently checked, the position where the buried point does not exist in the page a can be directly known according to the preset identification field, and the position is triggered by the user, so that a service person can quickly find the position where the buried point does not exist in the subsequent analysis and determine whether the buried point needs to be buried in the position.
In the method, the attribution parameter value of the buried point to be reported is generated based on the common attribution capability and attribution format facing to the buried point object, so that the buried point of the user behavior is automatically generated and recorded, further, the automatic attribution of the buried point reporting event can be realized in various complex business scenes, and the efficiency of attribution of the buried point is improved.
Meanwhile, the buried point attribution parameter value to be reported is generated based on the general attribution capability and the attribution format, so that the buried point reporting event is automatically attributed through the matching of the target object identifier included in the buried point attribution parameter value to be reported and the buried point object identifier exposed by the buried point reporting event, and the accuracy of the buried point attribution can be improved. And based on the universal buried point attribution capability, the maintenance cost attributed to the buried point can be reduced.
Further, in the disclosure, by considering the conditions of the second page exposure event, the automatic trigger event, and the like, the automatic playback event, and the like, which enters the application client from the third-party application program and is in the application client, can be accurately attributed, and the accuracy of the automatic attribution of the buried point is ensured.
In addition, in the present disclosure, different events in the application client can be accurately attributed from different aspects through the values of the target buried point attribution parameters of multiple types.
Exemplary devices
The exemplary embodiment of the present disclosure further provides a device for reporting the embedded point information. Referring to fig. 20, the device 2000 for reporting buried point information may include a preset event response module 2010, a module 2020 for generating a value of a to-be-reported buried point attribution parameter, an adding module 2030, a module 2040 for determining a value of a target buried point attribution parameter, and a module 2050 for reporting buried point information, where:
the preset event response module 2010 is configured to respond to a preset event occurring in an application client, and determine a buried point object associated with the preset event; the buried point attribution parameter value to be reported generating module 2020 is configured to generate a buried point attribution parameter value to be reported corresponding to the preset event according to the pit bit information and the content information of the buried point object associated with the preset event; an adding module 2030, configured to add, in a first preset storage container, the to-be-reported buried point attribution parameter value corresponding to a preset event based on an occurrence sequence of the preset event in the application client; a target buried point attribution parameter value determining module 2040, configured to determine, according to the type of a target buried point attribution parameter associated with a buried point object exposed by a buried point reporting event, a value of the target buried point attribution parameter from the first preset storage container; and a buried point information reporting module 2050, configured to report, based on the value of the target buried point attribution parameter, buried point information of the buried point object exposed by the target buried point reporting event.
In an optional embodiment, the preset event includes one or more of a triggered event, a page exposure event and an automatic triggering event of an element in the page; wherein, in a case that the preset event comprises a page exposure event, the page exposure event comprises 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.
In an alternative embodiment, the preset event response module 2010 may be specifically configured to: under the condition that the preset event comprises an element triggered event in the page, in response to the occurrence of the element triggered event in the page in the application client, determining a buried point object associated with the preset event according to the triggered element; under the condition that the preset event comprises the first page exposure event, responding to the first page exposure event in an application program client, and determining a buried point object associated with the preset event according to a root page of a page which finishes exposure; under the condition that the preset event comprises the second page exposure event, responding to the second page exposure event occurring in the application program client, and determining a buried point object associated with the preset event according to a buried point object associated with the second page exposure event in advance; and under the condition that the preset event comprises the automatic triggering event, responding to the automatic triggering event in the application program client, and determining a buried point object associated with the preset event according to the buried point object associated with the automatic triggering event in advance.
In an alternative embodiment, based on the foregoing embodiment, the to-be-reported buried point attribution parameter value generating module 2020 may be specifically configured to: generating an attribution parameter value of a buried point to be reported corresponding to the preset event according to the type of the preset event, the occurrence sequence of the preset event in the exposure period of the page where the preset event is located, the page exposure sequence 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; after the application client is started, each time page exposure occurs, the value of the page exposure sequence is increased by a unit numerical value, and the value of the page exposure sequence restarts counting along with the restart of the application client.
In an alternative embodiment, based on the foregoing embodiment, the to-be-reported buried point attribution parameter value generating module 2020 may also be configured to: and generating an attribution parameter value of the buried point to be reported corresponding to the preset event according to the session identifier when the application program client is started for the last time, 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.
In an optional implementation manner, based on the foregoing implementation manner, the content information of the buried point object associated with the preset event includes a target object identifier, where the target object identifier includes a buried point object identifier of a root page of a page that can be exposed after the buried point object is triggered, in the buried point attribution parameter value generation module 2020 to be reported.
In an alternative embodiment, based on the foregoing embodiments, the target buried point attribution parameter value determining module 2040 may be specifically configured to: matching the buried point object identifier of the exposed buried point object with a target object identifier in attribution parameter values of each buried point to be reported stored in a first preset storage container; and determining the value of the attribution parameters of the target buried point according to the matching result.
In an optional implementation manner, determining a value of the target buried point attribution parameter according to the matching result includes: when the matching is successful, determining the attribution parameter value of the target buried point by the following method: determining a first buried point attribution parameter value to be reported according to the buried point attribution parameter value to be reported containing the successfully matched target object identifier; determining a second buried point attribution parameter value to be reported from the first preset storage container, wherein the second buried point attribution parameter value to be reported comprises a buried point attribution parameter value to be reported corresponding to the latest page exposure event stored in the first preset storage container; determining the value of the target buried point attribution parameter according to the larger generation time of the first buried point attribution parameter value to be reported and the second buried point attribution parameter value to be reported; when the matching fails, determining the value of the attribution parameter of the target buried point by the following method: and determining the value of the target buried point attribution parameter according to the buried point attribution parameter value to be reported which is added in the first preset storage container for the last time.
In an optional implementation manner, based on the foregoing implementation manner, in a case that 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 the attribution parameter values of the buried points to be reported stored in the first preset storage container, wherein the matching comprises the following steps: when a new page is exposed in the application program client, matching the embedded object identifier of the exposed new page with the target object identifier in the attribution parameter values of the embedded points to be reported stored in the first preset storage container; according to the matching result, determining the value of the target buried point attribution parameter, comprising the following steps: determining the value of the attribution parameter of the first type of target buried point according to the matching result; the first type of target buried point attribution parameter is used for representing an exposure source of a root page of a page exposed by a buried point reporting event, and the first type of target buried point attribution parameter is updated when new page exposure occurs.
In an optional implementation manner, based on the foregoing implementation manner, in a case that the buried point reporting event includes a page exposure event, the target buried point attribution parameter includes a second type; matching the exposed buried point object identifier of the buried point object with a target object identifier in attribution parameter values of each to-be-reported buried point stored in the first preset storage container, wherein the matching comprises the following steps: under the condition that a page exposed in an application program client is a newly created page, matching a buried object identifier of the exposed page with a target object identifier in attribution parameter values of all points to be reported, which are stored in a first preset storage container; according to the matching result, determining the value of the target buried point attribution parameter, comprising the following steps: determining the value of the attribution parameter of the second type of target buried point according to the matching result; the second type of target buried point attribution parameter is used for representing a creation source of a root page of a page exposed by a buried point reporting event, and the second type of target buried point attribution parameter is updated when a new page is created.
In an optional implementation manner, based on the foregoing implementation manner, in a case that the buried point reporting event includes a page exposure event, and the type of the target buried point attribution parameter includes a third type and the first type, the determining manner of the value of the target buried point attribution parameter of the third type includes: responding to the root page exposure in the application program client based on the page exposure sequence in the application program client, and adding the value of the first type target buried point attribution parameter corresponding to the newly exposed root page into a second preset storage container; when the number of the values of the first type of target buried point attribution parameter stored in the second preset storage container is larger than a first preset value, deleting the value of the first type of target buried point attribution parameter with the earliest adding time in the second preset storage container from the second preset storage container; and determining the value of the attribution parameter of the third type of target buried point according to the second preset storage container.
In an optional implementation manner, based on the foregoing implementation manner, in a case that the buried point reporting event includes a page exposure event, and the type of the target buried point attribution parameter includes a fourth type and the second type, the determining manner of the value of the target buried point attribution parameter of the fourth type includes: responding to the root page exposure in the application program client based on the page exposure sequence in the application program client, and adding the value of the second type target buried point attribution parameter corresponding to the newly exposed root page into a third preset storage container; when the number of the values of the second type of target buried point attribution parameters stored in the third preset storage container is larger than a second preset value, deleting the value of the second type of target buried point attribution parameter with the earliest adding time in the third preset storage container from the third preset storage container; and determining the value of the attribution parameter of the fourth type of target buried point according to the third preset storage container.
In an optional implementation manner, based on the foregoing implementation manner, in a case that the types of the target buried point attribution parameter include a fifth type and the second type, the determining manner of the value of the target buried point attribution parameter of the fifth type includes: matching the buried point object identification of the buried point object exposed by the buried point reporting event with a preset buried point object identification; 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 second type of buried point attribution parameter corresponding to the buried point object indicated by the preset buried point object identifier which is successfully matched; the preset buried object identifier comprises a buried object identifier corresponding to a root page of a home page of the application client.
In an optional implementation manner, based on the foregoing implementation manner, when matching between the buried object identifier of the buried object exposed by the buried point reporting event and the preset buried object identifier fails, a determination manner of the value of the target buried point attribution parameter of the fifth type includes: acquiring a buried point object identifier corresponding to a root page of a page where a buried point object exposed by the buried point reporting event is located; matching the buried point object identifier corresponding to the root page with a target object identifier in the buried point attribution parameter values to be reported stored in the first preset storage container to determine target attribution parameter values to be reported; and matching the buried point object identifier contained in the attribution parameter value to be reported of the target with the preset buried point object identifier, and determining the value of the attribution parameter of the target of the fifth type according to the matching result.
In an optional implementation manner, based on the foregoing implementation manner, the matching the buried object identifier corresponding to the root page with a target object identifier in the to-be-reported buried-point attribution parameter value 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 attribution parameter value of the target buried point to be reported according to the attribution parameter value of the buried point to be reported successfully matched; and when the matching fails, determining the attribution parameter value of the target buried point to be reported according to the attribution parameter value of the buried point to be reported which is added to the first preset storage container for the last time.
In an optional implementation manner, based on the foregoing implementation manner, the 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 fifth type target buried point attribution parameter according to a matching result includes:
when the matching is successful, updating the value of the attribution parameter of the target buried point of the fifth type according to the value of the attribution parameter of the buried point of the second type corresponding to the buried point object indicated by the preset buried point object identifier which is successfully matched; when the matching fails, the values of the fifth type of target buried point attribution parameters are not updated.
In an optional implementation manner, based on the foregoing implementation manner, in a case that the buried point reporting event includes an add list unit to playlist event, the type of the target buried point attribution parameter includes a sixth type; the matching of the exposed buried point object identifier of the buried point object with the target object identifier in the attribution parameter values of the buried points to be reported stored in the first preset storage container includes: responding to an event that the application program client adds a list unit to the playlist, and matching a buried object identifier corresponding to a buried object exposed by the event that the list unit is added to the playlist with a target object identifier included in a buried point attribution parameter value to be reported, which is stored in the first preset storage container; and according to the matching result, determining the value of the target buried point attribution parameter, comprising the following steps: determining the value of the attribution parameter of the target buried point of the sixth type according to the matching result; wherein the sixth type of target buried point attribution parameter is used for characterizing a reason why a list unit is added to the playlist.
In an optional implementation manner, based on the foregoing implementation manner, in a case that the buried point reporting event includes a playlist unit played event of a playlist, the type of the target buried point attribution parameter includes a seventh type; the matching of the exposed buried point object identifier of the buried point object with the target object identifier in the attribution parameter values of the buried points to be reported stored in the first preset storage container includes: responding to a played event of a list unit in a play list of the application program client, and matching a buried object identifier of a buried object exposed by the played event of the list unit with a target object identifier included in an attribution parameter value of a buried point to be reported stored in the first preset storage container; according to the matching result, determining the value of the target buried point attribution parameter, comprising the following steps: determining the value of the attribution parameters of the seventh type of target buried points according to the matching result; wherein the seventh type of target buried point attribution parameter is used for characterizing a reason why a list unit in the play list is played.
In an alternative embodiment, based on the foregoing embodiment, the adding module 2030 may be specifically configured to: adding the attribution parameter values of the buried points to be reported corresponding to the preset events into the first preset storage container based on the occurrence sequence of the preset events except the preset events to be deleted in the application program client; and the preset event to be deleted is determined according to a preset page exposed in the application program client and/or a triggered preset element.
In an optional implementation manner, based on the foregoing implementation manner, the device for reporting buried point information 2100 may further include a module for generating a buried point attribution parameter value to be reported at a non-buried point position, where the module may be specifically configured to: when a preset event occurs in an application program client, if the preset event does not have a related buried point object, determining a root page where an element corresponding to the preset event is located according to a buried point attribution parameter value to be reported and a preset identification field corresponding to the root page, and determining a buried point attribution parameter value to be reported corresponding to the preset event; the preset identification field is used for identifying the buried point attribution parameter value to be reported as the buried point attribution parameter value to be reported generated after the position of the buried point object in the application program client is triggered.
In an optional implementation manner, based on the foregoing implementation manner, the buried point information reporting module 2050 may be specifically configured to: and taking the value of the attribution parameter of the target buried point 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.
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 are not described herein again.
Exemplary storage Medium
The storage medium of the exemplary embodiment of the present disclosure is explained below.
In the present exemplary embodiment, any of the methods described above may be implemented by a program product, such as a portable compact disc read only memory (CD-ROM) and including program code, and may be executed on a device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having 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 foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RE, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user computing device, partly on a remote computing device, or entirely on the remote computing device or server. In situations involving remote computing devices, the remote computing devices may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to external computing devices (e.g., through the internet using an internet service provider).
Exemplary electronic device
An electronic device of an exemplary embodiment of the present disclosure is explained with reference to fig. 21. The electronic device may be a client or a server.
The electronic device 2100 illustrated in fig. 21 is merely an example and should not impose any limitations on the functionality or scope of use of embodiments of the disclosure.
As shown in fig. 21, the electronic device 2100 is 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 memory unit 2120, a bus 2130 connecting the various system components including the memory unit 2120 and the processing unit 2110, a display unit 2140. Wherein the storage unit stores program code, which may be executed by the processing unit 2110 for causing the processing unit 2110 to perform the steps according to various exemplary embodiments of the present disclosure as described in the above-mentioned "exemplary methods" section of this specification. For example, the processing unit 2110 may perform the method steps as shown in fig. 1, 5-10, 12-18, etc.
The memory unit 2120 may include volatile memory units such as a random access memory unit (RAM) 1321 and/or a cache memory unit 2122, and may further include a read-only memory unit (ROM) 2123.
The storage unit 2120 may also include a program/utility 2124 having a set (at least one) of program modules 2125, such program modules 2125 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination thereof may comprise an implementation of a network environment.
Bus 2130 may include a data bus, an address bus, and a control bus.
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., which may be via an input/output (I/O) interface 1350. The electronic device 2100 also includes a display unit 2140 connected to the input/output (I/O) interface 2150 for display. Also, the electronic device 2100 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the internet) via the network adapter 2160. As shown, 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 figures, 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, among others.
It should be noted that although in the above detailed description several modules or sub-modules of the apparatus are mentioned, such division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the units/modules described above may be embodied in one unit/module, in accordance with embodiments of the present disclosure. Conversely, the features and functions of one unit/module described above may be further divided into embodiments by a plurality of units/modules.
Further, while the operations of the disclosed methods are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
While the spirit and principles of the present disclosure have been described with reference to several particular embodiments, it is to be understood that the present disclosure is not limited to the particular embodiments disclosed, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims (10)

1. A method for reporting embedded point information is characterized by comprising the following steps:
responding to a preset event in an application program client, and determining a buried point object associated with the preset event;
generating an attribution parameter value of the buried point to be reported corresponding to the preset event according to the pit position information and the content information of the buried point object associated with the preset event;
adding the attribution parameter values of the buried points to be reported corresponding to the preset events in a first preset storage container based on the occurrence sequence of the preset events in the application program 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 the embedded point information of the embedded point object exposed by the embedded point reporting event based on the value of the target embedded point attribution parameter.
2. A reporting method of buried point information according to claim 1, wherein the preset event includes one or more of a triggered event, a page exposure event and an automatic trigger event of an element in a page;
wherein, in a case that the preset event comprises a page exposure event, the page exposure event comprises 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.
3. The method of claim 2, wherein the determining the buried point object associated with the preset event in response to the preset event occurring in the application client comprises:
under the condition that the preset event comprises an element triggered event in the page, in response to the occurrence of the element triggered event in the page in the application client, determining a buried point object associated with the preset event according to the triggered element;
under the condition that the preset event comprises the first page exposure event, responding to the first page exposure event in an application program client, and determining a buried point object associated with the preset event according to a root page of a page which finishes exposure;
under the condition that the preset event comprises the second page exposure event, responding to the second page exposure event occurring in the application program client, and determining a buried point object associated with the preset event according to a buried point object associated with the second page exposure event in advance;
and under the condition that the preset event comprises the automatic triggering event, responding to the automatic triggering event in the application program client, and determining a buried point object associated with the preset event according to the buried point object associated with the automatic triggering event in advance.
4. A buried point information reporting method according to claim 1, wherein the generating of the to-be-reported buried point attribution parameter value corresponding to the preset event according to the pit position information and the content information of the buried point object associated with the preset event includes:
generating an attribution parameter value of a buried point to be reported corresponding to the preset event according to the type of the preset event, the occurrence sequence of the preset event in the exposure period of the page where the preset event is located, the page exposure sequence 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;
after the application client is started, each time page exposure occurs, the value of the page exposure sequence is increased by a unit numerical value, and the value of the page exposure sequence restarts counting along with the restart of the application client.
5. A buried point information reporting method according to claim 1, wherein the generating of the buried point attribution parameter value to be reported corresponding to the preset event according to the pit bit information and the content information of the buried point object associated with the preset event includes:
and generating an attribution parameter value of the buried point to be reported corresponding to the preset event according to the session identifier when the application program client is started for the last time, 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. A method as claimed in claim 1, wherein the content information of the embedded point object associated with the preset event includes a target object id, and the target object id includes an embedded point object id of a root page of a page that can be exposed after the embedded point object is triggered.
7. The method as claimed in claim 6, wherein 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 a target object identifier in attribution parameter values of each buried point to be reported stored in the first preset storage container;
and determining the value of the attribution parameters of the target buried point according to the matching result.
8. A device for reporting buried point information is characterized by comprising:
the system comprises a preset event response module, a preset event processing module and a preset event processing module, wherein the preset event response module is configured to respond to the occurrence of a preset event in an application program client and determine a buried point object associated with the preset event;
a to-be-reported buried point attribution parameter value generating module configured to generate a to-be-reported buried point attribution parameter value corresponding to the preset event according to the pit bit information and the content information of the buried point object associated with the preset event;
the adding module is configured to add the buried point attribution parameter values to be reported corresponding to the preset events in a first preset storage container based on the occurrence sequence of the preset events in the application program 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 the buried point information reporting module is configured to report the buried point information of the buried point object exposed by the target buried point reporting event based on the value of the target buried point attribution parameter.
9. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
10. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out the method of any one of claims 1 to 7.
CN202211167977.3A 2022-09-23 2022-09-23 Method and device for reporting embedded point information, medium and electronic equipment Pending CN115576772A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211167977.3A CN115576772A (en) 2022-09-23 2022-09-23 Method and device for reporting embedded point information, medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211167977.3A CN115576772A (en) 2022-09-23 2022-09-23 Method and device for reporting embedded point information, medium and electronic equipment

Publications (1)

Publication Number Publication Date
CN115576772A true CN115576772A (en) 2023-01-06

Family

ID=84580872

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211167977.3A Pending CN115576772A (en) 2022-09-23 2022-09-23 Method and device for reporting embedded point information, medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN115576772A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116668506A (en) * 2023-07-26 2023-08-29 北京搜狐互联网信息服务有限公司 Feed exposure reporting and recording method, server, equipment and medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116668506A (en) * 2023-07-26 2023-08-29 北京搜狐互联网信息服务有限公司 Feed exposure reporting and recording method, server, equipment and medium
CN116668506B (en) * 2023-07-26 2023-10-03 北京搜狐互联网信息服务有限公司 Feed exposure reporting and recording method, server, equipment and medium

Similar Documents

Publication Publication Date Title
US20190163594A1 (en) Using Cognitive Technologies to Identify and Resolve Issues in a Distributed Infrastructure
WO2018133864A1 (en) Page display method, device, terminal, server, and data storage medium
CN109275047B (en) Video information processing method and device, electronic equipment and storage medium
US8639559B2 (en) Brand analysis using interactions with search result items
KR101748833B1 (en) Software failure locating method, apparatus and equipment
US9535978B2 (en) Semantic mapping of topic map meta-models identifying assets and events to include weights
CN111798833A (en) Voice test method, device, equipment and storage medium
CN112987996B (en) Information display method, information display device, electronic equipment and computer readable storage medium
CN113946547B (en) Method and device for ferrying network disk file, network disk and storage medium
CN115328742B (en) Container information monitoring method and device, storage medium and electronic equipment
CN115576772A (en) Method and device for reporting embedded point information, medium and electronic equipment
CN110941554B (en) Method and device for reproducing faults
CN113485909B (en) Test method, test device, computing equipment and medium
RU2654789C2 (en) Method (options) and electronic device (options) for processing the user verbal request
CN113138934B (en) Automatic test method, medium, device and computing equipment
JP6162134B2 (en) Social page trigger
KR101336846B1 (en) Contents Search Service Providing Method, Search Server and Search System Including that
US10853430B1 (en) Automated agent search engine
CN115129922A (en) Search term generation method, model training method, medium, device and equipment
US8140318B2 (en) Method and system for generating application simulations
US10558697B2 (en) Segmenting a set of media data using a set of social networking data
CN112989102A (en) Audio playing control method and device, storage medium and terminal equipment
CN110515803B (en) Processing method and device for log message and electronic equipment
CN113392625A (en) Method and device for determining label information, electronic equipment and storage medium
CN112650839A (en) Retrieval information optimization method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination