RE: LocationCriterionService not working in Airflow

Hi Jayant, Thank you for reaching out to our API support team. You may note that our team can only provide support for AdWords / Google Ads API related concerns. Since you mentioned that the issue is being encountered when the API request is made through Airflow, then our API support team may

RE: LocationCriterionService usage python (awql // change response language)

Hi Maxim, Thank you for reaching out to our support team. You may refer below for my responses : 1) Can you provide an example how to query the LocationCriterionService with AWQL in python? I found this example on GitHub, but in general would like to stick to AWQL since it is more compact and

RE: LocationCriterionService

Hello, In order to use the LocationCriterionService, you will need to include predicates. If you don't you'll get the MISSING_PREDICATES error. Regards, Anthony Google Ads API Team ref:_00D1U1174p._5001UOE6kR:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our

RE: LocationCriterionService mapping to maps

Hi Pradeep, Thanks for reaching out to us. Unfortunately there is no link between Place ID and Location Criteria Id that you have underlined in the code example. Place ID can only be used across Places API. The Location Criteria Id that you is the Parent ID of the location, California. For a

RE: LocationCriterionService return INVALID_PREDICATE_OPERATOR error

Hello Zeid, For the LocationCriterionService, ONLY and IN operators are currently supported. I have raised a feature request to the team. Please keep an eye on our blog for more updates. Thanks, Bharani, AdWords API Team

Re: LocationCriterionService return INVALID_PREDICATE_OPERATOR error

Hi Bharani, > > As I know their is now label in the location entity, so how can I filter by label using ContainAny? The idea is to reproduce the dropdown location component bellow, when user start typing the location name, I give him location suggestion by calling LocationCriterionService.

RE: LocationCriterionService return INVALID_PREDICATE_OPERATOR error

Hello Zeid, The CONTAINS_* is only supported for Labels. Please check this thread for a discussion on the same topic. Thanks, Bharani, AdWords API Team

Re: LocationCriterionService, location name is not fully translated in RU locale, why?

Pada tanggal Kam, 8 Nov 2018 14.24, 'Vincent Racaza (AdWords API Team)' via AdWords API and Google Ads API Forum menulis: > Hi, > > My apologies as I can not comment on if they utilize different databases > or back-end configurations. However, I have already created a feature > request for this

Re: LocationCriterionService, location name is not fully translated in RU locale, why?

Hi, My apologies as I can not comment on if they utilize different databases or back-end configurations. However, I have already created a feature request for this to further check this behavior. I will inform you once there are updates. Best regards, Vincent AdWords API Team On Thursday,

Re: LocationCriterionService, location name is not fully translated in RU locale, why?

