BLOG

Verifying addresses after POS collection

Collecting email addresses at point of sale is a challenge. Some stores collect the addresses electronically, where the clerk or the customer types addresses directly into the register. Smaller stores, however, typically collect addresses on a sheet of paper at the cash register. Eventually someone takes the list and types it into whatever contact management system the store maintains.

There are all sorts of errors that can happen when someone types in an address, but those errors are only compounded when the addresses are written on a sheet of paper for later transcription. Not all of us have perfect, copperplate handwriting and many of us have barely legible scribbles. In one case I had a sender read the tag in my email address wrong causing all their mail to me to bounce.

One person found an interesting solution to the problem of illegible addresses: using Facebook’s lookup to clarify illegible addresses.

To figure out what the addresses should have read, we turned to Facebook which allows you to search for anybody by the email address(es) they have registered (unless they have tweaked some privacy settings). We just kept trying to enter each address we weren’t sure about, permuting a few of the difficult to read letters each time, until Facebook returned a match.aprèsSci

Standard caveats about how the addresses verified as valid addresses may not be the addresses belonging to the store customers, but it is an interesting way to resolve the problem.

3 comments

  1. Chris T. says

    That’s a great idea, just as long as the sender is an honest Joe and is not tempted to scrape addresses from FB. We deal with a number of small businesses that get heaps of bounces due to illegible handwriting. Good article, thanks.

  2. Neal says

    Integrating a email validation API like on from StrikeIron at the point of capture (POS in this case) improves data quality and email verification.

  3. Catherine Jefferson says

    I’ve heard some complaints about Strikeiron marketing to businesses that ran into trouble with Spamhaus, so I’d be cautious where they are concerned. However, the concept of email verification itself is I think a good one. With all the problems caused by typos at points-of-sale and in web forms, I can’t see any objections whatsoever to software that spots likely typos and prompts the user for corrections. Ditto software that spots likely accumulated typos on lists and puts them on a list for a COI loop before continuing to email them.

Comment:

Your email address will not be published. Required fields are marked *

  • HE.net DNS problems

    Hurricane Electric had a significant outage of their authoritative DNS servers this morning, causing them to return valid responses with no results for all(?) queries. This will have caused delivery problems for any mail going to domains using HE.net DNS - which will include some of their colocation customers, as well as users of their free services - but also will have caused reverse DNS to fail for most servers hosted by Hurricane Electric worldwide, so if any of your mail is being sent from HE hosted machines you may have seen problems. (We're HE customers so we noticed. Still happy with them as a vendor.)No Comments


  • 65.0.0.0/8 DNS issues

    If you're sending email from any address beginning with a 65 - in 65.0.0.0/8 - it's possible you'll see some delivery problems. Something appears to be broken with dnssec signatures for the reverse DNS zone, leading queries for reverse DNS to fail for anyone using a dnssec aware DNS resolver (which is almost everyone).1 Comment


  • Our green bar certificate is going away

    Later today we'll be switching from an Extended Validation ("green bar") SSL certificate to a Domain Validation certificate. This isn't exactly a planned change but I'm waiting for responses from Comodo before I go into it too much. I'll share some more details next week.3 Comments


Archives