Google Play Console Integration

Setup takes about 15 minutes and consists of two parts: first you prepare access in Google Cloud (done once), then you connect it in ASOMobile.

💡 If you run into an unclear authorization error at any step, repeat that step in an incognito window. This rules out conflicts with other Google accounts signed in to your browser. Also, always make sure the correct project is selected.

Go to Google Cloud Console and select a project in the list at the top of the screen.

If you already have a project linked to Google Play Console (it is usually called Google Play Console Developer), use it.
​

If you have no projects, create a new one (New Project). Project name — enter any name that is clear to you. Parent resource — select your organization (if you have one).
​

Select the created project in the list at the top of the screen.

In the left menu ☰, open APIs & Services → Library,

find Google Play Android Developer API

select it in the results list and click Enable.

If you see a Manage button instead of Enable, the API is already enabled — nothing to do here.
​

An enabled API looks like this:

Open Google Auth Platform: click the ☰ menu in the top-left corner → APIs & Services → OAuth consent screen (or Google Auth Platform). Or use the direct link: console.cloud.google.com/auth/overview
​

If you don't see this item, check that the correct project is selected at the top (Step 1) and the API is enabled (Step 2).
​

If you see the message "Google Auth Platform not configured yet",

click Get started and fill in the setup wizard:

Then open the Branding tab and scroll down to the App domain section — you need to fill in two required fields here: Application home page and Application privacy policy link.

💡 The easiest way: take the domain from the Authorized domains section just below (it is usually added there automatically) and paste it with the https:// prefix into both fields. If the Authorized domains section is empty, add your website's domain there and use it in both fields.

Click Save. Without these fields, Google will not let you switch the app to In production in the next step.

​If Google Auth Platform has already been configured earlier, just move on to the next step.
​

Open Google Auth Platform → Audience. If the Publishing status says Testing, click Publish app.

💡 If the Publish app button is inactive, hover over it: a tooltip will list exactly which fields are missing. To switch to production, App name, User support email, Application home page, and Application privacy policy link are required — all of them are filled in on the Branding page (Step 3). If all fields are filled in but the Save button on the Branding page is inactive (the form thinks there is nothing to save), make any change — for example, add a character to the App name — click Save, then restore the original name and save again. After that, refresh the Audience page (Ctrl+Shift+R / Cmd+Shift+R).
​

This matters: in Testing status, the granted access is valid for only 7 days, after which the integration stops working. Google's app verification is not required for this.
​

The end result:

2. Application type — select Desktop app.

3. Name — any clear name, e.g. "ASOMobile My App".

4. Click Create.
​

A window with the Client ID and Client Secret will appear.
​

⚠️ Copy both values to a safe place right away. Google shows the Client Secret only once — at the moment the client is created. If the secret is lost, you will have to create a new secret for the client, or a new client.

2. Click "Add Google Play Console account".

3. Select one or several apps. ​Important! If you select several apps, they must all be available in the Google Play Console account you used for the Google Cloud setup in the previous steps. If your apps are spread across different Google Play Console accounts, you need to complete the integration, with all its steps, for each of them.

4. Paste the Client ID and Client Secret saved in Part 1 (Step 5) and click "Next".

5. Click the "Click to get the link" link.
​

6. A Google sign-in window will open — choose the account that has access to Play Console (see "Before you start") and click "Allow".
​

Google may show the warning "Google hasn't verified this app". This is normal: you are authorizing your own app, the one you created in Part 1 (Step 5). Click Advanced → Go to … and allow access.

After you confirm, the browser will open an error page (for example, "401") — this is expected. You don't need the page itself, only its address: copy the full link from the browser address bar — it contains the authorization code. It is important to copy the link in full!

7. Paste the link into the input field in ASOMobile labeled "paste the received link".

8. Click "Add Google Play Console integration". The status will change to "Connected".
​

⚠️ Important! The code in the link is single-use and valid for about 2 minutes. If you didn't finish connecting in time, go back to Step 4, get a new link, and repeat.

Error at the Google sign-in stage. Repeat the authorization in an incognito window and make sure you selected the account that has Play Console access.

​"Access blocked" or the app is blocked. Check that the consent screen is configured (Part 1, Step 3) and the publishing status is In production (Part 1, Step 4).

​The integration is connected, but replies to reviews are not sent. Check in Play Console (Users and permissions) that the account has the "Reply to reviews" permission for the selected apps.

​The integration stops working after about a week. The OAuth app is still in Testing status. Publish it (Part 1, Step 4) and connect the integration again.

​The Client Secret is lost. Create a new secret or a new client in Google Auth Platform → Clients and reconnect the integration with the new credentials.