Point burying event attribute reporting method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a point burying event attribute reporting method and device, electronic equipment and a storage medium. The method comprises the steps that multiple point burying events of a target application program of a target version and multiple point burying event reporting attributes needing to be reported by the point burying events are determined; determining a repeated buried point event reporting attribute reported by at least two buried point events and a non-repeated buried point event reporting attribute reported by at most one buried point event; and uniformly reporting the repeated point burying event reporting attributes, and when a target point burying event is triggered, reporting non-repeated point burying event reporting attributes reported by the target point burying event. Through the embodiment of the invention, the reporting opportunities of different data can be reasonably set from the global perspective through the distributed buried point event design, so that the data reporting efficiency is improved, the problem of repeated reporting is solved, and the code quantity is effectively reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular to a method for reporting attributes of a buried event, a device for reporting attributes of a buried event, an electronic device and a computer-readable storage medium. Background Art

[0002] Currently, APP (Application) tracking mainly uses tracking events as units. The design of data tracking is achieved by defining the triggering and reporting mechanism, reporting content, and reporting standardization of tracking events.

[0003] However, in this process, there will inevitably be duplication of reporting content for different tracking events. For example, both event A and event B need to report user ID (Identifier), device MAC (Media Access Control) and other information; this will lead to code redundancy and low reporting efficiency. Summary of the invention

[0004] In view of the above problems, a method for reporting attributes of a buried event, a device for reporting attributes of a buried event, an electronic device and a computer-readable storage medium are proposed to overcome the above problems or at least partially solve the above problems, including:

[0005] A method for reporting attributes of a buried event, the method comprising:

[0006] Determine multiple tracking events of the target application of the target version, and multiple tracking event reporting attributes that need to be reported for each tracking event;

[0007] Determine the reporting attributes of duplicate tracking events reported by at least two tracking events, and the reporting attributes of non-duplicate tracking events reported by at most one tracking event;

[0008] The reporting attributes of the repeated burying point events are reported uniformly, and when a target burying point event is triggered, the reporting attributes of the non-duplicate burying point event reported by the target burying point event are reported.

[0009] Optionally, the repeated burying point event reporting attribute includes a globally applicable first repeated burying point event reporting attribute; the unified reporting of the repeated burying point event reporting attribute includes:

[0010] When the target application of the target version is started, the first duplicate burying event reporting attribute is reported.

[0011] Optionally, the repeated burying point event reporting attribute includes a globally applicable first repeated burying point event reporting attribute; the unified reporting of the repeated burying point event reporting attribute includes:

[0012] When the target application of the target version starts to enter the foreground running state from the background pause state, the first repeated burying event reporting attribute is reported.

[0013] Optionally, the first repeated tracking event reporting attribute includes at least one of the following:

[0014] Application version information, operating system information, terminal information, account information.

[0015] Optionally, the method further comprises:

[0016] When the target application of the target version is started, the first repeated burying event reporting attributes are uniformly collected.

[0017] Optionally, the repeated burying point event reporting attribute includes a second repeated burying point event reporting attribute common to burying point events of the same type, and the unified reporting of the repeated burying point event reporting attribute includes:

[0018] The preset tracking point software development toolkit reports the second repeated tracking point event reporting attribute.

[0019] Optionally, the method further comprises:

[0020] The preset tracking point software development toolkit collects the second repeated tracking point event reporting attributes.

[0021] Optionally, the repeated burying point event reporting attribute includes a third repeated burying point event reporting attribute common to related burying point events of a target analysis subject, and the unified reporting of the repeated burying point event reporting attribute includes:

[0022] The third repeated embedding event reporting attribute is reported by the main event of the target analysis topic.

[0023] Optionally, the method further comprises:

[0024] The third repeated embedding event reporting attributes are collected by the main event of the target analysis topic.

[0025] The embodiment of the present invention further provides a device for reporting attributes of a buried event, the device comprising:

[0026] A first determination module is used to determine multiple tracking events of a target application of a target version, and multiple tracking event reporting attributes that need to be reported for each tracking event;

[0027] A second determination module is used to determine the reporting attributes of duplicate burying point events reported by at least two burying point events, and the reporting attributes of non-duplicate burying point events reported by at most one burying point event;

[0028] The reporting module is used to uniformly report the reporting attributes of the repeated burying point events, and when a target burying point event is triggered, report the reporting attributes of the non-duplicate burying point event reported by the target burying point event.

[0029] Optionally, the duplicate burial point event reporting attribute includes a globally applicable first duplicate burial point event reporting attribute; the reporting module is used to report the first duplicate burial point event reporting attribute when the target application of the target version is started.

[0030] Optionally, the repeated burial event reporting attribute includes a globally applicable first repeated burial event reporting attribute; the reporting module is used to report the first repeated burial event reporting attribute when the target application of the target version starts to enter the foreground running state from the background pause state.

[0031] Optionally, the first repeated tracking event reporting attribute includes at least one of the following:

[0032] Application version information, operating system information, terminal information, account information.

