Model-mapping event table
This document describes only the fields specific to the Model-Mapping Event 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
The AE standard event table data structure contains some key data columns, which affect how features of analysis models can be used later
For example: $part_event, #event_time, $part_date, and so on
The other columns are custom event properties, such as channel, role_level, and amount in the sample table below
| #user_id | $part_event | #event_time | #zone_offset | $part_date | channel | role_level | amount |
|---|---|---|---|---|---|---|---|
| Zhang San | login | 2025-10-29 10:25:59 | 8 | 2025-10-29 | Douyin | ||
| Li Si | level_up | 2025-10-09 04:00:48 | 8 | 2025-10-09 | 47 | ||
| Wang Wu | payment | 2025-10-20 10:29:16 | 0 | 2025-10-20 | 70 | 166 | |
| Ma Liu | battle_win | 2025-10-08 15:56:31 | -4 | 2025-10-08 | 83 |
AE event table sample
When you set an external data source as a model-mapping event table, convert it to the AE standard format and set it up in the model-mapping configuration fields
Other columns used as event properties can be set up in the asset list as your business requires
⚠ Columns already set in the model-mapping configuration fields don't need to be set again as assets in the asset list
| uid | action | ts | timezone | pt | channel | role_level | amount |
|---|---|---|---|---|---|---|---|
| Zhang San | login | 2025-10-26 04:21:54 | 8 | 2025-10-26 | Douyin | ||
| Li Si | level_up | 2025-10-09 15:22:26 | 8 | 2025-10-09 | 77 | ||
| Wang Wu | payment | 2025-10-15 06:28:51 | 0 | 2025-10-15 | 54 | 166 | |
| Ma Liu | battle_win | 2025-10-21 19:23:40 | -4 | 2025-10-21 | 71 |
External data source sample
2. Model-mapping configuration fields
2.1 Entity information
Set the column in the data source that's equivalent to #user_id in the AE event table. In the sample data, it's uid
For data unrelated to user behavior, such as ad attribution events and aggregated data events, leave this field blank
⚠ 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
Entity column_preview
2.2 Event name information
Set how the information equivalent to $part_event in the AE event table is read from the data source
🔵 Read column value
Directly select the column in the data source that records the event name
In the sample data, it's
action⚠ We recommend making this column a partition key in the data source to improve query performance
Event name_read column value preview
🔵 Constant
If the data source contains data for only 1 event and has no column that records the event name, select Constant here
Also enter the corresponding name in the event name field, such as user_login
Event name_constant preview
2.3 Event time information
Set how the information equivalent to #event_time in the AE event table is read from the data source
🔵 Read column value
Directly select the column in the data source that records the event time. Its data type must be Time
In the sample data, it's
ts
Event time_read column value preview
🔵 custom SQL
If the data source records the event time as a string, a numeric timestamp, or in another form, convert it to the Time type with an SQL function
For example: try_cast( "ts" as timestamp )
For other complex scenarios, see Complex model-mapping configuration scenarios and SQL examples
Event time_custom SQL preview
2.4 Event time zone information
Set how the information equivalent to #zone_offset in the AE event table is read from the data source
🔵 Read column value
Directly select the column in the data source that records the event time zone. Its data type must be Number
In the sample data, it's
timezone
Event time zone_read column value preview
🔵 Constant
If all data in the data source comes from the same time zone, such as logs collected by servers in UTC+8, set the corresponding time zone here
Event time zone_constant preview
🔵 custom SQL
If the data source records time zone information in another form, convert it to the Number type with an SQL function
For example: try_cast( substr( 'UTC+8' , 4 , 9 ) as double ) /* Replace 'UTC+8' with the column name when you use it */
For other complex scenarios, see Complex model-mapping configuration scenarios and SQL examples
Event time zone_custom SQL preview
2.5 Data partitioning method
Set how the information equivalent to $part_date in the AE event table is read from the data source
🔵 Date column
Directly select the column in the data source that records the date partition. Its data type must be String
In the sample data, it's
pt⚠ We recommend making this column a partition key in the data source to improve query performance
🔵 Custom Pushdown Logic
If the data source is partitioned in another way, use custom pushdown logic: take the date range selected in the frontend at query time as a variable, and write the corresponding pushdown SQL
For details, see Complex model-mapping configuration scenarios and SQL examples
3. Model-mapping asset list configuration
In the model-mapping event table configuration, there are three kinds of assets to configure: event properties, events, and event-property matching relationships. Configure each of them separately
Preview of the asset types in the model-mapping event table
3.1 Event properties
3.1.1 Asset data types
Model-mapping event property assets 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 event property data type preview
3.1.2 Super properties
When you configure model-mapping event properties, you can set a property as a super property in Expansion configuration
After that, the property is matched with all events in the current configuration (other model-mapping configurations aren't affected)
Super property preview for model-mapping event properties
3.2 Events
⚠ Before you use Scan Assets for event assets, finish configuring Event name information in the configuration fields
After the scan, the first column of the asset list shows the scanned event names. You can then modify the display names and descriptions of the output events
- If an output event is the same as the original value, leave Original event list blank (payment in the figure below)
- To merge multiple events into one event, enter the list of events to merge using English parentheses and single quotes (battle_end in the figure below)
- To change the output name of a single event, enter a list that contains only 1 event in the original event list (activity_attend in the figure below)
Event asset configuration preview
3.3 Event-property matching relationships
In analysis models, after you select event A, you can further filter or calculate by property B of that event, and the unrelated property C doesn't appear
This logic is called the "event-property matching relationship". It helps business users identify the associations within event data and work more efficiently
Preview of event-property relationships in the AE system
In the AE system, for data ingested through reporting, the relationship between each event and its properties can be parsed during ETL
For model-mapping data, however, the system can't automatically identify the relationships in external data sources, so you need to specify them in the configuration
Event-property relationship configuration preview
When you configure them, you can first click Download full mapping relationship table. The system reads the configured event properties and event names and generates full mapping relationship data. Alternatively, click One-click setting for full mapping to set all event properties and events as fully mapped directly
Then delete the rows you don't need from the data and export a CSV file in UTF-8 format (How do I export a CSV file in UTF-8 format?)
| Output event name | Output Property Name |
|---|---|
| event_a | prop_a |
| event_a | prop_b |
| event_a | prop_c |
| event_b | prop_a |
| event_b | prop_b |
Processed matching relationship preview
When you're done, click Upload matching relationship, upload the file, and follow the steps
After parsing completes, the system shows the upload and parsing results in a dialog
⚠ If no matching relationship is set in the configuration, the event may not work properly in analysis models later, and the page shows a warning dialog
Matching relationship error dialog preview