[ Marketing ]
Google Ads integration for your workflows.
Connect Google Ads to Collabase once and use 8 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.
Google Ads in Collabase
Connect Google Ads to Collabase once and use 8 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Manage campaigns, ad groups, ads, keywords, audiences and performance reports in Google Ads.
How to connect it
- Open the integrations in the workspace settings.
- Choose Google Ads and connect your account.
- Add a trigger or an action to the workflow.
- In Google Cloud Console, select or create a project. APIs & Services → Library: enable Google Ads API and Data Manager API (the latter only for Customer Match uploads).
- Open the Google Ads API page in the console and check the project's access level. New projects get Test access (test accounts only). To operate real accounts, apply for Explorer or Basic access there (Google reviews it, typically within 10 business days).
- APIs & Services → OAuth consent screen: add the scopes https://www.googleapis.com/auth/adwords and https://www.googleapis.com/auth/datamanager. While the app is in Testing, add the Google accounts that will connect as test users.
- APIs & Services → Credentials → Create credentials → OAuth client ID, type Web application. Add the Redirect URL shown below to Authorized redirect URIs.
- Paste the Client ID and Client Secret here and sign in with a Google account that can access the Google Ads accounts you want to automate.
Google Ads triggers
| Name | Description | Fields |
|---|---|---|
| New RecordChecks at intervals | Fires when a campaign, ad group, ad, keyword or audience list is created in the selected account (removed records are ignored) |
|
Google Ads actions
| Name | Description | Fields |
|---|---|---|
| Create Record | Create a campaign, ad group, ad, keyword or audience list |
|
| Update Record | Change fields of an existing campaign, ad group, ad, keyword or audience list |
|
| Delete Record | Remove a campaign, ad group, ad, keyword or audience list (Google marks it REMOVED; it cannot be restored) |
|
| Search Records | Run a GAQL query (campaigns, ad groups, ads, keywords, audiences, reports) with pagination |
|
| Retrieve Advertising Report | Performance metrics per campaign, ad group, ad, keyword, search term or account, over a date range |
+ 6
|
| Add Customer Match Data | Upload e-mails, phones or addresses to a Customer Match audience list (Data Manager API) |
+ 1
|
| Remove Customer Match Data | Remove members (by e-mail, phone or address) from a Customer Match audience list (Data Manager API) |
|
| Custom API Call | Call any Google Ads API endpoint. The path must start with the API version: /v25/customers/{customerId}/... (e.g. /v25/customers/1234567890/campaignBudgets:mutate). Data Manager API endpoints take a full URL on https://datamanager.googleapis.com (e.g. GET https://datamanager.googleapis.com/v1/requestStatus:retrieve?requestId=... to check a Customer Match upload). |
+ 3
|
[ Marketing ]
Related integrations
Tools that often share a workflow.
Questions about Google Ads
What can I automate with Google Ads in Collabase?
Google Ads brings 8 actions and 1 trigger, for example Create Record, Update Record, Delete Record, Search Records and 4 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect Google Ads to Collabase?
You open the integrations in the workspace settings, choose Google Ads and connect your account once, using OAuth 2.0. After that all triggers and actions are available in the workflow.
Can Google Ads start a workflow?
Yes. Google Ads provides 1 trigger, for example New Record. The workflow runs as soon as the event happens.
Does the Google Ads integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.