Re: CustomerService in v201607

After recently getting approved for a Basic token, we had to remove the validateOnly setting on the AdWords Service to prevent from returning null on calls to getCustomers(). On Monday, August 8, 2016 at 4:31:13 PM UTC-6, Karan Vohra wrote: > > For the MCC account, if i call

Re: CustomerService in v201607

Thanks for confirm it, As a Workaround, (If anyone is interested ) We can use *ManagedCustomerService.get *, to achieve info about all Accounts Managed by and MCC . ( If you are implementing webFlow , be sure you include the clientCustomerId of your MCC in the SOAP Headers ) . It would be

Re: CustomerService in v201607

Hello Jorge, Thanks for the information. Yes, currently you will only get back the Id of the MCC account whether you omit the clientCustomerId or not. We are currently working on making all the client customer Ids returned for future versions. Regards, Anthony AdWords API Team -- --

Re: CustomerService in v201607

It seems that doesn't matter if you add your clientCustomerId(MCC) in the soap headers or not . >From our side , we always get only the ClientCustomerId of the MCC account. As other people said in this thread , when you omit ClientCustomerId of your MCC on SOAP Headers, it should return a

Re: CustomerService in v201607

Hi Sachin, There should be no scenario in which you should get null when calling getCustomers. If you are encountering this, please create a new thread with more details. Regards, Anthony AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and

Re: CustomerService in v201607

Also, is there any scenario in which case the call to CustomerService.getCustomers() can return null? Thanks, -Sachin On Tuesday, 9 August 2016 05:10:31 UTC+5:30, Anthony Madrigal wrote: > > Hi Karan, > > If you set the client customer Id from the MCC account, getCustomers > should return

Re: CustomerService in v201607

Hi Karan, If you set the client customer Id from the MCC account, getCustomers should return all the customers under that account. However, if you do *not *set the client customer Id from the MCC account, you will only have the MCC account returned. This new method in the API will allow us to

Re: CustomerService in v201607

Hello, Currently, this functions exactly as you have seen, where it will only return the single account you're authenticating as. This does mean that it functions effectively the same way as the old get method. However, the new API does allow us to make future improvements without having to

Re: CustomerService in v201607

Further to my last post pointing to what the documentation said, we tested this functionality and it seems the documentation is not correct. Without setting the *clientCustomerId,* we still get back one entry only when calling the getCustomers() method for a Manager account. It seems the new

Re: CustomerService in v201607

Further to my last post pointing to what the documentation said, we tested this functionality and it seems the documentation is not correct. Without setting the *clientCustomerId,* we still get back one entry only when calling the getCustomers() method for a Manager account. It seems the new

Re: CustomerService in v201607

Hi Shwetha, The documentation says something different from what you mentioned. It says in this page: https://developers.google.com/adwords/api/docs/guides/accounts-overview#customerservice *In v201605 and earlier, if no clientCustomerId is specified, then the response will contain a

Re: CustomerService in v201607

Hi Oliver, If you do not specify a clientCustomerId in the request header, the getCustomers method will return the account details of the authenticated customer. If the canManageClients