Query Google Campaign Manager Data as a SQL Server Database in Node.js

You can use CData Connect Cloud to query Google Campaign Manager data through a SQL Server interface. Follow the procedure below to create a virtual database for Google Campaign Manager in Connect Cloud and start querying using Node.js.

CData Connect Cloud provides a pure MySQL, cloud-to-cloud interface for Google Campaign Manager, allowing you to easily query live Google Campaign Manager data in Node.js — without replicating the data to a natively supported database. As you query data in Node.js, CData Connect Cloud pushes all supported SQL operations (filters, JOINs, etc) directly to Google Campaign Manager, leveraging server-side processing to quickly return Google Campaign Manager data.

Configure Google Campaign Manager Connectivity for NodeJS

Connectivity to Google Campaign Manager from NodeJS is made possible through CData Connect Cloud. To work with Google Campaign Manager data from NodeJS, we start by creating and configuring a Google Campaign Manager connection.

1. Log into Connect Cloud, click Connections and click Add Connection
2. Select "Google Campaign Manager" from the Add Connection panel
3. Enter the necessary authentication properties to connect to Google Campaign Manager.

   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.

4. Click Create & Test
5. Navigate to the Permissions tab in the Add Google Campaign Manager Connection page and update the User-based permissions.

Add a Personal Access Token

If you are connecting from a service, application, platform, or framework that does not support OAuth authentication, you can create a Personal Access Token (PAT) to use for authentication. Best practices would dictate that you create a separate PAT for each service, to maintain granularity of access.

1. Click on your username at the top right of the Connect Cloud app and click User Profile.
2. On the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
3. Give your PAT a name and click Create.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured, you are ready to connect to Google Campaign Manager data from Node.js.

Query Google Campaign Manager from Node.js

The following example shows how to define a connection and execute queries to Google Campaign Manager with the SQL Server module. You will need the following information:

• server: tds.cdata.com
• port: 14333
• user: a Connect Cloud user (e.g. user@mydomain.com)
• password: the PAT for the above user
• database: The connection you configured for Google Campaign Manager (GoogleCM1)

Connect to Google Campaign Manager data and start executing queries with the code below:

var sql = require('mssql')
var config = {
	server: 'tds.cdata.com',
	port: 14333, 
	user: 'user@mydomain.com', //update me
	password: 'CONNECT_USER_PAT', //update me	
	options: {
		encrypt: true,
		database: 'GoogleCM1'
	}
}

sql.connect(config, err => { 
    if(err){
        throw err ;
    }
    new sql.Request().query('SELECT * FROM CampaignPerformance', (err, result) => {
        console.dir(result)
    })
        
});

sql.on('error', err => {
    console.log("SQL Error: " ,err);
})