This page provides you with instructions on how to extract data from Google Ads and load it into Delta Lake on Databricks. (If this manual process sounds onerous, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)
What is Google Ads?
Google Ads (formerly AdWords) is a popular paid marketing tool. With Google Ads, you set a budget, select keywords, and publish ads that appear on Google search results pages relevant to your keywords. Google Ads collects data about campaigns that businesses can use to measure their effectiveness.
What is Delta Lake?
Delta Lake is an open source storage layer that sits on top of existing data lake file storage, such AWS S3, Azure Data Lake Storage, or HDFS. It uses versioned Apache Parquet files to store data, and a transaction log to keep track of commits, to provide capabilities like ACID transactions, data versioning, and audit history.
Getting data out of Google Ads
Google provides a SOAP API for Google Ads. The first step of getting your data into your data warehouse is pulling the data off of Google's servers by using the AdWords API's Reporting features. This is a subset of the API's functionality, which also includes the ability to manage ads.
You can also link your Google Analytics and Google Ads accounts to allow the data to cross-pollinate. This can provide richer reporting due to the breadth of knowledge that exists in Google Analytics about the people who may have viewed or clicked your ads.
You can extract granular data from AdWords API reports, allowing you to see things like impressions, clickthrough rates, and CPC broken out by time period.
Loading data into Delta Lake on Databricks
To create a Delta table, you can use existing Apache Spark SQL code and change the format from
delta. Once you have a Delta table, you can write data into it using Apache Spark's Structured Streaming API. The Delta Lake transaction log guarantees exactly-once processing, even when there are other streams or batch queries running concurrently against the table. By default, streams run in append mode, which adds new records to the table. Databricks provides quickstart documentation that explains the whole process.
Keeping Google Ads data up to date
So, now what? You've built a script that pulls data from Google Ads and loads it into your data warehouse, but what happens tomorrow when you have thousands of new impressions?
The key is to build your script in such a way that it can also identify incremental updates to your data. If you can identify some fields that auto-increment, you could use them to give your script the ability to recognize new data. You can then set your script up as a cron job or continuous loop to keep pulling down new data as it appears.
Other data warehouse options
Delta Lake on Databricks is great, but sometimes you need to optimize for different things when you're choosing a data warehouse. Some folks choose to go with Amazon Redshift, Google BigQuery, PostgreSQL, or Snowflake, which are RDBMSes that use similar SQL syntax, or Panoply, which works with Redshift instances. Others choose a data lake, like Amazon S3. If you're interested in seeing the relevant steps for loading data into one of these platforms, check out To Redshift, To BigQuery, To Postgres, To Snowflake, To Panoply, and To S3.
Easier and faster alternatives
If all this sounds a bit overwhelming, don’t be alarmed. If you have all the skills necessary to go through this process, chances are building and maintaining a script like this isn’t a very high-leverage use of your time.
Thankfully, products like Stitch were built to move data from Google Ads to Delta Lake on Databricks automatically. With just a few clicks, Stitch starts extracting your Google Ads data, structuring it in a way that's optimized for analysis, and inserting that data into your Delta Lake on Databricks data warehouse.