New 42 day free trial
Smarty

When to use strict vs enhanced matching in your address API

When to use strict vs enhanced matching in your address API
Andrew Townsend
Andrew Townsend
 • 
May 20, 2024
Tags

In our recent webinar, we invited Easton Gibson, one of our US Street API software engineers, to discuss key features of address validation and give insights into the functionalities of both strict and enhanced modes.

Understanding strict mode

Strict mode is precisely what it sounds like—it rigorously validates addresses against the official USPS database, ensuring that only fully accurate, postal-verified addresses are accepted. This mode is typically used for operations requiring high precision, such as legal or financial document dispatch.

For example, if you enter a known address into Smarty's address tools with strict mode, you'll see that it processes and standardizes address data, rejecting any entry that doesn't perfectly match USPS records.

However, while most people use strict mode for its reliability in confirming that an address is recognized by the USPS, its rigidity creates problems.

Introduction to enhanced mode

Enhanced mode is better than strict mode because it uses fuzzy logic, machine learning, and generally more information to provide a holistic story for each address. This mode is designed to capture and validate addresses that might not be part of the USPS database. These are known as non-postal addresses and include things such as newer developments or rural locations.

Enhanced mode’s ability to handle non-postal addresses is a significant benefit. For instance, it can identify and validate non-postal addresses and correct common address mistakes, giving you workable information instead of just an unknown result.

Enhanced mode provides everything strict mode will, but with more information about why an address does or doesn’t match. Instead of giving a “yes/no” response, it may give a “yes, if” response or “no, because.”

You can play with the enhanced mode results on the US Street API demo page.

FAQ for enhanced mode

What are the main sources for non-postal addresses in Smarty’s database?
The sources for non-postal addresses include several proprietary datasets that Smarty™ has access to, which are part of our "secret sauce." For detailed information, you can reach out to an account executive.

If I want results only from USPS addresses, should I use enhanced mode and filter out non-postal matches, or stick with strict mode?
Using enhanced mode is recommended even if you require only USPS addresses. Enhanced mode's aggressive matching strategy means it can handle typographical errors and other common discrepancies better than strict mode. Results that are non-postal will be clearly indicated, allowing easy filtering while still benefiting from enhanced mode's robust matching capabilities.

How does enhanced mode handle inputs with significant errors or typos, especially in critical components like the street name or number?
Enhanced mode is designed to be more forgiving of errors, including significant misspellings. It uses sophisticated algorithms to interpret and correct errors where possible, differentiating it from strict mode, which requires exact matches. However, there are limits; if an input is too far off from any real address data, even enhanced mode may not be able to make a correct match.

If you'd like to view the full webinar recording and the demos given, you can view that here:

 

Subscribe to our blog!
Learn more about RSS feeds here.
rss feed icon
Subscribe Now
Read our recent posts
Inside Smarty® - Irina O'hara
Arrow Icon
Irina O'Hara is one of our uniquely clever, expert frontend developers. She’s immensely talented and has had a vital impact on our website redesign. When it came time to spotlight her, Irina was a joy to sit down with and get to know a little better. To get to the basics, she writes code and creates awesome websites, and she’s darn good at both. BackgroundIrina was born and raised in St. Petersburg, Russia. However, she wasn't born a development expert and had other aspirations from the start.
How I reduced my returned mail from 27% to 1% using address autocomplete
Arrow Icon
The following is based on a true story. Some of the names and relationships have been changed to protect the anonymity of individuals and companies. However, the numbers are 100% accurate. In 2023, I wanted to mail some really fancy cards to 165 businesses. I collected their addresses by asking for them or finding them in their online listing and collected them all in a neat little row. Then, I went a step further and ran these addresses through Smarty's bulk address validation tool. Everything was set and perfect.
The ROI of accurate healthcare address validation: Stop hemorrhaging red on your financial statements
Arrow Icon
In healthcare, the havoc an inaccurate address can wreak on your financial results is significant in more ways than one, and the boost in overall profitability from maintaining a clean address database is equally worth noting. Accurate healthcare address validation improves operational efficiency, patient engagement, and compliance and builds revenue to heights that couldn’t be met without it. Here’s what we’ll be covering:Healthcare address validation pros and consCon: Increased claim denials and organizational costsPro: Reduced claim denials and reprocessing costsCon: Increasing patient match error ratesPro: Improved patient matching and data qualityCon: Complicated billing and collections processesPro: Streamlined billing and collections capabilitiesCon: Exposure to legal liabilitiesPro: Enhanced regulatory compliance and risk aversionCon: Misplaced market strategyPro: Data-driven decision-making and market insightsEpilogue: Avoiding the pain (see our summarized financial savings)Healthcare address validation pros and consThere’s a pro and a con associated with having (or not having 🫣) accurate address data in your healthcare systems.

Ready to get started?