Aggregation and timeline for the datasets in the apps and games report
Appropriate roles: Executive report viewer | Report viewer
The following table displays the aggregation and timeframe applicable for the datasets in the Apps and Games report.
Note
The items marked with an asterisk (*) are timeframe additions as part of Downloads hub and applicable for only single app download.
| Data | Frequency | Downloads hub export for all apps | Downloads hub export for single apps |
|---|---|---|---|
| Acquisition | Daily | 30 days 3 months |
30 days 3 months |
| Hourly | 72 hours | 72 hours | |
| Weekly | 6 months 12 months |
6 months 12 months |
|
| Monthly | 4 years (2,3,4)* | ||
| Add-on acquisition | Daily | 30 days 3 months |
30 days 3 months |
| Weekly | 6 months 12 months |
6 months 12 months |
|
| Monthly | 4 years (2,3,4)* | ||
| Usage | Daily | 30 days 3 months |
30 days 3 months |
| Monthly | 6 months 12 months |
6 months 12 months 4 years (2,3,4)* |
|
| Health | Hourly | 72 hours | 72 hours |
| Monthly | 30 days* | ||
| Channel and conversion | Daily | 30 days 30 months |
30 days 30 months |
| Weekly | 6 months 12 months |
6 months 12 months |
|
| Monthly | 4 years (2,3,4)* | ||
| Install | Daily | 30 days 30 months |
30 days 30 months |
| Weekly | 6 months 12 months |
6 months 12 months |
|
| Monthly | 4 years (2,3,4)* | ||
| Wishlist | Snapshot | ||
| Reviews | None | 30 days | 30 days 1 year* |
| Ratings | Daily | 30 days 30 months |
30 days 30 months |
| Weekly | 6 months 12 months |
6 months 12 months |
|
| Monthly | 4 years (2,3,4)* |
Date and filter options calculation
| Dataset | Filter options | How is it calculated? |
|---|---|---|
| Date Filter for all the Datasets except Usage | Last 72 hours (Default) Last 30 days Last 3 months Last 6 months Last 12 months Last 2 years Last 3 years Last 4 years |
The number of hours, days, months, or years are determined by calculating the duration from the current timestamp backward by the specified period. Examples: Hourly: If the current timestamp is August 6, 2024, 3:00 PM, the last 72 hours would be between August 3, 2024, 3:00 PM and August 6, 2024, 3:00 PM. Monthly: If the current date is August 6, 2024, then last 6 months would be between February 6, 2024 and August 6, 2024 Yearly: If current date is August 6, 2024, then last 2 years are between August 6, 2022 and August 6, 2024 |
| Daily Usage | Last 30 days (Default) Last 3 months |
The last 30 days are calculated as the period between 30 days before the current date and the current date. Example: If the current date is Aug 6, 2024, the last 30 days are calculated as the period between July 7, 2024 and August 6, 2024. |
| Monthly Usage | Last 6 months (Default) Last 12 months Last 2 years Last 3 years Last 4 years |
The last 6 months are calculated as the period between 6 months before the current date and the current date. Example: If the current date is Aug 6, 2024, the last 6 months are calculated as the period between February 6, 2024 and August 6, 2024. |
Limits to consider
- Favorites: 30 per program
- Templates: 200 per program
Understand the totalRecurrenceCount field for scheduled reports
Today, partners can choose to either:
- Download the report immediately for one-time use via Download now, or
- Set the reports to be downloaded at regular intervals over a specified period via Schedule reports.
The totalRecurrenceCount field is essential for tracking the number of times a scheduled report is executed within a predefined time frame. This field is primarily used for scheduled reports, allowing publishers easy access to reports at regular intervals.
In cases where a report is scheduled to run only once, the totalRecurrenceCount field will have a value of "1" to indicate the execution count. This differs from "download now" reports, which are executed immediately and do not use this field.
Whether reports are created via Partner Center or public APIs, there are two ways to calculate totalRecurrenceCount:
- When the user provides a start date and the number of recurrences, the number of recurrences is saved directly as the totalRecurrenceCount.
- When the user provides a start date, end date, and report frequency, the system automatically computes the totalRecurrenceCount based on the provided interval.
The totalRecurrenceCount field helps publishers ensure that critical data reports are generated and delivered at scheduled intervals without missing executions. It also aids in troubleshooting and tracking report execution patterns.
Restrictions on the scheduling of reports
Because scheduling of the reports results in preparing the report for download, there's opportunity for the scheduling of the reports to be misused. To avoid such scenarios, there are two-level restrictions on the scheduling of the reports:
Program level total scheduled reports count:
- Level 1: Per program: 40 scheduled reports per user
- Level 2: Allowed maximum time range restriction when scheduled reports are selected
| Scheduling frequency | Month time range allowed |
|---|---|
| Hourly | Last 30 days |
| Daily | Last 30 days |
| Weekly | Last 30 days |
| Monthly | Last two years |
| Yearly | Lifetime or last years (as applicable) |
Users can't create more than allowed count of scheduled reports and the time range has to comply, as shown in the scheduling frequency.
Scheduled report execution limits
- Hourly: 30 Days (720 executions)
- Daily: Six months (180 executions)
- Weekly: One year (52 executions)
- When the selection for daily is more than seven days
- Monthly: Two years (24 executions)
- Yearly: Five years (five executions)