Google Ads Connector

Google Ads is an online advertising platform that allows businesses to create and manage ad campaigns across Google Search, YouTube, and partner websites. This component allows managing campaigns, uploading conversions, handling customer accounts, and working with Local Services ads in Google Ads.

API Documentation

This component was built using the Google Ads API, currently utilizing v23 by default. Older versions (v21, v22) are supported by specifying the API Version in the connection.

EU Political Advertising Self-Declaration (v22+)

When using API v22 or later, the containsEuPoliticalAdvertising field must be set when:

• Creating new campaigns
• Modifying location or proximity targeting on existing campaigns

This field is required and accepts one of the following values:

• CONTAINS_EU_POLITICAL_ADVERTISING: Campaign contains EU political advertising.
• DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING: Campaign does not contain EU political advertising.
• UNSPECIFIED or UNKNOWN: Use when the value is unknown or indeterminate.

Failure to set this field will result in a FieldError.REQUIRED error from the API.

Connections

Data Manager OAuth 2.0

Authenticate to the Google Data Manager API using OAuth 2.0. Use this connection for the Ingest Offline Conversions action. A Developer Token is not required for this API.

This connection uses OAuth 2.0 to connect to the Google Data Manager API. Use this connection for the Ingest Offline Conversions action. A Developer Token is not required for the Data Manager API.

Prerequisites

• A Google Developer account with permission to manage APIs and OAuth credentials
• A Google Ads account that owns the conversion actions to ingest into
• The numeric Customer ID of the Google Ads account that will receive the offline conversions (configured per-action, not on the connection)

Configure Google Cloud Project

1. Sign in to the Google Cloud Console and select or create a project.
2. Select APIs & Services -> Enabled APIs & services from the left hand menu.
3. Click Enable APIs and Services at the top of the screen.
4. Search for "data manager api" and select Data Manager API in the results.
5. Click the Enable button to add the API to the project.
6. From the sidebar, select Credentials.
7. An OAuth 2.0 app requires a "Consent Screen". Click CONFIGURE CONSENT SCREEN.
   1. The app will be externally available to customers, so choose a User Type of External.
   2. Fill out the OAuth consent screen with an app name, support email, app logo, and authorized domain.
   3. On the next page, add the https://www.googleapis.com/auth/datamanager scope to the app.
   4. Enter test users for testing purposes. The app will only work for those testing users until it is "verified" by Google. When ready for verification, click PUBLISH APP on the OAuth consent screen.
8. Once the "Consent Screen" is configured, open the Credentials page from the sidebar again.
9. Click +CREATE CREDENTIALS and select OAuth client ID.
   1. Under Application type select Web application.
   2. Under Authorized redirect URIs enter the OAuth 2.0 callback URL: https://oauth2.flowbuilder.eu.lansweeper.com/callback for EU sites or https://oauth2.flowbuilder.us.lansweeper.com/callback for US sites
   3. Click CREATE.
10. Take note of the Client ID and Client Secret that are generated.

Configure the Connection

• Client ID: From the Google Cloud Console OAuth client credentials
• Client Secret: From the Google Cloud Console OAuth client credentials
• API Version: The Google Data Manager API version to use. Defaults to v1. Refer to the Data Manager API reference for the latest version.

After entering the credentials, authorize the connection by signing in with the Google account that has access to the target Google Ads account.

Supported API Versions

The component supports the following Google Data Manager API versions through the API Version connection field:

Refer to the official Data Manager API release notes for the latest version information.

App Verification

Google requires OAuth apps that request access to user data to pass a verification review before being deployed at scale. This process ensures the app complies with Google's API Services User Data Policy, accurately represents its functionality, and handles user data responsibly.

Google OAuth apps pass through three stages before they are ready for production use.

Testing (unpublished): The app is only accessible to users manually added as test users in the OAuth consent screen. Up to 100 test users are allowed. All other users receive an error. This is the expected state during initial development.

Published, unverified: After publishing the app, all Google users can authenticate. However, for sensitive scopes, users see a "This app isn't verified" warning. Users can proceed by clicking Advanced -> Go to [app name] (unsafe), but this warning reduces trust and may be blocked by organizations with strict Google Workspace policies.

Verified: Google has reviewed and approved the app. No warning is shown. Verification is required before deploying to production users.

Publishing the App

Publishing is required before any users outside the test list can authenticate:

1. In the Google Cloud Console, navigate to APIs & Services -> OAuth consent screen
2. Click PUBLISH APP and confirm

Requesting Verification

The datamanager scope used by this connection is classified as sensitive by Google. Submitting for verification removes the "This app isn't verified" warning:

1. On the OAuth consent screen, click Prepare for verification
2. Provide a privacy policy URL, authorized domain, and app logo
3. Submit for review. Google typically responds within several weeks.

Refer to Google's OAuth consent screen documentation for the full verification requirements.

Verify Connection

Save the integration to authenticate. After authorizing, run the Ingest Offline Conversions action with Validate Only enabled to confirm the connection and payload are valid without ingesting live data.

This connection uses OAuth 2.0, a common authentication mechanism for integrations.
Read about how OAuth 2.0 works here.

OAuth 2.0

Authenticate using OAuth 2.0.

This component uses OAuth 2.0 to connect to the Google Ads API.

Prerequisites

• A Developer Token is required to work with Google Ads
• The Customer ID of the Ads Manager account (the hyphenated number in the top-left corner of the Ads app) must be noted
• A Google Developer account is required

Developer Token

The Developer Token is obtained from a Google Ads Manager account:

