General Event Analytics, understanding and interpretation

outline

General Event Analytics allows you to analyze event status.
Select General Event Analytics from the Analytics > Data Explorer menu.

Metric

General Event Analytics provides three metrics, the definitions of which are as follows.

Total Event count	This means the total number of times the selected event was executed. If a total of 3 purchases occurred on the same device, it is counted as '3'.
Unique Event count	This refers to the unique number of times the selected event occurred. If a total of 3 purchases occurred on the same device, it is counted as '1'.
Price x Quantity	This is confirmed when an In-App Event containing Price and Quantity items is linked. Events such as Purchase and Add to Cart fall into this category.

[[Quote:Guide:Small]] Meaning of Event in DFINERY
DFINERY Event is a concept that includes both App Open Event and In-App Event.
By setting the Event name in Group by and Conditions, you can freely configure app open and in-app event analysis indicators as needed.
You can additionally refer to the definition document for DFINERY events .

[[Quote: Guide: Small]] About the basic structure and concepts of using data explorers such as Group by, Analytics Conditions, and Audience.
Data Explorer - Please check additional documentation for understanding of the analysis structure and examples .

Report examples and interpretation

	Analysis Purpose
#1	MAU, DAU, HAU analysis by platform (Android, iOS)	look
#2	Purchase report by platform (Android, iOS)	look
#3	Purchase conversion report by advertising channel	look
#4	Add to cart conversion report by advertising channel	look
#5	Purchase report for a specific product	look
#6	Purchase status report by city	look
#7	Membership conversion report by user inflow channel	look

#1

MAU, DAU, HAU report by platform

We analyze monthly MAU separately by Android and iOS. This is MAU, or Monthly Active User, as it calculates the unique event count among all monthly events that occurred in the app for each platform. If you select Daily, you will become a DAU (Daily Active User), and if you select Hourly, you will become a HAU (Hourly Active User). Select the date that requires analysis from the Date Range.

Table Design

Conditions

#2

Purchase report by platform

We analyze the total number of daily purchases (Total Event), number of unique purchases (Unique Event), and purchase amount (Price x Quantity) that occurred in the app by platform by platform. You must add the event name 'include' abx:purchase condition to Conditions to define the selected Metric as a 'purchase' event. If you select Hourly as the Date Type, it will be a purchase report by time period.

Table Design

Conditions

#3

Purchase conversion report by advertising channel

We analyze the total number of purchases (Total Event), number of unique purchases (Unique Event), and purchase amount (Price x Quantity) of incoming users by advertising channel. Group by includes Ad Partner > Tracking Link. 'Event Name' in Analytics Conditions 'includes' abx:purchase to analyze only purchase event results.In addition, Organic is 'not included' in 'Ad Partner' in Analytics Conditions and only advertising channels are analyzed.(Of course, Organic channels are not Ad Partners, but are included as Ad Partners for analysis convenience.)

Open Attribution Type included New Install, Re-Install, and Deeplink Open, and Event Lookback Window was selected as 7 days. In other words, we analyze purchase conversions that occurred within 168 hours after launching all apps from Ad Partners.

Table Design

Conditions

#4

Add to cart report by advertising channel

We analyze the total number of shopping cart additions (Total Event), unique event additions (Unique Event), and shopping cart amount (Price x Quantity) results of incoming users by advertising channel. Group by includes Ad Partner > Tracking Link. The Event Name of Analytics Conditions ‘includes’ abx:add_to_cart to enable analysis of only purchase event results. In addition, Organic is 'not included' in 'Ad Partner' in Analytics Conditions, and only advertising channels are analyzed.(Of course, Organic channels are not Ad Partners, but are included as Ad Partners for analysis convenience.)

Open Attribution Type included New Install, Re-Install, and Deeplink Open, and Event Lookback Window was selected as 7 days. In other words, we analyze add-to-cart conversions that occurred within 168 hours of launching all apps from Ad Partners.

Table Design

Conditions

#5

Sales report for specific product

Analyze the total number of purchases per day, number of unique purchases, and total purchase amount of a specific product corresponding to the Product ID by date and platform.

This is a report setting to check only the purchase status of specific products among purchases by platform (Android, iOS). Since you need to analyze the purchase status of a specific product, select abx:purchase among the Event Name items in Analytics Conditions and enter the product number you want to analyze in Product ID. For Metrics, select Unique Event, Total Event, and Price x Quantity.

Table Design

Conditions

#6

Purchase status report by city

Table Design

Conditions

#7

Membership conversion report by user inflow channel

We analyze the total number of user registrations (total events) by inflow channel. Group by includes Ad Partner > Tracking Link. In 'Event Name' of Analytics Conditions, select the event (sign_up) defined as a membership registration event to analyze only the membership registration results.Since Organic was not excluded from 'Ad Partner' in Analytics Conditions, the Organic channel is also included in the inflow channel.(Of course, Organic channels are not Ad Partners, but are included as Ad Partners for analysis convenience.)

Open Attribution Type included New Install, Re-Install, and Deeplink Open, and Event Lookback Window was selected as 7 days. In other words, we analyze membership conversions that occurred within 168 hours after launching all apps from Ad Partners.

Table Design

Conditions