Page identifier tracking and behavior analysis method and device, equipment, medium and product

Abstract

The embodiment of the invention provides a page identifier tracking and behavior analysis method and device, equipment, a medium and a product. The page identification tracking method comprises the steps of detecting a current operation event triggered by a user, determining an original page identification of a page corresponding to the current operation event, judging whether the original page identification meets a tracking condition or not, and if yes, taking the original page identification as a target page identification corresponding to the current operation event; and if not, controlling the current operation event to inherit the target page identifier corresponding to the last operation event. The target page identifier is used for user behavior analysis. According to the technical scheme provided by the embodiment of the invention, the page identifier can be accurately tracked, so that the accuracy of user behavior analysis is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, device, medium, and product for page identifier tracking and behavior analysis. Background Technology

[0002] Analyzing user behavior within an application is a crucial foundation for optimizing application experience, improving service conversion rates, and achieving refined operations. To analyze user behavior, such as conducting user conversion funnel analysis, it's necessary to track page identifiers (i.e., action pages). Page identifier tracking refers to collecting a unique page type each time a user visits an action page and continuously recording these identifiers to analyze user behavior within the application.

[0003] Currently, page identifier tracking typically relies on embedded event tracking information within the page. For example, the corresponding page identifier is hard-coded into the event tracking information. When a user's action triggers an event tracking event, the page identifier tracking of the user's action on the page is achieved based on the configured page identifier.

[0004] However, with the evolution of application architecture, pages in applications are no longer isolated view units, but complex pages formed by nesting each other through hybrid application frameworks and containers. At this point, page identifiers based on tracking points may fail to reconstruct the user's true behavioral intent, thus affecting the accuracy of user behavior analysis, and urgently need improvement. Summary of the Invention

[0005] This application provides a method, apparatus, device, medium, and product for page identifier tracking and behavior analysis, which solves the problem of poor page identifier tracking accuracy in the prior art, affecting the accuracy of user behavior analysis.

[0006] Firstly, this application provides a page identifier tracking method, applied to a client, comprising: Detect the current operation event triggered by the user; Determine the original page identifier of the page corresponding to the current operation event; Determine whether the original page identifier meets the tracking conditions; If the conditions are met, the original page identifier will be used as the target page identifier corresponding to the current operation event; If this condition is not met, then the current operation event is controlled to inherit the target page identifier corresponding to the previous operation event; The target page identifier is used for user behavior analysis.

[0007] Secondly, embodiments of this application provide a behavior analysis method applied to a server, the method comprising: Obtain the target page identifier corresponding to the current operation event sent by the client; the target page identifier is the page identifier corresponding to the current operation event detected by the client. If the original page identifier of the page corresponding to the current operation event meets the tracking conditions, the target page identifier is the original page identifier. If the original page identifier of the page corresponding to the current operation event does not meet the tracking conditions, the page identifier inherits the target page identifier corresponding to the previous operation event. User behavior analysis is performed based on the target page identifier and the historical page identifiers of the acquired historical operation events.

[0008] Thirdly, this application provides a page identifier tracking device configured on a client, the method comprising: The event monitoring module is used to detect current operation events triggered by the user; The original identifier determination module is used to determine the original page identifier of the page corresponding to the current operation event; The judgment module is used to determine whether the original page identifier meets the tracking conditions; The target identifier determination module is used to, if satisfied, use the original page identifier as the target page identifier corresponding to the current operation event; The identifier inheritance module is used to control the current operation event to inherit the target page identifier corresponding to the previous operation event if the condition is not met; wherein, the target page identifier is used for user behavior analysis.

[0009] Fourthly, embodiments of this application provide a behavior analysis device configured on a server, the device comprising: The identifier acquisition module is used to acquire the target page identifier corresponding to the current operation event sent by the client. The target page identifier is the page identifier corresponding to the current operation event detected by the client. If the original page identifier of the page corresponding to the current operation event meets the tracking conditions, the target page identifier is the original page identifier. If the original page identifier of the page corresponding to the current operation event does not meet the tracking conditions, the page identifier inherits the target page identifier corresponding to the previous operation event. The behavior analysis module is used to perform user behavior analysis based on the target page identifier and the historical page identifiers of the acquired historical operation events.

[0010] Fifthly, this application provides a computing device, including a processing component and a storage component; the storage component stores a computing program; the computer program is invoked and executed by the processing component to implement the page identifier tracking method of the first aspect or the behavior analysis method of the second aspect.

[0011] Sixthly, this application provides a computer storage medium storing a computer program thereon. When the computer program is executed by a processing component, it implements the page identifier tracking method of the first aspect or the behavior analysis method of the second aspect described above.

[0012] In a seventh aspect, this application provides a computer program product, including a computer program or instructions, which, when executed by a processing component, implement the page identifier tracking method of the first aspect or the behavior analysis method of the second aspect described above.

[0013] This embodiment detects the current operation event triggered by the user, determines the original page identifier of the page corresponding to the current operation event, and uses the original page identifier as the target page identifier corresponding to the current operation event if the original page identifier meets the tracking conditions. If the tracking conditions are not met, the current operation event integrates the target page identifier of the previous operation event. In this embodiment, when tracking the page identifier of the corresponding page for a user-triggered operation event, the original page identifier is not directly used as the tracked target page identifier. Instead, tracking conditions are introduced. For page identifiers that do not meet the tracking conditions, such as pages that would affect the accuracy of user behavior analysis, their original page identifiers are not used. Instead, the page identifier corresponding to the previous operation event is inherited, thereby ensuring that the tracked page identifiers are specifically used for user behavior analysis, which helps improve the accuracy of user behavior analysis.

[0014] In other words, this embodiment is based on the user behavior analysis scenario and specifically sets up the above-mentioned page identifier tracking method, introducing tracking conditions to improve the accuracy of the tracked page identifiers, thereby ensuring the accuracy of the user behavior analysis results. This has never been achieved in the existing page tracking process, resulting in a new working paradigm.

[0015] These or other aspects of this application will become more apparent in the following description of the embodiments. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1This application provides a schematic diagram illustrating the operation page of its e-commerce application. Figure 2 A flowchart of one embodiment of a page identifier tracking method provided in this application is shown; Figure 3 A flowchart of one embodiment of the behavior analysis method provided in this application is shown; Figure 4 This application provides a system architecture diagram for implementing a page identifier tracking process. Figure 5 This application provides a flowchart of a method for behavioral analysis based on tracking page identifiers. Figure 6 This illustration shows a structural schematic diagram of one embodiment of a page identifier tracking device provided in this application; Figure 7 This illustration shows a structural schematic diagram of one embodiment of a behavior analysis device provided in this application; Figure 8 A schematic diagram of the structure of the computing device provided in this application is shown. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0018] It should be noted that, in the cases involving user information in the embodiments of this application, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse. In addition, the various models involved in this application (including but not limited to language models or large models) comply with relevant laws and standards.

