User property

Last updated 10/02/2026

1. Feature overview

Previous approach

• In the previous data model, reported data directly generated assets such as user properties 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

Unlike event properties, each user property can have only 1 data source (data reporting or model mapping)

Model-mapping user property configuration must be enabled by a data administrator. Discuss and confirm this during the project kickoff phase, and then carry out the related operations

In the current version, model-mapping user properties are configured in Model-Mapping Configuration (Entity table)

Note

To distinguish "user properties" from their source "reported user properties" or "model-mapping user properties" in the super-layer model, this document refers to "user properties" as "super user properties", and collectively refers to "reported user properties" and "model-mapping user properties" as "source user properties"

Use in analysis

• List selection: In the previous system, the user property lists contained only "reported user properties". After the upgrade to the super-layer model, the user property lists contain only "super user 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 user property, 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

2. Usage

Automatic detection logic

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

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

• Logic for automatic creation/connection:

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

List page

List management page overview

The features of the list page are as follows. The numbers correspond to the callouts in the figure above:

1. Visibility: Filter user properties by visibility.
2. Property name, display name, description: The name, display name, and description of the user property.
3. Source user property management: Opens the source user property management page, where you can view and manage source user properties.
4. Display Name: Set the display names of user properties in batches.
5. + User Property: Create a new super user property or custom user property.
6. Search box: Search by user property name, display name, or description.
7. Row actions: Edit the current super user 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 user property. Properties of the Row / Array Row type also have Create sub-property.

• The fields are described in the following table:

Field name	Description
User property name	Starts with a letter and can contain letters, digits, and underscores, up to 80 characters
User property display name	Supports Chinese and English, up to 80 characters
Remarks	Supports Chinese and English, up to 200 characters
Property type	User 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 / Time / List / Row / Array Row
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 user property is connected to source data
Data status	Whether the data connection is available and working normally
Action	Edit = edit the basic information of the user property Duplicate = create a copy based on the current user property Hide/Show = set the user 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 user property

Create a user property

Creating a super user property

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

Set user property connections

Source connection settings of a super user property

• Property source connections:

  • A super property can be connected to only 1 reported property
  • 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 in user property features are as follows:

Permission ID	Feature	Permission	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

The entries corresponding to the numbers in the figure and their required permissions are as follows:

1. Open the user properties page (view): permission ID 19
2. Source user property management (manage source user properties): permission ID 5000
3. Display Name (edit display names): permission ID 20
4. + User Property: creating a super user property requires permission ID 5000, and creating a custom user property requires permission ID 21
5. Inline editing of display names and descriptions: permission ID 20
6. Row actions: editing a super user property and setting connections require permission ID 5000, and editing a custom user property requires permission ID 21

The permissions required for each action in the More menu (see the figure in the List page section) are as follows:

• Hide a user property: permission ID 20
• Duplicate a user property: permission ID 5000
• Add a dimension table: permission ID 89
• Create a sub-property: permission ID 5000
• Delete a user property: permission ID 5000
• Properties with a dimension table: updating the dimension table requires permission ID 89, downloading it requires permission ID 59, and deleting it requires permission ID 21

4. Limits

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

5. FAQ

• Why can't I edit or delete the #user_id user 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