Hello Tim, Have you tried v13's getClientAccountInfos() method?
http://code.google.com/apis/adwords/docs/developer/AccountService.html#getClientAccountInfos If you call it when the effective user (as explained in the docs) is your "MainMccAccount" then you should receive a list of all accounts one level under that, including what you refer to as "NestedMccAccount". The accounts that are normal AdWords accounts will have their isCusomterManager attribute in the response set to "false". The "NestedMccAccount" that you refer to would have its isCustomerManager attribute set to "true", which would be your cue to perform another getClientAccountInfos() method with "NestedMccAccount" as the effective user and get all the accounts one level under that, including what you call "Normal Account". Iteratively calling getClientAccountInfos() like that should give you a complete picture of your account structure with all the information you need to model the hierarchy. If you're seeing different behavior, please let me know and provide the values of the requestId SOAP response headers in the relevant SOAP calls so that I can check on exactly what might be going on. Cheers, -Jeff Posnick, AdWords API Team On Oct 29, 3:45 pm, timprepscius <[EMAIL PROTECTED]> wrote: > Oh.. By the way.. > > There is a bug with e-mails with nested mcc accounts.. > > If I have an MCC account "MainMccAccount" that contains an MCC > "NestedMccAccount" and that contains a normal account "Normal > Acccount". > > And I say to your service.. Give me all email addresses for my > MainMccAccount. > I do not get the email for the NestedMccAccount.. I get the email > address for the "Normal Account". > > This is a problem.. > > Why is this a problem? > Because if I then go and request a report for the Email address I got > back (via the MCC, but using the NormalAccount e-mail in the "clients" > field), I will get a DIFFERENT ACCOUNT ID back in the data than if I > request the report via the MCC and clients=NULL. > > Anyway.. > That was a confusing description of the problem.. > > I believe there is no mechanism to get the e-mail address of the > NestedMccAccount. Which is what I need to keep the mcc data reference > frame correct. > > I could be wrong... If I am, please tell me. Else please fix (in the > next 5 years is fine). > > -tim > > p.s. Of course making the structure report cross client.. And fixing > the numerous bugs therein would be much nicer than fixing this email > bug. > > On Oct 29, 5:50 am, "[EMAIL PROTECTED]" > > <[EMAIL PROTECTED]> wrote: > > Jeff, > > > Thanks for the workarounds you suggested. I'll send the request id > > later. > > > On Oct 29, 12:07 am, AdWords API Advisor > > > <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > I'm sorry, but I'm not having any luck even trying to add an email > > > address with a colon in it as a login in the AdWords web interface. > > > (I'm not exactly sure how your client was able to add such an > > > address.) I'm assuming that this just isn't supported, but if you > > > could give me the value of the requestId SOAP response header from the > > > response you get when trying to log in, I can pass that along to the > > > engineering team to confirm. > > > > I'm skeptical about this working, though, so I'd also recommend > > > reaching out to your client and seeing if they can associate an > > > additional email address as a login for that account. > > > > Another suggestion, though this might require some reworking of your > > > code, is that if you're logging in with your MCC and passing this > > > address in as the clientEmail header, you might want to try using the > > > clientCustomerId header instead: > > > > http://code.google.com/apis/adwords/docs/developer/index.html#adwords... > > > > But if you're not accessing this from your MCC but rather using their > > > email and password directly, that's not an option. > > > > Cheers, > > > -Jeff Posnick, AdWords API Team > > > > On Oct 28, 5:12 am, "[EMAIL PROTECTED]" > > > > <[EMAIL PROTECTED]> wrote: > > > > Yes, it sounds crazy but we actually have emails containing a colon > > > > that we use to login to AdWords. > > > > > Problem is the API always reject the request with error code 9. Do we > > > > need to do some form of escaping for email headers? We have never > > > > needed to escape colons in all our requests before, destinationUrls > > > > for example. > > > > > Please advise, thank you. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
