Collect Microsoft Ads data in Google BigQuery
Load Microsoft Advertising, formerly Bing Ads, into your own BigQuery tables with OWOX Data Marts: campaigns and performance reports, each in its own table, refreshed on a schedule. Join it with web analytics and CRM to see which search ads become deals.
Microsoft Ads search traffic gets left out of channel reports because its data stays in its own account, not in Google BigQuery.
Paste this into your AI assistant. It creates a Microsoft Ads Data Mart on your Google BigQuery storage, loads campaigns and performance reports into your own tables, and joins spend to sessions and deals.
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/free-microsoft-ads-connector-to-google-bigquery.md. The task: load Microsoft Ads ad performance reports into Google BigQuery on a daily schedule and build a Data Mart with spend, conversions, revenue and CRM deals by campaign and month. Tag the links you give me with utm_campaign=ai-task and utm_term=m4. 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 join Microsoft Ads with your web analytics and CRM
Microsoft Advertising reports spend, clicks and the conversions and revenue it tracked. Where Bing search share is material, those clicks deserve the same scrutiny as Google's, and that means joining spend with website touch points and CRM deals in one warehouse.
- Add Microsoft Ads to the same spend table as Google, Facebook and LinkedIn
- Connect Microsoft Ads clicks and form fills to the deals they became
- Compare the Revenue Microsoft reports with the revenue in your CRM
Step 1: Connect Microsoft Ads and pick the fields
Create a Data Mart, choose Microsoft Ads as the source, sign in with Microsoft or add an access token, and tick only the fields you need.
- 3 endpoints and 225 fields to choose from
- Ad Performance Report alone has 92 fields: spend, clicks, conversions, revenue, video views
Step 2: Load Microsoft Ads into a BigQuery table
The dataset and table in your storage are pre-filled, and you can change them. Run it and the first load lands in your own BigQuery project.
- Each report gets its own table, such as microsoft_ads_ad_performance_report
- Rows are dated by TimePeriod, with campaign, ad group and ad ids beside the names
Step 3: Get a business-friendly output schema
After the first run you get the output schema: every field with a readable description, not a report column code. Your quality checks can read it too.
- Account, campaign, ad group and ad names sit beside their ids
- Anyone on the team can read the table
Step 4: Keep the Microsoft Ads tables linked
Campaigns and the two performance reports stay separate tables, joined by CampaignId. Together they become one Microsoft Ads model.
- The ad report and the user location report both carry CampaignId
- FinalUrl gives each ad's landing page, ready to match web analytics
Step 5: Schedule the refresh and backfill history
Set it once. A scheduled refresh keeps the tables current, and a manual backfill loads any past period.
- Each incremental run reloads today plus a lookback window you set
- Backfill a custom start and end date
Step 6: Reuse the same table everywhere
One table feeds your model, , , assistants like Claude and ChatGPT, and scheduled AI insights in Slack or email.
- Show search spend from Microsoft and Google side by side
- Every report reads the same table
- 0.44.0Microsoft Ads imports work for advertisers who sign in with Google
- 0.44.0Connector Data Marts set up through MCP no longer fail their first run because of the table path
- 0.44.0Backfill a catalog for any period in one run, and follow a long backfill as parts of one operation
- 0.43.0Parallel reads of a SQL Data Mart on Google BigQuery no longer fail with a rate limit error
- 0.41.0Rotating a warehouse key is one change: Storages share reusable Credentials
Why OWOX for Microsoft Ads in BigQuery
Hand-built reporting API scripts, a generic ETL tool or exports from the Microsoft Advertising interface each get the data out. OWOX also keeps it yours, readable and ready to model.
- You own the data. It lands in your own BigQuery project, in tables you control.
- Report tables you can read. Performance reports arrive as ordinary tables with described columns, instead of files to download and parse.
- Ready for a data model. Campaigns and reports joined by CampaignId, built to connect to Google Ads, web analytics and CRM.
- Maintained for you. No scripts to fix when Microsoft changes its reporting API.
- Free to self-host. The open-source OWOX Data Marts runs in your own infrastructure.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.