[0033] Optionally, the reporting module is further used to uniformly collect the first repeated burial event reporting attributes when the target application of the target version is started.

[0034] Optionally, the repeated burying point event reporting attribute includes a second repeated burying point event reporting attribute common to the same type of burying point events, and the reporting module is used to report the second repeated burying point event reporting attribute by a preset burying point software development toolkit.

[0035] Optionally, the reporting module is also used to collect the second repeated burying point event reporting attributes by the preset burying point software development toolkit.

[0036] Optionally, the repeated burial point event reporting attributes include a third repeated burial point event reporting attribute that is common to relevant burial point events of a target analysis subject, and the reporting module is used to report the third repeated burial point event reporting attribute by the main event of the target analysis subject.

[0037] Optionally, the reporting module is also used to collect the reporting attributes of the third repeated embedding event from the main event of the target analysis topic.

[0038] An embodiment of the present invention also provides an electronic device, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor, and when the computer program is executed by the processor, the method for reporting the attributes of the buried event as described above is implemented.

[0039] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method for reporting attributes of a buried event as described above is implemented.

[0040] The embodiments of the present invention have the following advantages:

[0041] In an embodiment of the present invention, multiple burying point events of a target application of a target version and multiple burying point event reporting attributes that need to be reported by each burying point event are determined; duplicate burying point event reporting attributes reported by at least two burying point events and non-duplicate burying point event reporting attributes reported by at most one burying point event are determined; duplicate burying point event reporting attributes are uniformly reported, and when a target burying point event is triggered, the non-duplicate burying point event reporting attributes reported by the target burying point event are reported. Through an embodiment of the present invention, the reporting timing of different data can be reasonably set from a global perspective through a distributed burying point event design to improve the efficiency of data reporting, solve the problem of duplicate reporting, and effectively reduce the amount of code. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solution of the present invention, the accompanying drawings required for use in the description of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0043] Figure 1 This is a flowchart of a method for reporting attributes of a buried event according to an embodiment of the present invention;

[0044] Figure 2 This is a flowchart of another method for reporting attributes of a buried event according to an embodiment of the present invention;

[0045] Figure 3 This is a flowchart of another method for reporting attributes of a buried event according to an embodiment of the present invention;

[0046] Figure 4 This is a flowchart of another method for reporting attributes of a buried event according to an embodiment of the present invention;

[0047] Figure 5 This is a flowchart of another method for reporting attributes of a buried event according to an embodiment of the present invention;

[0048] Figure 6 This is a flow chart of the steps of reporting attributes in an embodiment of the present invention;

[0049] Figure 7It is a structural diagram of an attribute reporting device for a buried event according to an embodiment of the present invention. DETAILED DESCRIPTION

[0050] In order to make the above-mentioned purposes, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0051] In order to improve the overall operating efficiency, the embodiments of the present invention can use distributed event tracking design to reasonably set the reporting timing of different data from a global perspective, so as to improve the efficiency of data reporting, solve the problem of duplicate reporting, and effectively reduce the amount of code.

[0052] For details, please refer to Figure 1 , shows a flowchart of a method for reporting attributes of a buried event according to an embodiment of the present invention, which may include the following steps:

[0053] Step 101: Determine a plurality of tracking point events of a target application of a target version, and a plurality of tracking point event reporting attributes that need to be reported for each tracking point event.

[0054] The current version of the target application can be the target version; for the target application of the target version, its APP tracking is mainly based on tracking events as units, and the design of data tracking is realized by defining the trigger reporting mechanism, reporting content, and reporting standardization of tracking events. In actual applications, multiple tracking events of the target application can be pre-entered into the tracking system background.

[0055] In some feasible embodiments, each tracking event of the target application of the target version may involve multiple tracking event reporting attributes, that is, the content that needs to be reported by the tracking event, such as: tracking event trigger time, user ID, APP version, etc.

[0056] In actual applications, multiple tracking event reporting attributes corresponding to multiple tracking events of the target application can also be entered into the tracking system backend.

[0057] In each version, taking the current target version as an example, you can first determine multiple tracking events of the target application of the target version, as well as multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version.

[0058] Exemplarily, the target application of the target version is set to T1, T2, T3, ..., T 10There are 10 tracking events in total, including A1, A2, A3, ..., A 30 There are 30 event reporting attributes that need to be reported. Duplicate event reporting attributes can exist. For example: A1 and A 30 The same burial point event reporting attributes are present; of course, there may be no repeated burial point event reporting attributes, and this is not limited in the embodiments of the present invention.

[0059] Step 102: Determine the reporting attributes of repeated burying point events reported by at least two burying point events, and the reporting attributes of non-duplicate burying point events reported by at most one burying point event.

[0060] Each tracking event can correspond to at least one tracking event reporting attribute, and different tracking events may contain the same tracking event reporting attribute. If each tracking event reports the same tracking event reporting attribute once, there will be a problem of repeated reporting; and the code corresponding to the repeatedly reported tracking event reporting attribute needs to be included for each tracking event, which will lead to the problem of duplicate code.

