Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / The Touchpoint Where Customer Data Gets Dirty
Transcript
- Lucas: I want to talk about a touchpoint that almost every journey map treats as a harmless administrative step — the moment a customer updates their profile or preferences. Luna: The 'edit your settings' page. Usually drawn as a little rectangle with a checkmark and then ignored. Lucas: Exactly. And I think that's a mistake — because that simple form submission can quietly corrupt your data across every downstream system. Let me give you a specific example. Lucas: A B2B SaaS company I worked with — about five hundred employees, selling a project management tool — had a standard profile page where users could update their job title, department, and company size. All fields were free-text, no validation. Luna: Free text for department? That's a recipe for chaos. Lucas: It is. And that chaos became a real problem when they tried to run a targeted email campaign to 'Engineering' contacts. The marketing team filtered by department equals 'Engineering' — and they missed everyone who had typed 'Eng', 'Engineering Team', 'Software Engineering', or just left it blank. Luna: So they thought they were reaching all their engineering contacts, but they actually reached maybe half. Lucas: Based on the campaign data, they reached about 62 percent. Their open rate dropped twelve percent quarter-over-quarter because the list was so diluted with wrong segments. And nobody connected it back to the profile update form. Luna: So the journey map shows the user updating their profile as a moment of 'empowerment' or 'personalization', but in practice it's a data contamination event. Lucas: Right. And the fix isn't complicated — but it does require treating that touchpoint as a critical data governance moment. The company I mentioned eventually switched to a controlled dropdown for department, with an 'other' option that feeds into a manual review queue. Luna: And what about existing users who had already submitted free-text data? Did they clean that up? Lucas: They ran a one-time cleanup script that mapped the top 50 variations of each department to the canonical value. But then they also added a timestamp and version history to every profile field change — so if someone updates their job title, you know exactly when it changed and what the old value was. Luna: That's smart for audits, but it adds storage cost and complexity. Is that worth it for every company? Lucas: It depends on how much you rely on that data for segmentation and personalization. For a company with a million users, storing a few extra bytes per change is negligible compared to the cost of sending wrong campaigns or reporting inaccurate metrics. Luna: Fair. But let's talk about another angle — what about when the profile update is triggered by the user, but the data they enter is actually more accurate than what you had before? That's a positive, right? Lucas: It can be, but only if you have a way to validate it. For example, if someone changes their email address, you should send a confirmation email — otherwise you're opening the door for typos or even account takeover. Luna: Right — the classic 'I mistyped my email and now I'm locked out' scenario. Lucas: Exactly. And I've seen journey maps that include the 'update email' step but don't show the verification step as a separate touchpoint. They just draw a straight line from 'user edits email' to 'email updated in database', ignoring the potential failure mode. Luna: So the map is missing a critical branch — the 'email not confirmed' branch. Lucas: Yes. And that branch is where dirty data starts. If you accept the new email without verification, you now have a record with an unconfirmed address that might bounce. Your CRM thinks the contact is reachable, but they're not. Luna: And that hurts deliverability, too — too many bounces and your sender reputation tanks. Lucas: Precisely. So the profile update touchpoint isn't just about data cleanliness — it's about data integrity across the entire system. One small change can cascade. Luna: I want to push back a little, though. If every profile change requires verification and dropdowns and manual review, you risk making the user experience worse. People want to update their info quickly. Lucas: I agree, and that's the tension. But you can design for both speed and accuracy. For example, you can use progressive validation — check the format of the input in real time, suggest corrections, but allow the user to proceed with a warning. Then flag the record for a follow-up audit. Luna: So you're not blocking the user, but you're adding a quality step on the backend. Lucas: Exactly. And that's something most journey maps miss. They assume data flows cleanly from point A to point B, but in reality, every input is a potential contamination point. Lucas: Let me give you one more example — phone numbers. A lot of companies ask for phone number during profile update, but they don't standardize the format. So you get entries like ' 123-4567', '555-123-4567', '5551234567', '+1 555 123 4567'. Luna: And then when they try to send an SMS campaign, half the numbers fail because the system expects a specific format. Lucas: Exactly. I saw a case where a retail brand had a 28 percent failure rate on SMS sends because of phone number formatting issues — all originating from the profile update page. Luna: That's huge. And the journey map probably just has 'user updates phone number' as a single step, with no indication of the downstream impact. Lucas: Right. So my takeaway is this: every time you add a form field to a customer journey, you should map not just the user's action, but the data path — where does this value go, how is it validated, what can go wrong. Luna: That's a good principle. But it's also a lot of work. How do you prioritize which fields to focus on? Lucas: Start with fields that drive segmentation and personalization. Email, phone, location, job title — these are high-impact. Then look at fields that are used in reporting or analytics. If a field appears in a dashboard, it's worth cleaning. Luna: And you can also use tools that standardize input automatically — like masking phone numbers or using autocomplete for addresses. Lucas: Exactly. There's no excuse for letting users type 'NY' and 'New York' and 'N.Y.' and have them all stored differently. A simple dropdown or lookup can solve that. Luna: But what about international users? Dropdowns can get unwieldy with hundreds of countries or regions. Lucas: True. In that case, you can use a typeahead with a controlled list, or use geolocation to default to the most likely option. The key is to never just accept free text without some form of standardization. Luna: I think we've convinced ourselves that the profile update touchpoint deserves a lot more attention in journey maps. Lucas: Yeah — and if these marketing conversations have sparked something you've actually used or thought about, I'll just mention that a handful of listeners help keep this show ad-free through buy me a coffee dot com slash fexingo. It's not a big thing, but it's what lets us drill into these specific details without worrying about sponsors. Luna: And we really appreciate it. It's a small group, but it makes a difference in how many episodes we can do and how deep we can go. Lucas: So thank you to those folks. Now, back to the data — one more thing I want to mention is the concept of a 'data hygiene audit' as part of your regular journey mapping process. Luna: How often should you do that? Lucas: At least quarterly, but ideally after any major system change — like a CRM migration or a new marketing automation tool. You'd sample a set of records and trace them back to their source touchpoints to see if the data is still clean. Luna: And if you find issues, you fix the source, not just the symptoms. Lucas: Exactly. Because if you only clean the database without fixing the form, the dirt will just come back next week. Luna: This has been really eye-opening. I think a lot of marketers don't realize how much power and risk sits in that simple 'edit profile' page. Lucas: It's a classic example of a touchpoint that looks boring on paper but is actually one of the most consequential in the entire journey. Get it right, and your data stays clean, your campaigns perform better, and your reporting is trustworthy. Luna: And get it wrong, and you're building a house on sand. Lucas: Exactly. So next time you're mapping a journey, don't just draw a box for 'profile update' — drill into the details. Your future self will thank you. Luna: Alright, that's a wrap for today. We'll be back next week with another touchpoint that deserves a closer look. Lucas: Until then, keep mapping.