Our DOTS Address Detective service is an address-based service looking to help clients clean up the most challenging of addresses. It works well as a secondary check to our DOTS Address Validation – US service, but is also capable of performing the same duties and can be used as a standalone service.

Address Detective is a utility service intended to house operations outside of the scope of normal address validation that can help in a number of different ways. This article will take a detailed look into its operations.

We will explore the three main operations of Address Detective:

• The FindAddress operation uses extra datasets to link names and phone numbers to a very messy address to solve problems such as a missing house number.
• FindAddressLines is a helper operation that can assist in cases where the user might not know what pieces of information they have, or perhaps these pieces are out of order.
• Finally, FindOutlyingAddresses is an operation that aggregates alternative datasets to identify good addresses that are not within the USPS dataset.

First, however, let’s look at an address validation capability that serves as the foundation for Address Detective: the GetBestMatches operation of our DOTS Address Validation service.

Address Validation – The GetBestMatches Operation

It is impossible to talk about Address Detective without a brief dive into our Address Validation service. At its core, Address Detective builds off of our industry leading GetBestMatches operation, which uses a USPS CASS certified engine to validate, standardize, correct and append informational data points to US based addresses. Its response contains a corrected and/or standardized address consisting of Address, City, State and Zip that can be saved to a CRM or database, or set up for a piece of mail.

This response also contains several other outputs. One is a list of address fragments containing the various parts of the address, in case a user needs to know a specific part of the address – for example, whether it is an apartment number or the name of the street that is available. DPV and DPV Notes contain interesting information about the address from things like the deliverability of the address to if it is vacant, returning mail or is a business or residence. Corrections indicate anything that might have changed in the address from the input to the response, such as a city change, zip code change or street suffix change. A full list of possible outputs and descriptions can be found in the Operations section of our Developer Guide, under GetBestMatch.

GetBestMatches does have some ability to fix messy addresses. Some of these changes happen within the CASS engine and some outside of it. In the case of an address that has been changed outside of the CASS engine, there is a flag called IsCass that will be set to false to indicate this. Small changes are accepted by us, and these normally find their way into the next iteration of the CASS engine.

The most important thing for the Address Validation service, however, is that any address returned – whether CASS validated or not – is 100% accurate. So, rigorous testing is always done on all sides, and more likely than not drastic or dangerous inconsistencies will cause an address to fail validation. In addition, the dataset is still strictly linked to the USPS dataset.

These are the reasons that Address Detective exists. The operations below will explain how Address Detective can go beyond the capabilities of Address Validation.

Address Detective – FindAddress

FindAddress is the primary operation in Address Detective. With a reasonably clean USPS known address, it functions identically to GetBestMatches, returning a response object so similar that it is essentially interchangeable with that service. This makes it easy for clients to potentially build in a failover and call FindAddress using almost exactly the same procedure they used with the GetBestMatches operation.

Where this helps are cases where the address is either too different from the actual address or perhaps even incomplete. FindAddress has more leeway to make changes than GetBestMatches, but it also uses potential personal names, business names and/or phone numbers to cross-check against alternate datasets to make more drastic changes.

Take this address for example:

Taco Bell

821 N Milpas St

Santa Barbara, CA 93103

That will validate normally but if you only had something like:

Milpas Street

Santa Barbara, CA 93103

You would not be able to properly validate this address alone in an address validation service. However, by using extra pieces of information such as Taco Bell or (805) 962-1114 and cross-checking these against other datasets, we are able to identify that 821 N Milpas is a good candidate. In this case, FindAddress is able to move forward and successfully correct and validate the address and return that similar response as if the clean 821 N Milpas Street address had been given in the first place.

In some cases, even messier addresses will continue to be fixable. For example:

Milpaaas Str

Santa Bar

CF 93103 

This very ‘messy’ address could still be validated using the extra data points. The MatchRate score provided gives some indication of risk for addresses that need to be drastically changed, and this last example would have a lower MatchRate than the previous one.

FindAddress will continue to evolve with newer algorithms and datasets. Currently, it still tries to take a very messy address and find a clean USPS valid address from that. In the future, it should also be able to validate addresses outside of the USPS dataset as FindOutlyingAddresses does (more on that later).

Address Detective – FindAddressLines

FindAddressLines is a good operation to use if you are not sure which address components are which. There are a number of common examples, like data sloppily collected, stored incorrectly in a database, or perhaps corrupted when transfering from one system to another, to name a few. Address portions can be combined into one field or split up into their own. Instead of the normal Address, City, State, Zip Code paradigm, FineAddressLines allows for up to 10 generic address lines where data can be randomly added. The operation will analyze the components and identify the best candidates for a valid address.

For example, if you had:

Line1: Service Objects

Line2: C/O John Doe

Line3: Floor 5

Line4: 27 E Cota St

Line5: Ste 500

Line6: Santa Barbara

Line7: CA

Line8: 93101

It would correctly identify, validate and return a normal response for:

27 E Cota St STE 500

Santa Barbara, CA 93101

The response looks very similar to that returned by both FindAddress and GetBestMatches. If you were to reverse those lines, the operation still IDs the correct final address and returns a good final result:

Line1: 93101

Line2: CA

Line3: Santa Barbara

Line4: STE 500

Line5: 27 E Cota St

Line6: Floor 5

Line7: C/O John Doe

Line8: Service Objects

The operation will start to error out as data elements that cannot be properly identified are added. For example, if 123 Fake Street were added into the mix ahead of 27 E Cota St, it would identify as a candidate for a street address and cause a failure because it is not. At this point, the given data is deemed too dangerous to try and find a good result for.

That said, this operation solves a problem that is not uncommon for our users. It is not uncommon for databases or CRMs to get populated with bad data points, especially if a service such as Address Validation was not used on the front end to initially clean and parse the addresses. Extra pieces of information like C/O John Doe and 5th Floor that are not important to the validation of the address can actually confuse things if they are stored with the address. Trying to deal with these data points without the help of Address Validation can easily lead to a corruption of data.

Address Detective – FindOutlyingAddresses

FindOutlyingAddresses has the same basic core purpose as the first two operations: find and validate the given address. However, it has a very different response from the previous two operations. The addresses it serves are addresses that are not found in the USPS dataset. They are pulled from datasets aggregated from many different data sources.

Throughout the United States are pockets of areas that do not receive direct mail, such as extremely rural farm houses that would not be cost effective for the USPS to service, or even towns like Summerland and Avalon in California that are General Delivery areas. Mail goes to a central post office instead of being delivered to a door. This means that USPS does not need to service them and may not track their addresses.

Other companies like FedEx and UPS may still do deliveries to these locations, so it is important to know if they are good. It may also be important for non-shipping reasons to know if a location is likely to be good: for example, a fraudster may make up an address to get past a website checkpoint, or a valid user might be blocked because they are in a location that is more unknown. In either case, knowing more about the locations helps identify both potential cases.

FindOutlyingAddresses helps to solve these problems by dipping into datasets outside the USPS to identify these challenging locations. The data is not as complete nor necessarily as authoritative as USPS data, so the response is a best attempt validation and standardization of the given address. Address, City, State and Postal Code are returned. Level indicates how close we were able to get to the desired address.

The possibilities for a Level response are:

• USPS
• Premise
• PremiseInterpolated
• Street
• PostalCode
• City
• State
• NotFound

This is one of the most important parts of the operation, as it gives some insight into the likelihood that the address exists. USPS or Premise indicate that the actual address was found in the primary dataset or at least identified as good in one of the aggregated datasets. PremiseInterpolated suggests we did not find the address but know other addresses around that one are good. Street means we have identified the street as existing, and so on.

This kind of response provides obvious value even if the true address cannot be identified. Notes and InformationComponents allow extra information to be returned about the address, however, these are mostly future expansion fields at the moment. Two possible InformationComponents are CountyName and CountyFIPS to return some county information about the address.

This operation has the best direct synergy with our Address Validation service, as it can be a direct call after a failed address call. It does not need new pieces of information and it is not a result of corrupted starting data.

Hopefully, this blog gives a deeper understanding of the operations currently available in DOTS Address Detective. We look forward to continuing to enhance its capabilities to solve even more challenging address problems, as well as adding new operations to solve problems still to be identified.

Please contact us if you want to learn more about the service.

With the holidays fast approaching, your customers will soon be shopping online and breaking last year’s sales records. They will be counting on your business to make sure all of their packages are delivered on-time to their correct addresses. Adding to the holiday stress, there are even some Scrooges out there that will try to commit fraud.

To help ease some of your stress during this season, Service Objects is sharing one of Santa’s secret tools: Address Validation. Like Santa, you can enjoy the benefits of verifying and correcting addresses, ensuring accurate and timely delivery, while helping weed out fraudsters and malicious actors.

Simply visit our Santa’s Delivery Secret, powered by our Address Validation tools, to try it out.

If you have never used a real-time address validation service before – or even if you have – this is a quick and fun way to check up to 10 addresses.  If you are more like Santa and have a large number of addresses to check, we are here to help.  Either way, you can get started by looking up one address at a time, including business names, as shown here:

Once you enter a business or personal delivery address – anywhere in the world that reindeers fly – Santa’s helpers will be right back with a validated address, showing corrections where needed, ensuring happy deliveries.

If you have a larger database of addresses you want to validate and verify, Santa is giving you 500 free transactions when you sign up to test any of our real-time Address Validation APIs.

We’re hoping that once you get a taste of some holiday address verification – and understand how simple it is to implement for your business – you’ll want to have these capabilities for your business, all year round.

Have questions or want to learn more? Contact us and we’ll do our best to make it a happy holiday season for you too!

Once upon a time, mail was delivered to residences, workplaces, or a Post Office (PO) box that are provided by the United States Postal Service. More recently, there is also a third option: private mail boxes or PMBs, which are provided by commercial mail receiving agencies (CMRAs) like The UPS Store, FedEx Kinkos, and other independent providers.

PMBs are a convenient alternative to PO Boxes for many people, but they also can have implications for people shipping to them. Let’s look at some of the differences between these two options, and how you can know what kind of address you are sending to.

Comparing PO Boxes and PMBs

Some of the main differences between PO Boxes and PMBs:

• USPS Post Office boxes have a “PO Box” address, while PMBs may have a street address. The latter are often desirable for consumers, particularly small businesses, who wish to have a business “address” while keeping their home address private. This is normally the business address of the PMB provider, often with an additional “suite” or “PMB” number identifying the recipient.
• Post office boxes are only for USPS mail, packages or parcels. As a result, delivery services such as UPS and FedEx normally cannot deliver to PO Boxes, with rare exceptions.  Conversely, PMBs can accept deliveries from all carriers, including the USPS.
• Similarly, post offices are unable to sign for mail delivered to a PO Box.
• PMB providers frequently offer additional services, included or at an extra cost, such as packing, shipping and forwarding. Some even serve as virtual offices where customers can rent an office or conference room as needed to meet with clients.
• PMB staff can alert you when you have mail or packages waiting.

Private mail boxes are a growing industry, with projected 2019 US revenues of over $2 billion and roughly 20,000 people employed in this sector. In particular, they have become a favorite of small businesses and independent professionals who need inbound and outbound mailing services.

When you need to know the difference

Now, let’s switch gears and look at this from the sender’s standpoint. The difference between a PO Box and a PMB can be huge when it comes to the delivery of products – because, as we mentioned previously, the former often cannot receive or sign for packages. It may also be important to know whether you are delivering to an actual residence or business versus a PMB for certain shipments: for example, time-critical deliveries such as refrigerated products. There are also cases where the actual recipient or an authorized agent must sign for a delivery, such as the USPS’ Certified Mail with Restricted Delivery option.

PO Boxes are easily identified by their address – they normally take the form “PO Box XXXX,” often with a ZIP+4 code tied to the specific PO Box number. PMBs, however, often use a regular street address. But with the aid of a little automation, you can determine these addresses as well.

How we can help

Our flagship DOTS Address Validation – US product has the ability to flag both PO Box and PMB addresses. It can also determine whether an address is a so-called commercial mail receiving agency (CMRA), whether or not it contains a specific PMB number. As a bonus, Address Validation also validates and corrects the addresses in your database, ensuring greater accuracy in determining the address type.

This data and more gets returned as part of Address Validation’s built-in Delivery Point Validation feature, which verifies the deliverability of an address against up-to-date USPS data. A quick look at our developer guide will show how we return this data as part of a DPV Notes code, with specific codes for a PO Box, a PMB that matches a CMRA, or a CMRA with no PMB specified. In addition, DPV Notes can flag addresses such as Rural Route, General Delivery, Military APO/FPO addresses and much more.

The bottom line? The growth of private mail boxes means that you can no longer tell by observation whether the street address you are shipping to is potentially a PMB or not. But if you need to know, for more accurate shipping with fewer problems, the tools to determine this are bundled right inside our regular address validation capabilities.

The United States Postal Service (USPS) has an acronym for almost everything and this leads to some pretty interesting conversations around the Service Objects’ water cooler. You might overhear our Director of Engineering saying, “I was surprised to see the RDI was ‘residential’ but SLK still returned a suite number” or “I was really happy to see their UAA rate drop below 1% with our validation service.”

Yes – we are address-validation geeks and we want to talk with everyone about it. So we put together this short primer on USPS acronyms, what they mean and why they are important. For us, it starts with being CASS-certified.

Coding Accuracy Support System (CASS)

CASS stands for the Coding Accuracy Support System (CASS). It was developed by the United States Postal Service as a certification process designed to improve accuracy in the mailing industry by helping developers improve and maintain their address validation software.

CASS evaluates and measures the accuracy of address matching software in the following areas:

• 5-digit ZIP coding
• ZIP+4 coding
• Carrier route coding
• Delivery Point Validation (DPV) 
• Residential Delivery Indicator (RDI)
• Locatable Address Conversion System (LACS)
• SuiteLink (SLK)
• Enhanced Line of Travel (eLOT)

To achieve CASS-certification, the software must pass a two-stage test and achieve a score of 98.5% or better in matching accuracy.

The Two Stages of CASS Testing:

Stage I is a self-administered and generally used to help developers test and diagnose their address matching software against a provided list of 150,000 test addresses. This is generally used to measure and see where your software can be improved before moving on to Stage II.

Stage II uses a test file supplied by the USPS with 150,000 static addresses that present more difficult use cases for correction and address matching. The results are graded by the USPS’ CASS department and certification is granted on accuracy scores above 98.5%. The USPS charges a fee for the certification process.

We are proud to say that our DOTS Address Validation – US service has achieved a score of over 99% for the past 10 years.

But don’t stop at CASS. If you really want to catch our attention, pull out some of these key terms and facts at the next Service Objects holiday party:

Zone Improvement Plan (ZIP) and ZIP+4

Although ZIP code might seem pretty ubiquitous with addresses now, you might be surprised to learn that it has only been around since 1963. The ZIP+4, which added 4 additional digits after the ZIP code for even greater address accuracy, has only been in place since 1983.  Our address validation service ensures accurate ZIP+4 coding, and when combined with carrier route coding, results in significant postal discounts and stronger delivery rates.

Do you know what each number in your ZIP code represents?

Want to bring some obscure ZIP code facts to the party, check out “Fun Facts About ZIP Codes“.  (Good luck getting the ZIP code song out of your head!)

Delivery Point Validation (DPV)

DPV is a product provided by the USPS that determines whether an address with a ZIP+4 currently exists within the USPS’ delivery dataset. Said another way, it determines if an address exists and can receive delivery from the USPS. It is one of the core elements when seeking CASS-certification.

Residential Delivery Indicator (RDI)

RDI is another product provided by the USPS and indicates if an address is classified as ‘business’ or ‘residential’. This was specifically designed for shipping packages or parcels and allows for more accurate and cost-efficient shipping practices, especially to businesses. 

SuiteLink (SLK)

This USPS product enables customers to improve their business addressing information by appending known suite information to a business address. This is used to help better sort and improve delivery ‘sequencing’, especially in high-rises and office buildings, which results in less expensive postal costs. This product cannot be used as a standalone process and must be included in CASS processing (and is part of our Address Validation – US service).

LACSLink (LACS)

The USPS offers the Locatable Address Conversion System (LACS) product to convert rural-style addresses to city-style addresses. This is especially important for the delivery of emergency services and primarily arose from the implementation of the 911 system. The information has also benefited mailers, as it can be used to derive more accurate and deliverable addresses from rural addresses, reducing duplicate and undeliverable mail and packages. 

Enhanced Line of Travel (eLOT)

The USPS eLOT product allows mailers to sort their mailings in carrier-casing sequences. For those who do not speak USPS-ese, eLOT contains a number, which indicates the first occurrence of a delivery made within a mail carrier route, which can be used to presort your mailings. The more presorting you can do, the better your mailing rate discounts.

Commercial Mail Receiving Agency (CMRA) 

CMRAs are private businesses that accept mail from the USPS (and other delivery services) on behalf of recipients. There are both larger ones you may have heard of like, The UPS Store and FedEx Kinkos, and many, smaller, independent businesses that provide the same services. 

CMRA’s offer ‘private mailboxes’ (PMB), not to be confused with post office boxes (PO boxes), which are provided by the United States Postal Service. PMBs can also accept deliveries from non-USPS, commercial delivery services like UPS, FedEx and DHL. Our address validation service can help identify when these types of boxes are being used.

Undeliverable-as-Addressed (UAA) Mail

UAA mail is our mortal enemy and where it all got started for Service Objects!

UAA mail is all mail that cannot be delivered to the name and address as specified on the mailpiece. UAA mail must be either, forwarded, returned to sender or properly treated as waste. UAA results in substantial costs to businesses, the USPS (which ultimately get passed on to consumers), the environment, and customer satisfaction.

Although there are a number of reasons that mail may be Undeliverable-as-Addressed, over 86% of it is correctable. Our services can improve and correct insufficient address details and even help identify a vacant premise/lot.

Change-of-Address (COA)

Which naturally bring us to the last acronym of the day, COA. Besides validating and correcting bad addresses, detecting and replacing a change-of-address is one of the best ways to prevent the dreaded UAA designation. The USPS provides NCOALink, their change of address dataset, that tracks approximately 160 million permanent change-of-address records for both residential and businesses. Our DOTS NCOA Live service is a simple-to-implement API that provides secure access to this data, so you can keep your addresses up-to-date, ensuring your mail reaches your intended target, without delay.

We Speak the ABCs of Address Validation

Our flagship address validation services bring together all of the above USPS products, combines them with our proprietary AI, additional datasets and expertise, to create a simple-to-integrate API that corrects, standardizes and verifies US addresses.  We also have services for Canada and International addresses.

Want to try on your new-found address validation vocabulary or have questions about one of our services? Drop us a note or give us a call, we would love to chat!

If you have ever run into a unique ZIP code while doing address lookups or validation, then there is a good chance that they may have caused some confusing results for you. Take the following address as an example:

123 Not a Real Street
Schenectady NY, 12345

To most users, this address looks like it is fake. But if you send it to an address checker like DOTS Address Validation – US, to be validated and standardized, then you will get a response like the following.

Our service indicates that this is a valid mailing address. So what gives? This might lead one to believe that something went wrong in the address checker or validation engine. But there is a perfectly reasonable explanation for cases like this. If we take a look at the DPV Notes returned by our service, we will see Code 3, which indicates that the ZIP code provided is a unique ZIP code.

What are unique ZIP codes?

In short, unique ZIP codes are high volume mail receivers that receive mail at one location and then distribute the mail internally. Unique ZIP codes generally are used by large organizations, government buildings, universities or large medical facilities. For these cases, the USPS would drop off all the mail at one single location, and then the mail recipients would distribute it to the necessary parties internally. Since all that mail is distributed internally, the USPS and our services by extension will mark every address with a unique ZIP code as valid and deliverable.

How should we handle unique ZIP codes?

Great question! These are cases that would certainly require some type of additional logic to process. If you have a user submitted form, perhaps you could process this by asking the user to double check the postal code entered. This could help ensure that the unique ZIP code was not entered by mistake.

If you are cleaning up a database and find a number of unique ZIP codes in your data, this might be a case where you would want to contact the owner or operating organization of the ZIP code to ensure that the addresses obtained are valid.

Each use case is different. If you want some assistance or suggestions on how to best handle unique ZIP codes for your case, reach out to us at support@serviceobjects.com. We’re always happy to make recommendations and help customers get the most out of their data.

Conclusion

Understanding unique ZIP codes before you encounter them can be key to preventing any hiccups that may occur when using Address Validation – US and address checking in a production environment. Preparation and knowing different scenarios like this are key.

We strongly recommend reviewing our developer’s guide and all the possible DPV Note codes that the service can return. If you have any questions, don’t hesitate to ask us; we’re always ready to help educate our customers to be their own data experts.

In case you were wondering, the ZIP code 12345 belongs to the world headquarters for General Electric.

We recently revamped our developer guides to make them more user-friendly. The information for each service has been broken into its component parts, to make each feature more comprehensible. In this article, we share some of the changes we have made and they help you get the most from our products.

1. A new, easy-to-navigate landing page

Our new landing pages now have a developer guide map (our US Address Validation product is a good example) to provide easy access to each web service’s component parts. By clicking on the links on this page, you will be taken directly to the respective page that provides a more in-depth breakdown of the service’s individual fields. Below is an example of one of these landing pages.

2. Quick lookup & Open API

Our quick lookup page has been greatly simplified to provide only the most relevant data at your fingertips. Once you have received a trial or production license key, the validation process is as simple as plugging your input data into the fields, adding your license key, and clicking Execute. The web service request is made for you and the response formatted in the output section.

Similarly, if you are looking to run a different operation the Service Reference page has quick lookups for every operation within its respective service.  Check out an example of Address Validation US.

3. Citations and Additional Field Information

Have questions about the service fields? Need more information about how to leverage them to fit your business needs? Our redesign now includes accordion panels that can be expanded to provide more information about the field. We’ve also added citations next to some of the inputs and outputs where we have additional information available. In the example, below the Barcode Digits is linked to the following blog:

https://www.serviceobjects.com/blog/address-deduplication-using-usps-barcodes/

By clicking a reference link, you can read a more in-depth analysis of the field and often gain ideas about how to use the data point in your workflow.

Each of these new features is designed to help you get up and running more quickly with our services, and serve as an easy-to-use reference for your development work. Try out our new developer guide soon, and let us know what you think!

Some terms sound similar but aren’t actually interchangeable – like sympathy versus empathy or good versus well. In the data quality business, two similar phrases with totally separate meanings are Address Validation service versus Address Verification service (AVS) – and these have very important distinctions if you process credit cards. However, when used together, they can solve common credit card processing issues and increase sales, decrease fraud and provide better customer experiences. Let’s look at the differences between these two capabilities and how they can be used together.

Address Validation service vs. Address Verification service (AVS)

First of all, an Address Validation service ensures that your address is correct and deliverable – and often corrects addresses when necessary. An Address Verification service (AVS), by comparison, is supplied by credit card companies for fraud prevention. It is part of the credit card authorization process, ensuring that components of an address correspond to a specified credit card number the issuing company has on file.

A good example of Address Validation is our flagship DOTS Address Validation – US service (along with its Northern counterpart, DOTS Address Validation – Canada). As for credit card transactions, there are varying but very similar versions of Address Verification Service (AVS) created by most major credit card issuers in the US and other countries to use with their authorization process. Here are some key differences in the way these two systems work:

Address Validation – US is a CASS Certified^TM service that links directly with up-to-date USPS address data, together with other authoritative data sources, to verify – and if necessary, correct – a supplied delivery address. Address Validation – US also goes far beyond simple street address checking, including Delivery Point Validation (DPV) to make sure an address is deliverable, verifying suite numbers, and flagging residential versus business addresses.

AVS, by comparison, checks an address against the one on file with the issuer of the credit card being authorized. As this article describes in detail, AVS only compares the numerical portion of a street address and the ZIP code against a credit card provider’s records. It then either approves the address or returns one of several error codes, outlined in this Wikipedia summary.

When to use Address Validation and AVS

So, should you use Address Validation or AVS for credit card transactions? The answer is that both are very important, depending on your situation. Here’s why:

• Using AVS with unvalidated addresses can lead to false negatives that decline legitimate sales and lose business. Validating an address before submitting to AVS can help prevent false-negatives.
• AVS doesn’t guarantee deliverability – so a misspelled street or city name could still leave your package lost at the wrong address or loading dock, causing financial losses as well as possible brand damage from unhappy customers. Address Validation checks and corrects for deliverability.

The best of both worlds

With thoughtful business logic, you can harness the strengths of Address Validation to correct addresses BEFORE submitting them for authorization, decreasing the number of false negatives.  This increases sales and provides confidence in declined authorization attempts. In addition, incorporating contact-data-hygiene best practices that ensure the address provided is accurate and deliverable reduces the cost of mis-shipped products and increases customer satisfaction.

Managing credit card transactions

It is important to understand that there are multiple approaches to managing your credit card transactions, including both automated tools and human approval procedures (we devoted an entire article to this recently), including our own BIN validation capabilities for checking credit card types and validity. Every strategy has its pros and cons, and there is always a balance between preventing fraud and chasing away valid sales and customers.

Need to take a deeper dive into credit card processing and data quality? Contact our knowledgeable product experts anytime, and we’ll be happy to discuss your own situation in more detail.

We have many mission-critical applications for our products. But every year in May, one of the most critical ones is keeping moms happy on Mother’s Day. After all, customer satisfaction is important in any industry, but no one EVER wants to disappoint their mom on her special day.

Do you know how many flowers are sent every year on Mother’s Day? A lot! This ‘very technical’ answer comes from my first-hand experience as a teenager.  When I was young, my girlfriend’s parents owned a floral shop, and Mother’s Day was the biggest day of their year.  It took us all week to prepare orders and plan deliveries.

A more precise answer comes from the Society of American Florists: one article notes that Mother’s Day flower sales were nearly $2 billion US in 2016, edging out Valentine’s Day by volume and representing 64 percent of all gifts to mom that day.

What you might not know is that Service Objects plays a major role in the logistics of Mother’s Day. Delivering perishable floral products on a specific date, with little margin for error, is a complex challenge requiring bulletproof data quality. We serve many important customers within the floriculture and floral industry and wanted to share some of our tools they use to help make moms smile all over the US.

How We Power the Flowers

Here are some of the key tools our customers use to help ensure a successful Mother’s Day:

Address Validation. Integrating our DOTS Address Validation – US product within your order entry process makes sure that the Mom’s address is correctly captured at the time of ordering. This is particularly important for a holiday like Mother’s Day, where addresses are not generally being entered by the recipient and are more prone to error.

Our Address Validation service matches and, where possible, corrects addresses in real time at the point of data entry, using up-to-date USPS and proprietary databases. Our USPS CASS-Certified^TM database engine also flags residential versus business addresses and returns a full ZIP+4 postal code.

Delivery Point Validation (DPV). This feature is part of the output from Address Validation, and it is critically important when a third party enters the address: Delivery Point Validation ensures that an address is not only correct but also recognized as being deliverable by the USPS. A simple example is knowing that a unit number is required for a multi-unit building and flagging the address as incomplete.

Address Geocoding. Sometimes a delivery address isn’t a mailing address. For example, a rural address may not be recognized as deliverable by the USPS (because its mail goes to a PO box or general delivery), but it still corresponds to a real, physical location where Mom actually resides and other delivery services can reach. Our DOTS Address Geocoding product can determine the latitude and longitude of a delivery address with up to a 99.8% property-level match rate accuracy, ensuring that flowers get delivered to the front door, as well as, helping delivery drivers with efficient delivery route planning.

Address Detective. What happens when an address is incorrect or undeliverable? When it is being entered by a well-meaning but down-to-the-last-minute, hasty son, too often it could result in a lost sales opportunity. Our DOTS Address Detective saves many of these sales by using fuzzy logic with available data points to correct and append address data for “bad” addresses – so that Mom still receives her much-deserved bouquet.

50 Million Mothers Can’t Be Wrong

With an average of almost $40 per person spent on flowers and delivery, Mother’s Day is more than just a day of recognition – it is big business, serving roughly 50 million customers in just one weekend. It has come a long way since US President Woodrow Wilson issued a proclamation for the first national Mother’s Day in 1914.

We are proud to play a key role in ensuring the delivery of all these flowers every year – after all, we love to celebrate our moms too.

And we have a present for you too: a free access key that lets you try out 500 transactions for any of these or other capabilities in your own applications. Want to learn more? Contact our friendly and knowledgeable product team and we’ll take it from there.

Happy Mother’s Day – Mom ?

You’ve got questions? We’ve got answers! This is the first in a series of articles exploring common user questions about our products and how they can be used in business use cases, based on what you’ve asked our sales and technical support teams. We hope you’ll find these enlightening, interesting – and even fun to read!

For our first topic, we’ve chosen an area near and dear to many of our business clients: validating credit card transactions. We’ve previously explored some of the pros and cons of various approaches for credit card validation in a recent post, and will take a deeper dive into the differences between validation and verification of credit card addresses in a future article. Here, we will explore how to handle some of the most common use cases for credit transactions.