[0061] To address these issues, an embodiment of the present invention can determine the multiple tracking events of the target application of the target version, and the multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version, and then determine the tracking event reporting attributes that are repeatedly reported.

[0062] For example, if a burying point event reporting attribute that needs to be reported in a burying point event is the same as a burying point event reporting attribute that needs to be reported in another burying point event, it can be determined that the burying point event reporting attribute is a duplicate burying point event reporting attribute.

[0063] In actual applications, the tracking system backend can automatically compare the reporting attributes of duplicate tracking events in multiple tracking events corresponding to the target application of the target version.

[0064] In addition, non-repeating point event reporting attributes can be used as non-repeating point event reporting attributes; at most only one point event is reported for these non-repeating point event reporting attributes.

[0065] Step 103: uniformly report the reporting attributes of repeated burying point events, and when a target burying point event is triggered, report the reporting attributes of non-duplicate burying point events reported by the target burying point event.

[0066] After determining the reporting attributes of duplicate and non-duplicate event tracking events, you can define the duplicate event tracking attributes to be reported only once. That is, although there are multiple tracking events that need to report the duplicate event tracking attributes, the duplicate event tracking attributes are designed to be reported only once, so as to avoid the problem of duplicate reporting; and there is no need to design relevant code for each tracking event, thereby reducing the amount of code for the target application.

[0067] In addition, for the non-repetitive burial point event reporting attributes, the original reporting strategy can continue to be used by default; specifically, for the non-repetitive burial point event reporting attributes, when its related target burial point event is triggered, the non-repetitive burial point event reporting attributes can be triggered by the target burial point event, and the embodiments of the present invention do not limit this.

[0068] In an embodiment of the present invention, multiple burying point events of a target application of a target version and multiple burying point event reporting attributes that need to be reported by each burying point event are determined; duplicate burying point event reporting attributes reported by at least two burying point events and non-duplicate burying point event reporting attributes reported by at most one burying point event are determined; duplicate burying point event reporting attributes are uniformly reported, and when a target burying point event is triggered, the non-duplicate burying point event reporting attributes reported by the target burying point event are reported. Through an embodiment of the present invention, the reporting timing of different data can be reasonably set from a global perspective through a distributed burying point event design to improve the efficiency of data reporting, solve the problem of duplicate reporting, and effectively reduce the amount of code.

[0069] Reference Figure 2 , shows a flowchart of another method for reporting attributes of a buried event according to an embodiment of the present invention, which may include the following steps:

[0070] Step 201: Determine multiple tracking events of a target application of a target version, and multiple tracking event reporting attributes that need to be reported for each tracking event.

[0071] In actual applications, multiple tracking events of the target application of the target version can be pre-entered into the tracking system background. Each tracking event of the target application of the target version may involve multiple tracking event reporting attributes, that is, the content that the tracking event needs to report.

[0072] In addition, multiple tracking event reporting attributes corresponding to multiple tracking events of the target application can also be entered into the tracking system backend.

[0073] In each version, taking the current target version as an example, you can first determine multiple tracking events of the target application of the target version, as well as multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version.

[0074] Step 202: Determine the reporting attributes of repeated burying point events reported by at least two burying point events, and the reporting attributes of non-duplicate burying point events reported by at most one burying point event.

[0075] Each tracking event can correspond to at least one tracking event reporting attribute, and different tracking events may contain the same tracking event reporting attribute. If each tracking event reports the same tracking event reporting attribute once, there will be a problem of repeated reporting; and the code corresponding to the repeatedly reported tracking event reporting attribute needs to be included for each tracking event, which will lead to the problem of duplicate code.

[0076] To this end, after determining multiple tracking events of the target application of the target version and multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version, the tracking event reporting attributes that are repeatedly reported can be determined.

[0077] Specifically, if a burying event reporting attribute that needs to be reported in a burying event is the same as a burying event reporting attribute that needs to be reported in another burying event, it can be determined that the burying event reporting attribute is a duplicate burying event reporting attribute.

[0078] In actual applications, the tracking system backend can automatically compare the reporting attributes of duplicate tracking events in multiple tracking events corresponding to the target application of the target version.

[0079] In addition, non-repeating point event reporting attributes can be used as non-repeating point event reporting attributes; at most only one point event is reported for these non-repeating point event reporting attributes.

[0080] Step 203: The duplicate burying point event reporting attribute includes a globally applicable first duplicate burying point event reporting attribute; when the target application of the target version is started, the first duplicate burying point event reporting attribute is reported.

[0081] In some feasible embodiments, the repeated burial point event reporting attributes may include a globally applicable first repeated burial point event reporting attribute; that is, a globally applicable burial point event reporting attribute that most or even all burial point events need to be reported.

[0082] In one embodiment of the present invention, the first repeated tracking event reporting attribute includes at least one of the following:

[0083] Application version information, operating system information, terminal information, account information.

