Sync data from Databricks to Google Ads
Connect your data from Databricks to Google Ads with Hightouch. No APIs, no months-long implementations, and no CSV files. Just your data synced forever.
Activate your data in 3 easy steps
Name
Name
Total_orders
All_orders
Last_login
Last_login
Sync data from Databricks to Google Ads
- Upload lists to Google Ads to run ads based on certain attributes within your database, such as people who have visited your site
- Run lookalike audiences on Google Ads using subsets of your users rather than all of them
- Continuously fuel your Google Ads custom audiences with live data so that data never goes stale
What Google Ads objects can you sync to?
Customer Match (User) Lists
Customer Match lets you target ads to your customers using the data they share with you. You can upload it into Google Ads to incorporate this targeting into your campaigns.
Call Conversions
Phone call conversion tracking helps you track when your ads lead to different kinds of phone calls. By importing call conversion information into Google Ads, you can track when phone calls lead to sales or other valuable customer actions. To learn how to import phone call conversions, refer to Import phone call conversions.
Enhanced Conversions
Using the Google Ads API, you can leverage enhanced conversionsby sending first-party customer data in the form of conversion adjustments. Google uses this additional data to improve the reporting of your online conversions driven by ad interactions.
Offline (Store) Conversions
Sometimes, an ad doesn't lead directly to an online sale, but instead starts a customer down a path that ultimately leads to a sale in the offline world, such as at your office or over the phone. By importing offline conversions, you can measure what happens in the offline world after your ad results in a click or call to your business.
Conversion Adjustments
A customer's typical conversion path ends after they convert, but this isn't always the case. Customers return retail purchases, cancel reservations, or perform actions that increase their value to your business. To account for these changes in conversion value, you can adjust the value of a conversion after it's reported in Google Ads.
What methods can I use to model my Databricks data?
dbt model selector
Sync directly with your dbt models saved in a git repository.
SQL editor
Create and Edit SQL from your browser. Hightouch supports SQL native to Databricks.
Sigma model
Hightouch converts your Sigma workbook element into a SQL query that runs directly on Databricks.
Table selector
Select available tables and sheets from Databricks and sync using existing views without having to write SQL.
Customer Studio
For less technical users, pass traits and audiences from Databricks using our visual segmentation builder.
FAQs
There are several options to sync data between sources. You can manually build and maintain a data pipeline, use a point-to-point solution such as Zapier, or you can manually upload CSVs.
With Hightouch, you get:
- Automation: You do not need to build and maintain custom data pipelines and you do not have to have your team do manual work
- Simplicity: You avoid a complex web of integrations caused by point-to-point solutions by syncing data from your source
- Speed: You can get set up in quickly - the average Hightouch customer starts syncing data in 23 minutes
- Control: companies of all sizes have access to enterprise-level controls including observability, dbt integrations, and version control
- Security: Hightouch never stores your data and is HIPAA, GDPR, CCPA, and SOC-2 compliant
90% of all Hightouch syncs complete in 30 seconds or less, and the platform enables non-technical users to self-serve.
With Hightouch, you can sync data as frequently as it changes within your Databricks. You can trigger data syncs manually or schedule them to run at an interval or custom recurrence as often as once per minute.
Hightouch offers a basic mapper or advanced mapper that allows you to visually match columns from your Databricks to fields in Google Ads.
Yes, if you integerate Databricks and Google Ads 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 Google Ads). 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 workshere.