Google Ads Connector

Sync Google Ads account structure, campaigns, keywords, and date-segmented performance reports into your warehouse with daily incremental updates.

SourceBronze

Start Free View Documentation

Evaluating against Fivetran? See how Supaflow handles Google Ads pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Managed Developer Token, Google Sign-In

Connect with Google sign-in and Supaflow provides and manages the Google Ads API developer token, so you do not apply for or paste one. Supaflow only performs read queries through the Reporting API (Google does not offer a read-only Google Ads scope); it never creates, edits, or pauses anything in your Google Ads account.

Automatic Manager Account Resolution

If the account you sync sits under a manager (MCC) account, Supaflow resolves the manager account automatically. You enter only the customer ID of the account you want to report on; there is no login-customer-id or manager account to configure.

Account Structure on Full Refresh

Twenty-one account-structure objects (accounts, campaigns, budgets, ad groups, ads, criteria, labels, bidding strategies, assets, audiences, and reference constants) re-read in full on each sync so your warehouse mirrors the current account setup.

Date-Segmented Performance Reports

Twenty-one performance reports across account, campaign, ad group, ad, keyword, geo, demographic, audience, shopping, video, and landing-page breakdowns sync incrementally on a daily date cursor.

Conversion-Window Lookback

Google restates conversion metrics for up to about 30 days after the click. The connector re-reads a trailing window on each sync (30 days by default, up to 90) so restated conversions land on the already-synced days. Lower it for a shorter window or raise it if conversions settle slowly.

Field Selection Pushdown

Deselect report fields you do not need and the connector requests only the fields you keep, keeping each query lean. The columns needed to identify each row and drive incremental sync are always retained.

Rolling 2-Year Backfill by Default

Leave Start Date blank and the initial backfill of performance reports covers a rolling 2-year window. Set Start Date explicitly when you want a different starting point. The click performance report is the exception: Google only exposes click data for the last 90 days, so it backfills at most 90 days.

Supported Objects

Account structure (full refresh)

Accounts, campaigns, campaign budgets

Account-level settings plus the campaign and budget configuration for the account.

Ad groups, ads, ad group criteria, campaign criteria

Ad groups and ads with their keyword and criteria targeting at the ad-group and campaign level.

Labels, campaign labels

Labels defined on the account and their associations to campaigns.

Bidding strategies, accessible bidding strategies

Portfolio bidding strategies owned by and shared with the account.

Assets, call details, user lists, user interests

Creative assets, call-reporting details, and audience lists and interest categories.

Reference constants (6 tables)

Carriers, languages, mobile app categories, mobile devices, operating system versions, and topics used as lookup dimensions.

Performance reports (incremental)

Account, campaign, ad group, and ad performance

Spend, impression, click, and conversion metrics at each level, segmented by date.

Keywords, search query, and keywordless query

Keyword and search-term performance, including queries matched without keywords.

Click performance

Click-level performance keyed by Google click ID and date.

Age range and gender

Demographic breakdowns of performance.

Geo and user location

Geographic-view and user-location breakdowns of performance.

Campaign audience and ad group audience

Audience-segment breakdowns at the campaign and ad-group level.

Display keyword, display topics, and placement

Display-network keyword, topic, and placement breakdowns.

Shopping and video performance

Shopping product and video performance, segmented by campaign and ad group.

Landing page and expanded landing page

Landing-page performance, segmented by campaign and ad group.

Not yet supported

Individual conversion action records and conversion adjustments, ad extension and asset performance reports, smart campaign reports, lead form data, audience and market insights, and any write or change operations

Not exposed by the connector today. Aggregate conversion metrics (conversions, conversion value) are already included in the performance reports. Email support@supa-flow.io with the report or object you need -- expansion is prioritized by customer demand.

How It Works

Find your customer ID

In Google Ads, the 10-digit customer ID appears in the top corner of the UI, formatted like 123-456-7890. Use the ID of the account you want to sync, with or without dashes.

Authorize with Google

Click Authorize in the Supaflow source wizard and sign in with a Google account that can open that Google Ads account. Supaflow stores the resulting refresh token and supplies the developer token for you, so you do not apply for one.

Confirm account access

The Google account needs read access to the Google Ads account. If you reach the account only through a manager (MCC) account, sign in with a login that can see it in the Google Ads UI; Supaflow resolves the manager account automatically.

Configure optional sync settings

Set Start Date (YYYY-MM-DD) to override the default rolling 2-year backfill, and adjust Conversion Window Lookback (30 days by default, up to 90) if conversions in your account settle on a different schedule.

Test and save

Click Test & Save. Supaflow verifies access to the account and saves the source. If the connected login cannot reach the customer ID, the save fails with a specific error.

Use Cases

Blended paid-acquisition reporting

Land Google Ads spend and conversion reports next to GA4, CRM, and revenue data in your warehouse to compute blended CAC, channel ROI, and campaign payback in dbt instead of stitching exports together by hand.

Keyword and search-term analysis

Pull the keyword and search-query reports to surface wasted spend, negative-keyword candidates, and high-intent queries, joined against conversions and revenue from your billing or CRM source.

Cross-account portfolio reporting

Run one source per account under your manager account to consolidate campaign and budget performance across clients or brands into a single warehouse model.

Frequently Asked Questions

Do I need a Google Ads API developer token?

No. Supaflow provides and manages the developer token. You connect a Google account with access to your Google Ads account; you do not apply for, paste, or renew a developer token.

What does Supaflow sync from Google Ads?

Twenty-one account-structure objects (accounts, campaigns, budgets, ad groups, ads, criteria, labels, bidding strategies, assets, audiences, and reference constants) on full refresh, and 21 date-segmented performance reports on a daily incremental cursor. Each becomes its own table in your destination.

Does the connector write to or change my Google Ads account?

No. Supaflow only performs read queries through the Google Ads Reporting API. Google does not offer a read-only Google Ads scope, so the consent screen grants the Google Ads API scope, but the connector never creates, edits, or pauses anything in your account.

How do manager (MCC) accounts work?

Enter the 10-digit customer ID of the account you want to report on. If it sits under a manager account, Supaflow resolves the manager account automatically; there is no login-customer-id or manager ID to configure.

Why do recent conversions keep changing?

Google restates conversion metrics for up to about 30 days after the click. The connector re-reads a trailing window on each sync (30 days by default, up to 90) so restated conversions land on the already-synced days. Adjust Conversion Window Lookback if your account settles faster or slower.

How far back does the first sync go?

Performance reports backfill a rolling 2-year window by default. Set Start Date (YYYY-MM-DD) for a different starting point; it applies on the first sync of each report, and later runs advance from the saved cursor. The click performance report is the exception: Google only exposes click data for the last 90 days, so it backfills at most 90 days regardless of Start Date.

How does Supaflow handle Google Ads API limits?

Google applies rate limits and quotas to the Google Ads API per developer token and per account. Supaflow handles transient rate limiting automatically with retry and backoff. Very large initial backfills or many parallel pipelines on one account may take longer or need off-peak scheduling. See Google's Google Ads API quota documentation at developers.google.com/google-ads/api/docs/best-practices/quotas for current limits.

Can I run the Google Ads pipeline natively inside Snowflake?

Yes. Supaflow runs as a Snowflake Native App via Snowpark Container Services, so your Google Ads data is extracted and loaded without leaving your Snowflake account. See our Snowflake Native ETL guide for details.