[0084] Among them, application version information may refer to the version number of the target application, and the application version information may be used to identify the current version of the application; operating system information may refer to the version and type of the operating system running on the user's device; terminal information may refer to detailed information of the device used by the user, including device brand, device model, screen size, resolution, etc.; account information may refer to the user's identity and related information in the target application, and the embodiments of the present invention do not limit this.

[0085] In some feasible embodiments, for the globally common first duplicate burial point event reporting attribute, the first duplicate burial point event reporting attribute can be uniformly reported through a preset initialization event when the target application of the target version is triggered to start by the user.

[0086] Step 204: When a target burying point event is triggered, report the non-duplicate burying point event reporting attributes reported by the target burying point event.

[0087] In some feasible embodiments, for non-repetitive burial point event reporting attributes, the original reporting strategy can continue to be used by default; specifically, for non-repetitive burial point event reporting attributes, when its related target burial point event is triggered, the non-repetitive burial point event reporting attributes can be triggered by the target burial point event, and the embodiments of the present invention do not limit this.

[0088] In an embodiment of the present invention, the above method may further include the following steps:

[0089] When the target application of the target version is started, the reporting attributes of the first repeated tracking event are collected uniformly.

[0090] In some feasible embodiments, a preset initialization event can uniformly collect the reporting attributes of each first repeated burial event when the target application of the target version is started; after the collection is completed, the preset initialization event can uniformly report the collected reporting attributes of each first repeated burial event, and the embodiments of the present invention are not limited to this.

[0091] In an embodiment of the present invention, multiple burying point events of a target application of a target version and multiple burying point event reporting attributes that need to be reported by each burying point event are determined; duplicate burying point event reporting attributes reported by at least two burying point events and non-duplicate burying point event reporting attributes reported by at most one burying point event are determined; duplicate burying point event reporting attributes include a globally applicable first duplicate burying point event reporting attribute; when the target application of the target version is started, the first duplicate burying point event reporting attribute is reported; when the first target burying point event is triggered, the non-duplicate burying point event reporting attribute reported by the target burying point event is reported. Through the embodiment of the present invention, the reporting timing of different data can be reasonably set from a global perspective through a distributed burying point event design to improve the efficiency of data reporting, solve the problem of duplicate reporting, and effectively reduce the amount of code.

[0092] Reference Figure 3 , shows a flowchart of another method for reporting attributes of a buried event according to an embodiment of the present invention, which may include the following steps:

[0093] Step 301: Determine multiple tracking events of a target application of a target version, and multiple tracking event reporting attributes that need to be reported for each tracking event.

[0094] In actual applications, multiple tracking events of the target application of the target version can be pre-entered into the tracking system background. Each tracking event of the target application of the target version may involve multiple tracking event reporting attributes, that is, the content that the tracking event needs to report.

[0095] In addition, multiple tracking event reporting attributes corresponding to multiple tracking events of the target application can also be entered into the tracking system backend.

[0096] In each version, taking the current target version as an example, you can first determine multiple tracking events of the target application of the target version, as well as multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version.

[0097] Step 302: Determine the reporting attributes of repeated burying point events reported by at least two burying point events, and the reporting attributes of non-duplicate burying point events reported by at most one burying point event.

[0098] Each tracking event can correspond to at least one tracking event reporting attribute, and different tracking events may contain the same tracking event reporting attribute. If each tracking event reports the same tracking event reporting attribute once, there will be a problem of repeated reporting; and the code corresponding to the repeatedly reported tracking event reporting attribute needs to be included for each tracking event, which will lead to the problem of duplicate code.

[0099] To this end, after determining multiple tracking events of the target application of the target version and multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version, the tracking event reporting attributes that are repeatedly reported can be determined.

[0100] Specifically, if a burying event reporting attribute that needs to be reported in a burying event is the same as a burying event reporting attribute that needs to be reported in another burying event, it can be determined that the burying event reporting attribute is a duplicate burying event reporting attribute.

[0101] In actual applications, the tracking system backend can automatically compare the reporting attributes of duplicate tracking events in multiple tracking events corresponding to the target application of the target version.

[0102] In addition, non-repeating point event reporting attributes can be used as non-repeating point event reporting attributes; at most only one point event is reported for these non-repeating point event reporting attributes.

[0103] Step 303, the repeated burying point event reporting attribute includes a globally applicable first repeated burying point event reporting attribute; when the target application of the target version starts to enter the foreground running state from the background pause state, the first repeated burying point event reporting attribute is reported.

[0104] In some feasible embodiments, the repeated burial point event reporting attributes may include a globally applicable first repeated burial point event reporting attribute; that is, a globally applicable burial point event reporting attribute that most or even all burial point events need to be reported.

[0105] For the globally common first repeated tracking event reporting attribute, the first repeated tracking event reporting attribute can be uniformly reported through a preset initialization event when the target application of the target version enters the foreground running state from the background pause state.

