Weld
Start free

Microsoft Ads to PostgreSQL integration

Connect Microsoft Ads to PostgreSQL and automatically sync your advertising platform data. Weld extracts data from Microsoft Ads, loads it into PostgreSQL, and lets you transform the data using SQL or dbt, no custom scripts required.

Start for freeView setup guide
4.8 on G2
Microsoft AdsSource
WeldWeld
PostgreSQLWarehouse
Weld · New sync
Microsoft AdsSourceMicrosoft AdsConnected
Tables to sync
  • account39 cols
  • campaign38 cols
  • ad_group31 cols
  • ad23 cols
  • keyword_performance_daily_report58 cols
  • keyword_performance_hourly_report52 cols
  • Extract
  • Load
  • Keep in sync
PostgreSQLDestinationPostgreSQLReady
microsoft_ads schema
  • microsoft_ads.accountSynced
  • microsoft_ads.campaignSyncing
  • microsoft_ads.ad_groupSynced
  • microsoft_ads.adSynced
  • microsoft_ads.keyword_performance_daily_reportSynced
  • microsoft_ads.keyword_performance_hourly_reportSynced
Microsoft Ads tables
28
fields, typed
1,122
relationships kept
60
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 Microsoft Ads to PostgreSQL in Weld.
In the app, with the API or an agent.

Setup guideAPI guideMCP docs
Weld · New Microsoft Ads sync
Microsoft AdsNew connectionMicrosoft AdsAuthorised
Connection namemicrosoft_ads
AuthorizeOpens Microsoft Ads to grant read access
Use cases

Why sync Microsoft Ads to PostgreSQL?
Ready for analysis.

Centralizing your Microsoft Ads data in PostgreSQL lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying Microsoft Ads data directly in PostgreSQL using SQL or your preferred BI tool.

  • Cross-channel ad performance

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

  • Centralized data warehouse

    Bring Microsoft Ads data into PostgreSQL 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 Microsoft Ads to PostgreSQL. Connect BI tools like Looker, Metabase, or Power BI.

Schema

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

Weld syncs the objects the Microsoft Ads connector exposes into PostgreSQL, and you choose which tables and fields to include. The connector's docs list what is available.

Open the schema explorer
All 28 tables
  • account
  • campaign
  • ad_group
  • ad
  • keyword_performance_daily_report
  • keyword_performance_hourly_report
  • search_query_performance_daily_report
  • ad_performance_daily_report
  • ad_performance_hourly_report
  • keyword
  • ad_group_impression_performance_daily_report
  • user_location_performance_report
  • ad_group_impression_performance_hourly_report
  • ad_group_performance_daily_report
  • ad_group_performance_hourly_report
  • campaign_impression_performance_daily_report
  • campaign_performance_daily_report
  • campaign_impression_performance_hourly_report
  • campaign_performance_hourly_report
  • budget
  • account_impression_performance_daily_report
  • account_performance_daily_report
  • account_performance_hourly_report
  • account_impression_performance_hourly_report
  • ad_group_label
  • label
  • campaign_label
  • ad_label
Weld MCP server

Ask your agent.
It queries PostgreSQL for you.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Microsoft Ads context, finds the tables it needs and runs the query in PostgreSQL.

Set up the MCP serverClaudeCursorChatGPTGemini
Claude CodeOpus 5
>

How many campaign rows do we have per account? Use our Microsoft Ads data in PostgreSQL.

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

●weld·search_available_references
⎿raw.microsoft_ads.campaign
raw.microsoft_ads.account
+ 26 more Microsoft Ads tables
●weld·get_reference_schema
⎿campaign · 38 columns
joins account on account_id
●weld·run_query
⎿select a.id, count(*) from {{raw.microsoft_ads.campaign}} c
join {{raw.microsoft_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 Microsoft Ads data in PostgreSQL
>Ask about your Microsoft Ads data
Under the hood

Technical considerations.
What to expect.

Incremental syncing
Weld uses incremental syncing where supported by the Microsoft Ads API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling
Weld automatically manages schema changes. If Microsoft Ads adds new fields, they're detected and added to the corresponding PostgreSQL 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.
Resources

Keep reading.
Guides, docs and schema.

Documentation

Microsoft Ads setup guide

How to connect Microsoft Ads to Weld, step by step.

Documentation

PostgreSQL setup guide

How to connect PostgreSQL to Weld, step by step.

Schema

Microsoft Ads schema explorer

Browse all 28 tables and 1,122 fields.

Connector

Microsoft Ads connector

Everything Weld does with Microsoft Ads.

FAQ

Common questions.
About Microsoft Ads to PostgreSQL.

Start syncing Microsoft Ads to PostgreSQL.

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

Microsoft AdsSource
WeldWeld
PostgreSQLWarehouse
Start for freeTalk to us
Related

Related integrations.
More with Microsoft Ads and PostgreSQL.

View all