☆ Create essential dashboard (analyze app status & advertising performance)
This document guides you through how to configure essential dashboards based on reports that are basic to analysis.
[[Quote:Information:Small]]A description of custom dashboard functions can be found in the Creating a Custom Dashboard document.
Create an app status analysis dashboard
Dashboard configuration
List of widgets required to construct an app analytics dashboard.
| widget name | Report type | Justice |
| New Install (total) | Single Touch Attribution | Total number of new installs |
| Re-Install (total) | Single Touch Attribution | Total number of reinstalls |
| Purchase amount (total) | General Event | Total purchase amount |
| DAU (by platform) | General Event | Number of unique app actives per day |
| HAU (by platform) | General Event | Number of unique app actives by time period |
| Purchase count (by platform) | General Event | Total purchases per day |
| Purchase amount (by platform) | General Event | Daily purchase amount |
| Open Retention (total) | Universal Retention | App open retention by date after installation |
| Purchase Funnel (total) | Conversion Funnel | Purchase Funnel Analysis |
Widget Guide
We will guide you through the features of each widget included in the essential dashboard.
New Install
Analyzes the total number of New Installs that occurred within a specific period.
In Definery , New Install refers to the number of advertising identifiers (adid/idfa) of devices that installed and ran the app for the first time after the Definery SDK was integrated into the app. Therefore, New Install is a unique value that occurs only once for one advertising identifier.
For example, if the New Install value is 10,000, it means that the app was first installed and launched from 10,000 different advertising identification values.
Since the Platform item was not set in Group by and Analytics Conditions, it includes all New Installs that occurred on Android and iOS.
Because Attribution-related items (Ad Partner, Tracking Link, etc.) are not set in Group by, Analytics Conditions, Attribution Conditions are not activated and have no effect on analysis.
[[Quote:Information:Medium]] If you set 'Android with Platform' in Analytics Conditions, you can distinguish Androids New Install figures.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | Single Touch Attribution |
| Table Design | Date Type | Daily |
| Group by | - | |
| Metrics | New Install (total) | |
| Conditions | Attribution Conditions | Disabled |
| Date Ragne | last week | |
| Time Zone | UTC+9 | |
| Audience | - | |
| Data Visualization | widget name | New Install (total) |
| Apply global filter | On | |
| Widget type | Summary | |
| formula | Sum |
Re-Install
Analyzes the total number of Re-Installs that occurred within the selected period.
In Definery, Re-Install refers to the number of advertising identifiers (adid/idfa) of devices that installed and ran the app for the first time after the Definery SDK was integrated into the app, then deleted and reinstalled the app. In other words, it is the number of reinstallations after deletion. Therefore, Re-Install can occur repeatedly for one advertising identifier.
Because the Platform item was not set in Group by and Analytics Conditions, all re-installs that occurred on Android and iOS are included.
Because Attribution-related items (Ad Partner, Tracking Link, etc.) are not set in Group by, Analytics Conditions, Attribution Conditions are not activated and have no effect on analysis.
[[Quote:Guide:Medium]] If you set 'Android with Platform' in Analytics Conditions, you can distinguish the Re-Install figures for Android.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | Single Touch Attribution |
| Table Design | Date Type | Daily |
| Group by | - | |
| Metrics | Re-Install (total) | |
| Conditions | Attribution Conditions | Disabled |
| Date Ragne | last week | |
| Time Zone | UTC+9 | |
| Audience | - | |
| Data Visualization | widget name | Re-Install (total) |
| Apply global filter | On | |
| Widget type | Summary | |
| formula | Sum |
Purchase amount
Analyzes the sum of all purchases made within the selected time period.
Since we need to analyze the 'purchase amount', select Price x Quantity from Metrics in General Event Analytics, and then select abx:Purchase from Event Name in Analytics Conditions.If you select this, the products Price and Quantity are multiplied during the Purchase event, that is, the purchase amount is calculated.
Since the Platform item was not set in Group by and Analytics Conditions, all purchases made on Android and iOS are included.
Because Attribution-related items (Ad Partner, Tracking Link, etc.) are not set in Group by, Analytics Conditions, Attribution Conditions are not activated and have no effect on analysis.
[[Quote:Guide:Normal]]
1. You can separate the total purchase amount that occurred on Android by adding 'Platform includes Android' in Analytics Conditions.
2. To analyze the amount of completed shopping cart additions, select Price x Quantity in Metrics equally, then set the Event name to 'abx:add_to_cart'.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | General Event Analytics |
| Table Design | Date Type | Daily |
| Group by | - | |
| Metrics | Price x Quantity | |
| Conditions | Attribution Conditions | Disabled |
| Date Ragne | last week | |
| Time Zone | UTC+9 | |
| Audience | - | |
| Data Visualization | widget name | Purchase amount (total) |
| Apply global filter | On | |
| Widget type | Summary | |
| formula | Sum |
DAU
Check the daily active user (DAU) figures.
The DAU figure provided is the unique value of the device advertising identification value obtained through the SDK. This means you can analyze how many unique devices your app is active on.
The Unique Event Count selected in Metrics refers to the number of unique events (i.e., the number of unique advertising identification values) that occurred from the specified conditions. Since no event is selected in Analytics Conditions and Date Type is selected as Daily and Group by is selected as Platform, the number of unique advertising identification values that activate the app on each Android and iOS are analyzed separately.
For example, if Androids Unique Event Count is 10,000 on January 20, 2022, the total number of unique advertising identifiers (adid) that activated the app on the Android platform on that date (=DAU of the Android app) is 10,000.
Because Attribution-related items (Ad Partner, Tracking Link, etc.) are not set in Group by, Analytics Conditions, Attribution Conditions are not activated and have no effect on analysis.
[[Quote:Guide:Normal]] To see the total number of unique advertising identifiers that activated your app within a selected period, set Date Type to Total to see the number of unique devices that activated your app within a specific period.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | General Event Analytics |
| Table Design | Date Type | Daily |
| Group by | Platform | |
| Metrics | Unique Event Count | |
| Conditions | Attribution Conditions | Disabled |
| Date Ragne | last week | |
| Time Zone | UTC+9 | |
| Audience | - | |
| Data Visualization | widget name | DAU (by platform) |
| Apply global filter | On | |
| Widget type | Bar | |
| Edit chart |
Axis Position - Primary
|
HAU
Check the Hourly Active User (HAU) figures.
The Unique Event Count selected in Metrics refers to the number of unique events (i.e., the number of unique advertising identification values) that occurred from the specified conditions. Since no events are selected in Analytics Conditions and Date Type is set to Hourly and Group by is set to Platform, the number of unique advertising identifiers that activate the app for each time zone on Android and iOS are analyzed separately.
For example, if Androids Unique Event Count is 3,000 at 13:00 on January 20, 2022, the total number of unique advertising identifiers (adid) that activated the app on the Android platform at that time (= HAU of the Android app) is 10,000. .
Because Attribution-related items (Ad Partner, Tracking Link, etc.) are not set in Group by, Analytics Conditions, Attribution Conditions are not activated and have no effect on analysis.
[[Quote:Guide:Normal]] If you want to check the total number of unique advertising identifiers that activated the app within a selected time period, you can set Date Type to Total to check the number of unique devices that activated the app within a specific period.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | General Event Analytics |
| Table Design | Date Type | Hourly |
| Group by | Platform | |
| Metrics | Unique Event Count | |
| Conditions | Attribution Conditions | Disabled |
|
Date Ragne |
last week |
|
| Time Zone | UTC+9 | |
| Audience | - | |
| Data Visualization | widget name | HAU (by platform) |
| Apply global filter | On | |
| Widget type | Bar | |
| Edit chart |
Axis Position - Primary
|
Purchase count
View the total number of purchases per day within a specific period.
Since we need to analyze the 'total number of purchases', select Total Event Count from Metrics in General Event Analytics, and then select abx:Purchase from Event name in Analytics Conditions.This selection allows you to analyze the total number of times the Purchase event occurred.
Since Date Type was selected as Daily and Group by was selected as Platform, Android and iOS figures by date can be analyzed separately.
Because Attribution-related items (Ad Partner, Tracking Link, etc.) are not set in Group by, Analytics Conditions, Attribution Conditions are not activated and have no effect on analysis.
[[Quote:Guide:Normal]]
1. If you need to check only the total number of purchases that occurred on Android, add 'Platform includes Android' in Analytics Conditions.
2. To analyze the total number of times the shopping cart was completed, select Total Event Count in Metrics and set it to 'Event name includes abx:add_to_cart'.
3. To analyze the number of unique purchases, select Unique Event Count in Metrics, then select the Purchase event in Analytics Conditions.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | General Event Analytics |
| Table Design | Date Type | Daily |
| Group by | Platform | |
| Metrics | Total Event Count | |
| Conditions | Attribution Conditions | Disabled |
| Data Range | last week | |
| Time Zone | UTC+9 | |
| Audience | - | |
| Analytics Conditions | Event name included purchase | |
| Data Visualization | widget name | Purchase Count (by Platform) |
| Apply global filter | On | |
| Widget type | Bar | |
| Edit chart |
Axis Position - Primary
|
Purchase amount
View daily purchase amount (sales) figures within a specific period.
Since we need to analyze the 'purchase amount', select PriceThis selection allows you to analyze the purchase amount for the Purchase event.
Since Date Type was selected as Daily and Group by was selected as Platform, Android and iOS figures by date can be analyzed separately.
Because Attribution-related items (Ad Partner, Tracking Link, etc.) are not set in Group by, Analytics Conditions, Attribution Conditions are not activated and have no effect on analysis.
[[Quote:Guide:Normal]]
1. If you need to check only the purchase amount that occurred on Android, add 'Platform includes Android' in Analytics Conditions.
2. To analyze the amount of completed shopping cart additions, select Price x Quantity in Metrics equally, then set it to 'Event name includes abx:add_to_cart'.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | General Event Analytics |
| Table Design | Date Type | Daily |
| Group by | Platform | |
| Metrics | Price x Quantity | |
| Conditions | Attribution Conditions | Disabled |
| Date Ragne | last week | |
| Time Zone | UTC+9 | |
| Audience | - | |
| Analytics Conditions | Event name including abx:purchase | |
| Data Visualization | widget name | Purchase count (by platform) |
| Apply global filter | On | |
| Widget type | Bar | |
| Edit chart |
Axis Position - Primary
|
Open Retention
After app installation, we analyze daily activation retention.
I selected abx:firstopen as the Standard Event, abx:start_session as the Target Event, and Unique as the Value Type. Therefore, we analyze unique start_session (app activation) events by date based on firstopen (first run after app installation).
For example, if the Standard User figure in Metrics as of February 20, 2019 is 5,000, the 1 day figure is 2,500, and the 3 day figure is 2,000, then among the 5,000 advertisement identification values that were run for the first time after installing the app on February 20th The unique advertising identification value of the app activated on February 21st (1 day) is 2,500, and the number of advertising identification values of 5,000 ads running for the first time after installing the app on February 20th is 'among' February 23rd (3 days). The number of unique advertising identification values that activate the app is 2,000.
Since the Platform item was not set in Group by and Analytics Conditions, both Android and iOS are included.
Because Attribution-related items (Ad Partner, Tracking Link, etc.) are not set in Group by, Analytics Conditions, Attribution Conditions are not activated and have no effect on analysis.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | Universal Retention Analytics |
| Table Design | Standard Events | abx:firstopen |
| Target Events | abx:start_session | |
| Method Type | Generic | |
| Value Type | Unique | |
| Date Type | Daily | |
| Group by | - | |
| Metrics | Standard User, 1 day, 2 day, 3 day, 5 day, 7 day | |
| Conditions | Attribution Conditions | Disabled |
| Date Ragne | last week | |
| Time Zone | UTC+9 | |
| Audience | - | |
| Analytics Conditions | - | |
| Data Visualization | widget name | Open Retention (total) |
| Apply global filter | On | |
| Widget type | Table | |
| Use heatmaps | shame |
Purchase Funnel
Analyze conversion results that lead to final purchase.
Since the order abx:firstoepn > abx:login > abx:purchase was selected in Events, the advertising identification value reached after installing and running the app in the selected period > login > purchase is analyzed. Since the Platform item was not set in Group by and Analytics Conditions, both Android and iOS are included.
For example, if abx:firstoepn(a) is 5,000, abx:login(b) is 3,000, and abx:purchase(c) is 1,000, among the 5,000 advertising identification values that generated firstopen, the final number from completion of login to purchase This means that the number of ad identification values reached is 3,000.
Since the Platform item was not set in Group by and Analytics Conditions, both Android and iOS are included.
Because Attribution-related items (Ad Partner, Tracking Link, etc.) are not set in Group by, Analytics Conditions, Attribution Conditions are not activated and have no effect on analysis.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | Conversion Funnel Analytics |
| Table Design | Date Type | Daily |
| Group by | - | |
| Events | abx:firstoepn, abx:login, abx:purchase | |
| Conditions | Attribution Conditions | Disabled |
| Date Ragne | last week | |
| Time Zone | UTC+9 | |
| Audience | - | |
| Data Visualization | widget name | Purchase Funnel (total) |
| Apply global filter | On | |
| Widget type | Table |
Create an advertising performance analysis dashboard
Dashboard configuration
This is a list of widgets required to construct an advertising performance analysis dashboard.
| widget name | Report type | Justice |
| New Install (by Click) | Single Touch Attribution | Number of new installations through advertising media |
| Re-Install (by Click) | Single Touch Attribution | Number of reinstalls via advertising media |
| Deeplink Open | Single Touch Attribution | Number of deep link opens through advertising media |
| Purchase amount (Last Open, LB24h) | General Event | Purchase amount through advertising media (based on last open, lookback window 24h) |
| KPIs by date (Last Open, LB24h) | Single Touch Attribution | Key indicators of advertising media by date (based on last open, lookback window 24h) |
| KPIs by medium (Last Open, LB24h) | Single Touch Attribution | Key indicators of integrated advertising media during the period (based on last open, lookback window 24h) |
Widget Guide
We will guide you through the features of each widget included in the advertising performance dashboard.
New Install (by Click)
Check the number of New Installs through Click Ad-Touch within the selected period.
This is the number of New Installs through advertising media that generated clicks. Since the Platform item was not set in Group by and Analytics Conditions, it includes all New Installs that occurred on Android and iOS.
[[Quote:Information:Normal]] If you set 'Android with Platform' in Analytics Conditions, you can only distinguish New Install figures for Android.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | Single Touch Attribution |
| Table Design | Date Type | Daily |
| Group by | - | |
| Metrics | New Install (by Click) | |
| Conditions | Date Ragne | last week |
| Time Zone | UTC+9 | |
| Audience | - | |
| Analytics Conditions | - | |
| Data Visualization | Apply global filter | On |
| Widget type | Summary | |
| formula | Sum |
Re-Install (by Click)
Check the Re-Install numbers through Click Ad-Touch for the selected period.
This is the number of re-installs through advertising media that generated clicks. Because the Platform item was not set in Group by and Analytics Conditions, all re-installs that occurred on Android and iOS are included.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | Single Touch Attribution |
| Table Design | Date Type | Daily |
| Group by | - | |
| Metrics | Re-Install (by Click) | |
| Conditions | Date Ragne | last week |
| Time Zone | UTC+9 | |
| Audience | - | |
| Analytics Conditions | - | |
| Data Visualization | Apply global filter | On |
| Widget type | Summary | |
| formula | Sum |
Purchase amount
The purchase amount during the selected period is analyzed by advertising inflow channel.
Set each item as follows.
| step | Setting items | Setting result |
| Select Report Type | Report Type | General Event Analytics |
| Table Design | Date Type | Daily |
| Group by | - | |
| Metrics | Price x Quantity | |
| Conditions | Open Attribution Type | New Install, Re-Install, Deeplink Open |
| Event Lookback Window | 1 day | |
| Event Attribution Viewpoint | Last | |
| Date Ragne | last week | |
| Time Zone | UTC+9 | |
| Audience | - | |
| Analytics Conditions |
Event name included purchase Ad Partner not included Organic |
|
| Data Visualization | widget name | Purchase amount |
| Apply global filter | On | |
| Widget type | Summary | |
| formula | Sum |
Restrictions on Dashboard & Widgets
Definary New Data Policy (24. 07. Depending on the criteria (effective from the 01th day), some of the Dashboard's functions may be restricted.
Limit auto-loading of widgets
Automatic data retrieval is limited when the number of events in the previous month exceeds 100 million.
The basic number of event data provided by Definery is 100 million (Count) per month .
Basically, data is automatically retrieved for widgets added or saved within the dashboard, and is limited to manual retrieval when the number of events in the previous month exceeds 100 million. The number of events in the previous month is counted by app, and it may take 2-3 days to determine the exact number of events.
[[Quote:Guide:Normal]] Even if the number of previous month's events exceeds 100 million, you can still use the Definary service.
Maximum number of widgets
Adding widgets to your dashboard may be limited depending on the number provided.
The default number of widgets that can be added in Definery is 20 per dashboard .
If the number of widgets in the existing saved dashboard has already been exceeded, data can be retrieved by deleting widgets.
[[Quote:Guide:General]] For further inquiries regarding limitations on the use of the Dashboard & Widgets, please contact the Definary team ( dfn@igaworks.com ).