Let’s dive in:

Q: If we use the credit card company’s Address Validation System (AVS), we get a much cheaper processing rate. But it is very strict about these addresses, and kicks back too many transactions that are actually valid – so we are losing business and customers. Help!

A: This is an extremely common issue. One reason is that AVS only compares the numerical portion of the street address, together with the ZIP code, to verify the address. If either of these numbers are off even a little bit, it will reject the address. Often this is a good thing – because it can protect you from, say, a thief using a stolen credit card to ship to a bogus address – but this can also reject legitimate customers.

A simple solution for these “false negatives” is to use our DOTS Address Validation – US service to validate the address at the time the customer enters it. This gives you the ability to inform the customer in real time about address errors, and also offer them a validated and corrected address from our CASS-certified validation engine, powered by up-to-date USPS address data.

You can either simply validate addresses that fail the AVS check, or even better, validate every incoming address to ensure correct shipping addresses and a clean contact database. Either way, this is a simple step that will help more of your transactions go through smoothly.

Q: We are suddenly getting a lot of chargebacks and fraudulent transactions. Ironically, a lot of these fraudsters are giving us credit card numbers that pass AVS. What can we do?

A: You’ve discovered the hard way that many crooks – identity thieves in particular – open fraudulent credit accounts with legitimate shipping addresses. Of course, they never pay the bill and make off with your merchandise. Chargeback or “friendly” fraud is another way people fraudulently obtain goods without paying for them.

A 2018 Gartner report outlined machine intelligence and online fraud detection (OFD) tools as being among the most promising safeguards against these kinds of fraud. Many customers use our DOTS Lead Validation service as an automated screen for the quality of potential customers, using tests involving over 130 data points that yield an overall lead quality score from 0 to 100. Tools like these can go a long way towards weeding out the bad actors before you ship your merchandise to them.

As a bonus, the detailed results provided by Lead Validation also helps you decide whether to simply reject an order or pass it along for further human verification, making it easier to save good orders that may have raised a red flag or two.

Q: We offer a subscription service or sell products on a payment plan, billed to a customer’s credit card monthly. Increasingly people have been defrauding us by signing up with a prepaid credit card with a low balance – so they get the goodies, but only the first payment gets made. How can we prevent this kind of fraud?

A: This problem is actually quite easy to solve, using our DOTS BIN Validation product. Its output contains a value called CardType that lets you detect and flag prepaid credit cards. Armed with this knowledge, you can create business logic with options like:

• Let the customer know in real time that you do not accept this type of card for this product/service
• Request another form of payment,
• Offer only a pay-in-full option for this card type, or
• Decline the order.

Q: Is there anything else we can do to prevent fraudulent credit transactions?

A: One more pro tip is to compare the customer’s shipping and billing address with the BIN Validation’s Country field, which lists the country of the credit card’s issuing bank and the country result from DOTS IP Address Validation lookup. If they are different, you can flag certain countries (e.g. those with high fraud rates) to decline the transaction immediately or ask for another form of payment.

So what are your questions?

We would love to hear from you. Of course, you can contact our product team anytime for a personal response – and if there is anything you would like to see us discuss in a future article, let us know. Thanks!

Addresses in the United States used to be a simple matter of a street location, a city and state, and perhaps a city-specific postal zone. But by the 1960s, between massive increases in mail volume and the advent of computerized scanning and sorting equipment, the U.S. Postal Service needed a strategy to automate and speed up delivery. The result was the Zone Improvement Plan, or ZIP code for short, and it has since become a model for the world’s postal codes.

At Service Objects we make part of our living resolving and geolocating addresses, including their ZIP codes, so we thought you might enjoy discovering some of the history – and idiosyncrasies – behind those numbers at the end of your mailing addresses.

A ZIP Code Entertainment Spectacular

When ZIP codes were first introduced in 1963, their use wasn’t mandatory. (And believe it or not, still isn’t.) So to help convince people to switch from their old address formats, the U.S. Postal Service commissioned a 15-minute long educational film led by musical group The Swingin’ Six. It featured music, comedy, and even romance, juxtaposed with a leaden-faced appearance from the Postmaster General of the United States.

Here it is, preserved for posterity on YouTube. As a disclaimer, we take no responsibility if you can’t get their songs out of your head.

In keeping with a tradition of using cartoon characters to raise social awareness (think, for example, Popeye getting children to eat their spinach), the Post Office also commissioned an artist to create their new mascot: Mr. ZIP. In character form, he signified a new generation of speed and accuracy.

Can a Person Have Their Own ZIP Code?

The answer is yes – but only if you are the President of the United States or the First Lady. The POTUS’s ZIP+4 code is 20500-0001, while the FLOTUS is 20500-0002. Both are subsets of the White House’s dedicated ZIP code of 20500, which also has +4 codes for its postal station and Greetings Office. (You can actually look these up on the USPS ZIP code search page for 1600 Pennsylvania Avenue in Washington D.C.).

The one other example of an individual with their own ZIP code happens to be U.S. Forest Service mascot Smokey Bear. Between his popularity as an advertising icon and interest in the real live Smokey (an orphaned bear cub rescued from a 1950 forest fire) at the National Zoo in Washington D.C., he received so much mail that he was granted his own ZIP code of 20252. Although this ZIP code was eventually decommissioned in 1993, it was recently brought back by popular demand, as he still gets letters from children across the US.

Further up North, one other individual sharing this honor is Santa Claus, who fittingly has the Canadian postal code of H0H 0H0. No such luck in the US however, where letters to Santa go to the actual town of North Pole, Alaska and its ZIP code of 99705.

The ZIP Code That Got Swallowed Up

Somewhere in central Pennsylvania – off I-80, nestled between the Pilot Travel Center and the local Walmart – is the little town of Conyngham, PA. Better known as the town that was swallowed up by another ZIP code. You see, Conyngham and its roughly 2000 residents, with a ZIP code of 18219, is completely surrounded by the Sugarloaf, PA ZIP code of 18249, as shown in the image below.

(Image courtesy Google Maps)

In fairness, Sugarloaf’s ZIP code is further divided by ZIP+4 codes into four separate regions within the 18249 ZIP code. But poor Conyngham is still surrounded. And some poor homeowner is probably trying to explain to an insurance agent that even though she lives WITHIN the 18249 ZIP code, she doesn’t live IN it.

This situation can also occur at a street level, which is in fact surprisingly common: a street-assigned ZIP code may extend into an area where this street is surrounded by a different ZIP code. So a different ZIP code may be as close as your backyard neighbor!

Situations like these may sound humorous, but as this article points out, they can have a real impact on people’s lives. Issues such as insurance rates, voter registration, and jury duty can be affected, as well as more serious concerns such as emergency response – not to mention a possible loss of status and property value when your home is in one neighborhood but your ZIP code is in another. In response to these concerns, the USPS now has a mechanism for reviewing ZIP codes on a case-by-case basis.

Those Numbers Actually Mean Something

ZIP codes aren’t just assigned at random: each digit has a specific function. The first digit, from 0 to 9, places a mailing destination in one of ten broad mailing regions of the United States. The next two digits narrow down this destination to a central Post Office for a smaller region such as a city. Finally, the last two digits defines the destination further to a local Post Office.

So-called ZIP+4 codes refine the destination further, with the last four digits signifying data ranging from a PO Box number to a floor within a building.

Some entities are so large or specialized that they have their own ZIP code, including the Empire State Building, Dodger Stadium, the CIA, and New York’s LaGuardia Airport.

Putting More ZIP in Your Contact Data

As you have probably learned from this article, determining ZIP codes and their corresponding locations isn’t for the faint of heart. But fear not, we can help. Our DOTS Address Validation – US service helps correct and complete US addresses down to the ZIP code level, and our DOTS Address Geocode service provides accurate latitude and longitude coordinates for geographically-based applications ranging from insurance rates to home values. Contact us anytime, and we’ll respond faster than Mr. ZIP!

What time is it? The answer isn’t always a simple one – particularly in states like Arizona and Hawaii that do not observe daylight saving time (DST). And this can be important for your business: nobody wants to reach out to a client at 8 am, only to find out it is 7 am their local time and they aren’t in yet.

Here in California, the topic of daylight saving time has been a point of contention recently. With the passage of Proposition 7 in November, our legislature now has the ability to either change the dates and times of DST, or even establish permanent year-round DST should the Federal government allow it in the future.

As a developer, this kicked off a series of questions about the history of DST, how changes to local observations of time would affect programmed systems, and the nightmare of non-unified time standards. I don’t work directly with highly time-critical applications such as Global Positioning Systems (GPS), network television, or transportation systems. However, time that matches country, state, and local rules and regulations is important to me. Many of the tools I use leverage location-based clocks: for instance, servers or databases often create timestamps based on the machine’s current time.

Imagine a simple scenario where you have a computer in California and one in New York. Their clocks will of course read differently, because New York is in a different time zone that is 3 hours ahead. Simple enough, but what would happen if DST were observed differently across different localities? Would that mean that, when DST is in effect, New York is only 2 hours ahead of California? What if different states chose different dates to start or end DST? What if they ignored it entirely? What about my poor servers in different states and the timestamps that they are generating? What does it mean for the parts of the United States that don’t currently observe DST?

You probably see where the questions are leading: how do we build tools on top of systems in different localities, and what if I want to build in timing related elements into my own software? Overcoming these challenges can be better addressed by first looking at a brief history of DST, and the regulations put in place to help solve this nonuniformity.

What is Daylight Saving Time? – a brief history

Daylight saving time has been observed in both the US and various European countries since the World War I. It was enacted to cut down on energy consumption. In 1918 the U.S. adopted this policy, but it only lasted through the end of the war. At the time the observation of DST was unpopular, likely due to earlier waking hours, and was repealed a year later.

DST was adopted again in the US during the second world war under the name of “War Time”. At the time there was no federal law dictating whether a state had to observe DST or not. This lack of regulation resulted in inconsistent observations of DST.

Finally, in 1966 Congress decided to try and fix the inconsistent observation issue by enacting the Uniform Time Act. It was not the be-all-end-all solution to the problem, but it was a step in the right direction to get most states to follow the same regulations.

How does Daylight Saving Time affect computers?

The modern approach to solving time-related issues is for computers to set their system time based on a well-established time server. This time server has the difficult task of maintaining the correct time by factoring in any regional differences in policies such as DST. Chances are your home computer came preconfigured to reach out to one of these time servers using the Network Time Protocol (NTP). This protocol helps to keep your machine’s time in sync.

The same protocol can be used on databases, web servers, or other systems to keep up to date. These servers remove the burden from the end user by automatically updating the time based on your regional time standards. This is why there is no more dialing the clock on your computer an hour forward on that Sunday in March.

This network of time servers is also the answer to my worry about maintaining the proper time despite the differences and changes in local time related policies. California can be free to vote on keeping or removing DST, and I can rest assured there are measures in place to properly handle the changes.

How knowledge of Daylight Saving Time helps businesses

Spurred on by the vote in California and the differing opinions on DST, I decided to take a deeper dive into how local regulations can affect my line of work. It became readily apparent that scheduling tasks would need to have knowledge of DST as well as time zones. With these two items in hand I could write a scheduling application to smartly notify the recipients of meeting requests based on their local time. They would get a meeting request based on their local time, instead of having to add or subtract hours based on the difference in their time zones.

To get started I would need to determine the offset from Greenwich Mean Time + 0 (GMT +0), now more commonly known as Universal Coordinated Time + 0 (UTC +0). The time zone offset of the recipient’s location in conjunction with a daylight savings indicator would allow my application to be built. Both a DST flag indicating if an address observes daylight savings time and a time zone digit are returned by several Service Objects services. DOTS Address Geocode – Canada, DOTS Address Geocode – US, and DOTS Address Insight could all be leveraged for their DST flag and time zone.

My application is just the tip of the iceberg. The DST flag in conjunction with time zone information can be leveraged to make better business decisions. These fields could be combined into applications that help facilitate smarter contact with your prospective clients. Knowing your client’s location allows you to determine an ideal time to reach out to them. In a similar vein, if you know your target’s ideal emailing hour, you can use their location to dictate when to send out your targeted marketing campaigns.

Sales calls, meeting coordination, and targeted email campaigns are just a few of the ways you can use the fields from Service Objects services to improve your business efficiency. Contact us to learn more ways you can leverage our services.

Accurate address autocomplete

At Service Objects, our mission is to ensure contact data is ‘genuine, accurate and up-to-date.’ This can be challenging when it comes to our clients wanting to use an address suggestion or address autocomplete tool while ensuring accuracy and deliverability.

What is address autocomplete?

Address autocomplete is a real-time web service that suggests addresses while a user is still typing it out. The majority of them are built using Google’s Place Autocomplete, which Google defines as:

“a web service that returns address predictions in response to an HTTP request. The request specifies a textual search string and optional geographic bounds. The service can be used to provide autocomplete functionality for text-based geographic searches, by returning places such as businesses, addresses and points of interest as a user types.”

It sounds great on the surface but when you dig a little deeper, a few problems are uncovered:

• Google Places API often does not suggest locations at the apartment or suite level.
• The locations the Google Places API suggests are often not mail deliverable. For instance, a business may have a physical location at one address and receive mail at a completely different address.
• When Google is not sure of a location or address, it will make approximations as to where an address should be.

If your business mails or ships, these issues are going to create poor customer experiences and potentially generate expensive customer service issues. So, how can you can you enjoy the benefits of an address autocomplete tool while maintaining a high rate of accuracy and deliverability?

Address suggestion + validation = The super suggestor!

This is where Service Objects comes in. By combining the power of our Address Validation tools (US, Canada, and International) web services with Google’s Place Autocomplete API, we can identify if an address is complete, accurate and deliverable. Furthermore, where addresses are incomplete or not deliverable, they can be corrected in real-time by our address validation services. In fun, we call this the Super Suggestor (insert favorite superhero theme music here), providing the best of both worlds, time-saving, customer-friendly address suggestion with the confidence that the address selected is validated, accurate and deliverable.

So how do you combine these two APIs? Watch the step-by-step tutorial below to learn how to create your own Super Suggestor.

We have also provided the complete transcript here.

When are two addresses actually the same? And when can you remove one of them from your contact database?

The answer isn’t as simple as it sounds. Suppose you have two addresses as follows: 429 East Figueroa Street, Apartment 1, Santa Barbara, California, 93101 versus 429 E Figueroa St Apt 1, Santa Barbara, CA 93101. Or that for only one of these two addresses, the street address and the apartment number are on separate lines of the address. Simple text or line-by-line comparisons aren’t going to work in this case.

However, the United States Postal Service (USPS) can come to the rescue here, thanks to its standards for delivery barcodes.

What is a barcode?

Barcodes are unique identifiers assigned to each deliverable address by the USPS. A set of digits between 00 and 99 are assigned to each address and then, when that number is combined with the address’ zip+4, a sequence is created to uniquely identify the delivery point. The complete barcode consists of a zip+4, a 2 digit code identifying the premise, and a checksum digit to allow barcode sorters to verify the zip, zip+4 and delivery point code’s correctness.

Barcode Example: 931011445011

931011445	01	1
Zip+4	Deliver Point Code	Checksum Digit

How barcodes help you clean up duplicates

In short, barcodes can be leveraged to help identify duplicate records in your address database. The uniqueness of the barcode helps to solve the age old problem of identifying duplicate data. Let’s go back to the example we mentioned above:

Address A	Address B
429 East Figueroa Street	429 E Figueroa St Apt 1
Apartment 1
Santa Barbara, California, 93101	Santa Barbara, CA 93101

On the surface, these addresses seem very similar. They would both be deemed deliverable by the USPS despite their spelling differences. On one hand, you have Address A spelling out “East”, “Street”, “Apartment”, and “California”. On the other hand, Address B abbreviates these same fields. If you were to address an envelope with either of the spellings, it would reach the same destination.

As a human, looking at the two addresses above, it is easy to figure out that these two addresses are really the same delivery point. As a developer, however, figuring out that the two are the same is a nightmare without some sort of unique identifier. You would break these addresses into their component parts – address, address2, city, state, and zip – and then compare each field for Address A versus Address B.

If you came across any field that didn’t match up perfectly, you would assume the addresses were different and handle them accordingly. At this point it is easy to see that this approach is inadequate and would lead to the misidentification of the Address A/B example above. And even if you tried to write a smarter program, you would quickly discover that this a complex problem involving fuzzy matching, distance algorithms, and various other string comparison algorithms. If only there was a unique identifier that could be assigned to an address…

This is where Service Objects’ DOTS Address Validation products shine. On top of the validation of each input, every deliverable address is matched up with its USPS barcode. With these barcodes in hand, it is easy to compare two addresses without having to worry about spelling or standardization differences.

 

Mailing address input:

  

 

Service Objects’ return with barcode:

  

Detecting duplicate mailing addresses using the address’ USPS barcode is a simple, elegant solution to a complicated problem. If you’d like to try any of our address services, sign up for a free trial key and get your first 500 transactions free.

Below is a full transcript of the video Tutorial: Address Suggestor using Google’s Places API & Service Objects’ Address Validation API.

Today we are going to be building out an address suggestion input form tool. I’ve already built this out, but I will take you from the beginning, and show you step-by-step what you must do to implement this. In this demonstration, I will be using Visual Studio. This is the type of form that will predict the address you are trying to type. Besides address suggestion, it is also referred to as type-ahead, or predictive typing, and a couple of other things as well. We will use the Google Places API in conjunction with our DOTS International Address Validation to the predictive addresses, and address validation.

First, why is a form like this helpful? Why would someone want this? The main reason is so that you can have clean, accurate data added to your systems up front, instead of trying to clean the data up later, which can be very costly to do. Another reason, is to help speed-up the data entry, and data accuracy on the form. The data entry could be coming from your prospects and clients on a form you have published on the web. Maybe someone is purchasing a subscription, or ordering a product or service. The data could be coming from call-center staff, who are on the phone entering the data for the same types of reasons. There are really many reasons that an address suggestion form can help.

Now that we have some idea as to why we would want to implement an address suggestion tool, let’s switch over to how it works. There are three main parts to this integration. The Google Places API, the DOTS Address Validation – International API, and the web form itself. Some people wonder why we just can’t stop at the Google Places API, and the form, and exclude the Address Validation portion. One of the paramount reasons that the Google Places API is not enough is because it does not give you mailing accuracy. The second reason is that it makes approximations as to where an address could be, versus if it exists or not.

On the first point, accuracy, Google does not verify, or suggest addresses that are mailable. They typically return an address’s physical location on a map, but not if it is a valid mailing address. The second point is the guessing that the Google Places API does. It approximates where an address could be based on other addresses on the street. 508 Kings Road, Brighton, UK, looks like a legitimate address, but when you look at it on Google Maps, then it does not look like the address is actually associated with anything. Those are the main reasons why the Google Places API isn’t enough. You need to bring DOTS Address Validation – International to save the day, and make the solution truly useful.

In this demonstration, we are going to get a Google API account, and get an API key for the Places API. After that, we are going to get our DOTS Address Validation – International key from Service Objects. Here is an important note, you can alter the validation sections we are going to go over, to meet your specific needs. Here, I’m demonstrating how this can be done with DOTS Address Validation – International.

However, if your need is just in the US, then you can, instead, get a key for DOTS Address Validation – US, DOTS Address Detective, DOTS Address Insights, or DOTS Address Validation Plus. If all you need is Canadian address validation, then DOTS Address Validation – Canada should suit perfectly as a substitution. Any of our services that take an address as an input pairs perfectly with the Google Places API. Taxes is another one, DOTS FastTax is a great example that can also help you out. I could go on, but I’ll leave it to you to explore.
Once we have those keys, we will move on to setting up the form, and getting some of the UI Boilerplate stuff taken care of. After that, we will jump into the needed methods from the Google Places API. Lastly, we will go over how to setup the call to DOTS Address Validation – International. Though most of the work is done in Java Script, we will show you how to create a proxy, so that our license key is not exposed to the outside world for anyone to use and take. I guess this will be a kind of a two-in-one demo.
Now we’re going to switch over to the Google API account on page, this is where you can get any API that Google offers. Here we’re interested in the Places API, and the Maps Java Script API. You can see we have those already selected here. Here’s a bunch of unselected APIs down here, unused. We have the ones that we want already selected and added. What we’re going to want to do … I’ll go back for a sec. We’re going to want to first create a project, and we’ve already done that. We’ve called it Service Objects Address Suggest, and we added the APIs to this.

On their dashboard here, you can see the transactions that have occurred against the API. You can have the resolution up to 30 days, down to an hour. You can download this kind of information to really keep track of how your APIs are being used. We’re going to want to click in, and get some deeper resolution on the Google Places API, because we’re going to need the key. We’re going to need to pull the key out. When we switch over to that page, we have the key here, I suggest copying that off, saving it for later. You can name it whatever you want.

Then there’s some restrictions, non-HTTP, IP address, Android, iOS. You can set some restrictions up here that’s going to help with securing your API key when people are looking at your Java Script. They can see your key, so locking it down to particular page, or an IP address, those things are going to help secure your key so other people don’t take it and use it. For now, while we’re in development mode, we’re going to use the “None” selection so we can just get through our development. But before we go to production, we’re going to want to lock this down a lot better. That’s pretty much it. Save your API key off for later, and then we’ll show you where that plugs in as we go through the steps.
Jumping back really quick, I did want to mention that you can use the Google API key to a degree for free, but you’re going to want to go through the usage, and billing plans that they have for the key itself. Depending on your volume, you’re going to want to watch out for this, because it will cost money per transaction. There’s a few links here that I found useful when trying to analyze which plan to go with. You’re going to have to read through this yourself. It seems to be changing a lot recently, so you’re going to want to keep up to date with these pages here, and make sure you’re always on the right plan.

This page here, the Places API usage and billing was good. The pricing that scales to fit your needs helped a lot for figuring things out, and also this Pricing and Plans page as well gave a lot of good information that can help figure out which plan you need to go with, and what you need to look out for. But there’s a lot here, and it can be kind of confusing. I would really take your time, and look through these pages. Make sure you’re setting yourself up for the right plan.

Now we’re going to switch over to getting the DOTS Address Validation – International API key from Service Objects. This is our homepage, a lot of useful links to the products, solutions, developer support, blogs. Blogs have a lot of information. All of us in the company really help provide information, and write a lot of information about our services and products here, and really what’s happening in the industry that can help you guys out. That’s really worth taking a look at.

But we’re going to jump right in, and we’re going to go get the API key. I’m going to select this section for Address & Geocoding. We also have Lead Validation, Phone, Demographics, Ecommerce, Email. We’re interested in addresses, so we’re going to go in this section, and go from there. Coming into here, we have Address Validation, Address Geocode, Address Insights, NCOA Live. Address Detective. A lot of this can be used with what we’re trying to get accomplished here, since they’re all address-type services. But, for our purposes right now, we’re going to jump in, and do the Address Validation – International.

We’re going to click on this link. It’s going to take us to the product page for that service. Down here, you can fill out your information, and get your trial key. It will get emailed to you. Once you fill out this page, you’ll also get redirected to the information that you need as well. If you don’t see it in your email, maybe you got … You’re going to want to check your Junk Mail, just in case, but if you don’t find it in either place, you could still get the information after you get redirected here, so you’ll be okay.

Otherwise, you’ve got this input form, where you can try one-off lookups. You have your own information that you can send through the API in these fields here, or you can select this drop-down, and select some pre-populated data, and run that through to see what you can get back. Then at the bottom, we just have some example request, and responses in JSON and XML, based on the information that’s in these fields when you submit, just to take a look at what the service will give you back.

We do have an API key already, so I’m not going to fill out this form, it’s just good to know where you can get the API key. We already have all the code worked out for this project. I’m going to, instead of recreating everything one-by-one, I’ll just go through everything that I’ve created, the order in which you’re going to want to create these things, and I’ll highlight the different interesting points along the way. You could then take the code, and really understand what’s going on here. It’s not all the complicated, you guys should be able to use this, and use any of our other services that could use address suggestion, and implement that here as well, it would be really easy.

Just follow along as I go through the steps. I’ll point out the different things that are really unique, or something that you’re going to watch out for. The first thing we’re going to do, or what we did, was create some files that we’re going to need. Let’s just start with the style sheet folder. This stuff, I’m really not going to over style sheets, this is just to make the page look the way we want it to look. You guys could take what we have here, or do whatever you want on your side with the styles and classes here. The only interesting part here really, is the first part, where we create, basically default all the browser settings that may be sitting in the background, just to make sure that you have a consistent style sheet all the way through the different browsers. That’s all this is. The rest of it is any specific things that you wanted to change on your own with the look and feel of the page.

All this code that we’re going to be going over is going to be included in a file that you can download, and adjust, make your own. You can adjust anything we have here to suit your needs, which is likely what you’re going to want to do. All this code is freely available, so please take it, and make it your own. The next thing we’re going to go over is the addresssuggestinternationalform.HTML, the HTML markup page. We’re going to start by looking at the first include here that we have. Here it is, the jQuery script. We do use jQuery in the background, and when we get to the Java Script section of this tutorial. Keep that in mind. If you’re not familiar with jQuery, it’s really simple, a lot of good documentation out there to learn that, you can be up and running in no time. Just take a look at their documentation and you should be good.

The second script we have here is the API Handlerinternational.js. This is the file we’re going to be writing later on, once we get to the JavaScript section. Don’t worry about that one for now. That’s followed by the div for the result modal. That’s the modal that’s going to popup after we click the Verify button so we can see the results from the validation. After that, we have our header area, with the logo, and the title of our application, in this case, it’s Address Suggestion Demo. Then we have the country input field, the drop-down select. Here I’ve hard-coded all the different countries that we want to deal with. You’re going to want to populate this list dynamically when you’re doing this for production, or for live, or for your company.

I did this real quick to hard-code it in, but it’s definitely going to be better as something that you can dynamically populate. Then we’re followed by all the different input fields we have, autocomplete, this is really our address one field, this is the field where people are going to be typing their address in. Google Places API is going to be keying off of this, and showing you suggested addresses based off of what you’re typing in here. That’s what autocomplete field here is, it’s our address line one. Then we have our address line two, which really is supposed to be containing our apartment, or our suite information, the city, the state, the zip, that should be all pretty straight forward. Then we have a div, which is really our verify button, our validate button here.

At the bottom we have script to the Google Places API. Here we have our API key. This is going to be hidden when you’re looking at it, but this is where you’re going to want drop your key that you’ve made note of earlier when you set up your Google Places API key, that’s going to drop right into here. That’s all you’re really going to need to know about this page. There really isn’t anything special, or unique about it, other than the styling, and that we link up to the autocomplete field here to do the autocomplete against the Google Places API.

I do want to go back to this section here about the Google Places API key. I really want to highlight that this is exposed when somebody runs the form that goes to the page that has your form. So when looks at the background code, they can see your API key. As I mentioned earlier, we have no restrictions on our API key right now, so someone could, if they had this, use it for their own purposes, start running up transactions on the key, and that could end up being very costly. When you do move to production, do not forget to go back and change the settings on the key in the Google API account. You’re going to want to make sure it’s locked down as best you can, so that you don’t get calls against your API key unwittingly.

Now we’re going to jump into the API Handlersinternational.js file. This is the JavaScript file that’s going to really contain a lot of the interesting things that happen in the background on the screen. We created a JavaScript folder for that, so we can keep things nice and organized. JavaScript probably needs an S, capital S there. Oh well, we’ll keep it the way it is for now, and there’s our file.

The first thing in the file are these three variables that we set up, the autocomplete object here, the variable here, it’s just going to contain the autocomplete object that’s sent back from the Google Places API. The component form, this is really just an array of the IDs in our forms. If we really want to reset any of those fields, we can easily, quickly loop through those resetting them. Then selected country, we have set to US, but that’ll be overwritten whenever we have a new country selected from that drop-down.

The first thing we’re going to do is jump down to this function at the bottom. This function executes once the page has completed loading. What it does is it adds an event to whenever someone changes the country in the drop-down for countries, to another country, then this is going to execute, and it’s going to reset all the fields in the form, which makes sense. You don’t want to have data for the wrong country displayed. Then it executes this initAutocomplete method.

I’m going to jump into this one right now, and just get it out of the way. We’ll do that next. What the initAutocomplete method does is really just initializes the Google Places API, and it returns the autocomplete object into autocomplete here based off of the autocomplete element that we pass in through the IP. We set the Google Places API to respond with geocode type, which is the address type data that we’re looking for. You could put other things in here, and it gives you varying degrees of data back. The geocode is exactly what we’re looking for, so that’s what we have here.

