Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / Why Your Customer Journey Map Needs a Data Layer
Transcript
- Lucas: There is a difference between a customer journey map that looks good on a wall and one that actually changes how you spend money. And the difference usually comes down to one thing — whether you've put a data layer under it. Luna: A data layer meaning — actual behavioral data, not just what customers tell you in a survey? Lucas: Exactly. Most maps are built on attitudinal data — focus groups, interviews, survey responses where people say 'I usually research on Instagram and then buy on the website.' But what people say and what they actually do are often two different things. Luna: Right, the classic intention-action gap. So a data layer would be pulling from analytics, clickstream, CRM data — the stuff their systems already capture. Lucas: Yes. And the reason most teams don't do it is that it's messy. Journey maps are often owned by the brand or CX team, while analytics lives in a separate silo — maybe product, maybe marketing ops. So the map becomes a creative exercise instead of a diagnostic tool. Luna: I've seen that. A beautifully designed map with icons and arrows, but when you ask 'what percentage of customers actually go from this touchpoint to that one?' — silence. Lucas: Right. So let's make it concrete. I was looking at a case from an e-commerce brand — mid-sized, about fifty million in annual revenue — that had a fairly typical map: social media awareness, email capture, browse, cart, purchase, post-purchase. Standard stuff. Lucas: But when they layered on actual behavioral data — page views per session, time between email open and purchase, repeat purchase triggers — they found something unexpected. Their highest-converting touchpoint for repeat purchases wasn't the post-purchase thank-you page or the loyalty program. Luna: What was it? Lucas: A simple abandoned-cart email that went out twenty-four hours after a completed purchase. Wait — I know that sounds contradictory. But what was happening is that customers who had just bought something would often browse again later that day or the next day, add something to the cart, and then abandon it. That email was bringing them back at a rate of twenty-two percent for a second purchase. Luna: Huh. So the abandoned cart email after a purchase wasn't a mistake — it was a cross-sell trigger they hadn't labeled. Their map had 'abandoned cart' as a pre-purchase step only. Lucas: Exactly. Their data layer showed that the same touchpoint was actually two different journeys depending on context. Pre-first-purchase, the abandoned cart email had a ten percent conversion rate. Post-purchase, it had twenty-two percent. But because the map was built on assumptions, they'd lumped them together and optimized for the wrong behavior. Luna: That's a great example. So how do you actually build a data layer without it becoming a massive engineering project? Lucas: You don't have to build a custom analytics platform. Most tools — Google Analytics, Mixpanel, Amplitude, even a good CRM — can export event-level data. The key is to map your touchpoints to specific events. So instead of a sticky note that says 'browse website,' you define that as 'session with at least three page views and a time on site over sixty seconds.' Now it's measurable. Luna: So you create a dictionary that links each stage in your journey to a concrete metric or event. Then you actually measure the flow between them. Lucas: Yes. And once you do, you'll almost always find a gap. Maybe thirty percent of people who click the email never land on the product page. Or your map says they go from social to blog to product, but the data shows they go from social straight to product, skipping the blog entirely. That changes content strategy. Luna: It also changes budget allocation. If you're spending on blog content thinking it's a key touchpoint, but the data shows it's rarely visited, that's money you could move somewhere else. Lucas: Exactly. And this is where I think a lot of marketing teams get stuck — they treat the journey map as a permanent artifact rather than a living model. You should be updating it quarterly as the data changes. Lucas: You know, this kind of practical, data-backed thinking is exactly the sort of thing we try to bring to every episode of this show. And if these conversations have sparked something you've actually used — maybe a new way of looking at your analytics, or a change you made to a campaign — a couple of dollars a month is genuinely what keeps these going. Buy me a coffee dot com slash fexingo. No pressure, just — if you've gotten something out of it, that's the way to keep it ad-free and independent. Luna: Yeah, I think listeners often don't realize how much time goes into researching these cases. That support really does make a difference. Lucas: Okay, back to the data layer — one more concrete tip. When you're mapping events, don't try to track everything. Pick the three to five touchpoints that matter most for conversion or retention. Start there. The e-commerce brand I mentioned started with just four events: email open, page view, add to cart, and purchase. That was enough to surface the post-purchase abandoned-cart insight. Luna: So the data layer doesn't have to be comprehensive to be useful. It just has to be aligned with the decisions you're trying to make. Lucas: Right. And the other thing is — once you have the data, you need to visualize it in a way that's useful. I've seen teams pull all this event data into a spreadsheet and then wonder why nobody uses it. Better to create a simple flow diagram with actual percentages on the arrows. People in the room need to see that 'sixty percent go here, only fifteen percent go there.' Luna: That makes it impossible to argue with. You can't say 'I think the blog is a key touchpoint' when the data says only two percent of customers visit it. Lucas: Exactly. And that's the real value of the data layer — it replaces opinion with evidence. The map becomes a tool for alignment across teams. Product might have a different view of the journey than marketing, but when you look at the same data, you can find common ground. Luna: I've seen that work. At a previous company, we had a big disagreement about whether to invest more in email or in-app messaging. Marketing wanted email, product wanted in-app. We built a simple data layer showing that email drove three times the conversion rate for first-time buyers, but in-app had higher engagement for repeat users. The answer was 'both, but at different stages.' Lucas: That's a perfect example. The data layer doesn't just tell you what's happening — it tells you where to put your energy. And it often reveals that the most important touchpoints are the ones you're not paying attention to. Lucas: So to wrap it up — if you have a customer journey map that feels like a decoration rather than a decision tool, the fix is to add a data layer. Pick your key events, measure the flows, and update it quarterly. You'll probably find at least one surprise that changes how you think about the journey. Luna: And that surprise might be the thing that moves the needle on retention or revenue. It's worth the effort. Lucas: Absolutely. Next time we'll talk about how to use that data layer to run experiments on individual touchpoints without breaking the whole journey.