Web crawler recognition

You can configure the recognition rules of the crawler and the processing method after recognition on the web-side data. Details can be seen General Settings: Web Crawle Recognition.

Query trigger method

Configure the query triggering method when querying the data to be analyzed when using the analysis tool for data analytics, which takes effect for advanced analysis functions other than attribution analysis, path analysis, and business object analysis.
See configuration details General Settings: Query Trigger Method.

Internet Protocol Addresses Only Resolved Not Stored

When configuring analysis, whether it is necessary to keep the original data source of Internet Protocol Address data, after opening, the system only stores the location information after IP resolution, discards Internet Protocol Address data, and hides related attributes.

Multi-time zone configuration

Multi-time zone query is only effective for analysis functions, Dashboard, clustering, and basic analysis; the data results of user scrutiny and user labels are consistent with the application time zone.

Users scrutinize data retention time

Configure the user to scrutinize the storage duration of relevant data.

Multi-device user identification correction

Configure whether user identification correction for multiple devices needs to be enabled. After activation, the user behavior before login that occurred on different devices in the past 10 days will be correlated with the user behavior after login by day.

Connect with the corporate calendar

After opening, it will support "excluding weekends", "removing holidays" and "non-trading days" in event analysis; among them, holidays and trading days need to be maintained uniformly by the administrator in the system management-enterprise calendar.

Query mode

• Accuracy first: sacrificing a certain amount of query efficiency to ensure the accuracy of the data.
• Speed first: sacrificing a certain amount of data accuracy to ensure query efficiency.

Resource load balancing

After opening, the utilization of resources will be more balanced. However, when the main and standby delays are high, the accuracy of the data will be affected. It is recommended to open it when the amount of data is large and the requirements for data accuracy are not high.

The limited viewership of query tasks

Turn on the limit viewership of the query task switch, you can customize the limit viewership of conditions, after the configuration is completed, when the subsequent query task meets the limit viewership of the configuration, the query task will limit the number of concurrent queries.

Download limit

After it is turned on, you need to set an upper limit on the amount of data exported per download. The effective scope of this function includes event analysis, retention analysis, conversion analysis, distribution analysis, user clustering, and user ID download in the advanced analysis microscope function.
After the setup is complete, the page will prompt for download restrictions when downloading data later.

Event tracking check

Configure whether to manually accept event tracking events and event properties. After opening, events and properties need to be manually accepted before warehousing.

Number of common events

Configure the upper limit on the number of meta events, event properties (non-public), user properties, and event properties (public).

Event tracking input/online mode configuration

• Event tracking input method: Support configuration Add according to demand, add directly.
• Event tracking online method: support configuration audit online (need to specify the reviewer after checking), directly online.

Attribute encryption

Configure whether some sensitive attribute data needs to be encrypted. Attribute encryption achieves the purpose of data protection by encrypting sensitive attributes and controlling the visibility of attribute query results in the data stream processing stage.
With the switch turned on, click Configure Encryption and you can configure the properties that need to be encrypted in the pop-up sidebar.

1. In the drop-down box, select the event property or user property that needs to be encrypted and desensitized later, and in which application the property needs to be encrypted. Click Add when finished.

   warning

   Currently only encryption settings for custom properties are supported, not preset properties.

2. Once you're done adding, you can view all the added properties that require encryption in the list below.
   On subsequent data analytics queries, the corresponding attributes are encrypted and desensitized. The currently supported encryption method is AES encryption.
3. If you do not want to encrypt these attributes in the future, you can click the Delete button after the attribute to delete. After "Delete", the subsequent reported content will no longer be encrypted, and the historical encrypted information will not be affected.
4. If you are using OpenAPI for data query analysis and want to decrypt encrypted properties during OpenAPI query analysis, you can click Get Token above for subsequent property decryption.

No permission event

• Turn on switch (default): When using each function module of DataFinder, you can view all events when selecting events in the page drop-down box. If the current operating account has no event permissions, the interface will prompt for missing permissions, but you can view the event name, event description and other information of grey out.
• Off switch: When using each function module of DataFinder, when selecting an event in the drop-down box of the page, only the event with permission can be viewed. If there is no event permission, the corresponding event cannot be seen in the drop-down list.