Skip to content

Commit 7c61e07

Browse files
authored
Update sample YAML file to clarify steps for service accounts. (googleads#451)
1 parent 7c763e4 commit 7c61e07

1 file changed

Lines changed: 22 additions & 14 deletions

File tree

google-ads.yaml

Lines changed: 22 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,35 @@
1+
# Developer token
2+
###############################################################################
3+
# A developer token is required when making requests to the Google Ads API #
4+
# regardless of whether you're using the OAuth2 or Service Account #
5+
# configurations. To obtain a developer token see: #
6+
# https://developers.google.com/google-ads/api/docs/first-call/dev-token #
7+
###############################################################################
8+
developer_token: INSERT_DEVELOPER_TOKEN_HERE
9+
110
# OAuth2 configuration
211
###############################################################################
312
# The below configuration parameters are used to authenticate using the #
413
# recommended OAuth2 flow. For more information on authenticating with OAuth2 #
514
# see: https://developers.google.com/google-ads/api/docs/oauth/overview #
615
###############################################################################
7-
developer_token: INSERT_DEVELOPER_TOKEN_HERE
816
client_id: INSERT_OAUTH2_CLIENT_ID_HERE
917
client_secret: INSERT_OAUTH2_CLIENT_SECRET_HERE
1018
refresh_token: INSERT_REFRESH_TOKEN_HERE
1119

20+
# Service Account configuration
21+
###############################################################################
22+
# To authenticate with a service account add the appropriate values to the #
23+
# below configuration parameters and remove the three OAuth2 credentials #
24+
# above. The "json_key_file_path" value should be a path to your local #
25+
# private key json file, and "impersonated_email" should be the email address #
26+
# that is being used to impersonate the credentials making requests. for more #
27+
# information on service accounts, see: #
28+
# https://developers.google.com/google-ads/api/docs/oauth/service-accounts #
29+
###############################################################################
30+
# json_key_file_path: INSERT_PATH_TO_JSON_KEY_FILE_HERE
31+
# impersonated_email: INSERT_DOMAIN_WIDE_DELEGATION_ACCOUNT
32+
1233
# Login customer ID configuration
1334
###############################################################################
1435
# Required for manager accounts only: Specify the login customer ID used to #
@@ -19,19 +40,6 @@ refresh_token: INSERT_REFRESH_TOKEN_HERE
1940
###############################################################################
2041
login_customer_id: INSERT_LOGIN_CUSTOMER_ID_HERE
2142

22-
# Service Account configuration
23-
###############################################################################
24-
# To authenticate with a service account add the appropriate values to the #
25-
# below configuration parameters and remove the four OAuth credentials above. #
26-
# The "json_key_file_path" value should be a path to your local private #
27-
# key json file, and "impersonated_email" should be the email address that is #
28-
# being used to impersonate the credentials making requests. for more #
29-
# information on service accounts, see: #
30-
# https://developers.google.com/google-ads/api/docs/oauth/service-accounts #
31-
###############################################################################
32-
# json_key_file_path: INSERT_PATH_TO_JSON_KEY_FILE_HERE
33-
# impersonated_email: INSERT_DOMAIN_WIDE_DELEGATION_ACCOUNT
34-
3543
# Logging configuration
3644
###############################################################################
3745
# Below you may specify the logging configuration. This will be provided as #

0 commit comments

Comments
 (0)