[0019] Additionally, it should be noted that when user interaction operations or triggering operations are involved in the embodiments of this application, these operations include, but are not limited to, various interaction methods such as touch operations, gesture operations, voice operations, head movement operations, and eye movement operations. Touch operations include, but are not limited to, click operations, double-click operations, long-press operations, swipe operations, pinch operations, or mouse hover operations. Swipe operations include, but are not limited to, straight-line swipes and curved-line swipes.

[0020] It should be noted that the technical solutions in this application are applicable to virtual network environments, and the users described generally refer to "virtual users." Real users can register user accounts on the server through registration to obtain user identities in the network environment. The same user account can log in to the server through different types of clients, enabling the server to identify the same user.

[0021] Interactions between the server and the user can be based on user accounts. The data received or sent by the server to the user is also based on the user account; in reality, the client corresponding to the user account receives or sends data to the server. Furthermore, users can also communicate with each other through their user accounts. Here, "user" can refer to an individual or an organization, such as a company; this application does not impose specific restrictions.

[0022] For ease of reference, some terms that may be used in this application are defined as follows. It is understood that the terms and their respective definitions are not strictly limited to these definitions, and terms may be further defined through their use in this application: In this embodiment, the page for page identifier tracking refers to any visually interactive page within the application. As mobile application architecture evolves towards componentization and hybrid technology stacks, current application pages are no longer isolated view units, but rather complex pages formed by nested hybrid application frameworks and containers. This means that application pages can consist of container pages, content pages, and temporary user pages, and each page can be built based on a cross-platform hybrid application architecture. Specifically: A container page is a fixed page unit used to organize the navigation structure, containing preset trigger controls. For example, Figure 1 The e-commerce application shown includes a container page 11, in which preset trigger controls include "Live Stream", "Messages", "Shopping Cart", and "My Account".

[0023] A content page is a dynamic page unit used to carry application service content. Content pages can further include system service pages and system function pages. System service pages present the application's core business content, and may include, but are not limited to, service content detail pages and service content list pages. System function pages handle user account or system-level operations, and may include, but are not limited to, system login pages and system settings pages. For example, Figure 1 In the e-commerce application shown, content page 12 is a service list page, which displays introduction information of multiple service objects in a list format.

[0024] Based on the technical implementation method, content pages can be divided into pages rendered based on native application frameworks, i.e., native content (Native) pages, and pages rendered based on non-native application frameworks, i.e., cross-platform content pages, such as HTML5 (H5) pages and React Native (RN) pages.

[0025] Temporary user pages are short-lived page units used for user feedback, for example, Figure 1 The pop-up notification for promotional activities on page 12 can be considered a temporary user page.

[0026] To perform user behavior analysis on any application, it is necessary to track the page types that users interact with within the application. These page types are strings that uniquely identify a business scenario or page within the application, such as "Home" or "Details".

[0027] This embodiment tracks page identifiers by tracking the page identifier of the page corresponding to each user action event triggered by the application. Based on these page identifiers, user behavior analysis is then performed. Specifically, this can involve analyzing the actual operation path of the service conversion process. For example, in e-commerce applications, the user's order path can be analyzed, such as homepage, search service, service details, adding to cart, and placing an order. It can also analyze the trigger frequency of a specific operation in the system (such as adding to cart before placing an order).

[0028] Currently, page identifier tracking relies on embedded event tracking information within the page. This involves hard-coding corresponding page identifiers (e.g., "details") and event types (clicks) into the event tracking information. When a user's action triggers an event, the page identifier in the event tracking information is used to track the user's action on that page. However, in the complex pages described above, relying on event tracking information to track page identifiers may have the following drawbacks: 1. Data pollution issues exist. Currently, different trigger controls in the container page are usually hardcoded with a unified page identifier, such as "control". However, in actual application scenarios, the page identifiers corresponding to each trigger control in the container page may be meaningless and may also segment user behavior path analysis, affecting the accuracy of user behavior analysis results. For example, when a user enters the shopping cart page from the service details page by clicking the "shopping cart" control in the container page, the method of tracking page identifiers using the tracking mechanism will treat the page identifier of the "shopping cart" control (such as the control) as an intermediate page. The resulting user behavior path is "details → control → add to cart", that is, the real behavior path "details → add to cart" is segmented by the page identifier of the "control", which masks the real conversion path of the page, making the user behavior analysis results unreliable.

[0029] 2. Business process disruption issues exist. Temporary user pages (such as pop-ups, prompts, etc.) are incorrectly reported as independent page events and inserted into the business flow, causing discontinuity in the user behavior path. For example, when the content page is a service content details page, an "Add to Cart" pop-up appears on the details page. The user follows the pop-up prompt to enter the shopping cart and then pays. At this time, the tracking mechanism will treat the pop-up as a new page, and the resulting behavior path is "details → pop-up → add to cart → payment", thus causing the conversion rate analysis of the key service funnel "details → add to cart → payment" to fail.

[0030] 3. Ambiguous Traffic Attribution Issues. System function pages (such as login pages) use the same page identifier in behavior reporting (e.g., the login page's identifier is always "Login"), making it impossible to distinguish the business line from which the traffic originates. For example, when business line A and business line B call the same login page, the analysis data only displays "Login," resulting in the inability to independently calculate the user conversion rate for each business line and a loss of service-level granular analysis capabilities.

[0031] 4. Page identifier fragmentation across technology stacks. In applications developed using hybrid technologies (such as those using a mix of Native, RN, and H5 technologies), page identifiers cannot be automatically synchronized. For example, if the page identifier passing mechanism is not configured correctly in the RN container, the context state stream of the global page identifier will be lost. Developers need to manually write glue code for synchronization, which significantly increases development complexity and maintenance costs, and is prone to data inconsistency due to configuration oversights.

[0032] To address the aforementioned technical problems, this application provides a solution. The basic idea is to detect the current operation event triggered by the user, determine the original page identifier of the page corresponding to the current operation event, and if the original page identifier meets the tracking conditions, use it as the target page identifier for the current operation event. If the tracking conditions are not met, the current operation event integrates the target page identifier of the previous operation event. In this embodiment, when tracking the page identifier of the corresponding page for a user-triggered operation event, the original page identifier is not directly used as the tracked target page identifier. Instead, tracking conditions are introduced. For page identifiers that do not meet the tracking conditions, such as pages that would affect the accuracy of user behavior analysis, their page identifiers are not tracked. Instead, the page identifier corresponding to the previous operation event is inherited, thereby ensuring that the tracked page identifiers are specifically used for user behavior analysis and improving the accuracy of user behavior analysis.

[0033] This embodiment addresses the aforementioned issues by setting the original page identifiers of container pages that may cause data contamination, temporary user pages with broken business links, system function pages that lead to unclear traffic attribution, and non-native pages with page identifier fragmentation issues across technology stacks to be ineligible for tracking. In other words, these pages inherit the target page identifier from the previous operation tracking, thereby resolving the aforementioned issues and improving the accuracy of user behavior analysis.

[0034] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0035] Figure 2 This is a flowchart of an embodiment of a page identifier tracking method provided in this application. The technical solution of this embodiment can be executed by a client, which can be a client in an online system, or it can be other nodes independent of the client in the online system.

