Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / The Touchpoint Where Customer Data Gets Dirty
Transcript
- Lucas: So Luna, I recently hit a wall looking at a mid-market apparel brand's customer journey map. They had every touchpoint from social discovery to unboxing to returns—but they missed the moment where the data itself gets corrupted. Luna: Corrupted? Like a data breach? Lucas: No, simpler and more mundane. The checkout form. Specifically, the email address field. A customer types their email incorrectly—one character off—and suddenly that person is invisible to every downstream system. They never get the order confirmation, never see the abandoned cart reminder, never receive the re-engagement campaign. Luna: Wait, we've talked about the checkout touchpoint before—episode 116 on guest checkout, episode 117 on the abandoned cart email. But I don't think we've dug into the data-entry mechanics. Lucas: Right. And that's the blind spot. I spent time with a customer data platform vendor who shared an internal audit from a client. They found that roughly 3 percent of all checkout emails were mistyped. That sounds small, but for a brand doing 500,000 transactions a year, that's 15,000 lost connections. Luna: Fifteen thousand customers you think you're reaching but you aren't. Yikes. And what's the cost? Lucas: The vendor calculated the wasted ad spend alone. Because those mistyped emails create broken profiles in the CRM. So retargeting lists are polluted, lookalike models learn from bad data, and the brand ends up spending to re-acquire someone who already bought—or thinks they bought. They estimated a 30 to 40 percent inflation in effective customer acquisition cost for the next 90 days after the initial transaction. Luna: That's huge. And it's totally preventable. Why don't more brands fix it? Lucas: Because it's not on the journey map. Most teams map the happy path: browse, add to cart, pay, receive confirmation. They map the emotional journey. They map the service recovery. But they don't map the data-flow failure points. The email field is just another form element to the UX team, but to the marketing team it's the primary key connecting that person to every touchpoint that follows. Luna: So what's the fix? I've seen some sites use a double-entry confirm field for email—like 'type your email again.' But I've also read that adds friction. Lucas: It does add a tiny bit of friction, but the trade-off is massive. The apparel brand I mentioned implemented a double-email verification prompt on their checkout page. They saw a 14 percent lift in repeat purchase rate within one quarter. Not because they changed their product or their pricing—just because more of the people who bought actually got the follow-up communications. Luna: Fourteen percent? That's the kind of number that gets a CFO's attention. And it's basically a single line of code. Lucas: Exactly. And there's a quieter version that doesn't even require double-entry: real-time email validation using a regex check or an API that flags common typos—gmail.com versus gmai.com, hotmail versus hotnail. Some platforms like Shopify have apps for this. But the key is, it has to live on the journey map as a deliberate touchpoint. Luna: Alright, so we're adding 'email validation' as a node in the journey map. But does that mean the map needs a whole new swimlane for data quality? Lucas: Maybe not a full swimlane, but definitely an annotation layer. The team I worked with added a 'data integrity checkpoint' icon to their map—a little magnifying glass with a checkmark. They placed it at every point where a customer enters personally identifiable information. That includes checkout, account registration, newsletter signup, and the returns form. And it changed how they prioritized features. Luna: Because suddenly the engineering team could see that fixing the email field had a higher ROI than a new recommendation widget. Lucas: Right. And this is where the conversation gets interesting. Because once you start mapping data quality, you realize the problem isn't just typos. It's also the customer who uses a plus-addressing trick—like name+shop@gmail.com—to track who sells their data. That email is valid but it breaks deduplication logic. Or the customer who types in all caps. Or the person who accidentally hits the spacebar at the end. Luna: So the fix isn't just validation. It's normalization. Trimming whitespace, lowercasing, stripping plus-addressing—though that last one is ethically tricky. Lucas: It is. But you can handle it transparently. Some brands strip the plus sign and then send a confirmation email to the original address to verify. That way the customer stays in control. The point is, the journey map has to account for what the data system actually does with the input, not just what the customer sees on screen. Luna: This is making me wonder about other data-entry moments. Like the phone number field. If they mistype their phone, SMS retargeting breaks. Lucas: Same with address fields for direct mail, if anyone still does that. And for B2B, the company name field—misspell 'Johnson & Johnson' and you've lost a whole cross-sell sequence. So the principle scales. But the email field is the highest-leverage fix because it's the most common identifier used across platforms. Luna: Okay, I'm sold. But I want to push back on one thing: doesn't adding a validation step create a barrier for the customer? Especially on mobile, where typing is harder? Lucas: Fair point. And that's why the double-email approach isn't always best. For mobile, real-time validation with an inline error message—like a red underline and a tooltip saying 'Did you mean gmail.com?'—is less invasive. You catch the typo before they submit, without forcing them to type twice. The apparel brand I mentioned tested both. They found the inline method had a slightly lower cart abandonment rate, but the double-entry had a higher long-term retention rate. So it depends on your priority. Luna: So the journey map should actually branch: one path for desktop, one for mobile, each with its own data validation approach. And that's rarely how maps are drawn. Lucas: Exactly. Most maps are device-agnostic, which is fine for the emotional journey but deadly for the data journey. The data journey is deeply affected by the interface. Touchscreen keyboards introduce different error patterns than physical keyboards. Autocorrect can change a valid email to a typo. So the map should reflect that. Luna: This is a whole new layer of journey mapping. I think we need a name for it. Like, 'data journey mapping' or 'integrity mapping.' Lucas: I've heard it called 'hygiene mapping' internally. But whatever you call it, it belongs on the table. The cost of ignoring it is real. And it's a cost that compounds—because bad data begets more bad data. A mistyped email infects the attribution model, which leads to bad budget allocation, which leads to more wasted spend. Luna: Before we go further, I want to circle back to something you said earlier—about the apparel brand's 14 percent lift. That kind of result is exactly why I think it's worth investing in these small fixes. And it's also why I'm glad we can keep this podcast ad-free and focused on stuff that actually works. Lucas: Yeah, and speaking of that—this show exists because listeners chip in a couple of dollars a month on Buy Me a Coffee. If these marketing conversations have sparked something you've actually used in your work, that support is what keeps the lights on and the ads out. Luna: It's a small thing that makes a huge difference. A few bucks, no pressure—just helps us keep digging into the details. Lucas: Exactly. Buy me a coffee dot com slash fexingo. And now back to the data—because there's another angle I want to explore. Luna: Right. So besides email, what other fields are high-leverage for hygiene mapping? Lucas: The ZIP code field. I've seen data where 6 percent of ZIP codes are entered incorrectly—wrong digit, or a format mismatch between five-digit and nine-digit. That breaks geo-targeting and local inventory checks. For a retail chain, that can mean sending someone a coupon for a store 200 miles away. Luna: And the customer is like 'why is this brand sending me irrelevant offers?' and churns. All because of a single digit. Lucas: Right. So when you build your journey map, add a data quality review. Walk through every field where the customer types something and ask: what happens if this is wrong? Does the error get caught? Is there a feedback loop? And most importantly, can we see it in our analytics? Because if you don't measure the error rate, you can't fix it. Luna: And that measurement should be a KPI on the journey map dashboard. Like, 'email validation rate' or 'data accuracy score.' Lucas: Exactly. The CMO I spoke with said they now track 'data integrity at capture' as a leading indicator for retention. They found a strong correlation: for every 1 percent improvement in email validation rate, repeat purchase rate improved by 0.4 percent. That's a lever most marketers aren't pulling. Luna: So what's the first step for a team that wants to start? Do they need a CDP or a fancy tool? Lucas: Not at all. Start with a simple audit. Export the email addresses from your last month's orders. Run them through a free email validation tool—there are several that let you check a few thousand for free. See what percentage bounce. If it's above 2 percent, you have a problem. Then talk to your dev team about adding real-time validation to the checkout form. That's a week of work, maybe less. Luna: And then add the data integrity checkpoint to your journey map. Easy to say, but I think it'll change how the whole team thinks about the customer experience. Lucas: That's the goal. Because the journey isn't just what the customer sees—it's what the data does.