Ready to get started?

Download a free trial of the DoubleClick Cmdlets to get started:

 Download Now

Learn more:

DoubleClick Campaign Manager Icon DoubleClick Cmdlets

An easy-to-use set of PowerShell Cmdlets offering real-time access to DoubleClick Campaign Manager data. The Cmdlets allow users to easily query live data - just like working with SQL server.

PowerShell Scripting to Replicate Google Campaign Manager Data to MySQL

Write a simple PowerShell script to replicate Google Campaign Manager data to a MySQL database.

The CData Cmdlets for Google Campaign Manager offer live access to Google Campaign Manager data from within PowerShell. Using PowerShell scripts, you can easily automate regular tasks like data replication. This article will walk through using the CData Cmdlets for Google Campaign Manager and the CData Cmdlets for MySQL in PowerShell to replicate Google Campaign Manager data to a MySQL database.

After obtaining the needed connection properties, accessing Google Campaign Manager data in PowerShell and preparing for replication consists of four basic steps.

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.

Collecting Google Campaign Manager Data

  1. Install the module:

    Install-Module GoogleCMCmdlets
  2. Connect to Google Campaign Manager:

    $googlecm = Connect-GoogleCM -UserProfileID $UserProfileID
  3. Retrieve the data from a specific resource:

    $data = Select-GoogleCM -Connection $googlecm -Table "CampaignPerformance"

    You can also use the Invoke-GoogleCM cmdlet to execute pure SQL-92 statements:

    $data = Invoke-GoogleCM -Connection $googlecm -Query 'SELECT * FROM CampaignPerformance WHERE Device = @Device' -Params @{'@Device'='Mobile devices with full browsers'}
  4. Save a list of the column names from the returned data.

    $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name

Inserting Google Campaign Manager Data into the MySQL Database

With the data and column names collected, you are ready to replicate the data into a MySQL database.

  1. Install the module:

    Install-Module MySQLCmdlets
  2. Connect to MySQL, using the server address and port of the MySQL server, valid user credentials, and a specific database with the table in which the data will be replicated:

    $mysql = Connect-MySQL -User $User -Password $Password -Database $Database -Server $Server -Port $Port
  3. Loop through the Google Campaign Manager data, store the values, and use the Add-MySQL cmdlet to insert the data into the MySQL database, one row at a time. In this example, the table will need to have the same name as the Google Campaign Manager resource (CampaignPerformance) and to exist in the database.

    $data | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "CampaignPerformance" -Columns $columns -Values $values }

You have now replicated your Google Campaign Manager data to a MySQL database. This gives you freedom to work with Google Campaign Manager data in the same way that you work with other MySQL tables, whether that is performing analytics, building reports, or other business functions.


  • Once you have connected to Google Campaign Manager and MySQL in PowerShell, you can pipe command results to perform the replication in a single line:

    Select-GoogleCM -Connection $googlecm -Table "CampaignPerformance" | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "CampaignPerformance" -Columns $columns -Values $values }
  • If you wish to replicate the Google Campaign Manager data to another database using another PowerShell module, you will want to exclude the Columns, Connection, and Table columns from the data returned by the Select-GoogleCM cmdlet since those columns are used to help pipe data from one CData cmdlet to another:

    $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name | ? {$_ -NotIn @('Columns','Connection','Table')}