Learn more
 

Replicate Google Ads Data from PowerShell


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



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

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

You can also write PowerShell code to download Google Ads data. See the examples below.

Create an ODBC Data Source for Google Ads

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 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.

Connect to Google Ads

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

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

Back Up Google Ads 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 Ads 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 commands to Google Ads through the .NET Framework Provider for ODBC:

Retrieve Google Ads Data

$sql="SELECT Device, Clicks 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[$_] } }

Ready to get started?

Download a free trial of the Google AdWords ODBC Driver to get started:

 Download Now

Learn more:

Google AdWords Icon Google AdWords ODBC Driver

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

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

In this article

Related articles