Re: client secret file (json)/key file and adwords

Hi, I can see that you open a new thread with your concern in this post . Let's keep the communication in that thread. Thanks, Joyce, AdWords API Team -- --

Re: client secret file (json)/key file and adwords

> > Hi, > Were you able to connect to Google Adwords using Talend? I am in a bind right now because I couldn't make it work. I am also using the same component. I followed everything but still getting this error. Please help. Starting job test at 00:49 14/09/2016. [statistics] connecting to

Re: client secret file (json)/key file and adwords

Hi Scott, With Adwords manager account login, client id and client secret could be generated. Please follow the steps given in the python OAuth2

Re: client secret file (json)/key file and adwords

Umesh, Just so I make sure I understand what you are saying. I should stick with using the adwords account and not a service account. I have a token already but i think the issue is that i am using talend and a component created in that application called tGoogleAdWordsReport_1 and it requires

Re: client secret file (json)/key file and adwords

Hi Scott, In the AdWords API, there are two types of account, AdWords Manager account (MCC) and the AdWords account. The manager AdWords account is used to manage the AdWords accounts and to apply for developer token. When you apply for

client secret file (json)/key file and adwords

probably a few dumb questions here but i will post it anyhow. I am attempting to use talend to pull data from google adwords at the request of our marketing group. They have been less than helpful in determining which type of account was set up and therefore two forms of authentication. One