Google Ads to Amazon S3 integration

Connect Google Ads to Amazon S3 and automatically sync your advertising platform data. Weld extracts Campaigns, Ad Groups, Ads, and Keywords from Google Ads, loads them into Amazon S3, and lets you transform the data using SQL or dbt, no custom scripts required.

4.8 on G2
Google AdsSource
WeldWeld
Amazon S3Warehouse
Weld · New sync
Google AdsSourceGoogle AdsConnected
Tables to sync
  • account15 cols
  • campaign22 cols
  • ad_group16 cols
  • campaign_criterion33 cols
  • ad_stats31 cols
  • audience_stats29 cols
  • Extract
  • Load
  • Keep in sync
Amazon S3DestinationAmazon S3Ready
google_ads schema
  • 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

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up Google Ads to Amazon S3 in Weld.
In the app, with the API or an agent.

Weld · New Google Ads sync
Google AdsNew connectionGoogle AdsAuthorised
Connection namegoogle_ads
AuthorizeOpens Google Ads to grant read access
Use cases

Why sync Google Ads to Amazon S3?
Ready for analysis.

Centralizing your Google Ads data in Amazon S3 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 Amazon S3 using SQL or your preferred BI tool.

  • Cross-channel ad performance

    Consolidate Google Ads campaign data in Amazon S3 alongside other ad platforms. Compare ROAS, CPA, and conversion rates in a single dashboard.

  • Centralized data warehouse

    Bring Google Ads data into Amazon S3 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 Amazon S3. Connect BI tools like Looker, Metabase, or Power BI.

Schema

What data can you sync?
Every Google Ads table, keys intact.

Weld syncs the following data objects from Google Ads into Amazon S3. The exact tables and fields depend on your Google Ads configuration and the permissions granted during setup.

Open the schema explorer
All 32 tables
  • 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
Weld MCP server

Ask your agent.
It queries Amazon S3 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 Amazon S3.

Claude CodeOpus 5
>

How many campaign rows do we have per account? Use our Google Ads data in Amazon S3.

Reading the Google Ads context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.google_ads.campaign
raw.google_ads.account
+ 30 more Google Ads tables
●weld·get_reference_schema
⎿campaign · 22 columns
joins account on account_id
●weld·run_query
⎿select a.id, count(*) from {{raw.google_ads.campaign}} c
join {{raw.google_ads.account}} a on c.account_id = a.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Google Ads data in Amazon S3
>Ask about your Google Ads data
Under the hood

Technical considerations.
What to expect.

Reverse ETL

ELT vs. reverse ETL: Google Ads and Amazon S3

ELT (Extract, Load, Transform) moves data from Google Ads into Amazon S3 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 Amazon S3 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 Amazon S3.

Amazon S3 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 Amazon S3 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.
FAQ

Common questions.
About Google Ads to Amazon S3.

Start syncing Google Ads to Amazon S3.

Set up your Google Ads data pipeline in minutes. No credit card required. Free for 14 days.

Google AdsSource
WeldWeld
Amazon S3Warehouse