Hi again, to follow up on that, one additional advantage of having a tree as opposed to a list is in a situation where an account manager wants to select *all* accounts under a given manager account *except *for a small number of them. In a selectable tree that's easy: select the manager account—causing all accounts under it to be selected—and then unselect the ones that aren't required. In a list, this task is obviously much more difficult.
Thanks & best regards, Dorian On Tuesday, 12 April 2022 at 17:05:50 UTC+2 Dorian Kind wrote: > Hi Peter, > > thanks for your continued support. Happy to share our main use case, which > is account selection in internal web tools—we are a mid-sized agency and > currently manage about 800 Google Ads accounts distributed over around 100 > manager accounts in a hierarchy around 3 to 4 levels deep on average. > In order to select the proper Ads account on which to run a specific job > in such a tool (they're mostly of the housekeeping and quality assurance > type), we've experienced that it's easier for account managers to be able > to follow the hierarchy of manager accounts in a tree-like view down to the > desired account instead of selecting it from a rather large list directly. > In the Adwords API, implementing such a tree view is simple as it can be > done with a single call in the app's backend. While migrating one of our > tools to the Ads API, we discovered that we'd now have to do around a > hundred calls to get to the same result—which slows down the loading of the > tree view significantly, frustrating our users. > > I hope this gives some context for a feature request. Feel free to reach > out if you need more details. > > Best, > Dorian > > On Thursday, 31 March 2022 at 08:49:00 UTC+2 adsapi wrote: > >> Hi Dorian, >> >> Thank you for your reply. >> >> I understand the concern on the new implementation of the get account >> hierarchy feature. We also are currently not aware of any plans or >> direction that this current implementation would be undergoing changes. >> >> However, our team could create a feature request, subject for review, >> regarding your suggestion in making the implementation less complex. For >> our team to do so, could you share your complete use case as well as >> relevant details on why the change would be more suitable? >> >> Best regards, >> >> [image: Google Logo] >> Peter Laurence >> Google Ads API Team >> >> >> ref:_00D1U1174p._5004Q2Ys3MH:ref >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads 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 "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/d553b9c5-9dcc-4120-94a8-25db012c1b31n%40googlegroups.com.
