Access Google Campaign Manager 360 Data in Mule Applications Using the CData JDBC Driver

The CData JDBC Driver for Google Campaign Manager 360 connects Google Campaign Manager 360 data to Mule applications enabling read , write, update, and delete functionality with familiar SQL queries. The JDBC Driver allows users to easily create Mule applications to backup, transform, report, and analyze Google Campaign Manager 360 data.

This article demonstrates how to use the CData JDBC Driver for Google Campaign Manager 360 inside of a Mule project to create a Web interface for Google Campaign Manager 360 data. The application created allows you to request Google Campaign Manager 360 data using an HTTP request and have the results returned as JSON. The exact same procedure outlined below can be used with any CData JDBC Driver to create a Web interface for the hundreds of available data sources.

1. Create a new Mule Project in Anypoint Studio.
2. Add an HTTP Connector to the Message Flow.
3. Configure the address for the HTTP Connector. 👁 Add and Configure the HTTP Connector
   
4. Add a Database Select Connector to the same flow, after the HTTP Connector.
5. Create a new Connection (or edit an existing one) and configure the properties.
   • Set Connection to "Generic Connection"
   • Select the CData JDBC Driver JAR file in the Required Libraries section (e.g. cdata.jdbc.googlecm.jar). 👁 Adding the JAR file (Salesforce is shown).
     
   • Set the URL to the connection string for 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.

   • Set the Driver class name to cdata.jdbc.googlecm.GoogleCMDriver. 👁 A configured Database Connection (Salesforce is shown).
     
   • Click Test Connection.
6. Set the SQL Query Text to a SQL query to request Google Campaign Manager 360 data. For example:

   SELECT Clicks, Device FROM CampaignPerformance

   👁 Configure the Select object (Salesforce is Shown)
   
7. Add a Transform Message Component to the flow.
8. Set the Output script to the following to convert the payload to JSON:

   %dw 2.0
   output application/json
   ---
   payload
    

   👁 Add the Transform Message Component to the Flow
   
9. To view your Google Campaign Manager 360 data, navigate to the address you configured for the HTTP Connector (localhost:8081 by default): http://localhost:8081. The Google Campaign Manager 360 data is available as JSON in your Web browser and any other tools capable of consuming JSON endpoints.

At this point, you have a simple Web interface for working with Google Campaign Manager 360 data (as JSON data) in custom apps and a wide variety of BI, reporting, and ETL tools. Download a free, 30 day trial of the JDBC Driver for Google Campaign Manager 360 and see the CData difference in your Mule Applications today.