Ask Claude about your Microsoft Ads data
Load Microsoft Ads into your data warehouse first, link its ad performance report to web analytics and deals with SQL keys, then ask Claude in plain words. The answers come from your governed Data Marts, not from the ad account.
Claude can't tell you whether Microsoft Ads spends money in countries that never convert.
Paste this into your AI assistant. It loads Microsoft Ads into your data warehouse as a Data Mart and connects Claude through the OWOX MCP server, so every answer comes from that Data Mart.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /connectors/microsoft-ads-connector-to-claude.md. The task: connect Claude to my Microsoft Ads data and show where the people who click our ads are located, and which countries take spend without converting. Tag the links you give me with utm_campaign=ai-task and utm_term=data-foundation. Use what you know about my context and goals
Microsoft Ads Endpoints
3 Microsoft Ads endpoints you can import. Each lands in its own table in your data warehouse.
Ad Performance Report
Daily ad performance — impressions, clicks, spend, and conversions segmented by device, network, and match type.
95 fieldsTime seriesCampaigns
Your campaign and ad group structure — type, status, bid strategy, budget, and keyword settings.
54 fieldsUser Location Performance Report
Daily performance by user physical location — impressions, clicks, spend, and conversions broken down by country, state, and city.
81 fieldsTime series
Why Claude needs your data warehouse, not the Microsoft Ads account
Pointed at the Microsoft Ads account alone, Claude sees one platform's own figures. The account does not show which campaign led to a deal, because ad spend, website visits and CRM deals live in different systems. Joining them reliably, at scale and business-ready is the job of a warehouse, so Claude reads the answers from there.
- Microsoft Ads reports where the searcher was and what they searched for, not whether the click became a deal
- The data analyst links Microsoft Ads spend, web analytics and CRM deals by SQL keys and controls the result
- Claude reads governed Data Marts, so every answer traces back to analyst-written SQL
Step 1: Load Microsoft Ads into your data warehouse first
Create a Data Mart with Microsoft Ads as the source and choose where the data lands. It works with any popular data warehouse.
- Three endpoints and 225 fields to choose from, each endpoint in its own table
- Open the Microsoft Ads connector for your data warehouse below
Step 2: Link Microsoft Ads to web analytics and deals
In your data warehouse the model merges Microsoft Ads with Google Ads and your other ad platforms, then joins web analytics sessions by a campaign key. Pick an industry to see the shape of its model.
- Microsoft Ads and Google Ads search spend sits in one table with your social spend
- Sessions and deals join by SQL keys, not VLOOKUP and gut feeling
- The measures, such as platform_roas, are defined once
Step 3: Connect Claude to your data with OWOX MCP
Add the OWOX MCP server in Claude under Settings > Connectors, then choose the Data Marts it may see. Claude gets only what you expose, never raw database access.
- Authorize specific Data Marts, not your whole data warehouse
- Publish the Data Marts you want Claude to answer from, such as Microsoft Ads Ad Performance Report and User Location Performance Report
Step 4: Ask Claude about Microsoft Ads
Ask in plain words. Claude finds the right Data Mart and runs analyst-defined SQL against it, so the answer is built from your data warehouse.
- The answer is built by get_relevant_data_marts_by_prompt and query_data_mart
- Ask about search spend next to Google Ads: both land in the same merged spend table
- platform_roas and platform_cpa are what each platform claims; Sessions and Orders in the same model give the store's own count to set against them
- 0.41.0Rotating a connector key is one change: Sources share reusable Credentials
- 0.39.0Reload a year of history in one backfill, not twelve
- 0.37.0Short links resolve only on known short link services and domains you allow
- 0.37.0Clearer connector errors, and custom connectors that handle more APIs
- 0.36.0Support MCP protocol 2026-07-28 and alert on compatibility failures
Why OWOX for Microsoft Ads in Claude
Pointing Claude at an ad account gets one platform's own figures into a chat. OWOX also keeps the data yours, linked and ready to model, so the answers cover the whole business.
- You own the data. It lands in your own data warehouse, in tables you control.
- Both Microsoft Ads reports, as tables. Ad Performance Report and User Location Performance Report land in your data warehouse next to Google Ads, so search spend is one model.
- Where the searcher was. User Location Performance Report carries Country and QueryIntentCountry, so spend can be read by where people were and what place they searched for.
- Zero hallucinations. Claude queries governed Data Marts with analyst-written SQL, so every number traces back to the query behind it.
- Maintained for you. No scripts to fix when Microsoft changes its reporting API.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.
