Google Ads to Apache Iceberg integration
Connect Google Ads to Apache Iceberg and automatically sync your advertising platform data. Weld extracts Campaigns, Ad Groups, Ads, and Keywords from Google Ads, loads them into Apache Iceberg, and lets you transform the data using SQL or dbt, no custom scripts required.
Source
WarehouseSourceGoogle AdsConnected- account15 cols
- campaign22 cols
- ad_group16 cols
- campaign_criterion33 cols
- ad_stats31 cols
- audience_stats29 cols
- Extract
- Load
- Keep in sync
DestinationApache IcebergReady- google_ads.accountSynced
- google_ads.campaignSyncing
- google_ads.ad_groupSynced
- google_ads.campaign_criterionSynced
- google_ads.ad_statsSynced
- google_ads.audience_statsSynced
- Google Ads tables
- 32
- fields, typed
- 591
- agent context included
- MCP
Trusted by data and AI teams
How to set up Google Ads to Apache Iceberg in Weld.
In the app, with the API or an agent.
New connectionGoogle AdsAuthorisedWhy sync Google Ads to Apache Iceberg?
Ready for analysis.
Centralizing your Google Ads data in Apache Iceberg lets you join it with other data sources for cross-platform analytics and deeper insights.
Build reliable dashboards and reports by querying Google Ads data directly in Apache Iceberg using SQL or your preferred BI tool.
Cross-channel ad performance
Consolidate Google Ads campaign data in Apache Iceberg alongside other ad platforms. Compare ROAS, CPA, and conversion rates in a single dashboard.
Centralized data warehouse
Bring Google Ads data into Apache Iceberg alongside other sources to create a single source of truth for your organization.
Automated reporting
Replace manual exports and spreadsheet-based reporting with automated pipelines from Google Ads to Apache Iceberg. Connect BI tools like Looker, Metabase, or Power BI.
What data can you sync?
Every Google Ads table, keys intact.
Weld syncs the following data objects from Google Ads into Apache Iceberg. The exact tables and fields depend on your Google Ads configuration and the permissions granted during setup.
- account
- campaign
- ad_group
- campaign_criterion
- ad_stats
- audience_stats
- ad
- ad_group_criterion
- ad_group_province_stats
- ad_group_hourly_stats
- ad_group_stats
- ad_group_country_stats
- campaign_hourly_stats
- keyword_stats
- campaign_stats
- search_term_keyword_stats
- search_term_stats
- campaign_budget
- user_list
- campaign_criterion_proximity
- campaign_criterion_schedule
- user_interest
- campaign_bid_modifier
- campaign_bidding_strategy
- account_hourly_stats
- account_stats
- ad_group_bidding_strategy
- label
- mobile_device
- operating_system_version
- and 2 more
Ask your agent.
It queries Apache Iceberg for you.
Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Google Ads context, finds the tables it needs and runs the query in Apache Iceberg.
How many campaign rows do we have per account? Use our Google Ads data in Apache Iceberg.
Reading the Google Ads context first, so the query uses the right tables and keys.
Technical considerations.
What to expect.
ELT vs. reverse ETL: Google Ads and Apache Iceberg
ELT (Extract, Load, Transform) moves data from Google Ads into Apache Iceberg for analysis. This is the approach shown on this page, and the one to use for dashboards, reports, and data models.
Reverse ETL works the other direction: it pushes enriched data from Apache Iceberg back into Google Ads. For example, you could sync computed lead scores or customer segments from your warehouse into Google Ads to personalize outreach.
Weld supports both directions, so you can build a complete data loop between Google Ads and Apache Iceberg.
Apache Iceberg to Google Ads- Incremental syncing
- Weld uses incremental syncing where supported by the Google Ads API, loading only new and updated records to minimize data transfer and warehouse costs.
- Schema handling
- Weld automatically manages schema changes. If Google Ads adds new fields, they're detected and added to the corresponding Apache Iceberg tables.
- Data freshness
- Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
- Security
- All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
Keep reading.
Guides, docs and schema.
Google Ads setup guide
How to connect Google Ads to Weld, step by step.
DocumentationApache Iceberg setup guide
How to connect Apache Iceberg to Weld, step by step.
SchemaGoogle Ads schema explorer
Browse all 32 tables and 591 fields.
ConnectorGoogle Ads connector
Everything Weld does with Google Ads.
Common questions.
About Google Ads to Apache Iceberg.
Start syncing Google Ads to Apache Iceberg.
Set up your Google Ads data pipeline in minutes. No credit card required. Free for 14 days.
SourceWarehouse
