Sadly, the system we're building will need to operate without human interaction. Otherwise, I'd love to take the easier option. I understand that any option for connecting to Google Ads via API (beside service accounts) would require a user to interact with the application, even if just to enter a password -- that is correct, yes?
As for the service account; The service account was created while signed in under email address: [email protected]. [email protected] is also a user on the Google Ads account. However, email [email protected] was utilized to create the test account. Also, the service account email is something like: [email protected] What if I just added the service account email as a user in the test Google Ads account, will that work? Better yet, should I be impersonating the email [email protected] with the service account [email protected]? Currently, I have 'impersonated_email' set to [email protected] but I can change it to [email protected]. On Tuesday, October 4, 2022 at 9:45:24 AM UTC-7 adsapi wrote: > Hi Chad, > > Thank you for your reply. > > Interactions are sometimes made private due to the sensitive information > being shared. Regarding your issue with the service account authentication, > and for this "*User in the cookie is not a valid Ads user.*" issue, this > appears to be related to the NOT_ADS_USER > <https://developers.google.com/google-ads/api/docs/best-practices/common-errors#not_ads_user> > > error. > > That said, could you confirm whether the user / email address you used > during the service account credentials generation process is indeed one > that has access > <https://support.google.com/google-ads/answer/9978556?visit_id=638004903301082274-1294938945&rd=1> > to > a Google Ads account? > > In addition, I understand that you have opted to use the service account > flow. However, we also recommend that you consider using the other > authentication flows, since as also per the service account > <https://developers.google.com/google-ads/api/docs/oauth/service-accounts> > guide > : > > - *Key Point: We strongly recommend using OAuth2 desktop app or web > app flow > > <https://developers.google.com/google-ads/api/docs/oauth/cloud-project#choose_an_application_type> > instead > of service accounts unless you need a domain-specific feature (for > example, > impersonation). OAuth2 desktop app and web app flows do require an initial > user interaction for granting access to the account, but are much simpler > to set up.* > - *For the OAuth2 desktop app flow > > <https://developers.google.com/google-ads/api/docs/oauth/cloud-project#desktop>, > > you can persist a refresh token (which never expires) to obtain a new > access token whenever necessary. When using one of our client libraries > <https://developers.google.com/google-ads/api/docs/oauth/client-library>, > you can authorize your app by filling out a configuration file.* > > Best regards, > > [image: Google Logo] > Peter Laurence > Google Ads API Team > > > ref:_00D1U1174p._5004Q2ewsYl:ref > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/18990715-9763-4e66-a46a-8eecfbae5338n%40googlegroups.com.
