Hi Kevin, Thanks for getting back to me.
Can you just confirm - there is now absolutely no way for me to begin with a login email address and end up connected to the correct client within our account? James On Friday, 10 May 2013 16:51:02 UTC+1, Kevin Winter (AdWords API Team) wrote: > > Hi James, > InfoService is deprecated (was removed with v201302) - we recommend > developer use ManagedCustomerService to locate accounts within a hierarchy. > Note that this service will return an arbitrary login-email (I think it > might be the first one that was added to the account) so you won't be able > to search by login-email. Our recommendation is to use clientCustomerId to > identify accounts locally. > > - Kevin Winter > AdWords API Team > > On Wednesday, May 8, 2013 5:44:48 AM UTC-4, James Preece wrote: >> >> We have been routinely using the API for a few years now across multiple >> sub accounts. Everything continues to work correctly except in the case of >> one account and we are having great difficulty resolving the problem. >> >> *Example 1 - Normal Use* >> >> We connect to the API using our parent account and then create an >> InfoSelector in order to load information about the sub account. We pass >> the InfoSelector to the InfoService and something like this is returned: >> >> ApiUsageInfo Object >>> ( >>> [apiUsageRecords] => Array >>> ( >>> [0] => ApiUsageRecord Object >>> ( >>> [clientEmail] => exa...@email.com >>> [clientCustomerId] => 1234567890 >>> [cost] => 0 >>> ) >>> ) >>> [cost] => 0 >>> ) >>> >> >> >> We then use the clientCustomerId in subsequent requests to the API using >> 'SetClientId' >> >> *Example 2 - Incorrect Email* >> >> If we use a completely fake email then we get an error, like this: >> >> [ApiUsageError.INVALID_CLIENT_EMAIL @ selector; trigge...@email.com'] >> >> *Example 3 - Problem Account* >> >> For this one account, when we pass the request to the infoService we do >> not get an error. We simply get the following response: >> >> ApiUsageInfo Object >>> ( >>> [apiUsageRecords] => >>> [cost] => 0 >>> ) >>> >> >> It is as though the accont *doesn't have* a client customer id? >> >> When we speak to adwords support they tell us that the account is fine >> and that they are unable to support the API. >> >> Does anybody have any suggestions as to what we should try with this next? >> >> Many thanks in advance! >> >> James >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
