A great example of a data integrity report!
A couple months back I discussed the importance of data integrity reports. One of my past clients and a longtime reader, David Churchill at Grantmakers in Health, offered up this idea, which I think is fantastic and should be added to any association's list of data integrity reports.
As he explains: "I found that there’s a lot of email address mistakes made during our online registration process. It's not always easy to spot simple typos like .cmo (.com), .ogr (.org) so I created a query that is titled “questionable top level domains” that shows any record with likely typos (or .ru which is largely spam)."
One reason I love this query is that it's designed to capture "common" errors with the knowledge that it won't catch every error. And it has the added bonus of looking at addresses that are likely spam.
But what a great idea! If a customer mistypes their email address, other than checking bounced emails in the future, how will anyone know there is an error? By proactively checking for errors, David is weeding the garden, which is critical to long-term data management success.
Wes's Wednesday Wisdom Archives
Eyes wide open and affirmative decision-making
Eyes wide open and affirmative decision-making When I work with my clients on any type […]
Honoring an industry legend
Honoring an industry legend I’m taking a break from my usual data management tips to […]
Never burn a bridge
Never burn a bridge My children have reached the age where they have, or are, […]
You CAN compete with the big guys…
You CAN compete with the big guys… In my experience, associations often undersell their actual […]
Join (or start) your users group!
Join (or start) your users group! Today’s message is simple: If the AMS you’re using […]
They don’t care, until they care.
They don’t care, until they care. One of the more common questions I get from […]
Longfellow and data management
Longfellow and data management “We judge ourselves by what we feel capable of doing while […]
Do you really need all that historical data?
Do you really need all that historical data? A question I’ll often get from my […]
AI actually requires thinking
AI actually requires thinking “I don’t think AI introduces a new kind of thinking. It […]
It’s not the mistakes, but how you respond
It’s not the mistakes, but how you respond Recently a client was complaining about a bug that […]