[0106] The background pause state may refer to the target application of the target version being in a suspended state; and entering the foreground running state from the background pause state may refer to the target application of the target version re-entering after being suspended. Specifically, when the target application of the target version re-enters after being suspended, the first repeated tracking event reporting attribute may be uniformly reported through a preset initialization event.

[0107] Step 304: When a target burying point event is triggered, report the non-duplicate burying point event reporting attributes reported by the target burying point event.

[0108] In some feasible embodiments, for non-repetitive burial point event reporting attributes, the original reporting strategy can continue to be used by default; specifically, for non-repetitive burial point event reporting attributes, when its related target burial point event is triggered, the non-repetitive burial point event reporting attributes can be triggered by the target burial point event, and the embodiments of the present invention do not limit this.

[0109] In an embodiment of the present invention, the above method may further include the following steps:

[0110] When the target application of the target version starts to enter the foreground running state from the background pause state, the reporting attributes of the first repeated tracking event are collected uniformly.

[0111] In some feasible embodiments, a preset initialization event can uniformly collect the reporting attributes of each first repeated burial event when the target application of the target version enters the foreground running state from the background paused state; after the collection is completed, the preset initialization event can uniformly report the collected reporting attributes of each first repeated burial event, and the embodiments of the present invention are not limited to this.

[0112] In an embodiment of the present invention, multiple burying point events of a target application of a target version and multiple burying point event reporting attributes that need to be reported by each burying point event are determined; duplicate burying point event reporting attributes reported by at least two burying point events and non-duplicate burying point event reporting attributes reported by at most one burying point event are determined; duplicate burying point event reporting attributes include a globally applicable first duplicate burying point event reporting attribute; when the target application of the target version starts to enter the foreground running state from the background pause state, the first duplicate burying point event reporting attribute is reported; when the first target burying point event is triggered, the non-duplicate burying point event reporting attribute reported by the target burying point event is reported. Through the embodiment of the present invention, the reporting timing of different data can be reasonably set from a global perspective through a distributed burying point event design to improve the efficiency of data reporting, solve the problem of duplicate reporting, and effectively reduce the amount of code.

[0113] Reference Figure 4 , shows a flowchart of another method for reporting attributes of a buried event according to an embodiment of the present invention, which may include the following steps:

[0114] Step 401: Determine multiple tracking events of a target application of a target version, and multiple tracking event reporting attributes that need to be reported for each tracking event.

[0115] In actual applications, multiple tracking events of the target application of the target version can be pre-entered into the tracking system background. Each tracking event of the target application of the target version may involve multiple tracking event reporting attributes, that is, the content that the tracking event needs to report.

[0116] In addition, multiple tracking event reporting attributes corresponding to multiple tracking events of the target application can also be entered into the tracking system backend.

[0117] In each version, taking the current target version as an example, you can first determine multiple tracking events of the target application of the target version, as well as multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version.

[0118] Step 402: Determine the reporting attributes of repeated burying point events reported by at least two burying point events, and the reporting attributes of non-duplicate burying point events reported by at most one burying point event.

[0119] Each tracking event can correspond to at least one tracking event reporting attribute, and different tracking events may contain the same tracking event reporting attribute. If each tracking event reports the same tracking event reporting attribute once, there will be a problem of repeated reporting; and the code corresponding to the repeatedly reported tracking event reporting attribute needs to be included for each tracking event, which will lead to the problem of duplicate code.

[0120] To this end, after determining multiple tracking events of the target application of the target version and multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version, the tracking event reporting attributes that are repeatedly reported can be determined.

[0121] Specifically, if a burying event reporting attribute that needs to be reported in a burying event is the same as a burying event reporting attribute that needs to be reported in another burying event, it can be determined that the burying event reporting attribute is a duplicate burying event reporting attribute.

[0122] In actual applications, the tracking system backend can automatically compare the reporting attributes of duplicate tracking events in multiple tracking events corresponding to the target application of the target version.

[0123] In addition, non-repeating point event reporting attributes can be used as non-repeating point event reporting attributes; at most only one point event is reported for these non-repeating point event reporting attributes.

[0124] Step 403: The repeated burying point event reporting attributes include a second repeated burying point event reporting attribute common to burying point events of the same type, and the second repeated burying point event reporting attribute is reported by a preset burying point software development toolkit.

[0125] In some feasible embodiments, the second repeated burying point event reporting attributes may include the second repeated burying point event reporting attributes that are common to the same type of burying point events; for example: the page loading type burying point event needs to record the loading time loadtime, the previous page prepage (to analyze the page jump path), etc.

[0126] In the embodiment of the present invention, with respect to the second repeated burying point event reporting attribute, the second repeated burying point event reporting attribute may be reported by a preset burying point software development toolkit.

[0127] Specifically, when a tracking event is triggered and a second repeated tracking event reporting attribute needs to be reported, the second repeated tracking event reporting attribute can be reported by a preset tracking software development kit.

[0128] Of course, the preset tracking software development toolkit can also report all the second repeated tracking event reporting attributes that need to be reported in advance; however, for the real-time second repeated tracking event reporting attributes, the preset tracking software development toolkit can report the second repeated tracking event reporting attributes when the tracking event is triggered, and the embodiments of the present invention do not limit this.

