Model-mapping tag table
This document describes only the fields specific to the Model-Mapping Tag 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. Wide and tall table structures
When a business records players' tag information, there are two record structures: Wide table and tall table
🔵 Wide table structure
The first column usually records the player's identifier, for example: player ID
The other data columns record tag data, and each column name is a tag name
| Player name | Skills | Combat power | Spending power | Activity level |
|---|---|---|---|---|
| Venom King | Pincer Fist | 1000 | Mid spender | Moderately active |
| Tiger Yin | Stealth Swift Blade | 800 | Big spender | Highly active |
Wide table example
🔵 Tall table structure
The first column usually records the player's identifier, for example: player ID
Tag names are recorded separately in one data column
Tag values are recorded in other data columns according to their type
| Player name | Tag Name | String tag value | Number tag value |
|---|---|---|---|
| Venom King | Skills | Pincer Fist | |
| Venom King | Combat power | 1000 | |
| Venom King | Spending power | Mid spender | |
| Venom King | Activity level | Moderately active | |
| Tiger Yin | Skills | Stealth Swift Blade | |
| Tiger Yin | Combat power | 800 | |
| Tiger Yin | Spending power | Big spender | |
| Tiger Yin | Activity level | Highly active |
Tall table example
2. Model-mapping configuration fields
2.1 Entity information
When you use tags, you need to specify the entity that the tags belong to
For example, tags for the user entity typically include registration time, payment frequency, login frequency, and so on
For example, tags for the device entity typically include activation time, Source Channel, ad group, and so on
When you configure model-mapping tags, specify the entity that the tag data belongs to and the column in the external data source that represents the entity
Entity fields preview
🔵 Entity
The entities that exist in the current project of the AE system. You can view and manage them in the Project Settings > Entity module
Or see the system manual: Project entities
⚠ Entities support only the String and Number types
Entity feature preview
🔵 User entities column
Select the data column in the data source that records the entity information
⚠ The type of the data column must match the selected entity. Options with a mismatched type are filtered out of the drop-down list automatically
2.2 Table type information
Select the table type based on the structure of the data source
🔵 Wide table
In wide table mode, there are no additional fields
Wide table fields preview
🔵 Tall table
In tall table mode, the Tag Name Column and Tag Value Column fields are added
Tall table fields preview
The following example shows how to configure the fields
| user_name | tag_name | str_value | num_value |
|---|---|---|---|
| Venom King | Skills | Pincer Fist | |
| Venom King | Combat power | 1000 | |
| Venom King | Spending power | Mid spender | |
| Venom King | Activity level | Moderately active | |
| Tiger Yin | Skills | Stealth Swift Blade | |
| Tiger Yin | Combat power | 800 | |
| Tiger Yin | Spending power | Big spender | |
| Tiger Yin | Activity level | Highly active |
Example data source in tall table mode
🔵 Tag Name Column
Select the column in the data source that represents the tag name. In the example above, the option is "tag_name"
🔵 Tag Value Column
Select the column in the data source that represents the tag value. In the example above, the option is "str_value"
⚠ Because tag values can be of many types, a data source may have multiple columns that record tag values. In this case, enter the column that holds most of the tag values. You can set the remaining tag values in the Asset List. For example, for the "Combat power" tag, enter "num_value" in Value Acquisition Method in the asset list
2.3 Date version information
The date version indicates whether a tag records a corresponding version for each historical date when it is calculated
a. Only current version
If each tag has only one latest recorded value and no historical date version information, it is treated as the "latest version", as shown in the following table
| user_name | skill | power |
|---|---|---|
| Venom King | Pincer Fist | 1000 |
| Tiger Yin | Stealth Swift Blade | 800 |
Example of tag values with only the current version
In this case, there are no additional fields. Select Only current version in Versions
Configuration example for only the current version
b. Historical and current versions
If each tag stores a corresponding tag value for each date
and the tag value on the latest date is the latest recorded result
then select Historical and Current Versions in Versions
| user_name | skill | power | tag_date |
|---|---|---|---|
| Venom King | Pincer Fist | 1000 | 2025-01-01 |
| Tiger Yin | Stealth Swift Blade | 800 | 2025-01-01 |
| Venom King | Pincer Fist | 1000 | 2025-01-02 |
| Tiger Yin | Stealth Swift Blade | 800 | 2025-01-02 |
Example of tags that contain date version values
In this case, configuration fields related to date information are added
Historical and current versions fields preview
🔵 Date column
Enter the data column in the data source that records date information. In the example above, it is "tag_date"
🔵 Date format
Enter this based on the format of the values in the date column. In the example above, it is "yyyy-MM-dd"
Here, yyyy is the four-digit year, MM is the two-digit month, and dd is the two-digit day
c. Only historical version
(Complex scenario) If a set of tags has historical versions, but the "latest version" and the "historical versions" are stored in 2 separate data sources
create model-mapping configuration A based on the data source of the "latest version", as described above
Then create model-mapping configuration B based on the data source of the "historical versions", and set the date version to Only historical version
Make sure the other fields and the asset lists of the two model-mapping configurations are the same
3. Model-mapping asset list configuration
3.1 Asset data types
Model-mapping tag assets support the following data types:
String, Number, Boolean, Time, List
For complex value acquisition scenarios, see Complex model-mapping configuration scenarios and SQL examples
Model-mapping tag data types preview
3.2 Expansion configuration for model-mapping tags
Model-mapping tags need the Value Time Zone field, which marks the time zone of the tag values. The default value is Local time (99)
Some features in the Analytics and Engage suites can only use tags with the same time zone configuration
Click [Apply to all tags] to apply the time zone value to all tags in the current asset list
Expansion configuration preview for model-mapping tags