Method for detecting a buried point, electronic device and program product

Abstract

The present disclosure provides a method for detecting a buried point, an electronic device and a program product. The method for detecting a buried point comprises: identifying a page identifier and an event type corresponding to a buried point event from the received buried point event information; determining the number of events of each event type related to the page identifier according to the event type of each buried point event related to the page identifier; performing quantity verification on the number of events of each event type related to the page identifier to determine whether the number of events of different event types meets a target quantity rule; and determining that the buried point event information is abnormal buried point event information if the number of events of different event types does not meet the target quantity rule.

Description

Technical Field

[0001] This disclosure relates to a method for detecting embedded points, an electronic device, and a program product. Background Technology

[0002] In mobile application development, event tracking technology is used to collect user behavior data, providing a basis for product effectiveness evaluation and business decisions. Current event tracking implementations primarily focus on data collection and post-event analysis, lacking real-time detection mechanisms for event tracking quality. This leads to quality defects in event tracking code regarding data accuracy, logical rationality, and trigger correctness. These quality defects are difficult to detect during the mobile application development phase and typically only become apparent after the application is launched through data anomaly analysis, resulting in lengthy troubleshooting cycles and high remediation costs. Summary of the Invention

[0003] This disclosure provides a method for detecting embedded points, an electronic device, and a program product.

[0004] According to one aspect of this disclosure, a method for detecting event tracking points is provided, comprising: identifying, based on received event tracking information, a page identifier and event type corresponding to the event tracking event, wherein the event type includes a page exposure event, an in-page element exposure event, or an in-page element click event; determining the number of events of each event type associated with the page identifier based on the event type of each event tracking event associated with the page identifier; performing quantity verification based on the number of events of each event type associated with the page identifier to determine whether the number of events of different event types conforms to a target quantity rule; and determining that the event tracking information is abnormal event tracking information if the number of events of different event types does not conform to the target quantity rule.

[0005] According to one technical solution, page identifiers and event types are identified from the event tracking information. Based on the event types of each event tracking event related to the page identifier, the number of events of different event types is determined and then the number is verified. This can detect data anomalies that violate basic business rules due to errors in tracking logic in a timely and accurate manner, improve the quality of tracking data, effectively shorten the discovery cycle of tracking data quality problems, and reduce repair costs.

[0006] According to at least one embodiment of the tracking point detection method of this disclosure, after identifying the page identifier and event type corresponding to the tracking point event from the received tracking point event information, the tracking point detection method further includes: when the event type is a page exposure event, determining whether there is a first user interface corresponding to the page identifier; when the first user interface exists, determining whether the first user interface is visible; and when the first user interface does not exist or the first user interface is invisible, determining that the tracking point event information is abnormal tracking point event information.

[0007] According to the technical solution of this embodiment, page exposure event data triggered by the user interface in invisible scenarios (such as background running state, application minimized, etc.) can be effectively identified, thus avoiding the generation of false page exposure data.

[0008] According to at least one embodiment of the present disclosure, the method for detecting embedded points determines whether a first user interface corresponding to the page identifier exists, including: searching for a first user interface corresponding to the page identifier in the user interface at the activity level based on the page identifier; and if the first user interface does not exist in the user interface at the activity level, searching for a first user interface corresponding to the page identifier in the user interface at the fragment level.

[0009] According to the technical solution of this embodiment, by using a hierarchical search strategy from the user interface at the activity level to the user interface at the fragment level, the interface component corresponding to the event tracking can be accurately located.

[0010] According to at least one embodiment of the tracking point detection method of this disclosure, after identifying the page identifier and event type corresponding to the tracking point event from the received tracking point event information, the tracking point detection method further includes: when the event type is an in-page element exposure event, identifying the corresponding element identifier from the tracking point event information; determining, based on the page identifier and the element identifier, whether there exists a second user interface corresponding to the page identifier and containing an in-page element corresponding to the element identifier; if the second user interface exists, determining whether the second user interface has been exposed; and if the second user interface does not exist or the second user interface has not been exposed, determining that the tracking point event information is abnormal tracking point event information.

[0011] According to the technical solution of this implementation method, the logical error of "no page exposure but page element exposure" can be effectively prevented, ensuring that the tracking data conforms to the basic business rule of "page exposure first, then page element exposure", thus guaranteeing the quality of tracking data.

[0012] According to at least one embodiment of the tracking point detection method of this disclosure, after identifying the page identifier and event type corresponding to the tracking point event from the received tracking point event information, the tracking point detection method further includes: if the event type is an element click event within a page, identifying the corresponding element identifier from the tracking point event information; determining, based on the page identifier and the element identifier, whether there exists a third user interface corresponding to the page identifier and containing an element within a page corresponding to the element identifier; if the third user interface exists, determining whether both the third user interface and the element within the page have been exposed; and if the third user interface does not exist or at least one of the third user interface and the element within the page has not been exposed, determining that the tracking point event information is abnormal tracking point event information.

[0013] According to the technical solution of this embodiment, the logical error of "no page exposure or page element exposure but page element click" can be effectively prevented, ensuring that the tracking data conforms to the basic business rule of "page exposure and page element exposure first, and page element click later", thus guaranteeing the quality of tracking data.

[0014] According to at least one embodiment of the tracking point detection method of this disclosure, after identifying the page identifier from the tracking point event information, the tracking point detection method further includes: if the page identifier identified from the tracking point event information is a null value or an invalid value, determining that the tracking point event information is abnormal tracking point event information.

[0015] According to the technical solution of this embodiment, it is possible to effectively prevent the data tracking points from becoming disconnected from the business scenario (i.e., user interface) due to missing or invalid page identifiers, and ensure that each data tracking point event can be accurately associated with the specific business scenario.

[0016] According to the tracking detection method of at least one embodiment of this disclosure, the target quantity rules include: the number of page exposure events is greater than or equal to the number of element exposure events within the page; and the number of element exposure events related to the same element within the page is greater than or equal to the number of element click events within the page.

[0017] According to the technical solution of this implementation, the basic business rules are converted into automatically executable verification rules through target quantity rules, thereby discovering and intercepting in real time errors in the tracking points that violate the basic causal relationship, such as "clicks are greater than exposures" or "exhibition events of elements within the page precede exposure events of the page", which greatly shortens the problem discovery and repair cycle.

[0018] According to at least one embodiment of the tracking point detection method of this disclosure, after determining that the tracking point event information is abnormal tracking point event information, the tracking point detection method further includes: identifying a first tracking point identifier from the abnormal tracking point event information that reported the abnormal tracking point event information; comparing the first tracking point identifier with a second tracking point identifier included in a target whitelist, wherein the second tracking point identifier is a tracking point identifier of a tracking point that is allowed to report abnormal tracking point event information; and generating and sending alarm information based on the abnormal tracking point event information when the first tracking point identifier and the second tracking point identifier are both different.

