Google Ads Developer Blog: oath2

Upcoming changes to CustomerService in Google Ads API

Thursday, February 27, 2025

CustomerService.CreateCustomerClientGoogle Ads APIMarch 17, 2025New error codes for policy enforcement

Google Ads manager accounts that do not have a certain threshold of spending or a certain number of active child accounts without policy issues (for example, not suspended or closed for policy violations) will be ineligible to create child accounts under them. Developers will receive a CustomerError.CREATION_DENIED_INELIGIBLE_MCC error code in the upcoming version v19 of the Google Ads API. To fix the issue, link a Google Ads account that is compliant with the Google policies and meets the threshold spending levels under your manager account.

Google Ads manager accounts that have been flagged for policy violations related to account creation will no longer be able to create child accounts under them. Developers will receive a CustomerError.CREATION_DENIED_FOR_POLICY_VIOLATION error code in the upcoming version v19 of the Google Ads API.

ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXTQuota limits for account creationQuotaError.RESOURCE_EXHAUSTEDretry_delayquota_error_detailsWhat do I need to do?support pageGoogle Ads product support team

- Anash P. Oommen, Google Ads API Team

Consent unbundling in Ads APIs

Thursday, February 20, 2025

What’s changing?May 1 2025BackgroundFigure 1Figure 2Who is affected by this change?

Your API application uses a Google Cloud Console project that was created before 2019.

Your application implements the OAuth 2.0 user consent flow – an authentication workflow where the user logs in with their Google account and grants one or more permissions that your application is requesting.

Your application uses more than one Google API, and one of the APIs is an Ads-related API listed below.

Who isn’t affected by this change?

Existing refresh tokens: This change doesn’t affect user authentications that you already have in place. Your existing refresh tokens will continue to work without any changes or re-authentication.

Single scope applications: If your application uses only one Google API scope, your application isn’t affected by this change, since there aren’t multiple OAuth scope to unbundle.

Single user applications / Manually authenticated applications: Your application doesn’t have an explicit OAuth user authentication flow implemented. Instead, you use a manual authentication script such as GenerateUserCredentials, gcloud CLI or OAuth Playground to authenticate the user, and then use those credentials for a long period of time. Since you select all the scopes that your application requires while authenticating, your application isn’t affected by this change.

Service accounts: If your application uses a service account to authenticate your API calls, you won’t be affected by this change

What do I need to do?

Request the list of OAuth scopes that the user consented to by including the include_granted_scopes parameter in your OAuth flow.

Examine the actual list of OAuth scopes that the user consented in the OAuth response.

Implement incremental authorization in your application.

granular consent guideHow do I test this feature?

Create a new Google Cloud project: New Google Cloud projects have enabled OAuth consent unbundling. So you can create a new Google Cloud project, and use it for testing your application.

Enable consent unbundling in your existing project: You can set the enable_granular_consent parameter to true in your OAuth authorization request.