How to integrate Google Ads using Microsoft Fabric

Name: ODBC PowerPack
Rating: 4.9 (8 reviews)
Author: ZappySys

Integrate Microsoft Fabric and Google Ads

Learn how to quickly and efficiently connect Google Ads with Microsoft Fabric 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 (powered by Google Ads Connector for ZappySys API Driver). 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

Low-code / No-code
High performance
Bidirectional
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

Create data source using Google Ads ODBC Driver

Video instructions

Watch this quick walkthrough to see how to configure your Google Ads ODBC data source, or scroll down for the step-by-step written guide.

While this video uses the OData Connector as an example, the core concepts and setup process are exactly the same for the Google Ads Connector.

Watch this video on YouTube

Step-by-step instructions

To get data from Google Ads using Microsoft Fabric, we first need to create an ODBC data source. We will later read this data in Microsoft Fabric. 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 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

Select your authentication scenario below to expand connection configuration steps to:

Configure the authentication in Google Ads.
Enter those details into the ZappySys API Driver data source configuration.

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)

Find full details in the Google Ads Connector authentication reference.

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)

Find full details in the Google Ads Connector authentication reference.

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 Microsoft Fabric 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 Microsoft Fabric:
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.

Install Microsoft On-premises data gateway (Standard mode)

To access and read Google Ads data in Microsoft Fabric, you must download and install the Microsoft On-premises data gateway (Standard mode). It acts as a secure bridge between Microsoft Fabric cloud services and your local Google Ads ODBC data source:

On-premises data gateway securely bridging ODBC data source and Microsoft Fabric

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

You must use the Standard mode of the gateway. Personal mode is not supported by Microsoft Fabric.

Link ODBC data source via the gateway

Follow these steps to download, install, and configure the gateway in 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 Microsoft Fabric 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 Microsoft Fabric 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.
Done!

Make sure to download and install Standard mode. The Personal mode gateway is not supported by Microsoft Fabric cloud services and will not work.

You are now ready to load data into Microsoft Fabric.

Load Google Ads data into Microsoft Fabric

Now that we have configured the ODBC data source and installed the On-premises data gateway, we can proceed with loading data. You can accomplish this in two ways:

Copy job
Best for simple, high-speed data copying without modification.
Dataflow Gen2
Best if you need to transform, clean, or reshape data before loading.

Let's dive into the steps for both methods.

Use Copy job for high-speed loading

Go to the Microsoft Fabric Portal.
Select an existing Workspace or create a new one by clicking New workspace (ensure you are in the Home section):
Inside your workspace, click the New item button in the toolbar to start creating your data pipeline:
In the item selection window, choose Copy job to open the data ingestion wizard:
In the Choose data source screen, search for odbc and select the Odbc source:
Then enter your ODBC connection string (DSN=GoogleAdsDSN) and select MyGateway from the Data gateway dropdown we configured in the previous step:

DSN=GoogleAdsDSN

DSN=GoogleAdsDSN
Select the table(s) and preview the data you wish to copy from Google Ads. Once done, click Next:

DSN=GoogleAdsDSN
Choose your Data Destination. You can create a New Fabric item (like a Lakehouse or Warehouse) or select an existing one:

In this example, we will use a Lakehouse as the destination.
Choose Full copy to load all data, or Incremental copy to load only changed data in subsequent runs:
Review the Column and Table mappings section:
On the summary screen, review your settings. You can optionally enable Run on schedule. Click Save + Run to execute the job:

DSN=GoogleAdsDSN

DSN=GoogleAdsDSN
The job will enter the queue. Monitor the Status column to see the progress:

DSN=GoogleAdsDSN
Wait for the status to change to Succeeded. Your Google Ads data is now successfully integrated into Microsoft Fabric!
Let's go to our Lakehouse (MyLakehouse) and verify the data:
Success! The data has been loaded.

Use Dataflow for advanced transformation

