Batch editing of events and properties
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
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
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"
Batch editing
- After the tracking plan has been agreed on and while you wait for data integration, business members can create the corresponding assets one by one on the Events, Event Properties, and User Properties pages and use them to build reports and dashboards
- To further improve the efficiency of creating these assets, you can now use the Batch import and export feature to import an agreed tracking plan, or the overall asset plan of a project with similar data specifications, into the current project directly or after editing it in Excel, so that you can move on to building dashboards faster
2. Entry point
On the Events, Event Properties, or User Properties page, click the [Manage] button in the upper-right corner to expand more features
The list includes the entries for importing and exporting asset configurations
Feature entry
The permissions required for each feature are as follows
| Entry | Permission feature name | Category | Permission feature details |
|---|---|---|---|
| Export configuration | Metadata | View | View the lists of events, event properties, and user properties; preview data tables |
| Import configuration | Metadata | Edit | Manage event/event property lists, set data connections, and view reported/model-mapping asset information |
Permission configuration page
3. Procedure
3.1 Export asset configuration
After you click Export, the browser automatically opens a download window. Save the Excel file directly
3.2 Import asset configuration
⚠ After you import an asset configuration, the system creates or changes the type, display name, remarks, and other information of the corresponding assets in the project based on the asset names
⚠ If a piece of information is empty in the configuration Excel, the system also clears that asset information in the project, such as remarks and display names
⚠ The system doesn't change asset information that exists in the project but isn't filled in the Excel. That is, assets that don't exist in the Excel aren't deleted in batches
Prompt dialog
⚠ Before you upload an asset configuration, we recommend confirming that its content is usable, to avoid having to delete assets repeatedly after uploading an incorrect configuration
After you click Import, a dialog shows key information. Click [Continue] to go to the next step and select the configuration file to import
Configuration file upload
After the file is uploaded, the system first parses the Excel content, and then imports the asset configuration after you confirm the results
Parsing result confirmation
Import execution result
4. Excel template overview
Asset import supports uploading Excel files from <Tracking>. After the tracking plan is confirmed, you can import the plan Excel directly to generate events and properties and start building reports and dashboards
4.1 Sub-sheet overview
After you export and open the asset configuration Excel file, you see 3 sub-sheets
Excel sub-sheet preview
The purpose of each sub-sheet is as follows
| Sub-sheet name | Description |
|---|---|
| #Events | Records events and their associated event properties. The format is similar to the tracking plan sheet in the <Tracking> feature |
| #Public Event Properties | If an event property is associated with all events, you can fill it in separately in this sheet. After import, the system activates its "super property" status |
| #User Properties | Records user property information |
4.2 Event data table
Fill in the information of a single event and its associated event properties by referring to the following table
| Event name (required) | Event display name | Event description | Property name (required) | Property display name | Property type (required) | Property description |
|---|---|---|---|---|---|---|
| activity_attend | Join activity | Claim activity rewards | activity_type | Activity type 1 | Text | Beginner activities, etc. |
| channel | Source Channel | Text | IOS/Android | |||
| level | Level after upgrade | Numeric | ||||
| platform | System platform identifier | Text | Platform identifier: android, IOS, harmonyOS, PC | |||
| serverid | Server ID | Numeric | ||||
| vip_level | VIP level | Numeric | ||||
| #device_id | Text | |||||
| #lib | Text | |||||
| #lib_version | Text | |||||
| #os | Text |
Event data table preview
The fields are described as follows:
| Field Name | Description |
|---|---|
| Event name (required) | Starts with a lowercase letter, contains lowercase letters, digits, and underscores, and is no longer than 60 characters |
| Event display name | No longer than 60 characters |
| Event description | No longer than 200 characters |
| Property name (required) | Starts with a lowercase letter, contains lowercase letters, digits, and underscores (sub-properties of Array Row contain periods), and is no longer than 80 characters |
| Property display name | No longer than 80 characters |
| Property type (required) | Number, String, Time, Boolean, List, Row, Array Row |
| Property description | No longer than 200 characters |
4.3 Super property table
If a property is associated with all events, fill in its information here
⚠ If a property is filled in both the <Event data table> and the <Super property table>, it's treated as a "super property"
| Property name (required) | Property display name | Property type (required) | Property description |
|---|---|---|---|
| channel | Channel | Text | |
| level | Level | Numeric | |
| gold_left | Remaining gold coins | Numeric |
Super property table preview
The fields are described as follows:
| Field Name | Description |
|---|---|
| Property name (required) | Starts with a lowercase letter, contains lowercase letters, digits, and underscores (sub-properties of Array Row contain periods), and is no longer than 80 characters |
| Property display name | No longer than 80 characters |
| Property type (required) | Number, String, Time, Boolean, List, Row, Array Row |
| Property description | No longer than 200 characters |
4.4 User property table
Fill in user property information by referring to the following table
| Property name (required) | Property display name | Property type (required) | Property description |
|---|---|---|---|
| ad | Ad ID | Text | |
| ad_set | Ad set ID | Text | |
| campaign | Ad campaign | Text | |
| channel | Source Channel | Text | app store,Huawei AppGallery,Xiaomi GetApps,vivo,taptap,Wandoujia=first |
| current_level | Current level | Numeric | |
| first_login_time | First login time | Time | Set at first login |
User property table preview
The fields are described as follows:
| Field Name | Description |
|---|---|
| Property name (required) | Starts with a lowercase letter, contains lowercase letters, digits, and underscores (sub-properties of Array Row contain periods), and is no longer than 80 characters |
| Property display name | No longer than 80 characters |
| Property type (required) | Number, String, Time, Boolean, List, Row, Array Row |
| Property description | No longer than 200 characters |