Event properties

Last updated 10/02/2026

1. Feature overview

Previous approach

• 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

View original image

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

View original image

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 event properties". After the upgrade to the super-layer model, the event lists contain only "super event properties", 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" containing the event property "Channel"

• Customer A creates a model-mapping configuration, which generates the super event "Backend Order Completed" that also contains the event property "Channel"

• If you now view the super event property list, you see only 1 event property named "Channel"

• The super event property "Channel" is now associated with 2 data sources:

  • The "User Registration" event in reported data
  • The "Backend Order Completed" event in model-mapping data

• When you query the Deduplication of "Channel" in "User Registration" in a report, the system reads the property in the event table in AE, then calculates and returns the result

• When you query the Deduplication of "Channel" in "Backend Order Completed" in a report, the system instead reads the property in the external data table, then calculates and returns the result

2. Usage

Automatic detection logic

• When new event data is reported, the AE system automatically detects it, and creates and connects a super event property with the same name

• When you create a Model-Mapping Configuration (Event Table), the AE system also reads the event properties in the configuration and then automatically adds connection settings for the properties

• Logic for automatic creation/connection:

  • If no super event property with the same name exists, the system automatically creates and associates a super event property
  • If a super event property with the same name and type already exists, the system adds 1 association to that super event property
  • If a super event property with the same name but a different type already exists, you need to manually confirm the event property and its connections

List page

List management page overview

1. Filter event properties by visibility.
2. The name, display name, and description of the event property.
3. View / manage source event properties (opens the Source Property Management page).
4. Set the display names of event properties in batches.
5. Create a new super event property or custom event property.
6. Search by event property name, display name, or description.
7. Edit the current super event property, or set its connections.
8. More menu: Hide toggles the visibility, Duplicate creates a copy of the property, Add adds a dimension table to the property, and Delete deletes the current super event property. Properties of the Row / Array Row type also have Create sub-property.

• The fields are described in the following table:

Field name	Description
Event property name	Starts with a letter and can contain letters, digits, and underscores, up to 80 characters
Event property display name	Supports Chinese and English, up to 80 characters
Remarks	Supports Chinese and English, up to 60 characters
Property type	Event properties are the basic properties used in analysis models. Combined with other features, they can generate custom properties, dimension properties, and currency properties
Data type	For example, String / Number / Boolean
Real-time available status	Whether the property can be used in trigger rules of Triggered Tasks and in Real-time Alerts
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 property Duplicate = create a copy based on the current event property Hide/Show = set the event property to hidden/visible Add dimension table = add a dimension table to the current property (not supported for the Row / Array Row types) Download/Update/Delete dimension table = the corresponding actions for properties that have a dimension table Create sub-property = create sub-properties for a property of the Row / Array Row type Delete = delete the current event property

Create an event property

Creating a super event property

• Event association: If the current Property A is associated with Event 1 but not with Event 2, then when you use it in an analysis model:

  • After you select Event 1, you can find Property A in its property list
  • After you select Event 2, you cannot find Property A in its property list

When you need to create many assets early in a project, you can use Batch editing of events and properties

Set event property connections

Source connection settings of a super event property

• Property source connections:

  • A super property can be connected to only 1 reported property

  • Within 1 model-mapping data source, a super property can be connected to only 1 model-mapping property

  • If Property A is associated with Event 1 and Event 2, but no source property connection is set:

    • Analysis models cannot get calculation results when they query

  • If Property A is associated with Event 1 and Event 2, and source connections are also set to properties in their data sources:

    • When you query Event 1, the system reads the property connected to Property A from the source data of Event 1 and calculates
    • When you query Event 2, the system reads the property connected to Property A from the source data of Event 2 and calculates

  • If there is a Property P of the Array Row type that contains Sub-property P1:

    • The property connected to Sub-property P1 must also be a sub-property, and its parent property must already be connected to Property P

3. Main feature permissions

The permissions involved are as follows:

Permission ID	Feature	Permissions	Details
19	Metadata	View	View the lists of events, event properties, and user properties; preview data tables
20	Metadata	Edit	Edit the display names of original events, event properties, and user properties
21	Metadata	Edit	Edit custom events, dimension tables, and custom properties
59	Metadata	View	Export dimension tables of properties; download data table content and historical content
89	Metadata	Edit	Add and edit file-upload data tables; restore historical versions of file-upload data tables
5000	Metadata	Edit	Manage event/event property lists, set data connections, and view reported/model-mapping asset information

Permissions for each entry in the figure:

1. Open the page: permission ID 19.
2. Manage source event properties (the Source Property Management entry): permission ID 5000.
3. Edit display names (set display names in batches): permission ID 20.
4. + Event Property drop-down: creating a super event property requires permission ID 5000, and creating a custom event property requires permission ID 21.
5. Inline editing of display names and descriptions: permission ID 20.
6. Edit and set connections on a row (edit a super event property and its connections): permission ID 5000.

Permission IDs for the More menu and other row actions: hide an event property 20, duplicate an event property 5000, add a dimension table property 89, create a sub-property 5000, delete an event property 5000, update a dimension table 89, download a dimension table 59, delete a dimension table 21; editing on a custom event property row requires 21.

4. Limits

• You can create up to 1,000 super event properties in a single project

5. FAQ

• Why can't I edit or delete the #user_id event property?

  • To keep analysis models usable, some properties cannot be edited on the page. These properties are described below:
  • #user_id: the unique user ID in the AE system, used for the default distinct user count in analysis models
  • #event_name: the event name, used to identify events in analysis models
  • #event_time: the event time, used to parse event times and calculate time zone offsets in analysis models
  • #zone_offset: the time zone offset, used to calculate time zone offsets of events in analysis models
  • #te_event_id: the unique event ID, used to uniquely identify events in real-time calculation for Engage