Another way to load data is by creating a Dataflow Gen2. This approach allows you to perform complex data transformations (ETL) before loading the data into its destination.

Configure Dataflow activity

Go to the Microsoft Fabric Portal.
Inside your workspace, click New item and select Dataflow Gen2:
In the Power Query editor, click Get data from another source:
Search for ODBC in the search bar and select the ODBC connector:
Then in the next step follow these instructions:
- Enter your ODBC connection string (e.g., DSN=GoogleAdsDSN)
- Expand Advanced options
- Enter your SQL statement
- Select your On-premises data gateway
- Finally, click Next:
DSN=GoogleAdsDSN

DSN=GoogleAdsDSN

SELECT * FROM get_campaigns --OR-- --SELECT * FROM get_resource_data WITH(Resource='Campaign') --slightly faster
You will see a preview of your Google Ads data. You can now transform the data if needed (filter rows, rename columns, change types, etc.):

Odbc.Query("DSN=GoogleAdsDSN", "SELECT * #(lf)FROM get_campaigns #(lf)--OR-- #(lf)--SELECT * FROM get_resource_data WITH(Resource='Campaign') --slightly faster")
Now, let's send this data to the Lakehouse. Click the + button (Add data destination) at the bottom right and select Lakehouse:

Odbc.Query("DSN=GoogleAdsDSN", "SELECT * #(lf)FROM get_campaigns #(lf)--OR-- #(lf)--SELECT * FROM get_resource_data WITH(Resource='Campaign') --slightly faster")
Configure the destination connection settings and click Next:
Select your specific Lakehouse, enter the Table name you want to create, and click Next:
Uncheck Use automatic settings to set data update or schema options manually. Map the columns with proper data types and click Save settings when done:
The destination is now set. Click the Publish button to save the Dataflow:

Odbc.Query("DSN=GoogleAdsDSN", "SELECT * #(lf)FROM get_campaigns #(lf)--OR-- #(lf)--SELECT * FROM get_resource_data WITH(Resource='Campaign') --slightly faster")
Done! You can now start building reports using your new semantic model.

Configure and run Pipeline

Once you have created and published your Dataflow, you can use a Pipeline to orchestrate and run it.

Go to the Microsoft Fabric Portal.
Inside your workspace, click New item and select Data Pipeline to create a new pipeline.
In the pipeline editor, select the Dataflow activity from the toolbar to add it to your canvas:
Select the Dataflow activity on the canvas and click the Settings tab. Choose your Workspace and the Dataflow you created in the previous steps:
You are now ready to link the Dataflow with other Pipeline activities.
Once the Pipeline flow is configured, click the Run button at the top, then click Save and run to execute the pipeline:
Monitor the Output tab below. The Pipeline status will initially show as In progress:
Wait for the process to complete. The status will update to Succeeded, indicating your data has been successfully loaded via the Dataflow:
Done! You can now start building reports on your new semantic model.

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 Microsoft Fabric (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 Microsoft Fabric. 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 Microsoft Fabric via the gateway

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

Go back to Microsoft Fabric.
Then, go to your Copy job or Dataflow and start configuring your ODBC data source (like you did in the previous step).
In the ODBC configuration window, configure these fields:
- Enter your ODBC connection string (DSN format), for example: DSN=ZappySysGatewayDSN
- Expand Advanced options and set the SQL statement
- Select MyGateway from the Data gateway dropdown that you configured in the previous step
- Select Basic from the Authentication kind dropdown
- Enter the Username (e.g., john) and Password that you configured in ZappySys Data Gateway
DSN=ZappySysGatewayDSN
```
SELECT *
FROM get_campaigns
--OR--
--SELECT * FROM get_resource_data WITH(Resource='Campaign') --slightly faster
```
DSN=ZappySysGatewayDSN
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 Microsoft Fabric 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 Microsoft Fabric, 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 Microsoft Fabric 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