A PostgreSQL Interface for Google Campaign Manager 360 Data

There are a vast number of PostgreSQL clients available on the Internet. From standard Drivers to BI and Analytics tools, PostgreSQL is a popular interface for data access. Using our JDBC Drivers, you can now create PostgreSQL entry-points that you can connect to from any standard client.

To access Google Campaign Manager 360 data as a PostgreSQL database, use the CData JDBC Driver for Google Campaign Manager 360 and a JDBC foreign data wrapper (FDW). In this article, we compile the FDW, install it, and query Google Campaign Manager 360 data from PostgreSQL Server.

Connect to Google Campaign Manager 360 Data as a JDBC Data Source

To connect to Google Campaign Manager 360 as a JDBC data source, you will need the following:

• Driver JAR path: The JAR is located in the lib subfolder of the installation directory.

• Driver class: cdata.jdbc.googlecm.GoogleCMDriver

• JDBC URL: The URL must start with "jdbc:googlecm:" and can include any of the connection properties in name-value pairs separated with semicolons.

  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.

  A typical JDBC URL is below:

  jdbc:googlecm:UserProfileID=MyUserProfileID;InitiateOAuth=GETANDREFRESH

Build the JDBC Foreign Data Wrapper

The Foreign Data Wrapper can be installed as an extension to PostgreSQL, without recompiling PostgreSQL. The jdbc2_fdw extension is used as an example (downloadable here).

1. Add a symlink from the shared object for your version of the JRE to /usr/lib/libjvm.so. For example: ln -s /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/libjvm.so /usr/lib/libjvm.so
2. Start the build: make install USE_PGXS=1

Query Google Campaign Manager 360 Data as a PostgreSQL Database

After you have installed the extension, follow the steps below to start executing queries to Google Campaign Manager 360 data:

1. Log into your database.
2. Load the extension for the database: CREATE EXTENSION jdbc2_fdw;
3. Create a server object for Google Campaign Manager 360: CREATE SERVER GoogleCM FOREIGN DATA WRAPPER jdbc2_fdw OPTIONS ( drivername 'cdata.jdbc.googlecm.GoogleCMDriver', url 'jdbc:googlecm:UserProfileID=MyUserProfileID;InitiateOAuth=GETANDREFRESH', querytimeout '15', jarfile '/home/MyUser/CData/CData\ JDBC\ Driver\ for\ Salesforce MyDriverEdition/lib/cdata.jdbc.googlecm.jar');
4. Create a user mapping for the username and password of a user known to the MySQL daemon. CREATE USER MAPPING for postgres SERVER GoogleCM OPTIONS ( username 'admin', password 'test');
5. Create a foreign table in your local database: postgres=# CREATE FOREIGN TABLE campaignperformance ( campaignperformance_id text, campaignperformance_Clicks text, campaignperformance_Device numeric) SERVER GoogleCM OPTIONS ( table_name 'campaignperformance');