[0019] According to the technical solution of this implementation, by setting a target whitelist, it is possible to effectively distinguish between real problems and compliance special scenarios, avoid false alarms for special business scenarios (such as backend services, preloading, etc.), and ensure the accuracy of alarms.

[0020] According to at least one embodiment of the tracking point detection method of this disclosure, after generating and sending alarm information based on the abnormal tracking point event information, the tracking point detection method further includes: recording the abnormal tracking point event information and marking its processing status as unprocessed; updating the processing status of the abnormal tracking point event information to processed according to the processing operation of the abnormal tracking point event information; and generating and sending a prompt message for the abnormal tracking point event information whose processing status is unprocessed in response to a target triggering condition.

[0021] According to the technical solution of this embodiment, by establishing an anomaly record with processing status for each anomaly tracking point, scattered anomaly alarms are transformed into a task list that can be queried, statistically analyzed, and followed up, providing a data foundation for subsequent problem handling.

[0022] According to one aspect of this disclosure, a tracking point detection device is provided, comprising: an identification module, configured to identify a page identifier and event type corresponding to a tracking point event from received tracking point event information, wherein the event type includes a page exposure event, an in-page element exposure event, or an in-page element click event; a determination module, configured to determine the number of events of each event type associated with the page identifier based on the event type of each tracking point event associated with the page identifier; a verification module, configured to perform quantity verification based on the number of events of each event type associated with the page identifier to determine whether the number of events of different event types conforms to a target quantity rule; and a processing module, configured to determine that the tracking point event information is abnormal tracking point event information if the number of events of different event types does not conform to the target quantity rule.

[0023] According to another aspect of this disclosure, an electronic device is provided, comprising: a memory storing execution instructions; and a processor executing the execution instructions stored in the memory, causing the processor to perform a data embedding detection method according to any embodiment of this disclosure.

[0024] According to another aspect of this disclosure, a readable storage medium is provided, wherein executable instructions are stored therein, which, when executed by a processor, are used to implement the embedded point detection method of any embodiment of this disclosure.

[0025] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the embedding detection method of any embodiment of this disclosure. Attached Figure Description

[0026] The accompanying drawings illustrate exemplary embodiments of the present disclosure and, together with the description thereof, serve to explain the principles of the present disclosure. These drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification.

[0027] Figure 1 This is a schematic diagram illustrating an application scenario of the embedded point detection method according to one embodiment of this disclosure.

[0028] Figure 2 This is a flowchart illustrating an embodiment of the embedded point detection method disclosed herein.

[0029] Figure 3 This is a flowchart illustrating the page visibility detection process in a tracking detection method according to one embodiment of this disclosure.

[0030] Figure 4 This is a flowchart illustrating step S310 of a method for detecting embedded points according to one embodiment of this disclosure.

[0031] Figure 5 This is a flowchart illustrating the event timing detection process in a data embedding detection method according to one embodiment of this disclosure.

[0032] Figure 6 This is a flowchart illustrating the event timing detection process in another embodiment of the embedding detection method of this disclosure.

[0033] Figure 7 This is a schematic diagram of the whitelist filtering process included in one embodiment of the embedding detection method of this disclosure.

[0034] Figure 8 This is a flowchart illustrating the abnormal event notification process included in one embodiment of the event detection method disclosed herein.

[0035] Figure 9 This is a flowchart illustrating the page visibility detection process in another embodiment of the embedding detection method of this disclosure.

[0036] Figure 10 This is a flowchart illustrating the event timing detection process in another embodiment of the tracking detection method disclosed herein.

[0037] Figure 11 This is a block diagram of an embedded point detection device according to one embodiment of the present disclosure.

[0038] Figure 12 This is a schematic structural block diagram of an electronic device according to one embodiment of the present disclosure. Detailed Implementation

[0039] The present disclosure will now be described in further detail with reference to the accompanying drawings and examples. It should be understood that the specific examples described herein are for illustrative purposes only and are not intended to limit the scope of the disclosure. Furthermore, it should be noted that, for ease of description, only the parts relevant to the present disclosure are shown in the accompanying drawings.

[0040] It should be noted that, where there is no conflict, the embodiments and features described in this disclosure can be combined with each other. The technical solutions of this disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0041] Existing technologies struggle to detect errors in event tracking data in a timely manner, and these errors can only be passively discovered through data analysis after the product has been launched. This results in a long discovery cycle and high repair costs for event tracking data quality issues.

[0042] To address this, this disclosure proposes the following technical solution: Upon receiving event information reported by the tracking points, the page identifier and event type corresponding to the tracking event are identified from the event information. Then, the number of events for each event type related to the page identifier is counted and verified to determine whether the number of events for different event types conforms to a target number rule. This target number rule includes: the number of page exposure events is greater than or equal to the number of element exposure events within the page; and the number of element exposure events related to elements within the same page is greater than or equal to the number of element click events within the page.

[0043] If the number of events of different event types does not conform to the target number rule, the received event information is identified as abnormal event information. This allows for timely and accurate detection of data anomalies caused by errors in event tracking logic that violate basic business rules, improving the quality of event tracking data, effectively shortening the discovery cycle of event tracking data quality issues, and reducing repair costs.

[0044] Figure 1This is a schematic diagram illustrating an application scenario of the embedded point detection method according to one embodiment of this disclosure. For example... Figure 1 As shown, this application scenario may include terminal device 101, network 102, and server 103. Among them, network 102 is used to provide a network link medium between terminal device 101 and server 103.

[0045] For example, users or developers can use or test the mobile application through terminal device 101 (e.g., a smartphone). During the use or testing of the mobile application, the event tracking points deployed for the mobile application can generate event information and report it to server 103 when the triggering conditions are met.

[0046] Server 103 may be configured with a data tracking detection device. For example, the data tracking detection device may receive data tracking event information reported by the data tracking points.

[0047] After receiving the event tracking information, server 103 identifies the page identifier and event type corresponding to the event from the event tracking information. The event type includes page exposure event, in-page element exposure event, or in-page element click event. Then, based on the event type of each event tracking event related to the page identifier, it performs statistics to determine the number of events of each event type related to the page identifier (i.e., the number of events of page exposure event, in-page element exposure event, and in-page element click event).

