Stay organized with collections
Save and categorize content based on your preferences.
When working with the Google Ads API, there are multiple places where email addresses
are used for contact and access management, the most important of which are the
following:
Google Ads API contact email: This is the email listed as the contact in the
API Center of the Google Ads UI.
Google Cloud Console account email: This is the email that has
administrator access to the Google Cloud Console account used for your OAuth
2.0 application.
Google Ads manager account email(s): These are the emails that have
administrator permissions on the manager Google Ads account(s) you access
through the Google Ads API. When you generate a refresh token for your application,
you usually authenticate your Google Ads API application with one of these emails.
We strongly recommend using shared team aliases so that you don't lose access to
these accounts when individual team members switch teams or leave the company.
The rest of this guide elaborates on each of the emails listed earlier and how
you can update it to use a shared team alias instead of an individual user's
email address.
Google Ads API contact email
The Google Ads API contact email is an email address you provide when signing up for
the Google Ads API. You should ensure access to this alias and monitor emails sent to
this address regularly. Google uses this email address to contact your team
during API reviews, audit requests, or production emergencies that require
immediate attention. Use a shared team alias as the contact email to ensure that
the whole team receives these notifications.
Follow these steps to update the API contact email:
Under Developer details, note the API contact email. Click the down arrow
and edit the email. Click Save.
Google Cloud Console account
The Google API Console project contains your application's OAuth credentials
and controls access to the Google Ads API. Ensure access to this account by making a
shared alias the account owner.
Follow these steps to update the Google API Console project's owner:
A common method of managing accounts using the Google Ads API is to link all your
accounts under a common manager account, and make API calls to all the accounts
using the top-most manager account's credentials. In this configuration:
The developer issues a refresh token using the credentials of a user who has
access to the Google Ads manager account.
The developer sets the login_customer_id header as the customer
ID of the Google Ads manager account, and the customer_id header as the
customer ID of the account to which API calls are made.
One potential risk of this setup is that if the authorized user loses access to
the Google Ads manager account, the refresh token is no longer valid and all API
calls fail. To avoid this scenario, you can invite a shared email alias to
manage this Google Ads manager account with the appropriate access levels.
Use this shared email alias to issue the refresh token for making API calls.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[[["\u003cp\u003eWhen working with the Google Ads API, ensure continuous access by using shared team aliases for contact, access management, and authentication purposes instead of individual user emails.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Ads API contact email is used for crucial communications, update it to a shared alias to keep your team informed about API reviews, audit requests, and production emergencies.\u003c/p\u003e\n"],["\u003cp\u003eSafeguard your Google Cloud Console account by granting ownership to a shared team alias, ensuring access to your application's OAuth credentials and control over API access.\u003c/p\u003e\n"],["\u003cp\u003eFor managing multiple Google Ads accounts, link them under a manager account and grant access to a shared alias for refresh token generation and uninterrupted API functionality.\u003c/p\u003e\n"],["\u003cp\u003eRegularly monitor and update these email addresses and access levels to maintain seamless API operations and avoid disruptions caused by personnel changes.\u003c/p\u003e\n"]]],[],null,["# Shared aliases\n\nWhen working with the Google Ads API, there are multiple places where email addresses\nare used for contact and access management, the most important of which are the\nfollowing:\n\n- **Google Ads API contact email**: This is the email listed as the contact in the API Center of the Google Ads UI.\n- **Google Cloud Console account email**: This is the email that has administrator access to the Google Cloud Console account used for your OAuth 2.0 application.\n- **Google Ads manager account email(s)**: These are the emails that have administrator permissions on the manager Google Ads account(s) you access through the Google Ads API. When you generate a refresh token for your application, you usually authenticate your Google Ads API application with one of these emails.\n\nWe strongly recommend using shared team aliases so that you don't lose access to\nthese accounts when individual team members switch teams or leave the company.\nThe rest of this guide elaborates on each of the emails listed earlier and how\nyou can update it to use a shared team alias instead of an individual user's\nemail address.\n\nGoogle Ads API contact email\n----------------------------\n\nThe Google Ads API contact email is an email address you provide when signing up for\nthe Google Ads API. You should ensure access to this alias and monitor emails sent to\nthis address regularly. Google uses this email address to contact your team\nduring API reviews, audit requests, or production emergencies that require\nimmediate attention. Use a shared team alias as the contact email to ensure that\nthe whole team receives these notifications.\n\nFollow these steps to update the API contact email:\n\n1. Sign in to your Google Ads [Manager\n Account](//ads.google.com/home/tools/manager-accounts/).\n\n2. Click **Admin** at the bottom left of the screen.\n\n3. Under **Manager account settings** , click **API center**.\n\n4. Under **Developer details** , note the API contact email. Click the down arrow\n and edit the email. Click **Save**.\n\nGoogle Cloud Console account\n----------------------------\n\nThe **Google API Console** project contains your application's OAuth credentials\nand controls access to the Google Ads API. Ensure access to this account by making a\nshared alias the account owner.\n\nFollow these steps to update the Google API Console project's owner:\n\n- Sign in to [**Google API Console**](//console.developers.google.com).\n- Select your project from the drop-down menu on the top-left corner of the page.\n- Navigate to **IAM and admin \\\u003e IAM** from the left menu.\n- Click the **Grant Access** button.\n- Enter the shared email address under the **Add principals** section.\n- Assign the **Owner** role.\n- Click the **Save** button. Refer to the Cloud documentation to learn more about [granting and revoking access](//cloud.google.com/iam/docs/granting-changing-revoking-access#single-role).\n\nGoogle Ads manager account\n--------------------------\n\nA common method of managing accounts using the Google Ads API is to link all your\naccounts under a common manager account, and make API calls to all the accounts\nusing the top-most manager account's credentials. In this configuration:\n\n- The developer issues a refresh token using the credentials of a user who has access to the Google Ads manager account.\n- The developer sets the [`login_customer_id`](/google-ads/api/docs/get-started/select-account#user_access_login_customer_id_and_customer_id) header as the customer ID of the Google Ads manager account, and the `customer_id` header as the customer ID of the account to which API calls are made.\n\nOne potential risk of this setup is that if the authorized user loses access to\nthe Google Ads manager account, the refresh token is no longer valid and all API\ncalls fail. To avoid this scenario, you can invite a shared email alias to\nmanage this Google Ads manager account with the [appropriate access levels](//support.google.com/google-ads/answer/9978556).\nUse this shared email alias to issue the refresh token for making API calls."]]