SmartSYNC supports Google Address Validation as an optional add-on within the address fields area. When enabled, addresses processed through SmartSYNC are validated and standardised using Google's Places API before being written to Raiser's Edge NXT.
This article explains how to enable the feature and answers common configuration questions.
Before enabling Google Address Validation, you will need a Google API key with the Places API enabled.
For instructions on obtaining a Google API key, see:
👉 SmartSYNC – Get a Google API key for Docs, Sheets, Places and other services
Note on cost: Google typically charges very little (or nothing) for address validation requests. The volume of requests is usually low enough to fall within Google's free tier, but you should check your expected usage against Google's current pricing.
Once connected, the option to use Google Verification will appear within the address fields area of SmartIMPORT flows and other areas of SmartSYNC.
Yes. Validation is configured at the address field level within each individual SmartIMPORT flow. You can choose which flows include the validation option and which do not.
Validation is triggered whenever an address is processed through SmartSYNC — it is not limited to new or changed addresses. Whether the address is then updated or added to Raiser's Edge NXT depends on the comparison SmartSYNC makes between the cleaned (validated) address and the existing RE NXT addresses for that constituent.
SmartSYNC writes the validated/standardised address back to RE NXT. If the address cannot be cleaned successfully, you can configure what happens — for example, add the address as-is, or skip adding it entirely.
There are no SmartTHING setup fees for enabling Google Address Validation. You will need to arrange a Google API key yourself (see Prerequisites above), and any Google usage charges are billed directly by Google.
Not at this time. SmartSYNC does not currently use the DPID or other RE NXT fields to determine whether an address has already been validated.
We are monitoring Blackbaud's development roadmap — additional field support in RE NXT is expected in the future, which may make this possible. We will update this article when that changes.
In most cases, no. The per-address cost through Google is very low, so re-processing addresses that haven't changed is generally not a concern from a cost perspective. Additionally, any supplementary data already stored against the address in RE NXT — such as a DPID — should remain untouched if SmartSYNC determines the address is unchanged.