[0048] Then, server 103 performs quantity verification based on the number of events of each event type associated with the page identifier, thereby determining whether the number of events of different event types conforms to the target quantity rules. These target quantity rules include: the number of page exposure events is greater than or equal to the number of in-page element exposure events, and the number of in-page element exposure events related to the same in-page element is greater than or equal to the number of in-page element click events. If the number of events of different event types does not conform to the target quantity rules, the event information is determined to be abnormal event information. In this way, through quantity verification, abnormal event data that violates basic business rules can be detected, improving the quality of event data.

[0049] Figure 2 This is a flowchart illustrating an embodiment of the embedded point detection method of this disclosure. This embedded point detection method can be applied to the embedded point detection device described above. Figure 2 As shown, the embedding detection method may include steps S210 to S240.

[0050] In step S210, based on the received event tracking information, the page identifier and event type corresponding to the event tracking are identified from the event tracking information. The event type includes page exposure event, page element exposure event, or page element click event.

[0051] Among them, the event tracking information can be a set of data automatically collected and reported by the tracking SDK (Software Development Kit) when the user interacts with the application interface during the operation of the mobile application.

[0052] A User Interface Code (UICODE) is identification information used to uniquely identify and locate a user interface. Preferably, the UICODE is configured in the user interface through annotations or attributes, serving as a key basis for identifying business scenarios.

[0053] The event type is a classification information obtained by dividing the types of event tracking. Preferably, the event types include page exposure events, in-page element exposure events, and in-page element click events.

[0054] Specifically, a page exposure event is a tracking event that indicates a user interface has entered the user's field of vision and becomes visible. An in-page element exposure event is a tracking event that indicates a module or component within the user interface (such as a button, card, or ad) has entered the user's field of vision. An in-page element click event is a tracking event that indicates the user has clicked on a module or component within the user interface.

[0055] In this embodiment, the event tracking detection device receives event information reported by the event tracking SDK. By parsing the event information (e.g., structured parsing), the event tracking detection device can identify the page identifier and event type corresponding to the event from the event information.

[0056] Preferably, the event tracking detection device can accurately identify the page identifier and event type of the event by reading key fields such as "UICODE (page identifier)" and "event (event type)" in the event tracking information.

[0057] In step S220, the number of events for each event type associated with the page identifier is determined based on the event type of each tracking event associated with the page identifier.

[0058] The number of events can be the cumulative number of times a certain event type associated with the same page identifier occurs within a pre-defined statistical period (such as the current usage time of a mobile application).

[0059] After the tracking point detection device determines the page identifier and event type corresponding to the newly received tracking point event information, it can perform statistics based on the event types of the tracking point events related to that page identifier to determine the number of events of each event type related to that page identifier.

[0060] Preferably, the event tracking device maintains a global mapping table (Map) with page identifiers as keys. Each key corresponds to a counting object, which contains three independent counters: a page exposure counter, an in-page element exposure counter, and an in-page element click counter. When a new event tracking information is received, the corresponding counting object in the global mapping table is located based on the identified page identifier and event type, and the corresponding incremental operation is performed according to the event type. For example, if it is a page exposure event, the page exposure counter value is incremented by 1; if it is an in-page element exposure event, the in-page element exposure counter value is incremented by 1; if it is an in-page element click event, the in-page element click counter value is incremented by 1.

[0061] After the incremental operation is completed, the event tracking device can extract the values ​​of three independent counters (including page exposure counter, page element exposure counter, and page element click counter) from the global mapping table associated with the page identifier, thereby determining the number of events of each event type associated with the page identifier.

[0062] It should be noted that since a single user interface can contain one or more in-page elements, the number of in-page element exposure counters and in-page element click counters can be one or more. That is, one in-page element corresponds to one in-page element exposure counter and one in-page element click counter, which are used to record the number of in-page element exposure events and the number of in-page element click events corresponding to that in-page element, respectively.

[0063] In step S230, a quantity verification is performed based on the number of events of each event type associated with the page identifier to determine whether the number of events of different event types conforms to the target quantity rule.

[0064] Among them, the target quantity rule can be a pre-set constraint on the quantity of events of different event types to ensure the logical rationality of the data tracking.

[0065] In this embodiment, after determining the number of events of each event type related to the page identifier, the event tracking device can perform quantity verification based on the number of events of different event types related to the page identifier, thereby determining whether the number of events of different event types conforms to the preset target quantity rules.

[0066] In some embodiments of this disclosure, the target quantity rules include: the number of page exposure events is greater than or equal to the number of element exposure events within the page; and the number of element exposure events related to the same element within the page is greater than or equal to the number of element click events within the page.

[0067] In this implementation, the target number rule is that for the same user interface, the number of page exposure events should be greater than or equal to the number of page element exposure events for all page elements contained in the user interface. Also, for the same page element within the user interface, the number of page element exposure events should be greater than or equal to the number of page element click events.

[0068] Preferably, the tracking device compares the number of page exposure events related to the page identifier with the number of page element exposure events (corresponding to each page element in the user interface corresponding to the page identifier) ​​to determine whether the page exposure event is greater than or equal to the number of page element exposure events corresponding to each page element.

[0069] For an element on the same page, compare the number of exposure events of the element with the number of click events of the element to determine whether the number of exposure events is greater than or equal to the number of click events.

[0070] Therefore, by setting the above target quantity rules, basic business rules are transformed into automatically executable verification rules, thereby discovering and intercepting in real time errors in the tracking points that violate basic causal relationships, such as "clicks are greater than exposures" or "exhibition events of elements within the page precede page exposure events", which greatly shortens the problem discovery and repair cycle.

[0071] It should be noted that the target quantity rule may include quantity relationship constraints in different forms based on the number of events of different event types (including page exposure events, in-page element exposure events, and in-page element click events).

[0072] Preferably, the target quantity rule may include one or more of the following: linear inequality quantitative relationships, nonlinear inequality quantitative relationships, and quantity size relationships constructed for the quantity of events of different event types.

[0073] Taking a linear inequality as an example, let the number of page exposure events be x, the number of element exposure events within the same page be y, and the number of element click events within the page be z. Then, the linear inequality can be ax + by + cz < d or e > x > y > z, where a, b, c, d, and e are constants that can be set by the tester based on prior experience. In one example, the linear inequality can be 2x + 3y + 4z < 5 (i.e., a = 2, b = 3, c = 4, d = 5) or 5 > x > y > z (i.e., e = 5).

[0074] Taking a nonlinear inequality relationship as an example, let the number of page exposure events be x, the number of page element exposure events within the same page be y, and the number of page element click events be z. Then the pre-constructed nonlinear inequality relationship can be x. f +y g +c h <i, where f, g, h, and i are constants that can be set by the tester based on prior experience. In one example, this nonlinear inequality can be expressed as x. 2 +y 2 +c 2 <9 (i.e., f=2, g=2, h=2, i=9).

[0075] It should be noted that the above figures are merely illustrative examples and are not intended to impose any specific limitations on them.

[0076] The embedded point detection device can substitute the determined number of events of each event type related to the page identifier into the above linear inequality relationship or nonlinear inequality relationship, and then determine whether the number of events of different event types related to the page identifier satisfies the linear inequality relationship or nonlinear inequality relationship.

[0077] In addition, to further ensure the rationality of the recorded tracking data, besides the aforementioned linear or nonlinear inequality relationships, x≥y≥z (i.e., the aforementioned quantitative relationship) can also be specified simultaneously to avoid situations such as "the number of clicks is greater than the number of exposures" and to ensure the quality of the tracking data.

[0078] Of course, the target quantity rule can also limit only the relationship between the quantity of events of different event types, and this disclosure does not make any special restrictions on this.

[0079] Please continue to refer to this. Figure 2 In step S240, if the number of events of different event types does not conform to the target number rule, the event information is determined to be abnormal event information.

[0080] In this implementation, after quantity verification, if the number of events of different event types related to the page identifier does not conform to the aforementioned target quantity rule, the newly received event information can be determined as abnormal event information. If the number of events of different event types related to the page identifier conforms to the aforementioned target quantity rule, the newly received event information can be determined as normal event information, and the event information can be recorded.

[0081] The event tracking detection method disclosed herein can detect data anomalies that violate basic business rules due to event tracking logic errors in a timely and accurate manner, thereby improving the quality of event tracking data, effectively shortening the discovery cycle of event tracking data quality problems, and reducing repair costs.

[0082] In some embodiments of this disclosure, after step S210, which identifies the page identifier and event type corresponding to the tracking event from the received tracking event information, the tracking detection method of this disclosure further includes steps S310 to S330, as described above. Figure 3 .

[0083] In step S310, if the event type is a page exposure event, it is determined whether there is a first user interface corresponding to the page identifier.

[0084] In this embodiment, when the event type is determined to be a page exposure event, the tracking detection device searches for the page identifier identified from the tracking event information to determine whether there is a first user interface corresponding to the page identifier, that is, to determine whether there is a user interface with the same page identifier as the identified page identifier.

[0085] In step S320, when the first user interface exists, it is determined whether the first user interface is visible.

[0086] In this embodiment, after determining that a first user interface corresponds to the identified page identifier, the event tracking device can acquire the lifecycle state of the first user interface. This lifecycle state is a status identifier representing different operational stages of the user interface, including a visible state or an invisible state. Based on the lifecycle state of the first user interface, the event tracking device can determine whether the first user interface is visible.

[0087] It should be understood that page exposure events should be triggered when the user interface is visible to the user. If the primary user interface is not visible to the user but a page exposure event is triggered, it indicates an error in the event tracking logic.

[0088] In step S330, if the first user interface does not exist or the first user interface is invisible, the event tracking information is determined to be abnormal event tracking information.

[0089] In this embodiment, through steps S310 and S320, if no first user interface corresponding to the page identifier identified from the event tracking information is found, or if a first user interface corresponding to the page identifier exists but is invisible, then the event tracking detection device can determine that the newly received event tracking information is abnormal event tracking information.

[0090] If a first user interface exists that corresponds to the page identifier identified from the event tracking information, and this first user interface is visible, then the event tracking logic is correct, and the event tracking information is correct.

[0091] In this way, page exposure event data triggered by the user interface in invisible scenarios (such as background running state, application minimized, etc.) can be effectively identified, avoiding the generation of false page exposure data.

[0092] In some embodiments of this disclosure, determining whether a first user interface corresponding to the page identifier preferably includes steps S311 to S312, please refer to... Figure 4 .

[0093] In step S311, based on the page identifier, a search is conducted in the user interface of the active level to determine whether a first user interface corresponding to the page identifier exists.

[0094] In step S312, if the first user interface does not exist in the user interface of the activity level, the user interface of the fragment level is searched to see if a first user interface corresponding to the page identifier exists.

[0095] Among them, the user interface of the activity level is the Activity component in an Android application. It is the basic interface unit of the application and is responsible for managing user interaction and the lifecycle of the interface.

[0096] The fragment-level user interface is a fragment component in an Android application. It is a reusable interface module within an Activity component and has an independent lifecycle.

[0097] In this embodiment, when the event tracking device searches for the existence of a first user interface corresponding to a page identifier identified from the event tracking information, it can first search within the user interfaces of the activity level. Specifically, the identified page identifier is matched with the page identifiers of the user interfaces of each activity level. If the identified page identifier is the same as the page identifier of a user interface of a certain activity level, then it is determined that a first user interface corresponding to the identified page identifier exists.

[0098] Furthermore, if the page identifier identified from the event tracking information is different from the page identifier of the user interface at the activity level, the event tracking detection device can match the page identifier with the page identifier of the user interface at the fragment level. If there is a user interface at a fragment level that has the same page identifier as the page identifier identified from the event tracking information, then it is determined that a first user interface corresponding to the identified page identifier exists.

[0099] If the page identifier of the user interface at the fragment level is also different from the page identifier identified from the event tracking information, it is determined that there is no first user interface corresponding to the page identifier identified from the event tracking information.

[0100] In this way, by adopting a hierarchical search strategy from the user interface at the activity level to the user interface at the fragment level, the corresponding interface component (i.e., the first user interface) can be accurately located, effectively solving the problem of location failure caused by the complexity of the interface hierarchy, and laying the foundation for subsequent page visibility verification.

[0101] In some embodiments of this disclosure, after step S210, which identifies the page identifier and event type corresponding to the tracking event from the received tracking event information, the tracking detection method of this disclosure further includes steps S510 to S540. Please refer to [link / reference]. Figure 5 .

[0102] In step S510, if the event type is an in-page element exposure event, the corresponding element identifier is identified from the event tracking information.

[0103] Among them, the element identifier can be the identification information used to uniquely identify elements within the page.

[0104] In this embodiment, the tracking point detection device can identify element identifiers related to tracking point events from the tracking point event information. Preferably, the tracking point detection device can identify key fields (such as the "EXPOID (element ID)" field) in the tracking point event information to determine the element identifier.

[0105] In step S520, based on the page identifier and the element identifier, it is determined whether there exists a second user interface that corresponds to the page identifier and contains elements within the page that correspond to the element identifier.

[0106] In this embodiment, the event tracking device first searches for a page identifier identified from the event tracking information to determine whether a user interface corresponding to that page identifier exists (see example...). Figure 4 The process for finding the first user interface is shown below (and will not be repeated here). If a user interface corresponding to the identified page identifier exists, it is then determined whether the found user interface contains an element within the page corresponding to that element identifier.

