Re: service account authentication issue

&#)$#$)$ Well the connection issue was a work VPN issue. back to the same error NOT_ADS_USER. I'll see if they can fix whatever is the issue. thanks, lee On Tuesday, July 2, 2024 at 2:11:42 PM UTC-5 Lee Franke wrote: > Fixed that issue. I'm not getting > > Detail="failed to connect to all ad

Re: service account authentication issue

Fixed that issue. I'm not getting Detail="failed to connect to all addresses" "description":"Failed to pick subchannel" thanks, On Tuesday, July 2, 2024 at 12:56:57 PM UTC-5 Lee Franke wrote: > Turning on logging got the error data I needed. It was as I expected: > > "The Google account (@gmail

Re: service account authentication issue

Turning on logging got the error data I needed. It was as I expected: "The Google account (@gmail.com user) that generated the OAuth access tokens is not associated with any Ads accounts. Create a new account, or add the Google account to an existing Ads account." Reading it literally indicate

Re: service account auth error - not_ads_user

Good day, Thanks for your response. I have managed to make the code above work. I have just replaced *OAuth2PrnEmail *with the manager's account email - I used the service account before, and it didn't work. Thanks for your help! Feel free to close the ticket. Regards, Vlad On Mon, Jun 26, 2

Re: service account auth error - not_ads_user

