Connector

Bring Google Ads data into Databricks

Load Google Ads campaigns, ad groups, ads and keywords into Databricks with OWOX Data Marts: one table per endpoint in your catalog, a readable schema, a scheduled refresh. Join search spend with web analytics and CRM to see which campaigns led to deals.

Google AdsConnectedAd Group Ads Sta…Ad GroupsAd Groups StatsCampaigns
Data MartPublishedone definition
DatabricksDateCostClicksDaily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get Started Free

Endpoints

S00 · Why

Why join Google Ads with web analytics and CRM in Databricks

Google Ads reports clicks and the conversions it counted, and it does not follow a campaign to a deal that closes months later. Put search spend, website touch points and CRM deals in one data warehouse so a single query can.

  • Compare Google Ads spend with Facebook, Microsoft and TikTok
  • Trace a campaign click to the deal it became
  • Keep conversions and conversion value in tables you own
Google AdsSearch spend
Web analyticsClicks, form fills
CRMDeals
Your data warehouseDatabricksCampaignTouch pointDealJoined by idCampaign clickedDeal months laterOne query links the ad to the deal.

S01 · Step 1

Step 1: Connect Google Ads and choose what to load

Create a Data Mart, choose Google Ads as the data source, authorize with Google or a service account, enter the Customer ID and tick only the fields you need.

  • 9 endpoints and 166 fields: campaigns, ad groups, ads, keywords and geo
  • Stats endpoints read an ad account Customer ID; structure endpoints can read a manager account
New Data MartChoose a sourceFacebook AdsGoogle AdsTikTok AdsAuthorizeConnectedEndpointCampaigns StatsAd Group Ads StatsAd GroupsAd Groups Stats
Campaigns Stats28 fieldsdatecost_microsimpressionsclicksconversionsconversions_value

S02 · Step 2

Step 2: Load Google Ads into Databricks tables

The catalog defaults to main, and the schema and table are pre-filled; change any of them. Run it and the first load lands in your own Databricks workspace.

  • Each endpoint gets its own table, such as google_ads_campaigns_stats
  • Cost arrives in micros as cost_micros; convert it once in your model
  • Every run is logged in Run History
DestinationDatabricksCatalogmainSchemagoogle_adsTablecampaigns_statsRun
Run HistoryPendingRunningSuccessIncremental load
Tablemain.google_ads.campaigns_sta…

S03 · Step 3

Step 3: Open the output schema in plain words

The first run gives you the output schema: every field with an alias and a readable description, not an API identifier. Your data quality checks can read it too.

  • The schema spells out units, such as cost_micros being cost in micros
  • Statuses read as plain values: ENABLED, PAUSED, REMOVED
main.google_ads.campaigns_statsOutput schemaFieldDescriptiondateDate for time series datacost_microsCost in MicrosimpressionsNumber of ImpressionsclicksNumber of ClicksconversionsNumber of Conversionsconversions_valueTotal Conversion Value

S04 · Step 4

Step 4: Keep the Google Ads tables linked

Campaigns, ad groups, ad stats and campaign stats stay separate tables, joined by ids. In SQL they become one Google Ads data model.

  • campaign_id and ad_group_id repeat across tables, so a stats row always finds its campaign and ad group
  • Join the model to web analytics and CRM on the campaign
Campaignscampaign_idcampaign_namecampaign_status
Ad Groupsad_group_idcampaign_idad_group_name
Ad Group Ads Statsad_idad_group_idcost_micros
Campaigns Statscampaign_idcost_micros

S05 · Step 5

Step 5: Refresh on a schedule and backfill the history

Set it once. A scheduled refresh keeps the Databricks tables current, and a manual run loads a past period of your choice.

  • Each incremental run reloads today plus a lookback window you set
  • Backfill a custom start and end date
ScheduleRun on a scheduleDaily 09:00
BackfillRun backfill
Run HistoryDaily scheduleManual backfillDaily schedule

S06 · Step 6

Step 6: Reuse the Databricks tables in every tool

One set of tables feeds your data model, spreadsheets, dashboards, AI assistants like Claude and ChatGPT and AI insights in Slack or email.

  • Blend Google Ads with Facebook and Microsoft spend once
  • Every report reads the same table
Google AdsData MartPublished
Blended ad spend
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email

Recent updates

Why OWOX

Why OWOX for Google Ads in Databricks

Google's transfer service writes only to BigQuery. OWOX loads Google Ads into Databricks the same way it loads Facebook, TikTok and Microsoft, with a choice of endpoints and fields.

  • Google Ads and every other source. Facebook, TikTok, Microsoft and the rest load the same way, so blended ad spend stays one model in Databricks.
  • You choose endpoints and fields. Pick campaign, ad group, ad, keyword or geo stats and tick only the columns you need.
  • Your schedule, any period. A lookback window picks up late changes, and a backfill loads any custom period.
  • Joined by campaign, ad group and ad ids. The tables arrive ready to meet web analytics and CRM.
  • Free to self-host. The open-source OWOX Data Marts runs in your own infrastructure.

Book a callGet Started Free

Trust

The Data Partner You Can Trust

users

175K Source: Internal OWOX data as of 2026-11-11

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

171K3

In Open Source We Trust

Customers