[0107] If a user interface corresponding to the page identifier is found, and the user interface contains an element within the page corresponding to the element identifier, then it is determined that the second user interface exists.

[0108] If no user interface corresponding to the page identifier is found, or if a user interface corresponding to the page identifier is found but does not contain any page element corresponding to the element identifier, then it is determined that the second user interface does not exist.

[0109] Preferably, in the global mapping table maintained in the event tracking device, the page identifier of the user interface is bound to the element identifier of each element within the page of the user interface. Therefore, after determining the user interface based on the page identifier, the event tracking device can query the global mapping table corresponding to the user interface to determine whether the page identifier of the user interface is associated with the element identifier identified from the event tracking information, thereby determining whether the user interface contains any elements within the page corresponding to the element identifier identified from the event tracking information.

[0110] In step S530, if the second user interface exists, it is determined whether the second user interface has been exposed.

[0111] In this embodiment, when the tracking detection device determines that a second user interface exists (i.e., a user interface that corresponds to the page identifier identified in the tracking event information and contains the page element corresponding to the element identifier identified in the tracking event information), the tracking detection device can further determine whether the second user interface has been exposed, that is, determine whether there is a page exposure record corresponding to the second user interface.

[0112] Preferably, the data entry detection device can extract the value of the page exposure event counter from the global mapping table corresponding to the second user interface. If the value of the page exposure event counter is greater than 0, it indicates that the second user interface has been exposed. If the value of the page exposure counter is equal to 0, it indicates that the second user interface has not been exposed.

[0113] In step S540, if the second user interface does not exist or the second user interface is not exposed, the event information is determined to be abnormal event information.

[0114] In this embodiment, if it is determined that there is no second user interface (e.g., there is no user interface corresponding to the page identifier identified from the event tracking information, or there is a user interface corresponding to the page identifier identified from the event tracking information but the user interface does not contain the corresponding page elements), or there is a second user interface but the second user interface is not exposed, the newly received event tracking information can be determined to be abnormal event tracking information.

[0115] If the existence of the second user interface is confirmed and the second user interface has been exposed, it indicates that the newly received event tracking information is normal event tracking information.

[0116] This effectively prevents the logical error of "no page exposure but on-page element exposure", ensuring that the tracking data conforms to the basic business rule of "page exposure first, then on-page element exposure", thus guaranteeing the quality of the tracking data.

[0117] In some embodiments of this disclosure, after step S210, which identifies the page identifier and event type corresponding to the tracking event from the received tracking event information, the tracking detection method of this disclosure further includes steps S610 to S640. Please refer to [link / reference]. Figure 6 .

[0118] In step S610, if the event type is an element click event within the page, the corresponding element identifier is identified from the event tracking information.

[0119] In this embodiment, if the newly received event information corresponds to an element click event within the page, the event detection device can identify the corresponding element identifier from the event information.

[0120] In step S620, based on the page identifier and the element identifier, it is determined whether there exists a third user interface that corresponds to the page identifier and contains elements within the page corresponding to the element identifier.

[0121] In this embodiment, the event tracking detection device determines whether a third user interface exists that corresponds to the page identifier and contains elements within the page corresponding to the element identifier, based on the page identifier and element identifier identified from the event tracking information. The process for determining the third user interface can be referred to as follows: Figure 5 The implementation method described in step S520 will not be repeated here.

[0122] In step S630, if the third user interface exists, it is determined whether both the third user interface and the elements within the page have been exposed.

[0123] In this embodiment, if a third user interface is determined to exist, the event tracking device can further determine whether the third user interface and the elements within the page (corresponding to the element identifiers identified from the event tracking information) have been exposed.

[0124] Preferably, when a third user interface exists, the event tracking device can extract the values ​​of the page exposure event counter and the page element exposure counter (corresponding to the page element exposure counter identified from the event tracking information) from the global mapping table corresponding to the third user interface. If both the page exposure event counter and the page element exposure counter are greater than 0, it indicates that the third user interface and the page element (corresponding to the element identifier identified from the event tracking information) have been exposed.

[0125] If the page exposure event counter value is equal to 0, it means that the third-party user interface has not been exposed. If the element exposure counter value within the page is equal to 0, it means that the element within the page has not been exposed.

[0126] In step S640, if the third user interface does not exist or at least one of the third user interface and the page elements is not exposed, the event tracking information is determined to be abnormal event tracking information.

[0127] In this embodiment, if there is no third user interface (including no user interface corresponding to the page identifier identified from the event tracking information, or a user interface corresponding to the page identifier identified from the event tracking information but the user interface does not contain the corresponding page element), or if the third user interface exists but at least one of the third user interface or the page element corresponding to the element identifier identified from the event tracking information is not exposed, the newly received event tracking information can be determined to be abnormal event tracking information.

[0128] If a third user interface exists, and both the third user interface and the page element corresponding to the element identifier identified from the event tracking information have been exposed, then the newly received event tracking information can be determined to be normal event tracking information.

[0129] This effectively prevents logical errors such as "no page exposure or page element exposure but page element clicks", ensuring that the tracking data conforms to the basic business rule of "page exposure and page element exposure first, followed by page element clicks", thus guaranteeing the quality of the tracking data.

[0130] In some embodiments of this disclosure, after identifying the page identifier from the event tracking information, the event tracking detection method further includes: if the page identifier identified from the event tracking information is a null value or an invalid value, determining that the event tracking information is abnormal event tracking information.

[0131] The page identifier being null can mean that the page identifier does not exist, is null, is an empty string (such as " "), or the page identifier only contains whitespace characters.

[0132] An invalid page identifier can mean that the identified page identifier does not conform to the pre-defined naming rules, including non-standard format or unregistered values ​​(such as the inability to locate the corresponding user interface based on the identified page identifier).

[0133] In this embodiment, after identifying the page identifier from the event tracking information, the tracking detection device can perform compliance verification on the page identifier (such as checking whether the value of the page identifier is null, an empty string, or contains only blank characters, or checking whether the length of the page identifier conforms to the naming rules, whether the page identifier has been registered, etc.), thereby determining whether the page identifier is an empty value or an invalid value.

[0134] When it is determined that the page identifier identified from the event tracking information is empty or invalid, the event tracking information can be identified as abnormal event tracking information.

[0135] This effectively prevents the data tracking from becoming disconnected from the business scenario (i.e., the user interface) due to missing or invalid page identifiers, ensuring that each tracking event can be accurately associated with a specific business scenario.

[0136] In some embodiments of this disclosure, after determining that the event information is abnormal, the event detection method further includes steps S710 to S730. Please refer to [link / reference]. Figure 7 .

[0137] In step S710, the first embedding identifier of the embedding point that reported the abnormal embedding event information is identified from the abnormal embedding event information.

