Connect Google Search Console
Clicks, impressions, position and top queries for each app's website.
What it unlocks in StoreScope Analytics
- Clicks, impressions, click-through rate, average position, top queries and top pages for each app's website.
The access it needs
| For | Least role or permission |
|---|---|
| Search performance | Restricted (a user on the property, in Settings, Users and permissions) |
- The Google Play service account works: one key can serve Play, Search Console and Google Analytics.
- Each app's website is read from its domain property (sc-domain:) or its https:// URL-prefix property; add the service account to whichever you have.
Steps
- Use a Google service account JSON key (your Play one works). Enable the Search Console API on its project. Enable the API
- In Search Console, Settings, Users and permissions, add the service account's email (Restricted is enough). Open Search Console
- Set each app's website on the Apps page.
- In StoreScope Analytics, open Connections, choose Google Search Console, fill in the form and save. The connection is checked live with the store first; a connection that fails the check is never saved.
What the form asks for
| Field | Note | |
|---|---|---|
| Service account JSON key | optional | |
| Or paste the JSON | optional |
Keys and secrets are stored encrypted and used only for your workspace. Only the non-secret fields are shown back.
Errors the check can show
The exact sentence the Connections page shows, then what to do. Italic words are filled in with your own values.
The service account JSON is required.
Upload the JSON key file you downloaded from Google Cloud, or paste its contents.
the uploaded JSON: not valid JSON
The file is not the key file, or the paste was cut short. Download the key again (Google Cloud, IAM and Admin, Service accounts, the account, Keys, Add key, JSON).
service account JSON is missing client_email/private_key
This is not a service account key file (an OAuth client file looks similar). Create a JSON key for the service account.
Upload a service account key ("type": "service_account"), not a user credential.
A personal sign-in file was uploaded. Only a service account key is accepted.
The key works but sees no property: add service account e-mail as a user in Search Console.
Add that e-mail in Search Console, Settings, Users and permissions, then connect again.
Enable the Search Console API on the service account's Google Cloud project, then try again.
Enable the API on the project the key belongs to; it can take a few minutes to apply.
Search Console answered status.
Google answered something unexpected. Try again in a few minutes.
Errors any connection can show are on Connect your stores.