You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.**Have an equivalent metric for both the Apple App Store and Google Play according to documentation found for each of the connector data sources.**<br>
6
+
For example, we included a field called `downloads` that occurs as `total_downloads` in the Apple App Store and as `device_installs` in Google Play.<br>
7
+
8
+
2.**Make sense when aggregated at the level of the respective report.**<br>
9
+
For example, we did not include `active_devices_last_30_days` from the Apple App Store although there was an equivalent metric in Google Play called `<insert metric name>`. This is because in the Apple App Store, this metric is typically aggregated by a dimension and source type, therefore, we cannot guarantee that there will not be any duplication in counts of `active_devices_last_30_days` if only aggregated by the dimension.
10
+
11
+
Additionally, we welcome any [discussion](https://github.com/fivetran/dbt_app_reporting/discussions/6) for fields to include/exclude!
12
+
13
+
## Excluding Subscription Report
14
+
Although the Apple App Store and Google Play both have subscription reports for each package, we have decided to not include this capability in the initial release. Currently, we cannot guarantee the proper mapping of subscription events that belong in the top major categories such as active subscriptions, subscription cancellations and subscription activations in the Apple App Store reports.
15
+
16
+
We are, however, very eager to include this report as a feature in the App Reporting package and welcome any [discussion](https://github.com/fivetran/dbt_app_reporting/discussions/7) that can help us create it!
17
+
18
+
## Metrics Naming
19
+
We made the design decision to keep each respective packages' naming convention as close to their original reporting as possible, making small tweaks where necessary. However, for this roll up package, we chose the column names that best represented the data field across both packages.
description: Each record in this table represents the daily count of deletions and crashes by app_platform, app_name and app_version.
8
+
columns:
9
+
- name: date_day
10
+
description: '{{ doc("date_day") }}'
11
+
- name: app_platform
12
+
description: '{{ doc("app_platform") }}'
13
+
- name: app_name
14
+
description: '{{ doc("app_name") }}'
15
+
- name: app_version
16
+
description: '{{ doc("app_version") }}'
17
+
- name: deletions
18
+
description: '{{ doc("deletions") }}'
19
+
- name: crashes
20
+
description: '{{ doc("crashes") }}'
21
+
22
+
- name: app_reporting__country_report
23
+
description: Each record in this table represents the daily count of downloads, deletions and page_views by app_platform, app_name, country, region and sub_region.
24
+
columns:
25
+
- name: date_day
26
+
description: '{{ doc("date_day") }}'
27
+
- name: app_platform
28
+
description: '{{ doc("app_platform") }}'
29
+
- name: app_name
30
+
description: '{{ doc("app_name") }}'
31
+
- name: country_long
32
+
description: '{{ doc("country_long") }}'
33
+
- name: country_short
34
+
description: '{{ doc("country_short") }}'
35
+
- name: region
36
+
description: '{{ doc("region") }}'
37
+
- name: sub_region
38
+
description: '{{ doc("sub_region") }}'
39
+
- name: downloads
40
+
description: '{{ doc("downloads") }}'
41
+
- name: deletions
42
+
description: '{{ doc("deletions") }}'
43
+
- name: page_views
44
+
description: '{{ doc("page_views") }}'
45
+
46
+
- name: app_reporting__device_report
47
+
description: Each record in this table represents the daily count of downloads and deletions by app_platform, app_name and device.
48
+
columns:
49
+
- name: date_day
50
+
description: '{{ doc("date_day") }}'
51
+
- name: app_platform
52
+
description: '{{ doc("app_platform") }}'
53
+
- name: app_name
54
+
description: '{{ doc("app_name") }}'
55
+
- name: device
56
+
description: '{{ doc("device") }}'
57
+
- name: downloads
58
+
description: '{{ doc("downloads") }}'
59
+
- name: deletions
60
+
description: '{{ doc("deletions") }}'
61
+
62
+
- name: app_reporting__os_version_report
63
+
description: Each record in this table represents the daily count of downloads, deletions and crashes by app_platform, app_name and os_version.
64
+
columns:
65
+
- name: date_day
66
+
description: '{{ doc("date_day") }}'
67
+
- name: app_platform
68
+
description: '{{ doc("app_platform") }}'
69
+
- name: app_name
70
+
description: '{{ doc("app_name") }}'
71
+
- name: os_version
72
+
description: '{{ doc("os_version") }}'
73
+
- name: downloads
74
+
description: '{{ doc("downloads") }}'
75
+
- name: deletions
76
+
description: '{{ doc("deletions") }}'
77
+
- name: crashes
78
+
description: '{{ doc("crashes") }}'
79
+
80
+
- name: app_reporting__overview_report
81
+
description: Each record in this table represents the daily count of downloads, deletions, page_views and crashes by app_platform and app_name.
82
+
columns:
83
+
- name: date_day
84
+
description: '{{ doc("date_day") }}'
85
+
- name: app_platform
86
+
description: '{{ doc("app_platform") }}'
87
+
- name: app_name
88
+
description: '{{ doc("app_name") }}'
89
+
- name: downloads
90
+
description: '{{ doc("downloads") }}'
91
+
- name: deletions
92
+
description: '{{ doc("deletions") }}'
93
+
- name: page_views
94
+
description: '{{ doc("page_views") }}'
95
+
- name: crashes
96
+
description: '{{ doc("crashes") }}'
97
+
98
+
- name: app_reporting__traffic_source_report
99
+
description: Each record in this table represents the daily count of downloads and page_views by app_platform, app_name and traffic_source_type.
{% docs app_platform %} The name of the App Platform and will either be 'apple_store' or 'google_play.' {% enddocs %}
6
+
7
+
{% docs app_version %} The app version of the app that the user is engaging with. {% enddocs %}
8
+
9
+
{% docs country_long %} The long country name for this record; the value is either the App Platform's notation or defaults to ISO-3166 naming. {% enddocs %}
10
+
11
+
{% docs country_short %} The short 2-character name for this record's country; countries that are not officially included in ISO-3166 are not included. For example, Google Play includes records from two unofficial ISO-3166 countries, XK and AN. {% enddocs %}
12
+
13
+
{% docs crashes %} The number of recorded crashes experienced (User Opt-In only); a value of 0 indicates there were 0 crash reports or no value from the source report that day. {% enddocs %}
14
+
15
+
{% docs deletions %} A deletion occurs when a user removes your app from their device (User Opt-In only). A value of 0 indicates there were 0 deletions or no value from the source report that day. {% enddocs %}
16
+
17
+
{% docs device %} Device type associated with the respective metric(s). {% enddocs %}
18
+
19
+
{% docs downloads %} The number of times your app has been downloaded onto a user's device. An individual user can have multiple device installs. {% enddocs %}
20
+
21
+
{% docs page_views %} The number of times your app listing was viewed. {% enddocs %}
22
+
23
+
{% docs os_version %} The operating system version of the device engaging with your app. {% enddocs %}
24
+
25
+
{% docs region %} The UN Statistics region name assignment. ([Original Source](https://github.com/lukes/ISO-3166-Countries-with-Regional-Codes/blob/master/all/all.csv)) {% enddocs %}
26
+
27
+
{% docs sub_region %} The UN Statistics sub-region name. ([Original Source](https://github.com/lukes/ISO-3166-Countries-with-Regional-Codes/blob/master/all/all.csv)) {% enddocs%}
28
+
29
+
{% docs traffic_source_type %} The original source that was credited for directing traffic to your target (e.g. directed users to a page view or a download). For detailed descriptions, please refer to the [Apple App Store](https://github.com/fivetran/dbt_apple_store_source/blob/main/models/docs.md) or [Google Play](https://github.com/fivetran/dbt_google_play_source/blob/main/models/docs.md) docs. {% enddocs %}
0 commit comments