[0138] Among them, the tracking point identifier can be the identification information used to uniquely identify the tracking point and to track specific tracking point instances.

[0139] In this embodiment, after the event information is determined to be abnormal event information, the event detection device can identify the first event identifier of the event that reported the abnormal event information from the abnormal event information.

[0140] In step S720, the first tracking point identifier is compared with the second tracking point identifier contained in the target whitelist, wherein the second tracking point identifier is the tracking point identifier of the tracking point that is allowed to report abnormal tracking point event information.

[0141] The second tracking point identifier can be a tracking point identifier recorded in the target whitelist that is allowed to report abnormal tracking event information. Even if the tracking point corresponding to this second tracking point identifier triggers an anomaly detection (e.g., not meeting the target quantity rules, the event order of different event types not conforming to basic business rules (e.g., triggering the exposure of elements within the page even though the page has not been exposed), or the page identifier is missing or invalid), the alarm will be suppressed, and only silent recording will be performed. The establishment of the tracking point corresponding to this second tracking point identifier is usually based on specific, acceptable business logic or testing requirements.

[0142] In this embodiment, the tracking point detection device has a target whitelist that is pre-maintained. The target whitelist contains tracking point identifiers (i.e., second tracking point identifiers) of one or more tracking points that are allowed to report abnormal tracking point event information.

[0143] After a certain event is identified as an abnormal event, the event detection device can match the first event identifier identified from the abnormal event with each of the second event identifiers in the target whitelist to determine whether the two are the same.

[0144] In step S730, if the first embedding identifier and the second embedding identifier are different, an alarm message is generated and sent based on the abnormal embedding event information.

[0145] In this implementation, if it is determined that the first tracking point identifier is different from all the second tracking point identifiers, it indicates that the tracking point corresponding to the first tracking point identifier does not exist in the target whitelist. In this case, the tracking point detection device can generate corresponding alarm information based on the abnormal tracking point event information and send the alarm information according to the pre-set push rules (including push method and push timing). For example, the tracking point detection device can display a pop-up alarm on the interface of relevant personnel on the mobile terminal based on the alarm information, so that relevant personnel can be informed in a timely manner.

[0146] Preferably, the alarm information includes one or more of the following: event type, page identifier, or abnormal description corresponding to the abnormal event information.

[0147] If the first tracking point identifier is the same as a certain second tracking point identifier, it means that the tracking point corresponding to the first tracking point identifier is a tracking point that is allowed to report abnormal tracking point event information, and the abnormal tracking point event information is within the range of "known and acceptable". At this time, the tracking point detection device can skip the alarm step and record the abnormal tracking point event information.

[0148] Preferably, the event tracking device can record the information of this abnormal event tracking in the background log with an "exempted" status for future auditing.

[0149] In this way, by setting up a target whitelist, it is possible to effectively distinguish between real problems and compliance-specific scenarios, avoid false alarms for special business scenarios (such as backend services, preloading, etc.), and ensure the accuracy of alerts.

[0150] In some embodiments of this disclosure, after generating and sending alarm information based on the abnormal event information, the event detection method further includes steps S810 to S830. Please refer to [link / reference]. Figure 8 .

[0151] In step S810, the abnormal event information is recorded and the processing status is marked as unprocessed.

[0152] The processing status can be an identifier used to indicate the processing progress of abnormal event tracking. The processing status can include two states: "unprocessed" (i.e., newly discovered or unrepaired abnormality) and "processed" (i.e., the abnormality has been confirmed and repaired).

[0153] In this embodiment, the event tracking detection device can construct a structured anomaly record based on abnormal event tracking information. Preferably, the structured anomaly record may include one or more of the following: event identifier (such as event number), platform (Android or iOS), page identifier, anomaly description, update time, and processing status. The event tracking detection device can mark the processing status corresponding to the abnormal event tracking information as "unprocessed".

[0154] In step S820, the processing status of the abnormal event information is updated to "processed" according to the processing operation of the abnormal event information.

[0155] In this implementation, the event tracking device provides a management interface through which developers or testers can view exception records with a processing status of "unprocessed" and perform corresponding repairs or processing, such as submitting repair code in the code repository or marking them as "no processing required" based on business logic.

[0156] After detecting a processing operation for an "unprocessed" abnormal record, the tracking detection device updates the corresponding processing status to "processed".

[0157] In step S830, in response to the target triggering condition, a prompt message is generated and sent for abnormal event information with an unprocessed status.

[0158] The target triggering condition can be a pre-set rule for automatically triggering alerts for unprocessed exceptions. Preferably, the target triggering condition can include one or more of the following: time condition (e.g., 09:00 daily), quantity condition (e.g., the number of unprocessed exceptions exceeds a certain threshold), or manual triggering condition.

[0159] The notification message can be a structured notification sent to developers or relevant personnel. It may include a statistical summary of the unhandled exception, key exception details, and an assessment of its impact. This notification message can be sent through various channels (such as pop-ups, WeChat Work, and email).

[0160] In this embodiment, the tracking point detection device can continuously detect whether the target triggering condition is met. When the target triggering condition is met, the tracking point detection device generates a corresponding prompt message based on the abnormal record with the processing status of "unprocessed", and sends the prompt message through a pre-set push channel and push timing.

[0161] In this way, by establishing an anomaly record with processing status for each anomaly tracking point, scattered anomaly alarms are transformed into a queryable, statistical, and follow-up task list, providing a data foundation for subsequent problem handling.

[0162] Figure 9 This is a flowchart illustrating the page visibility detection process in another embodiment of the tracking point detection method disclosed herein. For example... Figure 9 As shown, the page visibility detection may include steps S901 to S909.

[0163] In step S901, the event tracking device receives event information from the mobile application.

[0164] In step S902, the event tracking device extracts the page identifier (i.e., UICODE) from the received event tracking information. This page identifier is a key field used to uniquely identify and locate the business page.

[0165] In step S903, the event tracking device searches the user interface at the Activity level and checks whether the PageID (i.e., page identifier) ​​of the user interface at each Activity level matches the page identifier extracted from the event tracking information.

[0166] In step S904, if the page identifier is equal to the PageID of the user interface of a certain active level, the corresponding user interface is found and the process proceeds to step S907; if the page identifier is not equal to the PageID of the user interface of any active level, the process proceeds to step S905 and continues the search in the user interface of the fragment level.

[0167] In step S906, if the page identifier is equal to the PageID of the user interface at a certain segment level, then the corresponding user interface is confirmed to have been found; if the page identifier is not equal to the PageID of the user interface at any segment level, then the corresponding user interface is determined not to have been found.