[0036] In practical applications, online systems typically consist of clients and servers, with the client and server connected via a network. The network provides the medium for communication between the client and server. Networks can include various connection types, such as wired and wireless communication links or fiber optic cables, etc.

[0037] The client in this embodiment can be user-facing, allowing users to perform interactive behaviors such as object searching and browsing, and to track the page identifiers of user operations and send them to the server for user behavior analysis.

[0038] The client can be a browser, an app (application), a web application such as an H5 (HyperText Markup Language 5) application, a mini-program (also known as a lightweight application), or a cloud application. This client can be deployed on electronic devices and depends on the device or certain apps on the device to run. Electronic devices can have displays and support information browsing, such as personal mobile terminals like smartphones, tablets, personal computers, desktop computers, smart speakers, smartwatches, etc.

[0039] The aforementioned server may include servers that provide various services, such as servers that perform user behavior analysis based on page identifiers tracked by the client, or servers that process interactive information sent by the client.

[0040] It should be noted that the server can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. The server can also be a server in a distributed system, or a server combined with blockchain. The server can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0041] Figure 2 The tracking method for the page identifier shown may include the following steps: S201, Detect the current operation event triggered by the user.

[0042] The current operation event can be an operation event generated in response to a user's action on the application's currently displayed page (including content pages, container pages, etc.).

[0043] Optionally, the client can detect that the user has triggered any operation on the application's currently displayed page and determine the corresponding operation event as the current operation event.

[0044] Specifically, this can involve pre-setting tracking points in the application's front-end code and using these tracking points to detect current operation events. For example, tracking points can be pre-embedded in key interactive elements of the user interface (such as buttons, links, page entry points, etc.) or business process nodes. When the user performs the corresponding triggered operation, the tracking point will automatically capture the operation and determine the current operation event, that is, detect the current operation event triggered by the user.

[0045] S202, Determine the original page identifier of the page corresponding to the current operation event.

[0046] In one possible implementation, the configuration of the page identifier in this embodiment can be implemented declaratively. Specifically, when defining page routes at the application layer, the developer explicitly declares the page identifier of each operable page of the application through metadata (such as annotations, configuration items, or routing table fields). In this scenario, performing this step may involve determining the page corresponding to the current operation event; obtaining the original page identifier of the page from the page route definition; wherein the original page identifier is pre-configured in the page route definition in the form of declarative metadata. Specifically, after detecting the current operation event triggered by the user in S201, it indicates that the page corresponding to the operation event has entered a critical node in the page lifecycle. At this time, the page corresponding to the current operation event can be determined first, and then the page identifier configured declaratively can be automatically read from the page route definition as the original page identifier of the page corresponding to the current operation event. Since the original page identifier determined in this embodiment is uniformly and reliably injected into the route definition by the system framework, it not only reduces the development coupling but also ensures the consistency and accuracy of the identifier, thereby achieving Inversion of Control (IoC).

[0047] In another possible implementation, after the event tracking automatically captures a user's triggered operation on the application, it generates event information corresponding to the current operation event and reports this event information through the event tracking interface; the event information includes at least a page identifier. Specifically, after the event tracking automatically captures a user's triggered operation on the application, it captures the original event data of the triggered operation, such as event type, page identifier, timestamp, and business parameters, generates event information for the current operation event, and reports the generated event information to the server through the event tracking reporting interface. The page identifier can be hard-coded into the event tracking information or obtained from the page routing definition using the method described above; there is no limitation on this. Correspondingly, this step of determining the original page identifier of the page corresponding to the current operation event includes: obtaining the page identifier from the event information as the original page identifier of the page corresponding to the current operation event. This improves the convenience and accuracy of determining the original page identifier. By obtaining the page identifier from the page route definition, the event reporting triggering mechanism is decoupled from the page business logic. The system-level navigation component autonomously constructs and reports event information at preset nodes in the page lifecycle based on the declarative metadata in the route configuration, thus realizing an automated event tracking mechanism based on inversion of control.

[0048] S203, determine whether the original page identifier meets the tracking conditions.

[0049] In this embodiment, the tracking conditions are mainly used to measure whether the page corresponding to the original page identifier is a preset category page. The preset category page includes at least one of the following: pages rendered by non-native application frameworks, and container pages, temporary user pages, and system function pages rendered by native application frameworks.

[0050] In one possible implementation, this embodiment can set a page identifier naming convention that meets the tracking conditions, and determine whether the original page identifier conforms to the page identifier naming convention. If it does, the tracking conditions are determined to be met; otherwise, the tracking conditions are determined not to be met. For example, if the page identifier starts with "Native", it is determined to conform to the page naming convention.

[0051] In another possible implementation, this embodiment can also determine whether the original page identifier is a preset identifier. The preset identifier is an identifier set during the application development phase for preset category pages in the application. The preset category pages include at least one of the following: pages rendered by a non-native application framework, and container pages, temporary user pages, and system function pages rendered by a native application framework. Specifically, if the original page identifier determined in S202 is a preset identifier, it is determined that the tracking condition is not met; if the original page identifier is not a preset identifier, it is determined that the tracking condition is met. For example, a preset identifier "#" can be set for each of the above-mentioned preset category pages in the application. If the original page identifier is "#", it indicates that the page currently triggered by the user is a preset category page and does not meet the tracking condition. This embodiment uses a preset identifier comparison method to determine whether the page identifier meets the tracking condition, which has the advantages of simple implementation, accurate judgment, and high performance.

[0052] S204 If satisfied, the original page identifier will be used as the target page identifier corresponding to the current operation event.

[0053] S205, if not satisfied, then control the current operation event to inherit the target page identifier corresponding to the previous operation event.

