Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect to Google Campaign Manager 360 Data in CloverDX (formerly CloverETL)
Transfer Google Campaign Manager 360 data using the visual workflow in the CloverDX data integration tool.
The CData JDBC Driver for Google Campaign Manager 360 enables you to use the data transformation components in CloverDX (formerly CloverETL) to work with Google Campaign Manager 360 as sources and destinations. In this article, you will use the JDBC Driver for Google Campaign Manager 360 to set up a simple transfer into a flat file. The CData JDBC Driver for Google Campaign Manager 360 enables you to use the data transformation components in CloverDX (formerly CloverETL) to work with Google Campaign Manager 360 as sources and destinations. In this article, you will use the JDBC Driver for Google Campaign Manager 360 to set up a simple transfer into a flat file.
Connect to Google Campaign Manager 360 as a JDBC Data Source
- Create the connection to Google Campaign Manager 360 data. In a new CloverDX graph, right-click the Connections node in the Outline pane and click Connections -> Create Connection. The Database Connection wizard is displayed.
- Click the plus icon to load a driver from a JAR. Browse to the lib subfolder of the installation directory and select the cdata.jdbc.googlecm.jar file.
- Enter the JDBC URL.
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

Query Google Campaign Manager 360 Data with the DBInputTable Component
- Drag a DBInputTable from the Readers selection of the Palette onto the job flow and double-click it to open the configuration editor.
- In the DB connection property, select the Google Campaign Manager 360 JDBC data source from the drop-down menu.
- Enter the SQL query. For example:
SELECT Clicks, Device FROM CampaignPerformance
Write the Output of the Query to a UniversalDataWriter
- Drag a UniversalDataWriter from the Writers selection onto the jobflow.
- Double-click the UniversalDataWriter to open the configuration editor and add a file URL.
- Right-click the DBInputTable and then click Extract Metadata.
- Connect the output port of the DBInputTable to the UniversalDataWriter.
- In the resulting Select Metadata menu for the UniversalDataWriter, choose the CampaignPerformance table. (You can also open this menu by right-clicking the input port for the UniversalDataWriter.)
- Click Run to write to the file.
