client secret file (json)/key file and adwords

[scott....@gmail.com]

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 which is with a client ID for a native application which requires a client secret file (json). The other auth method appears to be as  Service account which requires a key file (ending with extension *.p12).

So the first question is how do i word it so i can ask my marketing team what kind of account they have set up for us? Is there somewhere they can look in their management console or something for adwords that will tell them.

Secondly,  where would i get the key file that is needed? I have asked them if they have access to that and they looked at me like i had three heads. They also mentioned that it appeared that a Service Account was a paid service so i am guessing they did not buy that.

So if they were to say that we have a Client ID account only, i was reading some information here:
https://developers.google.com/api-client-library/python/guide/aaa_client_secrets

which makes it appear as though i can create the json file, but i would still need to know the client secret. Is that just the developer token? that is the onlything that i was provided, was a token along with no other information.

Ultimate goal is to use this call to the web service to automate pulling of reports.

Any help is appreciated.

-Scott

[Umesh Dengale]

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 developer token, it will have pending approval status. Once the developer token is approved then you could make API call. However, you could make the API call to your test AdWords account with developer token with pending approval status. Please check out our Test account guide and create the test manager account and test AdWords account. Please check out our getting started guide.

 I recommend against using service accounts. It has very limited benefits comparing to normal flow and requires you to be a domain administrator. You could create the client id and client secret by following the steps given in the OAuth2.0 python guide. 

 

Cheers,

Umesh, AdWords API Team.

[scott....@gmail.com]

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 a client secret file(json). Is the MCC user able to go in to whatever console they have access to and create the client secret account for me? When they attempted to do that it appears that you have to put in billing information into the developer console in order to set up a "project", why would this be a paid service if the API calls are only going to be pulling reports like 'KEYWORDS_PERFORMANCE_REPORT'.

/Scott

[Umesh Dengale]

Hi Scott,

With Adwords manager account login, client id and client secret could be generated. Please follow the steps given in the python OAuth2.0 guide. The billing information needs to set up when creating the AdWords manager account and not required while creating the project in Google console. Please provide me privately the screenshot where it ask for billing information for creating the project in the Google console.  Just click Reply privately to author in the forum when responding.

Thanks,

Umesh, AdWords API Team.

[quasar.p...@gmail.com]

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 socket on port 3770

[statistics] connected

com.google.api.client.auth.oauth2.TokenResponseException: 400 Bad Request

{

  "error" : "invalid_grant",

  "error_description" : "Invalid JWT Signature."

}

at com.google.api.client.auth.oauth2.TokenResponseException.from(TokenResponseException.java:105)

at com.google.api.client.auth.oauth2.TokenRequest.executeUnparsed(TokenRequest.java:287)

at com.google.api.client.auth.oauth2.TokenRequest.execute(TokenRequest.java:307)

at com.google.api.client.googleapis.auth.oauth2.GoogleCredential.executeRefreshToken(GoogleCredential.java:384)

at com.google.api.client.auth.oauth2.Credential.refreshToken(Credential.java:489)

at de.jlo.talendcomp.google.adwords.AdWordsReport.initializeAdWordsSession(AdWordsReport.java:250)

at adw.test_0_1.test.tGoogleAdWordsReport_1Process(test.java:562)

at adw.test_0_1.test.runJobInTOS(test.java:961)

at adw.test_0_1.test.main(test.java:818)

Exception in component tGoogleAdWordsReport_1

java.lang.NullPointerException

at de.jlo.talendcomp.google.adwords.AdWordsReport.executeQuery(AdWordsReport.java:274)

[statistics] disconnected

at adw.test_0_1.test.tGoogleAdWordsReport_1Process(test.java:591)

at adw.test_0_1.test.runJobInTOS(test.java:961)

at adw.test_0_1.test.main(test.java:818)

Job test ended at 00:49 14/09/2016. [exit code=1] 

[Joyce Lava]

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