[0054] In this embodiment, the target page identifier is used for user behavior analysis.

[0055] Specifically, in this embodiment, if the original page identifier meets the tracking conditions, it is directly used as the target page identifier for tracking the current operation event. If the conditions are not met, the original page identifier is considered transparent, and the target page identifier corresponding to the previous operation event is retained as the target page identifier for tracking the current operation event. This is to prevent the original page identifiers of pages rendered by non-native application frameworks, as well as container pages, temporary user pages, and system function pages rendered by native application frameworks, from affecting the accuracy of page identifier tracking.

[0056] Based on the above embodiments, after controlling the current operation event to inherit the target page identifier corresponding to the previous operation event, the method further includes: responding to the inheritance operation, continuing to execute the operation of detecting the current operation event triggered by the user, or determining the inheritance identifier corresponding to the current operation event and sending the inheritance identifier as the target page identifier to the server for the server to perform user behavior analysis.

[0057] Specifically, one implementation of this embodiment is to directly return to continue executing the S201 operation in response to the inheritance operation of the target page identifier of the previous operation event, so as to avoid sending the target page identifier for the preset category page and affecting the accuracy of subsequent user behavior analysis. Another implementation is to determine the inheritance identifier for the current operation event. This can be a preset identifier (such as "#") as the inheritance identifier, or it can be an edit based on the inherited target page identifier, such as "target page identifier (inherited)" as the inheritance identifier. Then, the inheritance identifier is sent to the server as the target page identifier for the server to perform user behavior analysis, so as to provide more accurate page identifier tracking results and thus more accurate and comprehensive user behavior analysis. Correspondingly, after using the original page identifier as the target page identifier corresponding to the current operation event, the method further includes: sending the target page identifier to the server for the server to perform user behavior analysis. The target page identifier tracked in this embodiment can be sent to a dedicated server for user behavior analysis. The specific user behavior analysis method will be described in detail in subsequent embodiments.

[0058] This embodiment detects the current operation event triggered by the user, determines the original page identifier of the page corresponding to the current operation event, and uses the original page identifier as the target page identifier corresponding to the current operation event if the original page identifier meets the tracking conditions. If the tracking conditions are not met, the current operation event integrates the target page identifier of the previous operation event. In this embodiment, when tracking the page identifier corresponding to a user-triggered operation event, it does not directly use the original page identifier as the tracked target page identifier. Instead, it introduces tracking conditions. For page identifiers that do not meet the tracking conditions, such as pages that would affect the accuracy of user behavior analysis, their page identifiers are not tracked. Instead, the page identifier corresponding to the previous operation event is inherited, thus ensuring that the tracked page identifiers are specifically used for user behavior analysis, improving the accuracy of user behavior analysis.

[0059] This embodiment addresses the aforementioned issues by setting the original page identifiers of container pages that may cause data contamination, temporary user pages with broken business links, system function pages that lead to unclear traffic attribution, and non-native pages with page identifier fragmentation issues across technology stacks to be ineligible for tracking. In other words, these pages inherit the target page identifier from the previous operation tracking, thereby resolving the aforementioned issues and improving the accuracy of user behavior analysis.

[0060] In some embodiments, the current operation event may include page lifecycle events and business events. Page lifecycle events are events automatically triggered by the system or navigation framework when the page state changes, used to identify lifecycle nodes such as page creation, entering the foreground, exiting the background, or destruction. Business events are user-initiated operations with business semantics (such as clicking, submitting, playing, etc.). Both page lifecycle events and business events can occur in native pages, as well as pages implemented using cross-platform technologies such as H5 or React Native.

[0061] During user behavior data collection, different types of events differ significantly in semantics, purpose, and processing logic. For example, page lifecycle events (such as page entry and page exit) are mainly used to characterize user access paths and session structures, while business events (such as clicking "add to cart" and submitting an order) directly reflect the user's core interaction intent and conversion behavior. Mixing these two types of events in the same reporting channel not only complicates the backend parsing logic but may also affect the accuracy of user behavior analysis due to inconsistent field structures. Especially given the current widespread adoption of multi-technology stack hybrid development in clients (such as native pages, H5 pages, and RN pages coexisting), the sources of business events are more diverse. Therefore, this embodiment provides a clearly structured and responsibility-separated event tracking and reporting mechanism. Specifically, when the current operation event is a page lifecycle event, the event information of the page lifecycle event is reported through the first event tracking interface; when the current operation event is a business event, the event information of the business event is reported through the second event tracking interface.

[0062] This embodiment introduces a dual-channel event tracking architecture, using a first tracking interface (such as `reportScreenView`) and a second tracking interface (such as `reportEvent`) to report page lifecycle events and business events respectively. This is primarily based on the fundamental differences between the two in terms of semantics, purpose, and data structure. Page lifecycle events are used to construct user sessions and access paths, emphasizing page identification and temporal context; business events reflect users' proactive interaction behaviors in native, H5, or RN pages, requiring rich business parameters. Using the same reporting channel would lead to data structure chaos, increased backend parsing complexity, and easily cause inconsistencies in cross-platform event tracking. By using separate reporting channels, on the one hand, explicit differentiation of event types is achieved, facilitating on-demand routing, storage, and modeling by the backend system; on the other hand, a unified interface contract ensures that regardless of whether the business event originates from a native page, H5 container, or RN module, it can carry consistent contextual information (such as page identification, user ID, and timestamp) for standardized reporting. Thus, while improving data standardization and analysis efficiency, it also enhances the compatibility of the event tracking system with heterogeneous frontend technologies. This not only achieves data responsibility separation, facilitating targeted user behavior analysis such as path reconstruction and funnel analysis in the backend, but also ensures the consistency and maintainability of the tracking logic across multiple technology stacks, thereby significantly improving the accuracy, standardization, and efficiency of user behavior analysis.

