Google Play is an online platform by Google that provides access to apps, games, music, movies, and books for Android devices. It offers a wide range of digital content and serves as a one-stop shop for entertainment and utility needs on Android smartphones and tablets.
Show more...
Due to Google Play API delay of up to 4-5 days, the most recent data for Google Play metrics might not be displayed in Databox. Google Play can also decide to withhold Ratings and Reviews for up to 24 hours if they notice any suspicious activity on the Google Play account. This can also result in the most recent data from Google Play missing in Databox.
A number of metrics for the Google Play integration are Non-Aggregatable. This means that due to the nature of these metrics, summing daily/weekly/monthly values will not give correct results for total value of longer time periods.
These metrics are:
No-reset metrics (metrics that are not reset to value 0 with every new day) for the Google Play integration are:
The ‘Invalid grant’ error may be returned for the following reasons
1. The user has revoked your access.
Interpretation This happens when the user who connected the Google data source in Databox has their permissions changed or revoked to the Google account. Since Databox gains access to your Google data through this user, it is imperative that they have the necessary permissions.
Resolution Contact an Admin in your Google account to restore your original user permissions. Once that’s complete, navigate to the Data manager section in Databox and click the Reconnect button to reconnect your Google data source.
2. The refresh token has not been used for six months
Interpretation This happens when your refresh token is inactive. It is rare that this will be the reason for the error in Databox. However, if your account expires or you have no Google metrics used anywhere in your account, this could be the case.
Resolution Navigate to the Data manager section in Databox and click the Reconnect button to reconnect your Google data source and establish an active refresh token.
3. The user changed passwords, and the refresh token contains Gmail scopes
Interpretation This happens when the user that connected the Google data source in Databox changes their Google password. Since Databox gains access to your Google data through this user’s credentials, it is imperative that they are up-to-date.
Resolution Navigate to the Data manager section in Databox and click the Reconnect button to reconnect your Google data source with your updated credentials.
4. The user has exceeded the maximum number of granted (live) refresh tokens
This is the most common reason why the ‘Invalid Grant’ error is returned from the Google data sources.
Interpretation A user can have a maximum of 100 active Google connections at once. Once the 101st connection is initiated, the user’s connection limit is exceeded. When this happens, the oldest Google connection (i.e., the 1st connection made by the user) is automatically disconnected. If the same user connects a 102nd Google account, the 2nd connection they made will automatically become disconnected as well. This will continue in order to ensure that a single Google user only has a maximum of 100 active Google connections at any given time.
Resolution In order to resolve this error and prevent future occurrences, you’ll need to limit the number of connections that each Google user makes. If needed, you can create additional users in Google and use those to add more Google connections. For example, you may make it part of your process to create a new Google user for every 85 connections. (this will give you some margin for error). Once you’ve established 85 connections with that Google user, you can create a new user and continue adding connections.
Google generates individual reports on a daily basis. The reports are stored in the Google Play Developer account’s private Google Cloud Storage bucket. Databox downloads those reports as part of the syncing process. If a report does not exist (i.e. it was not generated by Google), it will not be found, and the API will return a 404 error that Databox will capture and display as the custom message ‘Report for selected interval not found’.
If this error is displayed, check if reports for the selected Date Range are available. If there are no reports in the Google Cloud Storage for the selected Date Range, change the Date Range in Databox to a Date Range for which reports are available in Google Cloud Storage and the data will be displayed.
In order to be able to connect Google Play to Databox, the Google user that is connecting Google Play needs to have the necessary permissions to access the bucket and view/download files from the relevant Google Cloud Storage. Google Cloud Storage access is managed in the IAM Tool.