DataWind supports direct integration with Volcano Engine DataFinder (hereinafter referred to as Finder). Behavior analytics data collected by Finder can be analyzed directly, or associated with business data for joint analysis, enabling deeper analytical insights. Prerequisites:
For private deployment of DataWind, the corresponding Finder must also be privately deployed. Both products need to be deployed in advance.
For SaaS DataWind, the corresponding Finder must be SaaS. You need to obtain a Finder account in advance, and the primary account used to apply for DataWind and Finder must be the same primary account.
Version requirements:
Private deployment: Finder must be version V4.3.0 or above, and DataWind must be version V2.50.0 or above.
SaaS: Finder must be the SaaS cloud-native version.
(1) Click to enter a specific project, click Data Preparation, find Data Connection in the dropdown list, and click Create Data Connection.
(2) Click Application Data Source on the left, and select "BytePlus Growth Analytics DataFinder".
(3) In the basic information for the data connection, select the corresponding application from the dropdown and click Save.
(4) Click the One-Click Create Dataset button. The system will automatically create the dataset.
(5) In the popup after successful creation, click "View here" to jump to the corresponding dataset and view details.
2.2 Application scope selectable during the data connection process #
For private deployment, there is a one-to-one relationship between projects. Only one application can be selected under each project space.
For the SaaS version, all applications created under the primary Volcano account can be selected.
On Finder, authorization controls the SQL custom query feature. Users authorized to use this feature can create Finder data connections on DataWind; users without authorization cannot.
In subsequent applications of the events table, the city field can be used directly when required.
Parsed fields in the events table
The event_params.xxx.yyy field, user_profiles.xxx field, and item_profiles.xxx.yyyy field will be parsed into multiple fields based on the actual reporting and definitions. The following is an example of parsing the event_params.xxx.yyy field.