Re: AuthenticationError.NOT_ADS_USER @

2016-02-22 Thread Matthew Trevor
I've tried that but it comes up the same. Going forward and when we are live, what if I'm not the MCC on one of our client accounts? On Monday, 22 February 2016 17:30:20 UTC, Yin Niu wrote: > > Hi Matt, > > The MCC accont login requests the token. However, to pull the campaign > data, you would

Re: AuthenticationError.NOT_ADS_USER @

2016-02-22 Thread Matthew Trevor
The scenario is we wish to get clients to log into our website and give us authority for our server to download a list of their campaigns. Currently the developer has logged into Google and created an application and we have got the client id/secret from that login. who then requests the acces

Re: AuthenticationError.NOT_ADS_USER @

2016-02-22 Thread Matthew Trevor
Hi Yin, I've just signed in to the TEST Adwords user account and got an authorisation code and then the access code and then submitted the request again, it came back with: http://schemas.xmlsoap.org/soap/envelope/";>https://adwords.google.com/api/adwords/cm/v201509";>00052c5e53be27000a8159c489

Re: AuthenticationError.NOT_ADS_USER @

2016-02-22 Thread Matthew Trevor
Hi Yin, Sorry for the late reply but I've been away on holiday. Thank you for your response. We have not even got to requesting the refresh token, do you mean the access token? Thanks, Matthew On Friday, 22 January 2016 16:29:35 UTC, Yin Niu wrote: > > Hi Matt, > > Can you verify that the a

Re: AuthenticationError.NOT_ADS_USER @

2016-01-22 Thread Matthew Trevor
Hi Yin, Thanks for the advice, but maybe I'm missing something with the Google app as I get back what looks to be a good result. If I explain the path in more detail: On our test website, the user (whilst logged into their Google Adwords account - a test MCC account at this point) clicks on a

AuthenticationError.NOT_ADS_USER @

2016-01-21 Thread Matthew Trevor
I'm rather new to the Google Adwords API but I'm struggling with the authentication. I've looked at the other posts that people have put on but they don't seem to relate to my issue, I think. The process so far: In the web app we get the Google authorisation code and this comes back fine. We