[0063] Based on the aforementioned dual-channel event tracking architecture, this embodiment further includes: when the current operation event is a business event, determining whether the page corresponding to the current operation event is rendered by a native application framework; if so, controlling the current operation event to inherit the target page identifier corresponding to the previous operation event; if not, obtaining the page identifier in the event information as the original page identifier of the page corresponding to the current operation event. Specifically, based on the reasonable utilization of the differences in page context management mechanisms of different technology stacks, for pages rendered by native application frameworks, i.e., native pages are uniformly managed by the client navigation architecture, their lifecycle is clear, page identifiers are stable, and business events usually occur closely following page lifecycle events. Therefore, this embodiment can, when it is determined that the page corresponding to the current operation event is a native page rendered by a native application framework, allow the current operation event to inherit the target page identifier corresponding to the previous operation event, thereby avoiding the execution of the original page identifier and the judgment operation of whether the tracking conditions are met. This simplifies the page identifier tracking process and improves tracking efficiency while ensuring the accuracy of page identifier tracking. For non-native pages (such as H5 and React Native), which often run within a container (such as WebView), internal navigation is not visible to the Native layer. Page identifiers must be actively reported and explicitly carried by the front-end, and cannot rely on Native context caching. Therefore, this embodiment can, even if it is determined whether the page corresponding to the current operation event is rendered by a native application framework, continue to execute the operation of obtaining the page identifier from the event information as the original page identifier of the page corresponding to the current operation event. This implementation ensures the simplicity of native scenarios while guaranteeing the accuracy of page identifier context in non-native scenarios, balancing efficiency and reliability.

[0064] Optionally, since business events on native pages typically occur immediately following page lifecycle events, this embodiment can be for business events on native pages, where the reported event information does not carry a page identifier. In this case, the way to determine whether the page corresponding to the current operation event is rendered by the native application framework is to judge whether the event information reported by the business event contains a page identifier. If it does, it means that the page corresponding to the current operation event is not rendered by the native application framework; if it does not, it means that the page corresponding to the current operation event is rendered by the native application framework.

[0065] In some embodiments, after using the original page identifier as the target page identifier corresponding to the current operation event, this embodiment further includes: storing the target page identifier in a singleton object; the singleton object is created when the application starts, and the lifecycle of the singleton object is consistent with the lifecycle of the application process; controlling the current operation event to inherit the target page identifier corresponding to the previous operation event includes: controlling the current operation event to inherit the page identifier stored in the singleton object.

[0066] In this context, a singleton object refers to a context management component created when the client application starts, globally unique, and with a lifecycle consistent with the application process. This singleton object, acting as a process-level context maintenance object, persistently stores key behavioral context information such as the latest valid page identifier in the current session. Because it does not depend on the lifecycle of any specific page or component, even if the previous page disappears due to navigation, destruction, or memory reclamation, its associated page identifier can still be retained in the singleton object, effectively breaking the context gap problem caused by lifecycle isolation between traditional components. In this embodiment, based on setting up this singleton object, the target page identifier can be stored in the singleton object after the original page identifier is used as the target page identifier corresponding to the current operation event; when the current operation event needs to inherit the target page identifier of the previous operation event, it directly inherits the currently stored page identifier in the singleton object. This mechanism ensures that in complex scenarios such as rapid page switching, asynchronous callbacks, or component destruction, user behavior events can still be accurately associated with their logically belonging page, achieving context continuity and data consistency across component lifecycles.

[0067] Figure 3 The flowchart illustrates an embodiment of the behavior analysis method provided in this application. The technical solution of this embodiment can be executed by a server, which can be a server in an online system. Alternatively, it can be another node independent of the server in the online system. Figure 3 As shown, the behavior analysis method in this embodiment may include the following steps: S301, Get the target page identifier corresponding to the current operation event sent by the client.

[0068] The target page identifier is the page identifier corresponding to the current operation event detected by the client. If the original page identifier of the page corresponding to the current operation event meets the tracking conditions, the target page identifier is the original page identifier. If the original page identifier of the page corresponding to the current operation event does not meet the tracking conditions, the page identifier inherits the target page identifier corresponding to the previous operation event. It should be noted that the process of determining and sending the target page identifier has been described in the above embodiments and will not be repeated here.

[0069] S302, based on the target page identifier and the historical page identifiers of the acquired historical operation events, perform user behavior analysis.

[0070] Optionally, the historical operation events in this embodiment can be at least one consecutive operation event that occurred before the current operation event. For example, if the current operation event is an "order placement event," then the historical operation events at this time can include, but are not limited to, "service object search event," "service object details viewing event," and "add to cart event." The page identifier for the historical operation event can be determined by the client during previous page identifier tracking and has already been sent to the server; that is, the server has locally acquired and saved the historical page identifier for the historical operation event.

[0071] In this embodiment, the target page identifier serves as a core context field for user behavior events and can be used to drive multi-dimensional user behavior analysis. For example, one analysis method could be that a server-side log analysis tool, based on the target page identifier and historical page identifiers, classifies and aggregates current and historical operation events, identifying the frequency of user visits, dwell time, and interaction depth on the current and historical operation pages. Another analysis method could be to sequentially concatenate consecutive target page identifiers and historical page identifiers within the same user session to obtain a page identifier sequence, thereby constructing a complete user behavior path. Based on this user behavior path, advanced analysis tasks such as funnel conversion analysis (calculating the conversion rate from the product details page to the payment success page), path anomaly detection (identifying frequently bounced pages), and user segmentation (e.g., users who have completed an order and users who only browsed but did not add items to their cart) can be performed. Furthermore, this embodiment could also associate page identifiers with preset business tags (e.g., high-value pages, core conversion nodes) to give the analysis results clear business semantics, supporting service optimization, operational strategy formulation, and user experience evaluation.

[0072] Optionally, the server-side user behavior analysis process can be based on an intelligent analysis model. This intelligent analysis model can refer to a large-parameter model trained using massive amounts of data and powerful computing capabilities, a machine learning model with a complex structure, capable of processing massive amounts of data and completing various complex tasks, such as natural language processing, computer vision, and speech recognition. It can include Large Language Models (LLMs) or Multimodal Large Models (MLMs). The AI ​​large model discussed in this paper can be a pre-trained model, which is retrained through model fine-tuning to adapt to different processing tasks. This utilizes the powerful capabilities of the pre-trained model while also adapting to new data distributions, thus ensuring the model's generalization ability and reducing overfitting.

[0073] To further improve the accuracy of user behavior analysis results, in some embodiments, after the client inherits the target page identifier corresponding to the previous operation event from the current operation event, it determines the inherited identifier corresponding to the current operation event and sends the inherited identifier as the target page identifier to the server; and after using the original page identifier as the target page identifier corresponding to the current operation event, it sends the target page identifier to the server for user behavior analysis. At this time, the target identifier and historical page identifier received by the server may contain inherited identifiers, such as the preset identifier "#". In this scenario, the server's method for performing user behavior analysis based on the target page identifier and the historical page identifiers of the acquired historical operation events may include: constructing an original user behavior path according to the page identifier acquisition order, based on the target page identifier and the historical page identifiers of the acquired historical operation events; removing the inherited identifier from the original user behavior path to obtain the target user behavior path. Specifically, it may involve concatenating historical target identifiers belonging to the same user session as the target page identifier according to the event occurrence order to obtain the original user behavior path, and then removing the inherited identifier from the original user behavior path to obtain the target user behavior path. For example, if the original user behavior path is constructed as "Search Service - Details - # - Shopping Cart - # - Place Order", since the user behavior path carries the inheritance identifier "#", it is not conducive to analyzing the actual operation behavior path. Therefore, the inheritance identifier "#" can be removed to obtain the final target user behavior path "Search Service - Details - Shopping Cart - Place Order".

