DataFinder has added virtual project function since 4.10.0 version. When you create a project, you can create a project of type "virtual project". The virtual project can be associated with multiple ordinary projects that have been created. After the creation is completed, part of the metadata of the associated project will be merged in the virtual project, which can realize cross-application data aggregation and statistical analysis at low cost and efficiency. This article introduces you to the precautions and usage points of virtual projects.
The DataFinder virtual project essentially adds a query view to enable data "merging" across projects by associating multiple common projects.
tip
Only users with project management privileges in the privatization console have permission to create virtual projects.
Create a new project in Project Management in the Privatization Console Management Center, see activity details Create and Manage Projects.
After the creation is completed, the project defaults to a normal project. You need to find the corresponding project in the project list, click the Enter Product link under the Growth Analysis Platform, and set the project as a virtual project.
After you jump to the DataFinder's Access New Project page, configure the project as a virtual project.
Modify Modify the project type to virtual project.
Similar to normal projects, configure the project's caliber ID and time zone information.
Add an associated project and configure project priority.
Parameter | Configuration instructions |
|---|---|
Select Associated Items | The associated items that can be added are all ordinary items with applications and permissions. |
Highest priority project | Select a project with the highest priority in the drop-down box. When the attribute-related metadata in each project associated with the subsequent virtual project conflicts, this priority will be used for data display. tip Since the virtual project will "merge" and "split" the metadata of the associated project, that is, the metadata of multiple projects will be directly displayed in the virtual project, so there may be conflicts. For example, there are user attributes with the same name but inconsistent display names, data types, and states in multiple projects. When such conflicts occur, in the function parameters of the virtual project, such as user scrutiny, microscope-user attribute list, user lifecycle, etc., the data display of the highest priority project here will be displayed by default. |
After completing the above configuration, click OK to complete the virtual project creation and configuration.
Like a normal project, once created, you can license the virtual project to other users. Authorization actions for virtual projects are the same as for normal projects. You can open projects to user roles in the admin center. When creating/editing roles, you can choose whether you need to open projects to roles and grant roles viewing or administrative permissions for DataFinder projects. See activity details Create Roles and Authorize Roles.
After the virtual project is created, the virtual project will merge and split part of the metadata of the associated project in real time. Whether various types of metadata will be processed and the processing methods are shown in the following table.
tip
If you also enable the event tracking governance function, then when you click metadata in the virtual project, you will jump to the event tracking governance page of the highest priority project according to the project priority configured by the virtual project.
Metadata type | Whether to process associated project metadata | Virtual project data generation logic |
|---|---|---|
General event | Yes, the default is merge operation | The combined list of events is deduplicated for the general events in each associated project, and the value of the highest priority item is displayed when the parameters conflict. |
Event classification | No | The event category for the virtual item is empty and needs to be redefined |
Event properties | Yes, the default is merge operation | The merged event properties are deduplicated for the event properties in each associated project, and the value of the highest priority item is displayed when the parameters conflict. |
User attributes | Yes, the default is split operation | The user properties of a virtual project display the user properties of the highest priority project by default.
Example: There is 1 membership level attribute, level 1 in Normal Item: Project A and level 2 in Normal Item: Project B. |
Attribute dictionary | Yes, the default is merge operation | Merge processing, you can update in related projects, virtual projects do not support direct modification. |
Virtual event | Yes, the default is merge operation | Default to merge |
Virtual property | No | The default is empty, you need to create it yourself. |
Statistical caliber | No | Keep the default value. |
Custom session | No | Keep the default value. |
Session management | No | Keep the default value. |
Index management | No | The default is empty, you need to create it yourself. |
Circle event | No | Do not show |
Business dimension | No | Do not show |
Project meta-information | No | Follow the new virtual project configuration. |
Labeling/grouping | No | You need to create it yourself. |
Dashboard | No | You need to create it yourself. |
Permission | No | Virtual projects require independent allocation of project and data permissions. |
After creating the virtual project, you can enter the virtual project in the DataFinder console for data analytics and other operations. Some functions in the virtual project are not supported, and the unsupported function interface is not available or visible. The specific interface shall prevail.