Ok, but what about the situation when the authenticated account is not an MCC, and in the selector, the client email of the authenticated non- MCC account is passed? Seems the service does not work in these cases. This is a problem because we need some way of obtaining the account ID of a non-MCC linked account, now that the reporting service won't allow using the email address as a header.
I have clients who have bought my reporting tool but don't have an MCC. They authenticate with their own non-MCC account. We normally use the ServicedAccountService to get the IDs, but in these cases it returns an account ID of -1. Kevin Winter from your team advised me to use the client email header in these cases to fetch the reports, which is what we've done. Now you're disallowing that header, and requiring that an account ID is provided instead. But is there any way to we get that ID for non-MCC linked accounts? On Nov 28, 9:56 pm, Eric Koleda <[email protected]> wrote: > Hi MT, > > That information is not outdated, and you can use an arbitrary MCC account. > However, the clientEmail you provide in the selector must exist somewhere > under the authenticated MCC or you will receive that error. > > Best, > - Eric Koleda, AdWords API Team -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [email protected] 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
