Learn more
 

Replicate Google Campaign Manager 360 Data from PowerShell


Write a quick PowerShell script to query Google Campaign Manager 360 data. Use connectivity to the live data to replicate Google Campaign Manager 360 data to SQL Server.



The CData ODBC Driver for Google Campaign Manager 360 enables out-of-the-box integration with Microsoft's built-in support for ODBC. The ODBC driver instantly integrates connectivity to the real Google Campaign Manager 360 data with PowerShell.

You can use the .NET Framework Provider for ODBC built into PowerShell to quickly automate integration tasks like replicating Google Campaign Manager 360 data to other databases. This article shows how to replicate Google Campaign Manager 360 data to SQL Server in 5 lines of code.

You can also write PowerShell code to execute create, read, update, and delete (CRUD) operations. See the examples below.

Create an ODBC Data Source for Google Campaign Manager 360

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

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.

Connect to Google Campaign Manager 360

The code below shows how to use the DSN to initialize the connection to Google Campaign Manager 360 data in PowerShell:

$conn = New-Object System.Data.Odbc.OdbcConnection $conn.ConnectionString = "DSN=CData GoogleCM Source x64"

Back Up Google Campaign Manager 360 Data to SQL Server

After you enable caching, you can use the code below to replicate data to SQL Server.

Set the following connection properties to configure the caching database:

  • CacheProvider: The name of the ADO.NET provider. This can be found in the Machine.config for your version of .NET. For example, to configure SQL Server, enter System.Data.SqlClient.

  • CacheConnection: The connection string of properties required to connect to the database. Below is an example for SQL Server:

    Server=localhost;Database=RSB;User Id=sqltest;Password=sqltest;

The SQL query in the example can be used to refresh the entire cached table, including its schema. Any already existing cache is deleted.

$conn.Open() # Create and execute the SQL Query $SQL = "CACHE DROP EXISTING SELECT * FROM " + $CampaignPerformance $cmd = New-Object System.Data.Odbc.OdbcCommand($sql,$conn) $count = $cmd.ExecuteNonQuery() $conn.Close()

The driver gives you complete control over the caching functionality. See the help documentation for more caching commands and usage examples. See the help documentation for steps to replicate to other databases.

Other Operations

To retrieve Google Campaign Manager 360 data in PowerShell, call the Fill method of the OdbcDataAdapter method. To execute data manipulation commands, initialize the OdbcCommand object and then call ExecuteNonQuery. Below are some more examples CRUD commands to Google Campaign Manager 360 through the .NET Framework Provider for ODBC:

Retrieve Google Campaign Manager 360 Data

$sql="SELECT Clicks, Device from CampaignPerformance" $da= New-Object System.Data.Odbc.OdbcDataAdapter($sql, $conn) $dt= New-Object System.Data.DataTable $da.Fill($dt) $dt.Rows | foreach { $dt.Columns | foreach ($col in dt{ Write-Host $1[$_] } }

Update Google Campaign Manager 360 Data

$cmd = New-Object System.Data.Odbc.OdbcCommand("UPDATE CampaignPerformance SET Device='Mobile devices with full browsers' WHERE Id = @myId", $conn) $cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH") $cmd.ExecuteNonQuery()

Insert Google Campaign Manager 360 Data

$cmd = New-Object System.Data.Odbc.OdbcCommand("INSERT INTO CampaignPerformance SET Device='Mobile devices with full browsers' WHERE Id = @myId", $conn) $cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH") $cmd.ExecuteNonQuery()

Delete Google Campaign Manager 360 Data

$cmd = New-Object System.Data.Odbc.OdbcCommand("DELETE FROM CampaignPerformance WHERE Id = @myid", $conn) $cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myId","001d000000YBRseAAH") $cmd.ExecuteNonQuery()

Ready to get started?

Download a free trial of the Google Campaign Manager 360 ODBC Driver to get started:

 Download Now

Learn more:

Google Campaign Manager 360 Icon Google Campaign Manager 360 ODBC Driver

The Google Campaign Manager 360 ODBC Driver is a powerful tool that allows you to connect with live data from Google Campaign Manager 360, directly from any applications that support ODBC connectivity.

Access Google Campaign Manager 360 data like you would a database - access all kinds of real-time performance and analysis data through a standard ODBC Driver interface.

In this article

Related articles