Connector

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 AdsConnectedAdAd AccountAd Account UserAd Creatives
Data MartPublishedone definition
DatabricksDateCostClicksDaily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get Started Free

Endpoints

Facebook Ads Endpoints

Documentation

15 Facebook Ads endpoints you can import. Each lands in its own table in your data warehouse.

S00 · Why

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 data 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
Facebook AdsAd spend, reach
Web analyticsVisits, sign-ups
CRMDeals
Your data warehouseDatabricksAdTouch pointDealJoined by idAd seen or clickedDeal months laterOne query links the ad to the deal.

S01 · Step 1

Step 1: Connect Facebook Ads and choose what to load

Create a Data Mart, choose Facebook Ads as the data 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
New Data MartChoose a sourceMicrosoft AdsFacebook AdsLinkedIn AdsAuthorizeConnectedEndpointAd InsightsAdAd AccountAd Account User
Ad Insights100 fieldsdate_startspendimpressionsclicksreachpurchase_roas

S02 · Step 2

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
DestinationDatabricksCatalogmainSchemafacebook_adsTablead_account_insightsRun
Run HistoryPendingRunningSuccessIncremental load
Tablemain.facebook_ads.ad_account_…

S03 · Step 3

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 data 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
main.facebook_ads.ad_account_insightsOutput schemaFieldDescriptiondate_startThe start date for your data…spendThe estimated total amount of…impressionsThe number of times your ads…clicksThe number of clicks on your ads.reachThe number of people who saw…purchase_roasThe total return on ad spend…

S04 · Step 4

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 data 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
Ad Accountnameaccount_id
Ad Creativesidname
Adsidaccount_idcreative_id
Ad Insightsad_idspend

S05 · Step 5

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
ScheduleRun on a scheduleDaily 09:00
BackfillRun backfill
Run HistoryDaily scheduleManual backfillDaily schedule

S06 · Step 6

Step 6: Reuse the Databricks tables in every tool

One set of tables feeds your data model, spreadsheets, dashboards, AI 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
Facebook AdsData MartPublished
Blended ad spend
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email

Recent updates

Why OWOX

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.

Book a callGet Started Free

Trust

The Data Partner You Can Trust

users

175K Source: Internal OWOX data as of 2026-11-11

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

171K3

In Open Source We Trust

Customers