[0129] Step 404: When a target burying point event is triggered, report the non-duplicate burying point event reporting attributes reported by the target burying point event.

[0130] In some feasible embodiments, for non-repetitive burial point event reporting attributes, the original reporting strategy can continue to be used by default; specifically, for non-repetitive burial point event reporting attributes, when its related target burial point event is triggered, the non-repetitive burial point event reporting attributes can be triggered by the target burial point event, and the embodiments of the present invention do not limit this.

[0131] In an embodiment of the present invention, the above method may further include the following steps:

[0132] The preset tracking software development toolkit collects the reporting attributes of the second repeated tracking event.

[0133] In some feasible embodiments, a declaration can be made through a unified logic, and a unified method and logic can be used in a preset embedding point SDK (Software Development Kit) to obtain the second repeated embedding point event reporting attributes; thus, there is no need to make a separate definition in each embedding point event, nor is there a need to add additional code for obtaining the second repeated embedding point event reporting attributes for each embedding point event, thereby reducing the amount of code.

[0134] In an embodiment of the present invention, multiple burying point events of a target application of a target version and multiple burying point event reporting attributes that need to be reported by each burying point event are determined; duplicate burying point event reporting attributes reported by at least two burying point events and non-duplicate burying point event reporting attributes reported by at most one burying point event are determined; duplicate burying point event reporting attributes include a second duplicate burying point event reporting attribute common to burying point events of the same type, and the second duplicate burying point event reporting attribute is reported by a preset burying point software development kit; when the first target burying point event is triggered, the non-duplicate burying point event reporting attribute reported by the target burying point event is reported. Through the embodiment of the present invention, the reporting timing of different data can be reasonably set from a global perspective through a distributed burying point event design to improve the efficiency of data reporting, solve the problem of duplicate reporting, and effectively reduce the amount of code.

[0135] Reference Figure 5 , shows a flowchart of another method for reporting attributes of a buried event according to an embodiment of the present invention, which may include the following steps:

[0136] Step 501: Determine multiple tracking events of a target application of a target version, and multiple tracking event reporting attributes that need to be reported for each tracking event.

[0137] In actual applications, multiple tracking events of the target application of the target version can be pre-entered into the tracking system background. Each tracking event of the target application of the target version may involve multiple tracking event reporting attributes, that is, the content that the tracking event needs to report.

[0138] In addition, multiple tracking event reporting attributes corresponding to multiple tracking events of the target application can also be entered into the tracking system backend.

[0139] In each version, taking the current target version as an example, you can first determine multiple tracking events of the target application of the target version, as well as multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version.

[0140] Step 502: Determine the reporting attributes of repeated burying point events reported by at least two burying point events, and the reporting attributes of non-duplicate burying point events reported by at most one burying point event.

[0141] Each tracking event can correspond to at least one tracking event reporting attribute, and different tracking events may contain the same tracking event reporting attribute. If each tracking event reports the same tracking event reporting attribute once, there will be a problem of repeated reporting; and the code corresponding to the repeatedly reported tracking event reporting attribute needs to be included for each tracking event, which will lead to the problem of duplicate code.

[0142] To this end, after determining multiple tracking events of the target application of the target version and multiple tracking event reporting attributes that need to be reported for each of the multiple tracking events of the target application of the target version, the tracking event reporting attributes that are repeatedly reported can be determined.

[0143] Specifically, if a burying event reporting attribute that needs to be reported in a burying event is the same as a burying event reporting attribute that needs to be reported in another burying event, it can be determined that the burying event reporting attribute is a duplicate burying event reporting attribute.

[0144] In actual applications, the tracking system backend can automatically compare the reporting attributes of duplicate tracking events in multiple tracking events corresponding to the target application of the target version.

[0145] In addition, non-repeating point event reporting attributes can be used as non-repeating point event reporting attributes; at most only one point event is reported for these non-repeating point event reporting attributes.

[0146] Step 503: The repeated burying point event reporting attributes include a third repeated burying point event reporting attribute common to related burying point events of a target analysis theme, and the third repeated burying point event reporting attribute is reported by the main event of the target analysis theme.

[0147] In some feasible embodiments, the complex buried point event reporting attributes may include a third repeated buried point event reporting attribute common to related buried point events of a target analysis theme; for example: the third repeated buried point event reporting attribute common to related buried point events of the target analysis theme of network configuration is the network configuration type nw_type (Bluetooth network configuration, manual network configuration, automatic network configuration, etc.), the network configuration task taskid, etc.

[0148] In an embodiment of the present invention, for the third repeated burying point event reporting attribute, the second repeated burying point event reporting attribute can be reported by the main event of the target analysis subject. Specifically, when the main event is triggered, the third repeated burying point event reporting attribute can be uniformly reported.

[0149] Among them, the main event can refer to the problem of the analysis target analysis theme, and the event that plays a major role among the several problems set.

