Identify Records Not Geocoding

There are a number of reasons why the Google API may not be able to identify coordinates for an address, even if you've created a Map Object and processed the Geocoder. The first step in fixing these records is to identify the ones that need fixing. This is easy to do with a simple report filter.

In this example, we'll be looking for Accounts that have not been geocoded, but you can apply this technique to any object type. 

1. To get a quick idea of how many records are missing from the Map, run a report of All Accounts and compare the record count to an unfiltered Everywhere search of Accounts. 
We can quickly see that our report has 5,129 records and the map only shows 5,055. 

Now lets identify which 74 records are missing. 

If the Map Object uses off-record geocoding, continue to Step 2.
If the Map Object uses on-record geocoding, continue to Step 3.

2. (Off-Record Geocoding)
Edit the Accounts report. In the Fields column under Account: Custom Info, drag the Geocode field to your report.
Click Add, then add the Geocode filter. Adjust the filter to show Geocode equals (blank).

3. (On-Record Geocoding)
Edit the Accounts report. In the Fields column under Account: Custom Info, drag the Geocode Quality field to your report.
Click Add, then add the Geocode Quality filter. Set the filter logic to show Geocode Quality equals (blank)

4. Save your report. We chose to Save As and rename it as "Accounts Not Geocoded."

Common reasons why records may not geocode include validation rules, lack of address information, or because the address information is stored in the wrong fields indicated for that Map Object. Check out the links below to learn more. 

Learn More

Data Quality and Geocoding
Records Not Geocoded Due to Validation Rules
Map Objects
The Geocoder