Then based off of the country selected, you can restrict the API to a country. You can have a list here of countries. I think of up to five, you’ll want to double-check the documentation for this field. But what we need it for right now is the one country that is selected from the drop-down. After that, we add a listener to the autocomplete object. It’s going to basically react to selecting one of the addresses, once a address is selected from one of the suggestions this fill in address method gets executed. Basically, what we do is we get the place object back from the autocomplete object, and then we reset the form.

After we reset the form, we parse the place object, basically parsing apart the places data that comes back in JSON, and we populate the input fields based off of the address that was selected. Varying pieces of data come back, so you have several cases here that you might want to deal with, or expand upon, or not use, depending on your purpose. This is just an example of what can be done. After that, we populate the fields with parsed address from the response.

The bottom of the page really just has … what’s left is the modal start method, that really just deals with opening and closing the modal page, the result page that comes up after verification. The next part to really talk about is the click event, when someone clicks the Verify button, the click event will fire, and then we’re going to pull in the variables from the screen, the fields, and we’re going to populate them to the local variables here. Once we have those variables populated, we’re going to then toss them into the call address validation method. This is where the magic on the Java Script side of things happen. But inside that code, we’re going to call our backend proxy, which will really do the call to the validation. We’ll go over that next.

This is the call address validation method. It takes in the parameters that we sent in earlier from below. Then it makes an AJAX call, and processes the request. It processes the request against a Handler that we create, and that’s basically a backend script that’s going to allow us to hide our license key from being exposed to the outside world. It’s going to make a call to the API from there. It’s going to do the address validation. It’s going to process the response, and send it back to the AJAX method here. It’s going to land in either the success, or error sections here.

If there’s a response, and we have data coming back, and everything looks good, then we’re going to go into the success method. If not, we’re going to land in the error. With the error, we’re going to call the Handler again, but this time, we’re going to call the ValidateAddressBackup method instead. The only difference here, is that we’re calling the backup endpoint. Everything between the two endpoints is really the same, it’s just a backup server with the same data. Everything’s going to be the same, except, this is basically how we’re going to be handling our failover so that we can always guarantee a response from the service.

From there, we can still have a success or a fail. If we have a fail, then there’s more likely than not, a network error. Based on your process, you might be able to return more detail then show network error that I have here, but it really just depends on what you’re doing. If we’re successful, then again, we’ll call the success method. The AJAX method is going to call the Handler.aspx methods, and they’re going to basically be a single web form with nothing really on the markup page, except the basic stuff that gets prepopulated there. Really doesn’t matter, we’re not going to be using this part of it. We’re more interested in the Handler.aspx.cs page, the code behind for that page.

This is the page that’s going to be doing the request to the API. It’s going to be pulling in our key information from the Web.config file. Then it’s going to call out to the web service, and come back with a response, and then send that back to the Java Script that was calling us originally. To create the service references, you can go to References, and click Add Service Reference. In here you can fill in the URL of the address to the WSDL, and then name it. To know what URL to use here, you could just go to our website, and look at our docs. The documentation page is docs.serviceobjects.com. If you go there, you’ll have a list of all the services that we have. You’ll click on Address Validation. Once you get to Address Validation, you could scroll down a little bit, and find the WSDL.

This is the link to the trial WSDL. Just copy and paste that here, hit Go, and it finds the service. Here you can rename it however you’d like. I’ve already done this for our live, and backup endpoints, so let me just go over those with you really quick. What we’ve done already is created the AVI, and AVI Backup endpoints here. Right now, they’re actually both configured to look at this trial.serviceobjects.com endpoint. This is the main endpoint, and the backup endpoint. That one also is set to the trial.serviceobjects.com endpoint.

When you start out, you’re going to have your trial key. You’re going to set it up this way. But when you move to production, you’re going to come in here, and you can update this to ws.serviceobjects.com for your main endpoint. And then you’ll switch over to the backup endpoint, and you’ll switch trial over to wsbackup.serviceobjects.com. That way, you could hit the live, and backup endpoints, with the service reference.

Here in the Web.config file, you’re going to see a couple of things. Here we have appSetting key that we set for a value that we can pull in for the timeout, 5000 milliseconds, five seconds, and our license key for our service that we got in the trial signup for Address Validation – International. The rest of this is generated code based off of the WSDL that you created with the service reference earlier. There’s really not much going on in here, but the key part is that you have a license key outside of the application. We can change it on the fly, but it’s also something that gets pulled in, and it’s not seen by anyone who’s running your code, who’s running the form, who can easily look at your JavaScript or your code and see the underlying methods, the underlying codes. You won’t be able to see our key exposed this way.

Back in the Handler.aspx.cs file, we have the two methods, the ValidateAddressLive, and ValidateAddressBackup. They’re pretty much going to be doing the exact same thing, so we’re just going to go over one of them. The main point is that one of them is going to have the live endpoint, and the other one’s going to have the backup endpoint. Basically that’s really the only difference. Typically I would actually have this set into just one method, and maybe have another parameter here, but I just wanted to spread this out so that you could see that there is a difference, and one’s calling a main endpoint, and one’s calling a backup endpoint.

As I mentioned earlier, the live and backup endpoints are both pointed to the trial endpoint at this point. That’s what we’re going to keep doing here during our trial purposes, but when we switch to live, we’re going to switch our endpoints to the ws endpoint. Then for the backup, we’ll switch it to ws backup. Here we go. We’re going to start with this method. To be able to call it from the Java Script code, what we want to do is decorate the method with the web method attribute here. After that, we’re going to create the response object, and the service client object. From there we’re going to pull in our license key for the web service, and for the Address Validation – International API. Along with that, we’re going to pull back the 5000 millisecond timeout, the five second timeout.

After that, we create our client, and add the settings to it. Finally, we’re ready to call the endpoint with our parameters, with address one, two, we set a couple of these fields to empty strings, because we don’t need them in our cases. But depending on what country you’re dealing with, you may be pulling back address line one, two, three, four, five. So that’s what this is a placeholder for, is for additional address lines. We’re keeping it simple, and we’re just dealing with address lines one, and two. We’re going to cover the majority of situations this way anyways.

But those are there just in case you want to handle things a little bit differently. Then we have the Locality, AdministrativeArea, PostalCode, Country, and OutputLanguage, followed by the license Key. Since this is all on the backend server end, instead of the client, you’re going to be hiding the license key from anyone seeing it, and that’ll really protect your key from anybody being able to use it for any other purposes, other than what you’re intending here.

After the call to the service is made, the response is populated. If we have a null response, then we’ll just return an empty string, otherwise, we’re going to de-serialize the response into a JSON string, and return the JSON. The same exact same thing’s going to be happening here when, and if we need to make a call to the backup endpoint.

Here we are back in the CallAddressValidation method, where we called a Handler from the AJAX. Now we know what happens when the Handler is called. It basically calls the Address Validation – International API, processes it, and returns a result back to us. From there, we do the success, or the fail, the success, or error. In this case, we’re going to start by going through the success, and then we’ll go back over the error, or the failover later.

Going into the success, to get there, we make sure that the response object is not empty, so it has something to process. From there we get the JSON value out. It’s really just a JSON string at that point. Then we pass that over to the success method. Moving down to the success method, there’s really nothing too complicated here. What we’re doing is looking to see that the response is not undefined, and the response.AddressInfo object is not undefined as well. If we have those two things, we’re going to come in here, and we’re going to start building some string HTML output.

We’re going to use the string HTML output later on to inject back into class a div that we have on the main page. Let me see if I can find that. I might have it highlighted here already for us. This div, we’re going to try to populate that with the string HTML that we have in the JavaScript here. Moving back up, we’re going to be populating the HTML output with string HTML that we’re going to build in this method. We’re going to build it based off of comparing the inputs that were on the form, to the outputs of the results that we got from the API. That’s why you might really be wondering at this point why are we pulling back in the values that we had earlier, that we already passed and used to the address validation method?

Well, we’re pulling them back in so that we have these values locally, and that we can compare them to the output results from the service. We can show to the user what’s different between what we entered, and what the API found. Moving down … well first we have the inputs, these are the outputs pulled from the response object. Now we start building our HTML. We’re really just making our comparisons here, and figuring out how we want to display the output. Let’s just move to one of these ones here. Here we check to see if the outputLocality is not undefined. If we have something then, if it’s not equal to the input, then we’re going to put a “Bold” clasp, put “Bold” around the result, so that we can point out, or make it easy for the client to see, what is different, so they quickly make changes on their end, once they see the result.

We do that comparison for several of these fields. Based on what you’re doing, you’re going to want to probably do this section a lot different. This is just mainly a demonstration so you can see how we’re getting the elements out of the JSON, and how we’re comparing them to the inputs. You’ll have likely a different scenario, but this is how you could use it. As we move down here, the HTML is built. Then we inject it into the div. Back at the top of the success method, we demonstrated what happened if the response was not undefined, and the AddressInfo object was not undefined. Well, what happens if they are undefined?

Let’s go down and see what happens there. Well first we check to see if there is a response object that actually is defined, but has an error object that’s defined as well, and in particular, an error object with a TypeCode three. Well, if response is still undefined, we’re going to drop down here, and we’re just going to show the error. Otherwise, if we have the response code three, then we’re going to want to do a failover call. We’re only going to want do it once. We govern that with this count object that we increment once we get in here. That’ll force this to only ever happen once. Then we’ll call the failover method.

If we’ve already done it before, then we’re going to just drop down, and do the error response. One key thing that I want to point out here is that, even though we’ve made it into the success method, doesn’t mean we’re on our way to success guaranteed. There could be other problems along the way, like I just demonstrated with the else here, and what could have happened with the response. Success needs to be taken with a grain of salt. You might want to name it a little differently, so it’s a little more clear, but it’s not 100% success.

Now that we’ve gone over the success method popping out of the AJAX call here, well we should probably go over the error method when AJAX comes back with an error. When there’s an error, we’re just going to simply try our post to the other method, the ValidateAddressBackup method on the Handler. From there, it’s really, like I said earlier, going to do the exact same thing as the live, but call the backup endpoint, and run through the same steps. In here, again, we can have a success, or a fail, or a success and an error. If we get a success on the backup endpoint, then we’ll follow what we just went through with the success method, otherwise we’re going to show, at this point, it’s likely some sort of network error. We might, again, have some other information that you can add to this. You’ll do whatever you want there. We’re just showing a network error for now.

Earlier, as we went through the success method, and we realized that there’s an option when the address info or the response is undefined, we have this else here at the bottom. Well, I had mentioned the failover method here. The failover method, just to go into that briefly, it really mimics the same thing that the error did in the AJAX call, it just basically makes a second call to the other endpoint, to the backup endpoint, just in case there was a problem. It’s doing the exact same thing as earlier. You’ll see the exact same code here as you did there. You could pull this out into a method, and make sure that you only call this thing once since repeated, but here it is a demonstration just so it’s easy to see that you can do it this way.

Besides that, I think we’re pretty much wrapping up going over this code. There really isn’t much else on this file that’s complicated. Here’s a couple of methods that use jQuery to remove and add classes based on what comes back from the service, and what you want to display to the screen. It’s just basically checking in off of the classes, and then removing, or adding classes based off of the results. There’s nothing too big there.

The other important one here is this geolocate. This really helps with the auto-complete, where it pretty much does a bias to where … to a location. In this case, we have it set to a lat/long. What it does, is it looks for your current location. It gets the lat/long, and draws a radius around that location. It biases the results to that circle. When the form is created, if we look down here at the bottom, you’ll see that … where is it? Oh, here it is. When the field is focused on, we set the geolocate method. From there, that’s how we create the bias.

There you have it. That’s pretty much it. What we have left to do now is just give this a run, and see what we built. Everything loaded up properly, as expected. We have our drop-down menu with the countries. Let’s try our Service Objects address. 27 East … There it is, 27 East Cota Street. That really helps adding those kinds of addresses real quick. Let’s just do any address, how about … and this is obviously biased from where I’m located. I’m located in Santa Barbara.

Even though I have the country selected to United States, which is correct, it’s not picking any random place in the United States to start guessing. It’s basically picking where I’m sitting. That’s going to be an important detail for a lot of people in call-centers that are working locally, or if you’re in a call-center, and you change locations, you might want to give people an option to change their bias to a particular area, so they get results that come up quicker for the area that they’re located in.

Let’s pick this address here. Populates the fields here. Then we can click Validate. Then what comes back is the address that was … or that came back from the service, and the address that was entered. We can see that East was changed, Street was changed, and we have the plus-four added to the results. We still have some other details, but you know the service, it comes back with a lot of different details. I just gave you a rough, short look at what you can do. If you look at the API in the documentation page that I showed you earlier, there’s a lot of information there that will allow you to do many different things with the service. There’s a lot of different fields that come back that are useful.

In this case, someone could click on one of these, and either proceed with one of these addresses, or they can close, or try a different address, but that’s basically how the address suggestion application works. Thank you.

 

The holidays are fast approaching. Soon you’ll be celebrating the season and sending holiday gift baskets and cards to people you have enjoyed working with this year. So here at Service Objects, we’ve teamed up with none other than Santa Claus himself, with a great gift for you! A free web-based portal where Santa will help you verify addresses online, powered by our Address Validation capabilities.

It’s ready to use right now.

If you have never used online address validation before – or even if you have, and want a quick, fun way to check a few addresses – Santa is here to help. Take a look:

Use this form to give him a delivery address – anywhere in the world where reindeer fly, business or personal – and then he and his helpers will be right back with one of the following results:

Finally, a little bit of fine print. You will be allowed to look up a maximum of 10 addresses using this tool. This screen will allow you to look up one address at a time, including business names where needed, but bear in mind that we offer convenient API and list-processing versions of these tools as well. If you need to look up more addresses, no worries – a convenient link will lead you to learn more about our full-feature capabilities, as well as additional information about our phone and email validation capabilities.

We’re hoping that once you get a taste of some holiday address verification – and find out how simple it is to implement for your business – you’ll want to have these capabilities for yourself, all year round. (In fact, Santa confided to us that he and Mrs. Claus will keep using Service Objects tools to improve his own delivery accuracy every Christmas from here, because sometimes even reindeer are no match for automated shipping.) Want to learn more? Talk to our friendly technical experts, and we’ll make it a happy holiday season for you too!

Service Objects has been returning location-based tax rates in the DOTS FastTax API since 2001. Back then, we identified sales tax rates using only zip code. Since zip codes could cross multiple city and county borders, we were returning the rate most likely to be accurate based on preferred city and county. That evolved to returning multiple results based on a zip code, with each result containing a unique city, county and state. This was more accurate, but still involved a level of human intervention as multiple rates could be returned.

The service improved further as Service Objects developed its DOTS Address Validation services, which allowed us to get even more precise in determining the right area for the tax rates. Users could now submit a full address to the API and in most cases get a single accurate result, pinpointing the result to a location that had a clear tax rate.

However, if a given address was bad – or maybe even good but too messy to validate – it would not return a result and users would need to failover to the zip code level operations. Rural addresses which fall outside of city boundaries could wreak havoc if the proper location is not identified.

Last year, Service Objects introduced a new operation, GetBestMatch, to solve these challenges.

GetBestMatch in FastTax is designed to find the best rate possible and return a clean result. It uses the latest algorithms from Address Validation – US to clean and validate the toughest addresses and failing that, validates that the other data points are valid in order to return a zip level rate.

The service can also return an address level rate through the analysis of the nearby area, even if the address is bad. If an area can be proven to have a consistent rate for a zip, city or county and we know the address would be within one of those areas with 100% certainty, it can be deduced that since any address within that area has the same rate, the rate we return would be accurate at the address level. This extra analysis means that GetBestMatch can more precisely return accurate rates more often than its predecessor operations.

Additional returns offer more insight

To add even more accuracy to the service, GetBestMatch also does boundary analysis to ensure the most accurate location is used in the tax calculations. The main piece of information returned to users here is the “IsUnincorporated” note. IsUnincorporated helps users identify locations that might be considered part of the city but actually are not. This example shows what that might look like:

823 Holiday Dam Rd, Honea Path, SC, 29654

This is a partial return of the operation including the Note IsUnincorporated. This notifies the user that the CityRate, if it exists, should not be used in the final TaxRate. We have decided not to modify the original found result (TaxRate and CityRate) but return the IsUnincorporated result so that the user can handle it however they wish. In an upcoming release we will be adding a new return “UnincorporatedTaxRate” to simplify all of this.

The improved rates of return for address level checks also come with a few new challenges. Since we can return accurate rates even if the address is extremely messy, there might be times when we do not always have an accurate city or county to return. We know the rate is accurate but not necessarily exactly where the location is located. For example:

11900 Hunting, Pickerington, OH, 34147

This is a bad address. However, through extra validation we know the other parts of the address are good. We know the zip code and county are good, but it’s possible for multiple cities to fall within these boundaries. Analysis shows the rates would be the same regardless so while we are not able to accurately tell what city is attached to the address, we still know every address in the potential area would have the same rate, so we can confidently say the rate would be good for the address. Another example shows an even more obvious reason why we might not have a value:

8538 Smith Street, Wales, MI, 48027

Again, the address is bad, but this one is easy. Michigan only has a state rate, which means that all addresses within Michigan will have the same state rate. The analysis of city, county and zip shows a consistent city and zip, but the county could be multiple results. So, we can display city and zip code but not county. FastTax is not intended to be an address validation service, but a helpful tip is to look at the Zip return. If the Zip is 5 digits, it meant something happened during validation and the address did not pass inspection.

The latest GetBestMatch updates also added support for the US Territories (Guam, Micronesia, American Samoa etc.) Here is an abbreviated example of an address in Guam:

Bldg 30 Farenholt, Tutahan, 96910

In addition, we already supported military locations within the United States, but now there is support for all of the remote bases around the world as well. An abbreviated example of that can be seen here:

Unit 28103, USAG Graf Chaplain, APO, AE, 09002

Since all of these locations, even the ones abroad, had US assigned postal codes; making sure we could return results was of utmost importance. We now have a complete list of results covering all areas associated with the United States.

Finally, the latest operation also now supports JSON responses as one of our last services to be converted. This operation was also created to be more dynamic, information components outputs allow us to add new results on the fly without breaking any client integrations, like those using SOAP. Fields such as CountyFIPs have already been added, and the new field UnincorporatedTaxRate will also be added here. These fields allow us to work with our clients to add custom logic or results that might not otherwise be available.

Is there a custom logic you’d like to see in FastTax? Reach out and let us know, or get your free trial key and start testing today.

Service Objects is committed to fighting fraud and bad data wherever we see it. Through our APIs, best practices when handling sensitive data, or through recommendations on clients’ business logic, we are here to help enhance data quality and eliminate fraud.

A good example of the latter is educating our customers about how to avoid fraud losses. One way is by paying closer attention to orders using freight forwarders – which are legitimate services that are often misused by fraudsters. At the end of this post, you will find a free resource to make this easier: an extensive list of shipping and freight forwarders that you can use to help fight fraud when fulfilling orders.

What is a freight forwarder?

Freight and shipping forwarders arrange for the exporting and importing of goods. These companies often specialize in storage and shipping of goods on behalf of customers. In short, they help arrange for goods to get from point A to point B.

Are all freight forwarders associated with fraud?

Absolutely not! There are many reputable freight forwarders that do great work in coordinating the shipping of goods between consumers and sellers. When fraud is perpetrated, they are co-victims along with the seller. That being said, freight forwarders are often a go-to-tool for duping vendors and sellers into footing the bill for fraudulent purchases.

The typical process may go as follows:

• A customer will place a large order, and ask that the product(s) be shipped through a specific freight forwarder.
• The customer will offer to reimburse the seller for shipping through the freight forwarder – and normally wants the order shipped quickly, before the scam is discovered. (Money is no object for orders like these, because they are usually being placed with stolen or compromised payment methods.)
• Often the fraudster will have set up a legitimate-looking website ahead of time to give the appearance of a legitimate and trustworthy business.
• After the seller ships the goods and they are picked up by the fraudster, the payment for the shipping fee and the products itself usually falls through, leaving the seller to foot the bill for both the freight forwarder’s services and inventory loss.

How do I avoid fraud where freight forwarders are used?

Great question! One of the best and easiest ways to help mitigate this type of fraud as a seller of goods is to pay extra attention to orders using a freight forwarding company’s address. For PO’s like these, it would be smart to build in business logic for some extra vetting to ensure the purchaser’s legitimacy and help prevent fraud from the start.

That is why we are providing a list of all the freight forwarders we could find. We recommend using this list to detect matches between an order’s shipping address and a freight forwarder’s. To do this, run an order’s shipping address through our DOTS Address Validation – US service and use the BarcodeDigits field as a unique identifier for an address. If the BarcodeDigits address matches a freight forwarder’s address, the order should be flagged for some additional vetting to verify its authenticity.

Service Objects is committed to helping our clients avoid fraud however we can, and this list and the business logic is just one strategy that can make a real difference. If you need help setting up our address validation tools, please feel free to contact us, we are always happy to help.

Google Maps is an amazing service. Much of the civilized world has now been mapped through its data sources, ranging from satellite data to its ubiquitous camera-mounted vehicles. The result is a tool that allows you to find a location, link to local businesses, or virtually drive anywhere from downtown Paris to rural Mexico.

However, if you use Google Maps to validate addresses in a business, it is a little like trying to find a lifelong mate for your grandmother on Tinder: it is possible, but with a tool that wasn’t necessarily designed for that purpose. So let’s look at the differences between this service versus professional address validation and geolocation tools.

Google maps versus address validation

Let’s start with the most important difference: Google Maps is very complete, but sometimes wrong. How wrong? Mistakes can range from bad directions, wrong street names, and bad addresses to wrong country borders, omitting large cities and everything in between. Once, in a mistake Google acknowledged, a Texas construction firm even demolished the wrong house when Google Maps sent them there.

Another difference is where the data comes from in the first place. Google Maps uses a variety of sources including administrative boundaries, parcels, topographic features, points of interest, trails, road features, and address points or ranges. It also accepts data from “authoritative” organizations as well as individuals, subject to a vetting process. As a result, however, it is possible for mistakes to be introduced and/or made when aggregating or consolidating the data.

Finally and perhaps most importantly, Google does not know exactly where every address is. When it does not have rooftop level data to pinpoint the address it will estimate where an address is using techniques such as address interpolation. Sometimes an address may also be wrong because an individual claimed the location and entered the information incorrectly, or changes such as new municipal or postcode boundaries were not updated.

What the pros do

By comparison, professional address validation and geolocation tools don’t guess at results, because their focus is more on accuracy. Tools such as Service Objects’ DOTS Address Validation and Address Geocode capabilities are focused on delivering an accurate and precise response, versus settling for “close enough.”

To get specific, if our address validation tool cannot correct and validate that an address is real, we will fail it and will not guess. By comparison, Google may just use the closest approximation, which can lead to issues. Similar rules apply to geocoding latitude and longitude coordinates from address data: where necessary, Service Objects will move down a gradient of accuracy/precision, but will still often be closer to the correct coordinates than Google.

Another key difference lies in our data sources. For example, DOTS Address Validation uses continually updated USPS, Canada Post and international data in combination with proprietary databases, to create near-perfect match accuracy. Likewise, for Address Geocoding addresses and coordinates are validated against our master database, the US Census Bureau, TIGER®/Line file, USPS® ZIP+4 tables, and other proprietary databases, ultimately yielding a 99.8% match rate accuracy when translating an address to its latitude and longitude coordinates.

Use the right tool

We like Google Maps. Without it we wouldn’t be able to easily visit major world cities online, find a good sushi bar near our hotel, or get directions to visit Aunt Mildred. But when you need professional-grade accuracy in address and location data for your business, be sure to use the right tools. Need more specifics? Contact us for a no-pressure consultation, and our team will be happy to explore your specific needs.

Most people think that they mail or ship things to addresses – and they would be wrong. And the reasons for this might be very important to your bottom line.

First, let’s look at one actual address here in our native Santa Barbara, California: 1540 N. Ontare Road.

 

This address is quite real. (In fact, its property is currently for sale on Realtor.com.) But we wouldn’t recommend shipping a package there – at least not yet – because at the moment it is a vacant 20-acre lot.

Now, let’s look at another address: 350 Fifth Avenue, New York, NY:

 

This is also a valid address: it is the famous Empire State Building, one of the tallest buildings in the United States. We wouldn’t recommend using this address by itself for shipping a package either, because without more detail such as a suite number, there is no way of knowing which of its more than 1000 businesses serves as the destination. (In fact, the address itself isn’t even that important here: this building is large enough to have its own ZIP code, 10118.)

Understanding delivery points

These are both examples of the differences between an address and a delivery point. Addresses simply describe the location of a piece of geography, while delivery points are the lifeblood of physical shipments: they are approved unique locations served by delivery services such as the U.S. Postal Service. Many people think they are shipping to addresses, but they are actually shipping to delivery points.

This underscores the importance of delivery point validation, whether you are doing a direct mail marketing campaign or shipping products to customers. There are several possible points of failure where a delivery point may be invalid or undeliverable:

• The physical address may be incorrect
• The physical address may be correct, but undeliverable (such as our vacant lot example above)
• The physical address alone may be insufficient, such as a multi-tenant building
• Additional delivery point information may be incorrect or invalid: for example, a fourth-floor suite in a three-story building, or a nonexistent suite number
• The delivery point information may be completely correct, but correspond to the wrong recipient

So from here, your new mantra should be: is it deliverable?

Address validation: the key to accurate delivery points

This is where our flagship address validation tools come in. Available for US, Canadian and international markets, these services provide real-time verification of deliverability – including flagging of vacancy, returned mail, and general delivery addresses – to ensure accurate contact data at the time of data entry or use.

These tools instantly verify, correct and append delivery addresses, using APIs that integrate with your CRM or marketing automation platforms, cloud connectors, or convenient batch services for cleaning your databases without the need for programming. Whichever approach you use, you will leverage our vast infrastructure of up-to-the-minute data from the USPS, Canada Post and other sources, along with sophisticated and accurate address verification capabilities.

Our DOTS Address Validation – US 3 service, for example, provides near-perfect match accuracy with updates mirroring the USPS, and sub-second response times that allow you to validate live customer input in real time. And our industry-leading GetBestMatches operation combines Delivery Point Validation (DPV) to verify an address is deliverable, Residential Delivery Indicator (RDI) to identify residential or business, and SuiteLink (SLK) to add secondary suite information for businesses, all with a single API call to our USPS CASS Certified™ engine.

Want to learn more about engineering delivery point validation into your operations? Contact us for friendly, knowledgeable answers from our experienced team of data quality professionals.

Service Objects is pleased to welcome a new service to our lineup, DOTS Address Insight – US.  Built on the core of our USPS CASS Certified DOTS Address Validation – US and DOTS Address Geocode – US services, Address Insight – US blends address and geocode data with supplemental demographic data. Our proprietary datasets of hard to get addresses (like rural or unincorporated areas) enhance United States Postal Service data and provide additional insights about locations that no single service could handle. Address Insight – US uses this data to strengthen your customer profile with just one call.

Address Insight – US employs powerful data from Service Objects’ strongest services

Address Validation – US provides robust address validation, correction, and standardization for the vast majority of valid US addresses. Impressive fuzzy matching capabilities and logic are used for dealing with complex address structures. Delivery point validation, residential/business indicators, and suite link to append suite information are all included. In addition, Address Validation – US returns important informational pieces like corrections that were made to the address or identifying special cases such as location vacancy or returning mail.

Address Geocode – US combines multiple datasets to handle complex cases and messy addresses and return the most comprehensive set of Latitude and Longitude coordinates possible. Key informational pieces including State FIPS, County FIPS, Census Tract, and Census Block are also returned. Mapping calculations are performed to identify locations that are unincorporated, or outside of the bounds of a city. These calculations also identify the most accurate name of the location in PlaceName, which could be the name of an area within a larger city – where the larger city would normally be returned.

Three-in-one service improves results and location scoring

In addition to the vast datasets found in Address Validation – US and Address Geocode – US, Address Insight – US incorporates additional compiled datasets that improve results and enhances location accuracy scoring. The ability to return information about challenging or hard to find addresses is a critical feature of Address Insight – US. The service returns several notes that help identify information about the address, such as:

• AddressFoundByUSPS indicates that our Address Validation service successfully identified the location. This is the best possible result as it indicates a solid chance of mail delivery and more informational datapoints are available.
• AddressFoundInSupplementalData indicates that the address information was found in one of the supplemental data sets. Its not as high quality as the USPS data and not as many additional data points are available, however there is a high likelihood the location is a good address.
• AddressIsGeneralDelivery indicates that we could not find any specific information on the address, but the area is known and the street is good. The location is likely part of a General Delivery area and still has a strong likelihood of being valid.

Address Insight – US returns a score from 0-100 that approximates the likelihood that the location is a good one.

Additionally, Address Insight – US returns many other useful pieces of demographic and informational data, which can help businesses increase revenue through targeted marketing and satisfy regulatory requirements for compliance in different industries. Sample demographic returns include:

• ZipHouseholdValue tells the average value of houses in the area.
• ZipPersonsPerHousehold tells the size of households in the area.
• HouseholdIncome returns give the average house hold incomes for different levels of the area.
• Other informational returns include area codes associated with the area, time zone, MSA, CBSA, DMA and more.

New interface designed for future enhancements

One of the best new features available in Address Insight – US is that it is built upon a new dynamic interface that allows us to safely add in new data fields. We will never change a result that already exists, however, this interface allows us the ability to continually improve the service and add in new fields as they become available. This feature will allow Service Objects to potentially work with clients on custom solutions and in the future, we may even be able to build add-ons to the service that may return entirely new datasets.

Address Insight – US provides address validation, geocoding, and demographic data – all with a single call. We support REST, SOAP, GET, and POST requests over HTTPS outputting in XML and JSON formats. Get started with your free trial key for Address Insight – US or visit the developer guide to learn more.

Labor Day is much more than the traditional end of summer in America: it pays tribute to the efforts of working people. It dates back well over a century, with one labor leader in the 1800s describing it as a day to honor those “who from rude nature have delved and carved all the grandeur we behold.” And we aren’t forgetting our friends in Europe and elsewhere, who celebrate workers as well with holidays such as May Day.

As we celebrate work and the labor movement – and enjoy a long holiday weekend – we wanted to take a look at some of the ways that we help you save labor, as you try to carve grandeur from your organization’s data. Here are some of the more important ones:

Validation and more. Let’s start with the big one. For nearly two decades, the main purpose of our existence has been to take the human effort out of cleaning, validating, appending, and rating the quality of your contact and lead data. Whether your needs involve marketing, customer service, compliance or fraud prevention, these tools save labor in two ways: first, by saving you and your organization from re-inventing the wheel or doing manual verification, and second, by saving you from the substantial human costs of bad data.

Ease of integration. What is the single worst data quality solution? The one that gets implemented badly, or not at all. One of the biggest things our customers praise us for is how easy it is to implement our tools, to work almost invisibly in their environment. We offer everything from API integration and web hooks with common platforms, all the way to programming-free batch interfaces for smaller or simpler environments – backed by clear documentation, free trial licenses and expert support.

Speed and reliability. As one customer put it, “milliseconds matter” – particularly in real-time applications where, for example, you are validating customer contact data as they are in the process of entering it. Our APIs are built for speed and reliability, with a longstanding 99.999% uptime and multiple failover servers, as well as sub-second response times for many services – so you don’t waste time tearing your hair out or troubleshooting responsiveness issues.

Better analytics. Your contact data is a business asset – put it to work as a tool to gain business insight for faster, more informed decision-making and market targeting. You can target leads by demographics or geocoding, enhance your leads with missing phone or contact information, or leverage your customer base for better decision support, among many other applications.

Customer support. We recently interviewed a major longtime customer about using our products, and when we asked them about support they gave us the highest compliment of all: “We never need to call you!” But those who do call know that our best-in-class support, staffed by caring, knowledgeable experts who are available 24/7/365, represents a large savings of time and effort for our clients.

We hope you enjoy this Labor Day holiday. And when you get back, contact one of our product experts for a friendly, pressure-free discussion about how we can create less labor for you and your organization!

 

The golden rule of marketing has always been, “know your customer.” In today’s regulatory environment, however, it might be more accurate to say, “know your customer – or else!” Nowadays customer data – particularly in areas such as geocoding and demographic data – are often central to maintaining compliance with a wide range of regulations, in the financial world and elsewhere.

In response to this, Service Objects has just released a powerful new capability to help automate the gathering and analysis of geolocated consumer data: Address Insight – US. It provides address standardization, address geocoding and demographic information together in one real-time service, and is designed to serve a wide range of applications ranging from compliance to targeted marketing.

Examples of financial compliance issues

Let’s look at some of the areas where address insight can benefit your compliance efforts:

• The Community Reinvestment Act (CRA) requires federally insured lending institutions to provide lending opportunities to low-to-moderate income communities – and in particular, prove that they are not “redlining” specific neighborhoods and denying them credit. One of the key performance criteria for evaluating CRA compliance is your geographic distribution of loans.
• The Home Mortgage Disclosure Act (HMDA), enacted by Congress in 1975, requires lenders to publicly disclose data regarding their mortgage lending activities. While this is a disclosure law with no implied quotas, HMDA also serves to ensure that lenders do not contribute to the decline of specific geographic areas by failing to provide adequate mortgage financing.
• For consumer lending in general, the Federal Financial Institutions Examination Council (FFIEC) has a set of Fair Lending Examination Procedures used to audit lenders for evidence of lending discrimination. These reviews include an analysis of geographic patterns in lending to seek evidence of “redlining” or neighborhood-based discrimination.
• Conversely, certain real estate transactions may be subject to Geographic Targeting Orders (GTO), which are enhanced identification and record-keeping requirements imposed by the Federal Financial Crimes Enforcement Network for expensive real estate transactions in areas that are prone to money laundering activities. For example, as of 2017 transactions of $3 million or more in Manhattan or $1 million or more in parts of Florida were subject to GTOs, along with numerous other metropolitan areas.

A solution for compliance and beyond

Of course, there are numerous applications beyond compliance for geocoded address insight. For example, academic researchers can use address insight to study specific neighborhoods – for example, the University of Chicago divides the city of Chicago into 75 defined communities that correlate with tract information, and can be used as study variables. And of course, the combination of location insight and demographic data can be a very powerful tool for market targeting.

For compliance applications, Service Objects’ Address Insight – US provides data such as MSA code, state code, county code (FIPS), and tract number for addresses for FFIEC compliance. It also includes all the benefits of Service Objects’ flagship address validation and standardization capabilities, as well as appended demographic information such as household values and incomes by ZIP code.

As with all Service Objects services, Address Insight – US is available through APIs that can be interfaced directly to most contact data automation platforms, as well as convenient batch list processing for smaller applications or specific datasets. Contact us for a free 500-transaction trial key, and see what this new tool can do for you!

The country of Australia, officially known as the Commonwealth of Australia, consists of six states and two territories. There are over 13 million known deliverable addresses in Australia. This article breaks down the standard format used for Australian addresses, and what to check for in each field of these addresses.

Postal Services

Mail in Australia is handled by Australia Post, formally known as the Australian Postal Corporation. Australia Post is a government-owned corporation that was founded in 1809.

International Country Code

First, let’s look at how Australia defines its country codes, as well as its states and territories. The International Organization for Standardization (ISO) published the ISO 3166 standard, officially known as Codes for the representation of names of countries and their subdivisions.

The ISO 3166 standard consists of three parts:

Part	ISO	Description
1	ISO 3166-1	Country Codes – defines codes for the names of countries, dependent territories, and special areas of geographical interest.
2	ISO 3166-2	Country subdivision code – defines codes for the names of primary subdivisions of a country, such as a state or a province.
3	ISO 3166-3	Code for formerly used names of countries – defines codes for country names that have been removed from ISO 3166-1.

ISO 3166-1, which defines country codes, contains three sets of country codes:

ISO Country Codes	Description
ISO 3166-1 alpha-2:	Defines a country as a two-letter country code, commonly referred to as the ISO, ISO2, or ISO-2.
ISO 3166-1 alpha-3:	Defines a country as a three-letter country code, commonly referred to as ISO3, or ISO-3.
ISO 3166-1 numeric	Defines a country as a three-digit country code.

ISO 3166-1 Country Codes – Australia

Country Code Type	Country Code
ISO 3166-1 alpha-2 code	AU
ISO 3166-1 alpha-3 code	AUS
ISO 3166-1 numeric code	36

ISO 3166-2 Codes

The ISO currently lists codes for Australia’s six states and two of its territories.

ISO 3166-2 code	Subdivision Name	Subdivision category
AU-NSW	New South Wales	State
AU-QLD	Queensland	State
AU-SA	South Australia	State
AU-TAS	Tasmania	State
AU-VIC	Victoria	State
AU-WA	Western Australia	State
AU-ACT	Australian Capital Territory	Territory
AU-NT	Northern Territory	Territory

Address Format

Now, let’s look at how delivery addresses are constructed. The address format for deliverable mail in Australia is defined by Australia Post, where an address is made up of several components.

Position	Address Component	Description	Format	Requirement	Example
First line	Recipient	The name of the person, company or organization.	Use common abbreviations in titles and distinctions. Also,avoid unnecessary punctuation.	Required	Issac Nichols
Second line and third line if necessary	Reference Details	When necessary, the name of the person’s job/position and/orthe name of the company, organization or department.		Optional	Postmaster Australia Post
Second to last line	Thoroughfare	The street address, Box number or Locked Bag number. If athoroughfare is not available, then include thebuilding/complex name in its place. Include building subunitand floor/level when necessary.	Use common abbreviations where applicable. Also, no punctuationallowed.	Required	111 Bourke St
Last line, first component	Locality or Delivery office	The full name of the city, suburb, placename or Post Office-Delivery Centre (DC) or a Business Centre (BC). Note that thedelivery locality may not necessarily be the same as thegeographic locality.	Must be in UPPER CASE. Also, no punctuation allowed.	Required	MELBOURNE
Last line, second component	State or Territory	The abbreviated format of the state or territory.	The abbreviation of the state or territory and not the fullname. Also, no punctuation allowed.	Required	VIC
Last line, third component	Postcode	A four-digit numeric code used to identify the postal deliveryarea.	Do not omit leading zeros. Also, no punctuation allowed.	Required	300

States

Name	Abbreviation	Postcode Ranges
New South Wales	NSW	1000—1999 * 2000—2599 2619—2899 2921—2999
Queensland	QLD	4000—4999 9000—9999 *
South Australia	SA	5000—5799 5800—5999 *
Tasmania	TAS	7000—7799 7800—7999 *
Victoria	VIC	3000—3999 8000—8999 *
Western Australia	WA	6000—6797 6800—6999 *

* Reserved for PO Boxes and Large Volume Receivers (LVR)

Territories

Name	Abbreviation	Postcode Ranges
Australian Capital Territory	ACT	0200—0299* 2600—2618 2900—2920
Northern Territory	NT	0800—0899 0900—0999*

* Reserved for PO Boxes and Large Volume Receivers (LVR)

External Territories

Australia has three inhabited external territories. They do not use their own name and abbreviation in Australia Post’s postcode system and are instead assigned the name of another state.

Name	Abbreviation	Postcode
Norfolk Island	NSW	2899
Christmas Island	WA	6798
Cocos (keeling) Island	WA	6799

Postcodes

Australian postcodes are four-digit codes that are used to help sort and route mail. The first two digits often represent which state or territory the postcode belongs too, with the exception of the Australian Capital Territory (ACT) which is embedded in New South Wales (NSW).

The postcode is the third and final address component in the last address line, following the Locality and State/Territory components. However, if the envelope being used includes four postcode squares in the bottom right corner then Australia Post prefers that you fill those boxes in with the postcode instead.

Postcode vs Geography

Some postcodes may cover two or more states or territories. For example, the postcode 0872 is currently used to cover 87 localities located in West Australia (WA), South Australia (SA) and Northern Territory (NT). Australia Post sometimes finds it easier to send mail through a post office located in one state/territory for an address geographically located in another state/territory. So, it is not uncommon to find an address with a mailing address that does not match its physical address or geographic location.

Postcodes do not always correspond to a geographic location. Many postcodes are reserved for post office (PO) boxes and some are reserved for large organizations. Some large companies, government agencies, and organizations are classified as Large Volume Receivers (LVR) and will have their own unique postcode. For example, the postcode 0200 corresponds to the Australian National University

Address Validation International: Overcoming Cultural Idiosyncrasies and Postal Format Variables

The above content provides a general overview of Australia and the address format specified by Australia Post. Overall, there are more than 18 different address components, elements and fragments to consider when working with Australian addresses. There are also monthly data updates published by Australia Post to stay on top of.

As with most countries, Service Objects’ Address Validation International (AVI) is capable of processing and validating deliverable addresses in Australia. By understanding this country’s very structured address format, including specific idiosyncrasies such as required upper-case municipality addresses, state and territory abbreviations, and four-digit postal codes, you can automate much of the process of ensuring your contact data quality for this important international market.

In a previous blog, we discussed the benefits of using DOTS Address Detective – International to detect a contact’s country. This blog will discuss some of the challenges surrounding country detection in more detail, as well as provide an overview on how we determine the best country from your data.

Contact components

When trying to append a country to a contact, we have four main components to examine.

1. Address
2. Phone
3. IP Address
4. Email

Each component must be carefully evaluated on its own merit before it can be used to help identify a country for the contact.

Address component

The Address component may represent a contact’s physical location or mailable address. It is the most diverse and complex of all the components. International addresses do not follow a singular format, language or standard. Each country has its own set of rules and standards, which can also make the storage of international addresses problematic for US-centric CRMs.

This also means that is common for a contact’s address to be incorrect and/or incomplete. Additionally, some businesses are not always interested in capturing a mailable address and only wish to store a contact’s region. Depending on who is entering the contact address and how it is being stored, it would not be unreasonable to expect this data to be flawed in more ways than one.

Knowing the country is critical to processing most addresses. It determines the address format, which is needed to identify individual address elements, which in turn are needed to identify a locality, postal code or region. With that said, our sophisticated data-driven algorithms are not dependent on completeness and allow for a wide variety of formats and languages.

If you think you can identify a country’s address, take our fun, short Country Quiz.

Similar to the DOTS Address Validation International service, the address component consists of Address Lines 1-8, Locality, Admin Area and Postal Code. The address can be entered entirely in lines 1-8 or in combination with the Locality, Admin Area and Postal Code fields. Address line order does not matter, and common mistakes like putting an address value into the wrong address field are detected and handled.

Not all countries follow the US city-state pairing format or the equivalent locality admin area pairing. Many international addresses do not include an admin area, which can make country detection difficult since many localities from around the world can often share names. Take Venice, for example, which can be found in separate locations of three different countries.

Locality	Admin Area	Country
Venice	Venice	Italy
Venice	Alberta	Canada
Venice	California	USA
Venice	Florida	USA

If no other address information besides the name Venice was made available, one would be left having to choose between these three countries. However, by making use of other contact data such as a phone number, IP address and/or email, the service can cross reference various datasets to better determine which country is the best match. Then again, if the locality was entered as Venezia, the Italian endonym for Venice, there would be less ambiguity and the country Italy would be the clear choice.

Phone component

The phone component consists of a contact’s phone number(s). The format of a phone number is dictated by its country’s numbering plan. Some countries have their own numbering plan, while others share one. The USA and Canada, for example, share the North American Numbering Plan (NANP), whereas the UK and its crown dependencies share the UK National Telephone Numbering Plan. Most countries conform to the E.164 International Telecommunication Numbering Plan, which is published by the International Telecommunication Union (ITU).

The E.164 Numbering Plan

The E.164 currently provides five number structures (numbering plans) for international phone numbers:

1. International ITU-T E.164-number for geographic areas.
2. International ITU-T E.164-number for global services.
3. International ITU-T E.164-number for Networks.
4. International ITU-T E.164-number for groups of countries.
5. International ITU-T E.164-number for trials.

Each structure has its own set of rules and requirements, but telephone numbers that conform to E.164, in general, will adhere to the following:

• The recommended maximum length for a telephone number is 15 digits.
• Telephone numbers will begin with a Country Code (CC).
• Telephone numbers will not include Prefixes and Suffixes

Country codes

Country calling codes are published by the Telecommunication Standardization Bureau (TSB). Depending on which E.164 structure is being used the country code (CC) may vary between 1 to 3 digits or may be fixed to 3 digits. Country codes are followed by the destination number in accordance with the E.164 numbering plan. When storing a country code or an international (E.164) number, the number is commonly prefixed with a plus symbol (+) to indicate that when dialing the number, one must first dial the appropriate international call prefix to complete the call.

Prefixes

International call prefixes (also known as call out codes, dial out codes, exit codes or international access codes) are used to make a call from one country to another. The Prefix is dialed before the country code (CC) and the destination telephone number. Prefixes are not a part of the E.164 numbering plan and it is recommended to not include them as they can interfere with country code identification.

Making the Call

Suppose you have a contact in the UK with the following number saved in your CRM, ‘+44 123 456 7890 Ext. 123’, and you wanted to call this person from within the USA. To call them, you would dial 011441234567890, and then after you have been successfully connected you would next dial your contact’s extension of 123.

The table below shows how the prefix and suffix are not a part of an international number.

Prefix	International Number		Suffix
	Country Code	Destination Number
011	44	1234567890	Ext. 123

Now suppose that you wanted to call this contact again, but this time you are in Sweden and not in the USA. Instead of dialing the 011 prefix, which is shared by all countries in the North American Numbering Plan (NANP), you would dial 00 which is the prefix used by many countries in Europe.

At Service Objects, we understand that not all phone numbers will conform to an E.164 numbering plan and that many numbers will have missing country codes, which why our services make use of a wide variety of datasets and are flexible enough to intelligently identify a country.

IP address component

Not all companies capture a contact’s IP address, but when they do they are most likely capturing it via the web form the contact used to submit their information. The captured IP address and the location for that IP is often for the registered owner of the IP, so if the contact filled out a web form from their home computer then it is likely that the IP is for their Internet Service Provider (ISP). If they filled it out from their office computer, then the IP address may belong to the business or to the business’s ISP. IP based geolocation systems will commonly return a general location for the owner of the IP, which in most cases is the end user’s ISP.

There is often a misconception that IP based geolocation services will always return an end user’s exact location. For example, that the IP address assigned to a mobile smartphone can alone be used to pinpoint and track the phone’s exact location. This is simply not true. In most cases, IP based geolocation services will return the city and/or the metropolitan area for where the IP address is commonly served. Subscribers will generally be located within the serviceable area of their ISP, and so the IP based location can be used in confidence to identify the region of the end user.

Identifying anonymous users

If a contact used a Virtual Private Network (VPN) or Proxy connection, such as a Tor network, when filling out a form then that means that the end user’s true IP address was masked and it was not captured. Some users will make use of methods such as these to try and remain anonymous and prevent others from capturing their true IP address. These methods are not only used to mask a user’s true location, but they can also be used to make a user appear to be from somewhere they are not. This is commonly done to circumvent region locked sites and services, however not all VPN and proxy connections are used for this purpose. Many businesses make use of VPN and proxy connections to connect their employees, sites and services from various regions, including remote employees.

A service like DOTS IP Address Validation is capable of identifying proxy related IP addresses as well as IP addresses associated with malicious activity. By leveraging this data, the country detection algorithm can determine if the IP is trustworthy and if the IP based location is genuine.

Email component

The email address component uses the contact email address to identify where in the world the mail servers are located. The location of the mail server should not be confused with the location of the mail sender; after all, one of the benefits of email is that you can send and receive it from just about anywhere an internet connection is available. This means that a contact may not necessarily be anywhere near where the mail server is located and could potentially reside in an entirely different country. It’s also worth noting that the domain name, including the Top Level Domain (TLD), can be misleading.

For example, let’s suppose we have an email with a domain that consists of Spanish words and the TLD country code for Spain (ES), like: ejemplo@una_palabra_espanola.es

While the above example email address may appear to be for a contact for Spain, the company could instead be hosted or even located in another country, such as the USA. Another possibility is that the company is located in one country and has their email handled by a provider in another. It is quite common for businesses to outsource email duties to specialized email providers.

Some domains have mail servers located in multiple countries and regions and are not tied to a single location. So, email addresses alone cannot be used to accurately and confidently identify a contact’s country, as doing so would be too far-reaching. However, the country or countries for the email component can be used in some cases to help identify a single country when used in combination with other contact data.

Which country is best

As you can see, each contact component is carefully analyzed to the point where a country may be singled out for each one, but the next step is to now determine which country best represents the overall contact. By taking the countries that are related for each component and carefully weighing their relevance as well as cross-examining them we can in many cases successfully identify the single best country that best exemplifies the contact.

As previously mentioned, contact components like the Address and Email can result in more than one country. The country detection algorithm takes all possible countries into account, so even though a single component may not have a clear country winner, a best match can be found between all the components. Some components have a stronger influence than others. For example, the IP address and email address components do not have as much influence as the address and phone components since they are not always directly related to where a contact resides.

In general, the more complete the contact information is, the more the country detection algorithm will have to work with, choosing a best overall country. However, even when a few contact components are available, the service will still be able to make do with the information it receives.

I have a superpower that most people don’t have. In my position here at Service Objects, I have had the privilege of being a fly on the wall with many companies while helping them create clean and validated data. So I know, perhaps better than most people, what businesses go through as they wrestle with how to improve their data quality and ROI.

In this article, I would like to take you inside the mind of a typical business as they look at their data challenges, and what happens when they decide to work with us. You probably know what *we* think about our products, of course – but the only opinions that really matter are those of our customers. So let’s look at a hypothetical case study of a typical business, based on my many actual interactions with prospects and clients.

Discovering your data quality issues

I was a new hire at my company when it all started. We were a large manufacturing firm serving the business-to-business market, and things were ramping up. We had a website where people could make orders and sign up for a catalog, as well as opt-in for email alerts when special items would go on sale or we had an email campaign.

My job was ensuring that the data we were collecting was accurate and up-to-date. And I found that this data was a mess! For one thing, we had lots of inconsistencies in our contact data. Sometimes street suffixes and street prefixes were abbreviated, and sometimes they weren’t. Sometimes they were in all upper case, or all lower case, or sometimes mixed case. The same things were also true for the state field. One of the complaints from management was that the shipping labels on our catalogs looked very bad.

More importantly – particularly from a financial standpoint – the team was getting frustrated with the amount of “return to sender” items we were receiving. This gave us a few problems to solve. First, I knew that our data input forms would need to be updated, but I also quickly realized that somehow forcing our users to always provide good consistent data was a pipe dream. Standardizing the data alone wouldn’t fix the problem of returned catalogs, so I knew that this really came down to getting our existing data standardized and validated, as well as making sure new addresses coming into the system were also high quality and valid. Address validation was the key to solving this.

Finding an address validation solution

Now a decision needed to be made: do we get our software engineers involved and build it ourselves, or do we get something off the shelf? I had faced this dilemma before in previous positions. For small tasks, building solutions from scratch is OK and can save money in the long run. But I have found that when trying to implement solutions for larger projects, finding products off the shelf can have a much greater impact.

You see, the problem really wasn’t that we couldn’t update our forms to help standardize the inputs. It was a small job to switch data entry fields from open text fields to dropdown selectable options. The tough part was the address validation component. We were experts with our products, but it really didn’t make sense to try to be experts with address validation. Address validation is no simple task, and I knew the right solution would be finding a company that had a lot of experience with it.

Naturally, like everyone else, I did a Google search for “Address Validation”. I was looking for three main things for our solution. First, they had to be experts. Second, they had to have integration options, because I knew I wanted a solution that integrated with the forms we had on the website. I also didn’t want to have to build out a process to clean the existing addresses: I wanted to simply send the data over in a file have it cleansed and returned to me to repopulate our database. And third, I wanted service. I wanted a company that was available to talk when I needed to talk, and would respond quickly to my email questions.

It turned out that Service Objects had all of this and more. I had access to experts with solutions to my problems – not just people selling solutions, but also the people building and integrating these solutions. And it turned out that our team didn’t really need much help integrating the Service Objects’ Address Validation solution into our website. The documentation and sample code were clear, and with just a free trial key we were able to get up and running. Then all we needed to do was switch to a live production key, and we were done! I really like it when things are that easy.

When it came to validating the existing addresses, we wanted a solution where we could upload our data and get it cleansed and returned to us, as I mentioned earlier. After talking it through with a Service Objects representative I realized that we just didn’t have one data set to cleanse. In addition to our direct data set needing to be validated, we would also be importing address data from other divisions of the company on a periodic basis.

Here it would be nice to set up a process where we could regularly deliver a file and have it processed. After talking it over some more, Service Objects told us that they did do one-time processing, But also offered an automated batch service where we could upload a file that would get processed and returned to us automatically. This was exactly what we needed.

Moving on to email validation

So we integrated address validation into our system and got the automated batch process going, and everything was running like a well-oiled machine. Address data was coming into the system as clean as it could be, and the issue with returned catalogs disappeared. Next, I wanted to tackle the issue we were having with our email alerts that visitors could sign up for.

It was being reported that we were getting a lot of bounces on the email offers we were sending. When I examined the email data, some of the reasons were obvious. I was finding things like emails that appeared to have been entered by the user mashing a bunch of random keys on their keyboard. But the problem was larger than that – we were also getting bounces from emails that appeared legitimate.

I recalled from my conversations with Service Objects that they were experts in several types of data validation. Besides address validation, for which they had Canada and international products as well, they also had phone validation services, geocoding services, lead and ecommerce services, demographics services and more. But most importantly, for my purposes, Service Objects had a solution for real-time email validation.

The solution I was looking for would be one where we could validate an email at the point of entry into our system, and also one where we could send automated batches to get validated before we do an email campaign. The automated batches would also help us with the multiple email lists that we purchased or rented. The Service Objects’ Email Validation service was perfect for this and was just as easy to integrate as the address validation service was.

Lessons learned

This case study tried to identify a few phases companies go through when they try to validate their data. They involve identifying what the problems are, and sometimes these problems are not always obvious. Moreover, validating your data once does not mean that you are done. For starters, email addresses change and people move. Also, if your records are of people in the European Union then personal data needs to be as accurate and current as possible, particularly in light of their new GDPR regulations.

Stale or incorrect data is your enemy, and we have the services you need to keep it valid. After identifying the problem, most companies look next at how and who should solve the problem. As I mentioned in the case study, there are reasons to build out solutions in-house, but when you get into the realm of data validation it is really best left to the experts.

There are additional benefits to buying off the shelf with us besides our capabilities and expert support. You also benefit by always having the latest and greatest versions of our products. When we update our services, these updates are often injected into the operations you are already using and can provide for faster response times as well. Also, nearly every customer goes through a discovery phase where they are learning about a service and all the different data points that it can return. There are a lot of terms involved, and unless you are an expert some of them can be confusing. In cases like these, our assistance can make a big difference.

We’re here to help

Above all, we are there with our customers every step of the way. And there are often times when some expert advice can help you get more out of our services.
For example:

• For email validation, you may want to know what greylisting is or what catchall means, and how knowing these data points can help you.
• For address validation, it may be very helpful to know when an address is classified as residential, so you can better define shipping costs.
• You may not be aware of how some of our capabilities could directly profit your specific operations, such as demographic analysis or lead validation.

We are always here to help you understand our capabilities, as well as helping you through the integration process. Integration is usually the last main phase in the process. We do find that most organizations have few real issues when it comes to integration, but there are unique cases that we work through together. We have lots of documentation and sample code to help with integration, and you can count on us as a resource for help.

This hypothetical case study has a lot in common with our real-life experience with customers: they come to us with data quality issues that are costing them money, hurting their productivity or damaging their brand image. And then we collaboratively help them find solutions to these problems and make it look easy. We would love to help you too!

Contact us any time for a no-obligation discussion on what we can do for you.

Is a mailing address the same as a physical address?

No, not always.

In general, a mailing address can often be the same as a street address, but this is not always the case. To understand why, we must first acknowledge that the two types of addresses are often defined and regulated by two separate authoritative entities that generally serve different purposes.

Different purposes

A mailing address, or postal address, is often regulated by postal authorities that are commonly associated with services related to the sending and receiving of mail. For example, in the US this would be USPS. In the United Kingdom, Royal Mail. Deutsche Post DHL Group for Germany and JP Post or Japan Post (日本郵政 Nippon Yūsei) for Japan. These postal authorities can be public government agencies, like the USPS, or privatized companies like Royal Mail, Deutsche Post and JP Post- which were sold off by their governments.

A physical address, sometimes referred to as a street address, is used to describe where a place is geographically located. It often pertains to a geographic location under the jurisdiction of an administrative area or region that has some government function. The physical address should have a set geographic boundary that is recognized and governed by an administrative area. If an address resides in an incorporated area then its municipality is generally responsible for providing some public services, such as law enforcement, public schools, sanitation, water works etc. If an address resides in a rural and/or unincorporated area, then sometimes these services are provided by the governing state, territory, province, county etc. Sometimes certain services are not available at all.

Location, location, location

Where a physical address is geographically located will often determine what public and private services it has access to. For example, a rural address may not have access to readily available public transportation or high-speed internet, whereas an address in a metropolitan area likely would.

In the US, it is the job of the US Census Bureau (USCB) to collect and produce data about the people. Both public and private agencies rely on the various datasets produced by the USCB, such as geographic and demographic data, to help make informed decisions. The USCB produces various Topologically Integrated Geographic Encoding and Referencing (TIGER) datasets that are designed for use with Geographic Information Systems (GIS) and various mapping projects. TIGER products are spatial datasets used to describe geographic features such as boundaries, roads, address information, water features, as well as legal and statistical geographic areas.

