Source connector

Google Ads connector

Google Ads integration for databases, warehouses and BI tools

Paid media source for campaign and conversion metrics. Datrise captures Google Ads entities such as campaigns, ad groups, spend, clicks, conversions, and attribution signals, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Google Ads API v22 (GoogleAdsService, gRPC/REST) authenticates with OAuth 2.0, incremental runs key on change_status.last_change_date_time (ChangeStatus resource), and Google Ads caps calls at 15,000 operations/day for Test and Basic access (both test and production accounts); Explorer access is capped at 2,880 operations/day in production; Standard access has no fixed daily operation cap but is still subject to system rate limits.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `google_ads_campaigns`) with a schema derived from the Google Ads API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Google Ads pipeline page, and join the waitlist to get the Google Ads connector (Ads) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Google Ads data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
campaigns	google_ads_campaigns	Upsert by primary key, incremental on updated-at
ad groups	google_ads_ad_groups	Upsert by primary key, incremental on updated-at
spend	google_ads_spend	Upsert by primary key, incremental on updated-at
clicks	google_ads_clicks	Append-only, incremental by timestamp
conversions	google_ads_conversions	Upsert by primary key, incremental on updated-at
attribution signals	google_ads_attribution_signals	Upsert by primary key, incremental on updated-at

Google Ads API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Google Ads API v22 (GoogleAdsService, gRPC/REST)
Authentication	OAuth 2.0 — OAuth 2.0 (service account or user consent) plus a per-project developer token on every call, with `login-customer-id` set for manager-account (MCC) access.
Pagination	token — `GoogleAdsService.Search`/`SearchStream` use a fixed 10,000-row page in v19+ (`page_size` can no longer be set); page with `next_page_token` until a response omits it.
Rate limit	15,000 operations/day for Test and Basic access (both test and production accounts); Explorer access is capped at 2,880 operations/day in production; Standard access has no fixed daily operation cap but is still subject to system rate limits
Incremental cursor	change_status.last_change_date_time (ChangeStatus resource) — ChangeStatus only covers a rolling 90-day window and returns at most 10,000 rows per query (LIMIT), with up to a 3-minute propagation delay, so most connectors pair it with `segments.date`-filtered reports for older history.
Webhooks	No
Bulk export	No
Deletes detectable	Yes — Query the `change_status` resource and filter `resource_status = REMOVED`; the deleted entity's `resource_name` is returned but not its historical field values.

Official API reference

What bites when replicating Google Ads

Explorer-level developer tokens are throttled to 2,880 operations/day against production accounts, roughly 5x tighter than the 15,000/day Basic tier, and each mutated item (not each request) counts as one operation.
`change_status` only stores a rolling 90-day history and caps results at 10,000 rows via `LIMIT`, so a connector that has been offline longer than 90 days cannot rely on it alone and must fall back to a full GAQL re-pull.
GoogleAdsService.Search caches the full result set server-side keyed on the exact query text; changing even whitespace or field order invalidates the cache and forces a slower cold read.
Standard access removes the fixed daily operation ceiling but still requires passing Google's Required Minimum Functionality (RMF) review, and accounts stuck on Test access can only query test accounts, never production data.

Compare this against every other documented API

Popular destinations for Google Ads

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Google Ads connector FAQ

What Google Ads data does the connector extract?: 6 objects: campaigns, ad groups, spend, clicks, conversions and attribution signals. Each lands in its own table with types preserved; history-style objects (1: clicks) load as append-only streams.
Is the Google Ads integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Google Ads data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Google Ads → destination pair has its own page with the object-to-table mapping.

Related Ads sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Google Ads pipeline with guided onboarding

Join the waitlist to get priority access for Google Ads integrations with guided setup, schema-aware mapping, and production-grade incremental sync.