Metrics included in this package had to:
-
Have an equivalent metric for both the Apple App Store and Google Play according to documentation found for each of the connector data sources.
For example, we included a field calleddownloads
that occurs astotal_downloads
in the Apple App Store and asdevice_installs
in Google Play. -
Make sense when aggregated at the level of the respective report.
For example, we did not includeactive_devices_last_30_days
from the Apple App Store although there was an equivalent metric in Google Play calledactive_devices_last_30_days
(renamed fromactive_device_installs
). 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 ofactive_devices_last_30_days
if only aggregated by the dimension. This is not the case in Google Play, rendering this metric inconsistent across platforms.
Additionally, we welcome any discussion for fields to include/exclude!
Although the Apple App Store and Google Play packages both have subscription reports, we have decided to not extend this capability in the initial release of the App Reporting roll-up package. Currently, we cannot guarantee the proper aggregating and mapping of subscription events in Apple to active subscriptions, subscription cancellations, and subscription purchases in Google Play.
We are, however, very eager to include this report as a feature in the App Reporting package and welcome any discussion that can help us create it!
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.