TIGER products are widely used in many US related geolocation solutions, including our own DOTS Address Geocode US service, and are considered a standard when it comes to working with geographic locations and features in the US and its territories. TIGER data, along with other topological geographic mapping datasets, can be used to help geocode a physical address to varying degrees of accuracy.

Choosing the right route

Mailing address datasets are generally used to help facilitate and ensure the delivery of mail, and they are not necessarily one-to-one comparable with geographic datasets like TIGER. The main reason being that these datasets are intended to serve different purposes. Let’s take USPS ZIP Codes for example. USPS ZIP Codes are not geographic areas. They are a collection of mail delivery routes and they help identify individual post offices and delivery stations that are associated with mailing addresses.

ZIP Codes help the USPS determine the best route for delivering mail. It is not uncommon for a physical address, that is geographically located in one locality, to be assigned to a different locality in its mailing address. This is common for areas where a single post office or delivery station may serve multiple localities.

Not all mailing addresses are physical addresses

Here’s an interesting example of an address that is physically or geographically located in one state of the US, but the mailing address has it listed as being in another.

Physical Address:
25777 Co Rd 103
Jelm, CO 82063

USPS Mailing Address:
25777 Co Rd 103
Jelm, WY 82063-9203

Using Google Maps to inspect the address and the surrounding area, we see that the location is near a state line, but the address is clearly in Colorado and not in Wyoming.

According to Google the physical address is approximately six miles from the Wyoming and Colorado state line. When we investigated other addresses in the area we found that they too had a mailing address that said they were in Wyoming.

When we reached out to USPS to inquire about the addresses they acknowledged that they were indeed geographically located in Colorado; however, their ZIP code is associated with a USPS Post Office located in Jelm, Wyoming and that is the reason why the mailing addresses are for Jelm, Wyoming and not Jelm, Colorado. It may be confusing to base an address’ location on where it’s post office is located, but logistically it makes sense for the postal authority, USPS.

It’s also not uncommon for some rural areas to use general delivery, where mail is not delivered to a recipient’s physical address and it is instead kept at a post office that the recipient will go to and pick it up. If the post office is located in a different locality, then the recipient’s mailing address would be different from their physical address.

Other examples of mailing addresses that are not physical addresses include:

• Post Office Box (PO Box) and Private Mailbox (PMB) – Many individuals and businesses use PO Boxes and Private Mailboxes as an alternative to their physical address. Postal Agencies like UPS offer PMBs as Personal Mailboxes, and while they do advertise that their PMBs include a street address it still is not the recipient’s physical address.
• Centralized Mailboxes – Also known as cluster mailboxes or community mailboxes, are basically a large communal mail box made up of multiple individual boxes clustered together. The mailing address for a centralized mailing box does not have to reflect the recipient’s physical address as each box in the cluster will have its own unique identifier.
• Unique ZIP Codes – These are ZIP codes that are assigned to some single high-volume addresses such as universities, government agencies and some large businesses. Postal carriers will deliver mail to the organization’s mail department, and it then delivers the mail to the final destination which may be in an entirely different geographic location.
• Military Addresses – Are used to route mail for military mail services, such as the US Military Postal Service (MPS), the British Forces Post Office (BFPO) and the German Armed Forces (Feldpost). Civilian postal carriers deliver mail to military post offices which then perform the final delivery.

Which address to use

For some people, their physical address is the same as their mailing address and when asked for their address they don’t have to worry about which address to give because they are both the same. For others who don’t have matching mailing and physical addresses, some consideration is needed. If the purpose of the address is to send mail to it, then the mailing address should be given. If the address is needed to locate where a place is geographically located, then the physical address is needed.

The answer should be clear but sometimes there are misconceptions and confusion and on the behalf of the party requesting the address. The party asking for the address may simply be unaware that not all mailing addresses are physical addresses and that not all physical address have mailing addresses. If the intent on how an address is to be used is not made clear, then the person giving their address could potentially give the wrong one if the two are not the same. Sometimes the person giving the address will be sure to specifically ask if they want the mailing address or the street address, but the party asking may be unaware of the difference and inadvertently ask for the wrong one.

Shipping address and physical address

There can also be some confusing cases when it comes to the terms billing address and shipping address. Likely, the billing address will be a mailing address, but what about the shipping address? Let us suppose that a customer wants to have a package delivered to their doorstep. They want to enter their physical address, but they know that USPS does not deliver mail to their physical address. However, they do know that UPS does deliver to their door, but they are not sure about FedEx. If the site they are purchasing from gives them the option to choose the shipping carrier then that helps, but if it doesn’t then which address do they choose to give? Worse yet, what if the customer is unaware that their physical address is undeliverable?

Helpful tools

When businesses and organizations work with addresses it is important to know where they are located and if they are valid and deliverable. Otherwise, they risk making uninformed decisions that can end up wasting valuable resources like time and money and damaging customer relationships. That is why Service Objects provides various address related products to help prevent mistakes and reduce waste. Our services can quickly correct and standardize address to help determine where they are located and if they are valid and deliverable.

Test drive any of our address products with a free trial key and see how we handle these scenarios.

Service Objects has been providing USPS CASS-Certified Address Validation services for over 17 years. Over this time, we have developed one of the best systems for validating, correcting and appending useful data points to US addresses. Our address validation service specializes in fuzzy matching for address corrections and, more importantly, making sure that each and every address provided is NOT changed to something unexpected or incorrect.

While our address validation service is top notch, the focus on both USPS and accuracy introduces necessary limits on how we treat addresses that might be messy or missing key elements.  Which brings us to one of Service Objects more under appreciated offerings, our DOTS Address Detective service.

 

Address Detective and its Operations

Address Detective was born from a need to help our customers fill in the gaps and make sense of their very messy and/or incomplete addresses. This service is an ever-evolving collection of address utilities designed to help with various problems that can arise from these messy or incomplete addresses.  Currently, there are three operations available that each solve uniquely different problems.  It is helpful to understand what each operations does and how it can be best used to correct an address before you even start your implementation.

Operation Name	Description
FindAddress	Uses name and phone number to assist with the processing of very messy or incomplete addresses.
FindAddressLine	Takes inputs that might be jumbled into the wrong columns and parses them into a usable result.
FindOutlyingAddresses	Digs into alternative data sets from USPS to identify addresses that while not deliverable may still be good addresses.

 

Address Detective’s Operations Explained: FindAddress

The flagship operation of Address Detective is FindAddress. This service was designed to help clients with addresses that may be so messy or incomplete that they may not be obviously fixable, even to the human eye. FindAddress is given free reign to be more aggressive in its basic operation but also makes use of other data points like name, business name or phone number to assist with the validation.

Behind the scenes the service will dig into public and proprietary data sources to connect the dots between given data points to return an accurate result. The service is not designed to return an address if one is not given, its designed to analyze data given with cross referenced values in order improve or validate a normally unvalidatable address.

For example, perhaps the desired address is:

Taco Bell
821 N Milpas St
Santa Barbara, CA 93103

But what if the input address is something like:

Milpas Street
Santa Barbara, CA 93103

Clearly, not enough information is given for this address to pass validation. A house number is always required. DOTS Address Detective is able to use either the name “Taco Bell” or the phone number, (805) 962-1114, to properly identify and standardize the right location. The partial input values given are still important to compare back and make sure the most accurate result is returned.

What about addresses that are even messier with misspelled or incorrect data:

Milpaaaas Str
Santa Bar, CF 93103

Given either “Taco Bell” or (805) 962-1114, there is still enough information to go on to compare, cleanse and return the correct standardized result.

 

Address Detective’s Operations Explained: FindAddressLines

The second operation, FindAddressLines, solves a very different problem. We would often run lists of addresses for clients where they would give us a .csv file of addresses with data points that were in unexpected locations. Perhaps they tracked multiple address lines in which the third or fourth address line contained the normal “main” address line.  For example; what if they had something like this:

If the user does not know that the needed address in this case is Address4 (123 Main Street) its possible they may be sending the address: Johnson Paper Bag Company, C/O John Smith, Santa Barbara, CA, 93101 which obviously would not be a valid address. Perhaps they have an even bigger problem and there was an error in how the address was stored or a corrupted database leading to something like this:

Both of these cases are solved by using the FindAddressLines. FindAddressLines takes in a generic list of Address inputs and analyzes them to figure out how to properly assign the inputs to the correct fields.  The result is then validated, corrected and standardized as a normal address. While there is some synergy with the FindAddress operation here, in order to properly parse out an address, the address would have to at least look like an address.  FindAddressLines would not be able to do anything with an address of “Milpas Street” as opposed to “821 Milpas Street”.

 

Address Detective’s Operations Explained: FindOutlyingAddresses

The final operation is FindOutlyingAddresses. This operation cross references several massive non-USPS datasets to find likely good addresses when USPS cannot. While our Address Validation service is designed to accurately identify deliverable addresses and contains the vast majority of US based addresses it does not cover everything. Pockets of addresses either in very rural areas or some well known areas like Mammoth Lakes (California) do not have deliverable houses, all mail is delivered to a local post office for pickup by residents.

FindOutlyingAddresses aims to fill in the blanks of these hard to find addresses. They may not be important for mail delivery but still play a vital role in identifying lead quality. While the data returns for this operation are not as complete as our Address Validation service, we will attempt to identify the data points at the lowest level we can. Do we know the house number exists? Maybe the house number does not exist but we know the street does? This operation will return as much useful information as it can about these locations.

 

Address Validation + Address Detective = Powerful One-Two Punch

One of the best ways to ensure you have accurate and up-to-date address information is by combining our Address Validation service with Address Detective. This combination allows many of our customers to identify and repair addresses that they would have normally discarded.  We are always happy to help our clients set up this powerful one-two punch.

In its most basic form, we use Address Validation to correct and verify all addresses. Addresses that could not be validated or corrected by the initial, stricter validation process, would be sent to our Address Detective service where supplemental information helps ‘solve’ the address and returns a viable address.

 

What is next for Address Detective?

DOTS Address Detective is an ever-evolving collection of operations that were created to meet the needs of our clients. We are always looking for new algorithms, data sets and features we can add to meet these needs and help clients recover and update even more addresses.

One of the more recent requests we are working on is helping identify GDPR exposure.  Our clients need to know if a contact record resides in any of the European Countries that are covered by the far-reaching privacy protection regulations of the GDPR. It is always a little more fun to solve real-world problems that our clients are facing and we are excited to be launching a new international address detective service in the coming week to help.  (By the way, if you think it is simple to identify a country by an address, try taking this Country Quiz.)

We encourage clients and prospects alike to reach out and let us know if they have a need that does not seem to be covered by one of our current products.  Share your needs or try it today to see what DOTS Address Detective can do to help!

 

Some things are just better together. Like milk and cookies. Or peanut butter and jelly. Or, if you do online sales and marketing, ecommerce platforms and data validation services.

Integrating live, real-time validation services right into your ecommerce platform is easy to do, and gives you a whole host of benefits including promoting sales, preventing fraud and ensuring top-notch customer service and product delivery. This article explores a rich smorgasbord of benefits you can engineer into your own shopping cart platform – adding any of them will make your life easier:

Localize the online shopping experience

Even before a customer has a chance to look at your online store, you can curate its contents based on their location, using IP Address Validation to see where they are coming from. Detect their region or country and customize the language, currency and taxes for your online store to match. Or use their location to offer a ski sale for Colorado and surfboards for Hawaii. Geolocation can also be used to change your product mix to match local regulations and sensibilities. Another use we have seen is presenting customers with the appropriate terms of use and privacy policy based on their location, helping you maintain privacy compliance.

Keep online fraud at bay

Our IP Address Validation tool also lets you detect the location of a visitor to implement additional security rules for high risk countries, such as only allowing certain types of payment or restricting sales to high-fraud destinations. You can also compare the location of the IP address against the billing and shipping address, and flag discrepancies for further review.

Other tools to help reduce online fraud and chargebacks include:

• Using BIN Validation to identify high risk cards like prepaid and gift cards, especially for multi-payment and membership products and services. This tool can also help you compare the issuing bank and country with the billing and shipping location.
• Using Email Validation to flag questionable or fraudulent email addresses.
• Using GeoPhone Plus to match the address for a customer’s phone number against their billing and shipping details.

Finally, our advanced Order Validation tool is a comprehensive and composite service for fraud monitoring, performing multi-function verifications including address validation, BIN validation, reverse phone lookup, email validation, and IP validation. Our proprietary algorithm performs over 200 tests and returns a 0-100 quality score on the overall validity and authenticity of the customer, flagged for pass, review or fail.

Get accurate sales tax information

For customers in the United States and Canada, our FastTax product can provide you with up-to-date sales tax rates, as well as identify the correct tax jurisdiction and boundaries based on location. In some jurisdictions tax rates even vary on different sides of the same street, and we can catch this!

Ensure deliverability

By checking addresses, you can ensure cost-saving delivery rates, avoid returned shipments, and ensure customer satisfaction by getting their order to the right place on time.

Our flagship Address Validation services for the United States, Canada and international addresses validate and correct addresses in real-time to ensure customers have entered a correct (and deliverable) address for the USPS, FedEx and UPS. Our US service is CASS certified and includes Delivery Point Validation (DPV) to verify an address is deliverable, Residential Delivery Indicator (RDI) to identify residential versus business addresses, and SuiteLink (SLK) to add secondary suite information for businesses.

For Canada, we can validate and correct addresses whether they are in English or French, with an output that meets Canada Post standards. For international addresses, we can instantly correct, standardize and append addresses for over 250 countries, adapted to each country’s postal formats and cultural idiosyncrasies. You can also use our address validation tools to create an address suggestion tool that includes validation.

Use the right delivery approach

Another use for US address verification is that it can identify general delivery address (i.e. PO boxes). Some sellers choose not to deliver to PO boxes, present different shipper options, or ask the buyer for a different address. Conversely, it can also detect incorporated areas versus unincorporated areas where the USPS will not deliver, allowing you to create logic that doesn’t present the USPS as a delivery option for these types of addresses.

In addition to improving deliverability, these verifications can also improve your bottom line by keeping more orders in your online shopping cart: a frequent customer complaint is being told that they cannot order from a site because USPS-only verification logic says their address is undeliverable. UPS and FedEx can normally deliver to most US doorsteps, and our capabilities can help you close these sales as well.

Ensure accurate email addresses

Our Email Validation service helps make sure that you capture the correct email address at the time of entry, ensuring that all future communications reach the customer. It catches common typographical errors (like gmial.com instead of gmail.com) as well as bogus email addresses. And when accounts are created using the customer’s email address as the primary key or account id, this tool helps ensure that you can catch mistakes while they are still easy to correct.

Improve your customer service and marketing

The benefits of integrated data validation don’t stop when an order goes out the door. Regular validation and cleaning of your contact data, for customers and prospects, will streamline your future marketing efforts – not to mention helping you comply with consumer protection and privacy regulations. And our customer insight and demographics tools can help you leverage this contact data as a valuable asset for serving your customer base even better.

For each of these capabilities, it is easy to integrate our services into almost any ecommerce platform. Most of these systems offer a plugin, RESTful API, or exposed interface to integrate with our services, including cloud connectors and web hooks, and any application that can call a web service can obtain output from our services in either XML or JSON formats. And we recognize that not all shopping carts are built alike, with needs varying from mom-and-pop online stores to full-scale enterprise level platforms, so take advantage of our extensive documentation and support to get you going.

Of course, our tools also stand alone, with convenient batch processing options for cleaning up legacy data in list form as well as quick lookup capabilities. But if you have an automated solution for your ecommerce capabilities, our services can power up the accuracy, quality and productivity of your marketing and sales efforts. Learn more on our website, or contact us anytime to learn more!

Do we support your ecommerce system? Yes we do!

Here is a list of many of the popular ecommerce systems that we interface with.

2Checkout (formerly Avangate)	LemonStand	Spark Pay
3D Cart	Magento (recently acquired by Adobe)	Squarespace
Big Cartel	Microsoft Commerce Server	SuiteCommerce
BigCommerce	Miva	Symphony Commerce
CloudCraze	OpenCart	Systum
CommerceHub	Oracle Commerce Cloud	Volusion
Demandware	osCommerce	VTEX
Drupal Commerce	Paddle	WebSphere Commerce (WCS) (IBM)
Ecwid	Prestashop	Weebly
FastSpring	Salesforce Commerce Cloud	Wix
InfusionSoft	SAP Hybris Commerce	WooCommerce (WordPress plugin)
Kibo	Shopify	X-Cart

And new interfaces are coming online all the time, so if you don’t see yours on the list, talk to us!

 

 

Data gets stale over time. You rely on us to keep this data fresh, and we in turn rely on a host of others – including you! The information we serve you is the product of partnerships at many levels, and any data we mine or get from third party providers needs to be up-to-date.

This means that we rely on other organizations to keep their data current, but when you use our products, it is still our name on the door. Here at Service Objects, we use a three-step process to do our part in providing you with fresh data:

Who: We don’t make partnerships with just anyone.  Before we take on a new vendor, we fully vet them to be sure this partnership will meet our standards, now and in the future. To paraphrase the late President Reagan, we take a “trust but verify” approach to every organization we team up with.

What: We run tests to make sure that data is in fact how we expect it to be. This runs the gamut from simple format tests to ensuring that results are accurate and appropriate.

When: Some of the data we work with is updated in real time, while other data is updated daily, weekly, or monthly.  Depending on what type of data it is, we set up the most appropriate update schedule for the data we use.

At the same time, we realize this is a partnership between us and you – so to get the most out of our data, and for you to have the best results, we always suggest that you make sure to re-check some of your data points periodically, regardless of whether you are using our API or our batch processing system. Some of the more obvious reasons for this are that people move, phone numbers change, emails change, areas get redistricted, and so on. To maintain your data and keep it current, we recommend periodically revalidating it against our services.

Often business will implement our services to check data at the point of entry into their system, and also to perform a one-time cleanse to create a sort of baseline. This is all a good thing, especially when you make sure that data is going into your systems properly and is as clean as possible. However, it is important to remember that in 6-12 months some of this data will no longer be current.  Going the extra step to create a periodic review of your data is a best practice and is strongly recommended.

We also suggest keeping some sort of time stamp associated with when a record was validated, so that when you have events such as a new email campaign and some records have not been validated for a long time – for example, 12 months or more – you can re-run those records through our service.  This way you will ensure that you are getting the most out of your campaign, and at the same time protect your reputation by reducing bounces.

Finally, here is a pro tip to reduce your shipping costs: in our Address Validation service, we return an IsResidential indicator that identifies an address as being residential or not.  If this indicator changes, having the most recent results will help your business make the most cost-effective shipping decisions.

For both us and you, keeping your data fresh helps you get the most out of these powerful automation tools. In the end there is no specific time span we can recommend for verification that will suit every business across the board, and there will be cases where it isn’t always necessary to keep revalidating your data: the intervals you decide to use for your application will depend mostly on your application. But this is still an important factor to keep in mind as you design and evaluate your data quality process.

To learn more about how our data quality solutions can help your business, visit the Solutions section of our website.

What is one of the biggest growth industries in the United States today? Hint: It isn’t something most of you would want your kids to major in at school, unless you want them to go to the state pen instead of Penn State – because this rapidly growing industry is online fraud.

The costs of eCommerce fraud are staggering

Estimates vary, but recent figures from DigitalCommerce360 project the value of eCommerce fraud nearly doubling from US $10 billion to $19 billion between 2014 and 2018, as the eCommerce market continues to grow from a historic peak of US $2.3 trillion in 2017. One particular area of fraud, account takeovers, jumped 45% in Q2 of 2017 alone according to the Global Fraud Index, and these fraudulent pirated accounts represent one of the top three types of online retail fraud.

A subtle but equally important issue is what the fear of online fraud costs you and your business. According to a recent fraud benchmarking survey from CyberSource:

• Domestic and cross-border orders have exactly the same rates of fraud among companies surveyed – just under 1% – however nearly twice as many cross-border orders get rejected, costing valuable revenue as well as damaging customer relationships.
• The costs of manual transaction review are one of the major financial consequences of online fraud. Nearly 80% of companies conduct manual reviews, impacting an average 25% of their transactions – and yet nearly 90% of these transactions are ultimately accepted.
• The costs of manual review hits smaller companies particularly hard, where companies under US $5M in annual revenue review nearly six times the percentage of transactions (47%) as companies greater than $100M (8%).

The uptake of all of this? Guarding against eCommerce fraud is really a two-pronged effort: reducing online fraud itself, and reducing the revenue lost to the indirect costs of fraud. For both of these issues, the key is implementing effective automated solutions.

Technology plays a key role in preventing online fraud

According to the CyberSource survey, companies themselves rate three technologies among their top weapons against fraud:

Address verification: making sure an address is real, valid, and corresponds with the person making the order

Credit card number verification: making sure a credit card is legitimate and properly owned

Fraud scoring models: coming up with a quantitative score based on multifactor analysis

Other tools fall into the category of leveraging existing customer data, such as credit history checks, customer order history, or two-factor phone authentication using previous device information on file.

Cyber-fraud is growing explosively nowadays because the market for it gets more lucrative every year, and combating it requires tools that keep you one step ahead of the fraudsters. Service Objects’ fraud prevention capabilities have the advantage of leveraging authoritative up-to-the-minute third-party data, such as USPS CASS Certified® address validation capabilities, global address validation that verifies and corrects international mailing addresses to the unique requirements of each country’s postal address formats and cultural idiosyncrasies, and IP validation that helps you ensure that the origin of an online order correlates with billing and shipping locations. In addition, we offer lead and order validation capabilities using multi-function verifications that give you a quantitative quality score you can use to automate your order processing decisions.

We offer a free consultation to help you determine what tools can help protect your revenue stream. Contact us today to learn what we can do for you.

If you want to use our National Change-of-Address web service, DOTS NCOA Live, for contact address validation but are hesitant to dive in due to the complex nature of the service; this article is meant to set your worries aside. This blog will serve as a comprehensive guide to getting the most out of your NCOA Live subscription while addressing common questions, pitfalls, and recommended workflows. Additional information can also be found in our NCOA Live developer guide. With NCOA Live, businesses can easily update address information to maintain accurate and up-to-date contact records by accessing the USPS dataset of mail forwarding notifications.

Filling Out the Processing Acknowledgement Form

Before you can begin using NCOA Live, the USPS requires you to complete their simple Processing Acknowledgement Form (PAF) to access change-of-address data. Most of the fields in this form will be straightforward. You can look up your North American Industry Classification System (NAICS) code and business address here. To ensure correct PAF filing, we recommend using the USPS lookup tool to confirm your address and some of the additional details that the PAF requires. Please see the image below for reference.

Ensuring that your address has a ZIP+4 and a DPV Confirmation Indicator of “Y” will prevent any issues in the filing process.

Getting Your License Key and Service Endpoints

After successful filing the PAF, we will provide a license key and the service endpoint. These items will enable requests to the NCOA Live web service to check for change-of-addresses. Due to the flexible nature of our services, NCOA Live is accessible from almost any tool or programming language that can make a web service call. Specific coding examples for the service can be found in our developer guide’s sample code section.

We have sample code in most of the popular programming languages, including PHP, JAVA, Ruby, Python, ColdFusion, and C#, just to name a few. We can also provide customized code if needed and our Application Engineering team would be happy to answer any questions you may have about integrations and programming language-specific concerns.

Handling JobID Creation

Arguably the most challenging aspect of the NCOA Live web service is the USPS requirement that submissions for change-of-address lookups include an open JobID. The JobID links to your account and keeps track of the transactions you run. Each new JobID remains valid for one week, expiring at 11:50 pm Sunday evening. Opening a new JobID requires the following:

1. Building an array of 100-500 addresses (100 minimum to create a job)
2. Creating a personalized JobID (alpha-numeric string of fewer than 50 characters)
3. Submitting the addresses, JobID, and license key to the “RunNCOA Live” operation

After submitting the initial 100-500 records for the current week’s JobID, anywhere from 1-500 records can be processed per batch. Every transaction run during that week will operate under this new JobID. At the end of the week, the JobID closes, and we update the internal change-of-address data that powers our service. The following week, another NCOA Live operation can be initiated with a new JobID following the steps listed above.

Checking for Errors and Parsing the Response

The first step to safely parsing the response is to check for any root level errors. Root level errors are largely uncommon and generally related to issues with the service or license key. If root errors appear, please don’t hesitate to contact Service Objects and we will work with you to resolve them. If there are no root level errors, you can start working with the valid response data.

The NCOA Live response returns a result with multiple nested fields. See table below for the response fields and a brief description.

RunNCOA Live Outputs

Parent Object	Child	Values	Description
NameIn		Varies	The raw input name.
RawInputAddress	Address	Varies	The raw input address line.
	Address2	Varies	The raw input address2 line.
	City	Varies	The raw input city.
	State	Varies	The raw input state.
	Zip	Varies	The raw input Zip code.
CASSInputAddress	Address	Varies	The standardized address line.
	Address2	Varies	The standardized secondary.
	City	Varies	The standardized city name.
	State	Varies	The standardized state.
	Zip	Varies	The standardized Zip+4
	USPSFootnotes	Varies	A concatenated string of relevant 2-digit USPS "Footnote" codes that give additional information about the input address.
NCOAMatch	NameMatch	Varies	The name that matched the COA record.
	Address	Varies	The primary address line that the resident moved to.
	Address2	Varies	The secondary address line.
	City	Varies	The city name.
	State	Varies	The state abbreviation.
	Zip	Varies	The Zip+4.
	CarrierRoute	Varies	The Carrier Route code for the COA address.
	BarcodeDigits	Varies	The PostNet barcode for the COA address.
	COAFound		Whether or not a match was found in the COA data. Does not imply that a valid address could be found.
	NCOAReturnCode	Varies	The USPS's NCOALink Return Code providing additional information about the nature of the COA match.
	NCOAReturnCodeDesc	Varies	Short English description of the COA information. Longer descriptions found below.
	ExtendedNCOAReturnCode	(See below)	USPS's Extended NCOA Return Code comprising a series of key/value strings.
Diagnostics	DiscountCode	1-4	A code representing discount level.
	DiscountDescription	(See below)	An English description of the discount level.
	StatusCode	2-8	A code representing the level of quality of the input address post-validation. Higher is better.
	StatusDescription	(See below)	An English description of the level of quality of the input address post-validation.
	ServiceFlags	Varies	USPS Service Flags output explains what additional address services were run such as RDI, eLOT, etc.
Error	Type	Varies	English description of the error type. See "Error Codes" below.
	TypeCode	1,2,3,4	Unique error type code. See "Errors" below.
	Desc	Varies	English description of the error. See "Errors" below.
	DescCode	Varies	Unique code for the error. See "Errors" below.
JobID		Varies	The JobId sent to the service.

The response data comes back as a list of results corresponding to the addresses submitted. If specific address errors are detected at this level, they fall under our Domain Specific errors and apply to individual addresses. Reading the error’s description provides insight into why the service was not able to validate or return change-of-address information. Detailed notes about the individual error codes are available in the developer guide and can be seen in the table below.

Error Type 4: Domain Specific

DescCode	Description
1	Job not found for this License Key.	The job does not exist. Please try again with a different job id. *
2	Job has been closed.	The job can no longer be used. Please try again with a new job id. *
3	First transaction of a job must contain 100 records or more.	Please try again with at least 100 unique and valid addresses. *
4	Issue connecting to NCOA engine.	Please try again. If the issue persists then please contact technical support. *
5	Street not found.	Indicates that the street name was not found for the general area (city/state or zip).
6	Address not found.	Indicates that a reliable address candidate was not found. Portions of the address may be incorrect or it may be too ambiguous to return a reliable candidate.
7	Street number or box number out of range.	The address is invalid. The street and area appear to be correct but the number is wrong.
8	Multiple addresses match.	Indicates that multiple candidates were found that are equally likely given the input.
9	nsufficient address data.	Indicates that a reliable address candidate was not found. Portions of the address may be missing or incorrect.
10	DPV Lockout. Contact Service Objects immediately.	Returned for a specific type of address case known as a false positive.
11	Request cannot contain more than 500 addresses.	Please try again with no more than 500 addresses in a single request. *
12	License Key is not linked to a valid PAF Id.	Please contact Service Objects and complete a USPS NCOA Processing Acknowledgement Form (PAF) to register your license key with the service. *
13	Performing weekly NCOA data update. Please try again in a few minutes with a new Job Id.	USPS releases new NCOALink data every week and requires that we use the newest data, so we must close all jobs using the older dataset. *
14	Expired PAF agreement. Please contact Service Objects.	Your USPS NCOA Processing Acknowledgement Form (PAF) has expired. Please contact Service Objects to renew and continue using the service. *
15	Unable to create new NCOA Job. Please try again. If the problem persists then please contact Service Objects.	There was a problem creating the new job. Please contact Service Objects and notify technical support of the error. *

* This is not a billable error and it will not count as a transaction against the license key.

