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
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.