[0074] In a practical application scenario, such as Figure 4 This document illustrates a system architecture diagram for implementing page identifier tracking. Specifically, it includes three parts: declarative configuration, protocol engine driving, and analysis implementation. The declarative configuration part involves explicitly declaring the page identifier for each operable page of the application in the page route definition using metadata (such as annotations, configuration items, or routing table fields). For example, the page identifier for native content pages can be set according to the actual business content; for instance, the page identifier for the details page of a service object can be configured as "Details," which is the standard page identifier. The page identifier for native container pages can be configured as a unified preset identifier such as "#," which is a transparent page identifier and needs to inherit the page identifier of the previous operation event. Similarly, the page identifier for RN or H5 pages can also be configured as a unified preset identifier, such as "#," which can inherit the page identifier of the previous operation event through cross-site bridging. Specifically, the system detects the current operation event triggered by the user and retrieves the original page identifier, which is pre-configured declaratively for the page corresponding to the current operation event, from the page route definition.

[0075] The protocol-based engine can decouple component dependencies using a predefined identifier "#" set by the protocol. For container pages, RN, or H5 pages, there's no need to worry about their corresponding page types; they only need to declare "#", meaning the runtime automatically inherits the target page type from the previous operation event. Specifically, a protocol parser can determine if the original page identifier in the current operation event's declarative configuration is the predefined identifier "#". If not, the page identifier is updated, using the original page identifier as the target page identifier for the current operation event, and then the updated target page identifier is maintained using a global singleton object. If it is, the page identifier is inherited, meaning the current operation event inherits the target page identifier maintained by the global singleton object.

[0076] The analysis implementation part can be to send the target page identifier finally determined by the protocol engine driving phase for the current operation event to the log analysis tool, so as to perform user behavior analysis through the log analysis tool.

[0077] Next, combine Figure 5 The flowchart shown illustrates the method for tracking page identifiers and performing behavioral analysis. It describes the specific process of tracking page identifiers on the client side and sending the data to the server for user behavior analysis, including the following steps: The client responds to the user-triggered operation by detecting the current operation event (S501). If the current operation event is a page lifecycle event, it obtains the original page identifier of the page corresponding to the current operation event from the page routing definition (S502) and reports the event information of the page lifecycle event through the first tracking interface (such as reportScreenView), which may include the page name, page identifier, etc. (S503). It extracts the original page identifier from the reported event information and determines whether it is the preset identifier "#" (S504). If not, it updates the page identifier in the singleton object based on the original page identifier (S505) and uses the original page identifier as the target page identifier for tracking the current operation event (S507). If the original page identifier extracted from the reported event information is the preset identifier "#", it inherits the page identifier in the singleton object (S506) and sends the inherited identifier of the page identifier, such as the preset identifier "#", as the target page identifier (S507) to the server for user behavior analysis (S511).

[0078] If the current operation event is a business event, the event information of the business event is reported through the second tracking interface (such as report Event), which may include the event name and page identifier (S508). The page identifier can be obtained from the page route definition or hard-coded into the tracking information by the application developer. Next, it is determined whether the reported event information contains a page identifier (S509). If it does, it means that the page corresponding to the business event is a page rendered by a non-native application framework, and the target page identifier needs to be determined according to the method of S504-S5011 and sent to the server for user behavior analysis. If the page identifier is not contained, the currently maintained page identifier is read from the singleton object (S510) as the tracked target page identifier (S507), and then sent to the server for user behavior analysis (S511).

[0079] This embodiment proposes a highly cohesive and cross-scenario compatible user behavior context management method. Through a singleton-based centralized context hosting architecture, it breaks through the lifecycle limitations of traditional page-level states, constructing a session-level page identifier maintenance mechanism covering cross-components and cross-technology stacks, achieving unified control at the application level. It innovatively introduces a zero-intrusion automated inheritance mechanism, automatically deriving and normalizing page identifier states using metadata configuration and runtime protocol preset identifiers (such as "#"), completely replacing the hard-coded transmission of page identifiers. Combined with the Inversion of Control (IoC) design of navigation-as-annotation, it automatically extracts and updates page configurations based on the lifecycle hooks of the routing system, decoupling data collection responsibilities from specific business logic to the basic framework, achieving deep decoupling. Simultaneously, it establishes a standardized cross-scenario page identifier flow protocol, seamlessly compatible with native pages, container pages, temporary user pages, and hybrid technology stacks such as H5 and RN, ensuring the integrity and consistency of page identifier transmission under complex interaction paths.

[0080] By deeply integrating context page identifier management with the navigation framework and adopting a centralized context page identifier hosting mechanism, the quality and accuracy of user behavior analysis are significantly improved. On the one hand, through transparent transmission and automatic inheritance strategies, noisy data generated by container pages, temporary user pages, etc., are effectively filtered out, ensuring the continuity of conversion paths and the accuracy of dwell time statistics. On the other hand, dynamic scene identification and accurate business attribution of traffic sources for system function pages (such as login pages) are realized. At the same time, the context synchronization of multiple technology stacks such as Native, H5, and React Native is uniformly handled in a zero-intrusion and automated manner, transforming the originally scattered and error-prone manual maintenance into a centralized and reliable standard process, which greatly reduces the development and integration costs and maintenance complexity.

[0081] The detailed implementation methods and beneficial effects of each step in this embodiment have been described in detail in the foregoing embodiments, and will not be elaborated here.

[0082] It should be noted that some processes described in the above embodiments and accompanying drawings include multiple operations that appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order they appear in this document, or they may be executed in parallel. The sequence numbers of the operations are merely used to distinguish different operations and do not represent any execution order. Furthermore, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel. It should also be noted that the descriptions such as "first" and "second" in this document are used to distinguish different messages, devices, modules, etc., and do not represent a sequential order, nor do they limit "first" and "second" to different types.