[0150] For example, analyzing device network configuration may involve event A (main event) of the overall network configuration process, event B of each network configuration step, and event C of the user's choice of further operation after network configuration failure. Among the above three events:

[0151] ① From the demand point of view, each event should report the network configuration task ID (the same ID is regarded as the same network configuration process), network type (wifi / bluetooth / other, etc.), network signal strength (1-5), etc. ② Take event A as the main event;

[0152] In the above cases ① and ②, only event A needs to report three attributes, and events B and C need to report one attribute, the network configuration task ID. The remaining two attributes can be obtained from event A through the same network configuration task ID without the need for repeated reporting.

[0153] Of course, the preset tracking software development toolkit can also report all the third repeated tracking event reporting attributes that need to be reported in advance.

[0154] Step 504: When a target burying point event is triggered, report the non-duplicate burying point event reporting attributes reported by the target burying point event.

[0155] In some feasible embodiments, for non-repetitive burial point event reporting attributes, the original reporting strategy can continue to be used by default; specifically, for non-repetitive burial point event reporting attributes, when its related target burial point event is triggered, the non-repetitive burial point event reporting attributes can be triggered by the target burial point event, and the embodiments of the present invention do not limit this.

[0156] In an embodiment of the present invention, the above method may further include the following steps:

[0157] The third repeated embedding point event reporting attributes are collected by the main event of the target analysis topic.

[0158] In some feasible embodiments, the third repeated burial point event reporting attribute can be obtained by the main event; thus, there is no need to make a separate definition in each burial point event, nor is there a need to add additional code for obtaining the second repeated burial point event reporting attribute for each burial point event, thereby reducing the amount of code.

[0159] In an embodiment of the present invention, multiple burying point events of a target application of a target version and multiple burying point event reporting attributes that need to be reported by each burying point event are determined; duplicate burying point event reporting attributes reported by at least two burying point events and non-duplicate burying point event reporting attributes reported by at most one burying point event are determined; duplicate burying point event reporting attributes include a third duplicate burying point event reporting attribute common to related burying point events of a target analysis subject, and the third duplicate burying point event reporting attribute is reported by the main event of the target analysis subject; when a target burying point event is triggered, the non-duplicate burying point event reporting attribute reported by the target burying point event is reported. Through the embodiment of the present invention, the reporting timing of different data can be reasonably set from a global perspective through a distributed burying point event design to improve the efficiency of data reporting, solve the problem of duplicate reporting, and effectively reduce the amount of code.

[0160] The following, combined with Figure 6 The method of reporting the attributes of the above-mentioned tracking events is further explained; Figure 6 As shown:

[0161] S1. The user starts or reawakens the APP, triggering an initialization event, through which all global attribute fields (i.e., the first repeated burial event reporting attributes) are collected and reported.

[0162] S2. During user use, various tracking events are triggered. According to the type of each tracking event, the tracking SDK collects and reports the common attributes of the event type (i.e., the second repeated tracking event reporting attributes). The non-event type common attributes are reported by the code of each tracking event.

[0163] S3. Further, for the non-event type common attributes in S2, if other main events of the same topic have been collected and reported, there is no need to report them again.

[0164] S4. Further, for the attributes that are not reported repeatedly in S3, the embedding code is normally implanted and reported.

[0165] It should be noted that, for the sake of simplicity, the method embodiments are described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0166] Reference Figure 7 , shows a schematic diagram of the structure of a device for reporting attributes of a buried event according to an embodiment of the present invention, which may include the following modules:

[0167] The first determination module 701 is used to determine multiple tracking events of a target application of a target version, and multiple tracking event reporting attributes that need to be reported for each tracking event;

[0168] The second determining module 702 is used to determine the reporting attributes of duplicate burying point events reported by at least two burying point events, and the reporting attributes of non-duplicate burying point events reported by at most one burying point event;

[0169] The reporting module 703 is used to uniformly report the reporting attributes of repeated burying point events, and when a target burying point event is triggered, report the reporting attributes of non-duplicate burying point events reported by the target burying point event.

[0170] In an optional embodiment of the present invention, the duplicate burial point event reporting attribute includes a globally applicable first duplicate burial point event reporting attribute; the reporting module 703 is used to report the first duplicate burial point event reporting attribute when the target application of the target version is started.

[0171] In an optional embodiment of the present invention, the repeated burial point event reporting attribute includes a globally applicable first repeated burial point event reporting attribute; the reporting module 703 is used to report the first repeated burial point event reporting attribute when the target application of the target version starts to enter the foreground running state from the background pause state.

[0172] In an optional embodiment of the present invention, the first repeated embedding event reporting attribute includes at least one of the following:

[0173] Application version information, operating system information, terminal information, account information.

[0174] In an optional embodiment of the present invention, the reporting module 703 is also used to uniformly collect the first repeated embedding event reporting attributes when the target application of the target version is started.

