Process & Analyze Google Campaign Manager 360 Data in Databricks (AWS)

Databricks is a cloud-based service that provides data processing capabilities through Apache Spark. When paired with the CData JDBC Driver, customers can use Databricks to perform data engineering and data science on live Google Campaign Manager 360 data. This article walks through hosting the CData JDBC Driver in AWS, as well as connecting to and processing live Google Campaign Manager 360 data in Databricks.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live Google Campaign Manager 360 data. When you issue complex SQL queries to Google Campaign Manager 360, the driver pushes supported SQL operations, like filters and aggregations, directly to Google Campaign Manager 360 and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze Google Campaign Manager 360 data using native data types.

Install the CData JDBC Driver in Databricks

To work with live Google Campaign Manager 360 data in Databricks, install the driver on your Databricks cluster.

1. Navigate to your Databricks administration screen and select the target cluster.
2. On the Libraries tab, click "Install New."
3. Select "Upload" as the Library Source and "Jar" as the Library Type.
4. Upload the JDBC JAR file (cdata.jdbc.googlecm.jar) from the installation location (typically C:\Program Files\CData[product_name]\lib).

Access Google Campaign Manager 360 Data in your Notebook: Python

With the JAR file installed, we are ready to work with live Google Campaign Manager 360 data in Databricks. Start by creating a new notebook in your workspace. Name the notebook, select Python as the language (though Scala is available as well), and choose the cluster where you installed the JDBC driver. When the notebook launches, we can configure the connection, query Google Campaign Manager 360, and create a basic report.

Configure the Connection to Google Campaign Manager 360

Connect to Google Campaign Manager 360 by referencing the JDBC Driver class and constructing a connection string to use in the JDBC URL. Additionally, you will need to set the RTK property in the JDBC URL (unless you are using a Beta driver). You can view the licensing file included in the installation for information on how to set this property.

Step 1: Connection Information

driver = "cdata.jdbc.googlecm.GoogleCMDriver"
url = "jdbc:googlecm:RTK=5246...;UserProfileID=MyUserProfileID;InitiateOAuth=GETANDREFRESH"

Built-in Connection String Designer

For assistance in constructing the JDBC URL, use the connection string designer built into the Google Campaign Manager 360 JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

Fill in the connection properties and copy the connection string to the clipboard.

Google Campaign Manager uses the OAuth authentication standard. The data provider facilitates OAuth in various ways as described below. The following OAuth flow requires the authenticating user to interact with DoubleClick Campaign Manager, using the browser. You can also use a service account to authenticate.

For authentication guides, see the Getting Started section of the data provider help documentation.

Load Google Campaign Manager 360 Data

Once you configure the connection, you can load Google Campaign Manager 360 data as a dataframe using the CData JDBC Driver and the connection information.

Step 2: Reading the data

remote_table = spark.read.format ( "jdbc" ) \
	.option ( "driver" , driver) \
	.option ( "url" , url) \
	.option ( "dbtable" , "CampaignPerformance") \
	.load ()

Display Google Campaign Manager 360 Data

Check the loaded Google Campaign Manager 360 data by calling the display function.

Step 3: Checking the result

display (remote_table.select ("Clicks"))

Analyze Google Campaign Manager 360 Data in Databricks

If you want to process data with Databricks SparkSQL, register the loaded data as a Temp View.

Step 4: Create a view or table

remote_table.createOrReplaceTempView ( "SAMPLE_VIEW" )

With the Temp View created, you can use SparkSQL to retrieve the Google Campaign Manager 360 data for reporting, visualization, and analysis.

% sql

SELECT Clicks, Device FROM SAMPLE_VIEW ORDER BY Device DESC LIMIT 5

The data from Google Campaign Manager 360 is only available in the target notebook. If you want to use it with other users, save it as a table.

remote_table.write.format ( "parquet" ) .saveAsTable ( "SAMPLE_TABLE" )

Download a free, 30-day trial of the CData JDBC Driver for Google Campaign Manager 360 and start working with your live Google Campaign Manager 360 data in Databricks. Reach out to our Support Team if you have any questions.