This page contains the setup guide and reference information for the google search console source connector.
- Credentials to a Google Service Account (or Google Service Account with delegated Domain Wide Authority) or Google User Account
You can either:
- Use the existing
Service Account
for your Google Project with granted Admin Permissions - Use your personal Google User Account with oauth. If you choose this option, your account must have permissions to view the Google Search Console project you choose.
- Create the new
Service Account
credentials for your Google Project, and grant Admin Permissions to it - Follow the
Delegating domain-wide authority
process to obtain the necessary permissions to your google account from the administrator of Workspace
A service account's credentials include a generated email address that is unique and at least one public/private key pair. If domain-wide delegation is enabled, then a client ID is also part of the service account's credentials.
- Open the Service accounts page
- If prompted, select an existing project, or create a new project.
- Click
+ Create service account
. - Under Service account details, type a
name
,ID
, anddescription
for the service account, then clickCreate
.- Optional: Under
Service account permissions
, select theIAM roles
to grant to the service account, then clickContinue
. - Optional: Under
Grant users access to this service account
, add theusers
orgroups
that are allowed to use and manage the service account.
- Optional: Under
- Go to API Console/Credentials, check the
Service Accounts
section, click on the Email address of service account you just created. - Open
Details
tab and findShow domain-wide delegation
, checkmark theEnable Google Workspace Domain-wide Delegation
. - On
Keys
tab click+ Add key
, then clickCreate new key
.
Your new public/private key pair should be now generated and downloaded to your machine as <project_id>.json
you can find it in the Downloads
folder or somewhere else if you use another default destination for downloaded files. This file serves as the only copy of the private key. You are responsible for storing it securely. If you lose this key pair, you will need to generate a new one!
- Go to API Console/Credentials, check the
Service Accounts
section, click on the Email address of service account you just created. - Click on
Details
tab and findShow domain-wide delegation
, checkmark theEnable Google Workspace Domain-wide Delegation
. - On
Keys
tab click+ Add key
, then clickCreate new key
.
Your new public/private key pair should be now generated and downloaded to your machine as <project_id>.json
you can find it in the Downloads
folder or somewhere else if you use another default destination for downloaded files. This file serves as the only copy of the private key. You are responsible for storing it securely. If you lose this key pair, you will need to generate a new one!
You can return to the API Console/Credentials at any time to view the email address, public key fingerprints, and other information, or to generate additional public/private key pairs. For more details about service account credentials in the API Console, see Service accounts in the API Console help file.
Follow the Google Documentation for performing Delegating domain-wide authority to create a Service account with delegated domain-wide authority. This account must be created by an administrator of your Google Workspace. Please make sure to grant the following OAuth scopes
to the service user:
https://www.googleapis.com/auth/webmasters.readonly
At the end of this process, you should have JSON credentials to this Google Service Account.
- Log into your Airbyte Cloud account.
- In the left navigation bar, click Sources. In the top-right corner, click +new source.
- On the Set up the source page, enter the name for the google search console connector and select google search console from the Source type dropdown.
- Click Authenticate your account to sign in with Google and authorize your account.
- Fill in the
site_urls
field. - Fill in the
start date
field. - You should be ready to sync data.
- Fill in the
service_account_info
andemail
fields for authentication. - Fill in the
site_urls
field. - Fill in the
start date
field. - You should be ready to sync data.
The google search console source connector supports the following sync modes:
Feature | Supported?(Yes/No) | Notes |
---|---|---|
Full Refresh Sync | Yes | |
Incremental Sync | Yes | except Sites and Sitemaps |
SSL connection | Yes | |
Namespaces | No |
- Sites
- Sitemaps
- Full Analytics report (this stream has a long sync time because it is very detailed, use with care)
- Analytics report by country
- Analytics report by date
- Analytics report by device
- Analytics report by page
- Analytics report by query
This connector attempts to back off gracefully when it hits Reports API's rate limits. To find more information about limits, see Usage Limits documentation.
Integration Type | Airbyte Type | Notes |
---|---|---|
string |
string |
|
number |
number |
|
array |
array |
|
object |
object |
Version | Date | Pull Request | Subject |
---|---|---|---|
0.1.12 |
2022-05-04 | 12482 | Update input configuration copy |
0.1.11 |
2022-01-05 | 9186 9194 | Fix incremental sync: keep all urls in state object |
0.1.10 |
2021-12-23 | 9073 | Add slicing by date range |
0.1.9 |
2021-12-22 | 9047 | Add 'order' to spec.json props |
0.1.8 |
2021-12-21 | 8248 | Enable Sentry for performance and errors tracking |
0.1.7 |
2021-11-26 | 7431 | Add default end_date param value |
0.1.6 |
2021-09-27 | 6460 | Update OAuth Spec File |
0.1.4 |
2021-09-23 | 6394 | Update Doc link Spec File |
0.1.3 |
2021-09-23 | 6405 | Correct Spec File |
0.1.2 |
2021-09-17 | 6222 | Correct Spec File |
0.1.1 |
2021-09-22 | 6315 | Verify access to all sites when performing connection check |
0.1.0 |
2021-09-03 | 5350 | Initial Release |