[0168] In step S907, after finding the corresponding user interface, it is determined whether the user interface is visible. If the user interface is visible, proceed to step S909, where the event tracking device determines that the event tracking information has passed the page visibility check and allows the event tracking information to be reported normally.

[0169] In step S908, when no corresponding user interface is found or the user interface is invisible, the event information is determined to be an abnormal event information, triggering an alarm and recording mechanism. Preferably, the event detection device can generate and send alarm information, such as pushing alarm information to relevant personnel. Simultaneously, the abnormal information is uploaded to the service backend for recording.

[0170] Figure 10 This is a flowchart illustrating the event timing detection process in another embodiment of the tracking detection method disclosed herein. For example... Figure 10 As shown, the event timing detection may include steps S1001 to S1007.

[0171] In step S1001, the tracking device maintains a global mapping table Map, which uses UICODE (i.e., page identifier) ​​as the key and is used to maintain the number of events of different event types related to each page identifier in real time.

[0172] In step S1002, the event tracking detection device can determine the corresponding event type from the received event tracking information. If the event type is an in-page element exposure event, the event timing detection is triggered.

[0173] In step S1003, the event tracking detection device performs event timing detection on the exposure events of elements within the page. Specifically, based on the page identifier and element identifier extracted from the event tracking information, the device queries the global mapping table (Map) to determine whether there exists a binding relationship between the extracted page identifier and element identifier. That is, it determines whether there exists a user interface that corresponds to the extracted page identifier and contains the element within the page corresponding to the extracted element identifier.

[0174] If the above binding relationship exists, the event tracking device extracts the number of page exposure events corresponding to the page identifier from the global mapping table Map, and determines whether the number of events is greater than 0 (i.e., whether the user interface has been exposed).

[0175] If the above binding relationship exists in the global mapping table Map, and the number of page exposure events corresponding to the page identifier extracted from the event tracking information is greater than 0, it indicates that the element exposure event within the page conforms to the basic business rules (i.e., "page exposure first, then element exposure within the page"), and proceed to step S1004, where the event tracking detection device allows the corresponding event tracking information to be reported normally.

[0176] If the above binding relationship does not exist in the global mapping table Map, or if the number of page exposure events corresponding to the page identifier extracted from the event tracking information is equal to 0, it means that the element exposure event within the page does not conform to the basic business rule of "page exposure first, then element exposure within the page". Then proceed to step S1005, and the event tracking detection device triggers the alarm and recording mechanism.

[0177] In step S1006, if the event type is determined to be an element click event within the page from the received event tracking information, the event tracking detection device will also trigger event timing detection.

[0178] In step S1007, the event tracking detection device performs event timing detection on the click events of elements within the page. Specifically, in addition to determining from the global mapping table (Map) whether there exists a binding relationship corresponding to the page identifier and element identifier extracted from the event tracking information, and determining whether the number of page exposure events corresponding to the page identifier is greater than 0, it also needs to determine whether the number of page element exposure events corresponding to the element identifier extracted from the event tracking information (which can be extracted from the global mapping table) is greater than 0 (i.e., determining whether the corresponding page element has been exposed).

[0179] If a corresponding binding relationship exists in the global mapping table (Map), and the number of corresponding page exposure events and in-page element exposure events are both greater than 0, it can be determined that the in-page element click event conforms to the basic business rule of "first page exposure, then in-page element exposure, then in-page element click". Step S1004 can then be initiated, and the event tracking device allows the corresponding event tracking information to be reported normally.

[0180] If there is no corresponding binding relationship in the global mapping table Map, or if the number of events for either the corresponding page exposure event or the element exposure event within the page is not greater than 0, it indicates that the element click event within the page does not conform to the basic business rules, and proceeds to step S1005, where the tracking detection device triggers the alarm and recording mechanism.

[0181] Figure 11 This is a block diagram of an embedded point detection device according to one embodiment of this disclosure. Figure 11 As shown, the embedded point detection device includes an identification module 111, a determination module 112, a verification module 113, and a processing module 114.

[0182] The identification module 111 is used to identify the page identifier and event type corresponding to the tracking event from the received tracking event information. The event type includes page exposure event, page element exposure event, or page element click event.

[0183] The determining module 112 is used to determine the number of events of each event type associated with the page identifier based on the event type of each tracking event associated with the page identifier.

[0184] Verification module 113 is used to perform quantity verification based on the number of events of each event type associated with the page identifier, and to determine whether the number of events of different event types conforms to the target quantity rule.

[0185] The processing module 114 is used to determine the event information as abnormal event information when the number of events of different event types does not meet the target number rule.

[0186] In some embodiments of this disclosure, after identifying the page identifier and event type corresponding to the tracking event from the received tracking event information, the processing module 114 is further configured to: determine whether there is a first user interface corresponding to the page identifier when the event type is a page exposure event; determine whether the first user interface is visible when the first user interface exists; and determine whether the tracking event information is abnormal tracking event information when the first user interface does not exist or the first user interface is invisible.

[0187] In some embodiments of this disclosure, determining whether a first user interface corresponding to the page identifier exists includes: searching for a first user interface corresponding to the page identifier in the user interface at the activity level based on the page identifier; and if the first user interface does not exist in the user interface at the activity level, searching for a first user interface corresponding to the page identifier in the user interface at the fragment level.

[0188] In some embodiments of this disclosure, after identifying the page identifier and event type corresponding to the tracking event from the received tracking event information, the processing module 114 is further configured to: identify the corresponding element identifier from the tracking event information when the event type is an in-page element exposure event; determine whether there exists a second user interface corresponding to the page identifier and containing an in-page element corresponding to the element identifier based on the page identifier and the element identifier; determine whether the second user interface has been exposed when the second user interface exists; and determine that the tracking event information is abnormal tracking event information when the second user interface does not exist or the second user interface has not been exposed.

[0189] In some embodiments of this disclosure, after identifying the page identifier and event type corresponding to the tracking event from the received tracking event information, the processing module 114 is further configured to: identify the corresponding element identifier from the tracking event information when the event type is an element click event within a page; determine whether there exists a third user interface corresponding to the page identifier and containing an element within a page corresponding to the element identifier based on the page identifier and the element identifier; determine whether both the third user interface and the element within the page have been exposed when the third user interface exists; and determine that the tracking event information is abnormal tracking event information when there is no third user interface or at least one of the third user interface and the element within the page has not been exposed.

[0190] In some embodiments of this disclosure, after identifying the page identifier from the event tracking information, the processing module 114 is further configured to: if the page identifier identified from the event tracking information is a null value or an invalid value, determine that the event tracking information is abnormal event tracking information.

