Land Facebook Ads data in Databricks
Send Facebook and Instagram ad insights to Databricks with OWOX Data Marts: ads, creatives and insights as separate tables in your Databricks catalog, refreshed on a schedule. Join them with web analytics and CRM to see which ads brought customers.
Facebook Ads Endpoints
15 Facebook Ads endpoints you can import. Each lands in its own table in your data warehouse.
Ad
Individual ads with their creative, status, and links to their campaign and ad set.
32 fieldsAd Account
Your ad account settings, status, currency, and billing details.
61 fieldsAd Account User
Users with access to an ad account and their assigned roles.
2 fieldsAd Creatives
The images, videos, text, and other visual elements used in your ads.
65 fieldsAd Insights
Daily performance metrics for each ad — impressions, clicks, spend, and conversions.
100 fieldsTime seriesAd Insights by Ad Set
Daily ad set performance with reach deduplicated to match Meta Ads Manager.
92 fieldsTime seriesAd Insights by Age and Gender
Daily ad performance broken down by audience age range and gender.
102 fieldsTime seriesAd Insights by Campaign
Daily campaign performance with reach deduplicated to match Meta Ads Manager.
89 fieldsTime seriesAd Insights by Country
Daily ad performance broken down by the country where your audience is located.
101 fieldsTime seriesAd Insights by Device Platform
Daily ad performance broken down by the device type your audience used.
101 fieldsTime seriesAd Insights by Link URL Asset
Daily ad performance broken down by the link URL shown in your ads.
101 fieldsTime seriesAd Insights by Product ID
Daily ad performance broken down by individual product from your catalog.
101 fieldsTime seriesAd Insights by Publisher Platform and Position
Daily ad performance broken down by where your ads appeared — platform and placement position.
102 fieldsTime seriesAd Insights by Region
Daily ad performance broken down by the region where your audience is located.
101 fieldsTime seriesAds
Individual ads with their status, creative, and campaign hierarchy.
24 fields
Why join Facebook Ads with web analytics and CRM in Databricks
Ads Manager counts results with Meta's own attribution and stops at the ad account. To see which Facebook and Instagram ads led to revenue, put spend, website touch points and CRM deals in one warehouse, where SQL can join them.
- Line Facebook spend up with Google, TikTok and Microsoft Ads
- Follow an ad click or sign-up to the order or deal it became
- Keep spend, reach and ROAS in tables you query, not in an ad account
Step 1: Connect Facebook Ads and choose what to load
Create a Data Mart, choose Facebook Ads as the source, sign in with Facebook or add an access token, list your ad account ids and tick only the fields you need.
- 15 endpoints and 1172 fields to choose from
- Ad Insights alone has 100 fields: spend, reach, clicks, conversions, ROAS
- One Data Mart per endpoint, so each breakdown stays its own table
Step 2: Load Facebook 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, from the start of the previous month through today, lands in your own Databricks workspace.
- Insights go to a table such as facebook_ads_ad_account_insights
- Every run is logged in Run History
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.
- Results such as actions and action_values are fields of their own, with descriptions
- Teammates can query the table without the API reference
Step 4: Keep the Facebook Ads tables linked
Ad accounts, ads, creatives and insights stay separate tables, joined by ids. In SQL they become one Facebook Ads model.
- ad_id in Ad Insights is the id of the ad, and creative_id on the ad points to its creative
- Campaign and ad set ids ride on every row, so spend rolls up to either level
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.
- Run it daily, weekly, monthly or on an interval
- Backfills longer than a month are split into segments of up to 31 days for you
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.
- Blend Facebook with Google and TikTok spend once
- 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 Facebook Ads in Databricks
Databricks has connectors of its own, and plain API notebooks get Facebook data in too. OWOX adds control over what lands and how it reads.
- You own the data. It lands in your own Databricks workspace, in tables you control.
- Breakdowns on your terms. Country, region, age and gender, device and placement cuts each load as a table of their own; take the ones you need.
- Described columns. Results such as actions and action_values come with readable descriptions, not API names.
- Joined by ad, ad set and campaign ids. The tables arrive ready to meet web analytics and CRM in SQL.
- Maintained for you. No jobs to repair when Meta updates the Marketing 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.