CriterionError. INVALID_PROXIMITY_ADDRESS

[Mathew Westlake-Toms]

Since a few days ago, I am getting INVALID_PROXIMITY_ADDRESS when attempting to target an address (proximity). Attempting to add the address via the adwords interface works as expected, just the API returns this error.

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201802" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Header><ns1:RequestHeader><ns1:clientCustomerId>....</ns1:clientCustomerId><ns1:developerToken>REDACTED</ns1:developerToken><ns1:userAgent>... (AwApi-PHP, googleads-php-lib/33.1.0, PHP/7.2.3-1+ubuntu16.04.1+deb.sury.org+1)</ns1:userAgent><ns1:validateOnly>false</ns1:validateOnly><ns1:partialFailure>false</ns1:partialFailure></ns1:RequestHeader></SOAP-ENV:Header><SOAP-ENV:Body><ns1:mutate><ns1:operations><ns1:operator>ADD</ns1:operator><ns1:operand><ns1:campaignId>328732167</ns1:campaignId><ns1:criterion xsi:type="ns1:Proximity"><ns1:radiusDistanceUnits>MILES</ns1:radiusDistanceUnits><ns1:radiusInUnits>3</ns1:radiusInUnits><ns1:address><ns1:postalCode>SW1A0AA</ns1:postalCode><ns1:countryCode>GB</ns1:countryCode></ns1:address></ns1:criterion></ns1:operand></ns1:operations></ns1:mutate></SOAP-ENV:Body></SOAP-ENV:Envelope>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201802"><requestId>00056bd611ebd9a00a37b1457f076171</requestId><serviceName>CampaignCriterionService</serviceName><methodName>mutate</methodName><operations>1</operations><responseTime>364</responseTime></ResponseHeader></soap:Header><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>[CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[0].operand.criterion.address]</faultstring><detail><ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201802"><message>[CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[0].operand.criterion.address]</message><ApplicationException.Type>ApiException</ApplicationException.Type><errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CriterionError"><fieldPath>operations[0].operand.criterion.address</fieldPath><fieldPathElements><field>operations</field><index>0</index></fieldPathElements><fieldPathElements><field>operand</field></fieldPathElements><fieldPathElements><field>criterion</field></fieldPathElements><fieldPathElements><field>address</field></fieldPathElements><trigger></trigger><errorString>CriterionError.INVALID_PROXIMITY_ADDRESS</errorString><ApiError.Type>CriterionError</ApiError.Type><reason>INVALID_PROXIMITY_ADDRESS</reason></errors></ApiExceptionFault></detail></soap:Fault></soap:Body></soap:Envelope>

Thanks

[Bharani Cherukuri (AdWords API Team)]

Hi Mathew,

Thank you for sharing the logs. This is known issue and our team is actively investigating the issue. As a workaround you could add Address along with GeoPoint as the Proximity criteria or you could use the AdWords UI to add location criterion. I will keep you posted if I have any new updates to share. 

Regards,

Bharani, AdWords API Team

[Bharani Cherukuri (AdWords API Team)]

Hello, 

This issue has been resolved. Can you retry the API request again and see if you're having any trouble? 

Thanks,

Bharani, AdWords API Team