Address Problem Identification and Solutioning

Address Issues

• Overwriting addresses (billing address)
• Google Maps vs Smarty Streets (US only)
• Google Maps API
• Comma required and other characters ("Ste" or "Apt" stripped off unless there is a comma)
• Oddities with Bulk verification entries resulting in duplicate addresses
• Clean-up of existing address data for entry into Google MAPS
• Google MAPS acts as a validation for new addresses - and existing which required a bulk load of existing addresses
• There appear to be multiple Google address validation apps under Settings and Google MAPS is not the Google app lists, hence different APIs

Commonalities

• Standardized addresses
• Domestic vs International
• Incomplete addresses
• Duplicate addresses

Address validation tools:

• Cicero
• Smarty Streets
• Google MAPS

Solutions - Standardized Addresses:

• Picklists - get buy-in on what’s important (different picks for int’l)
• Validations - place on form
• Storing data elsewhere and doing exception report to clean up data
• US vs Int’l - are there formulas that existing in HUB

Google doesn’t does bulk load - not an option. Smarty Sheets does.

Simple solution for apps that link to Salesforce but are unable to perform mass uploads: have NPSP place a note under Settings that mass loads are only available under Smarty Streets and unavailable under Google MAPS or Cicero.

https://www.smartystreets.com/articles/address-apis

Key Questions for standardizations:

• How you use addresses
• Needs for addresses such as voting district
• County information
• Source of data
• Who manages data