Sync data from
Databricks to Facebook Offline Conversions
Connect your data from Databricks to Facebook Offline Conversions with Hightouch. No APIs, no months-long implementations, and no CSV files. Just your data synced forever.
Trusted by data teams at
Integrate your data in 3 easy steps
Add your source and destination
Connect to 15+ data sources, like Databricks, and 140+ destinations, like Facebook Offline Conversions.
Define your model
Use SQL or select an existing dbt or Looker model.
Sync your data
Define how fields from your model map to Facebook Offline Conversions, and start syncing.
Model your Databricks data using any of these methods
dbt Model Selector
Sync directly with your dbt models saved in a git.
Create and Edit SQL from your browser. Hightouch supports SQL native to Databricks.
Select available tables and sheets from Databricks and sync using existing views without having to write SQL.
For less technical users, pass traits and audiences from Databricks using our visual segmentation builder.
Does this integration support in-warehouse planning?
Yes, if you integerate Databricks and Facebook Offline Conversions using Hightouch, in-warehouse planning is supported.
Great, but what is in-warehouse planning?
Between every sync, Hightouch notices any and all changes in your data model. This allows you to only send updated results to your destination (in this case Facebook Offline Conversions). With the baseline setup, Hightouch picks out only the rows that need to be synced by querying every row in your data model before diffing using Hightouch’s infrastructure.
The issue here is this can be slow for large models.
Warehouse Planning allows Hightouch to do this diff directly in your warehouse. Read more on how this works here.
Why is it valuable to sync Databricks data to Facebook Offline Conversions?
Thanks to Databricks, it's easier than ever to access your customer data, run complex queries, and segment your customers/users into various categories or audiences.
However, to target users and send conversion data to Facebook Offline Conversions, you need access to all of the unique behavioral data (e.g., last-login date, items in cart, pages viewed, etc.) and core business metrics like lifetime value, workspaces, subscriptions, annual recurring revenue, etc. that lives in Databricks. You then need to be able to package this data to send to Facebook Offline Conversions in the format expected. Plus, you want to do this in a real-time and automated way.
Facebook Offline Conversions is only as good as the data you give them, and if you truly want to optimize your ad spend, increase your match rates, and drive conversions, you need to provide custom data from Databricks within your warehouse.
Maybe you want to retarget users who abandoned their shopping cart in the last seven days, or upload a list of high-value customers to identify potential lookalike audiences, or perhaps you want to upload offline conversion events to reduce your customer acquisition costs and increase your return on ad spend.
Why should you use reverse ETL to connect Databricks and Facebook Offline Conversions data?
In the past, uploading customer data to Facebook Offline Conversions meant hopping back and forth between your various SaaS applications or asking your data team for CSV files. Neither of these options is preferable because marketing teams want to self-serve, and data teams don't enjoy constantly fulfilling one-off marketing requests.
Even worse, if you truly want to optimize your advertising campaigns, you need to be uploading fresh data consistently. Non-fresh data can be expensive for ads. If you're using CSVs to define who to exclude from paid ads and you're uploading that data weekly, that's potentially one week of irrelevant ads. As a workaround, engineering teams will integrate directly with the Facebook Offline Conversions API, and build and maintain custom in-house pipelines. The problem is that a single API change can break everything, and data engineers don't want to spend their time building and maintaining pipelines.
With Hightouch, you can leverage the existing data models and customer segments your engineering team has defined in your warehouse and sync that data directly to your ad platforms in real time. You can schedule your data syncs to run automatically, on a set cadence, or even for the exact duration of your marketing campaign. Hightouch lets your data teams establish the guardrails for your marketers to self-serve and build custom audiences through a drag-and-drop interface.
Send events directly from your data warehouse to Facebook Offline Event Sets
Tune your measurement, optimization, and reporting processes with additional product data from the warehouse
Databricks is a data science and analytics platform built on top of Apache Spark. Databricks implement the Data Lakehouse concept in a single unified, cloud based platform.Learn more about Databricks
About Facebook Offline Conversions
Use the Offline Conversions API to send offline conversion events and to see how many customers viewed or clicked Facebook ads before converting.Learn more about Facebook Offline Conversions
Other Databricks Integrations
Other Facebook Offline Conversions integrations
Hightouch Playbooks: Best practices to leverage reverse ETL
Read more about Hightouch
What is Operational Analytics & Why You Should Use It
Operational Analytics shifts the focus from simply understanding data to taking action on it in the tools that run business processes. Instead of using dashboards to make decisions, Operational Analytics is focused on turning insights into action – automatically.Read
Activate data to any of your marketing and advertising tools
This might be one of the greatest inventions for technical marketers since the advent of legacy CDPs back in 2015.
Head of Marketing Technology
Your data is always secure
SOC 2 Type 2 compliant
Your data stays secure, available, and confidential. To see our report, .
If you’re in the EU, your data is only processed on EU data centers.
Healthcare companies like ThirtyMadison, Chapter Health, and Headway trust Hightouch.
To see our DPA (Data Processing Addendum), .
increase in return on ad spend
improvement in email engagement
lift in customer acquisition