CriterionError.INVALID_PROXIMITY_ADDRESS

43 views
Skip to first unread message

rentca...@gmail.com

unread,
May 9, 2018, 3:16:43 PM5/9/18
to AdWords API and Google Ads API Forum
I've been able to set location targeting with Proximity objects on Campaigns using the AdWords API but now I receive error: CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[0].operand.criterion.address. Below are two soap requests that return the error.

POST /api/adwords/cm/v201802/CampaignCriterionService VsDebuggerCausalityData: uIDPozZgBJ7il0NGldp05Pld12EAAAAAcrWcR4J8sk+Jzlx0EYeZRK1v4tzDrSNPp4pZNNDA8t8ACQAA Authorization: REDACTED Accept-Encoding: gzip, deflate TimeStamp: Wed, 09 May 2018 11:52:12 GMT <?xml version="1.0" encoding="utf-16"?> <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> <RequestHeader xmlns="https://adwords.google.com/api/adwords/cm/v201802"> <clientCustomerId>Removed for security</clientCustomerId> <developerToken>REDACTED</developerToken> <userAgent>RentCafe Site Manager (AwApi-DotNet/23.3.0, Common-Dotnet/9.1.0, .NET CLR/4.0.30319.42000, , gzip)</userAgent> </RequestHeader> </s:Header> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <mutate xmlns="https://adwords.google.com/api/adwords/cm/v201802"> <operations> <operator>ADD</operator> <operand> <campaignId>1396746409</campaignId> <criterion xsi:type="Location"> <id>1026650</id> </criterion> </operand> </operations> <operations> <operator>ADD</operator> <operand> <campaignId>1396746409</campaignId> <criterion xsi:type="Proximity"> <radiusDistanceUnits>MILES</radiusDistanceUnits> <radiusInUnits>15</radiusInUnits> <address> <cityName>New Boston</cityName> <provinceName>TX</provinceName> <postalCode>75570</postalCode> <countryCode>US</countryCode> </address> </criterion> </operand> </operations> <operations> <operator>ADD</operator> <operand> <campaignId>1396746409</campaignId> <criterion xsi:type="Language"> <id>1000</id> </criterion> </operand> </operations> </mutate> </s:Body> </s:Envelope>

---------------------------------------------------
POST /api/adwords/cm/v201802/CampaignCriterionService Authorization: REDACTED Accept-Encoding: gzip, deflate TimeStamp: Wed, 09 May 2018 12:05:35 GMT <?xml version="1.0" encoding="utf-16"?> <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> <RequestHeader xmlns="https://adwords.google.com/api/adwords/cm/v201802"> <clientCustomerId>Removed for security</clientCustomerId> <developerToken>REDACTED</developerToken> <userAgent>RentCafe Site Manager (AwApi-DotNet/23.3.0, Common-Dotnet/9.1.0, .NET CLR/4.0.30319.42000, , gzip)</userAgent> </RequestHeader> </s:Header> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <mutate xmlns="https://adwords.google.com/api/adwords/cm/v201802"> <operations> <operator>ADD</operator> <operand> <campaignId>1396753615</campaignId> <criterion xsi:type="Location"> <id>1026481</id> </criterion> </operand> </operations> <operations> <operator>ADD</operator> <operand> <campaignId>1396753615</campaignId> <criterion xsi:type="Proximity"> <radiusDistanceUnits>MILES</radiusDistanceUnits> <radiusInUnits>15</radiusInUnits> <address> <cityName>Houston</cityName> <provinceName>TX</provinceName> <postalCode>77019</postalCode> <countryCode>US</countryCode> </address> </criterion> </operand> </operations> <operations> <operator>ADD</operator> <operand> <campaignId>1396753615</campaignId> <criterion xsi:type="Language"> <id>1000</id> </criterion> </operand> </operations> </mutate> </s:Body> </s:Envelope>


KDJ

Peter Oliquino (AdWords API Team)

unread,
May 9, 2018, 11:29:34 PM5/9/18
to AdWords API and Google Ads API Forum
Hi,

Our team is currently actively investigating an issue related to yours. Let me get back to you once I receive information that the issue has been resolved.

Best regards,
Peter
AdWords API Team

Peter Oliquino (AdWords API Team)

unread,
May 23, 2018, 11:41:48 PM5/23/18
to AdWords API and Google Ads API Forum
Hi,

We've received information that this issue has now been resolved. You may now retry your requests for setting your Proximity criterion. Let me know if all goes well.
Reply all
Reply to author
Forward
0 new messages