#Address Verification Errors0 debatiendo

We recently switched our NPSP org to Google Geocoding for address verification from the Cicero NPSP connector (RIP). It has mostly worked as expected, but I noticed that we've received a handful of

"REQUEST_DENIED: indicates that your request was denied." errors since we switched over a week ago (see below):All of the addresses that were rejected include the # (number symbol/pound sign) character, which is a pretty common shorthand for unit/apt number. I tested and confirmed that removing the # character fixes the issue.

Has anyone else come across this issue? If yes, what workarounds/solutions were used? #NPSP #Address Verification Errors #Google #Cicero

I'm experiencing a bug with Google Address Verification where it strips out the entire first line. In on example today, the original address was something like  764 Cambridge, Charlottesville, VA 12345. When I submitted it for verification in that format, it stripped the first line. Next, I tried 764 Cambridge St, Charlottesville VA 12345. In that case, it corrected St to Ave and left the rest of the line alone.

@Robin Gardiner and I seem to be having related issues. From her earlier post, "I seem to be having a similar issue where the entire street address(number and street name) gets stripped, regardless of whether there is an apartment number attached (of course I am ensuring that a comma is present before the apt number)--I'm seeing a trend that it happens when there is a "NW" or "SE" in the street address (a la Washington, DC or Seattle, WA addresses, but to be fair we are based in DC so we have A LOT of these) but it's not a hard and fast rule--I just literally can't find any other similarities among the ones it's messing up."

@Salesforce.org System Administrators #Address Verification Errors #Address Verification  #Google Geocoding 

cc: @Chris Pifer