free trial

Posted by DataSan

Salesforce Lightning does NOT validate addresses via Google

In the past week Salesforce has released their lightning update where we were greeted with a new layout and total makeover of the desktop version of Salesforce.

In their lightning release the focus is on creating drag and drop functionality for custom object and applications. Which is great news and a massive leap forward when it comes to technology and user experience.


One thing for us, as an ISV partner and our address validation app called DataSan is that this new lightning update now comes standard with a google search function for addresses.

Which is bad for everyone.. more on that later. 

We want to provide a short introduction on Google vs DataSan (valid addresses).
One of the fundamental reasons why we think businesses should adopt a data quality strategy, regardless of their business industry.

We understand that this might be achievable but we would like to show you an example below why Google does not deliver data quality.

Address Example: 240 Francis, St Lilyfield
(Which does not actually exist, but Google will tell you it does)


DataSan vs Google



DataSan vs Google 2


If  the non-existent “240 Francis Street, Lilyfield” is submitted, to Google Maps it will appear as a “valid” address, with a marker approximating where the address might be (in this case in the middle of an intersection).

Complete with picture.

DataSan vs Google 3

Google will even accept the non-existent “240 Francis Street, Sydney” and assign it to Bondi Beach.
Complete with picture.

Bizarrely, the 2 addresses suggested under “Did you mean” are also both non-existent.

DataSan vs Google 4



If  the non-existent “240 Francis Street, Lilyfield” is submitted, to DataSan the GNAF will  identify the street as “Francis St, Lilyfield” and assign it a geocode at the road centroid level only.

AMAS Postal Address Validation will fail as shown by “DPIP: N/A

DataSan vs Google 5


Now using this example with Salesforce Lightning

When navigating to your “leads” section within the new Salesforce Lightning environment you can see this screen pop up.

DataSan vs Google 6


Scrolling down you see the “Address Search” feature that has been introduced within Lightning.

DataSan vs Google 7


We again use the same example “240 Francis St, Lilyfield
(remember this does not exist)


DataSan vs Google 8


As you can see Google will find you an address that fits your need, regardless if it exists or if its validated. DataSan will validate not only the street but also the number, state and the actual spelling of the address which automatically corrects if the spelling is incorrect.

DataSan vs Google 9


Below is the address that you will stored within your CRM and that address will not exist. But your staff will think that is the case.

Imagine if you want to do a targeted mailing to some of the high level clients and invite them to an event.

You will be surprised when you not only get the amount of RSVP’s you expected but you will have to pay for the invites returned to you and resend them. Along with the resources to find the CORRECT address for each of your invites.

Risks using the Lightning Google Address lookup 

1) Address does not exist but you can still add this to your CRM

2) The input address does not actually get validated

3) The address number does not get validated

4) Data that is in your CRM CANNOT be trusted

5) Staff will view address data as accurate and validated while it is not.

Please contact us if you have any additional questions or would like to know more about Data Quality for your business. We can help your business with implementing the correct Data Quality process or help your with the address validation for your eCommerce business and online forms.

DataSan is available as a Salesforce App or Hosted Service

Share This
As of 21 February 2019, DataSan has been rebranded as Harmony RightAddress for SalesforceVisit Harmony RightAddress