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 Ads Endpoints
9 Google Ads endpoints you can import. Each lands in its own table in your data warehouse.
Ad Group Ads Stats
Daily performance for individual ads — impressions, clicks, cost, and conversions.
27 fieldsTime seriesAd Groups
Your ad group settings — type, status, and bid configuration within each campaign.
9 fieldsAd Groups Stats
Daily ad group performance — impressions, clicks, cost, and conversions.
24 fieldsTime seriesCampaigns
Your campaign settings — channel type, bidding strategy, budget, and scheduling.
11 fieldsCampaigns Stats
Daily campaign performance — impressions, clicks, cost, and conversions.
28 fieldsTime seriesCriterion
Ad group targeting criteria — keywords, placements, and negative exclusions with bid settings.
18 fieldsGeo Stats
Daily performance by country and targeting type — impressions, clicks, cost, and conversions.
18 fieldsTime seriesGeo Target Constants
Reference table of geographic targets — join with geo_stats on country_criterion_id to resolve country names.
7 fieldsKeywords Stats
Daily keyword performance — impressions, clicks, cost, conversions, and quality score.
26 fieldsTime series
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 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
Step 1: Connect Google Ads and choose what to load
Create a Data Mart, choose Google Ads as the 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
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
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 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
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 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
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
Step 6: Reuse the Databricks tables in every tool
One set of tables feeds your model, , , 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
- 0.43.0Compare LinkedIn Ads results across markets: spend by country, region, and county
- 0.43.0The Sheet link of a Google Sheets source opens the imported tab, not the first one
- 0.43.0Connect a Google Sheets plan with one Google sign-in
- 0.41.0Rotating a warehouse key is one change: Storages share reusable Credentials
- 0.41.0Dates from Google Sheets arrive as dates, not text
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.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.