☆ Understanding and examples of DFINERY analysis structure
FollowOverview
- All analysis results provided by DFINERY can be viewed in the Data Explorer menu and saved as a report.
- Check the desired analysis results in the Analytics > Data Explorer menu and save them as a report.
- Saved reports can be loaded as widgets from the Analytics > Dashboard menu.
Understanding the Analysis Structure
- Data Explorer ’s report is It consists of a combination of Group by, Metric, and Condition .
- After selecting a report type, you can combine three search items to view the data you want.
Group by
Group by Ran This refers to the condition for calculating data with the same value by grouping them on the horizontal axis (Row). Up to 3 items can be set as sub-group by. for example, You can check the report with a three-level drill-down structure, such as Platform > Ad Partner > Tracking Link Name (ID) .
- Group by condition items are as follows.
[[Quote: Guide: Small]] In case the data analysis results are adjusted according to the attribution Conditions settings in Group by, ‘O’ is indicated.
Justice | Apply attribution conditions | |
Data Range | Data Analysis Period Unit | - |
Platform | Android, iOS distinction | - |
Ad Partner | Classification of advertising media operated | O |
Tracking Link Name | Issued tracking link name | O |
Event Name | Linked event name (app open, purchase, etc.) | - |
Order ID | purchase order number | - |
Product ID | Product ID | - |
Product Name | product name | - |
Payment Method | payment method | - |
Category 1~5 | Product Category | - |
Campaign (adv) |
Parameters issued when issuing a tracking link
(Entered directly by the advertising operator) |
O |
Ad (adv) | " | O |
Ad Group (adv) | " | O |
Creative (adv) | " | O |
Keyword (adv) | " | O |
Placement (adv) | " | O |
Cost Model (adv) | " | O |
Agency (adv) | " | O |
Country (IP) | Country name based on IP information | - |
City (IP) | City name based on IP information | - |
Region (IP) | Region name based on IP information | - |
Country (Device) | Country name set on the device | - |
Language (Device) | Language name set on the device | - |
Campaign (m) |
Parameters issued when issuing a tracking link
(Input from advertising media) |
O |
Publisher (m) | " | O |
Sub Publisher (m) | " | O |
Ad (m) | " | O |
Ad Group (m) | " | O |
Creative (m) | " | O |
Keyword (m) | " | O |
Placement (m) | " | O |
Cost Model (m) | " | O |
Agency (m) | " | O |
utm_source |
Parameters issued when issuing a tracking link
(Entered directly by the advertising operator) |
O |
utm_medium | " | O |
utm_campaign | " | O |
utm_term | " | O |
utm_content | " | O |
OS | OS version of the app | - |
Model | Device model name | - |
Vendor | Device manufacturer name | - |
Resolution | Device resolution information | - |
Portrait | App screen orientation information | - |
Network | Network status information | - |
wifi only |
true for devices that only support wifi, false if mobile network is supported |
- |
Carrier | News agency name | - |
SDK version | Definary SDK Version Information | - |
App version | App version information | - |
Installer | The installer value that caused the app installation. | - |
[[Quote:Danger:Small]]
- The more detailed the Group by
is and the longer the query period range, the more rows there will be.
- If there are a large number of rows, the report may not be displayed.
- The maximum time to attempt a query is 5 minutes, and if the query is not completed within 5 minutes, the report cannot be checked.
- If the report is not confirmed, please try again after reducing the Group by step or the search period range.
Metric
What is Metric ? It refers to the vertical axis (Column) result indicator that shows the analysis result of the Group by condition. For example, the Group by condition New Install figures , or Specific event figures , etc. You can check by adding it as a metric . It is provided in each report type. Metric items are different.
Metric items provided by each report type and examples of interpretation by situation can be found in more detail in the guide below.
- Single Touch Attribution, report examples and interpretation
- General Event Analytics, report examples and interpretation
- Universal Retention Analytics, report examples and interpretation
- Conversion Funnel, report examples and interpretation
Conditions
Conditions refers to items that set conditions that specify analysis items, such as the period of the constructed report and audience group. Each condition item provided by Conditions is as follows.
-
Data range
Determine the time period for analysis. It can be limited to hours.
-
Time Zone
Select the time zone to analyze. All analysis results can be set to Coordinated Universal Time (UTC) units.
-
Audience
Analysis is performed on specific audience groups created through Audience Studio .
-
Analytics Conditions
You can select or exclude events, inflow channels, device information, etc. that are analysis conditions. For example, you can analyze only purchase events or only users who came through advertising media.
-
Attribution Conditions
Attribution conditions are items that set performance contribution standards for each inflow channel . For example, you can identify and analyze only purchase results that occurred within 48 hours after New Install for each inflow channel.
Screen Description: Among all Open Attribution Types, only events within 7 days after the Last Open are aggregated and reported as performance of the inflow channel.
-
Open Attribution Type
New Install / Re-Install / Deeplink Open
Choose open type through inflow channel.
For example, if you select only Re-Install, only events (purchases, logins, etc.) that occur after Re-Install through an inflow channel will be recognized and analyzed as performance of that inflow channel.
-
Event Lookback Window
1 hour ~ 31 days
Set attribution windows for analyzing event performance measurements.
For example, if you select Re-Install as Open Attribution Type and 2 days as Event Lookback Window, the event occurred by a user who re-installed through inflow channels such as advertising within the past 48 hours based on the time of occurrence of the selected event. Only results (purchase, login, etc.) are recognized and analyzed as the performance of each inflow channel.
-
Event Attribution View Point
First / Last
Set the order of app open attribution that contributed to event performance measurement.
For example, if you select Re-Install as the Open Attribution Type, 2day as the Event Lookback Window, and Last as the Event Attribution View Point, the event results (purchase, login, etc.) of the 'last' user to perform a Re-Install among users who have performed a Re-Install through a specific channel within the past 48 hours from the event occurrence time will be recognized and analyzed as the performance of the corresponding inflow channel.
Report Type
DFINERY provides separate report types for ease of analysis.
-
Single Touch Attribution
Provides attribution analysis metrics needed to evaluate the ROI of inbound channels.
-
General Event Analytics
Provides metrics for analyzing events that occur within the app.
-
Universal Retention Analytics
Analyze the retention of the target event based on the standard event.
Any event set in the app can be analyzed by setting it as a standard/target event.
Any event set in the app can be analyzed by setting it as a standard/target event.
-
Conversion Funnel
Design and analyze the conversion flow of the funnel structure using events set in the app.
Restrictions on use of reports
According to the new Definary data policy (effective from 24.07.01), some of the reporting functions of Data Explorer may be limited.
Limit automatic report loading
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 when a newly created or saved report is viewed, 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.
You can manually search individual reports by clicking the 'Data Search' button in the report manual search screen, and the global search button only works on widgets where data search has been completed.
[[Quote:Guide:Normal]] Even if the number of previous month's events exceeds 100 million, you can still use the Definary service.