ZZLily-based app data point burying method
The ZZLily data tracking framework solves the problems of large package size, performance impact, high cost, and low autonomy in existing data tracking frameworks for mobile banking apps. It achieves lightweight, flexible, efficient data collection and secure transmission, and is suitable for real-time data analysis in various environments.
Patent Information
- Application Number
- CN202511110670.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-08
- Publication Date
- 2025-11-21
AI Technical Summary
Existing data tracking frameworks in mobile banking apps suffer from issues such as large package size, performance impact, high cost, low autonomy, data leakage, and insufficient customization, especially in resource-constrained environments.
By adopting the ZZLily data tracking framework, we can achieve secure, customized, and efficient data collection through initialization, enabling full tracking, crash information collection, visual full tracking, app integration with H5, setting static and dynamic public attributes, event collection, and enabling SDK encryption. Combined with data storage and reporting strategies, we can achieve secure, customized, and efficient data collection.
It achieves lightweight, flexible, and efficient data acquisition, ensuring data accuracy and security, supporting real-time analysis, and is suitable for various environments. It reduces network bandwidth consumption and improves data collection efficiency and security.
Smart Images
Figure CN120994514A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The application relates to the field of Internet APP development, and in particular to an app data burying method based on ZZLily. BACKGROUND
[0002] With the rapid development of the Internet, the functions of mobile bank apps are becoming increasingly complex, and the interaction modes between users and products are becoming more and more diversified. In order to better understand user behaviors, optimize product design and improve user experience, an effective method is needed to collect and analyze user operation data on the product, and data burying technology emerges as the times require. By collecting detailed user behavior data, data analysis provides rich materials, helping enterprises understand user preferences, behavior paths, consumption habits and the like, thereby providing strong support for product strategies, operation strategies, market strategies and the like. Data burying can provide every operation detail of a user in a product, such as the user's stay time on a certain page, the number of clicks, the scrolling distance and the like.
[0003] Prior art solutions:
[0004] 1. A development engineer injects code statistics functions into a product developed by the company and builds a corresponding background query.
[0005] 2. Through integration of third-party data burying frameworks such as Lily statistics and Xueyue statistics.
[0006] 3. Purchase a third-party data burying platform, integrate an SDK, pay for access, and view burying data on the service platform.
[0007] 4. The third-party data burying framework is overused, and excessive nesting and unnecessary functions may result in a large package size, affecting the performance of the application and the loading speed, especially in an environment with limited resources.
[0008] 5. Paid access is required, the use cost is high, customization is weak, the self-determination right is low, and business demands may not be fully met due to some restrictions. The problem of data leakage is often encountered.
[0009] ZZLily is a lightweight, flexible and efficient data collection and burying framework, which not only has code burying functions, but also realizes user attribute setting, burying event collection, static public attributes, dynamic public attributes and full burying on the iOS side through related technologies in the runtime mechanism (Runtime). Users can accurately set the time of reporting burying data. Custom attributes and custom events can be conveniently set, and relatively rich data can be transmitted to the service side. ZZLily provides a good solution for enterprises to collect user behavior data individually.
[0010] Data quality: safe and reliable data collection technology and cross-end data integration capability, high framework maturity, stable performance.
[0011] Real-time: can process real-time data streams, very suitable for real-time analysis and real-time monitoring and other application scenarios. Support for real-time decision-making and business optimization.
[0012] Customization: on-demand tracking, customized personalized reporting, almost covering all data collection scenarios. Behavior data and business data can be integrated and reported.
[0013] Efficiency: using efficient data transmission protocols and strategies, it can minimize data transmission volume and transmission time while ensuring data accuracy, reduce network bandwidth usage, and improve data collection efficiency.
[0014] Fast integration: can be quickly integrated into existing projects, whether new applications or mature projects that have been put online, can be connected in a short time and start collecting data.
[0015] Exception handling: can effectively handle various possible exceptions, such as network failures and data transmission failures, to ensure that the tracking framework runs stably in various complex environments.
[0016] Lightweight: small size, code volume is simple, can run smoothly on devices with low performance. Fewer dependencies reduce the complexity of the project and stability problems caused by dependency conflicts or excessive dependencies. SUMMARY
[0017] In view of the above problems, the present application is proposed to provide a ZZLily-based app data tracking method to overcome the above problems or at least partially solve the above problems.
[0018] According to one aspect of the present application, a ZZLily-based app data tracking method is provided, which comprises:
[0019] ZZLily-based data tracking, at app startup, initialize ZZLily, start full tracking, start automatic collection of Crash information;
[0020] Start visual full tracking, start App through H5;
[0021] Start page exit time collection, start tracking Log log printing, set static public properties, dynamic public properties, activate event collection;
[0022] Start SDK encryption function;
[0023] Configure the network reporting policy, set the number of trigger entries to be reported, and set the trigger interval.
[0024] Optionally, the initialization of ZZLily specifically includes: setting configuration information using the ZZLConfigOptions class, setting the data receiving address, and initializing the ZZLily framework.
[0025] Optionally, enabling full event tracking specifically includes setting full event tracking using the autoTrackEventType method of ZZLConfigOptions.
[0026] Optionally, enabling full-scale visualization specifically includes:
[0027] Use the `enableVisualizedAutoTrack` method of `ZZLConfigOptions` to enable full-scale visualization of tracking points.
[0028] Optionally, enabling the App to connect to H5 specifically includes: using the enableJavaScriptBridge method of ZZLConfigOptions to enable the App to connect to H5.
[0029] Optionally, setting static public properties specifically includes:
[0030] Use the registerSuperProperties: method of ZZLAnalyticsSDK to register static public properties and set the channel name.
[0031] Optionally, the dynamic public attributes specifically include:
[0032] Use the registerDynamicSuperProperties: method of ZZLAnalyticsSDK to register dynamic public properties and set the login status.
[0033] Optionally, the activation event acquisition specifically includes: using the trackInstallation method of ZZLAnalyticsSDK to collect the attributes of the activation event.
[0034] Optionally, enabling the SDK encryption function specifically includes:
[0035] Use the enableEncrypt method of ZZLConfigOptions to enable SDK encryption, enhance the security of data tracking, and store and report data in encrypted form.
[0036] Optionally, the data embedding method further includes:
[0037] The data storage is used to cache the buried point data locally, and when the trigger interval flushInterval is greater than 15 seconds and the trigger number flushBulkSize is greater than 100, the reporting is triggered in batches.
[0038] If specific buried point data needs to be reported immediately, the flush method of ZZLAnalyticsSDK is called after the event is triggered to report immediately.
[0039] The application provides an app data buried point method based on ZZLily, and the data buried point method comprises the following steps: based on the data buried point of ZZLily, when the app is started, ZZLily is initialized, full buried point is started, and automatic collection of crash information is started; visual full buried point is started, App is connected to H5, page leaving time collection is started, buried point Log log printing is started, static public attributes and dynamic public attributes are set, and event collection is activated; the SDK encryption function is started; the reporting network strategy is set, the trigger number of reporting is set, and the trigger interval is set. The encryption of the buried point data strengthens the security of the buried point data.
[0040] The above description is only a summary of the technical scheme of the application, in order to more clearly understand the technical means of the application, the content of the specification can be implemented, and in order to make the above and other purposes, characteristics and advantages of the application more obvious and easy to understand, the specific embodiments of the application will be described below. BRIEF DESCRIPTION OF DRAWINGS
[0041] In order to more clearly illustrate the technical scheme of the embodiments of the application, the drawings needed in the embodiment description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the application, and those skilled in the art can obtain other drawings according to these drawings without creating any creative labor.
[0042] Figure 1 A flowchart of an app data buried point method based on ZZLily provided by the embodiments of the application. DETAILED DESCRIPTION
[0043] The exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided so that the present disclosure can be more thoroughly understood and the scope of the present disclosure can be accurately conveyed to those skilled in the art.
[0044] The terms "comprise", "comprising", "include", "including", "have" and "having" and any variations thereof in the Specification and Claims and the Appendices of the present application are intended to cover a non-exclusive inclusion, for example, a list of steps or units.
[0045] The technical solutions of the present application will be described in further detail below in combination with the drawings and examples.
[0046] As Figure 1 shown, an app data burying point method based on ZZLily includes:
[0047] Based on ZZLily data burying point, when the app starts, ZZLily is initialized, full burying point is started, automatic collection of crash information is started, visual full burying point is started, App is connected to H5, page leaving time collection is started, burying point Log log printing is started, static public properties and dynamic public properties are set, and event collection is activated. Start the SDK encryption function. Set the reporting network strategy, set the number of trigger reporting, and set the trigger interval.
[0048] Use the ZZLConfigOptions class to set the configuration information, set the data receiving address, and initialize the ZZLily framework.
[0049] Use the autoTrackEventType method of ZZLConfigOptions to set full burying point.
[0050] Use the enableVisualizedAutoTrack method of ZZLConfigOptions to start visual full burying point.
[0051] Use the enableJavaScriptBridge method of ZZLConfigOptions to start App connecting H5.
[0052] Use the registerSuperProperties: method of ZZLAnalyticsSDK to register static public properties and set the channel name.
[0053] Use the registerDynamicSuperProperties: method of ZZLAnalyticsSDK to register dynamic public properties and set the login state.
[0054] Use the trackInstallation: method of ZZLAnalyticsSDK to activate the properties of the event.
[0055] Using data storage, cache the buried point data locally, when the trigger interval flushInterval is greater than 15 seconds, and the trigger number flushBulkSize is greater than 100, report in batches and in batches.
[0056] If the specific buried point data needs to be reported immediately, the flush method of ZZLAnalyticsSDK can be called after the event is triggered to report immediately.
[0057] Use the enableEncrypt method of ZZLConfigOptions to enable the SDK encryption function, and enhance the security of the buried point data, and store and report the data in the form of ciphertext.
[0058] Beneficial effects:
[0059] Light, flexible, efficient data collection and buried point framework.
[0060] Accuracy and reliability of buried point data.
[0061] Encryption of buried point data to enhance the security of buried point data.
[0062] The above specific embodiments further illustrate the purpose, technical solutions and beneficial effects of the present application. It should be understood that the above is only a specific embodiment of the present application and is not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. within the spirit and principles of the present application should be included in the protection scope of the present application.
Claims
1. A data tracking method for apps based on ZZLily, characterized in that, The data embedding method includes: Based on ZZLily's data tracking, ZZLily is initialized when the app starts, full tracking is enabled, and automatic collection of crash information is enabled. Enable visualized full-tracking and enable integration between the App and H5; Enable page exit time collection, enable event log printing, set static and dynamic public attributes, and activate event collection. Enable SDK encryption; Configure the network reporting policy, set the number of trigger entries to be reported, and set the trigger interval.
2. The app data tracking method based on ZZLily according to claim 1, characterized in that, The initialization of ZZLily specifically includes: setting configuration information using the ZZLConfigOptions class, setting the data receiving address, and initializing the ZZLily framework.
3. The app data tracking method based on ZZLily according to claim 1, characterized in that, Enabling full event tracking specifically includes setting full event tracking using the autoTrackEventType method of ZZLConfigOptions.
4. The app data tracking method based on ZZLily according to claim 1, characterized in that, Enabling full-track visualization specifically includes: Use the `enableVisualizedAutoTrack` method of `ZZLConfigOptions` to enable full-scale visualization of tracking points.
5. The app data tracking method based on ZZLily according to claim 1, characterized in that, Enabling the integration of App and H5 specifically includes: using the enableJavaScriptBridge method of ZZLConfigOptions to enable the integration of App and H5.
6. The app data tracking method based on ZZLily according to claim 1, characterized in that, The setting of static public attributes specifically includes: Use the registerSuperProperties: method of ZZLAnalyticsSDK to register static public properties and set the channel name.
7. The app data tracking method based on ZZLily according to claim 1, characterized in that, The dynamic public attributes specifically include: Use the registerDynamicSuperProperties: method of ZZLAnalyticsSDK to register dynamic public properties and set the login status.
8. The app data tracking method based on ZZLily according to claim 1, characterized in that, The activation event collection specifically includes: using the trackInstallation method of ZZLAnalyticsSDK to activate the event's attributes.
9. The app data tracking method based on ZZLily according to claim 1, characterized in that, Enabling SDK encryption specifically includes: Use the enableEncrypt method of ZZLConfigOptions to enable the SDK encryption function, enhance the security of the data tracking points, and store and report the data in encrypted form.
10. The app data tracking method based on ZZLily according to claim 1, characterized in that, The data embedding method further includes: Use data storage to cache the event tracking data locally. When the trigger interval flushInterval is greater than 15 seconds and the number of triggers flushBulkSize is greater than 100, report the data in batches on a regular basis. If specific data points need to be reported immediately, the flush method of ZZLAnalyticsSDK will be called immediately after the event is triggered to report the data.