Andrew is a leader, storyteller, photographer, marketer, indie film director, author, and father. Working in operations he smooths out and massages customer data as it moves between Marketing, Sales, Support, and Customer Success. Andrew has over 20 years of leadership and organizational management experience in both the workforce and his community. When he's dead and buried, his tombstone will read: HubSpot Expert.
All posts by Andrew Townsend - Marketing Operations
On average, customers of Smarty process 2. 5 billion addresses collectively a day. If you were to count a single Cheeto for each address, that’s enough Cheetos to fill up 1,930 vans per day. If you were to start walking along the equator of the Earth and you took one step for each address, you’d make 38 trips around the planet. That’s a ton of address lookups. So with that much address data flying through our systems, we decided to host a webinar sharing some of the insights we’ve gained from the over 440 billion addresses that were validated in 2022.
It seems that 1969 was a very special year. Looking back, you’ll find some of the coolest American muscle cars peaking in their infant stages, such as the Mustang Boss 429 Fastback and the Charger R/T 427 HEMI made famous by the Duke brothers. You’ll find the first Concorde flight in France. You’ll remember what you can of Woodstock, and one man will take a small step on the moon for all mankind. It’s also the debut year of the children’s educational show Sesame Street on PBS. Very quickly, the street named after a seed became nationally known, and the question children would sing at the top of their lungs each day was, “can you tell me how to get to Sesame Street?” Originally the show was called “123 Avenue B” to focus on the counting and alphabet principles that would be showcased.
You bet he does. He kinda has to, there’s no other way he can get rooftop-accurate geocoding fast enough. The man travels the entire world in 14 hours and needs to know exactly where to land his reindeer. Look, for a lot of people’s needs you could say that "parcel centroid" is good enough when it comes to address geocoding. Many houses are in fact in the center of the parcel. However, there are also many homes that are not in the center of the parcel. Parcel Centroid (Other Guys): Rooftop-Accurate (Smarty): For example, think of apartment buildings.
There are many problems you may run into if you're working with address data. In our recent webinar, our own Adam Charlton went over some of the challenges he's encountered the most, and how to deal with them. Here’s some of what he talked about. You can view the full recording at the link below. Standardization Standardizing addresses helps solve many of the problems inherent with data blending (combining two or more address databases together). In order to properly blend different address databases together you need to either have an external ID correlate the two sources, or have identically formatted address fields.
We brought out the big guns in the way of our Development Team Lead, Kent Gividen, in a webinar all about authenticating your APIs. He went over some of his most useful tips and tricks that he uses to ensure APIs are authenticated. Was it helpful? You betcha. You wanna get the SparkNotes? Read on. Common and Not-So-Common APIs to Know About Kent began by outlining the APIs that he has run into the most in his years as a developer. Some of them he dug into a little deeper than others, but these are all useful to be aware of.
Tis the season to know “it’s coming from inside the house” but you still stay in the house. It’s the time of year when teenagers are alone in their convertible at makeout peak while there’s a monster on the loose. The air is getting chilly, the leaves are falling, and people are moving into known haunted houses without a care in the world. So it just makes sense that we should look at some address data. There are some extremely famous addresses (or at least streets) in the “scary movie” genre.
With innumerable formats and unfamiliar spellings, standardizing and validating global address datasets can be a real pain. But it doesn't have to be. International Address Validation is an essential part of virtually every business that works with international address data. But how can you keep your address data in multiple countries accurate while not wasting your time and money? In our recent webinar, Jeffrey Duncan went over the details of international address validation. You can view the recording below, or continue reading for the quick recap.
There are two types of frequent errors: 401 "Authentication Required" errors, and 402 "Payment Required" errors. Status Code 401 - Authentication Required If you're seeing this error there's a chance that there's an issue with your API key, there's a mistake inside your client-side request, or a mistake in the server-side request. In the recording Lyle dives deep into each of these, but here are the basics. How to Authenticate API Requests It is important that you are familiar with your API keys.
Are you looking to use an API to verify addresses and convert them to latitude and longitude coordinates? Maybe you also need to standardize addresses in order to de-duplicate records across millions of addresses in your database too. That's right, we're talking about validating, standardizing, and bulk-processing geocodes with a geocoding API. There are several options out there, so let us tell you how *speed* sets Smarty apart from the rest. Smarty is fast. Now, we're not just talking about fast like Usain Bolt.
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.
In this webinar, our geocoding and address expert Adam Charlton went over the ins and outs of address data. He gave details about address components and how they influence the way an address is composed. He also dove into the difference between ZIP9 and ZIP11, what a non-postal is, and other address hacks you didn’t learn in primary school. Standardization and Validation What exactly is a valid address? There are lots of different definitions depending on what your goal is with the address.
Geocoding can unlock valuable business intelligence that is hiding in your address data. But how do you know what level of geocoding you would benefit from the most? Do you need rooftop data? Or maybe you just need parcel data? What about ZIP 9 geocodes? These are the questions Adam Charlton, one of Smarty's genius geocoding developers, set out to answer in his recent webinar. What Is Geocoding? Geocoding most typically means appending a latitude and longitude to a named location like an address.
Have you ever tried to add a minor feature to your application only to discover that you’ll have to re-write large blocks of code first? Or maybe you’ve spent hours deciphering hundreds, or perhaps thousands, of lines of existing code just to find out a task only required two lines of additional code. If you’re like most developers, you’ve wasted countless, frustrating hours wading through immensely complicated code trying to force it to do things it wasn’t built for. In his presentation, Mike Manwill, Frontend Team Lead here at Smarty, discussed 5 principles to help you create stupidly-simple applications that are maintainable, extendable, and bug-resistant.