Thanks for the explanation. I understand you have some valid reasons for making the change. Still, wouldn't it be quite simple to also make the city/country IDs available as report fields, instead of just the string values?
On Dec 30 2011, 7:10 pm, Evgeniy Bogdanov <bogda...@tagan.ru> wrote: > Mikael. > > I'm agree with you that this method gives us as API's users some > problems. > But as you can see - API is growing and evaluating. > > As a developer i think that new behavior is good idea. > And I'll try you to explain why. > > You know that searching in database by integer works faster than by > strings. > I think that developers meet with problem of load: count of API users > is growing, load of servers too. > > And they started to think about possible ways to reduce load. One of > the ways were: > 1. Use IDs for location strings > 2. Block users which create a big load (a lot of activity), without > any needs for Google Advertise Network (it's main idea - sell > advertise). > > So they have moved to pointing Location IDs as integers. > > Showing location as strings in report I think is good as you can show > it to user > directly without any changes (calculations, lookup data) in data. > > This is my thoughts. > Your idea is good, but not good enough for all API developers. > > Regards, > Evgeniy. > > On 30 дек, 16:28, MT <mikael.thuneb...@gmail.com> wrote: > > > > > > > > > Hi Evgeniy, > > > The problem is that it unnecessarily adds complexity when for some > > fields, the filter value passed by the user can't be used as such, but > > needs to be passed through another service first to change it to an > > ID. It doesn't seem like very good design when the same field has two > > different datatypes depending on whether it it's selected as a field > > in the report or used as a filter. > > > If the ID needs to be used in the filters, then why can't it also be > > available as a field in the reports? That would at least make it a bit > > simpler, as we could then instruct the user to use a city ID when they > > wish to filter by city (but much better still would of course be to > > simply filter using the city name string, like in the Analytics API). > > > On Dec 30, 12:44 pm, Evgeniy Bogdanov <bogda...@tagan.ru> wrote: > > > > Hi Mikael. > > > > I do not understand your problem. If you have string - you can get ID > > > and vice versa, what is wrong? > > > > You're trying to compare different APIs. > > > GA API have many good things, but this is generally other API for > > > other platform. > > > And this 'other platform' makes such differences. > > > > Regards, > > > Evgeniy. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
