☆ Definition and understanding of DFINERY Event

outline

DFINERY ‘events’ are divided into two types.

• App Open Event : App launch event
• In-App Event : User activity events and property values ​​within the app, such as membership registration, character creation, and purchase

Defining the events required for app analysis and accurately linking and measuring them are the most important tasks in data analysis.
This document defines and explains the events provided by DFINERY.

You can also refer to the article Three Principles for Event Analysis and Event Design .

App Open Event

DFINERY app launch events are classified as follows.

division	type	Event name	Justice
App Open	New Install	abx:new_install	_ Number of devices that launched the app after installing it for the first time _ Can only occur once
	Re-Install	abx:re_install	_ After New Install, Number of runs after deleting and reinstalling the app _Duplicate may occur
	Deeplink Open	abx:deeplink_open	_ With the app installed, Number of apps launched through deep links _ Can only occur through Adbrix tracking link
	First Open	abx:firstopen	_ Sum of the number of apps launched after app installation _ means New Install + Re-Install

UserInfo Event

This event is used to define the logged in user in DFINERY.

division	type	Event name	Justice
UserInfo	Login	abx:login	_ When a user login event occurs
	Logout	abx:logout	_ When a user logout event occurs
	User Property Changed	abx:user_property_changed	_ When UserID is set through login and user information is added/changed through age, gender settings, and setUserProperty api.

In-App Event

DFINERY divides in-app events as follows.

• Pre-defined Event : Events predefined by Adbrix for convenience of use (common, commerce, game)
• Custom Event : An event that the customer can directly define
  

Common (general) events

Among DFINERY pre-defined events, this is an event that can be commonly used regardless of the app category.

division	defined event	Event name	Justice
common	join the membership	abx:sign_up	When a new membership registration event occurs
	Make payment*	abx:purchase	When a payment (purchase) occurs within the app
	app updates	abx:app_update	When an app update occurs
	user invitation	abx:invite	When a user invitation event occurs
	credit usage	abx:use_credit	When a virtual currency usage event occurs within the app

* This is the most commonly linked recommended event for analysis and advertising operations.

commerce event

This is an event for commerce apps among DFINERY pre-defined events.
It can be applied not only to commerce apps, but also to apps that sell content and services such as content, O2O, and recruiting.

You can perform more detailed analysis by adding property values ​​such as product ID, product name, order ID, and category under each event.
Please check the integration guide for more details.

division	defined event	Event name	Justice
commerce	Enter home screen	abx:view_home	Go to home screen
	Enter category	abx:category_view	Go to a specific category or special exhibition
	View product details*	abx:product_view	Enter product details page
	Put in a shopping cart*	abx:add_to_cart	Add to cart completion and product information
	Add product of interest	abx:add_to_wishlist	Add products of interest and relevant product information
	order confirmation	abx:review_order	Order confirmation and corresponding product information
	refund*	abx:refund	Refunds and refund product information after purchase
	Product Search*	abx:search	Product search keywords and search results Product information
	Product sharing	abx:share	Product sharing and shared product information
	Product list inquiry	abx:listview	Product list inquiry and product information
	Shopping Cart View	abx:cartview	Shopping cart search results and product information
	Enter payment information	abx:paymentinfoadded	Payment method information used for payment

* This is the most commonly linked recommended event for analysis and advertising operations.

game event

This is an event for game apps among DFINERY's pre-defined events.

You can perform more detailed analysis by adding property values ​​such as tutorial completion, stage name, and level section to each event. Please check the integration guide for more details.

division	defined event	Event name	Justice
game	Tutorial completed	abx:tutorial_complete	When the in-game tutorial is completed
	character generation	abx:character_created	When character creation is complete
	Stage completed	abx:stage_cleared	When a specific stage is completed
	Level achieved	abx:level_achieved	When you reach a certain level

custom event

In addition to predefined events, DFINERY supports customers to configure and analyze desired in-app events.
Please check the integration guide for more details.

In-App Event Property

DFINERY supports linking and analyzing properties, which are lower level information, to events.
For detailed analysis and advanced data-based advertising operations, it is very important to appropriately use the property values ​​provided by each event.

Example of ‘purchase’ event

Below is a list of properties and sample code that can be added to the Purchase event, which represents a purchase ( Android-Java ).
Supports everything from Order ID to Payment method. Required items and optional items are separated.

By linking 'Category' and 'Product name' to the product in the Purchase Event, you can segment the analysis as shown in the example below.
For example, you can only analyze the sales results of products belonging to a specific category, or you can analyze in detail whether the target product was actually sold through a specific advertisement.

Alternatively, you can use Audience Studio to perform a cohort analysis targeting only users who have purchased more than 1 million won in a specific category, or to extract advertising identification values ​​and start targeting advertisements.