The flexible framework of NCOA Live’s outputs allows you to integrate the results into your application to best meet your needs. We recommend exploring the various outputs such as the RawInputAddress, CASSInputAddress, and likely the most relevant information, the NCOAMatch. Because it delivers new address information in real-time, the NCOA Live service can be easily integrated into existing workflows and databases.

Maintain Better Mailing Lists with Easy Contact Address Validation

The USPS National Change-of-Address database provides a valuable resource for organizations who depend on up-to-date contact data. NCOA Live leverages the USPS dataset of forwarding notifications with a flexible API interface to provide you with the latest address information for clients and prospects. More details on all the elements of our NCOA Live service are available in our developer guide. And we are always here to help you with any questions or integration challenges you may encounter. Don’t hesitate to reach out to us today!

 

Knowing the geographical location of contact data records is crucial for compliance with the over 100 different Data Protection laws currently in force around the globe. While Europe’s General Data Protection Regulation (GDPR) goes into effect May 25, 2018, many other international Data Protection rules and regulations already govern the collection, management and use of customer data, including Canada’s PIPEDA, Australia’s NDB, and Japan’s APPI. Meanwhile, in the US, both California and New York have already passed data protection laws, with more states likely to enact their own rules in the near future. Unfortunately, the consequences of noncompliance are significant, including costly fines and other penalties.

To help achieve compliance, Service Objects recently released Country Detective, a new service which enables businesses to correct or append country of origin information to existing contact records. Companies can try out the service by requesting a free Global Data Assessment. With more accurate information on the geographic location of clients and prospects, companies can adapt their processes and protocols to satisfy current and future Data Privacy laws.

Knowing the Location of Customers and Prospects is Key to Compliance

Because these regulations vary across different industries and regions, knowing the geographical location of contact records in a database is the first step to compliance.  Many organizations maintain large databases full of incomplete contact records. Without a solid understanding of where customers and prospects are located, businesses risk running afoul of global Data Protection laws.

Contact data is also constantly changing, making accuracy particularly challenging. For example, Convince & Convert reports up to 34% of Americans will create a new address within the next year. According to USPS, mail determined to be “undeliverable as addressed” costs the Postal Service about $1.5 billion per year.

US businesses already lose more than $3.1 trillion every year due to bad contact data, and the newest slate of global data protection laws will only add another layer of expense. That’s why it remains critical that companies maintain up-to-date contact records.

“Contact information ages incredibly fast, and it remains critical that organizations take a proactive approach to data management,” says Geoff Grow, CEO, Service Objects.

Contact Data Quality is Key to Reducing Liability

Service Objects’ Country Detective service is designed to help businesses comply with Data Protection laws around the globe. The service will append and correct the country in each contact record and evaluate other data points to deliver an overall quality score. The free Global Data assessment is intended as an introduction to Country Detective by allowing organizations to identify and, if necessary, correct the country information for their contact records. To get started, businesses can securely send a list of 500 contact records and results will be delivered within 1-2 business days.

“We know that many US organizations have a large percentage of customer records that are currently missing country data, which is the first step to achieve compliance with data protection laws,” says Grow. “Our Country Detective service will give businesses the information they need to determine which of their contact records have the greatest liability.”

 

Once upon a time, customer service and support operations were viewed as the “complaint department” – a back-office function, a necessary evil, and above all a cost center whose role should be reduced as much as possible. These days, it has become increasingly clear that businesses must prioritize data quality. As Thomas Redman advised is a recent guest post, “Getting in front on data quality presents a terrific opportunity to improve business performance.”

While some organizations still have a break/fix mentality about customer support, the very best organizations now view their customer contact operations as the strategic voice of the customer – and leverage customer engagement as a strategic asset. Thanks to tools ranging from CRM and social media, many businesses manage their customer experience as closely as they manage their products and services.

The Strategic Role of Data Quality

This leads us to an important analogy about data quality. Like the “complaint department” days of customer service, many organizations still view data quality as little more than catching and fixing bad contact data. In reality, our experience with a base of nearly 2500 customers has taught that data quality plays a very strategic role in areas like cost control, marketing reach, and brand reputation in the marketplace.

This worldview is still evolving slowly. For example, according to a 2017 CIO survey by Talend, data quality and data governance remain the biggest concerns of IT departments, at 33 and 37 percent respectively – and yet their top priorities reflect more trendy objectives such as big data and real-time analytics. And back in 2012 Forrester vice president Kate Leggett observed that data quality often remains the domain of the IT department, and data projects for customer service rarely get funded.

Meanwhile, data quality has also become an important component of customer experience. Leggett notes that instead of an IT-driven process of “cleaning dirty customer data,” organizations should reframe the conversation towards the impact of data quality on customer-facing functions, and understand the connection between investments in data quality and customer service metrics.

Here at Service Objects, we see three key areas in the link between data quality and customer experience:

Customer Engagement

When you have good data integrated with effective CRM, you have the ability to market appropriately and serve customers responsively. You can target your messages to the right people, react responsively in real time to customer needs, and create systems that satisfy and delight the people you serve.

Service Failures

Mis-deliver a package because of a bad address, and you make a customer very unhappy. Do things like this even a small percentage of the time, and you gain a reputation as a company that doesn’t execute. Keep doing it and even many customers who haven’t been wronged yet will seek other options where possible, because of the “herd mentality” that builds around those who do complain publicly and on social media.

Strategic Visibility

Your customer data is an important asset that gives you the ability to analyze numerous aspects of your customer relationships and react appropriately. It holds the knowledge of everything from demographics to purchasing patterns, as well as their direct feedback through service and support. Having accurate customer data is central to leveraging this data strategically.

One heartening trend is that more organizations than ever now see the connection between data quality and their customer relationships. For example, one 2017 article in PharmExec.com cited a European customer data survey showing that nearly three-quarters of life sciences respondents feel that having a complete and real-time view of customers is a top priority – while only 40% are satisfied with how well they are doing this. We are seeing similar figures across other industries nowadays, and view this as a good sign that we are moving over time towards a smoother, more data-driven relationship between organizations and their customers.

“Can’t you just add that feature today!?”

“Can you add a simple update for this!?”

“It’s obvious, it really shouldn’t take very long to implement!”

Software developers hear statements like this more than about half a million times over their career.  It raises my eyebrows every time I hear it, typically giving me a little chuckle inside. In all honesty, it is not a surprise that those kinds of inquiries come up and that they come up as often as they do. After all, these queries come from people that do not code so, from their perspective, the questions seem legitimate.

Errors, Intent and Responsive Address Validation

Fundamentally, these are legitimate questions. The misconceptions that trigger this type of confusion often stem from how well humans can quickly find patterns, errors and solutions. So rapidly, in fact, many problems appear to have “fast” or “obvious” solutions.

For example, to us, it may seem obvious that in our Service Objects address the typo “Cta Street” should be “Cota Street” or “Santa Barbra” should be “Santa Barbara.”  These errors are relatively easy to identify, fix and classify right? For humans, the answer is yes. For a computer, on the other hand, the answer is, well…maybe.

At its heart, the issue involves underlying questions about conceptual intent and programming capabilities. For example, when the name of a city is corrected, what does that mean for the data related to the corresponding physical address? Does St. Louis being changed to Saint Louis maintain the fidelity of the locational intent? What about changing Santa Barbara to nearby Goleta? Would these solutions fall within what would be expected behavior?

While both actions result in changes to a piece of information, each solution is based on a different procedure. The first follows a standardized correction of the name of a specific location, which is a type of change to the input. The second, on the other hand, signifies a change in the place itself.

Variations on a Standard: Address Line 2

When it comes to address validation, there are more than enough address variations to examine that constitute a standard address format, and that’s just talking about Address Line 1.  Though Address Line 2 is not a standard address field, it has been a custom to see that field in one of it’s many variations on forms when we fill out our address.

Address Line 2 has often left users confused as to what information should be included in that field. While many argue Address Line 2 is designed for apartment numbers, suites, and similar secondary information, there is no consensus. In fact, the USPS does not recognize Address Line 2 as a standard address field.

Reactive Address Verification

In practice, the field is often used for apartment and suite numbers, but also for other details like ‘care of’ or to give additional information to the mail delivery person.  Almost anything can go into Address Line 2, and increasingly, people expect Address Line 2 data to be handled as part of the entire address validation protocol.

Ultimately, this field adds a significant layer of complexity to an address validation solution. Take for instance the scenario where someone enters “Apt 2 A C O Sally” on Address Line 2. Typically, someone would not enter the data that way, but you may be surprised how often something like this does come up. Visually, we can easily identify the intention of the data. An address validation process, on the other hand, will find identification and categorization of this information difficult. For example, what does “Apt 2 A C O Sally” signify? Is it Apt 2A, Care of Sally? Or is just Apt 2? Furthermore, once we identify the “Care Of” details, does that information need to be preserved on the output?

Standardized Solutions and a Custom Fix

In some situations, Service Objects can create a solution capable of handling the complexities of multiple address data inputs beyond the standard format. In other instances, the best result is a happy medium. Sometimes a specific solution can be tailored to a particular client based on their individual needs. Always, our updates can fine-tune operations and benefit all of our clients.

We use our extensive validation knowledge and industry standards and expectations to help govern which approach we take. Situations like these represent what our teams look at all the time, and we are always finding ways to make improvements. Our services are based on almost 20 years of experience.

When we update logic in the system, we often walk a fine line between what the code should do versus what it already does.  We always want to improve our processes without negatively impacting clients already used to expected behavior. Improvements capable of changing the expected results for current users will often be bundled up in a new version, but usually, we can find ways to update current versions, so clients always have the latest and greatest option without needing to make any changes.

As we know, the devil is in the details. By drilling down to the smallest and most incremental element of an address input, Service Objects provides the highest level of data verification and address validation services. In fact, our focus on details allows us to be experts in the validation services field, so your organization doesn’t have to be.

 

DOTS Address Validation 3 is one of our most popular services – for good reason! This service is robust and good at what it does. Our powerful CASS certified engine provides our customers with quick and efficient address validation. Because of the complexities associated with DOTS Address Validation 3, there can be lingering questions about what certain fields mean or even how to use it. I am one of the integration specialists here at Service Objects, and I am here to help demystify some of the key features that DOTS Address Validation 3 boasts.

DOTS Address Validation 3 Use Cases

One of the most popular ways to use DOTS Address Validation 3 is to put it directly in a web form where the user enters their address. In this case, an address can be sent to our services, verified, cleansed, and validated before it is used for shipping purposes or before it is put into a database. Based on the DPV code that our service returns, we can also indicate whether an address is missing secondary unit information (i.e., like an apartment or suite number), or if the given secondary unit information isn’t considered valid by the USPS. This DPV value can be used to relay information back to a customer to correct or add the right Secondary unit number.

If you don’t have the ability to call an API from a web form, another use case could be to collect the addresses that you acquire and submit them in bulk with an FTPS set up. Our processes will determine when a file has been uploaded and will process the records and then spit out a file with the validated data that you can use to upload back into your database

If you have a large existing database of uncleansed addresses, you are in luck! We offer large list processing that will allow you to cleanse existing databases. We are experts at running large quantities of data quickly, so we’re happy to process these lists for you to clean up your existing database.

Responses

Knowing how an API works is essential to integrating it and to using its response. One thing to note about DOTS Address Validation 3 is that if an address is invalid, then it will return an error object in the response. In other words, if DOTS Address Validation 3 returns an error, it means the address couldn’t be validated. If an address is valid or partially valid (more on that later) then it returns the address information. There are different errors the service can return that will help you troubleshoot what is occurring with the API call and determine so you can correctly handle each type of error that comes back.

 

1. Error Code 1 – Authorization Codes

These errors indicate that something was wrong with the license key. These errors are not billable. You may also need to reach out to Service Objects if you encounter these errors in a production environment.

Error Desc Code	Error Description	Additional Desc
1	Please provide a valid license key for this web service	There was no license key submitted to the service. Oftentimes this occurs when the URL encoding hasn’t occurred correctly.
2	The daily allowable number of transactions for this license key has been exceeded.	This doesn’t apply to all keys, but some have a daily maximum transactions
3	The monthly allowable number of transactions for this license key has been exceeded.	Some keys have a monthly maximum. You will encounter this value if you pass the monthly maximum
4	The total allowable number of transactions for this license key has been exceeded	The overall amount of transactions has been exceeded.

 

2. Error Code 2 – User Input

Something was wrong with the inputs. Either necessary fields were blank, or the inputs were too long.

Error Desc Code	Error Description	Additional Desc
1	Address and Address2 fields were too long. Together, they must be 100 characters or less.	The input fields were too long
2	Address field was too long, must be 100 characters or less.	The input fields were too long
3	Please input a street address.	There was no Address1 or Address2 values entered
4	Please input either zip code or both city and state.	The service needs either a zip code or both city and state to perform a successful validation.

 

3. Error Code 3 – Fatal Errors

These errors indicate that a Service Objects web service is behaving in a way that it should not. If you ever see this error in a production environment, please notify Service Objects immediately.

Desc Code	Error Description	Additional Desc
1	Unhandled error. Please contact Service Objects.	Like it says, please contact Service Objects immediately and let us know what inputs you used to create this error.

 

4. Error Code 4 – Domain Specific

These errors occur when something has gone wrong with the validation process; usually, an invalid address. There are also more specific messages for each error you can use to help decipher the reason for the failed address validation.

Desc Code	Error Description	Additional Desc
1	Address not found	Major issue with the address that doesn’t fit known USPS special case scenarios.
3	Multiple addresses match	Several address candidates were found that are equally likely given the input. Ex: “1 Main St” matches “1 E Main St” and “1 W Main St”.
5	Please enter a valid address number.
7	Street not found	Street name not found for the general area (city/state or zip)
8	Street number or box number out of range	Street name found in the area, but the given primary number is not valid for that street
12	Internal error.	Returned when an unexpected error occurs while processing address, or for special address cases. This error isn’t likely to appear
14	City not found	City name not found for given state or postal code
15	State not found	State abbreviation not found. The input state didn’t seem to be a valid state.
17	Address not found but the region has General Delivery service	Given address not found, but the region provided matches a known area that only provides General Delivery services. Mail sent to “General Delivery” with the recipient’s name may get delivered to the recipient.
21	Unable to parse address.	Indicates that the input could not be parsed into address fragments.

Non-Error Response

If there wasn’t an error returned, that’s good news! It means your request has resulted in validated address information. Below is a list of all the values recommended for a GetBestMatches operation. If you are using an operation other than GetBestMatches, then some of these values may not apply. Another thing to be aware of regarding GetBestMatches is the possibility it will return multiple addresses if the input address is vague. For example, when directional information should have been included but was not. In that case, the service will return multiple addresses and let the user navigate the ambiguity.

Return Value	Description
Address1	This is the standardized Address1 line of the address. This along with City, State, and Postal Code are where you will find the verified and standardized address components
Address2	The USPS doesn’t consider the Address2 field to be necessary for mailing purposes. If there is any valid Secondary Unit information sent in the Address2 input our system will pick it up and append it at the end of the Address1 field. If there is any extraneous information in the input Address2 field (i.e. “c/o John Smith” etc.) we’ll try to maintain it in the Address2 field.
City	The validated city for the given input address.
State	The corrected and validated state name.
Zip	The validated and corrected Zip + 4 for the given address.
IsResidential	A “TRUE” or “FALSE” flag will be given to indicate whether the input address is considered to be residential
DPV	A value between 1 and 4. This is arguably the most important values to look at when determining what to do with an input address. The DPV value will essentially indicate the total validity of an address. Your use case may vary but here is an example of how to deal with different DPV values when a customer may be entering address information on a web form. DPV 1 – The Address is in the USPS database and is considered to be a valid mailing address. DPV 2 – The address is not in the USPS database. This means that this address may exist, but the USPS simply does not deliver to it. Perhaps try using an alternate mail delivery company to deliver something to this address. DPV 3 – The given secondary unit information on the address is invalid, ask the user to double check the given Secondary Unit information and try again. DPV 4 – The service and subsequently the DOTS Address Validation 3 service expects a Secondary Unit (i.e., apt, unit, suite etc.) but none was provided. Perhaps ask the customer if they are missing the required unit information.
DPVDesc	The text value that explains the DPV result
DPVNotes	Numerical notes that indicate different pieces of information about a particular address. Some of the notes can be things like: Post Office Box address, Firm or Business address, Address exists but is vacant, Military APO/FPO address etc. For a full list of these codes please visit our developer guides.
DPVNotesDesc	The text descriptions that are associated with the values in the DPVNotes field
Corrections	An enumerated list of codes that indicate certain corrections were made to the input address. I.e., City corrected, state correction etc. For a full list of Correction codes, please visit our developer’s guide.
CorrectionsDesc	The text descriptions for the codes provided in the corrections field.
BarcodeDigits	This is a value that the USPS uses to sort mail. Each deliverable address has a unique barcode digit value. A benefit of this is that users can utilize this value to dedupe records in a database. Meaning if you have several different records with the same Barcode Digit, then you can clean up your database.
CarrierRoute	A 4-character string that highlights the carrier route the USPS uses to for this address.
CongressCode	This is congress code that is associated with the congressional district number in which the address is located
CountyName	The name of the county in which the address resides.
FragmentHouse	This is the parsed-out house number for an address. i.e., 123 of 123 W Main St N. The rest of these values are typically used to reconstruct an address that has been validated. Most customers who use these values use them to reassemble an address into different fragments for cases where an application might have character limitations.
FragmentPreDir	The parsed pre-directional of the address’s street. “W” of 123 W Main St N.
FragmentStreet	The parsed-out street name. “Main” of 123 W Main St N.
FragmentSuffix	The parsed-out suffix of the street. “St” of 123 W Main St N.
FragmentPostDir	The parsed-out directional fragment of the address. “N” of 123 W Main St N.
FragmentUnit	The parsed-out unit designator of the input address. Can be values like APT, STE, UNIT etc.
Fragment	The parsed-out unit number of the secondary unit designator. “4” of Unit 4
FragmentPMBPrefix	The parsed type of personal mailbox designator. This will likely be “PMB” or “Box”. Some addresses have personal mailboxes to which mail can be delivered.
FragmentPMBNumber	The parsed-out number from the PMB designator. 4 of PMB 4.

 

This covers most of the basics of DOTS Address Validation 3. As I mentioned, because of the robust capabilities of our CASS certified engine and the comprehensive nature of DOTS Address Validation 3’s data input fields, users are sometimes confused about how to use certain fields or how DOTS Address Validation 3 can be used or integrated. If you want to learn more about how DOTS Address Validation 3, please don’t hesitate to reach out to us! We’d be happy to answer any follow-up questions you may have and make recommendations on how to interpret and use the results from the service.

“Nobody is perfect. And my company wasn’t even talking about things like data quality ten years ago. So, what is the big deal if there are a few problems with my contact data? That’s life, isn’t it?”

Actually, it is a big deal. First, it affects your costs and competitiveness. Second, it affects your reputation in the marketplace. And finally, because bad data can be so easily fixed with the latest automated tools.

With new regulations on the horizon and an increasingly competitive marketplace, companies need data they can rely on. If you’re still on the fence, below are some of the main reasons your business needs confirmed data.

Saving Time and Money

Bad data always costs your business time, money, or both. It affects areas such as sales leads, delivery accuracy, your reputation when sending email marketing, and much more. It is estimated15-25% of contact data is inaccurate, incomplete, fraudulent, or out-of-date, and a great deal of resources are wasted due to inaccurate or straight-up bad data.

Getting sales leads is costly for most organizations, especially when leads are bad or inaccurate. The earlier you can validate incoming data, the better you will be able to utilize your resources.  Our Email and Address Validation services can help make sure your incoming contact data is coming in clean and valid, and our Lead Validation service helps prioritize your resources toward better targeted leads.

Improving Your Marketing Efficiency

Think of all the wasted resources involved when materials are sent to the wrong address, or salespeople chase after bad or mislocated prospects. Even a small percentage of errors can result in a great deal of frustration for everyone involved, and fixing these problems is low-hanging fruit you can easily automate.

Beyond our Address Validation services, our Address Geocode product can translate addresses to exact latitude-longitude coordinates in real time. For incomplete addresses, our Address Detective product can prevent you from purging good leads. It fixes fatal addressing errors by filling in the gaps of missing address data in your contact records, using a fuzzy-matching API that returns a confidence score for each updated address.

Protecting Your Email Reputation

Suppose you bought an email list and you are ready to send the perfect email, after weeks of refining. Nothing can give you a bad reputation quicker than sending email to a bunch of addresses that bounce, not to mention getting mediocre results from your campaign.

Use our Email Validation service to keep your reputation in good standing. Using a real-time API can reduce bounce rates up to 90%. Our service can process rented lists as well as your own house lists, giving you valuable insight into your contact data assets to make sure you get the most out of your investment.

Cleaning Up Your Existing Contact Data

We often hear people say, “What if I just realized we were doing things wrong and I want to get our data on the right track?” Once your database gets corrupted with uncertain data, typically two things must happen to reverse course. First, you need to draw a line in the sand and commit to making sure to validate any new information going into your system. The next step involves validating all your current database information in a separate process.

We can help automate much of the extra work of cleaning up existing data. We have lots of sample code and support many platforms to make it easy to integrate with us, not to mention the top-notch technical service team we have standing by to help you implement a robust solution.

Lather, Rinse, Repeat

Finally, we wanted to mention the importance of keeping your data current. Even after validating data coming into your system using our API or cleansing your system afterward with our batch process, data will still get old and invalid over time. People move, new homes are built, old buildings are repurposed, emails change, phone numbers are disconnected, and so on.  Like showering, regular data hygiene will help keep your data in the best condition possible, and we make this easy for you.

There are many benefits to keeping your data as up-to-date and accurate as possible, and we are here to help you every step of the way. Contact us to see what we can do for you and your data!

 

“Online retailers of all sizes are constantly under attack by sophisticated fraudsters. In fact, credit card fraud costs US online retailers an estimated $3.9 billion each year.” – Geoff Grow, Founder and CEO, Service Objects

At Service Objects, we know that data quality excellence is the key to helping retailers feel confident about improving delivery rates while reducing fraud associated with vacant addresses, PO boxes and commercial mail handlers. This, in turn, helps maintain higher customer satisfaction ratings among your legitimate customers.

This video, featuring Service Objects’ Founder and CEO, Geoff Grow, will show you tools you can use to improve the deliverability of your products and combat fraud. You will learn how to validate addresses against current USPS certified address data to prevent undeliverable and lost shipments, as well as how to validate a customer’s IP address against the billing and shipping information they provide, using data from over many authoritative data sources to stop fraud before it happens.

 

The word “deprecated” is thrown around frequently in the software development world. It is used to indicate a product or service that is either not going to continue being maintained or it is going to be sunsetted. Often times, when companies roll out a new product or API they decide to give their users a heads up that the older operations are going to be deprecated. This prompts the users to update to the latest version to take advantage of the latest and greatest features that the company is offering.

Marking a service to be deprecated is a warning to the users of the product or service that it will no longer be supported and it is highly recommended to upgrade to a newer, supported service.  Here at Service Objects, we don’t particularly like the practice of deprecating services.  Although we don’t rule it out completely, our mission is to maintain support for our legacy services. This is because we understand that it takes time, resources, and money to integrate with APIs. The time it takes for developers to integrate, test, and deploy new code inevitably costs money. To help solve the issue of legacy services falling behind the advancements, we keep our core code separate from the individual service outputs. A fixed set of output fields enables us to provide our clients with peace of mind that the service they have invested their time and resources into won’t change beneath their feet.

A clear picture of this concept can be seen in our DOTS Address Validation services. We have DOTS Address Validation 1, 2 and 3. The 3^rd iteration is currently our primary and most robust address validation service yet. It has the latest and greatest in terms of available output fields. Even though Address Validation 3  is our latest version of our address services, both DOTS Address Validation 1 and 2 are actively supported.

The reason we are able to maintain these is due to the fact that the share a core address validation code set, which is continuously refined to return the most accurate and up to date data available.

By choosing our services, you can rest assured that the service you integrate will not be left to be put out to pasture in the future  and will continue to push to provide you with the best data, regardless of which version of the service you are using.

We invite you to get started testing any of our 23 data quality services today.

Many of us use Google Maps to quickly verify that a location exists or give us an idea of what that location looks like. However, there is a common misconception that it will validate that the address found is correct and deliverable. So although Google Maps is an extremely powerful lookup tool, it will not validate addresses nor does it include the robust features and support included with our DOTS Address Validation-US service. To jumpstart your understanding and dispel some standard misconceptions, let’s explore some of the differences in our Address Validation service and Google Maps.

What does DOTS Address Validation do?

Although Service Objects can verify and validate many contact data points such as name, phone and email, our specialty is address validation. For us, addresses consist of business names, address fields, cities, states, and postal codes. Our USPS CASS Certified address validation service is designed to improve internal business mail processes and delivery rates by standardizing contact records against USPS data.

It’s all in the documentation

Our Developer Guide is a great place to start for an in-depth breakdown of the service and response features for Address Validation. It is extremely useful while integrating and can be used as a reference guide as well when learning more about the information each output field conveys.

24/7 Support when your business needs it most

With the amount of information provided in the results, it is common to have questions along the road to understanding each of the outputs. Our team is here to help you in this process and provide 24/7 technical support. We can be reached by phone (805-963-1700), email and even live chat on our website. “Best Practice” and “Step by Step Tutorial” blogs are also posted on a regular basis.

Deliverability is key

One of the biggest misconceptions about Google Maps and Address Validation is the ability to determine DELIVERABILITY. Beyond correcting and standardizing an address, our advanced algorithms and wide-reaching data sources allow us to determine if an address is deemed deliverable by the United States Postal Service. The service response will contain a Delivery Point Validation (DPV) indicator of 1-4 that can be used based on specific business logic. A DPV score of 1 indicates a perfectly deliverable address whereas a score of 2-4 indicates missing or incorrect inputs in the address field. The corrected address, component fields, and extra information such as the DPV indicator, residential delivery indicator (RDI), vacancy flags and more will be included and can be leveraged in your workflow.

Primarily, the locations that Google Maps will mark aren’t necessarily mail deliverable. There is a lot of leniency within the Google algorithms that allows for guesswork to be made. Although Google can put a pin on the map for a given input address, it does not mean that a postal carrier will deliver mail at that location. However, if DOTS Address Validation marks a location as invalid, you can be sure you are getting genuine and accurate information.

When is Google Maps useful for address lookup?

With all of that said, Google Maps should not be discounted in its ability to investigate a location. If the image data was captured recently it can be used to understand why our service marked an address the way it did. A prime example of this is an address marked as having a “street number out of range.” By checking Google Maps data and cross-referencing our service response, more light can sometimes be shed about that address location.

While you can use Google Maps to potentially confirm if a location exists, it is imperative to use robust validation tools like DOTS Address Validation to ensure any mail your business sends can actually be delivered, saving time and money.

 

If you have any questions about validating, verifying or appending addresses, or any other contact data points including name, phone, email and device, feel free to contact us.

Christmas is, of course, a major religious holiday celebrated around the world. And also one of the busiest and most profitable times of year for your business. But do you know how it first got that way?

Many people credit author Charles Dickens and his story A Christmas Carol with helping Victorian England, and later the world, see Christmas as a time of gift-giving and family connection. His mid-1800s story focused on how a lonely miser, Ebenezer Scrooge, learned to avoid the fate of his partner’s eternal torment when the ghosts of Christmas Past, Christmas Present and Christmas Yet to Come taught him to focus on what really matters – other people.

With apologies to Dickens, we feel that the three ghosts of Christmas have a valuable modern-day lesson to teach us about creating a happy holiday season for everyone, in the middle of your biggest crunch time. (Fair warning: it involves data quality.)

• First, the ghost of Christmas Past showed Scrooge what life was like once upon a time at the holidays, when employees were happy and the company took good care of everyone – before Scrooge eventually presided over a joyless, high-pressure workplace. Just like what happens when your own performance pressures put data quality on the back burner, something a recent executive survey showed as being a major concern.
• Next, the ghost of Christmas Present warns Scrooge that unless he changes his priorities, his neglect of others will harm people like the humble Bob Crachit and his ailing son Tiny Tim – much like your business can ruin the holidays for your customers when bad contact data causes service failures.
• Finally, the ghost of Christmas Yet to Come paints a grim picture of a world where Scrooge is dead and no one cares – the same way that people turn away from your business and never return when you don’t deliver what you promise.

What do these lessons have to do with your own holiday rush season? Everything.

You see, most people in most businesses focus on doing their individual jobs, like entering orders or shipping products. But what about the greater mission of making sure that everyone gets what they need from you, particularly at the holidays? Too often, that is someone else’s job. Which means it becomes no one’s job. And service failures, such as packages that never arrive or contact information that isn’t correct, just become a fact of life that gets tolerated by everyone.

