Model-mapping entity table
This document describes only the fields specific to the Model-Mapping Entity Table configuration and the logic specific to its asset list
For a general description of the model mapping assets configuration feature, see Model Mapping Assets Configuration
1. Basic information
- In the current version, the Model-Mapping Entity Table replaces AE's native User Table in model-mapping data scenarios
⚠ Because analysis model scenarios that involve the User Table are complex and data quality can greatly affect query performance, the data source and some fields must be configured with ops commands after you confirm them with your DataOps team
⚠ If your project data involves complex scenarios such as "mixing reported events with model-mapping events" or "drilling down across model-mapping user properties and model-mapping events", confirm the data status and the solution with ThinkingAI staff early in the integration
2. Model-mapping configuration fields
2.1 Entity information
⚠ The entity column must be configured with ops commands after you confirm it with your DataOps team. This field is used for join queries and drill-down with event data
Entity column field preview
2.2 Timeliness information
Optional. If the data source has a column that records when each row was updated, select that column name here
This field is used by features in the Engage suite
Update time field preview
3. Model-mapping asset list configuration
3.1 Asset data types
Assets of the model-mapping entity table support the following types:
String, Number, Boolean, Time, List, Row, Array Row
For complex value acquisition scenarios, see Complex model-mapping configuration scenarios and SQL examples
Model-mapping entity table data type preview