Learn the key concepts of custom event analysis before you begin.
Before you start this tutorial, understand the following concepts:
|
Concept |
Description |
|
Event |
An event records a user action in the app. Log a custom event when an action, such as a button click, occurs. |
|
Event ID |
An event ID uniquely identifies an event. Events are global to the app. Therefore, event IDs must be unique within the same mPaaS application. |
|
Property |
An event contains information such as the user ID, app version, and device model. Each piece of information is a property. The Mobile Analysis platform provides preset properties, and you can define custom properties as needed. |
|
Property ID |
A property ID uniquely identifies a property. Properties are global to the app. Therefore, property IDs must be unique within the same mPaaS application. |
|
Event analysis |
Events and their properties are stored as logs on the client and then reported to the Mobile Analysis server. After you complete the configuration in the console, you can view event analysis reports. |
Tutorial scenario
When a user completes a payment, a payment completed event is recorded. This event includes the payment time, user ID, and payment method properties.
Event IDs and property IDs are used in both client development and console operations. Therefore, Android and iOS developers and console operators must agree on these IDs in advance. This tutorial assumes the following:
-
Event ID:
PayResults. -
Property IDs:
pay_time,user_id, andpayment_method.Custom property IDs cannot be the same as preset property IDs. You can view preset properties on the mPaaS console > Mobile Analysis > Custom Analysis > Event and Property Configuration > Properties page.
This tutorial walks you through the analysis of the payment completed event:
For troubleshooting, see the FAQ document.