Hi. Example shown above is just one of many-many others. The main question is: why keyword planner ( https://ads.google.com/aw/keywordplanner/home ) shows correctly translated region, but API not? Keyword planner uses another "database", or? Thanks. On Wednesday, November 7, 2018 at 2:55:04

Re: LocationCriterionService, location name is not fully translated in RU locale, why?

Hi, We were able to replicate the scenario. With this, I have created a request to update that particular location to its Russian equivalent. However, it is not a guarantee that this will be updated. You may follow our blog for

Re: LocationCriterionService returning empty results

Hello, It looks like these Criterion IDs are not available in the Geo targets table. It is currently not possible to map these location IDs to the exact location through the AdWords API. It is possible that these IDs correspond to the restricted regions or the DMA regions. If its DMA region,

Re: LocationCriterionService Returns empty results for a locationID recieved from CampaignLocationTargetReport

Hi, I couldn't find the location IDs you provided in the Geographical Targeting table which probably is the reason why you're getting an empty response from the LocationCriterionService.get()

Re: LocationCriterionService does not return Country Code

Hello Armin, In fact, *CountryCode* is not selectable, so even if you specify that in the *Selector*, it will not be returned. (If a field can be selected, it will be explained explicitly in a reference page. For example, you can see countryCode

Re: LocationCriterionService does not return Country Code

Hello Armin, Thanks for reporting. I'll check with the engineering team and get back to you when having any updates. Best, Thanet, AdWords API Team On Friday, June 17, 2016 at 2:05:00 AM UTC+9, armin.lai...@netekspert.com wrote: > > It appears that the field name "CountryCode" is valid, but

Re: LocationCriterionService doesn't return country codes

All right, good to hear that. It's weird because the Locations file (csv) provided by Google does contain Country Codes. So it's confusing why these values are not returned by the service. thanks, Armin On Thursday, June 16, 2016 at 9:36:37 PM UTC+3, Anthony Madrigal wrote: > > Hello Armin,

Re: LocationCriterionService doesn't return country codes

Hello Armin, I saw that you posted this question on a new thread . I will take a look at it and respond to you there as soon as I can. Regards, Anthony AdWords API Team -- --

Re: LocationCriterionService doesn't return country codes

I'm struggling with the same issue.. What is the right field name then? "CountryCode" seems to be accepted, but the service does not return any value. Thanks for a hint. On Thursday, November 1, 2012 at 2:54:50 AM UTC+2, Ian Knox wrote: > > It's handy but currently the country code

Re: LocationCriterionService doesn't return country codes

As with version v201603 "CountryCode" seems to be a valid field, nevertheless it does not return any value. Please help! thanks, Armin On Friday, November 2, 2012 at 1:58:42 PM UTC+2, Danial Klimkin wrote: > > Hello Ian, > > > 'CountryCode' is not a valid selector field according to the

Re: LocationCriterionService returns incorrect values for CanonicalName field

Hi, I'm looking into this and will post an update as soon as I have more information. Thanks, Josh, AdWords API Team On Monday, July 28, 2014 4:54:31 AM UTC-4, Dzmitry Zahusta wrote: Hi! I'm trying to get location names using the following code: Selector selector = new

Re: LocationCriterionService returns wrong reach parameter

Hi, We've made some improvements to *LocationCriterionService* and it now returns a reach of 1,160,000 for location ID 1019250. Cheers, Josh, AdWords API Team On Sunday, January 5, 2014 7:08:26 AM UTC-5, Ittai Chorev wrote: Great, Thanks! We haven't found any other discrepancies between the

Re: LocationCriterionService returns wrong reach parameter

Great, Thanks! We haven't found any other discrepancies between the UI and API - I'll let you know if we do. On Friday, January 3, 2014 6:30:08 PM UTC+2, Josh Radcliff (AdWords API Team) wrote: Hi, I have confirmed the behavior you described. We're aware of this and looking into it on

Re: LocationCriterionService returns wrong reach parameter

Hi, I have confirmed the behavior you described. We're aware of this and looking into it on our side, and I'll post an update once I have more information. If you have any other locations where you see a *Reach* of zero, please pass those along so I can investigate those as well. Cheers,

Re: LocationCriterionService sometime not work properly

Hello nguyen khac tu, Please send us full XML code of the response and the server reply. Make sure to remove all sensitive data such as AuthToken and DeveloperToken. -Danial, AdWords API Team. On Saturday, June 30, 2012 2:28:12 PM UTC+4, nguyen khac tu wrote: hi all i want to estimate

Re: LocationCriterionService returns incomplete data in ParentLocations

Hi Kevin, Could you post the question on the Product forum in that case? Since the frontend and API pull data from same source, the issue should get fixed if it is addressed in the front end. The product forum url is https://www.en.adwords-community.com/t5/AdWords-Community/ct-p/AdWords

Re: LocationCriterionService returns incomplete data in ParentLocations

Hi Kevin, How does the AdWords front end report this location? Cheers, Anash P. Oommen, AdWords API Advisor. On Friday, 8 June 2012 00:27:59 UTC+5:30, Kevin wrote: Hi, For country of Spain, a city can belong to province, and a province is part of an autonomous community. For example:

Re: LocationCriterionService returns incomplete data in ParentLocations

Hi Anash, The front end is doing the same. -Kevin On Tue, Jun 26, 2012 at 3:13 AM, Anash P. Oommen anash.p.oommen+fo...@google.com wrote: Hi Kevin, How does the AdWords front end report this location? Cheers, Anash P. Oommen, AdWords API Advisor. On Friday, 8 June 2012 00:27:59

Re: LocationCriterionService returns incomplete data in ParentLocations

Hi, Any plan to address this issue? -Kevin On Thursday, June 7, 2012 11:57:59 AM UTC-7, Kevin wrote: Hi, For country of Spain, a city can belong to province, and a province is part of an autonomous community. For example: Barcelona is in Province of Barcelona, Autonomous Community of

Re: LocationCriterionService Selector returns bogus values

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

Re: LocationCriterionService Selector returns bogus values

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

Re: LocationCriterionService Selector returns bogus values

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

Re: LocationCriterionService Selector returns bogus values

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

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

Re: LocationCriterionService Selector returns bogus values

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: requestId0004bb5e111358380a0c0b28547d/requestId The body of my request is: get

Re: LocationCriterionService returning bad results?

Hi Brian, The LocationCriterionService tries to find good matches for the search term provided, but like the UI it may return some erroneous results from time to time. Best, - Eric Koleda, AdWords API Team -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and

Re: LocationCriterionService returning bad results?

Hi Brian. Till you're waiting answer from Google team try to remove: ParentLocations, Reach May be problem located in strings comparing on API side. So Reach is determines not as Euro Countries association, but like one of locations in Tennessee state in United States. Regards, Evgeniy. On 7

Re: LocationCriterionService only supports 'EQUALS' and 'IN' Predicates

Hi All, That's correct, the production environment has the same behavior. Best, - Eric Koleda, AdWords API Team -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api

Re: LocationCriterionService only supports 'EQUALS' and 'IN' Predicates

A little odd, but if I use 'EQUALS' or 'IN', it is giving me approximate matched records as well. My question is whether this is the desired behavior or if it only happens in Sandbox? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group:

Re: LocationCriterionService only supports 'EQUALS' and 'IN' Predicates

I am pretty sure IN matches approximate matched records in production as well. On Dec 20, 12:52 am, Stephen Yeargin stephen.year...@gmail.com wrote: A little odd, but if I use 'EQUALS' or 'IN', it is giving me approximate matched records as well. My question is whether this is the desired

Re: LocationCriterionService uses a different DateRange object

Hi, In this case, because the LocationCriterionService doesn't make use of the DateRange fields, this shouldn't in practice actually get sent to the API. Depending on how your framework serializes objects, you should be able to use the regular generic selector structure for this service.