Hi Vlad, Thank you for the reply. Kindly note that the NOT_ADS_USER error (https://developers.google.com/google-ads/api/docs/best-practices/common-errors#authenticationerror) is one of the common authorization errors encountered when the service account has not been correctly linked to the Goo

Re: service account auth error - not_ads_user

Good day - thanks for your response. I can confirm I have already completed all 1-5 actions described above. Service account should be configured correctly, and ready for using. As to this one: *< Moving forward to NOT_ADS_USER error, yes, it is indeed means that the Google account used to

Re: Service account

Let me explain all my steps. 1. I've created service account in my project in https://console.cloud.google.com/. 2. I've created key and get creds from json file. 3. My admin configure domain wide delegation for this service account, scope https://www.googleapis.com/auth/adwords 4. I have a user

RE: Service account

Hi Kate, Thanks for reaching out to the Google Ads API Forum. If you have used an impersonated email as @*.iam.gserviceaccount.com, then note that service account authentication will not work. Kindly note that impersonated_email (formerly delegate_account) is an account email used as a de

Re: Service Account receives HTTP code 401: Request is missing required authentication credential.

Hi Martin, Apologies for the delayed response. Could you point me to that thread you're referencing? Thanks, Ben, Google Ads API Team ref:_00D1U1174p._5004Q2R74x8:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~

Re: Service Account receives HTTP code 401: Request is missing required authentication credential.

Hi Ben, I have just read in another thread that the Master Account needs to be set up under a unique gmail address. My Master Account is under the same email address that owns my Sub Ad Accounts. Is this the reason for my OAuth issues? Regards, Martin On Wednesday, December 1, 2021 at 11:43

Re: Service Account receives HTTP code 401: Request is missing required authentication credential.

Hi Ben, I have been diving in to the documentation on the client library from your link. I looked at this before, and now I remember more clearly why I was reluctant to use a Client Library. I do not have any local PHP environment. From what I understand at first glance, to run a test locall

Re: Service Account receives HTTP code 401: Request is missing required authentication credential.

Hi Ben, I'm still a little concerned about my account setup since the documentation is dispersed over several different documents that are all written for a variety of use cases. Also the curl response contains the message: "User in the cookie is not a valid Ads user." I will set up the clien

Re: Service Account receives HTTP code 401: Request is missing required authentication credential.

Thanks Martin, As far as I can tell your account set up looks OK, but since it lives in Pantheon I can't examine your account directly so I can't be 100% sure. One benefit of using a client library is it will handle the process of generating and refreshing your access token automatically, which

Re: Service Account receives HTTP code 401: Request is missing required authentication credential.

Hi Ben, Thanks for your reply. Do I understand correctly that as far as you can see the setup of my Master Ad Account, the gmail account that owns it, the Master Account that owns the Developer Token, the Google Workspace and the Service Account is all OK? Yes, I am using php curl to request

Re: Service Account receives HTTP code 401: Request is missing required authentication credential.

Hi Martin, Apologies for the delayed response here. I'm still trying to determine the exact cause of this issue, but it's currently not quite clear. It doesn't appear related to how impersonation was set up. It looks like you're using curl to make these requests, right? Which means you must be

RE: Service Account still receiving HTTP code 401

Hello Martin, Thanks for reaching out to the Google Ads API support team. I saw you have another thread with this same concern. Our team is still investigating the issue you have encountered. As soon we have any updates we’ll reach out to you. Regards, Reminder: Share your feedback about the G

Re: Service Account receives HTTP code 401: Request is missing required authentication credential.

Hi, I sent the requested logs on November 12th, but I haven't heard back from anyone regarding the issue. Please can someone update me? Regards, Martin On Monday, November 8, 2021 at 6:56:18 PM UTC+2 Martin Levi wrote: > Hi Yasar, > > Thanks for your response. I followed the instructions in

RE: Service account give NOT_ADS_USER error

Hi Pratik, Did the the domain administrator delegate domain-wide authority to your service account? Does the delegated account a user in the ads account you are trying to reach? Could you privately send us a request and response log of API communication that returns this error? The request an

Re: Service account authentication issues

Hi Jakob, Would it be possible for your application to use either of the Desktop or Web App OAuth strategies instead of Service Accounts? Although they require human intervention, you should only need to intervene once to create a refresh token, which can then be used to generate access tokens

Re: Service Account receives HTTP code 401: Request is missing required authentication credential.

Hi Yasar, Thanks for your response. I followed the instructions in this document which has a slightly different workflow. I think that I have the right pieces but not set up the right way. I will send you the informati

RE: Service Account receives HTTP code 401: Request is missing required authentication credential.

Hi Martin, Thanks for reaching out to us. Could you confirm if you already followed the instructions discussed in this document, especially the prerequisite? If yes and the issue still persists, then could you provide the following details via Reply privately to author option to further invest

Re: Service account authentication issues

Hi Jakob, Thanks for your feedback. Please allow me to share this with our team and see if there are any other options we can provide. Regards, Matt Google Ads API Team Reminder: Share your feedback about the Google Ads (AdWords) API! Take the 2021 Google Ads API and AdWords API Annual Survey

Re: Service account authentication issues

Well ... that's really bad. For pure backend services there is no other way then using service accounts and this poses a major security risk. Are there any plan on improving on this? Maybe allow service accounts to be invited as users to a google ads account so that they can be managed similarly

RE: Service account authentication issues

Hi Jakob, I'm Kevin from the Google Ads API Team. I'll my best to answer your question. As stated in our documentation, Google Ads does not support using service accounts without impersonation. I'm afraid that there's no way to manage permissions for a service account in Google Ads. Let me

Re: Service Account

Hi Martin, Thank you for your feedback. I've raised this with the rest of our team, however, there's no definite timeline on when our Quickstart guide will be updated. You may check it again at a later time or follow our blog for future updates. Regards, Kevin Gil Soriano Google Ads API Tea

Re: Service Account

Hi Kevin, Thanks for your response. I think it would be a good idea to update the Google Ads Api Quickstart guide. The Oauth guide is apparently written for the user base of a vast ecosystem, whereas I suspect that many Ads Api developers will be specifically looking to develop unattended ser

RE: Service Account

Hi Martin, Thank you for raising your concern with us. I'll raise it with our team to possibly update our Quickstart guide to explicitly mention service accounts as another option to access the API. You may check our Quickstart guide at a later time or follow our blog for future updates. For

Re: Service account and client secret

Hi, Our client needs the campaign specific tracking data from Google ADs APi programmatically i.e. CampaignID channel Js enabled VPN/Proxy in use Country City Continent Language Browser ISP IP = IP of click app = app Id for marketing device = device type id of user mobile phone (eg iphone 6 plus,

Re: Service account and client secret

Hi Shikha, I work with Mark and allow me to assist you. For generating a service account, you may continue to refer to this guide. For issues that you may encounter when authenticating using the service account, even after following the API guide, you may reach out to the Google API Console su

Re: Service account and client secret

Thanks Team. Our client wants to use service account only and as we saw your guide it recommends to use client OAuth client instead of service account. I am working on it for last 2 weeks, and confused. For getting below details (tracking ) for campaigns which way needs to be used service acc

RE: Service account and client secret

Hello there, Thank you for reaching out to us. With regard to your concern related to service account, we suggest that you follow this guide on setting up the Google Ads API using service accounts. As stated on that guide, we strongly recommend using OAuth2 desktop app or web app flow instead

RE: Service Account to access MCC that are not linked

Hi Todd, Thank you for reaching out. >From the APIs' perspective in authenticating your API requests, we strongly >recommend using OAuth2 desktop app or web app flow instead of service accounts >unless you need a domain-specific feature (for example, impersonation), as >mentioned (Key Point se

RE: Service Account

Hi Klaudia, Thank you for reaching out to our API support team. Since your question appears to be more related to service accounts and its usage, then I would recommend that you reach out directly to the Google API Console support team, via this link, for further insight on what you may be abl

RE: Service Account: WaitingForActivation

Hi Todd, To have a closer look at the issue, could you provide the complete request and response logs with request ID generated on your end where we can see the issue? You can provide it via Reply privately to author option. If you haven't enabled the logging of the API transactions for the spe

Re: Service account and Google Ads Api

I had the exact same problem - NOT_ADS_USER If you indeed completed all the prerequisites and the succeeding steps

Re: Service account and Google Ads Api

Hi Thijs, The NOT_ADS_USER should point to an issue with user that was logged in while creating the service account. Errors related to the developer token and customerID should return a different error. Moving forward, could you also confirm if all the prerequisites and the succeeding steps, i

Re: Service account and Google Ads Api

I also noticed something else. If i change the developerToken or customerId parameter I get the same error. So apparently those are wrong. The developer token I got from the Google ads manager account > TOOLS> API center. Access level for this developer token is "Test account" The customer Id

Re: Service account and Google Ads Api

The *Reply privately to author* is disabled, i do not have sufficient rights for some reason. Just to make sure. In our Google Ads Manager Account there is no option Tools icon > Account access > Users. I can find my user details under SETTINGS & BILLING > ACCOUNT > Access & Security. I u

Re: Service account and Google Ads Api

Hi Thijs, I had to delete your previous response and repost it below : "Hi Peter thanks for replying. I checked this and I am using the correct e-mail account address for as far as I can tell. The (service account) e-mail address I use to generate the access token is listed under credentials

Re: Service account and Google Ads Api

Hi Peter thanks for replying. I checked this and I am using the correct e-mail account address for as far as I can tell. The (service account) e-mail address I use to generate the access token is listed under credentials compatible with this API (in Google Ads Api). The email address itself l

RE: Service account and Google Ads Api

Hi, The NOT_ADS_USER indicates that the email address you may have used to generate the credentials may not have access or associated to any Google Ads accounts. You may retry and make sure to log in with a valid Google Ads account (typically your manager account) when creating the credentials

Re: Service Account - creation + access

Hello, I Strongly recommend against using service accounts. It has very limited benefits comparing to normal flow and requires you to be a domain administrator. Please verify that you followed the steps provided in OAuth2.0 guide for the Ruby client library. Please check out our OAuth2.0 guide

Re: Service Account Access Error "Unauthorized client or scope in request"

Hi Cory, Thanks for the update - glad to hear that my recommendation worked for you. Your assessment of the docs is spot on -- there were some changes in the Google Developers Console recently, and we're a bit behind on syncing up our guides. We plan to take care of that in the near future. Th

Re: Service Account Access Error "Unauthorized client or scope in request"

Hi Josh, I followed your advice and used the offline flow from the OAuth guide to obtain a refresh token for the user. I added that token to the config with the new OAuth2 client credentials (not service account), and it wor

Re: Service Account Access Error "Unauthorized client or scope in request"

Hi, It may be that your old Google Apps Domain was a Free edition (legacy) domain, which is why the new domain with a similar setup will not work without upgrading. However, you can achieve your goal of having read-only access for your applic

Re: Service Account Access Error "Unauthorized client or scope in request"

We've had no problems with our previous service account for about 1 year now. It still works fine, and we never had to add any AdWords scope to anything. It even worked locally without any issues which isn't a Google App. And yes we need the service account, because managers of the AdWords MCC

Re: Service Account Access Error "Unauthorized client or scope in request"

Hi, I'm not aware of any recent changes to service account requirements -- they have always required a Google Apps Domain as far back as I recall. Coming at this from a different angle, do you actually need service account functionality, or could you simply use *offline* access as described in

Re: Service Account Access Error "Unauthorized client or scope in request"

The only way to use the API now with a service account is using a Google Apps domain paying for Google Apps users per month? It wasn't like that before. Plus how would this work with localhost and testing purposes? We don't need any of what Google Apps has to offer. We just want API access like

Re: Service Account Access Error "Unauthorized client or scope in request"

Hi, Did you also complete the Steps to granting a service account impersonation abilities , using the new client ID? Thanks, Josh, AdWords API Team On Thursday, August 20, 2015 at 4:11:04 PM UTC-4, Cory Sha

Re: Service Account Fail Connection for v201409 ?

Hi Jan, Thanks for the info. It looks like this is a known issue with the OAuth library: - https://github.com/google/google-oauth-java-client/issues/100 - https://github.com/google/google-oauth-java-client/issues/101 The AdWords API Team doesn't maintain that lib, but we'll upgrade our

Re: Service Account Fail Connection for v201409 ?

Hi Josh, yes, I have seen this problem also and changed to the new scope https://www.googleapis.com/auth/adwords I guess there is a problem with the error handling in the method TokenResponseException.from(..) If the response has no content (InputStream is null, the creation if the exceptio

Re: Service Account Fail Connection for v201409 ?

Additional information to my last post. I got NullPointerExceptions like this: java.lang.NullPointerException at com.google.api.client.repackaged.com.google.common.base.Preconditions. checkNotNull(Preconditions.java:191) at com.google.api.client.util.Preconditions.checkNotNull(Preconditio

Re: Service Account Fail Connection for v201409 ?

Hi Jan, That scope has been deprecated, but tokens obtained for it in the past should continue to work. See our Authentication guide for details and for the new, recommended scope. Were your requests working previous

Re: Service Account Fail Connection for v201409 ?

I have the same issue with the Java API. I use the version 1.37.0 of the ads-lib and 1.19.0 for the http-client. At the moment I use the scope "https://adwords.google.com/api/adwords";. Is there any additional scope I have to add? Best regards Jan Lolling On Wednesday, 5 November 2014 21:36:19

Re: Service Account Fail Connection for v201409 ?

I was using v17 with v201402 and v18.5 with v201409. It turns out that I needed an additional scope on my Google Apps Engine account set to allow my Adwords account access with the new API version. Thanks. On Wednesday, November 5, 2014 3:36:19 PM UTC-5, Josh Radcliff (AdWords API Team) wrot

Re: Service Account Fail Connection for v201409 ?

Hi, Just to make sure I'm understanding your setup, are you using the same version of the *client library* for both your v201406 and your v201409 tests? In other words, does v18.5 work for v201406 but not v201409, or does v18.5 not work for either API version? Thanks, Josh, AdWords API Team O

Re: Service Account NOT_ADS_USER error

Hi, Did you set the prn email when getting the access token in service account flow? This field is required, since AdWords API doesn't allow anonymous OAuth2 access. Cheers, Anash P. Oommen, AdWords API Advisor. On Friday, October 24, 2014 3:31:15 PM UTC-4, IMM Boulder wrote: > > I have verifi

Re: Service Account NOT_ADS_USER error

I have verified that clientCustomerId is in the header and that the user is an adwords user. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=

Re: Service account - different errors

Hello Justin, Please send me exact XML request and server response for both of these errors. Also, check that the account you specify in "prn" has access to the account you specify in "clientCustomerId", it is not the case now. -Danial, AdWords API Team. On Thursday, June 19, 2014 9:35:25 P

Re: Service account - different errors

Hi Danial, I replied here, but also directly to you (with private information). I can't see what I have configured here incorrectly - but maybe you have some insight and can see what's wrong. This is halting development, as we can't even get started :( Thanks Justin On Thursday, June 19, 2014

Re: Service account - different errors

Yes I am a google app domain administrator. I have a user in the MCC production account "jus...@campaignium.com" . I used this user to create the service account in the google developer console. Then I went in in google apps domain and gave rights to the "client id" of the service account user

Re: Service account - different errors

Hello Justin, Are you a Google App domain administrator? For all other cases please use an offline or web flow instead, see this guide for more details: https://developers.google.com/adwords/api/docs/guides/authentication The first error means you are trying to access the account that doesn'

Re: service account oauth2 node.js

Hi, Please review our authentication guide. In most cases, you do not need a service account. When using test accounts, please carefully review the test account guide

Re: Service Account Scope Access Failure

Hi, In case others have similar issues, below are a few tips on setting up service account access to the AdWords API: 1. You can only impersonate a user in your domain (this is the user you specify for the OAuth2PrnEmail key in App.config). In this case, one of the reasons we had tro

Re: Service Account Scope Access Failure

Hi, Having some more details on your config would indeed help. You can send those *only to me* by clicking "Reply to Author" on this message and we can follow up via email from there. Thanks, Josh, AdWords API Team On Friday, March 14, 2014 11:55:56 AM UTC-4, apiapi wrote: > > Hi Josh. Thanks

Re: Service Account Scope Access Failure

Hi Josh. Thanks for the fast response. We do in fact require a Service Account, we are not building a "typical" app that interacts with the API. I believe I have done all of the steps and am still getting an error about the scope permissions. I have notified our enterprise account manager as

Re: Service Account Scope Access Failure

Hi, In general we recommend (here and here) using the *installed application* or *web *flow instead of *service accounts*. Service accounts are consi

Re: Service Account Scope Access Failure

I downloaded the latest AdWords API v201402 bits, and still receive the same error when simply trying to enumerate the accounts under my MCC using the sample code. I am receiving the same error I got with the 201309-era code. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us

Re: Service account via Java client getting "access_denied"

Why not actually answer the original questions instead of deflecting? Why offer a service and then tell people not to use it? On Thursday, August 29, 2013 9:22:05 AM UTC-7, Takeshi Hagikura (AdWords API Team) wrote: > > Hi, > > First, does your application needs impersonation? > If all you wan

Re: Service account via Java client getting "access_denied"

Hi, First, does your application needs impersonation? If all you want to do is having access to client accounts under an MCC, then how about using other authentication (installed application or web flow)? Either way, once you store a refresh token, there'll be no human interactions like servi