Hello Tousdan, It looks like your MCC account (the account beginning with [EMAIL PROTECTED]) is quite old, and has a couple of irregularities with it that are remnants of legacy AdWords systems.
One odd thing is that it is an MCC account that also contains an inactive campaign in it, which shouldn't be possible anymore but is a symptom of an account migration that may have taken place a while ago. I'm not sure that that in particular is the reason you're getting these errors, but it's definitely non-standard and I wouldn't be surprised if it led to other irregularities down the line. The main odd thing is that there are three login emails associated with your MCC account. One of them is a "legacy" login that starts with [EMAIL PROTECTED] and another is the same email address with the G capitalized, [EMAIL PROTECTED] This could definitely be causing confusion in the AdWords API, and I'd recommend that you (or the account owner) disable access from the legacy AdWords account login. This can be done by logging in to the AdWords web interface with the account's credentials, going to the "My Account" tab and then the "Access" sub- tab, and clicking on "Terminate access" next to the email address that is described as being the "old, shared login". Cheers, -Jeff Posnick, AdWords API Team On Aug 29, 11:24 am, tousdan <[EMAIL PROTECTED]> wrote: > Listing the MCC: > 231468d27189721d29b129b5c168c7e3 > > Getting the information from the duplicate accounts: > 173aa171ac65d74539bc9e3898ec4857 > aaaf5ac868172b86e4fe34207a1e3390 > > I doubt the 2 last ones are relevant but still giving them to you. > > On 27 août, 16:04, AdWords API Advisor <[EMAIL PROTECTED]> > wrote: > > > Hello Tousdan, > > > If you're not at liberty to pass along the customer IDs in question > > then could you provide the value of the requestId SOAP response > > headers for the AccountService calls in question that illustrate the > > problem? > > > Cheers, > > -Jeff Posnick, AdWords API Team > > > On Aug 27, 1:49 pm, tousdan <[EMAIL PROTECTED]> wrote:> Thanks for the > > reply. I'm unable to provide you with the customer IDs > > > since the account is not mine. > > > > On 26 août, 12:11, AdWords API Advisor <[EMAIL PROTECTED]> > > > wrote: > > > > > Hello Tousdan, > > > > > You're correct in that each login email address should uniquely map > > > > to only one AdWords account, though there are always one-offs due to > > > > legacy accounts or other quirks that can cause confusion. > > > > > If you let me know the two different customer IDs I'll look into > > > > what's going on. > > > > > Cheers, > > > > -Jeff Posnick, AdWords API Team > > > > > On Aug 25, 3:26 pm, tousdan <[EMAIL PROTECTED]> wrote: > > > > > > Greetings. > > > > > > I'm having issues with the following methods: > > > > > AccountService.getClientAccounts & AccountService.getAccountInfo. I've > > > > > been trying to get the accounts from anMCCaccount (using > > > > > getClientAccounts) then getting the detailed information for each > > > > > individual account (using getAccountInfo with the clientEmail provided > > > > > by getClientsAccounts). > > > > > > Unfortunately I've just had anMCCwhich has different accounts using > > > > > the same email address and once I try to acquire each account > > > > > information, i'm receiving the same thing for both accounts. The only > > > > > hint I have that these accounts are different is that the customer ID, > > > > > when using the Adwords interface, is quite different. > > > > > > As I understood it, duplicates in anMCCshould not happen, so anybody > > > > > got a clue how I might acquire such information using the Adwords API? > > > > > > Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