The ghosts of Christmas taught Scrooge that he had to learn to care, or face the consequences. The same is true for you and your business at the holidays. And the best way to care for your customers – particularly when things are at their busiest – is to put processes in place that make sure the customer comes first.

At Service Objects, we help the holidays go smoothly with tools that range from simple address validation – fueled by up-to-date real-time data from the United States Postal Service and others – all the way to complete order verification capabilities that authenticate customers and guard against fraud. We can even append information such as phone numbers to your contact data, to help you keep in touch with people, or gain geographic and demographic insight that lets you serve people better in the future. All through automated processes that run seamlessly in your applications environment.

The lesson for Christmas, then and now? Don’t be a Scrooge. And let the holiday season be a time when your business shines for everyone.

If you are using an Address Validation service for shipping labels, then you may occasionally run into character count limitations with the Address1 field. Whether you are using UPS, FedEx, ShipStation or any other shipping solution, most character limits tend to range between 30 or 35 characters (some even as low as 25 characters). While most addresses tend to be under this limit, there are always outliers that you’ll want your business solution to be ready to handle.

If you are using a DOTS Address Validation solution, you are in luck! The response from our API not only validates and corrects bad addresses but also allows you to customize address lines to meet your business needs.  Whether you are looking to have your address lines be under a certain limit, want to place apartment or unit information on a separate line, or customize the address line in some other way, we can show you how to integrate the Address Validation response from Service Objects’ API into your business logic.

Below is a brief example using our DOTS Address Validation US 3 service to demonstrate the fragments that are returned in a typical valid response:

FragmentHouse
FragmentPreDir
FragmentStreet
FragmentSuffix
FragmentPostDir
FragmentUnit
Fragment
FragmentPMBPrefix
FragmentPMBNumber

If you are worried about exceeding a certain character limit, you can programmatically check the Address1 line result from our service to see if it exceeds a particular limit.

Check the result – not the input

There are two obvious reasons you should check the result of the service instead of the input.   First, you want to use validated and corrected addresses on your mailing label. Second, the input address may be too long before validating but post-validation, the corrected addressed could meet the requirements and no customizations are needed to fit within the character limitations.

With this understanding, if the resulting validated street address in Address1 line is over the character limitation, then your application can go about splitting up the address in ways that best suit your needs.

For example, let’s say you have a long address line like the following:

12345 W FAKE INDUSTRIAL ST NE STE 130, #678

This is obviously a fake street, but it helps demonstrate some of the different ways you can handle long address lines. In the example, the address ends up being around 45 characters long, including spaces. The service would return the following fragments for this address:

Fragment House: 12345
FragmentPreDir: W
FragmentStreet: Fake Industrial
FragmentSuffix: St
FragmentPostDir: NE
FragmentUnit: STE
Fragment: 130
FragmentPMBPrefix: #
FragmentPMBNumber: 678

With this example, one solution to reduce the character limits would be to move the Suite and Mail Box information to a separate address line, so it would appear like so:

12345 W FAKE INDUSTRIAL ST NE
STE 130, #678

You may need to fine tune the logic in your business application from this basic algorithm, but this can help you get started with catering your validated address information to meet different character limitations.

In most cases, the following can be used in Address line 1:

• FragmentHouse
• FragmentPreDir
• FragmentStreet
• FragmentSuffix
• FragmentPostDir

And the following in Address line 2:

• FragmentUnit,
• Fragment
• FragmentPMBPrefix
• FragmentPMBNumber

PO Boxes

There is an important exception to be aware of – PO Boxes. It is necessary to determine if the address is a PO Box to avoid applying the above logic to this type of address. It is simple to determine if the result is a PO Box by checking the DPVNotes field returned from the Address Validation service.  PO Boxes typically will fit under character length limitations but some organizations choose to rebuild addresses from fragments regardless of field length.  If this is the case and you have a PO Box, then the fragments to rebuild the PO Box are:

• FragmentStreet
• FragmentHouse

Highly Customizable

The examples above may require some fine-tuning to meet your business requirements but hopefully, they have also demonstrated the highly customizable nature of the address validation service and how it can be catered to meet your address validation needs.

If you have any questions about different integrations into your particular application contact our support team at support@serviceobjects.com and we will gladly provide any support that we can!

Do you sell products online? If you do, you have a great opportunity in front of you. An opportunity to boost revenues, increase market share, and create visibility for your business. Or an equally great opportunity to drive away customers, damage your brand, and lose money to fraud.

This opportunity comes once a year, in the form of the Black Friday and Cyber Monday holiday shopping period. Using figures from Adobe Digital Insights, Fortune Magazine noted that Cyber Monday 2016 was the biggest online shopping day in US history, with sales of $3.45 billion – a jump of 12% from the previous year. The traditional post-Thanksgiving shopping day of Black Friday came in a close second, with $3.34 billion of online sales in 2016, putting it on track to eventually surpass Cyber Monday as shopping channels continue to blur.

The good news is that both Black Friday and Cyber Monday each represent more than three times the volume of a normal online shopping day. And beyond sheer sales volume, these holidays traditionally draw new or annual shoppers online – people who are openly searching with an intent to purchase, with a great opportunity to discover your brand and become long-term customers.

Unfortunately, it is also open season for fraudsters. Online e-commerce fraud increases sharply during the holiday season, with fraudulent transaction rates reaching a peak of 2.5% versus a normal rate of 1.6%, against an average transaction value in excess of $200. The rise of chip-enabled cards has pushed even more fraudulent activity online in recent years, with online fraud attempts rising by 31% between 2015 and 2016. And there are risks associated with your legitimate customers as well, where problems such as missed deliveries or incorrect contact information can lead to problems ranging from lost business to poor social media reviews – particularly in the spotlight of the holidays.

Here is a quick guide to making the most of your customer opportunities this holiday season:

Screen out the bad guys.

Prevent fraudulent transactions by using multi-function order verification to check for things such as address validation, BIN validation, reverse phone lookup, email validation, and IP validation, returning a measure of order quality from 0 to 100 that you can use to flag potential problem orders before they ship.

Execute orders correctly.

Use address validation to verify and correct shipping information against up-to-date USPS, Canada Post or international address data, to ensure every order goes to the right place on schedule.

Keep your contact data working for you.

Did you know that 70% of contact data changes every year? Validating and correcting this data every time you use it in a campaign preserves this valuable contact information as a business asset.

Target your marketing.

Validate the legitimacy of your marketing leads, and check for appropriate demographics such as income and geographic location, to make your outreach for the holidays as efficient as possible.

Thankfully automated data quality solutions that can be engineered right in your API, or run as convenient batch processes with your existing data, can make optimizing the value of your contact data a simple and cost-effective process. And in the process, make Black Friday and Cyber Monday a little less scary – and a lot more profitable.

Customer Service Above All.  It is one of our core values here at Service Objects. Recently, we’ve received several requests for a list of the unique zip codes throughout the US and Canada. By leveraging our existing services, we’ve made this happen. We are now offering both the US and Canada list as a free downloadable resource.

So why is Service Objects providing this data? Our goal is to provide the best data cleansing solutions possible for our clients. Part of this means using our existing data to provide our users with the data they need. While other data providers might charge for this type of information, we’ve decided to make it freely available for anyone’s use. These files can be used for several purposes, such as pre-populating a list of cities and states for a form where a user needs to enter address information. The County and State FIPS information is widely used in census and demographic data or could be used to uniquely identify States and counties within a database. Additionally, the given time zone information can be used to determine appropriate times to place calls to a customer.

Where to download

allows you to access a .zip file containing two CSV records. One CSV contains the US information, the other is for Canada. The files indicate the month and year the records were created. Toward the middle of each month, the data in each record will be updated to account for any changes in US and Canadian postal codes.

What other information is in the files?

Both files will have postal codes, states (or provinces for Canada) and time zone information. The Canadian zip code file will be much larger in size with over 800K records. This is due to Canadian Postal Codes generally being much smaller than US Postal codes. Where a US postal code can sometimes encompass multiple cities or counties, a Canadian postal code can be the size of a couple city blocks or in some cases a single high-rise building.

The US file has information for all United States postal codes including its territories. This file will also include the county that the zip code lies in. There will be County and State FIPS numbers for each of the records to help with processing that information as well.  The US file will be considerably smaller than the Canadian file at only 41K records.

In making these files freely accessible, our hope is to make the integration and business logic easier for our users. If you’d like to discuss your particular contact data validation needs, feel free to contact us!

If you were to make a list of the things people love to do, data cleanup would usually rank pretty low on the list. (Except for us here at Service Objects. We rather enjoy data cleanup. But then again, we’ve always been a little different.) This naturally leads to another question: should you clean up your contact data BEFORE you put it into Marketo, or LATER, before you actually use it in a campaign?

We have a three-part answer to this question: yes, yes, and automate the process.

Here’s why: there are irreplaceable benefits to each process. And when you properly automate it with the right tools, the process becomes frictionless and institutionalizes the ROI of these benefits. Let’s explore this in more detail.

Validating contact data such as names, email, physical addresses and phone numbers BEFORE loading them into Marketo has several advantages:

Saving money.  Your Marketo pricing tier is depending on the number of leads in your database. By cleaning this data on the front end, you can often delay or perhaps even avoid entirely the problem of moving to a higher tier and paying more for non-viable leads. And within your tier, fewer bad leads translates directly to less human intervention throughout the marketing cycle and more accurate analytics.

Garbage in, garbage out. Putting dirty data into your marketing database skews whatever metrics or analyses you might do beyond marketing campaigns, including the all-important conversion rate. And catching bad contact information in real-time lets you message the user at time of entry so they can correct it, preserving valuable leads and preventing possible customer service issues.

Detecting bogus names and fraudulent leads. What good is a database full of Donald Ducks and Ninja Turtles, who faked you out to get a free report? Tools such as name validation can programmatically catch and keep fraudulent contact information out of your lead database in the first place.

Lead preservation. Conversely, your bad contact data can be a hidden source of leads and revenue – if you use automated tools to correct bad addresses or append missing information such as contact phone numbers.

Finally, there is the broader question of lead quality. Marketo’s own lead scoring – based on tracking activities, behavior and demographics – is important but may not provide front-end protection from fraudulent or bad data. Contact-level lead validation adds a quantitative value for lead quality, based on over 200 criteria, that lets you decide to fast-track a lead, put them in your drip campaign to see how they respond, or even discard the lead.

Now, let’s look at the other side of the coin. Validating lead data LATER at regular intervals, particularly at the time you use it, has several advantages as well.

Coping with change. Over 70% of contact data will go bad in the course of just a year. Lead validation tools can check your existing leads and then correct, update, or remove them based on the results. This saves you money by only keeping and paying for viable leads, allowing you to better identify sources of high and low quality leads and providing more accurate reporting.

Taking care of your customers. By triggering emails or other contacts to customers who appear to have changed their addresses, using tools such as our national change-of-address (NCOA Live) capabilities, you provide better service and pro-actively avoid future service or delivery failures.

Making your IT department happy. Lead and contact validation tools from Service Objects are easily automated within Marketo using our Webhooks which can be found on Marketo’s LaunchPoint marketplace. In addition, we offer convenient offline batch processing for contact data files without a technical interface.

Of course, automated contact and lead validation are not the only forms of data cleanup that can help – this blog by Perkuto’s John Hill touches on other useful areas such as screening out competitors, inactive leads and people with unresponsive email addresses. With a clear process in place – and the right automation partner – it can be easy and inexpensive to optimize the value of your Marketo database at EVERY contact touch point.

If you market to or serve people by mail, there are two acronyms you should get to know: CASS and DPV. Here is a quick summary of both of them:

• CASS stands for the Coding Accuracy Support System™. As the name implies, its function is to support address verification software vendors with a measurable standard for accuracy. It also represents a very high bar set by the US Postal Service to ensure that address verification meets very strict quality standards.
• DPV stands for Delivery Point Validation™. This is a further capability supported under CASS, making sure that an address is deliverable.

You may ask, “If an address is accurate, why do we have to check to make sure it is also deliverable?” The answer lies in the broader definition of what an address is – a placeholder for a residence or business that could receive mail. Not every address is, in fact, deliverable: for example, 45 Elm Street might be someone’s residence, while 47 Elm Street might currently be a vacant lot – or not exist at all. Another example is multi-unit dwellings that share an address: 100 State Street, Apartment 4 may be deliverable, while 100 State Street, Apartment 5 may not exist. So you want to ensure addressability AND deliverability for every address within your contact database.

Now, here is why you need to care about CASS and DPV in particular:

Rigorous. CASS certification is truly the data quality equivalent of Navy SEAL training. The first step is an optional (Stage I) test that lets developers run a sample address file for testing and debugging purposes. Next is Stage II, a blind 150,000-address test that only returns scores from USPS, not results. To obtain CASS certification, these scores must meet strict passing criteria ranging between 98.5% and 100% in specific categories.

Recurring. CASS certification is not a lifetime badge of honor. The USPS requires software providers to renew their certification every year, with a fresh round of testing required. Service Objects has not only been continuously CASS-certified for much of the past decade, but has also forged a unique partnership with USPS to update and refresh its CASS-certified address data every two weeks.

Reliable. DPV capabilities are based on the master list of delivery points registered with the USPS, which stores actual deliverable addresses in the form of an 11-digit code, incorporating data such as address, unit, and ZIP+4 codes. While the codes themselves can (and do) change frequently, the real key in address deliverability is having up-to-date access to current USPS data. Service Objects licenses DPV tools as an integral part of its address validation capabilities.

Our CASS-certified address engine and continuously updated USPS address data are two of the critical components behind our proprietary address database. Whether you run your addresses through our USPS address validation API in your application or use a convenient batch process, those addresses are instantly compared, validated, corrected, and/or appended to provide accurate results.

If you’ve read this far, it is probably clear that CASS certification and DPV capabilities are critically important for managing your contact data quality. So be sure to partner with a vendor that maintains continuous CASS certification with full support of DPV. Like Service Objects, of course. Contact us to learn what we can do for your contact addresses and marketing leads today!

So many reports focus on spitting out data that they often overlook the importance of being able to quickly digest the information and present a clear action plan. At Service Objects, we want you spending your valuable time acting on the results – not trying to make a report readable and understandable. As a result, we have invested considerable resources into ensuring our Batch Summary reports – the ones we provide you after we run your list – not only look great, but are immediately accessible and actionable. Your account executive will review the results of the report with you and answer any questions you may have, but you will also have a link to the detailed report for your reference and to share with your team members.

So how we did we improve the reports? We focused on telling your business’ data story and showing how our services can help improve your data accuracy. We have started with a few services and operations, and in the coming months, we will continue to roll out more of them out as they are ready. Some of the ways we tell the story better is presenting easy to understand charts and data breakdowns so that you can focus on the parts of your data that you are most interested in.

The following link provides a sample of our DOTS Address Validation US – 3 batch summary report and I have detailed out the features of the report below.

The summary starts with a brief description of the service and operation followed by a section where we define the main output of the service. In this case, the report is focused on Delivery Point Validation or DPV.

We show how the DPV results break down across the varying DPV notes, corrections and Is Residential data points. So, at a glance, it is easy to decipher the balance between the various DPV values.

 

 

 

 

 

Throughout each report, when we see interesting data points, we shine a spotlight on them and add additional custom content to help highlight them.

 

The report also drills down on the geographic nature of the data, showing how your list of addresses are distributed across each state and the country. The values are plotted on a map to provide a strong visual representation and hovering over a particular location also displays the underlying values.

Included in this location distribution, is how the DPV values correlate to a location, where we overlay the pie chart breakdown of the actual DPV values.

The break downs are by county and congressional district so your analysis can be completed very quickly.

Clicking on the three bars in the top right of any chart or graph will allow you to either save or print that particular chart. These new batch reports will also allow you to view your details from anywhere, on any screen size. No need to mess with PDF or specific file types, you just need an internet connection and a link to the report.

Lastly, we take data security very seriously. The reports are all provided very securely, so no one can see anyone else’s reports and data is never shared. Our hope is to provide a clearer understanding of your data, making it fast to digest and act on. If you have any questions or would like to us to run a sample data set for you, please contact sales@serviceobjects.com.

All right, we are finally going to admit it: there are some bad mailing addresses out there that even Service Objects can’t fix.

Of course, we’re talking about cases like illegible handwriting, physical damage, or the kid who addresses a Christmas letter to “Santa Claus, North Pole.” But even for them, there is hope – in the form of a nondescript building on the outskirts of Salt Lake City, Utah, known as the USPS Remote Encoding Center. Images of illegible mailing addresses are sent here online from all over the United States, in a last-ditch effort to get these pieces of mail where they are going.

Behind the walls of this beige, block-long building lies an optometrist’s dream: nearly 1700 employees working 24 hours a day, each scanning a new image every few seconds and matching it to addresses in the USPS database. (The same database we use to verify your contact address data, incidentally.) Most get linked to a verified address and are sent on their merry way; the truly illegible ones are forwarded to the USPS’s Dead Letter facility to be opened, and those letters to Santa get forwarded to a group of volunteers in Alaska to be answered.

According to the Smithsonian, there used to be more than 50 of these facilities all over the US. With time and improving automation, all of them have now been shuttered, with the exception of this lone center in Salt Lake City. To work there, you need to be fast, precise, and then go through more than a full week of training – and then you get put on one of 33 shifts, handling the roughly two percent of mail pieces that the Post Office’s computers cannot read automatically. That’s between five and eleven million pieces of mail per day on most days.

Of course, technology continues to improve, and USPS has become a world leader in optical character recognition for both handwritten and machine-addressed mailing pieces – even 98 percent of hand-addressed envelopes are processed by machine nowadays. In an interview with the New York Times, the center’s operations director acknowledges that computer processing could eventually put them out of business entirely. But for now, human intervention for illegible addresses hasn’t yet gone the way of the elevator operator.

Thankfully, your business correspondence probably isn’t hand-scrawled by your Aunt Mildred. And hopefully Santa Claus doesn’t show up very often in your prospect database (although fake names get entered for free marketing goodies more often than you think, and we can easily catch and fix these). So your chances of ending up on a computer screen in Salt Lake City are pretty slim – which means we can help you ensure clean contact data, and leverage this data for better marketing insight.

So for those of you who can’t spell, failed penmanship when you went to school, or have a habit of leaving your envelopes out too long in the rain, there is still hope. For the rest of you, there is Service Objects.

What is DOTS FastTax?

DOTS FastTax web service provides sales and use tax rate information for all US areas based on several different inputs. The operations that are offered within FastTax take input parameters such as address, city, state, postal code. The service also provides an operation that will take your Canadian province and will return the proper Canadian tax rate information.

How can it be used?

At its core, FastTax is an address to tax rate lookup system. You provide the service with a location and it will return the tax rate or rates for the given area. From there you can use this data in conjunction with your own business logic to easily determine the proper tax rate you should be charging. A common use case is for online retail companies that need to determine the rate to charge for an order. Rates vary greatly depending on where the client is located and if the company has a sales tax nexus in that state.  Nexus, also known as sufficient physical presence, is a legal term that refers to the requirement for companies doing business in a state to collect and pay tax on sales in that state. Calculating the proper rate is as easy as determining where your company has nexuses and then performing a tax rate look up via the FastTax web service. These two steps can be done programmatically, thus streamlining your business workflow.

What makes FastTax so powerful?

It may seem like a simple task to take an address and perform a lookup on a tax rate database. In theory it is just identifying a location and then finding the relevant tax rates for it. However, in reality there are many more factors that need to be accounted for to ensure the tax rate being returned is accurate, up to date, and truly relevant for the input address. It is in these aspects where Service Objects’ FastTax goes above and beyond. On top of our tax rate databases that are actively maintained to provide the latest and most accurate tax rate data, our operations benefit from the other services we specialize in. Namely, our address validation and address geocoding services.

How does FastTax go above and beyond?

Through the use of our address validation engine we are able to take an input address and determine its correctness as well as standardize it into its most useable form. Having an address corrected and standardized allows us to more accurately match the location with its corresponding tax rate. On top of address validation, our use of geocoordinates and spatial data allow us to identify boundaries between areas. This could be the difference between charging the proper rate for an area or misidentifying it and missing rates such as county, country district, city district, or even special district rates. Another extremely important distinction that geocoordinates allow us to make is for areas that are unincorporated. FastTax provides an “IsUnincorporated” flag when an address is in an unincorporated area. This allows for your business logic to correctly tax this address by removing any city or city district rates.

FastTax in action

To see the power of FastTax in action it helps to take a look at Google Maps. Let’s take the city of Littleton, Colorado. In fig.1 the city perimeter is outlined in red and its contents shaded in. The Google Maps result shows the officially recognized city limits. Comparing that to the pin shown in fig.2 it is clear that the address in this example falls beyond the city limits. Technically it is identified as part of the city of Littleton but is part of an unincorporated area. Tax rates for this address need to properly account for this geospatial and city boundary information. FastTax excels in identifying these areas and can provide the “IsUnidentified” flag to indicate this address falls into its own special case. With the indicator flag in hand you can properly account for the difference in tax rates.

See how FastTax can help your business. Sign up for your free trial key or send us a list and test up to 500 transactions.

The Service Objects’ team watched the steady stream of images from Hurricane Harvey and its aftermath and we wanted to know, ‘What can we do to help?’  We realized the best thing we could do is offer our expertise and services free to those who can make the most use of them – the emergency management agencies dedicated to helping those affected by this disaster.

It was quickly realized that as Hurricane Harvey continues to cause record floodwaters and entire neighborhoods are under water, these agencies are finding it nearly impossible to find specific addresses in need of critical assistance. In response to this, we are offering emergency management groups the ability to quickly pinpoint addresses with latitude and longitude coordinates by offering unlimited, no cost access to DOTS Address Geocode ℠ (AG-US). By using Address Geocode, the agencies will not have to rely on potentially incomplete online maps. Instead, using Service Objects’ advanced address mapping services, these agencies will be able to reliably identify specific longitude and latitude coordinates in real-time and service those in need.

“The fallout of the catastrophic floods in Texas is beyond description, and over one million locations in Houston alone have been affected,” said Geoff Grow, CEO and Founder of Service Objects.  “With more than 450,000 people likely to seek federal aid in recovering from this disaster, Service Objects is providing advanced address mapping to help emergency management agencies distribute recovery funds as quickly as possible. We are committed to helping those affected by Hurricane Harvey.”

In addition, as disaster relief efforts are getting underway, Service Objects will provide free access to our address validation products to enable emergency management agencies to quickly distribute recovery funds by address type, geoid, county, census-block and census-track. These data points are required by the federal government to release funding.  This will allow those starting the recovery process from this natural disaster to get next level services as soon as possible.

To get access to Service Objects address solutions or request maps, qualified agencies can contact Service Objects directly by calling 805-963-1700 or by emailing us at info@serviceobjects.com.

Our team wishes the best for all those affected by Hurricane Harvey.

Image by National Weather Service 

“Did you know that nearly 30 million Americans move each year? Did you also know that government agencies like counties, cities, and states are required to keep accurate and up to date records of their private citizens for communication purposes?”

Service Objects is committed to helping businesses reduce waste, and identify and improve operating efficiency through data quality excellence. And according to founder and CEO Geoff Grow, you can do this using databases up-to-the-minute USPS-certified data and more to verify your contact records.

This video will show you how to use simple API and web-based tools that validate and append data to your contact information. You will learn how data quality solutions can:

• identify change of addresses, making it easier to keep your contact records accurate and up-to-date,
• validate addresses to maximize delivery rates,
• geocode addresses to provide highly accurate latitude and longitude information. In addition,
• and append census, ZIP code and county boundary data.

If you are old enough to remember the disco era, one of its biggest hits was “Got to Be Real” by Cheryl Lynn. (And if you’re younger, it’s been sampled over 100 times since.) Decades later, if you work in marketing, this tune should become your new theme song.

The lifeblood of any marketing operation is its lead generation efforts. And sadly, many of these leads aren’t real – according to industry figures, as much as 25% of your contact data is bad from the start, and from there 70% of it goes bad every year as jobs, roles and contact information changes. This ranges from fake or fraudulent contact data, often entered to gain access to lead generation bonuses, all the way to fat-fingered data entry.

Unfortunately, when your contacts aren’t real, the costs involved are very real:

Marketing costs: Direct mail costs can easily total $2-3 or more per piece mailed, while outbound telemarketing costs can top $35 to $60 per lead. In both cases, there is direct cost in both time and resources to working with bad contacts. Nearly any lead conversion strategy has a scalable cost per prospect, and bad or fake leads directly eat into these costs.

Wasted human effort: Take the labor costs, taxes and benefits you pay for the direct employees on your sales and marketing teams. Add in the costs of the overhead and infrastructure they require to do their jobs. Now multiply that by the percentage of time these people spend mitigating bad leads, and this total probably adds up to a very real and tangible cost, as well as impacting sales conversion rates.

Inefficiency: Ultimately, every business must deal with the problem of bad contact data. But the real question is when you deal with it. In many businesses, where data quality is no one’s responsibility, it gets fixed the hard way when prospects don’t answer and direct mail pieces bounce back. We describe it as the 1-10-100 rule, where it may cost a penny to catch bad contacts as they are captured, 10 cents to cleanse them after capture, and a dollar to work with uncorrected data. In addition, bogus leads can bog down your CRM or Marketing Automation platform, driving up costs and negatively impacting marketing campaigns.

Customer service reputation: Your all-important first impression on a potential customer pivots around responding to their requests – and if you fail to respond due to bad or misdirected contact information, the damage is often permanent. For example, if a customer enters their email incorrectly but are waiting to receive information from customer service, causing dissatisfaction and frustration.

The good news is that each of these costs can easily be controlled by automating the data quality process for your contact lead data, using tools that range from address verification to filtering out fraudulent names. For marketing operations, you can also use bundled lead validation capabilities that check over 130 data points to yield a lead quality score from 0 to 100, as well as lead enhancement that appends phone and contact information to your existing lead data.

The key to success in marketing, according to Forbes Magazine, is to know your customer. Data quality – making sure every contact record in your database is as genuine, accurate and up-to-date as it can possibly be – represents an important and cost-saving first step for this. Or as Cheryl Lynn would say, they’ve got to be real.

You probably know what omnichannel means, but a quick definition is always helpful. It refers to the various touch points by which a business/organization can reach a customer. The idea — and the ideal — is to get the offer in front of them at the time they’re most likely to be interested. Typically in the modern business ecosystem, omnichannel refers to:

• Website
• Brick and mortar locations
• Social media
• Other digital efforts
• How you come across on mobile
• Face-to-face interactions between customers and employees

There is more you could group under omnichannel, but that’s a good start. Unfortunately, in a few years from now, we may need a different approach entirely.

Why?

OMNICHANNEL AND THE RAPID SCALE OF BIG DATA 

Consider this: in 2020, it’s possible 1.7 megabytes of new data will be created for every person on the planet every second. If you do the full math on that, the total volume of data globally in 2020 might be around 44 zettabytes. A zettabyte is a trillion gigabytes. This is somewhat because of “The Internet of Things” — connected devices and sensors — which should have an economic value of $3 trillion by 2025. Internet of Things tech alone will be 3-6 zettabytes of that total.

Now we know the rapid scale of Big Data. It’s actually arriving in daily life maybe faster than even mobile did. What are the repercussions?

THE REPERCUSSIONS FOR OMNICHANNEL

As noted in this post on Information Age:

Companies hoped “omnichannel experiences” would enable them to anticipate customers’ needs to provide them with a personalised response, which meets or even exceeds their expectations. And this effort is based on the company’s ability to mobilise the necessary data to deliver.

But what happened?

Today, these same companies struggle to draw together all the information required to give them a unified view and appreciation of their customers’ needs. The result is a mixed bag of omnichannel initiatives, many of which result in failures. In the retail sector, for example, only 18% of retailers claim to have an engagement strategy, which covers all channels.

The sheer math looks like this: 44 zettabytes of generated data in 2020 is 10 times — yes, ten times — what we are generating now, three years earlier. Companies are already struggling to manage data properly towards better customer experience. What will happen when 10 times the data is available in 33 months or so?

WHAT’S THE FUTURE LOOK LIKE FOR OMNICHANNEL AND CX?

This is obviously hard to predict. In times of great complexity, though, sometimes sticking to the basics — i.e. The Five Customer Experience Competencies — isn’t a bad idea. A strong base almost always beats an all-over-the-place strategy.

In my mind, this is what needs to happen:

• Companies need a good handle on what really drives their business now and what could drive it in the future.
• This involves products/services but also types of customer and platform they use.
• Once that picture is mostly clear, senior leaders need to be on the same page about the importance of customer-driven growth.
• “Being on the same page” also involves, ideally, vocabulary and incentive structures.
• If the customer-driven plan/platforms and senior leadership alignment are there, now you need to make sure the work is prioritized.
• No one should be running around on low-value tasks when great opportunity is right there.
• Kill a stupid rule, etc. Basically move as many people as possible to higher-value work, especially if lower-value work can be more easily automated.
• It’s all been important so far, but let’s bold this: You don’t need to collect all the data. You need data that relates to your priorities and growth. 
• That data should be analyzed and condensed for executives. You may need “data translators,” yes.
• Decision-making should come from relevant information and customer interactions.

