How to integrate Google Ads with Power BI

Learn how to quickly and efficiently connect Google Ads with Power BI for smooth data access.

Read and write Google Ads data effortlessly. Integrate, manage, and automate campaigns, ad groups, keywords, and performance — almost no coding required. You can do it all using the high-performance Google Ads ODBC Driver for Power BI (often referred to as the Google Ads Connector). We'll walk you through the entire setup.

Ready to dive in? Download the product to jump right in, or follow the step-by-step guide below to see how it works.

Google Ads ODBC Driver Powering this integration

High performance
Bidirectional
Low-code / No-code
Easy to use

Built on the ZappySys API Driver, the Google Ads ODBC Driver is a high-performance, low-code / no-code solution. It enables you to connect to Google Ads data without any coding right in your SQL Server, or any ODBC/JDBC application. Part of the ODBC PowerPack.

Documentation

Video Tutorial

This video covers the following topics and more, so please watch carefully. After watching the video, follow the steps outlined in this article:

How to download and install the required PowerPack for Google Ads integration in Power BI
How to configure the connection for Google Ads
Features of the ZappySys API Driver (Authentication / Query Language / Examples / Driver UI)
How to use the Google Ads in Power BI

Create data source using Google Ads ODBC Driver

Step-by-step instructions

To get data from Google Ads using Power BI, we first need to create an ODBC data source. We will later read this data in Power BI. Perform these steps:

Download and install ODBC PowerPack (if you haven't already).
Search for odbc and open the ODBC Data Sources (64-bit):
Create a User data source (User DSN) based on the ZappySys API Driver driver:

ZappySys API Driver
- Create and use a User DSN if the client application runs under a User Account. This is the ideal option at design time (e.g., when developing in Visual Studio). Use it for both types of applications (64-bit and 32-bit).
- Create and use a System DSN if the client application runs under a System Account (e.g., as a Windows Service). This is usually the required option in a production environment. If your Windows Service is a 32-bit application, you must use the 32-bit ODBC Data Source Administrator to configure this
When deployed to production, Power BI runs under a Service Account. Therefore, for the production environment, you must create and use a System DSN.
When the Configuration window appears give your data source a name if you haven't done that already, then select "Google Ads" from the list of Popular Connectors. If "Google Ads" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

GoogleAdsDSN

Google Ads

Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

User Account

Google Ads authentication

User accounts represent a developer, administrator, or any other person who interacts with Google APIs and services. User accounts are managed as Google Accounts, either with Google Workspace or Cloud Identity. They can also be user accounts that are managed by a third-party identity provider and federated with Workforce Identity Federation. [API reference]

Follow these steps on how to create Client Credentials (User Account principle) to authenticate and access Google Ads API in SSIS package or ODBC data source:

WARNING: If you are planning to automate processes, we recommend that you use a Service Account authentication method. In case, you still need to use User Account, then make sure you use a system/generic account (e.g. automation@my-company.com). When you use a personal account which is tied to a specific employee profile and that employee leaves the company, the token may become invalid and any automated processes using that token will start to fail.

Manager Account Setup - Obtain Developer Token

To access Google Ads API (your data or someone else data) you must perform the following steps (high level). Detailed steps listed in the next sections.

Create a Google Ads Manager account (formally known as MCC).
Apply for Production data access (Upgrade Developer Token access Level to Basic).
Link manager account with Google Ads Account.
Create a new Project and obtain Client Id and Client Secret

Step-1: Create a Google Ads Manager account (formally known as MCC)

Very first step to access Google Ads API for your own account or someone else account, you will need something called Google Manager Account (formally known as MCC). It will look like a Normal Google Ads Account with some difference so dont get confused if you see similar interface as Ads account.
Click here to see detailed instructions on how to create a manager account. Once you created a manager account, you can login or switch between Ads account and Manager account like below. You can identify manager account using "Manager" word next to the account id when you click Profile dropdown.

Step-2: Obtain Developer Token

Once you have created and logged in to your Google Ads Manager Account (formally known as MCC) we are ready for the next step which is obtain Developer Token. To access Google Ads API you need to pass developer token in each API call. By default Developer Token is only allowed to access Sandbox (Test) account. If you like to access Production data (Live Ads Account) then you must apply for Basic Access by clicking link under Access Level (See next section for information).
Here is how to can obtain your Developer Token.

Log in as Manager account (Or change Top-Right Profile > Choose Manager account ID
Click on Admin icon
Click on API Center (This option will be missing if you are logged in to Regular Ads account as Client and not using Manager Account (MMC)
Expand Access Level, Click Apply for Basic Access if it says "Test". By default Developer Token is created with Test Account access only. To access Production Ads account you must apply for higher access level. Must be Basic or Standard (not Test). After click the link you will see form with few questions, please fill out that and submit the form. Apploval process may take 3-5 days (or longer in some cases if you did not provide enough information).
If your token is already approved for the basic access then copy the token and paste on the Google Ads Connector - Connection UI (For Developer Token property)

Click here to see detailed instructions on obtaining a developer token

Developer Token for Google Ads API Access in API Center (Visible when logged in as Manager Account)

Link Manager Account to Google Ads Account

After you have manager account ready, next step is to link manager account with Google Ads Account. You have to send invitation from Manager account to access Google Ads account (it can be your own account or someone else). Here is how to send invite to link Google Ads account.

Log in as Manager account (Or change Top-Right Profile > Choose Manager account ID
Click on Accounts icon > Sub-account settings > Send Link Request
Click on Add Sign (+) and select + Link existing account option
When prompted enter Account Id(s) you like to link with this Manager Account.
Click Send Request. You can find Ad Account Id usually at the Top-Right corner after you login to the Google Ads account.
Now ask Google Ads Account owner to check email. Click Accept Invitation link in the email (If prompted login as Google Ads Account owner).
-OR-
Another way to see Invitation, Login to Google Ads account (Or Switch from the Top-Right corner by clicking Profile icon). Go to Admin icon > Access and security > Managers Tab. Find the pending invitation and click ACCEPT.
That's it. Now your Manager account is linked to the Google Ads account

Obtain ClientId and ClientSecret

Step-1: Create project

This step is optional, if you already have a project in Google Cloud and can use it. However, if you don't, proceed with these simple steps to create one:

First of all, go to Google API Console.
Then click Select a project button and then click NEW PROJECT button:
Name your project and click CREATE button:
Wait until the project is created:
Done! Let's proceed to the next step.

Step-2: Enable Google Ads API

In this step we will enable Google Ads API:

Select your project on the top bar:
Then click the "hamburger" icon on the top left and access APIs & Services:
Now let's enable several APIs by clicking ENABLE APIS AND SERVICES button:
In the search bar search for Ads and then locate and select Google Ads API:
Enable Google Ads API:
Done! Let's proceed to the next step.

Step-3: Create OAuth application

First of all, click the "hamburger" icon on the top left and then hit VIEW ALL PRODUCTS:
Then access Google Auth Platform to start creating an OAuth application:
Start by pressing GET STARTED button:
Next, continue by filling in App name and User support email fields:
Choose Internal option, if it's enabled, otherwise select External:
Optional step if you used Internal option in the previous step. Nevertheless, if you had to use External option, then click ADD USERS to add a user:
Then add your contact Email address:
Finally, check the checkbox and click CREATE button:
Done! Let's create Client Credentials in the next step.

Step-4: Create Client Credentials

In Google Auth Platform, select Clients menu item and click CREATE CLIENT button:
Choose Desktop app as Application type and name your credentials:
Continue by opening the created credentials:
Finally, copy Client ID and Client secret for the later step:
Done! We have all the data needed for authentication, let's proceed to the last step!

Step-5: Configure connection

Now go to SSIS package or ODBC data source and use previously copied values in User Account authentication configuration:
- In the ClientId field paste the Client ID value.
- In the ClientSecret field paste the Client secret value.
- In the DeveloperToken field paste the Developer Token value.
Press Generate Token button to generate Access and Refresh Tokens.
Finally, click Test Connection to confirm the connection is working.
Done! Now you are ready to use Google Ads Connector!

API Connection Manager configuration

Just perform these simple steps to finish authentication configuration:

Set Authentication Type to User Account [OAuth]
Optional step. Modify API Base URL if needed (in most cases default will work).
Fill in all the required parameters and set optional parameters if needed.
Press Generate Token button to generate the tokens.
Finally, hit OK button:

GoogleAdsDSN

Google Ads

User Account [OAuth]

https://googleads.googleapis.com/[$ApiVersion$]

Required Parameters
UseCustomApp	Fill-in the parameter...
CustomerId (without dash e.g. 2125557752)	Fill-in the parameter...
DeveloperToken	Fill-in the parameter...
Optional Parameters
ClientId
ClientSecret
Scope	https://www.googleapis.com/auth/adwords
Login CustomerId (without dash e.g. 2125557752)
Linked CustomerId (without dash e.g. 2125557752)
API Version	v20
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True
Redirect URL (Only for Web App)

Service Account (Using .json OR .p12 key file)

Google Ads authentication

Service accounts are accounts that do not represent a human user. They provide a way to manage authentication and authorization when a human is not directly involved, such as when an application needs to access Google Cloud resources. Service accounts are managed by IAM. [API reference]

To access Google Ads API (your data or someone else data) you must perform the following steps (high level). Detailed steps listed in the next sections.

Create a Manager account.
Apply for Production data access (Upgrade Developer Token access Level to Basic).
Link manager account with Google Ads Account.
Inside Manager account apply for Basic API Access level so you can use Developer Token to access Live data (Production Ads account). Without Basic access level Developer Token can be only used for Test / Sandbox Ads account.
Create a new Project and obtain Client Id and Client Secret

Manager Account Setup - Obtain Developer Token

To access Google Ads API (your data or someone else data) you must perform the following steps (high level). Detailed steps listed in the next sections.

Create a Google Ads Manager account (formally known as MCC).
Apply for Production data access (Upgrade Developer Token access Level to Basic).
Link manager account with Google Ads Account.
Create a new Project and obtain Service Account details

Step-1: Create a Google Ads Manager account (formally known as MCC)

Step-2: Obtain Developer Token

Log in as Manager account (Or change Top-Right Profile > Choose Manager account ID
Click on Admin icon
Click on API Center (This option will be missing if you are logged in to Regular Ads account as Client and not using Manager Account (MMC)
Expand Access Level, Click Apply for Basic Access if it says "Test". By default Developer Token is created with Test Account access only. To access Production Ads account you must apply for higher access level. Must be Basic or Standard (not Test). After click the link you will see form with few questions, please fill out that and submit the form. Apploval process may take 3-5 days (or longer in some cases if you did not provide enough information).
If your token is already approved for the basic access then copy the token and paste on the Google Ads Connector - Connection UI (For Developer Token property)

Click here to see detailed instructions on obtaining a developer token

Link Manager Account to Google Ads Account

Log in as Manager account (Or change Top-Right Profile > Choose Manager account ID
Click on Accounts icon > Sub-account settings > Send Link Request
Click on Add Sign (+) and select + Link existing account option
When prompted enter Account Id(s) you like to link with this Manager Account.
Click Send Request. You can find Ad Account Id usually at the Top-Right corner after you login to the Google Ads account.
Now ask Google Ads Account owner to check email. Click Accept Invitation link in the email (If prompted login as Google Ads Account owner).
-OR-
Another way to see Invitation, Login to Google Ads account (Or Switch from the Top-Right corner by clicking Profile icon). Go to Admin icon > Access and security > Managers Tab. Find the pending invitation and click ACCEPT.
That's it. Now your Manager account is linked to the Google Ads account

Obtain ClientId and ClientSecret

Step-1: Create project

This step is optional, if you already have a project in Google Cloud and can use it. However, if you don't, proceed with these simple steps to create one:

First of all, go to Google API Console.
Then click Select a project button and then click NEW PROJECT button:
Name your project and click CREATE button:
Wait until the project is created:
Done! Let's proceed to the next step.

Step-2: Enable Google Ads API

In this step we will enable Google Ads API:

Select your project on the top bar:
Then click the "hamburger" icon on the top left and access APIs & Services:
Now let's enable several APIs by clicking ENABLE APIS AND SERVICES button:
In the search bar search for ads and then locate and select Google Ads API:
Enable Google Ads API:
Done! Let's proceed to the next step.

Step-3: Create Service Account

Use the steps below to create a Service Account in Google Cloud:

First of all, go to IAM & Admin in Google Cloud console:
Once you do that, click Service Accounts on the left side and click CREATE SERVICE ACCOUNT button:
Then name your service account and click CREATE AND CONTINUE button:
Continue by clicking Select a role dropdown and start granting service account Project Viewer roles:
Find Project group and select Viewer role:
Finish adding roles by clicking CONTINUE button:

You can always add or modify permissions later in IAM & Admin.
Finally, in the last step, just click button DONE:
Done! We are ready to add a Key to this service account in the next step.

Step-4: Add Key to Service Account

We are ready to add a Key (JSON or P12 key file) to the created Service Account:

In Service Accounts open newly created service account:
Next, copy email address of your service account for the later step:
Continue by selecting KEYS tab, then press ADD KEY dropdown, and click Create new key menu item:
Finally, select JSON (Engine v19+) or P12 option and hit CREATE button:
Key file downloads into your machine. We have all the data needed for authentication, let's proceed to the last step!

Step-5: Give Permissions to Service Account

Now it's time to grant permission to Service Account we just created:

Login to https://ads.google.com/aw/settings/account with Google Ads account credentials (If propmpted choose your Ads account).
Go to Admin section, Access and security, Click on Users tab.
Click on Add Icon (+) and enter service account email address which you like to use for data access and choose permissions.
That's it! Let's proceed to the configuration!

Step-6: Configure connection

Now go to SSIS package or ODBC data source and configure these fields in Service Account authentication configuration:
- In the Service Account Email field paste the service account Email address value you copied in the previous step.
- In the Service Account Private Key Path (i.e. *.json OR *.p12) field use downloaded key file path.
Done! Now you are ready to use Google Ads Connector!

If you received an error saying DEVELOPER_TOKEN_PROHIBITED then read the following workaround.

Each Google API Console project can be associated with the developer token from only one manager account. Once you make a Google Ads API request, the developer token is permanently paired to the Google API Console project. If you don't use a new Google API Console project, you'll get a DEVELOPER_TOKEN_PROHIBITED error when making a request. Unfortunatly there is no other way to Unlink old Developer Token from the API Project, so for now just create a new Project as a workaround to fix this error.

API Connection Manager configuration

Just perform these simple steps to finish authentication configuration:

Set Authentication Type to Service Account (Using *.json OR *.p12 key file) [OAuth]
Optional step. Modify API Base URL if needed (in most cases default will work).
Fill in all the required parameters and set optional parameters if needed.
Finally, hit OK button:

GoogleAdsDSN

Google Ads

Service Account (Using *.json OR *.p12 key file) [OAuth]

https://googleads.googleapis.com/[$ApiVersion$]

Required Parameters
Service Account Email	Fill-in the parameter...
Service Account Private Key Path (i.e. .json OR .p12)	Fill-in the parameter...
CustomerId (without dash e.g. 2125557752)	Fill-in the parameter...
DeveloperToken	Fill-in the parameter...
Optional Parameters
Scope	https://www.googleapis.com/auth/adwords
Login CustomerId (without dash e.g. 2125557752)
Linked CustomerId (without dash e.g. 2125557752)
API Version	v20
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True
Impersonate As (Google account email address)

Once the data source connection has been configured, it's time to configure the SQL query. Select the Preview tab and then click Query Builder button to configure the SQL query:

ZappySys API Driver - Google Ads

Read and write Google Ads data effortlessly. Integrate, manage, and automate campaigns, ad groups, keywords, and performance — almost no coding required.

GoogleAdsDSN
Start by selecting the Table or Endpoint you are interested in and then configure the parameters. This will generate a query that we will use in Power BI to retrieve data from Google Ads. Hit OK button to use this query in the next step.
```
SELECT *
FROM get_campaigns
--OR--
--SELECT * FROM get_resource_data WITH(Resource='Campaign') --slightly faster
```
Some parameters configured in this window will be passed to the Google Ads API, e.g. filtering parameters. It means that filtering will be done on the server side (instead of the client side), enabling you to get only the meaningful data much faster.
Now hit Preview Data button to preview the data using the generated SQL query. If you are satisfied with the result, use this query in Power BI:
ZappySys API Driver - Google Ads

Read and write Google Ads data effortlessly. Integrate, manage, and automate campaigns, ad groups, keywords, and performance — almost no coding required.

GoogleAdsDSN
```
SELECT *
FROM get_campaigns
--OR--
--SELECT * FROM get_resource_data WITH(Resource='Campaign') --slightly faster
```
You can also access data quickly from the tables dropdown by selecting <Select table>.

A WHERE clause, LIMIT keyword will be performed on the client side, meaning that the whole result set will be retrieved from the Google Ads API first, and only then the filtering will be applied to the data. If possible, it is recommended to use parameters in Query Builder to filter the data on the server side (in Google Ads servers).
Click OK to finish creating the data source.

Video Tutorial

Connect to Google Ads data in Power BI

Import data from a table or view

Once you open Power BI Desktop click Get Data to get data from ODBC:
A window opens, and then search for "odbc" to get data from ODBC data source:
Another window opens and asks to select a Data Source we already created. Choose GoogleAdsDSN and continue:

GoogleAdsDSN
Most likely, you will be asked to authenticate to a newly created DSN. Just select Windows authentication option together with Use my current credentials option:

GoogleAdsDSN
Finally, you will be asked to select a table or view to get data from. Select one and load the data!
Finally, finally, read extracted data from Google Ads in a Power BI report:

Import data using a SQL query

If you wish to import Google Ads data from SQL query rather than a table then you can use advanced options during import steps (as below). After selecting DSN you can click on advanced options to see SQL Query editor.

GoogleAdsDSN

SELECT *
FROM get_campaigns
--OR--
--SELECT * FROM get_resource_data WITH(Resource='Campaign') --slightly faster

Get REST API data in Power BI Desktop using SQL query and ODBC

Consider using Custom Objects feature in ODBC data source to encapsulate SQL query in a Virtual Table. This way, you can see a virtual table in Power BI table list where you can import multiple objects using the same connection rather than creating a new connection for each custom SQL query.

Publish Power BI report to Power BI service

Here are the instructions on how to publish a Power BI report to Power BI service from Power BI Desktop application:

First of all, go to Power BI Desktop, open a Power BI report, and click Publish button:
Then select the Workspace you want to publish report to and hit Select button:
Finally, if everything went right, you will see a window indicating success:

What's next? If you need to periodically refresh Power BI semantic model (dataset) to ensure data accuracy and up-to-dateness, you can accomplish that by using Microsoft On-premises data gateway. Proceed to the next section - Refresh the Power BI semantic model via the gateway - and learn how to do that.

Refresh the Power BI semantic model (dataset) via the gateway

Power BI allows you to refresh semantic models (previously known as "datasets") that are based on data sources residing on-premises. This is achieved using the Microsoft On-premises data gateway. It acts as a secure bridge between Power BI cloud services and your local Google Ads ODBC data source:

Power BI and On-premises data gateway diagram

There are two types of On-premises data gateways:

Standard mode

Supports Power BI and other Microsoft Cloud services
Installs as a Windows service
Starts automatically
Supports centralized user access control
Supports the Direct Query feature
Ideal for enterprise solutions

Personal mode

Supports Power BI services only
Cannot run as a Windows service
Stops when you sign out of Windows
Does not support access control
Does not support the Direct Query feature
Best for individual use and POC solutions

You can download the On-premises data gateway directly from the Microsoft Fabric or Power BI portals:

Download Power BI On-premises data gateway

We recommend using Personal mode for quick POCs or personal use, and Standard mode for production scenarios.

Below are instructions on how to refresh the semantic model using both gateway types.

Use the Standard mode gateway (recommended)

Best for enterprise production environments where multiple users need to share the same gateway connection.

Follow these steps to refresh a Power BI semantic model using the On-premises data gateway (Standard mode):

Go to Power BI My workspace, hover your mouse cursor over your semantic model, and click Settings:
If you see this view, it means you must install the On-premises data gateway (Standard mode):
Download On-premises data gateway (standard mode) and run the installer.
Once the configuration window opens, sign in:

Sign in with the same email address you use for Microsoft Fabric.
Select Register a new gateway on this computer (or migrate an existing one):
Name your gateway, enter a Recovery key, and click the Configure button:

Save your Recovery Key in a safe place (like a password manager). If you lose it, you cannot restore or migrate this gateway later.
Once Microsoft gateway is installed, check if it registered correctly:
- Go back to Power BI portal
- Click Gear icon on top-right
- And then hit Manage connections and gateways menu item
Continue by clicking the On-premises data gateway tab and selecting Standard mode gateways from the dropdown menu:
If your gateway is not listed, the registration may have failed. To resolve this:
- Wait a couple of minutes and refresh Power BI portal page
- Restart the machine where On-premises data gateway is installed
- Check firewall settings
Success! The gateway is now Online and ready to handle requests.
Now, return to your semantic model settings in the Power BI portal. Refresh the page, and you should see your newly created gateway. Click the arrow icon to expand the options, and then click the Add to gateway link:

ODBC{"connectionstring":"dsn=GoogleAdsDSN"}
Once you do that, you will create a new gateway connection. Give it a name, set the Authentication method, Privacy level, and click the Create button:

dsn=GoogleAdsDSN

In this example, we use the least restrictive Privacy level.

If your connection uses a full connection string, you may hit a length limitation when entering it into the field. To create the connection, you will need to shorten it manually. Check the section about the limitation of a full connection string on how to accomplish this.

On-premises data gateway (Personal mode) does not have this limitation.
Select the newly created connection to map it to your dataset:

ODBC{"connectionstring":"dsn=GoogleAdsDSN"}
Finally, you can refresh the semantic model:

Use the Personal mode gateway (POC)

Best for single-user scenarios, quick tests (POC), or when you don't have administrative rights to install the Standard gateway.

Follow these steps to refresh a Power BI semantic model using the On-premises data gateway (Personal mode):

Go to Power BI My workspace, hover your mouse cursor over your semantic model, and click Settings:
If you see this view, it means you must install the On-premises data gateway (Personal mode):
Install On-premises data gateway (personal mode) and sign-in:

Use the same email address you use when logging in into your account.
Once Microsoft gateway is installed, check if it registered correctly:
- Go back to Power BI portal
- Click Gear icon on top-right
- And then hit Manage connections and gateways menu item
Continue by clicking On-premises data gateway tab and select Personal mode option from the dropdown:
If your gateway is not listed, the registration may have failed. To resolve this:
- Wait a couple of minutes and refresh Power BI portal page
- Restart the machine where On-premises data gateway is installed
- Check firewall settings
The On-premises data gateway is now Online and ready to receive requests.
Return to your semantic model Settings, expand Data source credentials, click Edit credentials, select the Authentication method and the Privacy level, and then click the Sign in button:

dsn=GoogleAdsDSN
Finally, you are ready to refresh your semantic model:

Advanced topics

Editing query in Power BI

There will be a time you need to change the initial query after importing data into Power BI. Don't worry, just right-click on your table and click Edit query menu item:

Edit query in Power BI to get REST API data

Refer to Power Query M reference for more information on how to use its advanced features in your queries.

Using parameters for dynamic queries

In the real world, many values of your REST / SOAP API call may be coming from parameters. If that's the case for you can try to edit script manually as below. In below example its calling SQL Query with POST method and passing some parameters. Notice below where paraAPIKey is Power BI Parameter (string type). You can use parameters anywhere in your script just like the normal variable.

To use a parameter in Power BI report, follow these simple steps:

Firstly, you need to Edit query of your table (see previous section)

Then just create a new parameter by clicking Manage Parameters dropdown, click New Parameter option, and use it in the query:

                
                            = Odbc.Query("dsn=GoogleAdsDSN",
                                         "SELECT ProductID, ProductName, UnitPrice, UnitsInStock
                                          FROM Products
                                          WHERE UnitPrice > " & Text.From(MyParameter) & "
                                          ORDER BY UnitPrice")

Use parameter in Power BI to get REST API data

Refer to Power Query M reference for more information on how to use its advanced features in your queries.

Using DirectQuery (live connection)

By default, Power BI imports Google Ads data into its internal cache. However, if you require real-time data, you can use the DirectQuery mode.

Since the native Power BI ODBC connector limits you to Import mode, we must bridge the connection via Microsoft SQL Server. To do this, we configure the ZappySys Data Gateway and create a Linked Server pointing to it:

Architecture diagram: Power BI (DirectQuery) connected to SQL Server, bridging to ZappySys Data Gateway via Linked Server, and finally fetching data from Google Ads Service

This method requires an existing Microsoft SQL Server instance to act as the bridge.

Follow these steps to use DirectQuery:

Configure ZappySys Data Gateway and create a Linked Server in SQL Server.
Once the Linked Server is ready, open Power BI Desktop.
Click Get Data and select SQL Server.
Enter your SQL Server instance name and a valid database name (e.g., master).
Under Data Connectivity mode, select DirectQuery.
Expand Advanced options and enter your SQL query using the OPENQUERY syntax below (replace [LINKED_SERVER_NAME] with your actual Linked Server name):

SELECT * FROM OPENQUERY([LS_TO_GOOGLE_ADS_IN_GATEWAY], 'SELECT * FROM get_campaigns --OR-- --SELECT * FROM get_resource_data WITH(Resource=''Campaign'') --slightly faster')
```
SELECT * FROM OPENQUERY([LS_TO_GOOGLE_ADS_IN_GATEWAY], 'SELECT *
FROM get_campaigns
--OR--
--SELECT * FROM get_resource_data WITH(Resource=''Campaign'') --slightly faster')
```
Click OK and load the data. Your Google Ads data is now linked live rather than imported.

Avoid using DirectQuery unless it is required for very large datasets or real-time data needs. Data is fetched on demand, which can impact performance compared to the cached Import mode.

Using full ODBC connection string

In the previous steps we used a very short format of ODBC connection string - a DSN. Yet sometimes you don't want a dependency on an ODBC data source (and an extra step). In those times, you can define a full connection string and skip creating an ODBC data source entirely. Let's see below how to accomplish that in the below steps:

Open ODBC data source configuration and click Copy settings:

ZappySys API Driver - Configuration [Version: 2.0.1.10418]

ZappySys API Driver - Google Ads

Read and write Google Ads data effortlessly. Integrate, manage, and automate campaigns, ad groups, keywords, and performance — almost no coding required.

GoogleAdsDSN
The window opens, telling us the connection string was successfully copied to the clipboard:
Then just paste the connection string into your script:

GoogleAdsDSN

DRIVER={ZappySys API Driver};ServiceUrl=https://googleads.googleapis.com/[$ApiVersion$];Provider=GoogleAdWords;ScopeSeparator={space};RetryMode=[$RetryMode$];RetryStatusCodeList=[$RetryStatusCodeList$]
You are good to go! The script will execute the same way as using a DSN.

The DSN defined in the Data source name (DSN) field will be ignored.

Have in mind that a full connection string has length limitations.

Proceed to the next step to find out the details.

Handling limitations of using a full connection string

Despite using a full ODBC connection string may be very convenient it comes with a limitation: it's length is limited to 1024 symbols (or sometimes more). It usually happens when API provider generates a very long Refresh Token when OAuth is at play. If you are using such a long ODBC connection string, you may get this error:

"Connection string exceeds maximum allowed length of 1024"

But there is a solution to this by storing the full connection string in a file. Follow the steps below to achieve this:

Open your ODBC data source.
Click Copy settings button to copy a full connection string (see the previous section on how to accomplish that).
Then create a new file, let's say, in C:\temp\odbc-connection-string.txt.
Continue by pasting the copied connection string into a newly created file and save it.
Finally, the last step! Just construct a shorter ODBC connection string using this format:
```
DRIVER={ZappySys API Driver};SettingsFile=C:\temp\odbc-connection-string.txt
```
Our troubles are over! Now you should be able to use this connection string in Power BI with no problems.

This feature requires ODBC PowerPack v1.9.0 or later.

Optional: Centralized data access via ZappySys Data Gateway

In some situations, you may need to provide Google Ads data access to multiple users or services. Configuring the data source on a Data Gateway creates a single, centralized connection point for this purpose.

This configuration provides two primary advantages:

Centralized data access
The data source is configured once on the gateway, eliminating the need to set it up individually on each user's machine or application. This significantly simplifies the management process.
Centralized access control
Since all connections route through the gateway, access can be governed or revoked from a single location for all users.

	Data Gateway	Local ODBC data source
Simple configuration
Installation	Single machine	Per machine
Connectivity	Local and remote	Local only
Connections limit	Limited by License	Unlimited
Central data access
Central access control
More flexible cost

To achieve this, you must first create a data source in the Data Gateway (server-side) and then create an ODBC data source in Power BI (client-side) to connect to it.

Let's not wait and get going!

Create Google Ads data source in the gateway

In this section we will create a data source for Google Ads in the Data Gateway. Let's follow these steps to accomplish that:

Search for gateway in the Windows Start Menu and open ZappySys Data Gateway Configuration:
Go to the Users tab and follow these steps to add a Data Gateway user:
- Click the Add button
- In the Login field enter a username, e.g., john
- Then enter a Password
- Check the Is Administrator checkbox
- Click OK to save
Now we are ready to add a data source:
- Click the Add button
- Give the Data source a name (have it handy for later)
- Then select Native - ZappySys API Driver
- Finally, click OK
GoogleAdsDSN

ZappySys API Driver
When the ZappySys API Driver configuration window opens, go back to ODBC Data Source Administrator where you already have the Google Ads ODBC data source created and configured, and follow these steps on how to Import data source configuration into the Gateway:
- Open ODBC data source configuration and click Copy settings:
  
  ZappySys API Driver - Configuration [Version: 2.0.1.10418]
  
  ZappySys API Driver - Google Ads
  
  Read and write Google Ads data effortlessly. Integrate, manage, and automate campaigns, ad groups, keywords, and performance — almost no coding required.
  
  GoogleAdsDSN
- The window opens, telling us the connection string was successfully copied to the clipboard:
- Then go to Data Gateway configuration and in data source configuration window click Load settings:
  
  GoogleAdsDSN
  
  ZappySys API Driver - Configuration [Version: 2.0.1.10418]
  
  ZappySys API Driver - Google Ads
  
  Read and write Google Ads data effortlessly. Integrate, manage, and automate campaigns, ad groups, keywords, and performance — almost no coding required.
  
  GoogleAdsDSN
- Once a window opens, just paste the settings by pressing CTRL+V or by clicking right mouse button and then Paste option.
Once done, go to the Network Settings tab and Add a firewall rule for inbound traffic:
- This will initially allow all inbound traffic.
- Click Edit IP filters to restrict access to specific IP addresses or ranges.
Crucial Step: After creating or modifying the data source, you must:
- Click the Save button to persist your changes.
- Hit Yes when prompted to restart the Data Gateway service.
This ensures all changes are properly applied:

Skipping this step may cause the new settings to fail, preventing you from connecting to the data source.

Create ODBC data source to connect to the gateway

In this part we will create an ODBC data source to connect to the ZappySys Data Gateway from Power BI. To achieve that, let's perform these steps:

Search for odbc and open the ODBC Data Sources (64-bit):
Create a User data source (User DSN) based on the ODBC Driver 17 for SQL Server driver:

ODBC Driver 17 for SQL Server

If you don't see the ODBC Driver 17 for SQL Server driver in the list, choose a similar version.
Then set a Name for the data source (e.g. Gateway) and the address of the Data Gateway:

ZappySysGatewayDSN

localhost,5000

Make sure you separate the hostname and port with a comma, e.g. localhost,5000.
Proceed with the authentication part:
- Select SQL Server authentication
- In the Login ID field enter the user name you created in the Data Gateway, e.g., john
- Set Password to the one you configured in the Data Gateway
Then set the default database property to GoogleAdsDSN (the one we used in the Data Gateway):

GoogleAdsDSN

GoogleAdsDSN

Make sure to type the data source name manually or copy/paste it directly into the field. Using the dropdown might fail because the Trust server certificate option is not enabled yet (next step).
Continue by checking the Trust server certificate option:
Once you do that, test the connection:
If the connection is successful, everything is good:
Done!

We are ready to move to the final step. Let's do it!

Access data in Power BI via the gateway

Finally, we are ready to read data from Google Ads in Power BI via the Data Gateway. Follow these final steps:

Go back to Power BI.
Once you open Power BI Desktop click Get Data to get data from ODBC:
A window opens, and then search for "odbc" to get data from ODBC data source:
Another window opens and asks to select a Data Source we already created. Choose ZappySysGatewayDSN and continue:

ZappySysGatewayDSN
When the ODBC driver authentication window opens, configure the following:
- Enter the User name (e.g., john)
- Enter the Password that you configured in ZappySys Data Gateway
- Hit the Connect button
dsn=ZappySysGatewayDSN

Make sure the Database tab is selected; otherwise, Power BI won't be able to connect to the ZappySys Data Gateway.
Read the data the same way we discussed at the beginning of this article.
That's it!

Now you can connect to Google Ads data in Power BI via the Data Gateway.

Supported Google Ads Connector actions

Got a specific use case in mind? We've mapped out exactly how to perform a variety of essential Google Ads operations directly in Power BI, so you don't have to figure out the setup from scratch. Check out the step-by-step guides below:

Conclusion

In this article we showed you how to connect to Google Ads in Power BI and integrate data without writing complex code — all of this was powered by Google Ads ODBC Driver.

Download ODBC PowerPack now or ping us via chat if you have any questions or are looking for a specific feature (you can also reach out to us by submitting a ticket):

Download Chat