[0175] In an optional embodiment of the present invention, the repeated burying point event reporting attributes include a second repeated burying point event reporting attribute common to the same type of burying point events, and the reporting module 703 is used to report the second repeated burying point event reporting attribute by a preset burying point software development toolkit.

[0176] In an optional embodiment of the present invention, the reporting module 703 is also used to collect the second repeated tracking event reporting attributes by a preset tracking software development toolkit.

[0177] In an optional embodiment of the present invention, the repeated burial point event reporting attributes include a third repeated burial point event reporting attribute common to the relevant burial point events of a target analysis subject, and the reporting module 703 is used to report the third repeated burial point event reporting attribute by the main event of the target analysis subject.

[0178] In an optional embodiment of the present invention, the reporting module 703 is also used to collect the reporting attributes of the third repeated embedding event from the main event of the target analysis subject.

[0179] In an embodiment of the present invention, multiple burying point events of a target application of a target version and multiple burying point event reporting attributes that need to be reported by each burying point event are determined; duplicate burying point event reporting attributes reported by at least two burying point events and non-duplicate burying point event reporting attributes reported by at most one burying point event are determined; duplicate burying point event reporting attributes are uniformly reported, and when a target burying point event is triggered, the non-duplicate burying point event reporting attributes reported by the target burying point event are reported. Through an embodiment of the present invention, the reporting timing of different data can be reasonably set from a global perspective through a distributed burying point event design to improve the efficiency of data reporting, solve the problem of duplicate reporting, and effectively reduce the amount of code.

[0180] An embodiment of the present invention also provides an electronic device, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, the above-mentioned method for reporting the attributes of the buried event is implemented.

[0181] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the attribute reporting method of the above-mentioned tracking event is implemented.

[0182] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0183] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0184] Those skilled in the art will appreciate that the embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0185] The embodiments of the present invention are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0186] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0187] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0188] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0189] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0190] The above provides a detailed introduction to a method for reporting the attributes of a buried event, a device for reporting the attributes of a buried event, an electronic device and a computer-readable storage medium. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A method for reporting attributes of a buried event, characterized in that: The method comprises: Determine multiple tracking events of the target application of the target version, and multiple tracking event reporting attributes that need to be reported for each tracking event; Determine the reporting attributes of duplicate tracking events reported by at least two tracking events, and the reporting attributes of non-duplicate tracking events reported by at most one tracking event; The reporting attributes of the repeated burying point events are reported uniformly, and when a target burying point event is triggered, the reporting attributes of the non-duplicate burying point event reported by the target burying point event are reported.

2. The method according to claim 1, characterized in that The repeated burying point event reporting attribute includes a globally applicable first repeated burying point event reporting attribute; The unified reporting of the repeated tracking event reporting attributes includes: When the target application of the target version is started, the first duplicate burying event reporting attribute is reported.

3. The method according to claim 1, characterized in that: The repeated burying point event reporting attribute includes a globally applicable first repeated burying point event reporting attribute; The unified reporting of the repeated tracking event reporting attributes includes: When the target application of the target version starts to enter the foreground running state from the background pause state, the first repeated burying event reporting attribute is reported.

4. The method according to any one of claims 2 to 3, characterized in that: The first repeated tracking event reporting attribute includes at least one of the following: Application version information, operating system information, terminal information, account information.

5. The method according to claim 2, characterized in that: The method further comprises: When the target application of the target version is started, the first repeated burying event reporting attributes are uniformly collected.

6. The method according to claim 1, characterized in that The repeated burying point event reporting attribute includes a second repeated burying point event reporting attribute common to the same type of burying point events, and the unified reporting of the repeated burying point event reporting attribute includes: The preset tracking point software development toolkit reports the second repeated tracking point event reporting attribute.

7. The method according to claim 6, characterized in that The method further comprises: The preset tracking point software development toolkit collects the second repeated tracking point event reporting attributes.

8. The method according to claim 1, characterized in that The repeated burying point event reporting attribute includes a third repeated burying point event reporting attribute common to related burying point events of a target analysis subject, and the unified reporting of the repeated burying point event reporting attribute includes: The third repeated embedding point event reporting attribute is reported by the main event of the target analysis subject.

9. The method according to claim 8, characterized in that The method further comprises: The third repeated embedding event reporting attributes are collected by the main event of the target analysis topic.

10. A device for reporting attributes of a buried event, characterized in that: The device comprises: A first determination module is used to determine multiple tracking events of a target application of a target version, and multiple tracking event reporting attributes that need to be reported for each tracking event; A second determination module is used to determine the reporting attributes of duplicate burying point events reported by at least two burying point events, and the reporting attributes of non-duplicate burying point events reported by at most one burying point event; The reporting module is used to uniformly report the reporting attributes of the repeated burying point events, and when a target burying point event is triggered, report the reporting attributes of the non-duplicate burying point event reported by the target burying point event.

11. An electronic device, characterized in that: It includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, it implements the attribute reporting method of the buried event as described in any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for reporting attributes of a buried event as described in any one of claims 1 to 9 is implemented.

Images