Hi Kevin, I've just started using the v201206 ManagedCustomerService and it appears to work even for non-MCC logins, showing the customer ID as well as the time zone and currency code.
Can you please confirm this is expected behaviour and that we can use the new service to get information for all accounts? On Tuesday, May 15, 2012 3:12:51 PM UTC+1, Kevin Winter wrote: > > Hi Ben (and future forum viewers), > We discussed this offline. Because this is an unlinked account (no > parent MCC) the ServicedAccountService can't operate on it (it can only > "see" accounts with parents). As a workaround, making an InfoService > request for this account (as I mentioned in my message on 2/22) will work. > > - Kevin Winter > AdWords API Team > > On Tuesday, May 8, 2012 12:26:53 PM UTC-4, Ben Vincent wrote: >> >> Hi Kevin, >> >> Are there still issues with the CustomerID = 0? >> >> For most my clients, I have no problems and can look up the Customer ID. >> But sometimes it comes back as 0. >> >> For example I just got this response: >> >> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >> <soap:Header> >> <ResponseHeader xmlns:ns2=" >> https://adwords.google.com/api/adwords/cm/v201109"; xmlns=" >> https://adwords.google.com/api/adwords/mcm/v201109";> >> <ns2:requestId>0004bf88a41487c80aec782b00003b94</ns2:requestId> >> <ns2:serviceName>ServicedAccountService</ns2:serviceName> >> <ns2:methodName>get</ns2:methodName> >> <ns2:operations>0</ns2:operations> >> <ns2:responseTime>25</ns2:responseTime> >> <ns2:units>0</ns2:units> >> </ResponseHeader> >> </soap:Header> >> <soap:Body> >> <getResponse xmlns="https://adwords.google.com/api/adwords/mcm/v201109"; >> xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201109";> >> <rval> >> >> <accounts><customerId>0</customerId><canManageClients>false</canManageClients></accounts> >> </rval> >> </getResponse> >> </soap:Body> >> </soap:Envelope> >> >> >> I am trying to run AdHoc reports for clients, for which I need the >> customerID. My code checks to see if I have the customer ID in my local DB, >> and if not it looks it up. Usually this works, but occasionally it fails. >> If I then look up the ID manually by logging into the web interface and >> copying the CustomerID, AdHoc reports work fine. >> >> Any ideas why? >> >> Thanks >> >> Ben >> >> >> >> >> >> On Thursday, 23 February 2012 16:52:09 UTC, Kevin Winter wrote: >> >>> Hi Chris, >>> Yes, that should work. It bases this behavior on the authenticated >>> user (which needs to be a non-MCC account). >>> >>> - Kevin Winter >>> AdWords API Team >>> >>> On Thursday, February 23, 2012 11:44:15 AM UTC-5, chris h wrote: >>>> >>>> Hi Kevin, >>>> Should this work with an existing oauth token? Or do I need to get a >>>> new token? I'm sure my token was created before you made this change. >>>> >>> -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
