Hello Ryan, Yes, if you'd rather experiment using the web interface that should give a good indication as to what the results would be via the AdWords API. Just be sure that you're including the same options and using the equivalent report type--there are some report types that are only available via the web interface, and the Structure report type is only available via the AdWords API.
Cheers, -Jeff Posnick, AdWords API Team On Sep 17, 9:53 pm, Ryan H <[EMAIL PROTECTED]> wrote: > Jeff - > > Thanks for the thorough answer. Would running the report from my > adwords interface give me a good sense of whether or not running the > report from the API would be sucessful? > > Thanks, > Ryan > > On Sep 17, 10:11 am, AdWords API Advisor > > <[EMAIL PROTECTED]> wrote: > > Hello Ryan, > > > There are no hard limits on the account level. However, the reports > > center backend will have trouble running reports based on the number > > of rows that would be returned. Factors like the date range, the > > number of elements in each account, and obviously the number of > > subaccounts can all affect the number of rows that will be returned. > > If you exceed the capacity that the reports backend can currently > > support, you'll either get a failure at the time the report is > > scheduled or the report will process for a while and then go into a > > Failed status. Zero-impression Keyword reports are especially > > heavyweight, so you might find that you can request a smaller amount > > of data for those types of reports than others. > > > What I'd recommend you do is to first try running your report with > > crossClient set to true and without specifying anything for the > > clientEmails value in your DefinedReportJob. This will result in a > > cross-client report scheduled for all the sub-accounts under your MCC. > > If that completes successfully in a reasonable amount of time then you > > should be good to go in the future with that method. > > > If your report fails then you'll want to do one of two things: either > > break your report into X smaller reports, and list 1/X of the sub- > > accounts in each DefinedReportJob's clientEmails attribute. > > Alternatively, you could fundamentally change your AdWords account > > structure and move form the one MCC->many AdWords account topology to > > something like one MCC (with your tokens)->a few sub MCCs->many > > AdWords accounts. Then you can schedule cross-client reports in each > > sub-MCC without having to specify the client emails that you're > > interested in. The other advantage of changing your account structure > > like that would be that each sub-MCC would have its own separate > > Reports Center that could retain the last 15 reports, rather > > scheduling X number of reports that all go into a single MCC's Reports > > Center. > > > Changing your AdWords account structure, especially when there are > > many sub-accounts, can be fairly time consuming. If you have a > > relationship with an AdWords account representative already you might > > want to engage him/her for assistance if you decide to go that path. > > > Cheers, > > -Jeff Posnick, AdWords API Team > > > On Sep 16, 8:20 pm, Ryan H <[EMAIL PROTECTED]> wrote: > > > > I have an MCC account with many (many) accounts underneath. I need to > > > do reporting across accounts. > > > > Is there a limit to the number of accounts that can be combined into a > > > single scheduled report job? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
