You need to enable JavaScript to run this app.
Growth Analysis (Privatization)

Growth Analysis (Privatization)

Copy page
Download PDF
Project Management
SDK Settings
Copy page
Download PDF
SDK Settings

Note: This function is only supported by privatization V4.4.0 and above

1. Overview

1.1 Scenarios of use

Through the SDK setting function, you can adjust the SDK collection items without sending the version on the client side; Android and iOS need to be upgraded to 6.15.0 and above versions, web needs to be upgraded to 5.1.8 and above versions, and Mini Program needs to be upgraded to 2.10.1 and above versions.
User-oriented: SDK development.
Specific controllable items include: full event tracking acquisition switch, A/B experimental switch, prohibit reporting event configuration list, real-time reporting event configuration list, event tracking report timing/reporting frequency, turn off sensitive field collection.

2. Function introduction

2.1 Settings Description

Function entrance: Project Center > Project Management > SDK Settings.
Image

2.1.1 Full event tracking

  • Open: Indicates that the full event tracking event is allowed to be reported; note that if the SDK turns off the full event tracking collection locally (on the end), the full event tracking event cannot be reported even if the switch on the platform page is turned on. For full event tracking switch configuration details, please refer to the SDK access documentation of each end.
  • Close: Indicates that full event tracking events are no longer reported.

2.1.2 A/B experiment

  • On: Indicates that the A/B experiment-related event tracking and triage functions are in effect; note that if the SDK turns off the experiment function locally (on the end), the experiment cannot be enabled even if the switch on the platform page is turned on. For details of the A/B experimental switch configuration at each end, please refer to the SDK access documentation at each end.
  • Off: Indicates that the A/B experiment-related event tracking and streaming functions are not effective.

2.1.3 Prohibited from reporting incidents

This function is used to intercept useless event tracking reports. You can set the events in the "disabled" and "blacklist" states to prohibit reporting, or customize the event range, and the number of custom events is limited to 100.

2.1.4 Real-time reporting of incident lists

This function is used to configure event tracking reports with high real-time requirements. You can customize the event range, and the number of custom events is limited to 100.
Note: When the request volume is too large and the server level resources are tight, the real-time event reporting may fail. At this time, the request will be downgraded to a normal event batch report.

2.1.5 Event tracking report

You can set the event tracking batch reporting timing to adjust the reporting frequency:
Method 1: According to the time interval, the minimum is 5 seconds, and the maximum is 300 seconds.
Method 2: According to the number of local cumulative logs, report to a specific number; minimum 50, maximum 10,000;

tip

Each end of the DataFinder has a default reporting mechanism and the timing of triggering reporting. After the console is configured here, the configuration result will prevail. See the default reporting mechanism DataFinder Data Access Overview.

2.1.6 Turn off sensitive field acquisition

This function is used to turn off the collection of sensitive fields for specific devices. See the page display for the fields that support closing. You can also turn off sensitive field collection on the terminal. For details of sensitive field switch configuration on each terminal, please refer to the SDK access documentation of each terminal.

2.1.7 Estimated reporting time

This function is used to specify the approximate time interval for the SDK to send data to the server after the user triggers an event. This time interval can be adjusted based on factors such as network conditions, priorities, and performance to ensure the efficiency and accuracy of data reporting.
For example, for data with low materiality requirements, a longer reporting interval can be set to reduce the impact of client performance and network traffic consumption; for data with high performance requirements, a shorter reporting interval can be set so that the data can be sent to the server for processing as soon as possible.

2.2 Description of operation authority

The function is only open to administrators by default. If you need to adjust the SDK settings, it is recommended to contact your administrator or enable administrative permissions for you.

Last updated: 2026.08.25 11:49:35