This flow is hard to arrive at for some companies, but essential.

Phrased another way: trying to be “omnichannel” in five years and looking at an Excel with trillions of touch points/data on it? That will just burn out employees and managers alike. You need a prioritized, aligned plan focused on customer-driven growth and well-articulated goals. That will get you there post-omnichannel.

Reprinted from LinkedIn with permission from the author. View original post here.

Author’s Bio: Jeanne Bliss, Founder & CEO, CustomerBliss

Jeanne Bliss pioneered the role of the Chief Customer Officer, holding the first-ever CCO role at Lands’ End, Microsoft, Coldwell Banker and Allstate Corporations. Reporting to each company’s CEO, she moved the customer to the strategic agenda, redirecting priorities to create transformational changes to each brands’ customer experience. Her latest book, “Chief Customer Officer 2.0” (Wiley) was published on June 15, 2015.

There has always been one eternal question in marketing: what is the shortest path between you and your next paying customer?

We already know the right answer to this question: “It depends.” But a better answer is that effective marketing is very context-dependent. So let’s look at the pros and cons of three of today’s key marketing approaches – phone, mail and email marketing.

Telemarketing has practically been with us ever since Alexander Graham Bell first solicited his assistant Watson from the next room in 1876. Its key advantage is that it is the only one of these three approaches that builds an interactive personal connection with a prospect – one that allows you to qualify him or her, ask questions, and respond to their needs. Big-ticket products and services, particularly in a business-to-business environment, are often sold as the result of a sales process that begins with a phone contact. Conversely, large scale telemarketing often is a key ingredient of selling consumer products and services in large volumes.

Telemarketing also has numerous drawbacks. It is labor-intensive, time-bound, and requires a good telecommunications infrastructure when used on more than a small scale. Perhaps most importantly, it requires the right business context. If you are selling an airliner or high-end financial services, those prospects may expect an initial phone call, while carpet-bombing consumers with telephone sales pitches at dinnertime may provoke mostly negative responses. Moreover, unsolicited calls to consumer wireless phones can lead to large fines under the Telephone Consumer Protection Act (TCPA).

Direct mail marketing gives businesses an opportunity they do not have with phone or email: the chance to deliver content-rich information in print or even multimedia form. (For example, anyone who belongs to Generation X or older remembers those ubiquitous AOL CDs that were a fixture of the 1990s.) Anyone with a valid mailing address is a potential prospect, it is a medium that lends itself well to A-B testing as well as demographic targeting, and there are few if any regulatory roadblocks to targeting consumers with a direct mail campaign.

Drawbacks of direct mail include its expense per prospect, in terms of time, content costs, and mailing costs. This is particularly a disadvantage for smaller businesses, given the economies of scale that reduce per-unit printing and mailing costs for those who can afford very large campaigns. Response rates are generally low and can vary widely, and the accuracy of your contact data is a critical factor in your costs and profitability.

Email marketing is, relatively speaking, the new kid on the block – even though it now has its own decades-long track record. It has one towering advantage over the other two approaches: a much lower cost per contact that only minimally scales with the size of your prospect base, once you have a list that opts in. Email also gives you the opportunity to include rich media content, or make “warm call” introductions to individual prospects as a precursor to telephone contact.

Disadvantages of email include being the easiest mode of contact for people to ignore – particularly as the inbox sizes of busy people continue to expand – as well as the need to have accurate contact information from people who have opted in to hear from you, to avoid consequences for spamming from your internet services provider.

A common thread through each of these marketing approaches is data quality. Inaccurate, incomplete or outdated contact information will cost you in time and marketing expenditure at the very least, and in the worst cases could subject your business to substantial penalties. And in a world where up to 25% of your contact data is bad, and up to 70% goes out of date each year, a data quality strategy is absolutely necessary for effective marketing.

The best marketing strategy? As we said earlier, it depends. But with the right approach to data quality, you can get the maximum ROI from any approach that fits your business.

In this demonstration I am going to show you how to implement our DOTS Address Validation 3 web service with JavaScript and no Asp.Net markup tags using Visual Studio. We are going to create a form for address inputs, similar to what you would see on a checkout page, which will call our API to validate the address. Although, we could call the web service directly from JavaScript, we would then be forced to expose our license key. So we will use an aspx.cs page to handle our call to the service API, keeping our license key safe from prying eyes. In this demonstration, I will also show you how to add the NuGet version of DOTS Address Validation 3 to the project so that you are always using our best practices and speeding up your integration.

First, create a new empty web site, which I am going to call, cSharpJavascriptAjax. Then I am going to add a new html page called, Addressvalidation.html.

Next, we are going to add the markup for the form. Add the following code in between the body tag.

This form was designed using the table structure for the layout. You will likely want to create the layout using divs, which is more appropriate. Here is what the page looks like in the browser.

To speed things up a bit, I am going to include jQuery in the header so we can utilize some of the short cut functions. Of course, all of this can be done in pure JavaScript.

For the action we will take when the Complete button is clicked, we will create the submit function. This will take in all the values from the form, call the web service and then display the response to the screen. I added an alert and left the URL blank, this will allow for a quick test to make sure what we have is working. Later we will update the failure and success sections as well. For now, they will simply display an alert for testing.

First, let’s start by making sure we are getting all the inputs into the submit function and are getting all the inputs back. I am going to display an alert with DataValue variable so we can see what we have.

Good, now that we know that is working, we will need to make the call to the web service. Like I mentioned before, we could call the service directly but using JavaScript would make the license key visible. So we are going to leverage asp.net for security by creating and empty aspx page and add a method to the aspx.cs page to handle the call. Let’s go ahead and add the aspx/aspx.cs page to the project and call it, ServiceObjectsAPIHandler.

Here is our empty aspx.cs page, where we will be adding our function. It will go below the Page_Load method.

Let’s call the method, CallDOTSAddressValidation3_GBM. There are two things to notice with the signature for this method. We decorate the method with the WebMethod attribute so that our new method can be exposed as a web service method. And, we declare it as static because of the stateless nature of the static methods. An instance of a class does not need to be declared.

To test things out, for now we will just take one string input and return it to the Ajax call where we will display it. In order to do this, we will need to adjust our DataValue call in the script on the html page.

We will also need to add the URL and method to the Ajax call.

I also adjusted the alerts so we can see the success or fail.

Great! That worked! Now, let’s write up the code in the aspx.cs page to make the call to the service. We could grab some sample code from the web site and walk through it, but we have documentation and tutorials already on how to do that. Instead, I am going to take a short cut and grab what I need from NuGet. We offer NuGet packages for most of our services, which include best practices such as failover configurations and speeding up the integration time.

To do this, we will need to open up the NuGet Package Manager in Visual Studio under the Tools menu option. When browsing for our services, you can type “Serviceobjects”. You should see a list of available Service Objects NuGet packages to choose from.

Select DOTSAddressValidation3US, you will be prompted to select the project you want to install it under. Select the project and then click install.

Once the installation is complete, a ReadMe file will automatically open that will contain a lot of information about the service. You will also notice a few things were added to your project. First, a DLL for DOTSAddressValidation3US was added to the bin folder and was referenced in your project.

Next, an AV3LicenseKey app setting was added to your web.config file with the value “WSXX-XXXX-XXXX”. You will need to substitute this value for the key you received from Service Objects.

Also in the web.config you will see several endpoints were added. These will be used in the pre-packaged code to determine how to call the service based on your key.

Now that we have the NuGet package added to the project, we can use it. Next is the code that will use the DOTSAddressValidation3US DLL by loading it up with the input parameters, making the call to the service, then working with the response and finally sending the data back out to our JavaScript.

First we get the license key from the web configs file.

Then we make the call to the service. You will notice that we throw in a Boolean parameter at the end of the call to GetBestMatches for live or trial. This is an indicator that will tell the underlying process which endpoints to use. A mismatch between your license key and this Boolean flag will cause the call to the service to fail.

After we make the call to the service, we will process the response and send the data back to the JavaScript. If there is an error, we will return the error details. Otherwise, we will return a serialized version of the response object. Note that you can also just deal with the response completely here or completely in JavaScript. I mixed it up so you can see a bit of both.

Now we will turn our attention back to the JavaScript and update our submit function. All we really have to deal with now is the response from the aspx method call. Here is the portion of the Ajax call implementing that.

Success or failure here does not mean that the address is good or not. It is really just a success or failure of the call to the aspx web method. On failure, we simply make an alert stating something went wrong. On success, we examine the response value, determine if the address was good or not and display the appropriate response. Here is the whole submit function.

 

Here is a good address.

 

And here is a bad address.

 

In the submit function, we did the most basic check to see if an address was good or not.

But many more data points from the response can be used to make any number of conclusions about an address. One thing you will notice is that AddressResponse.Addresses is an array. A check to see if multiple addresses are returned can be valuable because in certain situations more than one address may be returned. One example is when an East and a West street address are equally valid responses to an input address. In this case you may want to display both addresses and let the user determine which to use. You may want to evaluate the individual address fragments or the corrections that were made to the address.

The data points associated to the DOTS Address Validation US 3 service can be found on our development guide page for the service.

The following is commented out code that I added to the submit method for easy access to the various output data points.

And here is the same thing but for the Error object in the aspx page.

I hope this walk-thru was helpful in demonstrating how to implement our DOTS Address Validation 3 web service with JavaScript and no Asp.Net markup tags using Visual Studio. If you have any question, please feel free to contact Service Objects for support.

This is where the US government comes in. The federal universal service high-cost program – also known as the Alternative-Connect America Cost Model (A-CAM) – is designed to ensure that consumers in rural, insular, and high-cost areas have access to voice and broadband service at rates that are reasonably comparable to those in urban areas. And Service Objects is excited to help carriers find and deliver broadband internet to these hard-working rural Americans by introducing an indicator in our Address Geocode US that will let carriers know if the location is eligible for A-CAM funding.

The Connect America Fund is a win-win for everyone involved. It incentivizes the growth of rural internet access by reimbursing carriers for a portion of their costs of development, from the federal Universal Service Fund. Currently the Fund offers over 1 billion dollars annually to help defray the high cost of running fiber optic cables and equipment to sparsely populated areas, for carriers of all sizes. This can

Internet access is about much more than posting selfies to your Instagram feed. Today, it has become the engine of both commerce and human connection. The United Nations and the US both recognize that the internet has become so fundamental to freedom of expression and opinion that it is a basic human right needed for all people. But for many people living in rural areas of the United States, affordable internet access is still out of reach. According to US News and World Report, only 55 percent of rural Americans have access to broadband internet, versus 94 percent of urban dwellers.

quickly add up to a big source of income for the carriers and a great incentive to expand their coverage.

But there is a catch. To compete for these grants, carriers must submit the addresses, GPS coordinates and several other key pieces of information to the FCC. The deadline for 2016 funds is barely a month away – on July 1st, 2017 –so finding all the businesses and households located in these remote areas is not easy. Some of these addresses do not have mail service, others are just work sites such as barns or grain silos, and many are not the main address of the business. But all of these locations would still benefit from high speed internet, AND contribute to the per-address size of the carrier’s grant.

This is where Service Objects can help. Our Address Validation product can verify, correct and append address information, as fast as 150 milliseconds per record, using our CASS-certified USPS database engine. And our Address Geocode product can translate these addresses into exact latitude-longitude coordinates, with property-level match rate accuracy up to 99.8% and indicate if the location is within the funding boundaries. Both of these products can be put to work right away, as either an API for your application or through convenient batch list processing.

According to the Hudson Institute, rural broadband companies contributed nearly $25 billion US dollars to the economies of their states, were responsible for nearly 70,000 jobs, and supported over $100 billion dollars in e-commerce in 2015. And the impact of this broadband access ranges from the ability to locate manufacturing plants in rural areas, all the way to telehealth capabilities that bring top medical expertise to patients in remote areas. It is truly an enabling technology for closing the digital divide that still impedes economic growth in these areas.

Many people don’t realize that rural America was actually the birthplace of much of our modern telecommunications – long before most of us had phones, farmers would talk with each other on networks connected through barbed-wire fencing. Today, it makes perfect sense to have the online era come full circle to a population that needs and deserves the right kind of access.

Service Objects is proud to help with this initiative. We can now import the footprint of service from a rural carrier and match all eligible addresses within that area and provide the information needed to submit to the FCC. This allows the carriers to maximize funding of A-CAM and get their portion of the 1 billion dollars at stake.

If you would like more information on how we can help with Connect America Fund, send an email to communications@serviceobjects.com.

The reality about any set of residential customer data is that given enough time, addresses and the people living there are bound to change. Occasionally, businesses and organizations can rely on the customer to notify them of changing addresses but when people move, this often times falls to the wayside on the list of priorities.

For cases like these, accessing the USPS National Change of Address database can provide a helpful solution to ensure that mail gets delivered to the correct person. The USPS maintains a large data set of address forwarding notifications, and with the DOTS NCOA Live service, this information is right at your finger tips.

Our DOTS NCOA Live service is a bit different than the rest of our products. Most of our other products process validation requests in a one at a time manner. NCOA is a little different in that in order to start a request, a minimum list of 100 addresses must be sent to the service, and from there anywhere from 1 to 500 records can be processed at a time. To show you how it works, we’ve put together a quick step by step tutorial.

What You Will Need

• C# experience
• Visual Studio ( VS 2015 is used for this example)
• A DOTS NCOA Live license Key. A free Trial Key can be obtained here.

Project Creation and Setup

To get started, go ahead and launch Visual Studio and select File->New->Project.  From here you can choose whatever project will meet your needs. For this example, we’ll be creating a very basic console application.  So if you want to follow along step by step, you can choose the same project details as shown below.

Select OK and wait for Visual Studio to finish creating the project. Once that is done, right click the project, select Add and then select Service Reference. Here, we’ll enter the URL to the WSDL so that Visual Studio will create all the necessary classes, objects and methods that we’ll use when interacting with the DOTS NCOA Live service. To successfully do this, add the necessary information into the pop up screen as shown in the screenshot below.

Select OK. Now that the service reference is successfully set, open up the App.Config. Below is a screenshot of the App.Config that has been modified.

We’ve added the appSettings section and within that we’ve added two key value pairs. The first is the license key field where you will enter your key. Storing the license key in the app or web config files can be helpful and easy when transitioning from a trial to a live environment in your application. When you are ready to use a production key, changing it in the app config is an easier option than having to change a hard coded license key.

We’ve also put the path to a csv that will contain the address and name information that we will be sending to the NCOA service. You may not want to read in a CSV for your application but the process of building the input elements for the service will be relatively similar. For this example, we’re just going to put the file in the BIN folder of our project, but you can add any path you want to the file.

We’ve also increased the maximum buffer size in the http Binding. Since we’ll be sending a list of 100 addresses to the DOTS NCOA Live service, we’ll indeed need to increase the buffer size.

Lastly, we’ve changed the name of the original endpoint to “PrimaryClient,” made a copy of the endpoint and changed that name to “BackupPoint.” Currently, both of these endpoints point to the trial Service Objects environment, but when a production key is purchased, the PrimaryClient url should point to http://ws.serviceobjects.com/nl/ncoalive.asmx and the BackupClient should point to http://wsbackup.serviceobjects.com/nl/ncoalive.asmx.

Calling the DOTS NCOA Live web service

The first thing we’ll do is instantiate two static strings outside of the Main method. One will be for the input file, and the other will be for the license key that we’ve placed in the app.config. Inside the scope of the Main method, we’ll instantiate a NCOAAddressResponse object called response and set it equal to null. We’ll also create a string called jobID and set that equal to null as well.  This jobID will be passed as a parameter to our NCOA service call. A JobID can be seen as a unique identifier for all the records that are run against the service.

Now we’ll create the following method that will read our input file.

This method will return a List of the NCOAAddress object that will have all the inputs we need to send to the service. In my particular file the fields are as follows: Name, Address, Address2, City, State, Zip.  Your code will need to be modified to read the specific structure of your input file. This code reads in the file and then loops through each of the lines and adds the appropriate values to the fields of the NCOA address object. After the line is successfully read, we add the individual NCOAAddress objet to the list called inputAddresses and then return that object once the code has finished looping through the file.

Now we’ll insert a try catch block into the main method. Within this try catch block we’ll create a List of the NCOAAddress object and call the readInputFile method to fill it. We’ll also make a JobID with today’s date appended to the end of it. You will likely want to customize your job id to fit into your business application. Jobs close on Sunday at 11:55 PM so that is also something to take into consideration when designing your code.

Failover Configuration

Now that we have all our inputs successfully set up, we are able to call the NCOA web service. The first step we’ll take is create another try catch block to make the web service calls in. We will also create an instance of the DOTSNCOALibraryClient and pass in the trip “PrimaryClient” as a parameter. This will ensure that our first call to the NCOA service will point to our primary URL that we have defined in the web config. Next we’ll make the call to the webservice using the library client and set it equal to our response object.

After we get a response back from the service we’ll perform our failover check. We check if the response is null or if an error TypeCode of 3 was returned from the service. An error type code of 3 would indicate that a fatal error occurred with the service. If either of these criteria are met, then we’ll throw an exception that will be caught by the catch block we have created. Within this catch block we’ll set the library client object to a new instance with the “BackupClient” string passed to it to ensure that we call the backup client. The code should look like the following.

This failover logic will ensure that your application stays up and running in the event that a Service Objects web service is unresponsive or in the event that it is not behaving as expected.

Processing the Response

Now that we have successfully called the service, we’ll need to do something with the response. In this tutorial, we’ll take the results from the service and download them as a CSV into our bin folder.

To do this, we will call and create a method called processResponse that will take a NCOAAddressResponse as an input. This method will take the outputs from the service and build a DataTable that we will use to eventually turn into a CSV. This can be done as shown in the following screen shot.

 

 

Now that our output data table has been created, we’ll call and create two methods will loop through our DataTable and convert it to a CSV string, and then write that CSV to the bin folder.  The code to perform this is shown below.

More information on all the elements in the response object can be found on our developer guide for the NCOA service.

Now that our output data table has been created, we’ll call and create two methods will loop through our Data Table and convert it to a CSV string, and then write that CSV to the bin folder. The code to perform this is shown below.

Now our code is ready to run and the service is ready to test.

We’re always available for assistance, so be sure to contact us with any questions about integration for NCOA or any of our other services.

While Mother’s Day is all about the Moms in our lives, it’s an even bigger day for retailers. This year the National Retail Federation estimates Mother’s Day spending to reach an all-time high of $23.6 billion; roughly $10 billion higher than 2010. The traditional gifts of jewelry and flowers, along with personal services are predicted to contribute the most to this increase. Needless to say, with Mother’s Day only a few days away, businesses are experiencing a busy week, especially in ecommerce.

According to the National Retail Federation’s annual survey, conducted by Prosper Insights & Analytics, 30% of Mother’s Day shopping is to be done online this year. Most ecommerce sites have already experienced an influx of orders over the last few weeks. With an even bigger rush coming in now from typical procrastinators (like myself) who will take advantage of two-day delivery from retailers like Amazon. Online shopping has become even more convenient with the addition of mobile shopping. With thousands of easy to use mobile apps offering gift cards for anything from dinner to spa treatments, redeemable right on the recipient’s mobile device, digital sellers have definitely made Mother’s Day purchases easier than ever…even for the most ardent procrastinators.

Unknown to most, data quality solutions are quietly working behind the scenes contributing to a smooth and happy Mother’s Day for businesses and celebrants alike. Data quality solutions have made processing increased online holiday orders, restaurant reservations, and mobile app purchases more efficient and safer than ever. By leveraging tools like our Address, Phone and Email Validation services, our clients ensure that their customer contact information is complete and accurate while also identifying malicious fraud before transactions are completed. Our data quality tools give businesses more time to focus on providing memorable experiences for their customers and achieving their revenue goals on the busiest of holidays, including Mother’s Day.

Whether our clients are experiencing or still preparing for a busy Mother’s Day, our data quality solutions will be running smoothly in the background for them the entire time. If your business needs any assistance now or before the next major holiday contact us.

Before moving to my current home, making sure I completed a change of address form with the Post Office was on the top of my “to do” list.  Although most mail received these days is typically coupons and business advertisements, I looked forward to receiving the first piece of mail with my name and new address on the envelope. What can I say… I appreciate the little things in life.

Well, the first time I checked the mail I found a letter addressed to the prior resident. As I had recently filled out my own change of address form at the post office I understood it would take some time for each other’s information to be updated and anticipated this would continue happening for a bit. As expected, I began receiving mail addressed with my name soon after. However, years later I’m still getting the same letter from one particular storage company for the prior resident.

At first, I tried writing “Not at This Address,” “Moved, Left No Forwarding Address” and “Return to Sender” on the letters. After a couple months I realized this did not work. The next thing I tried was calling the storage company. I thought the human element of speaking to someone over the phone and explaining the situation would resolve the case of this never ending letter. This also did not work and actually seemed to make it worse.

As I mentioned previously, the bulk of my mail (like many other people) consists of coupons and advertisements addressed to “current resident” which are seemingly impossible to stop. Along with these, the never ending letter from this storage center started taking the excitement out of checking my mail. For a few years, checking the mail monthly instead of every few days became the routine. Every month, my mailbox was filled to max capacity with mainly junk and of course a letter (or two or three) from the storage center. Unfortunately there are some draw backs to checking your mail so infrequently. I eventually learned that if the mail does not fit in your box it is sent back to the post office which is how I missed a wedding invitation and a few birthday cards. Needless to say I went back to checking my mail more frequently and simply continued sending back the storage company letter hoping they’d eventually run their customer database through a National Change of Address (NCOA) service.

While this situation was obviously annoying, I also wondered how much this letter alone must be costing the storage center. At this point, I estimate receiving about 100 copies of the same letter equating to:

• $46 in just postage, each has a $0.46 First-Class stamp
• 100 wasted envelopes
• 100 wasted pieces of paper
• Ink for each letter
• Wasted time/salary of the person(s) at the storage center responsible for mailing
• Wasted time for the mail sorter(s)
• Wasted gas and time of the mail carrier(s)
• A big Headache for me over the last few years
• Possible frustration for the last tenant who still hasn’t received this letter (I’m assuming it’s a bill which is even worse if they are incurring additional costs all this time)

Ultimately, this also damaged the reputation of the storage company. This mail discrepancy gave me a glimpse into their lack of customer service, organization and concern for our environment. By simply implementing an address validation check in their processes this entire scenario could be avoided. What’s worse is imagining how many other letters they are sending to the wrong address.

After further research, I found out anyone can submit a change of address form at the post office for prior tenants by making a note that they did not provide a forwarding address (the online form requires a forwarding address to submit). I’ll be heading to the post office today to fill one out. If that doesn’t resolve this, I also learned storage centers eventually auction off your items if you don’t pay your bills. Although I don’t want the prior tenant to lose their personal items, I’ll be glad to stop receiving these notices.

Until then…

If your business needs help avoiding unnecessary costs, resources and headaches associated with outdated customer information including name, address, phone, email and more contact us!

Java is easily one of the most popular programming languages in the world. It is a general purpose language that users have managed to implement in a variety of applications. It is popular with web applications; which is why it is one of our most requested sample code languages for our DOTS validation products. This is no surprise either, since Java is able to run on a wide range of architecture, applications and environments.  Since it is so popular, we’re here to show you the ropes and get a Service Objects web service up and running.

For this example we’ll be using a fairly new operation in our DOTS Address Detective service. Our Address Detective service is a power house address validation service that can leverage multiple different data sources to validate an address.  The DOTS Address Detective service has input fields for a person’s name, a business name, and a phone number along with the traditional address fields. These additional data points help the service leverage other data sources to get your address validated.  This service even has an operation that will take your data in any order it’s given and return a standardized address. It’s called FindAddressLines and has 10 inputs ranging from “Line1” to “Line10” and can work wonders on standardizing messy data sources.  We’ll be integrating with this operation in our tutorial today, so let’s get started!

What you’ll need

• A Java IDE (We’re using Eclipse for this example)
• Basic Java Knowledge
• A Service Objects DOTS Validation product License Key (We’re using DOTS Address Detective for this case)

Setting up the project

Launch Eclipse and select a workspace if it asks you do so. Once everything has finished loading,  select File->New->Other. In the search field type “Dynamic Web Project” and click next.

On the next screen, type in an appropriate project name and configure the settings to our specific needs. Congratulations, you’ve built a project! We’ll need to add several files to take in our inputs, send them to the DOTS Address Detective service, serialize the XML response and display the results back to the user. To start, add two jsp files by right clicking the project and selectingNew->JSP File as shown below:

In this tutorial we’ll name them “inputForm.jsp” and “webServiceCall.jsp.”  These will function as the input form and the display page for the results from the service.

These new JSP files will obviously need something more than they currently have. We’ll place all the necessary HTML elements in the inputForm.jsp file. Make your page look like it does below:

These 10 input lines will send all the necessary information to the FindAddressLines operation.  Now that we have the necessary fields to take our input parameters, we’ll need to put the code in place to actually call the DOTS Address Validation web service. We’ll create a package with the necessary class files for the response from the Address Detective service and within that package we’ll create a method that will actually perform the call to the web service.

To add a package, right click the project and select New->Package.  For this project we’ll name the package “serviceObjects” as shown below.

Be sure to select the “Create package-info.java” checkbox as we’ll need to add some necessary import statements into the package.info file.  After the package as been added, right click it and select New->Class and add all the following classes to the project.

We’ll talk briefly about the necessary code to add to each of the different objects and classes so that the XML response from the web service will be successfully deserialized into the objects that we are defining here. One thing that needs to be added to the package-info.java file is as follows.

This will let the code know that it should expect the http://www.serviceobjects.com namespace in the XML response from the service.

Like most classes, all the values in each of the code files will need the “getters and setters” for each of the objects that the service returns in order to properly work with the returned object. The highest level object that is returned from the service (meaning all the other objects and values will be contained within that one) will be the FixedAddressResponse. This object will contain a possible array of FixedAddress objects that is called “Addresses” and it will contain an Error object that the Address Detective service can potentially return. See below for an example of how to format the declarations and, XML annotations and the “getters and setters.”

As mentioned this is a general example of how to do this and we’ll include all the class files with this tutorial so that they can be easily added to your own project.

Now we’ll point out some things to be aware of in our “ADClient” file.

Inside the class declaration, we’ll define a few things that we’ll need to make the actual call to the service.

In the above code, we’ve defined both the trial and the backup URLs. Currently, they both point to the trial environment Service Objects servers. In the event that a license key is purchased the primary call should be to ws.serviceobjects.com and the backup URL should be to wsbackup.serviceobjects.com. We’ve also defined our LicenseKey in the class which will allow us to keep it hidden from outside view and we’ve defined a method called “FindAddressLines” that will eventually call the same operation. Notice that it returns the FixedAddressResponse object.

Within the actual method we have some cleanup logic that is performed on the input strings, and then the URLs are assembled for the HTTP call. See below:

In the above snippet of code URL strings are assembled and sent to the DoHTTPRequest method. After the web service is called, it is necessary to do a check to ensure that the call was completed correctly. The code will check for a null response from the service or a ‘TypeCode” of 3 is returned which would indicate a fatal error from the Service Objects web service.  If either of those conditions is true, then the code will throw an exception and use the backup URL.  The above functionality and logic will ensure that your application will be uninterrupted in the unlikely event that the Service Object servers are non responsive or returning a TypeCode of 3.

Displaying the results from the web service

Since our failover logic and call to the DOTS Address Detective web service are set up, we can now create the objects that will call the web service with the inputs from the input form, and display the results to the user.

Navigate to the webServiceCall.jsp file and implement the following code:

In this bit of code we’ll grab the inputs from the inputForm.jsp page and place them in strings of the same name.  We’ve also instantiated an instance of the “FixedAddressResponse” object which will hold the results from the service and the “ADClient” object which will make the actual call to the web service.  Since our FindAddressLines method in the ADClient object returns a FixedAddressResponse object we can set it equal to it.

Our call to the web service is all set up and now we can implement some logic that will either display the results from the service.  Implement the following logic in your JSP page.

This code will first check if an error is present in the response; if it is present it will display that error to the screen. If the error response is null, it will display the validated response from the service.  Notice that we call the “getters” that we have previously defined in our response class to display the results to the user.

We now have everything we need to use the service, let’s see it in action!

As mentioned previously, the FindAddressLines operation can take the inputs for an address in any order and return the validated output address.  See below for an example.

After we send that input to the service, we will receive this response:

You are now all set to test the FindAddressLines operation in the DOTS Address Detective web service. Sample code downloads are also available for all of our other services. As always if you have any questions about integrations, service behavior or best practices, feel free to contact us and we will gladly assist in any way that we can!