1. Sign in to Google Ads with the Google account that will be used for the integration
2. Click Tools & Settings in the top right corner
3. Under Setup, click API Center
4. In the Developer token section, click Create token or view the existing token
5. Copy and save the Developer Token value securely
6. Take note of the Customer ID displayed in the top-right corner of Google Ads (XXX-XXX-XXXX). This will be needed when configuring the connection.

Configure Google Cloud Project

1. Access the project selector in the top-left and select an existing project or create a new one.
2. Select APIs & Services -> Enabled APIs & services from the left hand menu
3. Click Enable APIs and Services towards the top of the screen
4. Search for "google ads api" and select Google Ads API in the results (avoid selecting AdWords as that is deprecated)
5. Click the Enable button to add the API to the project
6. On the sidebar, select Credentials.
7. An OAuth 2.0 app includes a "Consent Screen". Click CONFIGURE CONSENT SCREEN.
   1. The app will be externally available to customers, so choose a User Type of External.
   2. Fill out the OAuth consent screen with an app name, support email, app logo, domain, etc.
   3. On the next page, add the https://www.googleapis.com/auth/adwords scope to the app.
   4. Enter some test users for testing purposes.
      The app will only work for those testing users until it is "verified" by Google.
      When ready for verification, click PUBLISH APP on the OAuth consent screen.
      That will allow customers to authorize the integration to access their Google Ads.
8. Once the "Consent Screen" is configured, open the Credentials page from the sidebar again.
9. Click +CREATE CREDENTIALS and select OAuth client ID.
   1. Under Application type select Web application.
   2. Under Authorized redirect URIs enter the OAuth 2.0 callback URL: https://oauth2.flowbuilder.eu.lansweeper.com/callback for EU sites or https://oauth2.flowbuilder.us.lansweeper.com/callback for US sites
   3. Click CREATE.
10. Take note of the Client ID and Client Secret that are generated.

Configure the Connection

• Client ID: From the Google Cloud Console OAuth client credentials
• Client Secret: From the Google Cloud Console OAuth client credentials
• Developer Token: From the Google Ads API Center
• API Version: The Google Ads API version to use. Refer to the Google Ads API release notes for the latest version.

Supported API Versions

The component supports multiple API versions through the API Version connection field:

Sunset dates are tentative and subject to change. See the official deprecation and sunset schedule for the latest information.

After entering the credentials, authorize the connection by signing in with the Google account used to create the Developer Token and OAuth credentials.

App Verification

Google requires OAuth apps that request access to user data to pass a verification review before being deployed at scale. This process ensures the app complies with Google's API Services User Data Policy, accurately represents its functionality, and handles user data responsibly.

Google OAuth apps pass through three stages before they are ready for production use.

Testing (unpublished): The app is only accessible to users manually added as test users in the OAuth consent screen. Up to 100 test users are allowed. All other users receive an error. This is the expected state during initial development.

Published, unverified: After publishing the app, all Google users can authenticate. However, for sensitive scopes, users see a "This app isn't verified" warning. Users can proceed by clicking Advanced → Go to [app name] (unsafe), but this warning reduces trust and may be blocked by organizations with strict Google Workspace policies.

Verified: Google has reviewed and approved the app. No warning is shown. Verification is required before deploying to production users.

Publishing the App

Publishing is required before any users outside the test list can authenticate:

1. In the Google Cloud Console, navigate to APIs & Services → OAuth consent screen
2. Click PUBLISH APP and confirm

Requesting Verification

The scopes used by this component are classified as sensitive by Google. Submitting for verification removes the "This app isn't verified" warning:

1. On the OAuth consent screen, click Prepare for verification
2. Provide a privacy policy URL, authorized domain, and app logo
3. Submit for review. Google typically responds within several weeks

Refer to Google's OAuth consent screen documentation for the full verification requirements.

This connection uses OAuth 2.0, a common authentication mechanism for integrations.
Read about how OAuth 2.0 works here.

Triggers

Account Change History

Checks for Google Ads account modifications with user attribution on a configured schedule.

Campaign Budget Alerts

Checks for campaigns approaching or exceeding budget thresholds on a configured schedule.

New and Updated Campaigns

Checks for new and updated campaigns in a Google Ads account on a configured schedule.

Actions

Confirm Client Link

Confirms a pending customer client link.

Create Client Link

Create an invitation to link a client account to a manager account.

Get Account Reports

Retrieve account reports showing performance and metrics for Local Services accounts linked to a Manager account.

Get Conversion Action

Retrieve Conversion Action data for a customer account.

Get Customer

Retrieve Customer data for a customer account.

Get Detailed Lead Reports

Retrieve detailed lead reports providing an in-depth view of leads for Local Services accounts linked to a Manager account.

Ingest Offline Conversions

Import offline conversion events into Google Ads using the Data Manager API.

Invite User

Invite a user by email to a customer.

List Accessible Customers

Get a list of customers accessible to the logged in user.

List Customers by Manager

List all customers under a manager account.

Mutate Campaign

Creates, updates, or removes campaigns as well as local services campaigns. Operation statuses are returned. When using API v22+, the containsEuPoliticalAdvertising field is required for campaign creation and location targeting changes.

Mutate Campaign Criteria

Creates, updates, or removes campaign criteria as well as local services campaign criterion. Operation statuses are returned. When using API v22+, the containsEuPoliticalAdvertising field must be set on the parent campaign before modifying location or proximity targeting criteria.

Raw Request

Send raw HTTP request to Google Ads.

Search Ads

Returns rows matching a GAQL query against Local Services resources.

Upload Call Conversions

Upload offline call conversions into Google Ads in order to track ads that led to sales.

Upload Click Conversions

Upload offline click conversions into Google Ads in order to track ads that led to sales. This action will stop working after June 15, 2026. Use Ingest Offline Conversions instead.