New 42-day free trial Get it now
Smarty

Improving address form completion rates—whether in a shopping cart, request for quote, or other form—can be a sinch if you’re using an address autocomplete tool. Not sure what that is? When you see an address line on a form and think “oh shoot this is going to take a minute” and then it fills it in after only a few keystrokes, that’s address autocomplete.

And no, not all address autocomplete tools are created equal.

Some check against their own address database only that is not frequently maintained. Some are only checked against the United States Postal Service database so they do not include non-postal addresses. And most do not have any sort of customization options when it comes to utilizing their APIs.

Smarty’s US Autocomplete Pro API checks against our incredibly large database of over 210+ million USPS addresses in addition to over 20 million non-postal addresses, and it is highly customizable.

Customizing for geolocation

One typical use for US Autocomplete is to assist an end user in entering their own address. In this case, you likely want to provide suggestions that are close to the user's location. The Geolocation feature, which is turned on by default, does just that. It uses data that maps the user's IP address to a city or surrounding area. It then places their city and state into the prefer_cities field.

Customizing for preferences

Another use for Autocomplete is for call centers where you may want to prefer suggestions that are in specific cities, states, or ZIP Codes. When set, these results will occupy the top percentage (prefer_ration) of the results.

Examples:

  • prefer_cities=SEATTLE, REDMOND,WA; RENO, NV
  • prefer_states=CO; OK
  • prefer_zip_codes=84660; 90210&prefer_geolocation=none

Customizing with include filters

Sometimes, you want to limit results to only specific cities, states, or ZIP Codes. This is different from preferences, which could provide suggestions outside your preference areas. Filters will only show suggestions that match the filter. Note that there are some keywords you can use for states that will filter on the 48 contiguous states (including DC), which exclude territories, Alaska and Hawaii. Or all states which exclude just the territories.

As with preferences, if you use the ZIP Code filter, you cannot use any other preference or filter.

Customizing with exclude filters

If you need to exclude specific states from your results, you can use this filter. It cannot be used with any other filter or the geolocation preference, but it works with other preference settings.

Customizing the source

US Autocomplete Pro has included non-postal addresses for a little over 6 months. Non-postal addresses are those that USPS won’t deliver to, but are valid physical addresses. By default, only postal addresses will be returned.

Set this to “all” if you also want to return non-postal addresses. You will know if a result is a non-postal address if it contains the source field with the value of “other.”

Customizing a selected secondary

This parameter gets it name from when a user selects an address to drill down on a particular secondary. This is the most complicated one of the options discussed in the webinar, but I’ll do my best to summarize.

If the address submitted is an apartment building with 100 units, this will dictate how many of those units there are and if the user can drill down to an exact unit. You can learn more about it in the recording below, beginning at 18:40.

View the webinar recording

This is just a brief overview of what was covered. You can view the full 26 minute video below.

Subscribe to our blog!
Learn more about RSS feeds here.
Read our recent posts
What to look for in an address data solution: Ease of implementation
Arrow Icon
You’ve maybe chosen an address data provider (or maybe you’ve just recently fallen out of love with the one you’ve got). Now comes the time to really test what matters: implementation. Even the best solution falls short if it’s hard to integrate, confusing to use, or impossible to maintain. This blog is part of our five-part series, What to look for in an address data solution. Previously, we discussed why human support teams should be top of mind when choosing an address data solution. Not just tech support, but educational materials, help getting started, and more.
What to look for in an address data solution: Quality of support
Arrow Icon
Selecting the right address data solution is only the beginning. Rolling it out successfully, resolving issues quickly, and keeping it performing at its best all depend on the quality of support behind it. This blog is part of our five-part series, What to look for in an address data solution. Previously, we discussed what it means to be accurate, what questions to ask any address data provider before entering into a contract with them, and how to avoid the accuracy “validation gap. ”Today, we’re focusing on an often-overlooked element: a supportive, accessible, and responsive partner.
What to look for in an address data solution: Data accuracy
Arrow Icon
Once you know what capabilities you need, the next challenge is choosing a provider that actually delivers—pun intended. This blog is part of our five-part series, What to look for in an address data solution. Previously, we discussed the need to find an address data solution that understands the importance of speed, scalability, and reliability, enabling you to maintain automated, efficient, and accurate workflows in any industry that deals with addresses. Today, we’ll focus on the hidden costs of inaccurate data, defining and combating the “validation gap”, and why it’s important in any industry.

Ready to get started?