Hello Dorian,
Thank you for your feedback. I've logged it internally to include in our review. Currently we do not have any timeframe for ad param related changes but this service is definitely on our radar for upgrade in future versions. -Danial, AdWords API Team. On Wednesday, July 31, 2013 5:21:19 PM UTC+4, Dorian Kind wrote: > > Hi all, > > There are some previous threads about AdParams, but I'd thought I combine > some of the issues I've encountered when using this feature, which from my > point of view is a great mechanism for making your campaigns more dynamic, > but is quite difficult to work with. I'm also interested whether there is > actually a significant number of developers using AdParams. > > The main problems I have with the current implementation are the following: > > - No possibility to define AdParams on an AdGroupAd or even AdGroup > level. This makes updating AdParams a fairly slow process when you have > more than just a few keywords in an ad group. I still struggle to see the > use case for defining different AdParams on different keywords within the > same ad group. I believe that in a majority of cases, one rather wants to > define params for a specific ad, or even on the whole ad group. > - No support for AdParamOperations in MutateJobService. This fact, > together with the above item, means that an update of ad params for the > whole account (say a million keywords) takes a very long time and involves > significant overhead as all the calls are synchronous and no more than > approx. 1000 operations can be submitted at once before hitting > REQUEST_SIZE_LIMIT_EXCEEDED. > - No reporting whatsoever. This means that you will need either to > have local state or, like above, submit hundreds or thousands of calls to > AdParamService.get > - The allowed range of characters apart from numbers is limited. For > example, in some central European countries, an apostrophe or single quote > is used as thousands separator, while others use a space—yet only dot and > comma are legal in the insertion text. > > To me, the lack of reporting functionality is the most severe issue, as it > forces me to add DB logic to an otherwise stateless tool. But I am very > interested what others have to say. > > Thanks for any feedback and best regards, > Dorian > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 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 "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