[0083] Figure 6 A schematic diagram of an embodiment of a page identifier tracking device provided in this application is shown. The device is configured on a client and includes: The event monitoring module 601 is used to detect current operation events triggered by the user; The original identifier determination module 602 is used to determine the original page identifier of the page corresponding to the current operation event; The judgment module 603 is used to determine whether the original page identifier meets the tracking conditions; The target identifier determination module 604 is used to, if satisfied, use the original page identifier as the target page identifier corresponding to the current operation event; The identifier inheritance module 605 is used to control the current operation event to inherit the target page identifier corresponding to the previous operation event if the condition is not met; wherein, the target page identifier is used for user behavior analysis.

[0084] In some embodiments, the original identifier determination module 602 is specifically used to determine the page corresponding to the current operation event; obtain the original page identifier of the page from the page routing definition; the original page identifier is pre-configured in the page routing definition in the form of declarative metadata.

[0085] In some embodiments, the device further includes: an information reporting module, configured to report event information corresponding to the current operation event through a data entry interface; the event information includes a page identifier; the original identifier determination module 602 is further configured to obtain the page identifier in the event information as the original page identifier of the page corresponding to the current operation event.

[0086] In some embodiments, the current operation event includes page lifecycle events and business events. The information reporting module is specifically used to report the event information of the page lifecycle event through a first tracking interface when the current operation event is a page lifecycle event; and to report the event information of the business event through a second tracking interface when the current operation event is a business event.

[0087] In some embodiments, the apparatus further includes: a rendering mode determination module, configured to determine whether the page corresponding to the current operation event is rendered by a native application framework when the current operation event is a business event; the identifier inheritance module 605 is further configured to, if yes, the current operation event inherits the target page identifier corresponding to the previous operation event; correspondingly, the original identifier determination module 602 is specifically configured to, if no, obtain the page identifier in the event information as the original page identifier of the page corresponding to the current operation event.

[0088] In some embodiments, the event monitoring module 601 is further configured to continue performing the operation of detecting the current operation event triggered by the user in response to the inheritance operation; or, the device further includes a sending module configured to determine the inheritance identifier corresponding to the current operation event and send the inheritance identifier as a target page identifier to the server for the server to perform user behavior analysis; correspondingly, after the original page identifier is used as the target page identifier corresponding to the current operation event, the target page identifier is sent to the server for the server to perform user behavior analysis.

[0089] In some embodiments, the apparatus further includes: an instance management module, configured to store the target page identifier in a singleton object after using the original page identifier as the target page identifier corresponding to the current operation event; the singleton object is created when the application starts, and the lifecycle of the singleton object is consistent with the lifecycle of the application process; the identifier inheritance module 605 is specifically configured to control the current operation event to inherit the page identifier stored in the singleton object.

[0090] In some embodiments, the determination module 603 is specifically used to determine whether the original page identifier is a preset identifier; the preset identifier is an identifier set for preset category pages in the application during the application development stage; the preset category pages include at least one of the following: pages rendered by non-native application frameworks, and container pages, temporary user pages, and system function pages rendered by native application frameworks.

[0091] Figure 6 The page identifier tracking device can perform Figure 2The implementation principle and technical effects of the page identifier tracking method described in the illustrated embodiments will not be repeated here. The specific methods by which each module and unit of the page identifier tracking device in the above embodiments performs its operations have been described in detail in the embodiments related to this method, and will not be elaborated upon here.

[0092] Figure 7 This illustration shows a structural diagram of an embodiment of a behavior analysis device provided in this application, applied to a server. The device includes: The identifier acquisition module 701 is used to acquire the target page identifier corresponding to the current operation event currently sent by the client; the target page identifier is the page identifier corresponding to the current operation event detected by the client. If the original page identifier of the page corresponding to the current operation event meets the tracking conditions, the target page identifier is the original page identifier. If the original page identifier of the page corresponding to the current operation event does not meet the tracking conditions, the page identifier inherits the target page identifier corresponding to the previous operation event. The behavior analysis module 702 is used to perform user behavior analysis based on the target page identifier and the historical page identifiers of the acquired historical operation events.

[0093] In some embodiments, the behavior analysis module is specifically used to construct the original user behavior path based on the target page identifier and the historical page identifiers of the acquired historical operation events, according to the page identifier acquisition order; and to remove the inherited identifiers in the original user behavior path to obtain the target user behavior path.

[0094] Figure 7 The behavior analysis device can perform Figure 3 The implementation principle and technical effects of the behavior analysis method described in the illustrated embodiments will not be repeated here. The specific methods by which each module and unit of the behavior analysis device in the above embodiments performs its operations have been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0095] Figure 8 This is a schematic diagram of the structure of one embodiment of a computing device provided in this application. Figure 8 As shown, in practice, the computing device may include a storage component 801 and a processing component 802.

[0096] Storage component 801 is used to store computer programs and can be configured to store various other data to support operation on a computing device. Examples of this data include instructions for any application or method used to operate on the computing device, data structures, contact data, phone book data, messages, pictures, videos, etc.

[0097] Processing component 802, coupled to storage component 801, is used to execute computer programs in storage component 801 for implementing, etc. Figure 2 The page identifier tracking method shown can be used to implement the behavior analysis method shown in Figure 3.

[0098] Furthermore, such as Figure 8 As shown, the computing device may also include other components such as a communication component 803, a display component 804, a power supply component 805, and an audio component 806. Figure 8 The diagram only shows some components and does not mean that the device includes only these components. Figure 8 The components shown. Additionally... Figure 8 The components within the dashed box are optional, not mandatory, and their specific requirements depend on the product form of the computing device. The computing device in this embodiment can be a terminal device such as a desktop computer, laptop computer, smartphone, or IoT (Internet of Things) device, or a server-side device such as a conventional server, cloud server, or server array. If the computing device in this embodiment is implemented as a terminal device such as a desktop computer, laptop computer, or smartphone, it may include... Figure 8 The components within the dashed box; if the computing device in this embodiment is implemented as a conventional server, cloud server, or server array, etc., then it may not include... Figure 8 The component within the dashed box.

[0099] The processing component described above includes one or more processors to execute computer instructions to complete all or part of the steps in the method described above. Alternatively, the processing component may be implemented as one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the method described above.

[0100] The aforementioned storage components can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0101] The aforementioned communication component is configured to facilitate wired or wireless communication between the device housing the communication component and other devices. The device housing the communication component can access wireless networks based on communication standards, such as mobile communication networks, or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel.

[0102] The aforementioned display components may include a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation.

[0103] The aforementioned power supply components provide power to various components within the device in which they reside. These power supply components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device in which they reside.

[0104] The aforementioned audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC) configured to receive external audio signals when the device containing the audio component is in an operating mode, such as call mode, recording mode, or voice recognition mode. The received audio signals can be further stored in memory or transmitted via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals.

