Google Ads Connector

Google Ads is an online advertising platform developed by Google, where advertisers bid to display brief advertisements.

Start for free View documentation

4.8 on G2

Weld · Data Sources

Google AdsYour warehouseLive

campaign22 columnsSynced

account15 columnsSynced

ad_group16 columnsSynced

campaign_criterion33 columnsSyncing

audience_stats28 columnsQueued

Lands in

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

Google Ads

Data source

Authenticating...

Ready to connect

Overview

Google Ads in your warehouse.
Ready for your agents.

Google Ads is an online advertising platform developed by Google, where advertisers bid to display brief advertisements. Weld's Google Ads connector is fully managed: it extracts data from Google Ads, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

Agent context

Google Ads data schema.
The map your agents read.

Every table, field and relationship Weld syncs from Google Ads is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables: 42
fields: 631

42 tables

Open the schema explorer Open the full schema explorer

Weld MCP server

Ask your agent.
It already knows Google Ads.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Google Ads context, finds the tables it needs and queries your warehouse.

Agent contextGoogle Ads tables, fields and joins
QuerySQL against your warehouse
OperateCheck, rerun and refresh syncs

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextGoogle Adstables42fields631

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

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

+ 40 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 your warehouse

>Ask about your Google Ads dataMCP

Destinations

Load Google Ads into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

Documentation

Google Ads setup guide

Step-by-step instructions to configure and start syncing.

MCP server

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

FAQ

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create Google Ads connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld Connect API reference

POST/elt_syncs

# Create a Google Ads ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "google-ads",
    "destination_schema_name": "google-ads_data",
    "sync_interval": "0 * * * *"
  }'
▌