Google Ads
Use the Google Ads connector to sync campaign, ad group, and performance metrics into your Athena lakehouse. Blotout runs the Airbyte Google Ads connector inside your deployment.
For connector reference (streams, rate limits, changelog), see the Airbyte Google Ads docs.
Prerequisites
Section titled “Prerequisites”- A tag with Blotout Cloud set up (green checkmark in the Tags table)
- A Google Ads account linked to a Google Ads Manager account
- Access to the Google account that manages the Ads account you want to sync
For self-hosted Open Source setups, Google also requires a Developer Token (Basic or higher — test tokens cannot read production data). See Apply for a developer token in the Airbyte docs.
Create the pipeline
Section titled “Create the pipeline”Follow the shared Create a pipeline steps until the source catalogue appears, then select Google Ads.
Source configuration
Section titled “Source configuration”On the Source step, configure the connector:
| Field | Purpose |
|---|---|
| Schedule Type | How the pipeline runs — typically Scheduled |
| Sync Frequency | How often Airbyte syncs (for example, Every 24 hours) |
| Source Name | Name for this pipeline — used in the Athena schema <SOURCE_NAME>_<ENV> |
Authentication (OAuth)
Section titled “Authentication (OAuth)”Blotout Cloud authenticates Google Ads with OAuth. Prefer automatic sign-in:
- Under Google Ads authentication, click Sign in with Google.
- Log in with the Google account that has access to the Ads / Manager account you want to sync.
- Approve the requested Google Ads API permissions when prompted.
- Continue to the remaining connector fields (for example, customer ID / manager account) as shown in the form after authentication.
You can instead enter OAuth credentials manually (Client ID, Client Secret, Refresh Token, and optionally Access Token). Prefer Sign in with Google unless your Blotout administrator has provided credentials for manual setup.
OAuth scope for the Google Ads API: https://www.googleapis.com/auth/adwords
Complete Schema and Summary
Section titled “Complete Schema and Summary”Continue through the Schema and Summary steps to choose streams and confirm the connection. Save and run the first sync.
After a successful sync, Airflow creates an organization-scoped DAG for the pipeline (for example, {org}_google_ads).
Related documentation
Section titled “Related documentation”- Data Pipelines overview — Tags-first create flow
- Airflow — DAG schedules and monitoring
- Airbyte Google Ads — streams, developer token, and connector reference