Connector
Google Ads data, connected in minutes.
Grant access with OAuth and Odins pulls your Google Ads accounts daily: spend, impressions, clicks and conversions, with 2 to 3 years of history loaded up front. Structured for modeling, and available raw in your own warehouse.
Fully managed · reviewed September 2026
The data
What you can get from Google Ads.
Everything the platform's API reports is available. The default set below covers daily performance; the rest is added on request.
Stream names follow the managed pipeline layer's Google Ads source. Full stream reference: Airbyte's google-ads documentation and Google's Ads API report list.
One grant, every account.
Manager (MCC) structures and multi-market setups are the normal case for our customers, not the exception.
- OAuth connection through our Google Ads app, no developer token needed on your side
- Multiple customer accounts in one connector, manager accounts included
- Daily incremental syncs with deduplication, monitored by our team
- Delivered onward to BigQuery, Snowflake, Redshift or Databricks if you want the tables yourself
Frequently asked questions.
How do I get Google Ads data into BigQuery?
Connect Google Ads to Odins with OAuth, and we sync your accounts daily into a managed pipeline. From there the data is delivered to your BigQuery project, both as raw tables and as one structured cross-channel dataset. No transfer service setup, no scheduled queries to maintain.
Which Google Ads tables do you sync?
By default: campaign, campaign_budget and customer, which cover daily cost and performance per campaign plus account metadata. Any other Google Ads API report, such as ad group, keyword, geo or click view, can be added to your sync.
We run an MCC with many accounts. Does that work?
Yes. One connection can cover multiple customer accounts under a manager account, and the account structure is preserved in the data.
How far back does the data go?
We load 2 to 3 years of history when you connect, which is what the first marketing mix model trains on 4 to 6 weeks later.
How is this different from Google's own BigQuery Data Transfer?
The transfer service moves raw Google Ads tables and stops there. Odins also structures the data into one daily cross-channel dataset, keeps the sync monitored, and does the same for every other source you run, offline included, so Google Ads lands next to Meta, TV and affiliate spend in one hierarchy.
What happens when the Google Ads API changes?
We update the connector. Our team monitors every sync and repairs breakage, usually before customers notice anything.
Marketing spend, modeled like an investment.
A 30-minute walkthrough of the connection, the data and what the model does with it.
Book a demo-1.png?width=1132&height=292&name=Asset%201@2x%20(12)-1.png)