[0191] In some embodiments of this disclosure, after determining that the event information is abnormal event information, the processing module 114 is further configured to: identify a first event identifier of the event that reported the abnormal event information from the abnormal event information; compare the first event identifier with a second event identifier included in the target whitelist, wherein the second event identifier is the event identifier of the event that is allowed to report abnormal event information; and generate and send alarm information based on the abnormal event information if the first event identifier and the second event identifier are not the same.

[0192] In some embodiments of this disclosure, after generating and sending alarm information based on the abnormal event information, the processing module 114 is further configured to: record the abnormal event information and mark the processing status as unprocessed; update the processing status of the abnormal event information to processed according to the processing operation of the abnormal event information; and generate and send a prompt message for the abnormal event information whose processing status is unprocessed in response to the target triggering condition.

[0193] This disclosure also provides an electronic device. Figure 12 A schematic diagram of the hardware implementation using the processing system is shown.

[0194] like Figure 12 As shown, the hardware structure of electronic device 1000 can be implemented using a bus architecture. The bus architecture can include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the hardware. Bus 1100 connects various circuits including one or more processors 1200, memory 1300, and / or hardware modules. Bus 1100 can also connect various other circuits 1400 such as peripherals, voltage regulators, power management circuits, external antennas, etc. Bus 1100 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Component (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one connection line is used in this figure, but this does not indicate that there is only one bus or one type of bus.

[0195] This disclosure also provides a readable storage medium storing a computer program that, when executed by a processor, is used to implement the methods described above. A "readable storage medium" can be any means that can contain a program for storage, communication, propagation, or transmission for use by or in conjunction with an instruction execution system, apparatus, or device. More specific examples of a readable storage medium include: an electrical connection with one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and portable read-only memory (CDROM), etc.

[0196] This disclosure also provides a computer program product, the methods of which can be implemented wholly or partially through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented wholly or partially as a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed, all or part of the processes or functions of this disclosure are performed.

[0197] Computer programs or instructions can be stored in a readable storage medium or transferred from one readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The readable storage medium can be any available medium capable of access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video optical disc; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or it can include both volatile and non-volatile types of storage media.

[0198] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0199] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus, electronic devices, and computer program products according to this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0200] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0201] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0202] In the description of this specification, the references to terms such as "one embodiment / mode," "some embodiments / modes," "example," "specific example," or "some examples," etc., refer to specific features, structures, or characteristics described in connection with that embodiment / mode or example, which are included in at least one embodiment / mode or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment / mode or example. Moreover, the specific features, structures, or characteristics described may be combined in any suitable manner in one or more embodiments / modes or examples. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments / modes or examples described in this specification, as well as the features of different embodiments / modes or examples.

[0203] Those skilled in the art should understand that the above embodiments are merely for illustrating the present disclosure and are not intended to limit the scope of the disclosure. Those skilled in the art can make other changes or modifications based on the above disclosure, and these changes or modifications still fall within the scope of the present disclosure.

Claims

1. A method for detecting embedded points, characterized in that, include: Based on the received event tracking information, the page identifier and event type corresponding to the event tracking event are identified from the event tracking information. The event type includes page exposure event, page element exposure event, or page element click event. Based on the event type of each tracking event associated with the page identifier, determine the number of events for each event type associated with the page identifier; Quantity verification is performed based on the number of events for each event type associated with the page identifier to determine whether the number of events for different event types conforms to the target quantity rule; as well as If the number of events of different event types does not conform to the target number rule, the event information is determined to be abnormal event information.

2. The embedded point detection method as described in claim 1, characterized in that, After identifying the page identifier and event type corresponding to the event from the received event information, the event detection method further includes: In the case that the event type is a page exposure event, determine whether there is a first user interface corresponding to the page identifier; When the first user interface exists, determine whether the first user interface is visible; and If the first user interface does not exist or the first user interface is invisible, the event tracking information is determined to be abnormal event tracking information.

3. The embedded point detection method as described in claim 2, characterized in that, Determining whether a first user interface corresponding to the page identifier exists includes: Based on the page identifier, search within the user interfaces of the activity hierarchy to see if a first user interface corresponding to the page identifier exists; and If the first user interface does not exist in the user interface of the activity level, search for the existence of a first user interface corresponding to the page identifier in the user interface of the fragment level.

4. The embedded point detection method as described in claim 1, characterized in that, After identifying the page identifier and event type corresponding to the event from the received event information, the event detection method further includes: When the event type is an in-page element exposure event, the corresponding element identifier is identified from the event tracking information; Based on the page identifier and the element identifier, determine whether there exists a second user interface that corresponds to the page identifier and contains elements within the page corresponding to the element identifier; If the second user interface exists, determine whether the second user interface has been exposed; and If the second user interface does not exist or is not exposed, the event tracking information is determined to be abnormal event tracking information.

5. The embedded point detection method as described in claim 1, characterized in that, After identifying the page identifier and event type corresponding to the event from the received event information, the event detection method further includes: When the event type is an element click event within the page, the corresponding element identifier is identified from the event tracking information. Based on the page identifier and the element identifier, determine whether there exists a third user interface that corresponds to the page identifier and contains elements within the page corresponding to the element identifier; In the presence of the third user interface, determine whether both the third user interface and the elements within the page have been exposed; and If the third user interface does not exist, or if at least one of the third user interface and the page elements is not exposed, the event tracking information is determined to be abnormal event tracking information.

6. The embedded point detection method as described in claim 1, characterized in that, The target quantity rules include: the number of page exposure events is greater than or equal to the number of element exposure events within the page; and the number of element exposure events related to the same element within the page is greater than or equal to the number of element click events within the page.

7. The embedded point detection method according to any one of claims 1-6, characterized in that, After determining that the event information is abnormal, the event detection method further includes: From the abnormal event information, identify the first event identifier of the event that reported the abnormal event; The first event tracking identifier is compared with a second event tracking identifier included in the target whitelist, wherein the second event tracking identifier is the event tracking identifier of an event tracking point that is allowed to report abnormal event tracking information; and If the first and second tracking point identifiers are different, an alarm message is generated and sent based on the abnormal tracking point event information.

8. The embedded point detection method as described in claim 7, characterized in that, After generating and sending alarm information based on the abnormal event information, the event detection method further includes: The abnormal event information is recorded and marked as unprocessed. Based on the processing operation of the abnormal event information, the processing status of the abnormal event information is updated to "processed"; and In response to the target triggering condition, generate and send a prompt message for abnormal event information with an unprocessed status.

9. An electronic device, characterized in that, include: The memory stores execution instructions; as well as A processor that executes the execution instructions stored in the memory, causing the processor to perform the embedding detection method according to any one of claims 1 to 8.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the embedding detection method according to any one of claims 1 to 8.

Images