Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Query Google Ads Data in ColdFusion
Write standard ColdFusion data access code to connect to Google Ads data.
The CData JDBC driver for Google Ads seamlessly integrates connectivity to Google Ads data with the rapid development tools in ColdFusion. This article shows how to connect to Google Ads data in ColdFusion and query Google Ads tables.
Create a JDBC Data Source for Google Ads in ColdFusion
The JDBC data source enables you to execute SQL from standard ColdFusion tags like cfquery and CFScript like executeQuery.
-
Copy the driver JAR and .lic file from the installation directory onto the ColdFusion classpath. For example, copy the files into C:\MyColdFusionDirectory\cfusion\wwwroot\WEB-INF\lib. Or, open the Java and JVM page in the ColdFusion Administrator and enter the path to the files in the ColdFusion Class Path box.
The JAR and license for the driver are located in the lib subfolder of the installation directory.
Restart the server after this step.
-
Add the driver as a data source:
From the ColdFusion administrator interface, expand the Data & Services node and click Data Sources. In the Add New Data Source section, enter a name for the data source and select Other in the Driver menu.
-
Populate the driver properties:
JDBC URL: Enter connection properties in the JDBC URL. The JDBC URL begins with jdbc:googleads: and is followed by the connection properties in a semicolon-separated list of name=value pairs.
Google uses the OAuth authentication standard. To access Google APIs on behalf on individual users, you can use the embedded credentials or you can register your own OAuth app.
OAuth also enables you to use a service account to connect on behalf of users in a Google Apps domain. To authenticate with a service account, you will need to register an application to obtain the OAuth JWT values.
In addition to the OAuth values, specify the DeveloperToken and ClientCustomerId.
See the "Getting Started" chapter of the help documentation for a guide to using OAuth.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Google Ads JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.googleads.jar
Fill in the connection properties and copy the connection string to the clipboard.
A typical JDBC URL is below:
jdbc:googleads:DeveloperToken=MyDeveloperToken;ClientCustomerId=MyClientCustomerId;InitiateOAuth=GETANDREFRESH
- Driver Class: Enter the driver class. The driver class is cdata.jdbc.googleads.GoogleAdsDriver.
- Driver Name: Enter a user-defined name for the driver.
- Username: Enter the username used to authenticate.
- Password: Enter the password used to authenticate.
You can now test the connection by enabling the CData Google Ads data source in the Actions column. After reporting a status of OK, the Google Ads data source is ready for use.
Execute Queries
The cfquery tag can pass SQL statements to Google Ads. Use the cfqueryparam tag to create parameterized queries and prevent SQL injection through the query string.
Note: To use the cfquery and cfscript, create a .cfm file. Inside the .cfm file, write the code to execute the query (see below). Place the file directly in the root directory of your web server (e.g., wwwroot in Adobe ColdFusion). Restart the service after placing the file for the changes to take effect.
<cfquery name="GoogleAdsQuery" dataSource="CDataGoogleAds">
SELECT * FROM CampaignPerformance WHERE Device = <cfqueryparam value="#Device#" cfsqltype="cf_sql_varchar">
</cfquery>
<cfdump var="#GoogleAdsQuery#">
Below is the equivalent in CFScript:
<cfscript> result = queryExecute( "SELECT * FROM CampaignPerformance WHERE Device = ?", [ { value="'Mobile devices with full browsers'", cfsqltype="cf_sql_varchar" } ], { datasource="CDataGoogleAds" } ); writeDump( var= result ); </cfscript>
You can then make requests to your .cfm like the following:
http://MyServer:8500/query.cfm?Device='Mobile devices with full browsers'