Hi,

At the moment, you would have to get them from your SOAP logs. We have an open 
issue for improving the capture of request IDs in the library 
<https://github.com/googleads/googleads-java-lib/issues/4>.

Thanks,
Josh, AdWords API Team

On Tuesday, March 10, 2015 at 9:43:11 AM UTC-4, Dzmitry Zahusta wrote:
>
> Hi,
>
> I've already changed my logic to what you mentioned (set geoPoint together 
> with Address object). 
> but can you please clarify how I can get request IDs in Java code?
>
> вторник, 10 марта 2015 г., 16:10:33 UTC+3 пользователь Josh Radcliff 
> (AdWords API Team) написал:
>>
>> Hi,
>>
>> I've tried reproducing this behavior multiple times but in all cases the 
>> address you provided is accepted.
>>
>> One thing you may want to do is use GeoLocationService 
>> <https://developers.google.com/adwords/api/docs/reference/v201502/GeoLocationService>
>>  
>> to first validate your *address*. This will give you back a *GeoLocation* if 
>> the address is valid, whose geoPoint 
>> <https://developers.google.com/adwords/api/docs/reference/v201502/GeoLocationService.InvalidGeoLocation#geoPoint>
>>  
>> you can then use in your Proximity object 
>> <https://developers.google.com/adwords/api/docs/reference/v201502/CampaignCriterionService.Proximity#geoPoint>
>>  instead 
>> of the address. If the address is invalid, it will give you back an 
>> InvalidGeoLocation 
>> <https://developers.google.com/adwords/api/docs/reference/v201502/GeoLocationService.InvalidGeoLocation>
>>  
>> object.
>>
>> If you see this inconsistency again, please capture the request IDs of 
>> the failed requests and send them over.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Monday, March 9, 2015 at 11:38:25 AM UTC-4, Dzmitry Zahusta wrote:
>>>
>>> Yep, you are right but it's just typo in my example. In reality all is 
>>> set in a right way.
>>>
>>> понедельник, 9 марта 2015 г., 18:28:52 UTC+3 пользователь Josh Radcliff 
>>> (AdWords API Team) написал:
>>>>
>>>> Hi,
>>>>
>>>> I just noticed that in your code snippet, you are setting the 
>>>> *provinceName* to *US* and the *countryCode* to *Tennessee*, which is 
>>>> invalid. You should be setting the *provinceName* to *Tennessee* and 
>>>> the *countryCode* to *US*.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Friday, March 6, 2015 at 1:33:08 PM UTC-5, Dzmitry Zahusta wrote:
>>>>>
>>>>> Unfortunately I can provide only Ids of problematic campaigns:
>>>>>
>>>>> '276257069' ('US Georgia Warner Robins')
>>>>> '264091949' ('US California Hayward')
>>>>> '243337469' ('US Tennessee Alcoa')
>>>>>
>>>>> пятница, 6 марта 2015 г., 1:35:47 UTC+3 пользователь Josh Radcliff 
>>>>> (AdWords API Team) написал:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Do you happen to have request IDs from a response for a request that 
>>>>>> succeeded and a request that failed?
>>>>>>
>>>>>> Thanks,
>>>>>> Josh, AdWords API Team
>>>>>>
>>>>>> On Wednesday, March 4, 2015 at 1:57:47 AM UTC-5, Dzmitry Zahusta 
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi!
>>>>>>>
>>>>>>> While performing the following code INVALID_PROXIMITY_ADDRESS occurs 
>>>>>>> episodically
>>>>>>>
>>>>>>>         Address address = new Address();
>>>>>>>         address.setCityName("Johnson City");
>>>>>>>         address.setCountryCode("Tennessee");
>>>>>>>         address.setProvinceName("US");
>>>>>>>
>>>>>>>         Proximity proximity = new Proximity();
>>>>>>>         proximity.setAddress(address);
>>>>>>>         
>>>>>>> proximity.setRadiusDistanceUnits(ProximityDistanceUnits.MILES);
>>>>>>>         proximity.setRadiusInUnits(30.0);
>>>>>>>
>>>>>>>         CampaignCriterion campaignCriterion = new 
>>>>>>> CampaignCriterion();
>>>>>>>         campaignCriterion.setCampaignId(campaignId);
>>>>>>>         campaignCriterion.setCriterion(proximity);
>>>>>>>
>>>>>>>         CampaignCriterionOperation operation = new 
>>>>>>> CampaignCriterionOperation();
>>>>>>>         operation.setOperand(campaignCriterion);
>>>>>>>         operation.setOperator(Operator.ADD);
>>>>>>>
>>>>>>>         campaignCriterionService.mutate(new 
>>>>>>> CampaignCriterionOperation[] { operation });
>>>>>>>
>>>>>>> After repeating this code with no changes proximity is added with no 
>>>>>>> issue. The proper address data may vary. 
>>>>>>> What is going on? It does seem as bug on your side.
>>>>>>>
>>>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/33c2b123-3770-4a47-8a20-9f4e2565e1ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to