New 42-day free trial Get it now
Smarty

Unlock value in your address database with metadata

In this webinar, we briefly considered the value of breaking an address into its component parts to reveal hidden metadata.
Updated October 29, 2025
Tags
In this webinar, we briefly considered the value of breaking an address into its component parts to reveal hidden metadata.

Did you know that every address has loads of hidden data buried in its metadata? In this webinar, we briefly considered the value of breaking an address into its component parts. Then we looked at the different metadata available and provided definitions for each one. And finally, we went over use cases and ideas on how to leverage metadata for improved operations, business intelligence, and financial performance.

There’s gold in your address metadata!

Every address contains basic components that are standardized by country. In the US, the components are:

▢ Primary number

▢ Pre direction

▢ Street name

▢ Street suffix

▢ Post direction

▢ Secondary designator

▢ Secondary number

▢ City

▢ State

▢ ZIP Code

While each of these is valuable, there’s knowledge and data available that’s associated with every address. It’s THAT data—categorized as Root, Components, Metadata, and Analysis—that can bring a new life and a wealth of information to your address database.

What is address metadata?

Address metadata is simply information about an address. Smarty provides up to 55 points of metadata for every address.

Because there is a lot of metadata and the webinar promised to be a short one, we only went over 9 of the data points that are offered, as indicated with yellow arrows in the image below:

Address data points

Break down of the metadata

  • Root
    • Input ID - Your identifier to reference the input & output address
    • Input Index - The order in which an address was submitted with others
    • Delivery Point Barcode - 12-digit barcode; consists of 5-digit ZIP Code, 4-digit add-on code, 2-digit delivery point, and 1-digit check digit
  • Components - Details listed above
  • Metadata
    • Record Types - Indicating what type of building is at the address, ex: highrise, rural, street, etc.
    • Residential Delivery Indicator - Whether the building is zoned as residential or commercial
    • Geocodes - Latitude and longitude for each address
  • Analysis
    • Vacancy Indication - Whether the USPS registered the address as vacant or not.
    • Footnotes - The notes on what was done to obtain a match
    • DPV Footnotes - The quality of match for each address

Try it yourself

If you want to start getting this hidden treasure, along with crazy accurate address validation and rooftop geocoding, you can try it out yourself for FREE by visiting our Single Address Verification Tool.

Do you want to validate and get this data on more than one address at a time? Try our bulk address lookup tool, also for free, by signing up for a free account.

You can also view the full webinar recording here:

Subscribe to our blog!
Learn more about RSS feeds here.
Read our recent posts
Verification update: Add provisional addresses to Smarty’s database
Arrow Icon
With the launch of our latest product feature, US Provisional Address Manual Process, US Address Verification users can now submit new or missing addresses, and we’ll verify them against authoritative databases and add any approved records to our database. Better yet, you won’t need to make any integration changes to see your addresses in your API results, it won’t take longer than 30–60 days, and it won’t cost you anything extra. That’s what we call an all-around win!Let us take the stress of verifying new or missing addresses off your plate so you can focus on what you do best.
Functional options pattern in Go: Flexibility that won’t make future-you sigh loudly
Arrow Icon
SDK authors live in a permanent tug-of-war:Users want a simple constructor they can paste and ship. Maintainers want room to grow without breaking everybody’s build on the next release. That second part matters a lot right now, because a lot of people are still relatively early in their software careers. Approximately one in three developers has coded professionally for four years or less. That matters because unclear or fragile APIs disproportionately hurt newer developers—they don’t have scars yet.
Ambiguous address matches: What they are and why compliance teams should care
Arrow Icon
If you’ve ever run into an address that seems to exist in more than one place, congratulations—you’ve discovered the world of ambiguous address matches. They’re the Schrödinger’s cat of location data: valid, yet potentially two distinct locations. This blog will focus on a few key things: What are ambiguous address matches?Why ambiguous address matches matter for compliance and customer serviceHow to handle matches with address ambiguityWhy you should inform your customers of ambiguous address matchesOur final thoughts on ambiguous address matchesWhat are ambiguous address matches?An ambiguous address match occurs when an entered address resolves to two or more valid locations with slight but meaningful differences.

Ready to get started?