Understanding the Event in DFINERY
Overview
What the ‘Event’ indicates in DFINERY is the general ‘In-App Events’ and ‘App Open Events’ taking place in the mobile application. Defining the necessary events needed for the app analysis and integrating them accurately are the most important steps for the data analysis. In this article, you will learn what is the ‘Event’ and get a better understanding on them.
App Open Events
The ‘App Open Events’ of the DFINERY are classified as following.
These event can be show to your report by just basic SDK integration.
|
Classification |
Type |
Event Name |
Definition |
|
App Open Events
|
New Install |
abx:new_install |
Number of ‘App Opens’ after initial ‘Install’ |
|
Re-Install |
abx:re_install |
Number of ‘App Opens’ after ‘Re-install’ |
|
|
Deeplink Open |
abx:deeplink_open |
Number of ‘App Opens’ through deep-links with the app installed |
|
|
First Open |
abx:firstopen |
Number of ‘App Opens’ after ‘Install’ |
|
|
Daily First Open |
abx:daily_first_open |
Number of app retention that day after App Install (New / Re Install) |
UserInfo Event
UserInfo Event that dfine user.
| Classification | Type |
Event Name |
Definition |
| UserInfo |
Login | abx:login |
_ Once user call Login API. |
| Logout | abx:logout |
_ Oce user call Logout API. |
|
| User Property Changed | abx:user_property_changed |
_ Set userID after login api and set age, gender and set user info with setUserProperty API. |
In-App Events
‘In-App Events’ in DFINERY are classified as following. For the convenience of use, ‘In-App Event’ is divided into ‘Pre-defined Events’ which is readily defined event by DFINERY , and ‘Custom Events’ which is the events which client can integrate directly. For the case of ‘In-App Event’, clients can choose the events according to their needs. Link to Integration Guide
Common(General) Event
‘Common Event’ is the events amongst other ‘Pre-defined Events’ which can be shared across all the app categories. Refer to each event APIs if the event is object the analysis.
|
Classification |
Defined Event |
Event Name |
Definition |
|
Common |
Sign-up |
abx:sign_up |
Case when sign-up event takes place |
|
Purchase* |
abx:purchase |
Case when in-app purchase takes place |
|
|
App Update |
abx:app_update |
Case when app update takes place |
|
|
User Invitation |
abx:invite |
Case when user invitation event takes place |
|
|
Credit Use |
abx:use_credit |
Case when in-app credit use event takes place |
* the most general event integrated for the analysis and campaign operation
Commerce Event
‘Commerce Event’ indicates the events of the application which falls into the commerce category amongst the other ‘Pre-defined Events’. This event is suitable for the contents, O2O, recruiting, commerce applications which merchandises products and services.
Add more parameters like product ID, product name, order ID, category, etc. to proceed much detailed analysis. Check more on the parameters in the link.
|
Classification |
Defined Event |
Event Name |
Definition |
|
Commerce |
Home view |
abx:view_home |
Move to ‘home view’ |
|
Category |
abx:category_view |
Move to specific category |
|
|
Product view* |
abx:product_view |
Move to product detail page |
|
|
Add to cart* |
abx:add_to_cart |
Complete add to cart / product info |
|
|
Wishlist |
abx:add_to_wishlist |
Add wishlist / product info |
|
|
Order confirmation |
abx:review_order |
Order confirmation / product info |
|
|
Refund* |
abx:refund |
Refund / refunded product info |
|
|
Product search |
abx:search |
Product search keyword / searched product info |
|
|
Product share |
abx:share |
Product share / shared product info |
|
|
Product list view |
abx:lstview |
Product list view / product info |
|
|
Cart view |
abx:cartview |
Cart view result / product info |
|
|
Payment information |
abx:paymentinfoadded |
Payment info used to purchase |
* the most general event integrated for the analysis and campaign operation
Game Event
‘Game Event’ indicates the events of the application which falls into the game category amongst the other ‘Pre-defined Events’. Add more parameters like tutorial completion, stage name, level, etc. to proceed much detailed analysis. Check more on the parameters in the link.
|
Classification |
Defined Events |
Event Name |
Definition |
|
Game |
Tutorial completion |
abx:tutorial_complete |
Tutorial is completed in game |
|
Create character |
abx:character_created |
Character is successfully created |
|
|
Stage completion |
abx:stage_cleared |
Certain stage is completed |
|
|
Level achievement |
abx:level_achieved |
Certain level is achieved |
Custom Event
‘In-App Events’ specifically customized for the clients are supported even if the events are not pre-defined by DFINERY. More details can be found in the link.