Microsoft Ads Connector

Microsoft Advertising, is Microsoft's online advertising platform that enables businesses to display ads on the Bing search engine.

Start for free View documentation

4.8 on G2

Weld · Data Sources

Microsoft Ads

Microsoft AdsYour warehouseLive

account39 columnsSynced

campaign38 columnsSynced

ad_group31 columnsSynced

ad23 columnsSyncing

keyword_performance_daily_report58 columnsQueued

Lands in

snowflake

bigquery

databricks

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

Microsoft Ads

Microsoft Ads

Data source

Authenticating...

Ready to connect

Overview

Microsoft Ads in your warehouse.
Ready for your agents.

Microsoft Advertising, is Microsoft's online advertising platform that enables businesses to display ads on the Bing search engine. Weld's Microsoft Ads connector is fully managed: it extracts data from Microsoft 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

Microsoft Ads data schema.
The map your agents read.

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

tables: 28
fields: 1,122
relationships: 60

Loading diagram…

account_financial_status

account_life_cycle_status

back_up_payment_instrument_id

billing_threshold_amount

bill_to_customer_id

business_address_id

account_impression_performance_daily_report

ad_distribution

delivered_match_type

account_impression_performance_hourly_report

ad_distribution

delivered_match_type

account_performance_daily_report

ad_distribution

delivered_match_type

account_performance_hourly_report

ad_distribution

delivered_match_type

custom_parameter

device_preference

editorial_appeal_status

editorial_location

ad_schedule_use_searcher_time_zone

bid_boost_value

bid_strategy_type

ad_group_impression_performance_daily_report

ad_distribution

delivered_match_type

ad_group_impression_performance_hourly_report

ad_distribution

delivered_match_type

ad_group_performance_daily_report

ad_distribution

delivered_match_type

ad_group_performance_hourly_report

ad_distribution

delivered_match_type

ad_performance_daily_report

ad_distribution

ad_performance_hourly_report

ad_distribution

ad_schedule_use_searcher_time_zone

bid_strategy_max_cpc

bid_strategy_name

bid_strategy_target_ad_position

bid_strategy_target_cpa

bid_strategy_target_impression_share

campaign_impression_performance_daily_report

ad_distribution

delivered_match_type

campaign_status

campaign_impression_performance_hourly_report

ad_distribution

delivered_match_type

campaign_status

campaign_performance_daily_report

ad_distribution

delivered_match_type

campaign_performance_hourly_report

ad_distribution

delivered_match_type

bid_strategy_type

custom_parameter

destination_url

editorial_appeal_status

editorial_location

keyword_performance_daily_report

delivered_match_type

ad_distribution

keyword_performance_hourly_report

delivered_match_type

ad_distribution

search_query_performance_daily_report

delivered_match_type

user_location_performance_report

ad_distribution

cost_per_assist

cost_per_conversion

Open the schema explorer Open the full schema explorer

Weld MCP server

Ask your agent.
It already knows Microsoft Ads.

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

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

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextMicrosoft Adstables28fields1,122joins60

>

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

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

>Ask about your Microsoft Ads dataMCP

Destinations

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

Resources

Everything you need.
To get started.

Microsoft Ads setup guide

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

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.

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 Microsoft 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 Microsoft 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": "microsoft-ads",
    "destination_schema_name": "microsoft-ads_data",
    "sync_interval": "0 * * * *"
  }'
▌

FAQ

Common questions.
About connectors.

Something not covered here? A data engineer can walk through your setup with you.

Put your Microsoft Ads data to work.

Connect Microsoft Ads, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.

Microsoft Ads

Source

Weld

MCPAgents

Start for free Talk to us

Connectors

Explore more connectors.
300+ and counting.

View all connectors