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

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

CData Connect Cloud provides a pure MySQL, cloud-to-cloud interface for Google Campaign Manager 360, allowing you to easily query live Google Campaign Manager 360 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 360, leveraging server-side processing to quickly return Google Campaign Manager 360 data.

Configure Google Campaign Manager 360 Connectivity for NodeJS

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

1. Log into Connect Cloud, click Sources, and then click Add Connection

2. Select "Google Campaign Manager 360" from the Add Connection panel

3. Enter the necessary authentication properties to connect to 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.

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

Add a Personal Access Token

When connecting to Connect Cloud through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect Cloud. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect Cloud app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the 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 and a PAT generated, you are ready to connect to Google Campaign Manager 360 data from Node.js.

Query Google Campaign Manager 360 from Node.js

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

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

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

var sql = require('mssql')
var config = {
	server: 'tds.cdata.com',
	port: 14333, 
	user: '[email protected]', //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);
})