Re: LocationCriterionService Selector returns bogus values

2012-04-05 Thread Eric Koleda
Hi Aaron, The CSV I linked you to is new, and is up-to-date as of two weeks ago. We plan to update this CSV much more frequently than the older ones. We apologize for the mixed message thus far regarding looking up location criteria IDs. Best, - Eric On Tuesday, April 3, 2012 1:56:47 PM UTC

Re: LocationCriterionService Selector returns bogus values

2012-04-03 Thread Aaron Sherman
Thanks again for taking the time to reply. With respect to using the CSV; this is where I had to go, but the problem is that in separate queries about the data in the CSVs being out of date, we've been told that if we want more current information we should use the location service. You see the

Re: LocationCriterionService Selector returns bogus values

2012-04-03 Thread Eric Koleda
Hi Aaron, No, unfortunately it's not possible to change the results returned by that service. If you want to perform a more strict lookup you may want to download the CSV and query that dataset locally: https://developers.google.com/adwords/api/docs/appendix/geotargeting Best, - Eric On Mond

Re: LocationCriterionService Selector returns bogus values

2012-04-02 Thread Aaron Sherman
On Monday, April 2, 2012 4:27:32 PM UTC-4, Eric Koleda wrote: > > Hi Aaron, > > The short answer is that the LocationCriterionService returns suggested > locations given your input, and those suggestions may occasionally include > some seemingly off-topic results. For the input "Abbeville, Ala

Re: LocationCriterionService Selector returns bogus values

2012-04-02 Thread Eric Koleda
Hi Aaron, The short answer is that the LocationCriterionService returns suggested locations given your input, and those suggestions may occasionally include some seemingly off-topic results. For the input "Abbeville, Alabama" I wasn't able to get the behavior you're seeing, so it may have been

Re: LocationCriterionService Selector returns bogus values

2012-03-16 Thread Aaron Sherman
On Friday, March 16, 2012 5:22:31 AM UTC-4, Anash P. Oommen wrote: > > > Could you please post the sanitized xml or the request id for this request? > >> >> Anash, this is the request ID in the response headers: 0004bb5e111358380a0c0b28547d The body of my request is: https://adwords.goo

Re: LocationCriterionService Selector returns bogus values

2012-03-16 Thread Anash P. Oommen
Hi Aaron, Could you please post the sanitized xml or the request id for this request? Cheers, Anash P. Oommen, AdWords API Advisor. On Friday, 16 March 2012 02:32:48 UTC+5:30, Aaron Sherman wrote: > > When requesting LocationCriterionService entries, I use the following > Predicate in my Select

LocationCriterionService Selector returns bogus values

2012-03-15 Thread Aaron Sherman
When requesting LocationCriterionService entries, I use the following Predicate in my Selector: field: LocationName operator: EQUALS values: [ 'Abbeville, Alabama' ] and I get a result which includes: 'id': '1012927', 'locationName': 'Abbeville', 'pa