Hi ZZ, It looks like you may have identified a few issues with our docs.
1) For locations, you can download the CSV on our Geographical Targeting page <https://developers.google.com/adwords/api/docs/appendix/geotargeting>, save it locally, and use it as a lookup table. If you want to use LocationCriterionService instead, based on some tests I just ran it appears that the statement about LocationCriterionService <https://developers.google.com/adwords/api/docs/guides/location-targeting#lookup-regions> requiring exact name matches is no longer true. You might want to try this yourself by passing various location names in the predicate to see what gets returned. 2 ) The docs look outdated here as well. I confirmed that you can use GeoLocationService <https://developers.google.com/adwords/api/docs/reference/v201402/GeoLocationService> and pass it an Address <https://developers.google.com/adwords/api/docs/reference/v201402/GeoLocationService.Address> with only the *postalCode* specified and it will return you a GeoLocation for that postal code. You can then use the GeoLocation's GeoPoint to construct your CampaignCriterionService.Proximity <https://developers.google.com/adwords/api/docs/reference/v201402/CampaignCriterionService.Proximity> object. I'll look into the documentation issues and update the docs accordingly. Thanks for bringing this to my attention! Cheers, Josh, AdWords API Team On Wednesday, June 18, 2014 2:51:35 PM UTC-4, ZekeZ wrote: > > Josh, > > This is not particularly straight forward. Couple of obvious questions: > > 1) It appears location id is required, but per the documentation, and > exact name match must be passed in. This would seem to be problematic > unless I can get a complete list of all of the location names to make sure > a valid name is passed in. Is that possible? > 2) What about an id for a proximity (zip plus radius)? How would it be > possible to derive that? > > > Thanks, > ZZ > > On Wednesday, April 16, 2014 6:22:03 PM UTC-4, Josh Radcliff (AdWords API > Team) wrote: > >> Hi ZekeZ, >> >> How are you attempting to do step 4 in your list? You can remove >> CampaignCriterion objects by passing a collection of >> CampaignCriterionOperations to CampaignCriterionService.mutate with operand >> = the CampaignCriterion and operator = REMOVE. I just confirmed this with >> one of my test accounts. >> >> Similarly, for step #5 you could add the new Locations and Proximities >> via CampaignCriterionOperations with operator = ADD, as shown in the >> AddCampaignTargetingCriteria >> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/java/adwords/axis/v201402/targeting/AddCampaignTargetingCriteria.java> >> example >> in each client library's v201402/targeting examples folder. You may also >> want to check out the GetCampaignTargetingCriteria >> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/java/adwords/axis/v201402/targeting/GetCampaignTargetingCriteria.java> >> example >> in the same folder, as it demonstrates how to select CampaignCriterion >> objects by criterion type. >> >> Cheers, >> Josh, AdWords API Team >> >> On Monday, April 14, 2014 11:25:39 AM UTC-4, ZekeZ wrote: >>> >>> Trying to dynamically GeoTarget our campaigns based on the locations of >>> our accounts. Currently using v201306, but will move to another version if >>> appropriate. >>> >>> Here's the scenario: >>> >>> 1) Read account information from internal customers database table - >>> successful >>> 2) Access Adwords API and retrieve all existing campaigns - successfully >>> doing that now using the CampaignService and CampaignCriterionService >>> 3) Retrieve all existing Locations and Proximities - successfully doing >>> that now using CampaignCriterionService >>> 4) Remove all existing existing Locations and Proximities - no luck >>> 5) Dynamically repopulate the Locations and Proximities based on current >>> internal customer data - no luck >>> >>> Has anyone successfully performed this scenario. >>> >>> Any advice / suggestions would be greatly appreciated. >>> >>> ZekeZ >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/d/optout.
