Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / When Customer Journey Maps Miss the Zero-Party Data Moment
Transcript
- Lucas: When we talk about customer journey maps, we usually plot out the touchpoints where the brand pushes something out — an ad, an email, a retargeting campaign. Luna: Right, outbound. The brand initiates. Lucas: Exactly. But there's a whole category of touchpoint where the customer initiates by offering information willingly. Marketing folks call it zero-party data — data the customer deliberately shares with the brand, like their skin type, their budget range, their style preference. Luna: And most journey maps completely skip that moment. They map the ad click, the cart add, the purchase — but not the moment the customer says 'I want you to know this about me.' Lucas: Precisely. And that's a blind spot, because zero-party data is arguably the most valuable signal you can get. It's declared preference, not inferred. No third-party cookie, no probabilistic model. Just a customer volunteering information because they see value in the exchange. Lucas: Take a premium skincare brand I looked at recently. They had a decent journey map — awareness through social, consideration through reviews, purchase on site, post-purchase email sequence. Standard stuff. But their return rate was hovering around 22 percent, and their repeat purchase rate was only 14 percent within 90 days. Luna: Those numbers are pretty rough for skincare. Usually you'd expect much higher repeat if the product fits. Lucas: Exactly, and the problem was fit. People bought the wrong cleanser for their skin type, or the wrong serum strength. So the brand added a single touchpoint: a skin quiz, placed right after the first purchase confirmation but before the shipping confirmation. Luna: So not before purchase — after. That's interesting. Usually we think of quizzes as pre-purchase lead gen. Lucas: Right, and that's the conventional placement. But the brand reasoned that after purchase, the customer is already committed and more likely to engage. The quiz asked five questions: skin type, primary concern, age range, climate, and current routine. Took about 90 seconds. Luna: And what did they do with that data? Lucas: They used it to personalize the post-purchase email sequence. The first email recommended products specifically for combination skin, for example. The third email included a personalized routine guide. And here's the kicker — they also used it to suggest a different product if the quiz suggested the purchased item might not be optimal. They offered a free exchange before the customer even received the original order. Luna: That's bold. Could backfire if the customer feels second-guessed. Lucas: It could, but they framed it as 'We want you to love this — here's what customers with your skin type often prefer.' Soft suggestion. The result: repeat purchase rate went from 14 percent to 41 percent within 90 days, and return rate dropped from 22 percent to 4 percent. Luna: Those are massive shifts. And the only change was adding that one zero-party data touchpoint. Lucas: And mapping it into the journey. Before the change, the map had a gap between 'purchase complete' and 'shipping notification.' The brand wasn't treating that interval as an opportunity for data exchange. Once they saw it as a touchpoint, they designed for it. Luna: This really gets at the idea that a journey map isn't just about what the company does — it's about what the customer is willing to do at each stage. Lucas: Exactly. And customers are increasingly willing to share data if the value is clear. A 2024 study from the Customer Data Platform Institute found that 67 percent of consumers will share personal data if they understand the benefit. But only 22 percent felt brands clearly communicated that benefit. Luna: So the gap isn't willingness — it's presentation. The brand doesn't ask in the right way at the right moment. Lucas: That's the journey map insight. Most maps treat data collection as a backend operation — CRM fields, profile completion percentages. But it's actually a frontend experience. The moment a customer fills in a preference should be as carefully designed as the moment they add to cart. Luna: Let me ask a practical question: where else besides post-purchase could a zero-party data touchpoint live? I'm thinking of the pre-purchase phase too. Lucas: Sure. Pre-purchase, the classic is a product finder or style quiz. But the key is to place it at a moment of high intent — not on the homepage when someone is just browsing, but on a product page when they're comparing options. That's when they're motivated to get the right fit. Luna: So the trigger matters more than the tool. A quiz on a landing page might get low engagement, but the same quiz on a product detail page could convert. Lucas: Exactly. And the other high-leverage spot is during onboarding — for SaaS products especially. When a user signs up, they're expecting to set things up. That's a natural moment to ask about role, company size, primary goal. Slack does this well with their 'what brings you to Slack' screen. It's a single click, but it feeds their entire personalization engine. Luna: And then you can map that into the journey — the data collected at onboarding should flow directly into the next touchpoints. Otherwise you're just collecting data for data's sake. Lucas: Right, and that's a common failure. Brands collect zero-party data but don't operationalize it. They ask for skin type but still send generic emails. That breaks trust — the customer thinks 'Why did I bother telling you?' Luna: Speaking of trust — there's an ethical dimension here. Zero-party data is voluntary, but customers still want to know what you'll do with it. How should a journey map reflect that? Lucas: I think the map should include a 'privacy reassurance' touchpoint immediately after the data collection moment. A simple one-liner: 'We'll use this to personalize your experience, and we'll never sell it.' That's not just legal compliance — it's experience design. It closes the loop on the exchange. Luna: And that reassurance itself can be a trust-building moment. If you map it, you're more likely to actually include it. Lucas: Exactly. The map forces you to think about what happens before and after each touchpoint. If you add a data collection point but no follow-through, the journey has a hole. Luna: You know, this conversation reminds me of something. If today's episode sparked an idea you might actually use — maybe you're thinking about adding a preference quiz to your own post-purchase flow — that's exactly the kind of thing that makes this podcast worth supporting. Lucas: Yeah, we keep this show ad-free, and listener support is what makes that possible. If today was worth a coffee to you, there's a link — buy me a coffee dot com slash fexingo. Luna: Truly, it helps us keep digging into these specific cases and frameworks. So thank you to anyone who does. Lucas: Alright, back to the map. So we've got the zero-party data touchpoint placed in the journey, with a privacy reassurance right after. But there's another layer — how do you decide what data to ask for? Luna: I imagine you don't want to ask everything at once. That would overwhelm the customer. Lucas: Right. The rule of thumb is: only ask for data you'll act on in the next two touchpoints. If you're not going to use their budget range in the welcome email, don't ask for it during signup. Map the data to specific downstream actions. Luna: So the journey map becomes a dependency graph — this data enables that personalization. Lucas: Exactly. And that's where the real value emerges. The skincare brand I mentioned didn't just ask the quiz questions and then forget. They built a content engine: the quiz responses determined which blog posts appeared in the customer's account dashboard, which product recommendations appeared in the cart, which replenishment reminders they got. Luna: So the zero-party data became the backbone of the entire post-purchase experience. Lucas: Yes. And that's what a good journey map should show — not just isolated touchpoints, but how data flows between them. The map is a system, not a list. Luna: One last thing — what about customers who don't want to share? How do you handle that in the journey? Lucas: You design for opt-out gracefully. Maybe they get a generic experience, but still a good one. And you don't punish them with nagging. The worst thing you can do is pop up the quiz every visit. Once declined, respect that. The journey map should have a parallel path for non-sharers. Luna: That's a nice way to think about it — parallel paths based on data willingness. Lucas: Right. And over time, some non-sharers may become sharers if they see the personalized experience others get. But that's a longer play. The immediate win is mapping those few high-value zero-party data moments that already exist in your customer journey but you're not using. Luna: So the homework for listeners: pull out your current journey map, find the gaps between purchase confirmation and shipping, or between signup and first value, and ask — is there a natural moment to invite data? Lucas: And if you find it, design for it. That one touchpoint might change everything.