Connectors / Service / Google Ads

Google Ads

Google Ads

Google Ads is Google's advertising system in which advertisers bid on certain keywords in order for their clickable ads to appear in Google's search results.


Google Ads is an online advertising platform developed by Google, where advertisers pay to display brief advertisements, service offerings, product listings, video content, and generate mobile application installs within the Google Ads network to web users.

API INFO: The Base URL used for the google-ads connector is More information can be found on their main API documentation (v6) site.
IMPORTANT!: Please note that there is a good reason why there are 2 versions of this connector available. The original Google Adwords is based off an entirely different backend (SOAP API).

The new REST API is so different from the original, that it is enough to merit Google re-branding their own product.

It is for these reasons that separates these "two connectors", despite the fact that they are in fact representations of the same product.

Please bare the above in mind when choosing between the two.


Within the workflow builder, highlight the Google Ads connector.

In the Google Ads connector properties panel to the right of the builder, click on the Authenticate tab and the 'Add new authentication' button.

This will result in a authentication pop-up modal. The first page will ask you to name your authentication and select the type of authentication you wish to create ('Personal' or 'Organisational').

The next page asks you for your 'Developer Token' credentials. The 'Manage Google Ads' box is automatically checked for you. You may also wish to add extra scopes should you choose to but these are not mandatory.

In order to get this field, head to the Google Ads dashboard. Navigate to the 'Tools & Settings' icon in the top right hand corner. Select 'Setup' followed by 'API Center' from the dropdown options presented.

Once you have added these fields to your authentication popup window, click the 'Create authentication' button.

Go back to your settings authentication field (within the workflow builder properties panel), and select the recently added authentication from the dropdown options now available.

Your connector authentication setup should now be complete.

Available Operations

The examples below show one or two of the available connector operations in use.

Please see the Full Operations Reference at the end of this page for details on all available operations for this connector.

Using the Raw HTTP Request ('Universal Operation')

As of version 1.0, you can effectively create your own operations.

This is a very powerful feature which you can put to use when there is an endpoint in Google Ads which is not used by any of our operations.

To use this you will first of all need to research the endpoint in the Google Ads API documentation v6, to find the exact format that Google Ads will be expecting the endpoint to be passed in.

Note that you will only need to add the suffix to the endpoint, as the base URL will be automatically set (the base URL is picked up from the value you entered when you created your authentication).

The base URL for Google Ads is:

For example, say that the 'Custom query' operation did not exist in our Google Ads connector, and you wanted to use this endpoint. You would use the Google Ads API docs to find the relevant endpoint - which in this case is a POST request called: /customers/{customer_id}/googleAds:search.

More details about this endpoint can be found here.

So if you know what your method, endpoint and details of your parameters are, you can get the customer client information with the following settings:

Method: POST

Endpoint: /customers/9304000742/googleAds:search

Body Type : Raw :

"query": "SELECT, customer_client.hidden, customer_client.manager FROM customer_client",
"page_size": 1

Final outcome being:

Example Usage

TRAY POTENTIAL: is extremely flexible. By design there is no fixed way of working with it - you can pull whatever data you need from other services and work with it using our core and helper connectors. This demo which follows shows only one possible way of working with and the google-ads connector. Once you've finished working through this example please see our Introduction to working with data and jsonpaths page and Data Guide for more details.

Below is an example of a way in which you could potentially use the Google Ads connector, to retrieve the details of a custom audience.

The steps will be as follows:

  1. Setup using a manual trigger and list all the custom audiences.
  2. Loop through the received list of custom audiences.
  3. Retrieve the details of each custom audience.

Your completed workflow should look similar to this:

1 - Setup Trigger & List custom audiences

Select the manual trigger from the trigger options available. From the connectors panel on the left, add a Google Ads connector to your workflow. Set the operation to 'List resources'.

Feel free to re-name your steps as you go along to make things clearer for yourself and other users. The operation names themselves often suffice.

Upon completion, you will have set up the manual trigger and fetched a list of all the custom audiences.

2 - Loop collection

Next, search for the Loop collection connector within your connector panel, and drag it into your workflow as your next step. Set your operations to 'Loop list'.

The Loop Collection connector allows you to iterate through a list of results. In this example, we will use it to iterate through the data found within the previous Google Ads connector step.

In order to specify the list you want to loop through, start by using the list mapping icon (found next to the list input field, within the properties panel) to generate the connector-snake.

While hovering over the 'List Custom Audiences' step (with the tail end of the connector-snake), select results from the list of output properties displayed. This will auto-populate a jsonpath within your list input field, and update the type selector to jsonpath.

For more clarification on the pathways you have available, open the Debug panel to view your step's Input and Output.

JSONPATHS: For more information on what jsonpaths are and how to use jsonpaths with, please see our Intro page and Data Guide for more details.
CONNECTOR-SNAKE: The simplest and easiest way to generate your jsonpaths is to use our feature called the Connector-snake. Please see the main page for more details.

Now, you will be able to loop through the list of the custom audience you have fetched in the first step.

3 - Get custom audience details

The last step is to drag a Google Ads connector inside of the Loop Collection step itself. Set the operation to 'Get resource'. As you can see, the 'Resource name' field is required.

Use the connector snake and hover over the 'Loop Collection' step (with the tail end of the connector-snake) and select the jsonpath for the specified identifier from the list of output properties displayed.

INTERPOLATION: When you wish to include JSON generated data within another input/ output/ result, use our Interpolation method as described here.

You can always inspect the logs of your workflow by using the ‘Debug’ tab available on the top of the Tray builder.

If you go through each execution of the 'Get Custom Audience' step, you will see the results of each loop.

BEST PRACTICES: Whenever you do decide to create your own workflow, please make sure you take a look at our Managing data best practices guide.

All Operations

Latest version: