1. Home
  2. Replying to Reviews
  3. Connecting your Google Play Developer Console to Appbot

Connecting your Google Play Developer Console to Appbot

To get the most from Appbot, it’s a good idea to link your Google Play Developer Console account and authorize view access. Linking your Developer Console to Appbot allows you to:

  • get app version data for each app review
  • get device data for each app review
  • fetch the complete review history for your Google Play apps.
  • fetch the complete rating history and get ratings breakdowns.
  • reply from within Appbot (limited beta)

In this guide we’ll cover the procedure to link your Google Play Developer Console account to Appbot and how to authorize access to your reviews.

Important – You need to be the Google Play Developer Console account owner to complete this guide.

Setting Up A New Google Play Developer Console Connection

Step 1 – Log in to your Google Developer Console account.


Step 2 – Navigate to ‘Developer Account’ and select ‘API access’.


Step 3 – If you see the ‘Linked Google Cloud project’ section as below, click on ‘Create new project’ button. If you do not, skip to Step 4.

 
Step 4 –  Click on the ‘View project’ link under Linked Google Cloud project

 
Step 5 – On the dashboard click “ENABLE API AND SERVICES”

 
Step 6 – Search for the following API’s and make sure they are all ENABLED:

  • Google Cloud APIs (lets us authenticate you)
  • Google Cloud Storage (allows us to access historical review data)
  • Google Cloud Storage JSON API (also allows us to access historical review data)
  • Google Play Android Developer (allows us to access current review data)


 
Step 7 – Back in your developer console, press ‘CREATE SERVICE ACCOUNT’.

 
Step 8 – Click on ‘Google API Console’ from the popup that appears.

 
Step 9 – When your API console loads, click ‘CREATE SERVICE ACCOUNT’ at the top.


Step 10 – Give the service account a name (this can be anything you want, but it’s a good idea to name it something to do with Appbot so you know what it is in future), and then click ‘Create’.

Step 11 – Under the ‘Select a role’ dropdown, choose ‘Basic’ and select ‘Browser’, then click ‘Done’.

 
Step 12 – Click the three dots and then ‘Create key’, and in the pop-up make sure ‘JSON’ is selected and click ‘Create’.




Step 13 – You should then get a message telling you ‘Private key saved to your computer’ and the private key should begin downloading. Click ‘Close’ on the dialog, then click ‘Done’ on the page. (Clicking the Done button on the dialog back in your developer console will refresh the page and show your what has changed)
 
Step 14 – Back in your Developer Console under ‘API access’ you should now see the Appbot service account you created under the list of service accounts.  Click the ‘GRANT ACCESS’ button next to the Appbot service account you just created.
 
Step 15 –  Account Permissions
Uncheck all except:

  1. View app information and download bulk reports (read-only)‘ – so you’re only giving the Visibility permission to Appbot. This allows us to access the data in the Reports section of your Console account, which is where we obtain the historical review data.
  2. Reply to reviews‘ – so you can reply from within Appbot.

Then press ‘Invite User’.




 
Step 16 – Login to your Appbot account, in the header, click the Cog icon, then click ‘Link App Stores’ from the menu. On the page that loads, press ‘Link a Google Account’.

 
Step 17 – Click ‘Choose File’.

 
Step 18 – Select the private key that was downloaded earlier.

 
Step 19 – Click on the ‘Upload Service Account Key’ button.

 
Step 20 – Head back to your Play Developer Console and navigate to “Download Reports” from the left menu. Click into “Reviews” and select your app from the right.



Step 21 – Click on “Copy Cloud Storage URI”


Step 22 – Back in Appbot, paste the URIs you just copied in and press “Start Fetching”

 

NOTE: Google is currently taking up to 24 hours for the permissions to take effect. If you get an error and are confident all steps above have been completed correctly, then please try again from step 15 in 24 hours.

 
Step 23 – Once it’s loaded you’ll see a message saying “Our bots are completing the account link” and you should see the Authenticated badge on each authenticated app on the Manage Sources page soon.

Step 24 – Enable replies
NOTE: This is currently limited beta functionality for some paid Appbot customers. If you don’t see this option and would like to like to test it please reach out to us.
Back on the Linked Accounts list press on ‘Enable Replies’ next to the Google Service you just added.


Step 25 – Once the new data is fetched you can navigate to the Reviews Page. You will now see extra metadata on reviews for App Version, Device and OS Version.

If you enabled replies then you will see a new option to reply from within Appbot:


 

Adding Replies To An Existing Linked Account

NOTE: This is currently limited beta functionality for some paid Appbot customers. If you don’t see this option and would like to like to test it please reach out to us.
Step 1 – Log in to your Google Developer Console account, choose ‘API access’ and then ‘View access’ on your service account.

Step 2 – Select ‘Account permissions’

Step 3 – Enable ‘Reply to reviews’ and click ‘Save changes’

Step 4 – Go to ‘Step 24’ above to enable replies in Appbot
 
 
If you need any further assistance on linking the Google Play developer console, don’t hesitate to contact us at support@appbot.co with any questions or check out our FAQ section here.­­­­

Who Can Access This Data?

The data collected under the authenticated Google Play app (the version with the green padlock) can only be accessed by users associated with teams that have a linked Google Play Developer Console account associated with that app connected to their team.