In the previous data model, reported data directly generated assets such as events and user properties, which were then used to build assets such as reports and dashboards
Multi-source data integration wasn't supported, and assets for analysis scenarios couldn't be built before data was reported
Previous data model: reported data is used directly by analysis features
Super-layer model and reported data
The super-layer model adds an isolation layer between source data and the analysis features that use it, removing the strong dependency between the two
Adds the Model-Mapping User Property management feature, where you can view model-mapping user property data
Unlike event properties, each user property can have only 1 data source (data reporting or model mapping)
Model-mapping user property configuration must be enabled by a data administrator. Discuss and confirm this during the project kickoff phase, and then carry out the related operations
In the current version, model-mapping user properties are configured in Model-Mapping Configuration (Entity table)
When there's a new model-mapping configuration, the AE system automatically creates a super user property with the same name and associates it with the model-mapping user property
If a super user property with the same name or type is already used by other data, the automatic detection logic is interrupted. Confirm the scope of impact, and then use the Create and Associate Super User Property feature below to do it manually