[0105] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement the steps in the above-described method embodiments. The computer-readable storage medium includes volatile or non-volatile components, or a combination thereof, and can be removable or non-removable. Examples of computer-readable storage media include, but are not limited to, phase-change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), flash memory or other memory technologies, CD-ROM, Digital Video Disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium. Accordingly, this application also provides a computer program product, which includes a computer program or instructions that, when executed by a processor, cause the processor to implement the steps in the above method embodiments. It should be understood that each step or combination of steps in the above method flow can be implemented by the computer program or instructions. Furthermore, these computer programs or instructions can be applied to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device, enabling the processor of the general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to function as an apparatus for implementing the corresponding functions in the above method embodiments.

[0106] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0107] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0108] Finally, it should be noted that the above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A page identifier tracking method, characterized in that, Applied to a client, the method includes: Detect the current operation event triggered by the user; Determine the original page identifier of the page corresponding to the current operation event; Determine whether the original page identifier meets the tracking conditions; If the conditions are met, the original page identifier will be used as the target page identifier corresponding to the current operation event; If this condition is not met, then the current operation event is controlled to inherit the target page identifier corresponding to the previous operation event; The target page identifier is used for user behavior analysis.

2. The method according to claim 1, characterized in that, The determination of the original page identifier corresponding to the current operation event includes: Determine the page corresponding to the current operation event; The original page identifier of the page is obtained from the page route definition; the original page identifier is pre-configured in the page route definition in the form of declarative metadata.

3. The method according to claim 1, characterized in that, Also includes: Report the event information corresponding to the current operation event through the data tracking interface; The event information includes a page identifier; The determination of the original page identifier corresponding to the current operation event includes: The page identifier in the event information is obtained as the original page identifier of the page corresponding to the current operation event.

4. The method according to claim 3, characterized in that, The current operation event includes page lifecycle events and business events, and the event information corresponding to the current operation event reported through the tracking interface includes: If the current operation event is a page lifecycle event, the event information of the page lifecycle event is reported through the first tracking point interface; If the current operation event is a business event, the event information of the business event is reported through the second tracking point interface.

5. The method according to claim 4, characterized in that, Also includes: If the current operation event is a business event, determine whether the page corresponding to the current operation event is rendered by the native application framework; If so, then control the current operation event to inherit the target page identifier corresponding to the previous operation event; Accordingly, obtaining the page identifier from the event information as the original page identifier of the page corresponding to the current operation event includes: If not, then the page identifier in the event information is obtained as the original page identifier of the page corresponding to the current operation event.

6. The method according to any one of claims 1-5, characterized in that, After controlling the current operation event to inherit the target page identifier corresponding to the previous operation event, the method further includes: In response to the inheritance operation, continue to execute the operation of detecting the current operation event triggered by the user, or determine the inheritance identifier corresponding to the current operation event and send the inheritance identifier as the target page identifier to the server for the server to perform user behavior analysis; Accordingly, after using the original page identifier as the target page identifier corresponding to the current operation event, the method further includes: The target page identifier is sent to the server for user behavior analysis.

7. The method according to any one of claims 1-5, characterized in that, After using the original page identifier as the target page identifier corresponding to the current operation event, the method further includes: The target page identifier is stored in a singleton object; the singleton object is created when the application starts, and the lifecycle of the singleton object is consistent with the lifecycle of the application process; The target page identifier corresponding to the current operation event inheriting the previous operation event includes: The current operation event inherits the page identifier stored in the singleton object.

8. The method according to any one of claims 1-5, characterized in that, The determination of whether the original page identifier meets the tracking conditions includes: Determine whether the original page identifier is a preset identifier; the preset identifier is an identifier set during the application development phase for preset category pages in the application. The preset category pages include at least one of the following: pages rendered by non-native application frameworks, and container pages, temporary user pages, and system function pages rendered by native application frameworks.

9. A behavior analysis method, characterized in that, Applied to the server side, the method includes: Obtain the target page identifier corresponding to the current operation event sent by the client; the target page identifier is the page identifier corresponding to the current operation event detected by the client. If the original page identifier of the page corresponding to the current operation event meets the tracking conditions, the target page identifier is the original page identifier. If the original page identifier of the page corresponding to the current operation event does not meet the tracking conditions, the page identifier inherits the target page identifier corresponding to the previous operation event. User behavior analysis is performed based on the target page identifier and the historical page identifiers of the acquired historical operation events.

10. The method according to claim 9, characterized in that, The user behavior analysis based on the target page identifier and the historical page identifiers of the acquired historical operation events includes: Based on the target page identifier and the historical page identifiers of the acquired historical operation events, the original user behavior path is constructed according to the page identifier acquisition order. Remove the inheritance identifier from the original user behavior path to obtain the target user behavior path.

11. A page identifier tracking device, characterized in that, Configured on a client, the device includes: The event monitoring module is used to detect current operation events triggered by the user; The original identifier determination module is used to determine the original page identifier of the page corresponding to the current operation event; The judgment module is used to determine whether the original page identifier meets the tracking conditions; The target identifier determination module is used to, if satisfied, use the original page identifier as the target page identifier corresponding to the current operation event; The identifier inheritance module is used to control the current operation event to inherit the target page identifier corresponding to the previous operation event if the condition is not met; wherein, the target page identifier is used for user behavior analysis.

12. A behavior analysis device, characterized in that, Configured on the server side, the device includes: The identifier acquisition module is used to acquire the target page identifier corresponding to the current operation event sent by the client. The target page identifier is the page identifier corresponding to the current operation event detected by the client. If the original page identifier of the page corresponding to the current operation event meets the tracking conditions, the target page identifier is the original page identifier. If the original page identifier of the page corresponding to the current operation event does not meet the tracking conditions, the page identifier inherits the target page identifier corresponding to the previous operation event. The behavior analysis module is used to perform user behavior analysis based on the target page identifier and the historical page identifiers of the acquired historical operation events.

13. A computing device, characterized in that, This includes processing components and storage components; The storage component stores a computer program; the computer program is invoked and executed by the processing component to implement the page identifier tracking method as described in any one of claims 1-8, or to perform the behavior analysis method as described in any one of claims 9-10.

14. A computer-readable storage medium, characterized in that, It stores a computer program, which, when executed by a processing component, implements the page identifier tracking method as described in any one of claims 1-8, or performs the behavior analysis method as described in any one of claims 9-10.

15. A computer program product, characterized in that, It includes a computer program or instructions that, when executed by a processing component, implement the page identifier tracking method as described in any one of claims 1-8, or implement the behavior analysis method as described in any one of claims 9-10.

Images