Re: Upgrading to v201206

Hi Bernardo, Could you post a sanitized (blank out developer and auth tokens) sample request? Are you authenticating with an MCC account? Are you targeting an MCC account or a client account (or no target, which effectively uses the account you authenticate with). - Kevin Winter AdWords API

Re: Upgrading to v201206

Hi Kevin, I tried this example to request information from ManagedCustomerService but I keep getting "internal server error". Any ideas of what might be going wrong? Thanks, Bernardo Quinta-feira, 25 de Outubro de 2012 16:08:15 UTC+1, Kevin Winter escreveu: > > Hi David, > Here's an example

Re: Upgrading to v201206

Hi David, Here's an example of an MCS.get call from the Java Library: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> https://adwords.google.com/api/adwords/mcm/v201209"; soapenv:mus

Re: Upgrading to v201206

Hi Simon, we have the problem when upgrade to v201209, we also use vb, did you fix this problem? if so, could you pleaase share your answer on how to fix this problem? Many thanks. David On Friday, July 13, 2012 10:16:41 PM UTC+10, Simon Day wrote: > > Hi, > > We have developed a number of

Re: Upgrading to v201206

Hi Kevin, We tried to upgrade to v201209 and we have the same problem. I have tried to add xmlns='https://adwords.google.com/api/adwords/cm/v201209' on the serviceSelector element. but we still receive the same error message. Could you please

Re: Adwords API - Upgrading to V201206 and OAuth

MCS will not return IDs of unlinked accounts. Use the CustomerService instead for this purpose as it always returns the ID. It's simpler and easier than using the InfoService. Oliver On Friday, October 5, 2012 3:47:50 PM UTC+1, Nakul Ringshia wrote: > > Hi Kevin > > I have implemented the co

Re: Adwords API - Upgrading to V201206 and OAuth

Hi Kevin I have implemented the code to call the Managed Customer Service to get the client customer id. However I have found a few emails for which the MCS is not returning the customer id (and hence I have unable to download reports). Based on my understanding its because these emails are ta

Re: Adwords API - Upgrading to V201206 and OAuth

Hi Nakul, As Kevin mentioned, yes, ClientLogin is deprecated, and there's a 3 year deprecation policy for Google Apps. Google Apps and Google AdWords are however two different products guided by different deprecation policies, so AdWords may decide to drop support for ClientLogin at an earlier

Re: Adwords API - Upgrading to V201206 and OAuth

Hi Alexander, Unfortunately, another team manages ClientLogin, so I can't speak with authority. Here's the blog post announcing the deprecation: http://googledevelopers.blogspot.com/2012/04/changes-to-deprecation-policies-and-api.html We'll probably provide support in the AdWords API until so

Re: Adwords API - Upgrading to V201206 and OAuth

Thanks Kevin I tried setting the ClientCustomerId in the request header and that worked!!!. I think using this approach makes sense (there's still some work that I will need to do - calling the managed service account to get the client id based on the email). One key factor that will determin

Re: Adwords API - Upgrading to V201206 and OAuth

On Tuesday, September 18, 2012 4:58:53 AM UTC-7, Nakul Ringshia wrote: > > Hi > > I am currently using v201109 to fetch data (keyword, adgroup and criteria > reports) from Google Adwords (using the dot net client library). Currently > we are using the ClientLogin authorization method. Since th

Re: Adwords API - Upgrading to V201206 and OAuth

This is slightly inaccurate. The error message refers to the use of clientEmail to identify which account is being targeted with a request. You'll need to specify a clientCustomerId instead (which can be retrieved with the ManagedCustomerService as mentioned below. You don't have to authenti

Re: Adwords API - Upgrading to V201206 and OAuth

BTW, you don't need to hard code the list of AccountID's, you can use the ManagedCustomerService to retrieve the account tree for an MCC. On Wednesday, September 19, 2012 8:43:19 AM UTC-4, Alexander Nitschke wrote: > > You can use OAuth 2.0 but it isn't really necessary. Your assumption > regard

Re: Adwords API - Upgrading to V201206 and OAuth

You can use OAuth 2.0 but it isn't really necessary. Your assumption regarding OAuth2 with v201206 is wrong as the old login still works. What doesn't work is the login as a simple client, only logins as MCC will work with v201206. So you have to login into the MCC, and then change the ClientID

Adwords API - Upgrading to V201206 and OAuth

Hi I am currently using v201109 to fetch data (keyword, adgroup and criteria reports) from Google Adwords (using the dot net client library). Currently we are using the ClientLogin authorization method. Since this version will sunset on Oct 26, 2012, I have started the upgrade to v201206 (downl

Re: Upgrading to v201206

Hi Simon, The ManagedCustomerService uses a Generic Selector (unlike the ServicedAccountService, which used it's own). This selector is shared from the CM namespace: https://developers.google.com/adwords/api/docs/reference/latest/ManagedCustomerService.Selector You will need an xmlns='https:

Upgrading to v201206

Hi, We have developed a number of custom VB functions to enable reporting on and managing Adwords accounts. I'm trying to upgrade from v201109 to v201206 but seem to be having issues straight away! The first thing I need to do is list the client accounts under a given MCC account. I can see th