Load Google Campaign Manager 360 Data to a Database Using Embulk

Embulk is an open source bulk data loader. When paired with the CData JDBC Driver for Google Campaign Manager 360, Embulk easily loads data from Google Campaign Manager 360 to any supported destination. In this article, we explain how to use the CData JDBC Driver for Google Campaign Manager 360 in Embulk to load Google Campaign Manager 360 data to a MySQL dtabase.

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).

Configure a JDBC Connection to Google Campaign Manager 360 Data

Before creating a bulk load job in Embulk, note the installation location for the JAR file for the JDBC Driver (typically C:\Program Files\CData\CData JDBC Driver for Google Campaign Manager 360\lib).

Embulk supports JDBC connectivity, so you can easily connect to Google Campaign Manager 360 and execute SQL queries. Before creating a bulk load job, create a JDBC URL for authenticating with Google Campaign Manager 360.

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.

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.

java -jar cdata.jdbc.googlecm.jar

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

👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)

Below is a typical JDBC connection string for Google Campaign Manager 360:

jdbc:googlecm:UserProfileID=MyUserProfileID;InitiateOAuth=GETANDREFRESH;

Load Google Campaign Manager 360 Data in Embulk

After installing the CData JDBC Driver and creating a JDBC connection string, install the required Embulk plugins.

Install Embulk Input & Output Plugins

1. Install the JDBC Input Plugin in Embulk.
   https://github.com/embulk/embulk-input-jdbc/tree/master/embulk-input-jdbc

embulk gem install embulk-input-jdbc

2. In this article, we use MySQL as the destination database. You can also choose SQL Server, PostgreSQL, or Google BigQuery as the destination using the output Plugins.
   https://github.com/embulk/embulk-output-jdbc/tree/master/embulk-output-mysql

   embulk gem install embulk-output-mysql
   

With the input and output plugins installed, we are ready to load Google Campaign Manager 360 data into MySQL using Embulk.

Create a Job to Load Google Campaign Manager 360 Data

Start by creating a config file in Embulk, using a name like googlecm-mysql.yml.

1. For the input plugin options, use the CData JDBC Driver for Google Campaign Manager 360, including the path to the driver JAR file, the driver class (e.g. cdata.jdbc.googlecm.GoogleCMDriver), and the JDBC URL from above
2. For the output plugin options, use the values and credentials for the MySQL database

Sample Config File (googlecm-mysql.yml)

in:
	type: jdbc
	driver_path: C:\Program Files\CData[product_name] 20xx\lib\cdata.jdbc.googlecm.jar
	driver_class: cdata.jdbc.googlecm.GoogleCMDriver
	url: jdbc:googlecm:UserProfileID=MyUserProfileID;InitiateOAuth=GETANDREFRESH;
	table: "CampaignPerformance"
out: 
	type: mysql
	host: localhost
	database: DatabaseName
	user: UserId
	password: UserPassword
	table: "CampaignPerformance"
	mode: insert

After creating the file, run the Embulk job.

embulk run googlecm-mysql.yml

After running the the Embulk job, find the Salesforce data in the MySQL table.

Load Filtered Google Campaign Manager 360 Data

In addition to loading data directly from a table, you can use a custom SQL query to have more granular control of the data loaded. You can also perform increment loads by setting a last updated column in a SQL WHERE clause in the query field.

in:
	type: jdbc
	driver_path: C:\Program Files\CData[product_name] 20xx\lib\cdata.jdbc.googlecm.jar
	driver_class: cdata.jdbc.googlecm.GoogleCMDriver
	url: jdbc:googlecm:UserProfileID=MyUserProfileID;InitiateOAuth=GETANDREFRESH;
	query: "SELECT Clicks, Device FROM CampaignPerformance WHERE [RecordId] = 1"
out: 
	type: mysql
	host: localhost
	database: DatabaseName
	user: UserId
	password: UserPassword
	table: "CampaignPerformance"
	mode: insert

More Information & Free Trial

By using CData JDBC Driver for Google Campaign Manager 360 as a connector, Embulk can integrate Google Campaign Manager 360 data into your data load jobs. And with drivers for more than 200+ other enterprise sources, you can integrate any enterprise SaaS, big data, or NoSQL source as well. Download a 30-day free trial and get started today.