New 42-day free trial
Smarty

Pros and cons of the fuzzy address matching algorithm

Fuzzy address matching head image
John Hickey
John Hickey
 • 
January 17, 2023
Tags

Typos, typoes or typo's?

No matter how you spell the word, typos are a problem. Even the most accurate typist occasionally misspells a word, leaves off a letter at the end, or just types a different word than intended.

Typos in a text to your friend aren't a big deal. They'll figure out what you mean using context clues. But in a business data scenario, if you're following the logic of traditional address matching, where an address is either an exact match or not a match, you can't account for different formats or misspellings.

Exact address matching methods won't catch common mistakes like:

  • Spelling mistakes
  • Incorrect type (street vs. road)
  • Abbreviations
  • Synonyms: Floor vs. level -Unit, flat, or apartment
  • Swapped letters
  • Sounds like
  • Out-of-correct-order

However, fuzzy logic address matching excels at handling common address mistakes.

Fuzzy matching (also known as approximate string matching) is a technique that helps identify two elements of text, strings, or entries that are approximately similar but not 100% the same.

Traditional address-matching logic is binary. An address either matches exactly, or it doesn't.

Fuzzy logic indicates the degree to which a statement is true, and can help identify errors like the list above. However, there are nuances to fuzzy matching. Being "too fuzzy" creates matches for addresses that deserve to fail, resulting in false positives.

To avoid this, you can choose your tolerance level, or what degree of similarity you'll accept, from the fuzzy matching algorithm. For example, a provider can set a threshold of 0.8 and then test and adjust as needed. The goal is to ensure that minimal false positives get through, while still returning results and allowing for misspellings, errors, and varying formats.

Here at Smarty, we have a multi-stage process that attempts to find a match using a reliable matching engine. If it doesn't find a match, that address is next run through more aggressive matching processes. By only running failed addresses through additional stages, match rates increase with minimal risk of matching addresses that deserve to fail.

Download the 4 Steps to Unlocking Latent Revenue and Driving ROI with Your Address Data ebook

Pros of fuzzy address matching

Fuzzy logic offers several advantages compared to traditional address matching. Let's look at a few of them.

1. Determining the likelihood of a full match

Fuzzy matching predicts the likelihood of a full match. Depending on how high the probability of a match is, you can decide to consider those two addresses a match or adjust your tolerance settings. Your match probability scores are also a good indicator of your data quality.

2. Handling misspellings, formatting errors, and phonetic variations

People often spell addresses based on how the street name sounds. Traditional address matching won't catch that Fontainebleau Drive is the same street as Fountainblue Drive or Fontinblow Drive. Fuzzy logic is much better at handling misspellings and minor differences because it looks at how many characters are different.

Without the ability to easily pair up the same address, written in two different ways, it's harder to deduplicate address data and merge your records.

3. Distinguishing unique address information

You can program your exact matches to accept some small, common variances in standard formatting (i.e., street vs. st, road vs. Rd, etc.). However, that won't help with non-standard address information or street names. You can't sit there and program in ten different spellings of Fontainebleau! Fuzzy logic allows you to set rules for address standardization, correcting address information like street names to match with greater accuracy.

Cons of fuzzy address matching

Nobody's perfect, and neither are fuzzy matching algorithms. Depending on your tolerance level, you might not catch the craziest misspellings or wacky formatting errors. However, fuzzy address matching addresses many weaknesses demonstrated by traditional address matching.

Powered by fuzzy address matching, better match rates can increase your revenue by providing more usable address data and minimizing time spent on manual validation.

Want to know more about how accurate address data can help your business? Download our free ebook, 4 Steps to Unlocking Latent Revenue and Driving ROI with Your Address Data.

Download the free ebook today

Download the 4 Steps to Unlocking Latent Revenue and Driving ROI with Your Address Data ebook

Subscribe to our blog!
Learn more about RSS feeds here.
rss feed icon
Subscribe Now
Read our recent posts
Ecommerce shipping efficiency tools you need: Address autocomplete and verification
Arrow Icon
We know it’s not New Year's anymore, but we can still push for improvement and efficiency in our lives. Maybe you’ve lapsed on that goal to be healthier or slightly slipped on your new reading and writing regimen. No worries. Not only are we here to remind you to KEEP GOING on whatever goals you have, but we’re also here to give you an easy-to-implement solution that will create shipping efficiency and stop sending packages into the void. I mean, we’re assuming you don’t like wasting money. If you do… that’s how we’re different.
Patient form optimization: The $17.4 million problem
Arrow Icon
Let's start with a number that should make every hospital administrator do a double take: $17. 4 million. That’s how much the average hospital loses annually—just from denied claims due to patient misidentification. This isn’t from equipment costs, not from staffing shortages, and not even from insurance negotiations—just from keeping bad patient data. Surely, our forms aren’t that bad. (Yes, they are, and stop calling me Shirley. )But here’s the reality: According to the 2016 Ponemon Misidentification Report, 30% of hospital claims get denied, and over a third of those denials are caused by inaccurate or incomplete patient information.
The GPS adventures of a distracted developer
Arrow Icon
My name is Jeffrey Duncan, and at the pestering of Smarty’s editor, I’m writing a blog about the many adventures I’ve had in life and how address data has played a big part in them. I met my wife about eight years ago on a dating website. At the time, I lived in Provo, Utah, while she lived in Palmwoods, Australia, on the east coast of Queensland. On this dating app, I entered the area where I was interested in finding someone, about a 25-mile radius of Provo, Utah. I had no intention of leaving the valley, definitely not the state, and certainly not the country.

Ready to get started?