Send Microsoft Ads data to Databricks
Move Microsoft Advertising, formerly Bing Ads, into Databricks with OWOX Data Marts: campaigns and performance reports as separate tables in your Databricks catalog, refreshed on a schedule. Join them with web analytics and CRM to see which search ads ended in deals.
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 web analytics and CRM in Databricks
Microsoft Advertising reports spend, clicks and the conversions and revenue it tracked. Where Bing search carries real volume, those clicks deserve Google's scrutiny, which means joining spend, website touch points and CRM deals in one warehouse.
- Add Microsoft Ads to the spend table beside Google, Facebook and LinkedIn
- Tie Microsoft Ads clicks and form fills to the deals they became
- Check the Revenue Microsoft reports against your CRM
Step 1: Connect Microsoft Ads and choose what to load
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 Databricks tables
The catalog defaults to main, and the schema and table are pre-filled; change any of them. Run it and the first load lands in your own Databricks workspace.
- 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: Open the output schema in plain words
The first run gives you the output schema: every field with an alias and a readable description, not an API identifier. Your quality checks can read it too.
- Account, campaign, ad group and ad names sit beside their ids
- Teammates can query the table without the API reference
Step 4: Keep the Microsoft Ads tables linked
Campaigns and the two performance reports stay separate tables, joined by CampaignId. In SQL 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: Refresh on a schedule and backfill the history
Set it once. A scheduled refresh keeps the Databricks tables current, and a manual run loads a past period of your choice.
- Each incremental run reloads today plus a lookback window you set
- Backfill a custom start and end date
Step 6: Reuse the Databricks tables in every tool
One set of tables feeds your model, , , assistants like Claude and ChatGPT and AI insights in Slack or email.
- Show search spend from Microsoft and Google side by side
- Every report reads the same table
- 0.43.0Compare LinkedIn Ads results across markets: spend by country, region, and county
- 0.43.0The Sheet link of a Google Sheets source opens the imported tab, not the first one
- 0.43.0Connect a Google Sheets plan with one Google sign-in
- 0.41.0Rotating a warehouse key is one change: Storages share reusable Credentials
- 0.41.0Dates from Google Sheets arrive as dates, not text
Why OWOX for Microsoft Ads in Databricks
Notebooks over the reporting API and generic ETL tools get the reports out. OWOX also keeps them in your tables, readable and ready to model.
- You own the data. It lands in your own Databricks workspace, in tables you control.
- Reports as tables. Performance reports arrive as ordinary Databricks tables with described columns, not files to download and parse.
- Joined by CampaignId. Campaigns and both performance reports meet in SQL, then meet Google Ads, web analytics and CRM.
- Ids beside names. Account, campaign, ad group and ad names sit next to their ids.
- Maintained for you. No jobs to repair 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.