TDV Adapter for Google Ads

Build 24.0.9060

OAuth Scopes and Endpoints

Required Scopes and Endpoint Domains for Google Ads

When integrating with Google Ads, your application needs specific permissions to interact with the API.

These permissions are defined by access scopes, which determine what data your application can access and what actions it can perform.

This topic provides information about the required access scopes and endpoint domains for the Google Ads adapter.

Understanding Scopes

Scopes are a way to limit an application's access to a user's data. They define the specific actions that an application can perform on behalf of the user.

For example, a read-only scope might allow an application to view data, while a full access scope might allow it to modify data.

Required Scopes for Google Ads

Scope Description
googleapis.com/auth/adwords This driver is read-only, however a read-only scope is not provided by Google Ads. This is the default scope and the only scope available.

Understanding Endpoint Domains

Endpoint domains are the specific URLs that the application needs to communicate with in order to authenticate, retrieve records, and perform other essential operations.

Allowlisting these domains ensures that the network traffic between your application and the API is not blocked by firewalls or security settings.

Note: Most users do not need to make any special configurations. Allowlisting is typically only necessary for environments with strict security measures, such as restricted outbound network traffic.

Required Endpoint Domains for Google Ads

Domain Always Required Description
googleads.googleapis.com TRUE The endpoint used to make API calls and retrieve data. For example, https://googleads.googleapis.com/v17/customers/1234567890/adGroups.
accounts.google.com TRUE The domain used for OAuth.

Copyright (c) 2024 CData Software, Inc. - All rights reserved.
Build 24.0.9060