Your access token passed with the HTTP header was not correct. OAuth access token in the header is not valid. You can also invite the Google account to access an existing Google Ads account by signing in to your manager account, selecting the customer or manager account in question, navigating to Tools and Settings > Access and security, then adding the Google account email address. Make sure to sign in with a valid Google Ads account (typically your manager account) for the OAuth flow. The login information provided corresponds to a Google account that does not have Google Ads enabled. The Google account used to generate the access token is not associated with any Google Ads account. Store and reuse access tokens until they expire. If you're using one of our client libraries, consult its documentation on how to refresh the token. The access token in the request header is either invalid or has expired. Wait a few minutes after the account is created before issuing requests against it. Wait an initial five minutes, then retry every 30 seconds. Trying to access an account that was just created before the account is established in the backend. No account found for the customer ID provided in the header. Consider using our client libraries as they handle this for you. Not specifying a client customer ID in the HTTP header.Ĭlient customer ID is required for all calls, so make sure you've specified one in the HTTP header. See Quickstart for details.Ĭlient customer ID was not specified in the HTTP header. Two operations in a single request contain a create operation for an asset with the same binary data.Ī mutate request with duplicated create operations containing the same binary data.Ĭreate the asset in a separate request, then link to it in the subsequent request or, use a temporary ID within the same request.ġ2 should be 1234567890. Log the error and present an error message to the user, optionally suggesting a unique ad group name or showing the list of names in use. Validate the keyword text in your app before making a request to the API.Īn ad group is being added or renamed, but the name is already being used by another ad group.Ĭreating a new ad group with the name of an existing active or paused ad group. The keyword text contains invalid characters. Once an ad is removed, it can no longer be updated-including changes to its status.Įnsure that your code does not attempt to update removed ads. Trying to associate the label with ads that have already been associated.Ĭheck first if the label to be added is already associated with the ads.Īn operation attempted to update a removed ad. This label is already associated with some of the ads. Validate the length of the line before making the API request. One of the fields in an ad was longer than the maximum allowed length. Validate URLs in your app before making the API request. One of the fields in an ad contains invalid characters. The status of the ad is, however, modifiable using MutateAdGroupAds. If you would like to modify the ad, you must make a new ad and then remove the old one. Once an ad is created, it cannot be modified. Trying to modify attributes other than the status of the ad. This operator cannot be used with a subclass of Ad. Then change the publishing status to In production following these instructions to avoid the refresh token expiring in 7 days. Go to the Google API Console and navigate to the OAuth consent screen. Your Google project's publishing status is Testing so the refresh token expires every 7 days and receives an invalid_grant error. Ī Google Cloud Platform project with an OAuth consent screen configured for an external user type and a publishing status of Testing is issued a refresh token expiring in 7 days. This page lists common errors and provides tips on preventing and handling them.įor a complete list of errors, review the error
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |