In the previous data model, reported data directly generated assets such as events and event 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
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
Supports multi-source data integration and sets up the connections of the data through super-layer objects
Before data is actually generated, super-layer objects can exist as placeholders, so you can build reports and dashboards at the same time
When you need to migrate a project, assets in the analysis layer can be migrated based on the super layer, and any abnormal connections can be flexibly adjusted after migration
Super-layer model: source data is connected through super-layer objects before it is used for analysis
Note
To distinguish "events" from their source "reported events" or "model-mapping events" in the super-layer model, this document refers to "events" as "super events", and collectively refers to "reported events" and "model-mapping events" as "source events"
Use in analysis
List selection: In the previous system, the event lists contained only "reported events". After the upgrade to the super-layer model, the event lists contain only "super events", which extends the supported data sources while keeping the same experience as before
Model queries: After you create a report, the AE system automatically identifies and reads reported data or model-mapping data for calculation based on the source of the super event, keeping the same experience as before
SQL IDE: Because queries in SQL IDE are highly customized, you need to fill in the actual from xxx statement based on the source when you query, and write the SQL query based on the data in the original table
Business scenario example
Customer A reports data directly, which generates the super event "User Registration"
Customer A creates a model-mapping configuration, which generates the super event "Backend Order Completed"
When you query the Event total of "User Registration" in a report, the system reads the event table in AE, then calculates and returns the result
When you query the Event total of "Backend Order Completed" in a report, the system instead reads the external data table, then calculates and returns the result
When new events are reported, the AE system automatically detects them, and creates and connects super events with the same names
When you create a Model-Mapping Configuration (Event Table), the AE system also reads the events in the configuration, and then automatically creates and associates super events
Logic for automatic creation and association:
If no super event with the same name exists, the system automatically creates and associates a super event
If a super event with the same name already exists but no Source Event is selected for it, the system updates the source of that super event
If a super event with the same name already exists and its Source Event is already set, you need to manually confirm the event name and its source relationship
Automatic adding: The AE system detects new reported events/model-mapping events, creates super events for them, and sets up the connections
Manual creation: Before data is reported, you can also create the super events you need manually so that you can build reports and dashboards in advance
List management page overview
View / manage source events (opens the Source Events page).
Manage the display names of super events in batches.
Create a new super event or custom event.
Filter super events by visibility.
Search by event name, display name, or description.
The event name, display name, and description of the super event.
The data type of the super event source: not connected, reported event, model-mapping event, or custom event.
Whether the event can be used for real-time operations.
The fields are described in the following table:
Field name
Description
Event name
Starts with a letter and can contain letters, digits, and underscores, up to 60 characters
Event display name
Supports Chinese and English, up to 60 characters
Remarks
Supports Chinese and English, up to 60 characters
Event data type
The type of data source the event is connected to
Not connected = not yet connected to source data
Reported event = connected to an event in reported data
Model-mapping event = connected to an event in model-mapping data
Custom event = a custom event created based on super events
Volume yesterday
Valid only when the data type is "Reported event". Shows the volume of event data reported yesterday
Real-time available status
Whether the event can be used in trigger rules of Triggered Tasks and in Real-time Alerts
Available: the event can be used in trigger rules of Triggered Tasks and in Real-time Alerts
Unavailable: when the event is a custom event or is connected to model-mapping data, it can't be used for real-time tasks
Connection status
Whether the current event is connected to source data
Data status
Whether the data connection is available and working normally
Action
Edit = edit the basic information of the event
Duplicate = create a copy of the event based on the current event's information
Event name must start with a letter, can contain only letters, digits, and underscores, and can be up to 60 characters long.
Event display name can be up to 60 characters long.
Source Event: Select the source of the event from the model-mapping event list or the reported event list. Clicking Empty Source Event clears the current source information, which affects reports and dashboards that already use the event.
Description can be up to 60 characters.
Search by the name or display name of associated super event properties.
The super event property list of the current project. Click to select the properties to associate. After you select them, the system automatically reads their display names, data types, and descriptions.
Delete associated super event properties.
Cancel or save the current configuration.
In addition, + Associated event properties adds 1 event property as an association. Sync from the source: After you select a source event, the system automatically reads the event properties already connected in the source event and overwrites the current configuration.
The reported data contains two events, "Battle Won" and "Battle Lost". Can I merge them into "Battle Ended" with a super event?
Because of partitioning in queries, a super event supports only 1 source event and can't merge two events into 1
For this scenario, you can use the Custom Events feature in the AE system directly
Can I create events and event properties in batches and set their associations?
Yes. Import an Excel file with the Batch import and export feature to create events and event properties in batches and set their associations. For details, see Batch editing of events and properties
